Hi, Would you mind detailing how you invoke piuparts so it gives that error? I've been running it for an hour and I only get successes (or false positives about font dirs that I skipped with --warn-on-leftovers-after-purge). The logs you provide apparently initializes a server by installing "hello" and running then seem to do special tests that are different from e.g. https://piuparts.debian.org/sid/source/f/freedink.html .
This, so I can thoroughly reproduce the bug(s) and test my fixes (unless you have a working patch, that is). - Sylvain On 28/01/2019 17:21, Andreas Beckmann wrote: > Package: freedink > Version: 109.4-1 > Severity: serious > User: [email protected] > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package fails to upgrade from > 'testing'. > It installed fine in 'testing', then the upgrade to 'sid' fails > because it tries to overwrite other packages files without declaring a > Breaks+Replaces relation. > > See policy 7.6 at > https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces > > From the attached log (scroll to the bottom...): > > Preparing to unpack .../freedink_109.4-1_all.deb ... > > Unpacking freedink > (109.4-1) ... > > dpkg: error processing archive > /var/cache/apt/archives/freedink_109.4-1_all.deb (--unpack): > > trying to overwrite > '/usr/share/metainfo/freedink.appdata.xml', which is also in package > freedink-engine 109.2-1 > Errors were encountered while > processing: > > /var/cache/apt/archives/freedink_109.4-1_all.deb > > > > > cheers, > > Andreas
