You are not logged in.
Hey guys,
Excellent work on the new release. I'm excited to give it a shot this weekend.
The one thing that is a bit strange with debian stable is the fact that it _isn't_ a rolling release model, and upgrades usually involve manually maintaining important files and information while completely blowing away your OS and installing the latest release. This is fun and cathartic and something I typically enjoy, but people inevitably ask about upgrades and the feedback is usually that userspace stuff won't change without significant manual intervention.
Here's an idea - how hard would it be to write some sort of script which can iterate through each userspace change between versions and ask the user, following an upgrade/dist-upgrade, to update each? Ostensibly it'd be copying things from /etc/skel or something along those lines, but each file or setting could be confirmed by the user. Think of it like a dist-upgrade when there's some kind of configuration conflict and apt gives you the option to use what's on disk, what the package maintainer wrote, and other options to diff the configs or open up a text editor.
Thoughts here? What would be the engineering lift for something like this? It _should_ be straightforward enough to build an initial framework to take care of this, no?
Offline
You mean like this?
bl-user-setup --refresh
Offline
Sounds like what happens when a config file in /etc gets changed on a package upgrade and you get promoted whether you want to use the developer's file, keep existing or to see the difference between them. Something like that should be useful for user config files as well despite user files not being touched on package upgrades.
Real Men Use Linux
Offline
The one thing that is a bit strange with debian stable is the fact that it _isn't_ a rolling release model, and upgrades usually involve manually maintaining important files and information while completely blowing away your OS and installing the latest release.
I transitioned the family laptop from jessie to stretch just fine, there were no problems whatsoever and it rebooted into a functional desktop and I had *lots* of added foreign repositories in that system.
I also tested the jessie → stretch change in BunsenLabs systems a few times and they all went through cleanly.
And transition problem threads are pretty rare over at forums.debian.net despite the fact that Debian do actually recommend an upgrade rather than a reinstall.
Did you follow the guides supplied by Debian when attempting your upgrades in the past?
They are very detailed:
Offline