Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Debian 13 “Trixie”

debian.org

Post reply on HN
Print view View original

191–200 of 428 posts

Re: Debian 13 “Trixie”

#191

Post by champtar »

foresto wrote: post #158
b112 wrote: post #48

For those worrying about the NIC change with systemd, this comes from the release doc: https://www.debian.org/releases/trixie/release-notes/issues.... # example: udevadm test-builtin net_setup_link /sys/class/net/eno4 2>/dev/null ID_NET_LINK_FILE=/usr/lib/systemd/network/99-default.link ID_NET_LINK_FILE_DROPINS= ID_NET_NAME=eno4 Here's a one-liner, excluding a bond interface and lo. Gives a nice list of pre and post…

Do you happen to know if this change can affect people who have disabled systemd's Predictable* Network Interface Names before upgrading to Trixie? *haha

You can easily keep the current naming behavior with the 'net.naming_scheme=' kargs

Re: Debian 13 “Trixie”

#192

Post by jpetso »

foresto wrote: post #160
ACS_Solver wrote: post #119

Earlier quoted context omitted.

Not if you want to remain on new Plasma, you can expect Debian to lag several minor versions behind. I've found it pretty easy though to use some KDE components built from source on top of the standard Debian packages. Build with kdesrc-build, then have those binaries linked to from your ~/bin and you're set. It might get difficult if you want to rebuild some key components like plasmashell itself but I've been using…

> you can expect Debian to lag several minor versions behind. Not necessarily forever, though. Bookworm got minor Plasma updates, so I wouldn't be surprised if Trixie does as well.

Bookworm stayed on Plasma 5.27.5 when Plasma shipped bugfix releases up to 5.27.12. Debian may have cherry-picked a handful of patches from there, but that's a lot of bugfixes missed on a release that was already super old.

Even at this point, Plasma 6.4 has been out for almost two months and 6.3 will not get any more updates ever. While everyone else is upgrading, Debian is going to be stuck on an already unsupported version for another two years or however much.

Debian is great for what it is, but you better hope you don't run into issues with your desktop environment because they will not be addressed.

Re: Debian 13 “Trixie”

#193

Post by BearOso »

Santosh83 wrote: post #68
happymellon wrote: post #46

Earlier quoted context omitted.

Snaps? Proprietary package managers are never great.

As I understand it, snap the package format is not proprietary. Its as open source as say flatpak. What is proprietary is Canonical official snap store, and they patch their version of snap to only use that store. It'd be the same as flatpak being tied to only flathub. Of course that goes against the spirit of FOSS, but there's a bit more nuance there than simply saying "snaps are proprietary".

I've tried making snap packages, but I discovered they're very tightly tied to Ubuntu's base packages. They're not portable at all. In essence they're effectively just a secondary Ubuntu-specific package format for user-level applications.

For example, with flatpak you select a base runtime for your package that contains mostly system-agnostic libraries. With snap, you specify an Ubuntu version as a base runtime and additional dependencies that are Ubuntu packages.

Re: Debian 13 “Trixie”

#195

Post by __david__ »

pss314 wrote: post #137

A new APT sources format "debian.sources" is announced with trixie. The now older "sources.list" format is still supported, but is likely to be deprecated in a future Debian release. See below: APT is moving to a different format for configuring where it downloads packages from. The files /etc/apt/sources.list and *.list files in /etc/apt/sources.list.d/ are replaced by files still in that directory but with names en…

> apt modernize-sources

Oh nifty, I hand converted all mine a couple years back. It would have been nice to have that then (or know about it?). I do really like the new deb822 format, having the gpg key inline is nice. I do hope that once this is out there the folks with custom public apt repos will start giving out .sources files directly. Should be more straightforward than all the apt-key junk one used to have to do (especially when a key rotated).

Re: Debian 13 “Trixie”

#196

Post by umvi »

ACS_Solver wrote: post #25

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…

Do you usually update in place or do a fresh install whenever a new major version comes out?

Re: Debian 13 “Trixie”

#198

Post by JonChesterfield »

fhdnfjf wrote: post #190

I'm too impatient to use a non-rolling release distro like Debian as my main OS, that, by my standards, already starts a new distro version with some outdated packages. I admire Debian though and it is my favorite server OS.

Testing is a rolling release. Unstable is a more exciting rolling release.

Re: Debian 13 “Trixie”

#199

Post by foresto »

champtar wrote: post #191
foresto wrote: post #158

Earlier quoted context omitted.

Do you happen to know if this change can affect people who have disabled systemd's Predictable* Network Interface Names before upgrading to Trixie? *haha

You can easily keep the current naming behavior with the 'net.naming_scheme=' kargs

I already have systems that use net.ifnames=0. My question is about whether this new behavior can affect them.

Re: Debian 13 “Trixie”

#200

Post by hsbauauvhabzb »

AstroBen wrote: post #108
master_crab wrote: post #29

Debian 13 trixie includes numerous updated software packages (over 63% of all packages from the previous release) I’m not familiar with the metric definition they use, but I’d be worried if close to 100% of the packages they included in bookworm hadn’t been updated in the roughly 2 years between releases. I use Debian for most of my servers, so I’m sure there is a valid explanation of that phrase.

Debian stable is just that - unchanging between major Debian versions. They do however push security updates when necessary, so you're not missing out on those

Any chance you know how they manage that? Surely not every package in the repos is supported for the entire 2 year cycle, so if a vuln comes out after a major refactor, it’s surely not easy to backport the patch.
Post reply on HN