$ ./change-override -c main -S wsl-setup
Override component to main
wsl-setup 0.1.1 in jammy: universe/admin -> main
wsl-setup 0.1.1 in jammy amd64: universe/admin/optional/100% -> main
wsl-setup 0.1.1 in jammy arm64: universe/admin/optional/100% -> main
wsl-setup 0.1.1 in jammy armhf: universe/admin/optional/100% -> main
wsl-setup 0.1.1 in jammy i386: universe/admin/optional/100% -> main
wsl-setup 0.1.1 in jammy ppc64el: universe/admin/optional/100% -> main
wsl-setup 0.1.1 in jammy riscv64: universe/admin/optional/100% -> main
wsl-setup 0.1.1 in jammy s390x: universe/admin/optional/100% -> main
Override [y|N]? y
8 publications overridden.
** Changed in: wsl-setup (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wsl-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1948392
Title:
[MIR] wsl-setup
Status in wsl-setup package in Ubuntu:
Fix Released
Bug description:
[Availability]
Built for all supported architectures. starting from jammy. It is a
simple arch-independent package.
[Rationale]
On WSL, we have an out of the box experience UI. This one is based on
ubuntu-desktop-installer (which includes subiquity) on a classic snap.
However, WSL doesn’t have systemd/apparmor (and so snap) support. For 22.04
LTS, we plan thus on mimicking a snap environment before executing the binaries
in the snap itself. There is no confinement planned here, just shipping all
dependencies that way before being able to switch to a more classic snap
behavior in future WSL releases.
This script is thus preparing this, mounting all needed snaps
(core/theme/installer) before exporting needed environment variables
for the snap and chaining to the binary within the snap. There is no
specific changes for this in the snap.
This package will be seeded on WSL.
[Security]
No known security issues
There is no CVE, as being a new package, as of today. The script, even
if ran as root on first setup, is using set -eu, and does basic things
like mounting, bind mount, directory creation and export environment
variables.
[Quality assurance]
There is no tests for this script, but we plan as part of our 22.04 LTS
roadmap to have automated installation tests as part of our CI and daily builds.
This will thus provision the machine, execute the Windows launcher executable
which will chain into that script, which will itself chain to the snap,
proceeding the OOBE experience. Consequently, failures will be quickly detected.
There is no bugs opened as of today, as it’s a new package, and it’s
only used by devs localy until we can seed it.
On the packaging itself, this one is really trivial, and only ship one
script. No postinst, no debconf questions.
Note about the false lintian positive W: wsl-setup source: unknown-field
wsl-setup_0.1.dsc Description, which is supported to fill the binary packages
description with it.
[UI standards]
No UI as part of this script itself.
[Dependencies]
No dependency. Note that we don’t install the needed snaps on purpose
in postinst. The snaps will be directly seeded. This is to prevent
installation failure on system without snap support.
[Standards compliance]
Use current Standards-Version and dh 13
[Maintenance]
The desktop team, as being responsible for WSL will maintain this
package.
[Background information]
This script is called by the Windows launcher directly and should not be
called directly by the user. This is why it ends up in libexec.
The plan is to phase out this script once we get snap support on WSL
(but this is dependent on Microsoft’s roadmap).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wsl-setup/+bug/1948392/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
