Thank you to all the Debian volunteers that make Debian and all its derivatives possible. It's remarkable how many people and businesses have been enabled by your work. Thank you! On a personal note, Trixie is very exciting for me because my side project, ntfy [1], was packaged [2] and is now included in Trixie. I only learned about the fact that it was included very late in cycle when the package maintainer asked fo…
Debian 13 “Trixie”
51–60 of 428 posts
Re: Debian 13 “Trixie”
#52Re: Debian 13 “Trixie”
#53> The overall disk usage for trixie is 403,854,660 kB (403 GB) What does this mean? If all 69k+ packages are installed, it will take up this much space?
Re: Debian 13 “Trixie”
#54Earlier quoted context omitted.
Snaps? Proprietary package managers are never great.
I don't really understand why this is such a big problem. You don't have to use snaps.
Using apt to install some packages installs snap plumbing and downloads the package as a snap automatically. You don't have to install it manually.
There's no malicious intent though, it's made to "impose a positive pressure on the snap team to produce better work and keep their quality high" (paraphrased, but this was the official answer).
Re: Debian 13 “Trixie”
#55Earlier quoted context omitted.
Snaps? Proprietary package managers are never great.
I don't really understand why this is such a big problem. You don't have to use snaps.
Re: Debian 13 “Trixie”
#56> i386 is no longer supported as a regular architecture: there is no official kernel and no Debian installer for i386 systems. The i386 architecture is now only intended to be used on a 64-bit (amd64) CPU. Users running i386 systems should not upgrade to trixie. Instead, Debian recommends either reinstalling them as amd64, where possible, or retiring the hardware. Impressive that i386 support made it all the way to A…
Hopefully i386 (or perhaps a new i386-like port with added support for 64-bit time values) can move to the unofficial Debian Ports infrastructure for Debian 14 (forky) or Debian 15 (duke). Debian Ports has a m68k port, so supporting one for i386 shouldn't be a huge problem.
I am not happy about unnecessary ewaste, but an i386 almost certainly has and order of magnitude less horsepower than a raspberry pi or N100.
Re: Debian 13 “Trixie”
#57My 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.
Re: Debian 13 “Trixie”
#58[flagged]
that's not 'content about the increasing politicization of Linux', that's just whiny reverse-victim maga youtuber ragebait. Sail on right past it.
Re: Debian 13 “Trixie”
#59> i386 is no longer supported as a regular architecture: there is no official kernel and no Debian installer for i386 systems. The i386 architecture is now only intended to be used on a 64-bit (amd64) CPU. Users running i386 systems should not upgrade to trixie. Instead, Debian recommends either reinstalling them as amd64, where possible, or retiring the hardware. Impressive that i386 support made it all the way to A…
Hopefully i386 (or perhaps a new i386-like port with added support for 64-bit time values) can move to the unofficial Debian Ports infrastructure for Debian 14 (forky) or Debian 15 (duke). Debian Ports has a m68k port, so supporting one for i386 shouldn't be a huge problem.
If that's all there's to it, you can still use debootstrap, compile a kernel, and point the root parameter to your shiny new install.
If the official i386 arch was built with instructions that your hardware doesn't support, tough cookies.
Re: Debian 13 “Trixie”
#60Writing 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?
snap, lxd (not lxc!), mir, upstart, ufw.
It's neverending, and it's always failing.