easymock is uninstallable after rebuild due to --has-package-version switch in byte-buddy

[Vladimir Petko]

Current uploaded version has a repack suffix `~us`

debian/libbyte-buddy-java.poms have --has-package-version switch that indicates that POM version exactly matches Debian version.

This causes all dependencies generate Depends: libbyte-buddy-java (>= 1.14.1) instead of (>= 1.14.1~) in {maven:Depends} variable of the control file, making the dependency uninstallable after rebuild.

Removing --has-package-version will generate an unversioned dependency. We can workaround the issue by manually replacing pom version with the version containing the repack suffix.

Packages dependant on libbyte-buddy-java currently in the archive:

Package: libeasymock-java
Depends: libasm-java (>= 9.4), libbyte-buddy-java (>= 1.12.23), libobjenesis-java (>= 3.3)

Package: libassertj-core-java
Depends: libbyte-buddy-java (>= 1.8.2)

Package: libjmock2-java
Depends: libasm-java (>= 9.0), libbsh-java (>= 2.0b4), libbyte-buddy-java (>= 1.8.2), libcglib-java (>= 3.2.12), libfindbugs-annotations-java, libhamcrest-java, libobjenesis-java (>= 3.1)

Package: libmockito-java
Depends: libhamcrest-java, libbyte-buddy-java (>= 1.8.2-2~), libobjenesis-java

So we do not need to upload no change rebuilds for them.

The issue happened because reverse dependencies were rebuilt, but not tested for instability after rebuild.

[Vladimir Petko (vpa1977)]

piuparts install/upgrade/purge test (pass) (versioned solution)

[Launchpad Janitor (janitor)]

This bug was fixed in the package byte-buddy - 1.14.11~us1-0ubuntu2

---------------
byte-buddy (1.14.11~us1-0ubuntu2) noble; urgency=medium

  * d/rules: replace the pom version with the changelog version to
    include a repack suffix (LP: #2054488). This change fixes
    the inability to install byte-buddy dependencies after rebuild
    due to binary dependency on byte-buddy >= 1.14.11.

 -- Vladimir Petko <email address hidden> Wed, 21 Feb 2024 18:27:13 +1300