Bug#742864: Build without "nostrip" fails on weezy, another try for debian/control generation
Le 08/07/2014 11:47, Thomas Klute a écrit :
> Compiling with the same build system (plus freshly generated
> debian/control) in a sid chroot works just fine. I'm not sure if this
> should be considered important for OpenJDK 8 packaging (looks more like
> a binutils bug to me). Any suggestions on how to handle this?
Could this be related to Lintian emitting a
debug-file-with-no-debug-symbols warning about these files?
> By the way, is the double "-8" in the cacao and jamvm package names
> intentional? It seems strange to me.
Thank you for spotting this, I made a mistake when I renamed these
packages. I pushed a fix.
> I've also taken another look at the debian/control situation. My
> previous suggestion to remove it from the repository could create the
> problem that it could not easily be generated from a fresh repository
> clone, because the code in debian/rules expected the file to be present
> (though it could be empty). A patch available on my Github repository
> [1] fixes that.
Good idea, I merged it. I also got caught by this issue once.
Emmanuel Bourg
Reply to: