home.social

#packagemanagement — Public Fediverse posts

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

  1. #Sandogasa update - now integrating our standalone tools we use for @centos #CentOSHyperscale work, as well as a long-overdue revamp of #ebranch for those who often backport large package sets from @fedora to #EPEL !

    michel-slm.name/posts/2026-04-

    This post is day 35 of my #100DaysToOffload challenge. Visit 100daystooffload.com to get more info, or to get involved.

    #centos #fedora #foss #LLM #PackageManagement #rust

  2. New guide on getnix.io — "What is Nix?"

    A beginner-friendly intro to what Nix actually is, how it differs from Docker/Homebrew/Apt/Ansible, and the core concepts you need before diving in. If you've ever wondered why people keep talking about Nix, this one's for you.

    getnix.io/guides/what-is-nix/

    #Nix #NixOS #Linux #macOS #DevOps #ReproducibleBuilds #PackageManagement

  3. Vintage DebConf7 gem: Alain Schröder on "Data Mining Popcon" — how Debian's Popularity Contest can suggest packages. A fascinating mix of data mining and package management for Debian fans! #Debian #DebConf7 #DataMining #Popcon #PackageManagement #OpenSource #Linux #FOSS #English
    tube.grin.hu/videos/watch/945e

  4. Vintage DebConf7 gem: Alain Schröder on "Data Mining Popcon" — how Debian's Popularity Contest can suggest packages. A fascinating mix of data mining and package management for Debian fans! #Debian #DebConf7 #DataMining #Popcon #PackageManagement #OpenSource #Linux #FOSS #English
    tube.grin.hu/videos/watch/945e

  5. Announcing sandogasa (why? it's a Japanese straw hat often associated with post-apocalyptic robots) - a collection of tools and libraries for @fedora packaging workflows.

    With emoji support!

    Status: 🥱 out of hours

    michel-slm.name/posts/2026-03-

    This post is day 33 of my #100DaysToOffload challenge. Visit 100daystooffload.com to get more info, or to get involved.

    #Fedora #LLM #PackageManagement #Rust

  6. Learn how to install Flatpak apps on an offline Linux system without Internet. Step-by-step commands for Debian, Ubuntu, Fedora, and all major distro.

    Step-by-Step Guide here: ostechnix.com/install-flatpak-

    #Flatpak #Packagemanagement #Linux #Debian #Ubuntu #Fedora #Linuxhowto #Linuxcommands

  7. Learn how to safely fix "E: Unable to parse package file /var/lib/apt/lists" error in Debian and Ubuntu Linux, without data lose.

    Step-by-Step Guide here: ostechnix.com/fix-apt-unable-t

    #Debian #ubuntu #Apt #Linux #Troubleshooting #PackageManagement #Linuxhowto

  8. I'm trying to understand / implement dependency resolving using the pubgrub algorithm (to use in my buildsystem nitto). But I keep running into bugs; The newset one:

    Suppose we have the following state:
    ```
    root 1.0.0 -> foo ^1.0.0, bar ^1.0.0
    foo 1.1.0 -> bar ^2.0.0
    foo 1.0.0 -> n/a
    bar 1.0.0 -> n/a
    bar 1.1.0 -> n/a
    bar 2.0.0 -> n/a
    ```

    Now after avoiding a conflict and by choosing to not select `foo 1.1.0` and deriving `not foo 1.1.0` from `{foo 1.1.0, not bar ^2.0.0}`, it derives `foo ^1.0.0` from `{root 1.0.0, not foo ^1.0.0}` even tho it is already an derivation term in the assignments! Aparentily it relates `not foo ^1.0.0` as as overlapping, and wants to add it again to the partial solution...

    #pubgrub #packagemanager #packagemanagement #dependencyresolution #programming #developing #coding #softwaredevelopment #foss #floss

  9. I'm trying to understand / implement dependency resolving using the pubgrub algorithm (to use in my buildsystem nitto). But I keep running into bugs; The newset one:

    Suppose we have the following state:
    ```
    root 1.0.0 -> foo ^1.0.0, bar ^1.0.0
    foo 1.1.0 -> bar ^2.0.0
    foo 1.0.0 -> n/a
    bar 1.0.0 -> n/a
    bar 1.1.0 -> n/a
    bar 2.0.0 -> n/a
    ```

    Now after avoiding a conflict and by choosing to not select `foo 1.1.0` and deriving `not foo 1.1.0` from `{foo 1.1.0, not bar ^2.0.0}`, it derives `foo ^1.0.0` from `{root 1.0.0, not foo ^1.0.0}` even tho it is already an derivation term in the assignments! Aparentily it relates `not foo ^1.0.0` as as overlapping, and wants to add it again to the partial solution...

    #pubgrub #packagemanager #packagemanagement #dependencyresolution #programming #developing #coding #softwaredevelopment #foss #floss

  10. I'm trying to understand / implement dependency resolving using the pubgrub algorithm (to use in my buildsystem nitto). But I keep running into bugs; The newset one:

    Suppose we have the following state:
    ```
    root 1.0.0 -> foo ^1.0.0, bar ^1.0.0
    foo 1.1.0 -> bar ^2.0.0
    foo 1.0.0 -> n/a
    bar 1.0.0 -> n/a
    bar 1.1.0 -> n/a
    bar 2.0.0 -> n/a
    ```

    Now after avoiding a conflict and by choosing to not select `foo 1.1.0` and deriving `not foo 1.1.0` from `{foo 1.1.0, not bar ^2.0.0}`, it derives `foo ^1.0.0` from `{root 1.0.0, not foo ^1.0.0}` even tho it is already an derivation term in the assignments! Aparentily it relates `not foo ^1.0.0` as as overlapping, and wants to add it again to the partial solution...

    #pubgrub #packagemanager #packagemanagement #dependencyresolution #programming #developing #coding #softwaredevelopment #foss #floss

  11. I'm trying to understand / implement dependency resolving using the pubgrub algorithm (to use in my buildsystem nitto). But I keep running into bugs; The newset one:

    Suppose we have the following state:
    ```
    root 1.0.0 -> foo ^1.0.0, bar ^1.0.0
    foo 1.1.0 -> bar ^2.0.0
    foo 1.0.0 -> n/a
    bar 1.0.0 -> n/a
    bar 1.1.0 -> n/a
    bar 2.0.0 -> n/a
    ```

    Now after avoiding a conflict and by choosing to not select `foo 1.1.0` and deriving `not foo 1.1.0` from `{foo 1.1.0, not bar ^2.0.0}`, it derives `foo ^1.0.0` from `{root 1.0.0, not foo ^1.0.0}` even tho it is already an derivation term in the assignments! Aparentily it relates `not foo ^1.0.0` as as overlapping, and wants to add it again to the partial solution...

    #pubgrub #packagemanager #packagemanagement #dependencyresolution #programming #developing #coding #softwaredevelopment #foss #floss

  12. #Notepad plus plus reminds us to thank our package maintainers for doing what they do.

    Tbh not having a #packagemanager seems kind of barbaric to me.

    #PackageManagement is a public good.

  13. I have been thinking for a while that I wanted to write a blog post on how the problem of inspecting "hostile python environments" exists and how picopip was born as a solution to that problem.

    This evening I decided it was finally time to put might thoughts in line and write them down. I hope it will be at least an interesting read for some people.

    open.substack.com/pub/amolnote

  14. My first article for Towards Data Science!

    How sharded repodata (CEP-16) makes conda and Pixi 10x faster with 90% less bandwidth on conda-forge.

    Thanks to Bas Zalmstra, @dholth, and the teams at @prefix, Anaconda, and Quansight.
    towardsdatascience.com/why-pac

    #PackageManagement #OpenSource #Python #Conda #Pixi #DataScience

  15. My first article for Towards Data Science!

    How sharded repodata (CEP-16) makes conda and Pixi 10x faster with 90% less bandwidth on conda-forge.

    Thanks to Bas Zalmstra, @dholth, and the teams at @prefix, Anaconda, and Quansight.
    towardsdatascience.com/why-pac

  16. My first article for Towards Data Science!

    How sharded repodata (CEP-16) makes conda and Pixi 10x faster with 90% less bandwidth on conda-forge.

    Thanks to Bas Zalmstra, @dholth, and the teams at @prefix, Anaconda, and Quansight.
    towardsdatascience.com/why-pac

    #PackageManagement #OpenSource #Python #Conda #Pixi #DataScience

  17. My first article for Towards Data Science!

    How sharded repodata (CEP-16) makes conda and Pixi 10x faster with 90% less bandwidth on conda-forge.

    Thanks to Bas Zalmstra, @dholth, and the teams at @prefix, Anaconda, and Quansight.
    towardsdatascience.com/why-pac

    #PackageManagement #OpenSource #Python #Conda #Pixi #DataScience

  18. My first article for Towards Data Science!

    How sharded repodata (CEP-16) makes conda and Pixi 10x faster with 90% less bandwidth on conda-forge.

    Thanks to Bas Zalmstra, @dholth, and the teams at @prefix, Anaconda, and Quansight.
    towardsdatascience.com/why-pac

    #PackageManagement #OpenSource #Python #Conda #Pixi #DataScience

  19. Any #unity3d #gamedev knows why opening the "Unity Registry" tab of Unity package manager always takes between 3-7 bussiness days? Shouldn't it just be a simple web request?

    #unity #packagemanagement #upm #unity2d

  20. Any #unity3d #gamedev knows why opening the "Unity Registry" tab of Unity package manager always takes between 3-7 bussiness days? Shouldn't it just be a simple web request?

    #unity #packagemanagement #upm #unity2d

  21. Any #unity3d #gamedev knows why opening the "Unity Registry" tab of Unity package manager always takes between 3-7 bussiness days? Shouldn't it just be a simple web request?

    #unity #packagemanagement #upm #unity2d