Acknowledge. We need to identify a key package and see whether it
changes suites compared to the os-release. Usually that's base-files on
Debian.
I'll add this to my apt 3.0 UX improvements list.
** Changed in: apt (Ubuntu)
Status: Invalid => Triaged
** Tags added: foundations-todo
--
I'd like to reopen this issue. 16 years later, there are still plenty of
*informed* users who change their sources.list, run a dist-upgrade to
upgrade the release, and break their system. They then come to the
desktop team asking for help to rescue their broken system.
Even if we don't block them
apt-get is a low-level tool. The people who use it should know what they
do. Normal Ubuntu users do not even reach the point where they'd do an
apt-get dist-upgrade, so I don't see a problem here.
** Changed in: apt (Ubuntu)
Status: New = Invalid
--
You received this bug notification
How would the upgrade from one release to the next be best checked?
Probably by checking the lsb release codename versus the distribution
field in sources.list. This might conflict with users of mirrors that
might have renamed that field. So the check needs to be configurable.
--
You received
