On Wed, Sep 06, 2017 at 12:31:19AM +0200, Andreas Beckmann wrote: > during a test with piuparts I noticed your package fails to upgrade from > 'stretch'. > It installed fine in 'stretch', then the upgrade to 'buster' 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#s-replaces
While it's true there's a bug, and I will fix that, I do not understand why piuparts is installing python3-cliapp. That doesn't seem like an obvious thing to do. The python3 version of the package did not exist in stretch, and upgrading the python2 version from stretch to buster seems to work just fine: I just tested that manually in a chroot. From the piuparts log I see that it is explicitly installing the python3 version after upgrading to buster. (Also, the advice to use Replaces+Breaks is just wrong for this package. The bug is that the same file is in both the python2 and python3 versions of the package. The correct solution is to have it in at most one package. I will be making that fix eventually.) -- I want to build worthwhile things that might last. --joeyh
signature.asc
Description: PGP signature