Hi Nick,
On Fri, Jan 12, 2024 at 1:05 PM Nick Rosbrook <nick.rosbrook@canonical.com> wrote:
Hi,
> I guess something in do-release-upgrade could be run to, when encountering such a situation, automatically select bin:samba-vfs-modules-extra for the upgrade as well? Is it worth it? Is there a precedence for something like this? And how would this be done in a more generic/general case, if at all?
We have the concept of "quirks"[1] in ubuntu-release-upgrader which
allows us to handle special cases like this. For example, a cycle or
two ago when flatpak was removed from flavor seeds, we added some code
to not auto-remove flatpak if it appeared the user was actively using
it. So yes, if nothing else we could add a quirk to make sure
samba-vfs-modules-extra is installed upgrades if samba-vfs-modules is
currently installed.
That sounds exactly what I need, thank a log for the pointer!
Is there an easy way to use "do-release-upgrade -d" to test my changes before proposing them, or will it always download the tarball at http://archive.ubuntu.com/ubuntu/dists/noble/main/dist-upgrader-all/current/noble.tar.gz and use that?
Thanks,
Nick
[1] https://git.launchpad.net/ubuntu-release-upgrader/tree/DistUpgrade/DistUpgradeQuirks.py
