Hi @Andreas! Per our conversation (for future reference):
1. do-release-upgrade: nothing happens. Upgrading the wsl-setup package won't trigger any scripts per se. The content introduced in version 0.5.8 is only invoked by WSL itself (the Windows machinery) at provisioning time. WSL has no notion of internal upgrades, so nothing will invoke the new script or make use of the new contents herein introduced because of do-release-upgrade. 2. The wsl-setup package as of today (0.5.4) mostly contains configuration overrides, such as disabling some systemd services that won't behave well in this environment, adding some MoTD warniings etc. Those could be subject to future regressions, but not now as we're not touching them. 3. Bootstrapping Oracular is possible, but requires advanced users to do so, because we don't ship interim releases. Users would have to build their own images and either package it with the MS Store format. The wsl-setup package exists in interim releases just because of how the archive works. 4. Using a rootfs tarball built with wsl-setup 0.5.8 to build a Windows application package in the current format is expected to behave exactly like 0.5.4, because WSL understands the packaging format and invokes the current behaviour (provision the instance via running the Windows binary). I'll add a test case in the body of the SRU bug to assert that. Thanks for your time going through this. It's very WSL-specific business indeed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2091293 Title: [SRU] Move WSL to new Microsoft WSL package format To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2091293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
