Your message dated Sat, 29 Feb 2020 20:41:41 +0000 with message-id <e1j88vd-0005em...@fasolo.debian.org> and subject line Bug#945498: fixed in whatweb 0.5.1-1 has caused the Debian Bug report #945498, regarding whatweb: unhandled symlink to directory conversion: /usr/share/whatweb/my-plugins 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.) -- 945498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: whatweb Version: 0.5.0-1 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: buster->sid buster->bullseye 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...): 0m36.7s ERROR: installs objects over existing directory symlinks: /usr/share/whatweb/my-plugins/plugin-tutorial-1.rb (whatweb) != /var/lib/whatweb/my-plugins/plugin-tutorial-1.rb (?) /usr/share/whatweb/my-plugins -> /var/lib/whatweb/my-plugins /usr/share/whatweb/my-plugins/plugin-tutorial-2.rb (whatweb) != /var/lib/whatweb/my-plugins/plugin-tutorial-2.rb (?) /usr/share/whatweb/my-plugins -> /var/lib/whatweb/my-plugins /usr/share/whatweb/my-plugins/plugin-tutorial-3.rb (whatweb) != /var/lib/whatweb/my-plugins/plugin-tutorial-3.rb (?) /usr/share/whatweb/my-plugins -> /var/lib/whatweb/my-plugins /usr/share/whatweb/my-plugins/plugin-tutorial-4.rb (whatweb) != /var/lib/whatweb/my-plugins/plugin-tutorial-4.rb (?) /usr/share/whatweb/my-plugins -> /var/lib/whatweb/my-plugins /usr/share/whatweb/my-plugins/plugin-tutorial-5.rb (whatweb) != /var/lib/whatweb/my-plugins/plugin-tutorial-5.rb (?) /usr/share/whatweb/my-plugins -> /var/lib/whatweb/my-plugins /usr/share/whatweb/my-plugins/plugin-tutorial-6.rb (whatweb) != /var/lib/whatweb/my-plugins/plugin-tutorial-6.rb (?) /usr/share/whatweb/my-plugins -> /var/lib/whatweb/my-plugins /usr/share/whatweb/my-plugins/plugin-tutorial-7.rb (whatweb) != /var/lib/whatweb/my-plugins/plugin-tutorial-7.rb (?) /usr/share/whatweb/my-plugins -> /var/lib/whatweb/my-plugins cheers, Andreas
whatweb_0.5.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---Source: whatweb Source-Version: 0.5.1-1 Done: Laszlo Boszormenyi (GCS) <g...@debian.org> We believe that the bug you reported is fixed in the latest version of whatweb, 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 945...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) <g...@debian.org> (supplier of updated whatweb 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: SHA512 Format: 1.8 Date: Sat, 29 Feb 2020 18:43:34 +0000 Source: whatweb Architecture: source Version: 0.5.1-1 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) <g...@debian.org> Changed-By: Laszlo Boszormenyi (GCS) <g...@debian.org> Closes: 945498 Changes: whatweb (0.5.1-1) unstable; urgency=medium . * New upstream release. * Update patches. * Handle symlink to directory switch (closes: #945498). * Update debhelper level to 12 . * Update Standards-Version to 4.5.0 . Checksums-Sha1: 9bf7043b4d5b238ce95b7ce4428c47e8c1c03adc 1765 whatweb_0.5.1-1.dsc 36a4c5a457597c7f1e4232084b4189a841ad537b 3633302 whatweb_0.5.1.orig.tar.gz 243db16ff41a87498115e0177b99d1c6129e5464 3492 whatweb_0.5.1-1.debian.tar.xz Checksums-Sha256: 3eedc376fa1df2715ea5fdb5f7db1cce2e59c47aa255ef75c19012c5a6e3d3d7 1765 whatweb_0.5.1-1.dsc 0d95c6a0a11ab19f8683e7f22702b9440ebdcdad3598201a34aeb1a2a2e07a82 3633302 whatweb_0.5.1.orig.tar.gz fd8485705e79f92e1b2b770a149bcf56e7443f782eed10e1e0b50f7a88dab83b 3492 whatweb_0.5.1-1.debian.tar.xz Files: 4b10c7cd0a8620b8abc6d3106a8f551f 1765 web optional whatweb_0.5.1-1.dsc a437d13dbfe9caccc1b4c39a57350c05 3633302 web optional whatweb_0.5.1.orig.tar.gz e606e661f4802777e9cc5a33da0cf668 3492 web optional whatweb_0.5.1-1.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAl5ayQgACgkQ3OMQ54ZM yL/5jw//TdwRP834ZTnAlR5wqK+EbT3/95tDY4uVJ9O5ZEGnaauFLRqj9jo5Nn+u nmlajnb+M00rmXJETYcGT53RV26i4r9KNPt7ZNg32b/JyRSy1ilYiYMIIWxus4Fr g+EihqV6BazLOXwV/d/RLIOV8B0gdkCfmhJDekdFHhA5HoiBwmUwGya2XhsUtkLC VzSxmpfDxngtuERAGZYsyXWjSInwNxApyIETWjKmI22OVy1zTJL2l3Fy4QKZzfRU vC/+OGjoE/J24upke+lx0cYCUFHIrVeTXg9Hzu+wV6A7x0T9SsGoo8cdj8yqAyZY ZgUk/sLqYPTuICfAFQPv/AiFienpd6kpiZbfknJOxhnr3Vxm7Y0J4GOK5HyR2N6n GYUxJxB14O455DNWz1eZ4fil6FMk+o9lpDL0E6Ww6FLHhKNX6npYP1acHDwKK/+W 97ZAaW2bB06kHSHx/6V2sdZIzwXjhh+Ag4mAWqmffh8hmO0B0PF+vaq3qf03b5av nF3qDgSO1yCNZUhJCHwNxs+aEMiGqv6jlgPgLW6/rwx85z0e7bp8oanih61/eCB4 8msE5r/fOr51KrfLNo4QaeqcFlBqazOZfHReBdbwX77bWTuei/3vWjzwW6QxWRd+ Mcqi4m3Q/jcjBvvsbIqNseLJoZSy+lVUe8IHAIOpCzFeoHe68sw= =88FB -----END PGP SIGNATURE-----
--- End Message ---