Originally I was going to make the argument that three replacements for
dmraid are not on-disk compatible, and therefore the Debian removal
rationale is disingenuous for anyone who is upgrading a system that
relies on this.

However, the fact that this has already been broken for two LTS cycles
without any Ubuntu developers noticing and having no capacity to test,
and we've effectively had only one user bug report about it, gives lie
to the idea that we can let this coast without upstream support and
without impact to our users.

So I am +1 now for removal; it's better to have a clean drop.

We should also add an ubuntu-release-upgrade quirk to block users from
upgrading to a release that will not support their disk.  Whether that
is added to the upgrader going back to upgrades to jammy, or whether we
SRU the udev fix to jammy and noble and only block upgrades to oracular
and later, I have no opinion.

** Changed in: dmraid (Ubuntu)
       Status: Confirmed => Triaged

** Also affects: ubuntu-release-upgrader (Ubuntu)
   Importance: Undecided
       Status: New

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

Title:
  Remove dmraid from oracular?

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to