I'm going to have a lot of fun abusing the package manager here. The obvious first step is preventing wireless-regdb updates which is comparatively easy.
The 2nd step is ensuring that we can actually remove the wireless-regdb package such that you don't get held back packages. So we need to convince dpkg that wireless-regdb no longer owns these files, which is going to involve us more or less running sed on its list of files in the dpkg database. I'm not sure how we can actually remove wireless-regdb given that if we made boot-managed-by-snapd Conflict with it, it would always try to remove it before we got a chance to make removals work... There is the other way: We make wireless-regdb upgradable. 1. We introduce changes to sneakingly add diversions into boot-managed- by-snapd (= 5~24.04.1, etc) that do not actually move the files being diverted but just register them as diverted 2. We upload wireless-regdb Conflicts: boot-managed-by-snapd (<< 5~) such that boot-managed-by-snapd needs to be upgraded first Then wireless-regdb can be updated, it just doesn't do anything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2096979 Title: wireless-regdb update problem at Ubuntu 24.04.1 TPM-backed Full Disk Encryption setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boot-managed-by-snapd/+bug/2096979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
