Bug#805228: Bug#806630: libnative-platform-java: FTBFS when built with dpkg-buildpackage -A (mh_installjar fails)
tony mancill
tmancill at debian.org
Sun Jul 17 15:22:59 UTC 2016
On 07/16/2016 03:35 PM, Santiago Vila wrote:
> On Sat, 16 Jul 2016, tony mancill wrote:
>
>> The first two packages I tried, src:pegdown and src:libjbcrypt-java,
>> both appear in the "successfully built reproducibly" set here [1], and
>> neither has any bugs assigned to it. Maybe I'm looking in the wrong place?
>
> If those packages generate only "Arch: all" packages and they build ok
> in the reproducible builds setup, then those packages are ok.
>
> The problem with the helper program you are using seems to be that it
> makes "dpkg-buildpackage -A" to fail on packages generating both
> "Arch: all" and "Arch: any" binary packages.
>
> The same packages might appear as "ok" in reproducible builds because
> they just test for "dpkg-buildpackage".
>
> So, it is possible that there are no other affected packages than the
> ones in my list.
Thank you the clarification. If that's the case, we can probably
address the bug with src:libnative-platform-java by updating
debian/rules to avoid using the DH sequencer and making the required
calls to mh_install explicitly.
That doesn't detract from the severity of this bug, but does allow more
time for discussion.
Cheers,
tony
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20160717/d05ab3d0/attachment.sig>
More information about the pkg-java-maintainers
mailing list