Hello, On 2021-03-16 12:39, Andreas Beckmann wrote: > 1m40.0s ERROR: FAIL: silently overwrites files via directory symlinks: > /usr/share/doc/nauty/changelog.Debian.gz (nauty) != > /usr/share/doc/libnauty2/changelog.Debian.gz (libnauty2:amd64) > /usr/share/doc/nauty -> /usr/share/doc/libnauty2 > /usr/share/doc/nauty/changelog.gz (nauty) != > /usr/share/doc/libnauty2/changelog.gz (libnauty2:amd64) > /usr/share/doc/nauty -> /usr/share/doc/libnauty2 > /usr/share/doc/nauty/changes24-27.txt.gz (nauty) != > /usr/share/doc/libnauty2/changes24-27.txt.gz (libnauty2:amd64) > /usr/share/doc/nauty -> /usr/share/doc/libnauty2 > /usr/share/doc/nauty/copyright (nauty) != > /usr/share/doc/libnauty2/copyright (libnauty2:amd64) > /usr/share/doc/nauty -> /usr/share/doc/libnauty2
I am trying to debug the issue, however, unsuccessfully. From the attached log I gather that the break happens upon upgrading from buster (2.6r10+ds-1) to bullseye (2.7r1+ds-1): 1m38.6s DUMP: PIUPARTS_DISTRIBUTION_PREV=buster PIUPARTS_DISTRIBUTION=bullseye Affected binary packages are nauty and libnauty. The former has recently (in 2.7r1+ds-1) switched from shipping a directory symlink to a real directory, and this is accommodated in debian/nauty.maintscript: symlink_to_dir /usr/share/doc/nauty libnauty2 2.7r1+ds-1~ >From this I gather that upgrades of nauty <= 2.7r1+ds-1 to this new version should trigger the replacement of a symlink with real directory before placing the files inside. Or am I wrong? Best, Andrius
