Bug#1055049: libtakari-polyglot-groovy-java: missing Breaks+Replaces: libtakari-polyglot-maven-java (<< 0.4.11-2)

Jérôme Charaoui jerome at riseup.net
Sat Dec 9 21:39:35 GMT 2023


On Mon, 30 Oct 2023 09:37:34 +0100 Andreas Beckmann <anbe at debian.org> wrote:
> 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 .../libtakari-polyglot-groovy-java_0.4.11-2_all.deb ...
>   Unpacking libtakari-polyglot-groovy-java (0.4.11-2) ...
>   dpkg: error processing archive /var/cache/apt/archives/libtakari-polyglot-groovy-java_0.4.11-2_all.deb (--unpack):
>    trying to overwrite '/usr/share/java/polyglot-groovy-0.4.11.jar', which is also in package libtakari-polyglot-maven-java 0.4.11-1
>   Errors were encountered while processing:
>    /var/cache/apt/archives/libtakari-polyglot-groovy-java_0.4.11-2_all.deb

Thanks for the heads up.

I'm not sure what's happening here: polyglot-groovy-0.4.11.jar was 
indeed split away from "libtakari-polyglot-maven-java" and into 
"libtakari-polyglot-groovy-java", however the new version of 
"libtakari-polyglot-maven-java" does *not* depend on/recommend 
"libtakari-polyglot-groovy-java".

So I'm unsure why "libtakari-polyglot-groovy-java" is being installed in 
the first place, during the piuparts upgrade. It's not present in 
testing, and it has currently zero reverse-dependencies.

I did my own testing and on a bare system with 
"libtakari-polyglot-maven-java" installed, upgrading to sid does not 
include an installation of "libtakari-polyglot-groovy-java".

Any idea what's going on?

Thanks,

-- Jérôme



More information about the pkg-java-maintainers mailing list