Selfhosted

63469 readers

508 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

How much pain should I expect upgrading my server from Debian 12 to 13? (lemmy.world)

submitted 3 days ago by AMillionMonkeys@lemmy.world to c/selfhosted@lemmy.world

37 comments fedilink hide all child comments

The insidious urge to fix what ain't broke has arisen. I'll probably follow the official documentation, unless someone has a better suggestion.
I'm not running anything unusual and I haven't done much, if any, "customization". I update packages maybe a couple of times a week, so they're current.
Should I go ahead and put myself through this now, or wait until support is dropped and I'm forced?

you are viewing a single comment's thread
view the rest of the comments

[–] non_burglar@lemmy.world 10 points 2 days ago (1 children)

Most of my infra is Debian, and I did it without serious incident:

#Update everything to latest
apt update && apt upgrade && apt full-upgrade && apt --purge autoremove
reboot

#Verify that debian_version is 12.x (STOP IF NOT 12!)
cat /etc/debian_version

#Check for any pinned or held packages
apt list '?narrow(?installed, ?not(?origin(Debian)))'
apt-mark showhold

#Swap bookworm for trixie in repo files
sed -i 's/bookworm/trixie/g' /etc/apt/sources.list
sed -i 's/bookworm/trixie/g' /etc/apt/sources.list.d/*

#Carry out update
apt update
apt upgrade --without-new-pkgs -y
apt full-upgrade -y
reboot

#Verify that debian_version is 13.x
cat /etc/debian_version

#Modernize apt sources to v3
apt modernize-sources -y

And then maybe apt update to make sure the updates still work OK.

Sometimes you have to make changes to certain repos that don't have Trixie manifests, but that's easy enough to roll back.

[–] AMillionMonkeys@lemmy.world 4 points 2 days ago (1 children)

apt modernize-sources -y

Thanks for this - I hadn't seen it yet in the docs I've been looking at.
No idea what it does, but it looks legit, so I'll run it!

[–] non_burglar@lemmy.world 1 points 2 days ago* (last edited 2 days ago)

Apt v3 comes with some quality-of-life stuff that apt has been direly missing for years, and one of those is apt sources that make sense to a human.

So the new apt source files have local key location, components, suites, and Uris.

The sources from the before-time just had a one-liner with a uri and some components.

Edit:also the modernize command makes a backup of the source files it touches.