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

Matthias Klose doko at debian.org
Wed Sep 6 16:56:11 UTC 2017


On 06.09.2017 15:08, Emmanuel Bourg wrote:
> 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

I didn't try that.

> - remove the suffix from the version in the pom

doesn't work

> - remove the --has-package-version flag

doesn't work

Matthias



More information about the pkg-java-maintainers mailing list