Source: blt Version: 2.5.3+dfsg-6 Severity: important User: helm...@debian.org Usertags: rebootstrap
Hi Sergei, did you know that blt participates in architecture bootstrap? It's required for building the Python interpreter for instance and thus far, this has all worked out well, but now you added a build dependency on libjpeg-dev. libjpeg-turbo in turn Build-Depends on default-jdk and while it builds its -java package as an Arch:all package, the jdk actually is being used as it stuffs jni symbols into the main library, so really the Arch:any package already requires default-jdk. So now we have a path from Python to Java. We also have a path from Java to Python already, so your blt upload introduces a bootstrap dependency cycle and this is bad. I suggest that you temporarily revert this change in unstable to restore the ability to bootstrap Debian from source. Then let's figure out the best way to break the cycle before re-enabling jpeg support. This has mostly worked earlier, because libjpeg-turbo was not part of the bootstrap set. Even adding libjpeg-turbo seems fine in principle, but Java less so. As explained earlier, breaking the cycle between libjpeg-turbo and Java is harder, because there are Java-specific symbols in the main library. Making jpeg support optional in blt seems similarly impractical to me. This is definitely more work than just enabling jpeg support unfortunately. Do you have more ideas? Helmut
