Your message dated Thu, 26 Mar 2020 20:53:24 +0000
with message-id <e1jhzve-0000cv...@fasolo.debian.org>
and subject line Bug#950090: fixed in gcc-mingw-w64 22~exp3
has caused the Debian Bug report #950090,
regarding gcc-mingw-w64: 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.)


-- 
950090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950090
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-mingw-w64
Version: 22~exp2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + gcc-mingw-w64-x86-64 gfortran-mingw-w64-x86-64 
g++-mingw-w64-x86-64 gobjc-mingw-w64-x86-64 gobjc++-mingw-w64-x86-64 
gnat-mingw-w64-x86-64
Control: affects -1 + gcc-mingw-w64-i686 gfortran-mingw-w64-i686 
g++-mingw-w64-i686 gobjc-mingw-w64-i686 gobjc++-mingw-w64-i686 
gnat-mingw-w64-i686
Control: found -1 gcc-mingw-w64/9.2.1-21+22~exp2

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:

  sid -> experimental

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...):

0m37.3s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/g++-mingw-w64-i686/changelog.Debian.gz (g++-mingw-w64-i686) != 
/usr/share/doc/gcc-mingw-w64-base/changelog.Debian.gz (gcc-mingw-w64-base)
    /usr/share/doc/g++-mingw-w64-i686 -> gcc-mingw-w64-base
  /usr/share/doc/g++-mingw-w64-i686/changelog.gz (g++-mingw-w64-i686) != 
/usr/share/doc/gcc-mingw-w64-base/changelog.gz (gcc-mingw-w64-base)
    /usr/share/doc/g++-mingw-w64-i686 -> gcc-mingw-w64-base
  /usr/share/doc/g++-mingw-w64-i686/copyright (g++-mingw-w64-i686) != 
/usr/share/doc/gcc-mingw-w64-base/copyright (gcc-mingw-w64-base)
    /usr/share/doc/g++-mingw-w64-i686 -> gcc-mingw-w64-base
  /usr/share/doc/gcc-mingw-w64-i686/changelog.Debian.gz (gcc-mingw-w64-i686) != 
/usr/share/doc/gcc-mingw-w64-base/changelog.Debian.gz (gcc-mingw-w64-base)
    /usr/share/doc/gcc-mingw-w64-i686 -> gcc-mingw-w64-base
  /usr/share/doc/gcc-mingw-w64-i686/changelog.gz (gcc-mingw-w64-i686) != 
/usr/share/doc/gcc-mingw-w64-base/changelog.gz (gcc-mingw-w64-base)
    /usr/share/doc/gcc-mingw-w64-i686 -> gcc-mingw-w64-base
  /usr/share/doc/gcc-mingw-w64-i686/copyright (gcc-mingw-w64-i686) != 
/usr/share/doc/gcc-mingw-w64-base/copyright (gcc-mingw-w64-base)
    /usr/share/doc/gcc-mingw-w64-i686 -> gcc-mingw-w64-base

0m36.2s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/gcc-mingw-w64-x86-64/changelog.Debian.gz 
(gcc-mingw-w64-x86-64) != /usr/share/doc/gcc-mingw-w64-base/changelog.Debian.gz 
(gcc-mingw-w64-base)
    /usr/share/doc/gcc-mingw-w64-x86-64 -> gcc-mingw-w64-base
  /usr/share/doc/gcc-mingw-w64-x86-64/changelog.gz (gcc-mingw-w64-x86-64) != 
/usr/share/doc/gcc-mingw-w64-base/changelog.gz (gcc-mingw-w64-base)
    /usr/share/doc/gcc-mingw-w64-x86-64 -> gcc-mingw-w64-base
  /usr/share/doc/gcc-mingw-w64-x86-64/copyright (gcc-mingw-w64-x86-64) != 
/usr/share/doc/gcc-mingw-w64-base/copyright (gcc-mingw-w64-base)
    /usr/share/doc/gcc-mingw-w64-x86-64 -> gcc-mingw-w64-base
  /usr/share/doc/gfortran-mingw-w64-x86-64/changelog.Debian.gz 
(gfortran-mingw-w64-x86-64) != 
/usr/share/doc/gcc-mingw-w64-base/changelog.Debian.gz (gcc-mingw-w64-base)
    /usr/share/doc/gfortran-mingw-w64-x86-64 -> gcc-mingw-w64-base
  /usr/share/doc/gfortran-mingw-w64-x86-64/changelog.gz 
(gfortran-mingw-w64-x86-64) != /usr/share/doc/gcc-mingw-w64-base/changelog.gz 
(gcc-mingw-w64-base)
    /usr/share/doc/gfortran-mingw-w64-x86-64 -> gcc-mingw-w64-base
  /usr/share/doc/gfortran-mingw-w64-x86-64/copyright 
(gfortran-mingw-w64-x86-64) != /usr/share/doc/gcc-mingw-w64-base/copyright 
(gcc-mingw-w64-base)
    /usr/share/doc/gfortran-mingw-w64-x86-64 -> gcc-mingw-w64-base

This seems to affect the full language x arch matrix.

Note that dpkg-maintscript-helper symlink_to_dir etc. don't work
reliably if the architecture changes between any and all.


cheers,

Andreas

Attachment: g++-mingw-w64-i686_9.2.1-21+22~exp2.log.gz
Description: application/gzip


--- End Message ---
--- Begin Message ---
Source: gcc-mingw-w64
Source-Version: 22~exp3
Done: Stephen Kitt <sk...@debian.org>

We believe that the bug you reported is fixed in the latest version of
gcc-mingw-w64, 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 950...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stephen Kitt <sk...@debian.org> (supplier of updated gcc-mingw-w64 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: Thu, 26 Mar 2020 20:56:24 +0100
Source: gcc-mingw-w64
Architecture: source
Version: 22~exp3
Distribution: experimental
Urgency: medium
Maintainer: Stephen Kitt <sk...@debian.org>
Changed-By: Stephen Kitt <sk...@debian.org>
Closes: 950090
Changes:
 gcc-mingw-w64 (22~exp3) experimental; urgency=medium
 .
   * Adjust gm2 extraction to allow building with current versions of gcc-
     9-source.
   * Handle symlink conversions for the new meta-packages. Closes:
     #950090.
   * Standards-Version 4.5.0, no change required.
Checksums-Sha1:
 f7b7a47b88c9810c9753eb09f1d4dbd047c9e355 6300 gcc-mingw-w64_22~exp3.dsc
 621f8415f5a0b992fdd781ff619ac8407e253b32 32432 gcc-mingw-w64_22~exp3.tar.xz
 7ccd7d67ef1679876a9855aaacf1029578e62eb7 8190 
gcc-mingw-w64_22~exp3_source.buildinfo
Checksums-Sha256:
 c786069df7a67c994cfdad8c0ef53bdbac39c5ede2bbcc94fc9390709e86640f 6300 
gcc-mingw-w64_22~exp3.dsc
 d26f64cd5f9bb0d9d609ed4c15dff50a532ad0a31c576fee8942acf409ad95c4 32432 
gcc-mingw-w64_22~exp3.tar.xz
 fe98226f0e124298f5d7ef6f398429d3b42dfa76e53a3da5218effa6cfd79de6 8190 
gcc-mingw-w64_22~exp3_source.buildinfo
Files:
 bc183363e71af3ff8fb0d583b104f99b 6300 devel optional gcc-mingw-w64_22~exp3.dsc
 2ba18d68215afdec07e28428d1c90bdb 32432 devel optional 
gcc-mingw-w64_22~exp3.tar.xz
 0aeb8fd5ebc1dc69237bc4686e75fa54 8190 devel optional 
gcc-mingw-w64_22~exp3_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAl59CSoACgkQgNMC9Yht
g5yT1w/7BcqK6MRUaoomHCM9nKkOnKBQL8yosTxhpNP7J/V4robDnjqX+0eCHMl2
u2j5Ze8SXnkGvHhY2y9dhw6MsTtregMeHMjnPP2Ps+zX72uswB/xLaARH4nF02tl
hVxKS2X1XR74xjqYkUIhGaPnK1V30cm2sH0w2xVQJCGZWR86C+sE5etS4qjWQ5aM
xq/9zDCJ1ABo1HsXxASfh5HtQ7Yr5Rd/GEP2HfZ5SFJCwHAp4eNni7nh8QHWhjby
hc/gFb5IwlmN+lEj/n9Zj/meWJIdpWTfGjRtezyKuZupqY76pT9kht12F3Bu1Ywn
PHJi2QVuQLBVYiH3z3Jv+bmFNrKLbgfLlrzd8DSwmhv13MdN1yizsmjmOlRgZkUh
ajWcE7w1KMBftOviALqmjuaz8luSoysRCbwWCuRnHSzAvLUFTdCRx+BHZKnIXXAZ
xADxibOqNHgjHbHozaFhgmy1wwEiHjfAwvdC93J9DiddYjRzOnQAa1k9//3kOo5X
6uS1DqSF2Vp9Hv1y0x/nQmPKd5PoJBgsdot0v4jwk+PRLKoxAfFZJ+qcW0CPfnqC
CCfEwaNhDIVavPmHCXZdhyT/pvwjDGLjOcT1vRQ6eaOQ3GScokXlhHzk4pBW+d4F
kuIok/U9g7MAW0PDvt1Dka3O1ewMaBYH3QPQSBQWYssHZYWlzzA=
=PBbx
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to