Live data from Hacker News

Debian 13 “Trixie”

debian.org

301–310 of 428 posts

Re: Debian 13 “Trixie”

#301

> Users running i386 systems should not upgrade to trixie. Instead, Debian recommends either reinstalling them as amd64, where possible, or retiring the hardware. What I did is switch to NetBSD.

In the abstract I'm a big fan of supporting me old machines forever, but I have to ask out of curiosity - what hardware is practical to run these days and only has a 32-bit processor?

I have a few old PCs (towers) here which don't support amd64 mostly Pentium 4-based.

They all still have DVD reader drives and are nice for ripping CDs. Despite the fact that the drives are nearing 20 years of age (machines are from ~2005) they still perform better than most “new” external drives. Of course one could also move the drives to a newer machine but many of them use the IDE connector which is not commonly found on modern systems. Also, modern cases typically don't account for (multiple) 5.25" drives.

The other use case is to flash microcontrollers. When fiddeling around with electronics there is always a risk of a short circuit or other error that could in worst case kill the attached PC's mainboard. I feel much safer attaching my self-built electronics to an old machine than to my amd64 workstation.

Due to their age, I think the old machines may not live much longer -- I fear not even 10 more years, some of my old 32-bit laptops have already failed. Hence even for me it does not make sense to try keeping up the software support. Maybe I switch them to a BSD or other Linux distribution if they live long enough but for now the machines run OK with Debian Bookworm (newly oldstable), too.

Re: Debian 13 “Trixie”

#303
post #296

They only mentioned it briefly, and not by number, but this release includes 95%+ bit-for-bit reproducibility on AMD64, ARM64, and RISC-V across more than 30,000 packages (92% mean across all architectures). Congratulations to the team--phenomenal work! https://reproduce.debian.net/

Is there a tool on a given debian trixie system to know what installed packages are not currently reproducible? Alternative to parsing the reproduce web site :)

Yes! From the site: sudo apt install debian-repro-status; debian-repro-status

Re: Debian 13 “Trixie”

#304
post #44

Writing this from my Debian system, it's a great distro that has been excellent to me as a daily driver. I switched to Debian 6 after Ubuntu went way downhill and haven't had cause to regret it. I like Debian's measured pragmatism with ideology, how it's a distro of free software by default but it also makes it easy to install non-free software or firmware blobs. I like Debian's package guidelines, I like dpkg, I lik…

> after Ubuntu went way downhill and haven't had cause to regret it. In what way Ubuntu went downhill?

Amazon ads in the Unity application menu (what was it called, 'lenses' or something?).

Re: Debian 13 “Trixie”

#305
post #84

Earlier quoted context omitted.

The maintainer has a short explanation here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098866#10 > The webapp is a nodejs app that requires packages that are not currently in debian. Since vendoring dependencies inside packages is frowned upon in Debian, the maintainer would have needed to add those packages themselves and maintain them. My guess is that they didn't want to take on that effort.

> but several features in ntfy won't be available through debian packaging due to missing golang and nodejs packages Woah. Shouldn’t Node and Golang be in Debian’s official repos by now?

Nodejs itself is, but when you install a node project manually, you type npm install and wait while it downloads the 500 different packages it depends on.

Debian follows the same philosophy as for other more traditional languages and expects that all these dependencies are packaged as individual Debian packages.

Re: Debian 13 “Trixie”

#306

Debian's signature feature (upgrade from stable to stable under 15 minutes) shines here too. My first system migrated in less than 10 minutes, incl. package downloads and reboot. It's not a beast either. N100 mini PC connected to a ~50mbps network.

What was the process for this? Does it involve manually modifying the sources.lists files, or is there a single command to instigate the upgrade?

Re: Debian 13 “Trixie”

#307
I've been on Debian forever and love it to bits. But in an act which can only be described as batshit insanity, they have chosen to patch Python's pip3 in a manner which breaks the --prefix option. On Debian

  pip3 install  --prefix=/usr/local
will install into /usr/local/local, so one has to use the prefix /usr. The same command on, say, OpenSuSE will install into /usr and break your system. Barking mad.

https://sources.debian.org/src/python3.7/3.7.3-2+deb10u3/deb...

Re: Debian 13 “Trixie”

#308
post #67
post #49

Earlier quoted context omitted.

I don't really understand why this is such a big problem. You don't have to use snaps.

I'm with my neighbor comments. How do you use Ubuntu without snaps? The base Ubuntu install already comes with several snaps. Installing random things through apt leads to snaps. I personally do not know how to avoid snaps on Ubuntu.

You migrate to Debian. Everything else is a bandaid that can be rug pulled any time Canonical feels like doing so.

Re: Debian 13 “Trixie”

#309
post #116

I love Debian and have a tremendous amount of respect for the people who work on the project. I no longer use Debian, but I think it's vitally important to have an anchor Linux distribution which isn't overly reliant on a for-profit entity and is truly community driven.

Arch isn't truly community driven?

Re: Debian 13 “Trixie”

#310

Writing this from my Debian system, it's a great distro that has been excellent to me as a daily driver. I switched to Debian 6 after Ubuntu went way downhill and haven't had cause to regret it. I like Debian's measured pragmatism with ideology, how it's a distro of free software by default but it also makes it easy to install non-free software or firmware blobs. I like Debian's package guidelines, I like dpkg, I lik…

You weren't around for when they broke the OpenSSL random number generator for no good reason. That was back in 2008 and it created vulnerabilities that persist to this day. https://16years.secvuln.info/ I still use Debian but it's hard to forget stuff like that even after all these years.

What do you expect Debian to do today about this 17 years old incident?
Post reply on HN