Bug#814876: lombok.patcher

Markus Koschany apo at debian.org
Wed Feb 17 16:02:29 UTC 2016


Am 17.02.2016 um 09:59 schrieb Hans-Christoph Steiner:
> 
> I remember getting odd errors like this while working with lombok-ast,
> my solution in the end was to try disabling chunks of lombok*, which
> obviously didn't work.

Yeah.

> Have you tried emailing upstream?  I did manage to get one or two
> responses from them.  This is a very specialized beast.

I think I have "fixed" it now but I can't explain how. Apparently the
old unpacked version of src:lombok works with src:lombok-patcher but the
new one doesn't. It took a while for me to realize that. Even if I
rename the old tarball into 1.16.1+ds2 it will also fail to build...
Perhaps it has something to do with the lombok.version string that is
injected into the build system but I'm not really sure about this. The
journey to find a solution for this bug sometimes reminded me of
Sherlock Holmes:

"When you have eliminated the impossible, whatever remains, however
improbable, must be the truth."


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


More information about the pkg-java-maintainers mailing list