Bug#919803: Bug#919802: libjstun-java: FTBFS (The code being documented uses packages in the unnamed module)

[Gilles Filippini]

Santiago Vila a écrit le 29/01/2019 à 22:55 :
> On Tue, Jan 29, 2019 at 09:44:40PM +0100, Gilles Filippini wrote:
> 
>> Looking at the jh_build code, the list of -link javadoc options is constructed from this snippet:
>>    CLASSPATHDOCS="`for i in $(grep-dctrl --no-field-names --show-field Build-Depends,Build-Depends-Indep -F source "$pkg" debian/control | tr , ' ' | sed 's/([^)]*)//g') ; do dpkg -L $i 2>/dev/null | grep /usr/share/doc/.*/api$; done | sed 's/^/-link /' | xargs`"
>>
>> Then dropping default-jdk-doc from Build-Depends did the trick!
> 
> Please note that if the package does not build when default-jdk-doc is
> present, then (imo) you should probably use build-conflicts against it and
> any similar package which we know makes the package to FTBFS, not just
> remove it from build-depends.
> 
> (At least this is what build-conflicts was invented for).

No, this is a misunderstanding: the code snippet above scans
Build-Depends* fields from debian/control. If default-jdk-doc is
installed but not referenced in Build-Depends*, then the package will
build fine. I've tested this configuration.

Thanks,

_g.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-java-maintainers/attachments/20190129/6a9a787b/attachment.sig>