Your message dated Wed, 14 Sep 2022 15:37:03 +0200
with message-id <cc8670e238a0e5118af4e4b0553096bcddfe3fb5.ca...@sviech.de>
and subject line Re: libopenmpi-dev: Cannot uninstall rmdir: failed to remove
'/usr/lib/x86_64-linux-gnu/fortran/gfortran': No such file or directory
has caused the Debian Bug report #1019721,
regarding libopenmpi-dev: Cannot uninstall rmdir: failed to remove
'/usr/lib/x86_64-linux-gnu/fortran/gfortran': No such file or directory
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.)
--
1019721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libopenmpi-dev
Version: 4.1.4-2
Severity: serious
Hello,
it seems to be impossible to uninstall libopenmpi-dev:
(sid)root@argenau:/# dpkg --purge libopenmpi-dev
(Reading database ... 25167 files and directories currently installed.)
Removing libopenmpi-dev:amd64 (4.1.4-2) ...
rmdir: failed to remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran': No such
file or directory
dpkg: error processing package libopenmpi-dev:amd64 (--purge):
[...]
Looking at the postrm script we find:
(sid)root@argenau:/# grep ^rmdir
/var/lib/dpkg/info/libopenmpi-dev\:amd64.postrm
rmdir --ignore-fail-on-non-empty /usr/lib/$multiarch/fortran/gfortran
rmdir --ignore-fail-on-non-empty /usr/lib/$multiarch/fortran/gfortran
rmdir --ignore-fail-on-non-empty /usr/lib/$multiarch/fortran/gfortran
rmdir --ignore-fail-on-non-empty /usr/lib/$multiarch/fortran/gfortran
rmdir --ignore-fail-on-non-empty /usr/lib/$multiarch/fortran/gfortran
i.e. rmdir is run unconditiionally multiple times on the same directory,
the first instance succeeds, the second one fails.
This is #1019050 in dh-fortran-mod which is now fixed. However
libopenmpi-dev 4.1.4-2 contains the broken code generated by
dh-fortran-mod and needs a rebuild against dh-fortran-mod (0.27) and
should not propagate to testing.
Is there a way to find all packages built against broken dh-fortran-mod
so all affected packages can be rebuilt?
cu Andreas
--- End Message ---
--- Begin Message ---
Thanks to the release team, a binNMU has been scheduled.
--- End Message ---
