Your message dated Fri, 30 Sep 2022 16:15:42 +0100
with message-id <1016eb1a2c286573e6cb97c3fe77fb3571e43d30.ca...@debian.org>
and subject line Re: Bug#1020971: usrmerge: Fails to install on Windows
Subsystem for Linux (WSL) 1.0
has caused the Debian Bug report #1020971,
regarding usrmerge: Fails to install on Windows Subsystem for Linux (WSL) 1.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1020971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020971
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: usrmerge
Version: 31
Severity: normal
X-Debbugs-Cc: none
Dear Maintainer,
When installing usrmerge on Debian Bookworm under the Windows Subsystem
for Linux (WSL) 1.0, installation fails at the setup stage.
**This bug effectively breaks the entire install of Debian Bookworm on
WSL 1.0**, because usrmerge is now a required dependency of the
essential/system-critical package init-system-helpers, as of version
1.65~exp1 through the current version (1.65.2) of that package.
I suspect the cause of this issue is related to the fact that WSL 1.0
uses a Microsoft-provided kernel for all Linux distributions that run on
WSL 1.0. WSL 2.0 allows the use of the actual distribution's kernel,
because it uses the Hyper-V hypervisor on the host Windows operating
system. However, WSL 2.0 is not an option for me (and I assume many
others), who use other virtualization products on Windows, or use a
cloud-hosted virtual Windows desktop, such as AWS Workspaces or C
itrix.
--
Setting up usrmerge (31) ...
mv: cannot move '/lib/x86_64-linux-gnu/security' to
'/usr/lib/x86_64-linux-gnu/security': Permission denied
FATAL ERROR:
mv --no-clobber /lib/x86_64-linux-gnu/security
/usr/lib/x86_64-linux-gnu/security: rc=1
You can try correcting the errors reported and running again
/usr/lib/usrmerge/convert-usrmerge until it will complete without errors.
Do not install or update other Debian packages until the program
has been run successfully.
E: usrmerge failed.
dpkg: error processing package usrmerge (--configure):
installed usrmerge package post-installation script subprocess
returned error exit status 1
Errors were encountered while processing:
usrmerge
E: Sub-process /usr/bin/dpkg returned an error code (1)
--
Attempting to run sudo mv --no-clobber /lib/x86_64-linux-gnu/security
/usr/lib/x86_64-linux-gnu/security manually results in the same
permission denied error.
-- System Information:
Debian Release: bookw
orm/sid
APT prefers testing
APT policy: (500, 'testing')
merged-usr: no
Architecture: amd64 (x86_64)
Kernel: Linux 4.4.0-22000-Microsoft
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE
not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
Versions of packages usrmerge depends on:
ii libfile-find-rule-perl 0.34-2
ii perl 5.34.0-5
usrmerge recommends no packages.
usrmerge suggests no packages.
-- no debconf information
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Control: forwarded -1 https://github.com/microsoft/WSL/issues/8927
On Thu, 29 Sep 2022 21:44:29 +0000 Sean Whalen <sea...@pm.me> wrote:
> I just created a bug report in the official Microsoft WSL project on
> GitHub to track the issue there as well, and maybe get some eyeballs
> from Microsoft.
>
> https://github.com/microsoft/WSL/issues/8927
I've talked with both the internal team and the Debian maintainer of
the WSL image. This is a WSL 1.0 specific issue, and there's not much
we can do in usrmerge about it, as it's related to the underlying
filesystem that we can't touch anyway.
The Debian stable WSL image in the store will be updated shortly to be
merged-usr out of the box, so this won't happen again for new
installations, and on upgrade to bookworm it will be a no-op. Older
installations on WSL 1.0 will have to remove and reinstall, unless a
workaround is found, but for that please use the upstream bug tracker
as here we really can't figure out what the problem is.
Also please note that it would be a good idea to just move to WSL 2.0
for all use cases at this point.
Hence, setting the forwarded address and closing.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
--- End Message ---
