Bug#874494: rebuilding libsambox-java generates unmet dependency on libsejda-io-java (>= 1.1.3.RELEASE)

Emmanuel Bourg ebourg at apache.org
Wed Sep 6 13:08:45 UTC 2017


Le 6/09/2017 à 14:51, Matthias Klose a écrit :

> rebuilding libsambox-java generates unmet dependency on libsejda-io-java (>=
> 1.1.3.RELEASE)
> 
> $ dpkg -I ../libsambox-java_1.0.34-1_all.deb | grep Depends
>  Depends: libcommons-io-java, libfontbox2-java (>= 2.0.7), libsejda-io-java (>=
> 1.1.3.RELEASE), libslf4j-java (>= 1.7.25)

This is an issue with libsejda-io-java, the --has-package-version flag
was mistakenly used [1]. This led maven-debian-helper to think that it
could use the version in the pom as a version constraint at the package
level, which is wrong in this case due to the ".RELEASE" suffix (this
behavior was broken before maven-debian-helper 2.2, see #862894).

The solution is to either:
- add the ".RELEASE" suffix to the package version
- remove the suffix from the version in the pom
- remove the --has-package-version flag

[1]
https://sources.debian.net/src/libsejda-io-java/1.1.3-1/debian/libsejda-io-java.poms/#L28



More information about the pkg-java-maintainers mailing list