Your message dated Sun, 09 Jun 2024 00:05:53 +0000
with message-id <e1sg64h-0092vf...@fasolo.debian.org>
and subject line Bug#1071114: fixed in plover 4.0.0~rc2-0.3
has caused the Debian Bug report #1071114,
regarding plover: unhandled symlink to directory conversion:
/usr/lib/python3/dist-packages/plover/assets -> ../../../../share/plover/assets
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.)
--
1071114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: plover
Version: 4.0.0~rc2-0.2
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...):
3m55.0s ERROR: installs objects over existing directory symlinks:
/usr/lib/python3/dist-packages/plover/assets/american_english_words.txt
(plover) != /usr/share/plover/assets/american_english_words.txt (?)
/usr/lib/python3/dist-packages/plover/assets ->
../../../../share/plover/assets
/usr/lib/python3/dist-packages/plover/assets/commands.json (plover) !=
/usr/share/plover/assets/commands.json (?)
/usr/lib/python3/dist-packages/plover/assets ->
../../../../share/plover/assets
/usr/lib/python3/dist-packages/plover/assets/main.json (plover) !=
/usr/share/plover/assets/main.json (?)
/usr/lib/python3/dist-packages/plover/assets ->
../../../../share/plover/assets
/usr/lib/python3/dist-packages/plover/assets/plover.png (plover) !=
/usr/share/plover/assets/plover.png (?)
/usr/lib/python3/dist-packages/plover/assets ->
../../../../share/plover/assets
/usr/lib/python3/dist-packages/plover/assets/user.json (plover) !=
/usr/share/plover/assets/user.json (?)
/usr/lib/python3/dist-packages/plover/assets ->
../../../../share/plover/assets
cheers,
Andreas
plover_4.0.0~rc2-0.2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: plover
Source-Version: 4.0.0~rc2-0.3
Done: Boyuan Yang <by...@debian.org>
We believe that the bug you reported is fixed in the latest version of
plover, 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.
Boyuan Yang <by...@debian.org> (supplier of updated plover 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, 08 Jun 2024 19:40:06 -0400
Source: plover
Architecture: source
Version: 4.0.0~rc2-0.3
Distribution: unstable
Urgency: medium
Maintainer: Harlan Lieberman-Berg <hlieber...@debian.org>
Changed-By: Boyuan Yang <by...@debian.org>
Closes: 1071114
Changes:
plover (4.0.0~rc2-0.3) unstable; urgency=medium
.
* Non-maintainer upload.
* debian/plover.maintscript: Add symlink_to_dir helper to fix unhandled
conversion from symlink to directory. (Closes: #1071114)
Checksums-Sha1:
a3ed2d1283b8a3f6dd1977881b0cee86124b29e1 2275 plover_4.0.0~rc2-0.3.dsc
79f230e1b757f63fb2c5beae985281a461ae81ed 4349852 plover_4.0.0~rc2.orig.tar.gz
66b920fca446df8fdacc0a9eab83ee7abe6e6df4 9476
plover_4.0.0~rc2-0.3.debian.tar.xz
573f693a3b5a4d796e76944f4c554e7b4f082111 11064
plover_4.0.0~rc2-0.3_amd64.buildinfo
Checksums-Sha256:
cef237c75b30951edd3a62613d433797b069081762a92bfca64a0fb0c922c8f1 2275
plover_4.0.0~rc2-0.3.dsc
5232ec40b536f87dbb80eb16d4a21fccf2b069c5d221d24e26b8e65ad575104e 4349852
plover_4.0.0~rc2.orig.tar.gz
64f4805b2bbe8a0bec0b100bdc5169c4acdf195514d881d3629f297f123c7fab 9476
plover_4.0.0~rc2-0.3.debian.tar.xz
6902ae23e2cd223067739aee80621bf8b837fc002f381cc0df970dd252327e56 11064
plover_4.0.0~rc2-0.3_amd64.buildinfo
Files:
76bd1846e208c31158d2e311953bf406 2275 utils optional plover_4.0.0~rc2-0.3.dsc
74495e6f8477a9df93c4a33ef2272ce5 4349852 utils optional
plover_4.0.0~rc2.orig.tar.gz
85436b930c2de4c0904b9a1c0f35a26f 9476 utils optional
plover_4.0.0~rc2-0.3.debian.tar.xz
17843054ce6130d1402a4d78a30173e0 11064 utils optional
plover_4.0.0~rc2-0.3_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmZk7QYACgkQwpPntGGC
Ws70og/+IzM57iEpai2Qxt7ILTJLhTbKxmuK07t7km46RZWFjlCdm7rKmI+aIYdV
q1zxcOZEddUkFhw8F8Vc+7B/ce+DPN9F4L2gSypwdrFz9SoXG4f2fShbf2NvK3OR
Z45xCRJoNVhxpdwGKoNKQSfndAJYusI4Jwyh24SXiWarlr7oiQKQh4cAsJkneKzK
FyCdBV3nt7bv42XZ5b+1kGdVfsEWZkvdmCAQd45mxCQT3N6jul5nI0t/25siKZdY
oaOFPol4nZlvqE4d/u7xdyBXPEQCcsHwOtJRyNePg4NieL0rEGoz4781XEedl6e5
l4nb8+wg4IlzUEuOjegnEyrWQFit2GLgPam/A2wRlcBb+GuNniMLBJQtQtFGkPK9
n8mg7vpm6a5yrGfHScZ1tBQVMBmaOsCcPv2tPbxYIW8XRJVHshWsHY2myGiCblX5
ODG4EmronLQmXffiHdYXg6xUEp8oRfUNBkScLQdIXVQ6OAGWNYGdz3tBcIHjqKr4
YiO3OP4pqPtEexNNy0ZLU4LGZ4h6BezcImNfMlLd9Pn7PszemHNKG0ZEhGWw1u1B
2yN6Cs/ugv3PU+DrnaX4DpqzWMkWyyAiXQvwHm5vwQoN+z4ADjLTVii0NjmKN8r0
cNPNpXK/NAkdnrywhb1a6eVUH620V5HaWPsSfTY3UEqVupCBEx0=
=Un7b
-----END PGP SIGNATURE-----
pgpGqa2SVY4EB.pgp
Description: PGP signature
--- End Message ---
