New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
This guy gets it.
Whatever... I've been running 6.16.0 in prod for 36 minutes now ... it's fine... not a single cra
sysctl.conf is still in effect, it has just been prioritized. The result is that your original values may be overwritten by the system. Yes, you may need to create a service to go and re-read it. Dye Write the original values back.
Congrats.
Mine just hangs on reboot at the Grub menu with no available options to do anything.
I spent a total of 2 minutes messing with it. Was just a test VM created purposely for this, so I'm not bothered enough to test further.
Usually just run xanmod stable mainline kernel on all my Debian production boxes. Just wanted to mess around with a bleeding edge setup for a bit.
Anyone going to a launch party?
I've never been to a Debian launch party. I assume it's A-listers snorting cocaine off the hip bones of models and such.
My remaining Debian 10 dedis have been begging for an upgrade for a while now. Libc compatibility for them can be really annoying. Good thing I didn't give into their demands, and can go straight to 13 when I get around to upgrading them.
That, and lots of sushi of naked prostitutes.
I'm waiting for two point releases. So long Old-Stable my friend.
I wonder if its worth risking upgrading my massivegrid virtuals. Last time I rebooted one I had to reboot it from their panel like 4 or 5 times before it actually came back.
Did you check it over VNC? Could have been running fsck or something.
Yea vnc was dead too, and their panel is so dogshit slow its painful. I think its simply their systems are so incredibly oversold that the boot process couldn't even complete. It only happened the one time but ever since I'm super hesitant to reboot heh.
I just upgraded one of my idlers (DeluxeHost), and it went smoothly. I didn't check any details before running the upgrade, just changed the repo and rebooted afterward.
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 ending in .sources, using the new, more readable (deb822 style) format.
apt-get in 2025 this guy!
damn, I was just about to upgrade but maybe I just wait awhile with xanmod
Nah, I got it working. Was missing a/some package(s).
sudo apt install --no-install-recommends dkms libdw-dev clang lld llvmand was golden.Well both my MassiveGRID units behaved responsibly and are now Trixie champs.
wot?
Ah teasing, I can't actually remember why I switched to using apt.. I wonder if it was just fewer characters to type.
Debian 13 “trixie” released
https://www.debian.org/News/2025/20250809
It's sudo apt full-upgrade not sudo apt dist upgrade
As of right now, the web page hasn't yet been updated, but you can download the netinstall ISO for Debian 13 via https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-13.0.0-amd64-netinst.iso
Debian 13 is out now
I got a new VPS provisioned to me recently. Debian 12. Is it fine to do sudo apt full-upgrade to get onto 13, or is there a risk in doing it this way and it would be better to wait to until the VPS host has 13 available on their end and have them re-image it from scratch?
In general, a fresh install of a new major version is to be preferred if this is a viable option
I've seen this said more than a few times on the debian-users list and I've often wondered where the idea comes from but never asked, now's my chance! Where does this come from and is it something you actually do?
If I had to install fresh I'd toss debian in the trash in a hot second.
I have upgraded Debian at least 4 versions without any issues , maybe it was just luck
Is it really so puzzling?
A fresh install simply avoids any number of potential conflicts/issues that one might experience when trying to upgrade an existing installation
There's a reason why (e.g.) RHEL doesn't (or didn't) support upgrades to major versions.
That said, Debian upgrades to major versions generally succeed well, and a fresh install isn't always a viable option
Why...?
I think this is a bit of old Unix neckbeard legend.
RHEL was special though, critical boxes sat there until you were standing up new hardware.. less critical still got upgraded, it just wasn't supported by RH. Anyway, I understand.
Debian teams have always put insane effort into upgrade-ability though, seems a shame to just wave it off because anything's possible.