#packagerlife — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #packagerlife, aggregated by home.social.
-
-
-
Today I realized, that the history of the #fakeroot project has recently been... well... completely rewritten, all tags have been deleted and recreated (this apparently happened multiple times in the past already and upstream is not reacting to mails).
I guess you can imagine how much "fun" that is for downstreams that try to rely on this software in their critical infrastructure (building packages), while regressions happen in addition...
-
Today I realized, that the history of the #fakeroot project has recently been... well... completely rewritten, all tags have been deleted and recreated (this apparently happened multiple times in the past already and upstream is not reacting to mails).
I guess you can imagine how much "fun" that is for downstreams that try to rely on this software in their critical infrastructure (building packages), while regressions happen in addition...
-
Interesting read on the perceived immutability of #git tags and the issues that come with it:
https://arxiv.org/pdf/2606.31354
There now is a paper about what I witness every now and again: Upstreams retagging their releases and causing a mess.
-
Interesting read on the perceived immutability of #git tags and the issues that come with it:
https://arxiv.org/pdf/2606.31354
There now is a paper about what I witness every now and again: Upstreams retagging their releases and causing a mess.
-
Corporate upstream retags their project release and breaks reproducibility for all of their downstreams.
You write a detailed ticket, outlining what the problem is and why it is a security concern.
You also mention that their behavior burns downstream volunteer time.You get ignored. End of story 👏
-
Corporate upstream retags their project release and breaks reproducibility for all of their downstreams.
You write a detailed ticket, outlining what the problem is and why it is a security concern.
You also mention that their behavior burns downstream volunteer time.You get ignored. End of story 👏
-
-
-
When you manage to do two kernel builds while the test suite of a certain other project is still running (most likely to fail again under bizarre circumstances in a while).
-
When you manage to do two kernel builds while the test suite of a certain other project is still running (most likely to fail again under bizarre circumstances in a while).
-
A kernel a day keeps the advisories at bay.
-
A kernel a day keeps the advisories at bay.
-
That feeling when you have 96 cores and a couple of them are not pulling their weight. Who even gives cores permission to slack off 1%? As for 2% slack off, get with the program! Don't they understand people are waiting for their fresh Electron releases?
-
That feeling when you have 96 cores and a couple of them are not pulling their weight. Who even gives cores permission to slack off 1%? As for 2% slack off, get with the program! Don't they understand people are waiting for their fresh Electron releases?
-
It's Sunday, I'm again looking into an update to the #edk2 package and have to deal with its terrible "build system"... questioning life choices....
-
It's Sunday, I'm again looking into an update to the #edk2 package and have to deal with its terrible "build system"... questioning life choices....
-
If you ever thought Linux packaging sounded fun I'm here to save you;
I'm sitting here with a compiler that does not produce any current, nor previous, version of the same compiler that doesn't choke on an AMD specific test case.
Currently reconsidering my hobbies.
-
If you ever thought Linux packaging sounded fun I'm here to save you;
I'm sitting here with a compiler that does not produce any current, nor previous, version of the same compiler that doesn't choke on an AMD specific test case.
Currently reconsidering my hobbies.
-
#autotools is when you can't even figure out how to make the thing install libraries to the correct location... even after patching all sorts of files that probably maybe have something to do with the installation target of those files... and eventually just move files manually...
It's really incredible how much of a time sink upstreams with this terrible build system are...
-
#autotools is when you can't even figure out how to make the thing install libraries to the correct location... even after patching all sorts of files that probably maybe have something to do with the installation target of those files... and eventually just move files manually...
It's really incredible how much of a time sink upstreams with this terrible build system are...
-
A failing test suite for the Go compiler was really not on my "lets have a relaxing Sunday working through my backlog"-list.
Plz, I just want to disable dwarf5 generation.
-
A failing test suite for the Go compiler was really not on my "lets have a relaxing Sunday working through my backlog"-list.
Plz, I just want to disable dwarf5 generation.
-
#Automation gone wrong: Someone thinking that downloading the #license file(s) for their projects during build time and implicitly defining the license for their project is a great idea.
Effectively breaking hermetic build environments, building from source, being able to contribute to a project.
Off the charts on the "wat" scala.Just normal #PackagerLife at #ArchLinux (aka. dealing with bizarre ideas so you don't have to).
-
#Automation gone wrong: Someone thinking that downloading the #license file(s) for their projects during build time and implicitly defining the license for their project is a great idea.
Effectively breaking hermetic build environments, building from source, being able to contribute to a project.
Off the charts on the "wat" scala.Just normal #PackagerLife at #ArchLinux (aka. dealing with bizarre ideas so you don't have to).
-
I packaged the Stackit CLI for #openSUSE. Tested it successfully, submit request to a developer project and on to #Tumbleweed is on its way.
-
I packaged the Stackit CLI for #openSUSE. Tested it successfully, submit request to a developer project and on to #Tumbleweed is on its way.
-
sometimes, debian packaging is like:
Well you have a debian subdirectory, which you typically just place in-source; don't worry. Inside, there's three dudes in red robes with two main weapons and a ferocious devotion to the pope.
-
sometimes, debian packaging is like:
Well you have a debian subdirectory, which you typically just place in-source; don't worry. Inside, there's three dudes in red robes with two main weapons and a ferocious devotion to the pope.
-
My lazyness to configure IPv6 is being twarted. One upstream made their upstream sources only available over IPv6.
-
My lazyness to configure IPv6 is being twarted. One upstream made their upstream sources only available over IPv6.
-
This fine evening on #CursedProjects: Trying to build #EDK2 without crying too much.
The build is again broken on so many levels, it's quite frustrating tbh.
Having to deal with a super custom (and frankly quite horrific) build system and an entire boatload of git submodules sure doesn't help in even understanding what is going wrong. 👌
-
This fine evening on #CursedProjects: Trying to build #EDK2 without crying too much.
The build is again broken on so many levels, it's quite frustrating tbh.
Having to deal with a super custom (and frankly quite horrific) build system and an entire boatload of git submodules sure doesn't help in even understanding what is going wrong. 👌
-
Mumbles something about some kernel projects suddenly becoming not reproducible, using broken #makefile based setups, also offering #meson, but that being broken (and leading to differing output!!), too.
I'm quite tired of these types of untested projects, without any CI. Maintainers pointing contributors to their 10 step "easy to follow" mail based workflow isn't helping either I guess 🙄
I have less and less energy packaging stuff like that.
-
Mumbles something about some kernel projects suddenly becoming not reproducible, using broken #makefile based setups, also offering #meson, but that being broken (and leading to differing output!!), too.
I'm quite tired of these types of untested projects, without any CI. Maintainers pointing contributors to their 10 step "easy to follow" mail based workflow isn't helping either I guess 🙄
I have less and less energy packaging stuff like that.
-
After adhering to a non-standard release scheme, somewhat resembling #semver, make sure to use a different tagging scheme with the release of version 1.0.0! Remember, the first stable release is special and you want to spice things up to keep downstream packagers on their toes 👌
-
After adhering to a non-standard release scheme, somewhat resembling #semver, make sure to use a different tagging scheme with the release of version 1.0.0! Remember, the first stable release is special and you want to spice things up to keep downstream packagers on their toes 👌
-
If a long and complex manual release check list leads to basic things still missing in a release because they have been forgotten, maybe it's not time to make that list longer and more complex but to rely on #automation?
-
If a long and complex manual release check list leads to basic things still missing in a release because they have been forgotten, maybe it's not time to make that list longer and more complex but to rely on #automation?
-
#autofools is when you can't install files because of concurrency issues 👌
Please.... **please** just stop using #autotools 🥺
-
#autofools is when you can't install files because of concurrency issues 👌
Please.... **please** just stop using #autotools 🥺
-
When upstreams use custom version strings not compliant with semver to denote a pre-release while referring to said release in documentation with the semver compliant pre-release notation.... 🤦♂️
Please, just use #semver and make a downstream's life easier...
-
When upstreams use custom version strings not compliant with semver to denote a pre-release while referring to said release in documentation with the semver compliant pre-release notation.... 🤦♂️
Please, just use #semver and make a downstream's life easier...
-
-
-
> This is zqpvr. Thank you for adding the conflicts to this package. I live in New Brighton, PA. I am actually a criminal of the felon level here in the US. Your assistance is much obliged.
-
> This is zqpvr. Thank you for adding the conflicts to this package. I live in New Brighton, PA. I am actually a criminal of the felon level here in the US. Your assistance is much obliged.
-
Only once you rebuild the #Python ecosystem you notice how much #abandonware there is and how much of that is still used on a day-to-day basis 😬
-
Only once you rebuild the #Python ecosystem you notice how much #abandonware there is and how much of that is still used on a day-to-day basis 😬
-
The wheels on the rebuild goes build build build. Build Build Build. BUILD BUILD BUILD.
The wheels on the rebuild goes BUILD BUILD BUILD.
All through Python3.12.
-
The wheels on the rebuild goes build build build. Build Build Build. BUILD BUILD BUILD.
The wheels on the rebuild goes BUILD BUILD BUILD.
All through Python3.12.
-
If only I received more sweet upstream mails such as the one I got from @geonkick today! 😍
-
If only I received more sweet upstream mails such as the one I got from @geonkick today! 😍
-
Today I have updated the unholy trio of #shadow, #filesystem and #pambase on #ArchLinux for addressing more than half a dozen issues.
Always a bit scary if you don't know how much you'll break all over the place when #PAM is involved. 😬
If you're on testing, please provide feedback and signoffs!