On Thu, May 11, 2017 at 12:33:36PM -0500, Jerome wrote: > Thank's a lot for your questions and remark. This will help me to detect > where was the problem. > And i apologize that teh error is generated during the creation of a live > debian iso file. As the error wa detected in the live itself, i send the > report as this.. Forgetting that i'm in a live session. You're bug system is > too perfect, as it permit report bugs in a live session! > > The problem was detected and corrected in the binfmt-support bug (#750245). > > So i'm declaring this issue corrected, as this from another problem.
Hello Jerome, Thank you for the follow-up and for tracing the problem back to an issue with the Live CD. It's always useful to know where these issues remain. While I was poking around with this, I was able to reproduce the problem by installing the jessie-backports version of artemis into a jessie chroot on a stretch (testing) system. (Which is nothing new, because it's just another mhandanifestation of #750245.) The root cause of the issue in the older chroot can be seen by trying to run the jarwrapper.postinst directly: # /var/lib/dpkg/info/jarwrapper.postinst update-binfmts: warning: found manually created entry for jarwrapper in /proc/sys/fs/binfmt_misc; leaving it alone Installing a artemis into a stretch or sid chroot on the same system works fine. What's curious to me (and perhaps helpful to others?), is that if I create a jessie chroot and install jarwrapper *before* installing artemis, and more to the point, before installing the JDK and its dependencies, the jarwrapper binfmt functions correctly. Cheers, tony
signature.asc
Description: PGP signature
