Package: xfsdump_3.1.9
Version: xfsdump_3.1.9_amd64.deb
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
upgrading from xfsdump_3.1.6+nmu2+b2
# apt install xfsdump
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
attr quota
The following packages will be upgraded:
xfsdump
1 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
Need to get 0 B/254 kB of archives.
After this operation, 19.5 kB of additional disk space will be used.
Reading changelogs... Done
(Reading database ... 500509 files and directories currently installed.)
Preparing to unpack .../xfsdump_3.1.9_amd64.deb ...
Unpacking xfsdump (3.1.9) over (3.1.6+nmu2+b2) ...
dpkg: error processing archive /var/cache/apt/archives/xfsdump_3.1.9_amd64.deb
(--unpack):
unable to install new version of '/usr/sbin/xfsdump': No such file or directory
Errors were encountered while processing:
/var/cache/apt/archives/xfsdump_3.1.9_amd64.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
I have a system with usrmerge installed where /sbin is a symlink to
/usr/sbin.
xfsdump_3.1.9 contains symlinks from /usr/sbin/xfsdump to /sbin/xfsdump
This is a regression from xfsdump_3.1.6+nmu2+b2 where those symlinks are not
present and a postinst/postrm script exist to check for combined /sbin,
/usr/sbin
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8),
LANGUAGE=sv:en_GB (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
