Your message dated Sun, 26 May 2024 23:06:53 +0000
with message-id <e1sbmx3-002mjk...@fasolo.debian.org>
and subject line Bug#1071115: fixed in mpich 4.2.0-6
has caused the Debian Bug report #1071115,
regarding libmpich-dev: unhandled symlink to directory conversion:
/usr/lib/x86_64-linux-gnu/mpich/include ->
../../../include/x86_64-linux-gnu/mpich
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.)
--
1071115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmpich-dev
Version: 4.2.0-5.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.
This was observed on the following upgrade paths:
bookworm -> trixie
For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information
For other overwritten locations anything interesting may happen.
Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade
It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
>From the attached log (scroll to the bottom...):
3m2.4s ERROR: installs objects over existing directory symlinks:
/usr/lib/x86_64-linux-gnu/mpich/include/mpi.h (libmpich-dev:amd64) !=
/usr/include/x86_64-linux-gnu/mpich/mpi.h (?)
/usr/lib/x86_64-linux-gnu/mpich/include ->
../../../include/x86_64-linux-gnu/mpich
/usr/lib/x86_64-linux-gnu/mpich/include/mpi.mod (libmpich-dev:amd64) !=
/usr/include/x86_64-linux-gnu/mpich/mpi.mod (?)
/usr/lib/x86_64-linux-gnu/mpich/include ->
../../../include/x86_64-linux-gnu/mpich
/usr/lib/x86_64-linux-gnu/mpich/include/mpi_base.mod (libmpich-dev:amd64) !=
/usr/include/x86_64-linux-gnu/mpich/mpi_base.mod (?)
/usr/lib/x86_64-linux-gnu/mpich/include ->
../../../include/x86_64-linux-gnu/mpich
/usr/lib/x86_64-linux-gnu/mpich/include/mpi_c_interface.mod
(libmpich-dev:amd64) != /usr/include/x86_64-linux-gnu/mpich/mpi_c_interface.mod
(?)
/usr/lib/x86_64-linux-gnu/mpich/include ->
../../../include/x86_64-linux-gnu/mpich
/usr/lib/x86_64-linux-gnu/mpich/include/mpi_c_interface_cdesc.mod
(libmpich-dev:amd64) !=
/usr/include/x86_64-linux-gnu/mpich/mpi_c_interface_cdesc.mod (?)
/usr/lib/x86_64-linux-gnu/mpich/include ->
../../../include/x86_64-linux-gnu/mpich
/usr/lib/x86_64-linux-gnu/mpich/include/mpi_c_interface_glue.mod
(libmpich-dev:amd64) !=
/usr/include/x86_64-linux-gnu/mpich/mpi_c_interface_glue.mod (?)
/usr/lib/x86_64-linux-gnu/mpich/include ->
../../../include/x86_64-linux-gnu/mpich
/usr/lib/x86_64-linux-gnu/mpich/include/mpi_c_interface_nobuf.mod
(libmpich-dev:amd64) !=
/usr/include/x86_64-linux-gnu/mpich/mpi_c_interface_nobuf.mod (?)
/usr/lib/x86_64-linux-gnu/mpich/include ->
../../../include/x86_64-linux-gnu/mpich
/usr/lib/x86_64-linux-gnu/mpich/include/mpi_c_interface_types.mod
(libmpich-dev:amd64) !=
/usr/include/x86_64-linux-gnu/mpich/mpi_c_interface_types.mod (?)
/usr/lib/x86_64-linux-gnu/mpich/include ->
../../../include/x86_64-linux-gnu/mpich
/usr/lib/x86_64-linux-gnu/mpich/include/mpi_constants.mod
(libmpich-dev:amd64) != /usr/include/x86_64-linux-gnu/mpich/mpi_constants.mod
(?)
/usr/lib/x86_64-linux-gnu/mpich/include ->
../../../include/x86_64-linux-gnu/mpich
/usr/lib/x86_64-linux-gnu/mpich/include/mpi_f08.mod (libmpich-dev:amd64) !=
/usr/include/x86_64-linux-gnu/mpich/mpi_f08.mod (?)
/usr/lib/x86_64-linux-gnu/mpich/include ->
../../../include/x86_64-linux-gnu/mpich
/usr/lib/x86_64-linux-gnu/mpich/include/mpi_f08_callbacks.mod
(libmpich-dev:amd64) !=
/usr/include/x86_64-linux-gnu/mpich/mpi_f08_callbacks.mod (?)
/usr/lib/x86_64-linux-gnu/mpich/include ->
../../../include/x86_64-linux-gnu/mpich
/usr/lib/x86_64-linux-gnu/mpich/include/mpi_f08_compile_constants.mod
(libmpich-dev:amd64) !=
/usr/include/x86_64-linux-gnu/mpich/mpi_f08_compile_constants.mod (?)
/usr/lib/x86_64-linux-gnu/mpich/include ->
../../../include/x86_64-linux-gnu/mpich
/usr/lib/x86_64-linux-gnu/mpich/include/mpi_f08_link_constants.mod
(libmpich-dev:amd64) !=
/usr/include/x86_64-linux-gnu/mpich/mpi_f08_link_constants.mod (?)
/usr/lib/x86_64-linux-gnu/mpich/include ->
../../../include/x86_64-linux-gnu/mpich
/usr/lib/x86_64-linux-gnu/mpich/include/mpi_f08_types.mod
(libmpich-dev:amd64) != /usr/include/x86_64-linux-gnu/mpich/mpi_f08_types.mod
(?)
/usr/lib/x86_64-linux-gnu/mpich/include ->
../../../include/x86_64-linux-gnu/mpich
/usr/lib/x86_64-linux-gnu/mpich/include/mpi_proto.h (libmpich-dev:amd64) !=
/usr/include/x86_64-linux-gnu/mpich/mpi_proto.h (?)
/usr/lib/x86_64-linux-gnu/mpich/include ->
../../../include/x86_64-linux-gnu/mpich
/usr/lib/x86_64-linux-gnu/mpich/include/mpi_sizeofs.mod (libmpich-dev:amd64)
!= /usr/include/x86_64-linux-gnu/mpich/mpi_sizeofs.mod (?)
/usr/lib/x86_64-linux-gnu/mpich/include ->
../../../include/x86_64-linux-gnu/mpich
/usr/lib/x86_64-linux-gnu/mpich/include/mpicxx.h (libmpich-dev:amd64) !=
/usr/include/x86_64-linux-gnu/mpich/mpicxx.h (?)
/usr/lib/x86_64-linux-gnu/mpich/include ->
../../../include/x86_64-linux-gnu/mpich
/usr/lib/x86_64-linux-gnu/mpich/include/mpif.h (libmpich-dev:amd64) !=
/usr/include/x86_64-linux-gnu/mpich/mpif.h (?)
/usr/lib/x86_64-linux-gnu/mpich/include ->
../../../include/x86_64-linux-gnu/mpich
/usr/lib/x86_64-linux-gnu/mpich/include/mpio.h (libmpich-dev:amd64) !=
/usr/include/x86_64-linux-gnu/mpich/mpio.h (?)
/usr/lib/x86_64-linux-gnu/mpich/include ->
../../../include/x86_64-linux-gnu/mpich
/usr/lib/x86_64-linux-gnu/mpich/include/mpiof.h (libmpich-dev:amd64) !=
/usr/include/x86_64-linux-gnu/mpich/mpiof.h (?)
/usr/lib/x86_64-linux-gnu/mpich/include ->
../../../include/x86_64-linux-gnu/mpich
/usr/lib/x86_64-linux-gnu/mpich/include/pmpi_base.mod (libmpich-dev:amd64) !=
/usr/include/x86_64-linux-gnu/mpich/pmpi_base.mod (?)
/usr/lib/x86_64-linux-gnu/mpich/include ->
../../../include/x86_64-linux-gnu/mpich
/usr/lib/x86_64-linux-gnu/mpich/include/pmpi_f08.mod (libmpich-dev:amd64) !=
/usr/include/x86_64-linux-gnu/mpich/pmpi_f08.mod (?)
/usr/lib/x86_64-linux-gnu/mpich/include ->
../../../include/x86_64-linux-gnu/mpich
cheers,
Andreas
libmpich-dev_4.2.0-5.1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: mpich
Source-Version: 4.2.0-6
Done: Andreas Beckmann <a...@debian.org>
We believe that the bug you reported is fixed in the latest version of
mpich, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1071...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann <a...@debian.org> (supplier of updated mpich package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 27 May 2024 00:33:02 +0200
Source: mpich
Architecture: source
Version: 4.2.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
<debian-science-maintain...@lists.alioth.debian.org>
Changed-By: Andreas Beckmann <a...@debian.org>
Closes: 1047086 1071115
Changes:
mpich (4.2.0-6) unstable; urgency=medium
.
* Team upload.
* Run autogen.sh via dh_autoreconf.
* Fix building twice in a row. (Closes: #1047086)
* Fix inverted logic when enabling features.
* Fix non-verbose build.
* Declare Rules-Requires-Root: no.
* Fix symbols file for amd64.
* libmpich-dev: Only ship .so links for libraries built from this source.
* libmpich-dev.preinst: Perform cleanup on upgrades from versions missing
dir_to_symlink/symlink_to_dir for the include directory.
* libmpich-dev: Perform dir/symlink direction change for the include
directory. (Closes: #1071115)
* Reproducibility: Strip -ffile-prefix-map from macros and shipped files.
* mpich-doc: Drop unusable build system artefacts from examples.
* Update Lintian overrides.
Checksums-Sha1:
b4af4692b5cdc0801c7765fa65ade9e017b69cc7 2788 mpich_4.2.0-6.dsc
ee3f88e39d708b862d490ffedc01ea455369cc76 350336 mpich_4.2.0-6.debian.tar.xz
254b5bd89015d624ffccae46e00ec9b647422843 8681 mpich_4.2.0-6_source.buildinfo
Checksums-Sha256:
a33d6f7c7fbb407533f3ace995a0fd021a48cf718159a695bf708499605f5e37 2788
mpich_4.2.0-6.dsc
672a6981fd2f0b1d2cb6248ef0808af4bba0d9a69a77dbdf06e4dbe069555d3c 350336
mpich_4.2.0-6.debian.tar.xz
1e3b4b33b8f5c5e258088e3d1af4c9ddf5a5ed8236f71a850923d55ceb665c3a 8681
mpich_4.2.0-6_source.buildinfo
Files:
4246e60f833fa603eae2c8cb4b8ff2d8 2788 devel optional mpich_4.2.0-6.dsc
7798ec90f328bb97888cf55e9adca6ab 350336 devel optional
mpich_4.2.0-6.debian.tar.xz
de9ba218229fc4e9722cfcf759d59106 8681 devel optional
mpich_4.2.0-6_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmZTu1gQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCPHQD/wOoamKbdHAONMxQkrRLzVOgFhR5WdoFWiE
eNCnpEeVgMtnXhXzm1sZQjLmvMUJQtrE/j7dsRgCCwrHj4s5VwasnlAootMhysD8
PPxuBZjA1mipX2zgok75IU0BjvG7szd+rY+/jQ4e0f57vbWs6mfnIfdzWjESCMAi
bV3U6kjMjz2+euLR/KhzUe38ako+WPko6pcYN0OfIu0TXoetqbswUCMjgCokYFkb
4tVTQJJa0ZmugcISXXktc1QTKSdGZXSQFd+I152MF9RSmxgTidGQ2Wi2F4mJJymp
6FLJS+BTgOLWp3lV5NpibpyC2biZ5UBXqXnEU0gylRBRTUi7gYiaVae6SqlGZUyh
NALIxAFfcF5kS/30gwLYwpmoqFdA8ZiAb7ae1Wty2Cj0HZTw/r+AlWLw+DerneyI
s+sQLrQZyywus5Fe3p9kGdwgfxIRw/0oFkUvgbz58AyVx+RmNkfeOsuIdOaK7m9B
RIOuK8LfwBSUBVRSfzhZR0BDwZKHGRCGuay0gr1TkBvK/3gd61glYC1KKPGvjrwv
7WyVPc1rsz+jzKizIR6vnc+Tr+/B8uID6GMinVTRDUMS3v/3kdRl+eEw8xJgp3Yu
mhKSng6c/Juk00JXWcnkWc6NQoRUFOYYtoCSnsE6DQZREX4IDrqm+VFJNcp22mYv
c4Md88djQQ==
=VqCk
-----END PGP SIGNATURE-----
pgp7vJL0DIo7t.pgp
Description: PGP signature
--- End Message ---
