#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...
-
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...
-
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.
-
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.
-
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 👏
-
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 👏
-
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).
-
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).
-
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.
-
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?
-
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....
-
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....
-
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.
-
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.
-
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...
-
#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...
-
#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.
