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

[Markus Koschany]

Am 10.09.2017 um 00:22 schrieb Emmanuel Bourg:
> Control: reassign -1 libsejda-io-java
> Control: affects -1 libsambox-java
> Control: tags -1 + patch
> 
> Le 9/09/2017 à 19:53, Markus Koschany a écrit :
> 
>> thanks for the patch. However we can just remove the
>> --has-package-version option in libsambox-java.poms which will have the
>> same effect. This issue was caused by a recent change in
>> maven-debian-helper and affects multiple packages.
> 
> The --has-package-version flag in libsambox-java is fine. It's the one
> in libsejda-io-java that isn't consistent with the pom version, sorry if
> this wasn't clear. The patch proposed is a good solution.

Hi,

I understand that this will resolve the issue but in my opinion patching
the pom file is the wrong solution. In fact we should avoid as much as
possible to do this kind of work manually.

I have created a bunch of packages which have a .RELEASE or .FINAL
version. Of course we can go without that in Debian. This probably
affects all jboss-* packages. Many of them use --has-package-version. If
we don't remove the --has-package-version flag from all of those
packages we will face a similar situation in the future.

If the change in maven-debian-helper is permanent than I am in favor of
removing this flag in packages because I don't want to maintain several
patches which just correct a version number. Tools like m-d-h should
take care of this for me.

Markus

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20170910/7ede904b/attachment.sig>