Processed: Re: Bug#1008764: dpkg: [dpkg-fsys-usrunmess] fails to copy /lib/modules directories, breaks

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1008764 [dpkg] dpkg: [dpkg-fsys-usrunmess] fails to copy /lib/modules 
directories, breaks
Severity set to 'normal' from 'critical'

-- 
1008764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1008764: dpkg: [dpkg-fsys-usrunmess] fails to copy /lib/modules directories, breaks

[Guillem Jover]

Control: severity -1 normal

Hi!

On Fri, 2022-04-01 at 07:27:26 +0900, Norbert Preining wrote:
> Package: dpkg
> Version: 1.21.6
> Severity: critical
> Justification: breaks the whole system

The script does not break the whole system, it fails quite early
during preparations before doing any migration.

> my system was installed *after* buster and now is in the unfortunate
> messed up state.
> 
> I tried to fix it as suggested by dpkg using dpkg-fsys-usrunmess, but
> it fails reproducibly:
> $ dpkg-fsys-usrunmess
> ...
> D: creating shadow file = /.usrunmess/lib/modprobe.d/aliases.conf
> D: creating shadow file = /.usrunmess/lib/modprobe.d/fbdev-blacklist.conf
> D: creating shadow file = /.usrunmess/lib/modprobe.d/systemd.conf
> D: creating shadow dir = 
> /.usrunmess/lib/modules/5.15.15+futex+zstd+intel+wine+
> error: cannot mkdir /.usrunmess/lib/modules/5.15.15+futex+zstd+intel+wine+: 
> No such file or directory
> $
> 
> I have my own compiled kernels.
> 
> The problem is that it seems to be a missing mkdir -p  or similar.

Sorry, it looks like I previously only fixed the cases of mixed tracked
and untracked kernel module files there. I've now fixed this locally,
which will be included in 1.21.7.

You'll need to remove the shadow hierarchy before being able to run
this again with a fixed script though.

Thanks,
Guillem

Bug#1008764: dpkg: [dpkg-fsys-usrunmess] fails to copy /lib/modules directories, breaks

[Norbert Preining]

Package: dpkg
Version: 1.21.6
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: norb...@preining.info

Hi

my system was installed *after* buster and now is in the unfortunate
messed up state.

I tried to fix it as suggested by dpkg using dpkg-fsys-usrunmess, but
it fails reproducibly:
$ dpkg-fsys-usrunmess
...
D: creating shadow file = /.usrunmess/lib/modprobe.d/aliases.conf
D: creating shadow file = /.usrunmess/lib/modprobe.d/fbdev-blacklist.conf
D: creating shadow file = /.usrunmess/lib/modprobe.d/systemd.conf
D: creating shadow dir = /.usrunmess/lib/modules/5.15.15+futex+zstd+intel+wine+
error: cannot mkdir /.usrunmess/lib/modules/5.15.15+futex+zstd+intel+wine+: No 
such file or directory
$

I have my own compiled kernels.

The problem is that it seems to be a missing mkdir -p  or similar.

Wth that, I cannot convert the system.

Best

Norbert



-- Package-specific info:
This system uses merged-usr-via-aliased-dirs, going behind dpkg's
back, breaking its core assumptions. This can cause silent file
overwrites and disappearances, and its general tools misbehavior.
See .

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.16.17+futex+wine+ (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dpkg depends on:
ii  libbz2-1.0   1.0.8-5
ii  libc62.33-7
ii  liblzma5 5.2.5-2
ii  libselinux1  3.3-1+b2
ii  tar  1.34+dfsg-1
ii  zlib1g   1:1.2.11.dfsg-4

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt2.4.3
pn  debsig-verify  

-- no debconf information