LWN: Comments on "Removing Guix from Debian" https://lwn.net/Articles/1035491/ This is a special feed containing comments posted to the individual LWN article titled "Removing Guix from Debian". en-us Sun, 02 Nov 2025 16:16:37 +0000 Sun, 02 Nov 2025 16:16:37 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net I'd say it's fine to remove Guix from official APT repos https://lwn.net/Articles/1038065/ https://lwn.net/Articles/1038065/ joeljuca <div class="FormattedComment"> I think whoever is using Guix to manage packages outside the APT scope is fine with managing Guix itself, so I'm good with Guix being removed from APT official repos. The Guix project can always maintain a dedicated APT repo in case people really want to have an easy APT-based installation option for it.<br> <p> Guix users are quite CLI-savvy, so they should be OK with running a small pack of commands instead of a `apt-get install`...<br> </div> Sun, 14 Sep 2025 19:46:40 +0000 I hope Guix is OK https://lwn.net/Articles/1036852/ https://lwn.net/Articles/1036852/ Lennie <div class="FormattedComment"> It's the only system at the moment (in the world for any operating system I think), which can do a 'full source bootstrap':<br> <p> <a href="https://guix.gnu.org/en/blog/2023/the-full-source-bootstrap-building-from-source-all-the-way-down/">https://guix.gnu.org/en/blog/2023/the-full-source-bootstr...</a><br> <p> I think they got both amd64 and maybe also RISC-V working.<br> <p> A detailed look:<br> <p> <a href="https://simon.tournier.info/posts/2023-10-01-bootstrapping.html">https://simon.tournier.info/posts/2023-10-01-bootstrappin...</a><br> <p> A talk from last year about the RISC-V progress:<br> <p> <a href="https://archive.fosdem.org/2024/schedule/event/fosdem-2024-1755-risc-v-bootstrapping-in-guix-and-live-bootstrap/">https://archive.fosdem.org/2024/schedule/event/fosdem-202...</a><br> </div> Fri, 05 Sep 2025 11:49:10 +0000 Fasttrack time? https://lwn.net/Articles/1036673/ https://lwn.net/Articles/1036673/ hmh <div class="FormattedComment"> Apparently it would qualify for fasttrack.debian.net, yes.<br> <p> Do note the "debian.*net*" part, it is run by Debian Developers, but not really official Debian infrastructure, so YMMV.<br> <p> I would personally use it without worries, but it is best to be upfront about this.<br> </div> Thu, 04 Sep 2025 11:15:57 +0000 A daemon process? https://lwn.net/Articles/1036639/ https://lwn.net/Articles/1036639/ phlogistonjohn <div class="FormattedComment"> podman does not use a daemon by default. I think you can enable one but it's not the typical deployment AFAIK. It's one of the major architectural differences from docker.<br> </div> Wed, 03 Sep 2025 20:38:58 +0000 A daemon process? https://lwn.net/Articles/1036515/ https://lwn.net/Articles/1036515/ ebee_matteo <div class="FormattedComment"> You mean, like docker or podman do? :-D<br> </div> Wed, 03 Sep 2025 10:36:06 +0000 A daemon process? https://lwn.net/Articles/1036498/ https://lwn.net/Articles/1036498/ taladar <div class="FormattedComment"> Probably also helps if the CLI is just a client for the daemon in terms of avoiding complex locking issues between multiple CLI calls in different terminals.<br> </div> Wed, 03 Sep 2025 07:39:54 +0000 Popcon Dark Figure https://lwn.net/Articles/1036497/ https://lwn.net/Articles/1036497/ taladar <div class="FormattedComment"> If a significant number of people using popcon have already updated to trixie they are likely unrepresentative of the majority of Debian users who are certainly less on the bleeding edge. It is too early for trixie to have support in all third party repositories and applications for a significant percentage of e.g. the server users to update to it already.<br> </div> Wed, 03 Sep 2025 07:38:37 +0000 Fasttrack time? https://lwn.net/Articles/1036496/ https://lwn.net/Articles/1036496/ DemiMarie <div class="FormattedComment"> Fasttrack seems to be the beat place for stuff like this.<br> </div> Wed, 03 Sep 2025 07:08:30 +0000 Popcon Dark Figure https://lwn.net/Articles/1036492/ https://lwn.net/Articles/1036492/ LtWorf <div class="FormattedComment"> But they won't be representative…<br> </div> Wed, 03 Sep 2025 06:14:55 +0000 The way forward https://lwn.net/Articles/1036487/ https://lwn.net/Articles/1036487/ emptymargin <div class="FormattedComment"> If you're one of the ignoble 230 like I am, it's worth mentioning that Guix has updated its manual with what to do in this situation:<br> <p> &lt;<a href="https://guix.gnu.org/manual/devel/en/html_node/Upgrading-Guix.html">https://guix.gnu.org/manual/devel/en/html_node/Upgrading-...</a>&gt;<br> </div> Wed, 03 Sep 2025 01:51:05 +0000 A daemon process? https://lwn.net/Articles/1036468/ https://lwn.net/Articles/1036468/ neggles <div class="FormattedComment"> AIUI this is so the daemon can run as a different, unprivileged user, so a badly-behaved build won't have permission to mess up your filesystem or read your home directory. On paper it'd also allow sharing one set of build directories and outputs between multiple users on the same system.<br> </div> Tue, 02 Sep 2025 22:54:42 +0000 Popcon Dark Figure https://lwn.net/Articles/1036451/ https://lwn.net/Articles/1036451/ ballombe <div class="FormattedComment"> From the FAQ: &lt;<a href="https://popcon.debian.org/FAQ">https://popcon.debian.org/FAQ</a>&gt;<br> The server automatically extracts the report from the email or HTTP and stores it in a database for a maximum of 20 days or until the host sends a new report.<br> <p> So each days, only submissions younger than 20 days are considered for the statistic of the day.<br> The graphs are only provided to give an historical perspective. For example, that bookworm peaked at almost 16k submissions before the release of trixie.<br> </div> Tue, 02 Sep 2025 19:27:53 +0000 Popcon Dark Figure https://lwn.net/Articles/1036450/ https://lwn.net/Articles/1036450/ jzb <div class="FormattedComment"> I'm not sure where the 20 days figure comes from? I was looking at the "Statistics per distributions reporting to Debian" on the Stable reports tab: it says "Submissions by distributions (last 12 months)" in the bottom graph, with a figure of 134,711 on the left-hand side. I don't see any reports/graphs that are a 20-day time period on that page, nor on the other tab. <br> </div> Tue, 02 Sep 2025 19:18:51 +0000 Popcon Dark Figure https://lwn.net/Articles/1036436/ https://lwn.net/Articles/1036436/ ballombe <div class="FormattedComment"> It is not 12 months, it is 20 days!<br> bookworm count is going down from 160000 because users are upgrading to Trixie<br> </div> Tue, 02 Sep 2025 18:52:29 +0000 Vuln proof-of-concept issues https://lwn.net/Articles/1036442/ https://lwn.net/Articles/1036442/ kkremitzki <div class="FormattedComment"> I've been meaning to share these results in a more appropriate place, but for what it's worth, the proof-of-concept script for the recent Guix CVEs bisects to a Jan 2023 commit, so it's not clear that released versions are affected.<br> <p> 4cf1acc7f30 + cherry-picked 71171538e12 + 1c78f71beb3 + a49536e3200 + 7f237f3e6ca<br> </div> Tue, 02 Sep 2025 17:37:57 +0000 A daemon process? https://lwn.net/Articles/1036426/ https://lwn.net/Articles/1036426/ daroc <div class="FormattedComment"> Guix uses a separate build daemon in order to better isolate builds. The builds are done by an unprivileged user that can only see the source of the package and nothing else.<br> </div> Tue, 02 Sep 2025 16:09:56 +0000 A daemon process? https://lwn.net/Articles/1036421/ https://lwn.net/Articles/1036421/ jafd <div class="FormattedComment"> <span class="QuotedText">&gt; the guix-daemon, which is a program that is used to build software and access the store where successful builds are kept. </span><br> <p> Am I the only one who finds it quite strange that to “build software and access the store where successful builds are kept”, a daemon process is required in the first place?<br> </div> Tue, 02 Sep 2025 15:59:09 +0000 Popcon Dark Figure https://lwn.net/Articles/1036416/ https://lwn.net/Articles/1036416/ muase <div class="FormattedComment"> Ok, but that is already sufficient to put that number into relation – 200 of roundabout 135,000 gives reasonable context if we assume that the 135k are roughly representative. Thank you!<br> </div> Tue, 02 Sep 2025 15:35:12 +0000 Popcon Dark Figure https://lwn.net/Articles/1036403/ https://lwn.net/Articles/1036403/ jzb <p>If you visit the <a href="https://popcon.debian.org/">main popcon pages</a> you'll find stats on how many systems are participating in popcon and how many submissions there are. The "stable reports" tab suggests that about 135K bookworm systems have checked in in the past 12 months. Whether 135K is 10%, 20%, etc. of all installs I have no idea.</p> Tue, 02 Sep 2025 14:56:35 +0000 Popcon Dark Figure https://lwn.net/Articles/1036402/ https://lwn.net/Articles/1036402/ rschroev <div class="FormattedComment"> The statistics are available at <a href="https://popcon.debian.org/">https://popcon.debian.org/</a><br> </div> Tue, 02 Sep 2025 14:45:07 +0000 Popcon Dark Figure https://lwn.net/Articles/1036378/ https://lwn.net/Articles/1036378/ muase <div class="FormattedComment"> <span class="QuotedText">&gt; According to Debian's popularity contest (popcon) statistics, there are not quite 230 systems with Guix installed. Popcon statistics only hint at the actual number of package installs, but assuming they are approximately accurate, then removing Guix will not inconvenience a significant number of Debian users.</span><br> <p> Do we have a meta-statistic or interpolated number how many systems participate in the popularity context? As it is disabled by default – and Linux-users maybe tend to be more privacy focused – I'd imagine there is quite a number of unreported installations.<br> </div> Tue, 02 Sep 2025 14:34:51 +0000