Your message dated Tue, 12 Aug 2025 19:20:51 +0200
with message-id <[email protected]>
and subject line Program no longer shipped in dpkg
has caused the Debian Bug report #991192,
regarding dpkg-fsys-usrunmess: should be restartable
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 [email protected]
immediately.)


-- 
991192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991192
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Version: 1.20.9
Severity: wishlist
File: /usr/sbin/dpkg-fsys-usrunmess
X-Debbugs-Cc: [email protected]

I tried to run dpkg-fsys-usrunmess from systemd’s emergency mode,
thinking that this would be safer, since nothing else would be
running.  This tickled a bug in systemd (see #991185) and got
dpkg-fsys-usrunmess killed in the middle of its run—specifically,
during the ‘dpkg --pending --configure’ operation.  As you can
probably imagine, this is a really bad time for the process to be
interrupted.  I have a *lot* of experience cleaning up after breakage
in unstable and it still took me five hours this time.

In another bug, I suggested a stopgap measure for the specific thing
that went wrong with dpkg-fsys-usrunmess this time, but a more
thorough fix would be to make dpkg-fsys-usrunmess restartable.  Each
phase of the operation could be made idempotent on a file-by-file
basis simply by ignoring failures due to the rename or whatever
already having happened, and in between phases it could checkpoint
itself in a file in the shadow directory.

If I get time this weekend I’ll try to come up with a patch.


-- Package-specific info:

-- System Information:
Debian Release: 11.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-amd64 (SMP w/32 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dpkg depends on:
ii  libbz2-1.0   1.0.8-4
ii  libc6        2.31-13
ii  liblzma5     5.2.5-2
ii  libselinux1  3.1-3
ii  tar          1.34+dfsg-1
ii  zlib1g       1:1.2.11.dfsg-2

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt            2.2.4
pn  debsig-verify  <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 1.22.12

The relevant program got removed from dpkg in the 1.22.12 release,
with:

  
https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=12e3bc2991ac27f73545a246bb95b84fb8d262c9

Closing, these reports.

Thanks,
Guillem

--- End Message ---

Reply via email to