Your message dated Fri, 26 May 2023 14:13:36 +0000 with message-id <e1q2ycg-007c6q...@fasolo.debian.org> and subject line Bug#1035631: fixed in curlpp 0.8.1-5.1 has caused the Debian Bug report #1035631, regarding libcurlpp-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE 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.) -- 1035631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: libcurlpp-dev Version: 0.8.1-5 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: bulseye -> bookworm 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...): 0m41.4s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/libcurlpp-dev/Readme.md (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/Readme.md (libcurlpp0:amd64) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/changelog.Debian.gz (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/changelog.Debian.gz (libcurlpp0:amd64) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/copyright (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/copyright (libcurlpp0:amd64) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/CMakeLists.txt (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/CMakeLists.txt (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/README (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/README (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example00.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example00.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example01.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example01.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example02.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example02.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example03.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example03.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example04.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example04.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example05.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example05.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example06.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example06.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example07.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example07.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example08.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example08.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example09.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example09.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example10.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example10.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example11.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example11.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example12.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example12.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example13.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example13.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example14.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example14.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example15.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example15.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example16.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example16.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example17.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example17.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example18.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example18.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example19.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example19.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example20.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example20.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example21.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example21.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example22.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example22.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example23.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example23.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 /usr/share/doc/libcurlpp-dev/examples/example24.cpp (libcurlpp-dev:amd64) != /usr/share/doc/libcurlpp0/examples/example24.cpp (?) /usr/share/doc/libcurlpp-dev -> libcurlpp0 cheers, Andreas
libcurlpp-dev_0.8.1-5.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---Source: curlpp Source-Version: 0.8.1-5.1 Done: Andreas Beckmann <a...@debian.org> We believe that the bug you reported is fixed in the latest version of curlpp, 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 1035...@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 curlpp 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: Thu, 25 May 2023 15:39:56 +0200 Source: curlpp Architecture: source Version: 0.8.1-5.1 Distribution: unstable Urgency: medium Maintainer: Aloïs Micard <creekor...@debian.org> Changed-By: Andreas Beckmann <a...@debian.org> Closes: 1035631 Changes: curlpp (0.8.1-5.1) unstable; urgency=medium . * Non-maintainer upload. * libcurlpp-dev: Perform symlink to directory conversion of /usr/share/doc/libcurlpp-dev. (Closes: #1035631) Checksums-Sha1: e56fe18e6fae1f580a6a855c627febe582d9cff5 2061 curlpp_0.8.1-5.1.dsc ccd7aea4081db4319c9673c329f12ad4d6de81e4 4416 curlpp_0.8.1-5.1.debian.tar.xz 9f52c447bd864c9d887ce00fd7c2dd0e09c3dc99 6332 curlpp_0.8.1-5.1_source.buildinfo Checksums-Sha256: 64936000b248f3ef71da7dba105e88b4b1e1d50a1ba14821cd337b8031f8c27e 2061 curlpp_0.8.1-5.1.dsc a768e7d4d83dc899a685d7d6cf019ddc2ea625e6f7f314a08d523f9677c79687 4416 curlpp_0.8.1-5.1.debian.tar.xz f3023f80227d59aa8629bd6f7ce3c1c27c1710fe6e9303a227bb1add72a9a744 6332 curlpp_0.8.1-5.1_source.buildinfo Files: 4fbca56504a522629a82f5945026d2bb 2061 libs optional curlpp_0.8.1-5.1.dsc 89e199fbe428487e4546ca8727e6750c 4416 libs optional curlpp_0.8.1-5.1.debian.tar.xz 233224e29d2a89f0bea766aabe097754 6332 libs optional curlpp_0.8.1-5.1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmRvZnsQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCCwSD/9dahtRjqNsMN2LM3juElQoDFfl5fx9R7P8 IF1duV3Fmzas2+otdRYt8pzvbMC4K54GCdtcTZnd8tAcSymYCxPLfQ5v/LsXhL8V 6Y5Hdn2BWpIIRXhGKvI1GhsKE2rNTLJCGd1wOJIHMIkDhpVIv3DttLxlNYvTs3Tc 28DnDNYHFcbe2F5DKWQ3VhNTJgGQGr6zJ9gM1Kge/cjKuhM4zEhCi2tcz7VZRL44 4+3DI1A+KN1yJrgNTN6B0FQnClL3OCvPtszaBNlgL4Gh6qkjPpN8A1Er3MxBGl4l qxR8QrkRvtJn/8UW4ly+hzYMXtLTX/z7jeZoESc8GuNPQzolGSZBztao/chryEcG N8RMIiBMtmSG5EJUBBLGI7Y/Ev/H1Tmr+g+DLpwnqJxpNU3YOfYJPlKUJQCiow8I t7R+ZCYOt43htcM/MrQbrziBp4spg+f0Md+5x912LxMKD9YLP3ctEuaPBnFOn6Er vHnLX8NfcEusUxfe82TNFrBftLdaMtSf9ii/32YjDtWLB+MmE4WclZU7pHtTTZ6I xzHHqr/NnrxB90P4iiZeO0ViKwu9KIkdorP3anLSv2BF7CxINU+OIje7l4GEY5cG +fIodQjZCM5cPZe6z7aWsRgPl2jtHpdA7ojn2e9BB8R7QOakKHdN1JI5HC+SOytN PUuhgn34cA== =mjRx -----END PGP SIGNATURE-----
--- End Message ---
