close 917133
thanks
On 23/12/2018 05:17, Christoph Anton Mitterer wrote:
Source: openmpi
Version: 3.1.3-6
Severity: critical
Justification: causes serious data loss
Thanks for your work, but this bug report is wrong.
Hi.
On upgrading from 3.1.3-5 I get these:
Unpacking libopenmpi3:amd64 (3.1.3-6) over (3.1.3-5) ...
rm: cannot remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran-8#': No such file
or directory
rm: cannot remove 'End': No such file or directory
rm: cannot remove 'automatically': No such file or directory
rm: cannot remove 'added': No such file or directory
rm: cannot remove 'section': No such file or directory
dpkg: warning: old libopenmpi3:amd64 package post-removal script subprocess
returned error exit status 1
dpkg: trying script from the new package instead ...
dpkg: ... it looks like that went OK
The bug here is #916565 (in 3.1.3-5), fixed in 3.1.3-6
Apparently this comes from:
if test ! -d /usr/lib/$multiarch/fortran/$base ; then
rm -f /usr/lib/$multiarch/fortran/$cmplr
fi
# End automatically added section
This code is correct , and from -6. The buggy code was in -5, where the
lack of a trailing newline led to a comment being added to the end of
the "rm" statement.
in the respective package's postrm, though I can't see any error in it.
The bug led to postrm failing in 3.1.3-5. A fix in -6 still calls the
buggy postrm script to remove the -5 package if installed, which fails,
and then calls 'failed-upgrade' in postrm on 3.1.3-6 (See
https://wiki.debian.org/MaintainerScripts).
This succeeds and hence the "... it looks like that went OK".
Marking this as critical and serious data loss,... as it seems to remove "End",
"automatically" in some relative path(?)... (or does dpkg always cd to some
fixed location?)... so there is at least a remote chance this could remove
user files of these names.
This bug is now removed from Debian. The upgrade output is ugly, but
upgrade works. Only those who upgraded to -5 will see it.
I'm not sure what the default directory that dpkg/apt runs from when
executing the upgrades (the users current directory? ). It may hit some
users who have a file named "automatically","added","section" or "End" ,
in their current directory while upgrading openmpi in sid this week, but
i'm not sure what to do about it.
regards
Alastair
Cheers,
Chris
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
Alastair McKinstry, <alast...@sceal.ie>, <mckins...@debian.org>,
https://diaspora.sceal.ie/u/amckinstry
Commander Vimes didn’t like the phrase “The innocent have nothing to fear,”
believing the innocent had everything to fear, mostly from the guilty but in
the longer term
even more from those who say things like “The innocent have nothing to fear.”
- T. Pratchett, Snuff
