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
