We already have container images for use with bootc of many non-Fedora distros (including Debian). This is (part of) the groundwork I alluded to earlier. So it's definitely possible. But I agree with you: it will only happen after the people in charge are interested in solving this.

And even if I'm being (very) optimistic, I can only see an officially supported bootc-variant of Debian come into fruition if it's necessarily better than the alternative; kinda like how systemd replaced the default init on most distros. And, even then, I only expect it to live alongside traditional Debian. As I'm simply unsure whether all of its kinks will eventually be ironed out. Only time will tell...

Fedora Atomic and its derivatives (like Bazzite and its uBlue-siblings). I wouldn't be surprised if the same applies to NixOS and other (paradigm-wise/philosophically-)related projects.

But that's the thing, I (and together with me many others) have already been doing this for a couple of years now. Granted, this is on another distro*. But I honestly don't know why it wouldn't be possible on Debian; perhaps (some of) the groundwork has already been put into place 😉.

The possibility of unattended major upgrades would without a doubt be an upgrade over this ~~mess~~. Even if it becomes possible, it doesn't have to be enabled by default anyways. So, if you don't like it, then you should be able to only make use of UnattendedUpgrades for minor upgrades; if at all*.

Besides, I don't think the crowds that use Fedora or Ubuntu Interim are necessarily opposed to it. Especially not if it's just seamless. Like, what would be even there to oppose if it doesn't introduce any troubles?

?

You can easily disable or uninstall unattended upgrades, and I would definitely have noticed if Debian’s unattended upgrades automatically did major release upgrades on its own …

To be clear, the automatic major release updates in the background does not happen on Debian. I was describing the experience on my daily driver; which happens to be another distro. That's why I wish to see the day in which Debian does receive this. I'm aware of UnattendedUpgrades doing minor upgrades only; so no major upgrades*.

IMO that’s not an issue at all, both Debian and Ubuntu are very good about providing security updates for their oldstable releases. Maybe your desktop environment or text editor isn’t going to receive updates anymore, but I have a really hard time imagining a relevant scenario where that makes a difference for security.

I absolutely love the effort put in by Debian's Security Team. But as they only provide it for three years after release, I don't feel confident to continue using it, even if I value the work of the group of volunteers that make Debian LTS possible. Note that "too paranoid" were keywords in my previous message.

I did maybe half of these steps and it still went without issue.

That's cool and all. But, to give some context as to where I'm coming from: for the last 2-3 years or so, I receive automatic major release updates in the background. Sometimes, it takes me up to a week before I even notice it. I wish to see the day that Debian is released from its ~~Un~~attendedUpgrades shackles and can ascend into pure bliss.

I’m a big fan of skipping over one major release when upgrading

I'm too paranoid on security to consider that 😅. But I'm glad it works out for you.

Thank you for that! IIRC, it was one of the settings I took from bash-sensible. I can say that it definitely improved after just a couple of changes to ~/.bashrc. Add in ble.sh and it suddenly seemed somewhat modern instead of archaic.

Unfortunately, I don't remember exactly what broke the camel's back. However, FWIW, contrary to how I recall my experiences with bash and zsh, I don't feel any frustration while using using fish. So it's definitely doing something for me 😉.

Thank you so much for the elaborate answer! Have a good one!

I suppose COSMIC technically never migrated/transitioned from X11 to Wayland, because it's been Wayland-only from inception.

I definitely agree with you on GNOME being rather opinionated. Perhaps more so than most other DEs.

Anyhow, thanks again for appreciating my input and compliments!

Nekoray in particular doesn’t have .rpm

Perhaps they don't provide any themselves. But installing it from a repository is preferred anyways. To be clear, it's found within Terra's repository. The very same Terra repository that's enabled by default on Bazzite. So, as I see it, there's nothing that would prevent rpm-ostree install nekoray from working. Have you even tried this?

I don't know why V2RayN doesn't work though. Try Nekoray and let us know how it goes.

EDIT: I just noticed how Nekoray has seemingly lost its maintainer. Thankfully, someone forked it and renamed it to Throne. And, with it, we find ourselves an RPM repository to install from. Thankfully, you don't even have to go through any hoops, as it's also found in the Terra repository. So you're simply one rpm-ostree install throne removed from installing it.

What have you tried? Why doesn't rpm-ostree install nekoray work for you?