[Bug 281232] Re: apt-get dist-upgrade shouldn't run when asked to upgrade between two releases

Julian Andres Klode 281232 at bugs.launchpad.net
Thu May 9 14:13:12 UTC 2024


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

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/281232

Title:
  apt-get dist-upgrade shouldn't run when asked to upgrade between two
  releases

Status in apt package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: apt

  apt-get dist-upgrade is not a supported upgrade path for upgrading
  from one release to another (e.g. hardy to intrepid).  However, I see
  a lot of people who a) don't realise it's not a supported upgrade path
  (for various reasons) and b) don't even realise do-release-upgrade
  exists.

  I think it'd be really useful to alter apt to check to see whether the
  dist-upgrade it's being asked to do is across releases and refuse to
  run if it is (or at least require confirmation like removing essential
  packages does) and suggest the user use do-release-upgrade instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/281232/+subscriptions




More information about the foundations-bugs mailing list