home.social

#packagerlife — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #packagerlife, aggregated by home.social.

  1. 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...

    #ArchLinux #PackagerLife

  2. 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...

    #ArchLinux #PackagerLife

  3. Upstream has a flaky test written in #Perl. You open a ticket about it and skip the test.

    Two years later, upstream has rewritten the test in #Python. But it's still flaky. 🥲

    #ArchLinux #PackagerLife

  4. Interesting read on the perceived immutability of #git tags and the issues that come with it:

    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.

    #PackageManager #Distribution
    #PackagerLife #ArchLinux

  5. Interesting read on the perceived immutability of #git tags and the issues that come with it:

    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.

    #PackageManager #Distribution
    #PackagerLife #ArchLinux

  6. 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....

    #ArchLinux #PackagerLife

  7. 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....

    #ArchLinux #PackagerLife

  8. 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....

    #ArchLinux #PackagerLife

  9. 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....

    #ArchLinux #PackagerLife

  10. 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....

    #ArchLinux #PackagerLife

  11. #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...

    #ArchLinux #PackagerLife

  12. #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...

    #ArchLinux #PackagerLife

  13. 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. 👌

    #ArchLinux #PackagerLife

  14. 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. 👌

    #ArchLinux #PackagerLife

  15. 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. 👌

    #ArchLinux #PackagerLife

  16. 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. 👌

    #ArchLinux #PackagerLife

  17. 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. 👌

    #ArchLinux #PackagerLife

  18. #autofools is when you can't install files because of concurrency issues 👌

    Please.... **please** just stop using #autotools 🥺

    #ArchLinux #PackagerLife

  19. #autofools is when you can't install files because of concurrency issues 👌

    Please.... **please** just stop using #autotools 🥺

    #ArchLinux #PackagerLife

  20. Some #corporate #opensource #python #upstreams are more cursed than others.

    We experience packager drain on #molecule and #ansible related packages, as upstream knowingly breaks compatibility from time to time and doesn't guard or test against it properly. Instead afterwards suggests to "just pin it" 🤡 (which does not work after the fact in system packaging).

    Soon they will have their wish fulfilled when no one wants to touch that stuff for packaging anymore...

    #ArchLinux #packagerlife

  21. Some #corporate #opensource #python #upstreams are more cursed than others.

    We experience packager drain on #molecule and #ansible related packages, as upstream knowingly breaks compatibility from time to time and doesn't guard or test against it properly. Instead afterwards suggests to "just pin it" 🤡 (which does not work after the fact in system packaging).

    Soon they will have their wish fulfilled when no one wants to touch that stuff for packaging anymore...

    #ArchLinux #packagerlife

  22. Some #corporate #opensource #python #upstreams are more cursed than others.

    We experience packager drain on #molecule and #ansible related packages, as upstream knowingly breaks compatibility from time to time and doesn't guard or test against it properly. Instead afterwards suggests to "just pin it" 🤡 (which does not work after the fact in system packaging).

    Soon they will have their wish fulfilled when no one wants to touch that stuff for packaging anymore...

    #ArchLinux #packagerlife

  23. Some #corporate #opensource #python #upstreams are more cursed than others.

    We experience packager drain on #molecule and #ansible related packages, as upstream knowingly breaks compatibility from time to time and doesn't guard or test against it properly. Instead afterwards suggests to "just pin it" 🤡 (which does not work after the fact in system packaging).

    Soon they will have their wish fulfilled when no one wants to touch that stuff for packaging anymore...

    #ArchLinux #packagerlife

  24. Some #corporate #opensource #python #upstreams are more cursed than others.

    We experience packager drain on #molecule and #ansible related packages, as upstream knowingly breaks compatibility from time to time and doesn't guard or test against it properly. Instead afterwards suggests to "just pin it" 🤡 (which does not work after the fact in system packaging).

    Soon they will have their wish fulfilled when no one wants to touch that stuff for packaging anymore...

    #ArchLinux #packagerlife

  25. Starting to #bisect #edk2 #ovmf stuff because the #microvm blobs don't build anymore since last release...

    If only they had a build system that is at least somewhat comprehensive and not a bizarre monster of #shell and #python scripts mangled together with some #make and other bits and pieces 🥺

    #archlinux #packagerlife

  26. Blast from the past!

    Sometimes upstreams do weird things (especially the ones without any version control or transparency) and you only find out much much later: bugs.archlinux.org/task/77963

    #archlinux #ladspa #packagerlife

  27. Blast from the past!

    Sometimes upstreams do weird things (especially the ones without any version control or transparency) and you only find out much much later: bugs.archlinux.org/task/77963

    #archlinux #ladspa #packagerlife