Your message dated Sun, 14 May 2023 10:50:14 +0000 with message-id <e1py9is-0030wa...@fasolo.debian.org> and subject line Bug#1035629: fixed in nlopt 2.7.1-5 has caused the Debian Bug report #1035629, regarding libnlopt-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.) -- 1035629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035629 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: libnlopt-dev Version: 2.7.1-4 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: bullseye -> 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...): 0m39.3s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/libnlopt-dev/changelog.Debian.amd64.gz (libnlopt-dev:amd64) != /usr/share/doc/libnlopt0/changelog.Debian.amd64.gz (libnlopt0:amd64) /usr/share/doc/libnlopt-dev -> libnlopt0 /usr/share/doc/libnlopt-dev/changelog.Debian.gz (libnlopt-dev:amd64) != /usr/share/doc/libnlopt0/changelog.Debian.gz (libnlopt0:amd64) /usr/share/doc/libnlopt-dev -> libnlopt0 /usr/share/doc/libnlopt-dev/changelog.gz (libnlopt-dev:amd64) != /usr/share/doc/libnlopt0/changelog.gz (libnlopt0:amd64) /usr/share/doc/libnlopt-dev -> libnlopt0 /usr/share/doc/libnlopt-dev/copyright (libnlopt-dev:amd64) != /usr/share/doc/libnlopt0/copyright (libnlopt0:amd64) /usr/share/doc/libnlopt-dev -> libnlopt0 /usr/share/doc/libnlopt-dev/examples (libnlopt-dev:amd64) != /usr/share/doc/libnlopt0/examples (?) /usr/share/doc/libnlopt-dev -> libnlopt0 /usr/share/doc/libnlopt-dev/examples/CMakeLists.txt (libnlopt-dev:amd64) != /usr/share/doc/libnlopt0/examples/CMakeLists.txt (?) /usr/share/doc/libnlopt-dev -> libnlopt0 /usr/share/doc/libnlopt-dev/examples/box.c (libnlopt-dev:amd64) != /usr/share/doc/libnlopt0/examples/box.c (?) /usr/share/doc/libnlopt-dev -> libnlopt0 /usr/share/doc/libnlopt-dev/examples/lorentzfit.c (libnlopt-dev:amd64) != /usr/share/doc/libnlopt0/examples/lorentzfit.c (?) /usr/share/doc/libnlopt-dev -> libnlopt0 /usr/share/doc/libnlopt-dev/examples/myconstraint.m (libnlopt-dev:amd64) != /usr/share/doc/libnlopt0/examples/myconstraint.m (?) /usr/share/doc/libnlopt-dev -> libnlopt0 /usr/share/doc/libnlopt-dev/examples/myfunc.m (libnlopt-dev:amd64) != /usr/share/doc/libnlopt0/examples/myfunc.m (?) /usr/share/doc/libnlopt-dev -> libnlopt0 /usr/share/doc/libnlopt-dev/examples/t_fortran.f90 (libnlopt-dev:amd64) != /usr/share/doc/libnlopt0/examples/t_fortran.f90 (?) /usr/share/doc/libnlopt-dev -> libnlopt0 /usr/share/doc/libnlopt-dev/examples/t_guile.scm (libnlopt-dev:amd64) != /usr/share/doc/libnlopt0/examples/t_guile.scm (?) /usr/share/doc/libnlopt-dev -> libnlopt0 /usr/share/doc/libnlopt-dev/examples/t_matlab.m (libnlopt-dev:amd64) != /usr/share/doc/libnlopt0/examples/t_matlab.m (?) /usr/share/doc/libnlopt-dev -> libnlopt0 /usr/share/doc/libnlopt-dev/examples/t_octave.m (libnlopt-dev:amd64) != /usr/share/doc/libnlopt0/examples/t_octave.m (?) /usr/share/doc/libnlopt-dev -> libnlopt0 /usr/share/doc/libnlopt-dev/examples/t_python.py (libnlopt-dev:amd64) != /usr/share/doc/libnlopt0/examples/t_python.py (?) /usr/share/doc/libnlopt-dev -> libnlopt0 /usr/share/doc/libnlopt-dev/examples/t_tutorial.cxx (libnlopt-dev:amd64) != /usr/share/doc/libnlopt0/examples/t_tutorial.cxx (?) /usr/share/doc/libnlopt-dev -> libnlopt0 /usr/share/doc/libnlopt-dev/examples/testfuncs.c (libnlopt-dev:amd64) != /usr/share/doc/libnlopt0/examples/testfuncs.c (?) /usr/share/doc/libnlopt-dev -> libnlopt0 /usr/share/doc/libnlopt-dev/examples/testfuncs.h (libnlopt-dev:amd64) != /usr/share/doc/libnlopt0/examples/testfuncs.h (?) /usr/share/doc/libnlopt-dev -> libnlopt0 /usr/share/doc/libnlopt-dev/examples/testopt.c (libnlopt-dev:amd64) != /usr/share/doc/libnlopt0/examples/testopt.c (?) /usr/share/doc/libnlopt-dev -> libnlopt0 cheers, Andreas
libnlopt-dev_2.7.1-4+b4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---Source: nlopt Source-Version: 2.7.1-5 Done: Nilesh Patra <nil...@debian.org> We believe that the bug you reported is fixed in the latest version of nlopt, 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. Nilesh Patra <nil...@debian.org> (supplier of updated nlopt 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: Sun, 14 May 2023 09:35:20 +0000 Source: nlopt Architecture: source Version: 2.7.1-5 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers <debian-science-maintain...@lists.alioth.debian.org> Changed-By: Nilesh Patra <nil...@debian.org> Closes: 1035629 Changes: nlopt (2.7.1-5) unstable; urgency=medium . * Team Upload. * Add maintscript to convert libnlopt-dev doc symlink to directory (Closes: #1035629) * Add a preinst to remove examples directory in libnlopt0 which should be present in -dev only Checksums-Sha1: 3d385c56ee91c19c6b2c64d33550d05b4355c779 2026 nlopt_2.7.1-5.dsc 04364e745bb28aa93fc3f7dee4082194278bf245 14728 nlopt_2.7.1-5.debian.tar.xz 3a531b0dc4b2c1770c29f332f8d7b9731ee314b9 27387 nlopt_2.7.1-5_amd64.buildinfo Checksums-Sha256: 797ef248277fb1ec71fed5f527e9052192867fca8b50c7089a12625a5ccf2038 2026 nlopt_2.7.1-5.dsc e2130402d3f8c9440c17f793166dcfb3bbc0785141f659b4303f8fe60b2a0153 14728 nlopt_2.7.1-5.debian.tar.xz 3e76e2a59ded87c11a3820e2d5d12a8530db0d55d118b5329a19cddb809eade1 27387 nlopt_2.7.1-5_amd64.buildinfo Files: 7e729ef5ddd06587c8499383bf7efd05 2026 math optional nlopt_2.7.1-5.dsc 2af6ed20170da8db3fbff629313c8b60 14728 math optional nlopt_2.7.1-5.debian.tar.xz 1937ee12eeacbf50b634a70a39717b67 27387 math optional nlopt_2.7.1-5_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCZGC54AAKCRAqJ5BL1yQ+ 2n9hAP4nLwGCO76ZqWOs6rhCtR/x+ebjPGG64GbSY6nFC2+8egEAhXYngXtARmmZ wgSbxXFZjfvOzKXQLX3zbhG6loZgFws= =LbqA -----END PGP SIGNATURE-----
--- End Message ---
