Your message dated Mon, 10 Aug 2015 00:08:40 +0200
with message-id <20150809220840.gb20...@home.ouaza.com>
and subject line Re: Bug#795027: jarwrapper: Does not work when installed in
chroot while already active outside the chroot
has caused the Debian Bug report #795027,
regarding jarwrapper: Does not work when installed in chroot while already
active outside the chroot
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
795027: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795027
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jarwrapper
Version: 0.52
Severity: important
User: de...@kali.org
Usertags: origin-kali
In Kali, we have a package depending on jarwrapper and which provides
/usr/bin/burpsuite as an executable jar. However when it gets installed
in the build chroot of our live ISO image, the postinst of jarwrapper does
nothing because it believes that the required binfmt-support is already
there:
Setting up jarwrapper (0.48) ...
update-binfmts: warning: found manually created entry for jarwrapper in
/proc/sys/fs/binfmt_misc; leaving it alone
Thus nothing is stored in /var/lib/binfmts/ and the required binfmt_misc
support is not setup when you boot the generated live image.
$ ls -al /var/lib/binfmts/
total 12
drwxr-xr-x 2 root root 4096 août 9 19:15 .
drwxr-xr-x 17 root root 4096 août 9 19:15 ..
-rw-r--r-- 1 root root 58 août 9 19:15 python2.7
I believe that the proper fix for this is also the proper fix for
#779895 : shipping a file ready to use by binfmt-support
in /usr/share/binfmts as /usr/share/doc/binfmt-support/README.Debian
suggests.
A patch will follow.
-- System Information:
Debian Release: stretch/sid
APT prefers oldoldstable
APT policy: (500, 'oldoldstable'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages jarwrapper depends on:
ii binfmt-support 2.1.5-1
ii fastjar 2:0.98-5
jarwrapper recommends no packages.
jarwrapper suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: block -1 by 750245
Control: affects 750245 + jarwrapper
On Sun, 09 Aug 2015, Raphaël Hertzog wrote:
> Setting up jarwrapper (0.48) ...
> update-binfmts: warning: found manually created entry for jarwrapper in
> /proc/sys/fs/binfmt_misc; leaving it alone
[...]
> I believe that the proper fix for this is also the proper fix for
> #779895 : shipping a file ready to use by binfmt-support
> in /usr/share/binfmts as /usr/share/doc/binfmt-support/README.Debian
> suggests.
So I thought that switching to file-based registration would solve
this issue but I was wrong. The patch I sent sooner is still good to
apply because it ensures we don't rely on local state data but on
system-wide packaged data.
But it doesn't solve this issue... the fix needs to happen at the
binfmt-support level (cf #750245).
So I'm closing this bug and attaching my patch to the other bug report.
Sorry for the noise.
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/
--- End Message ---
__
This is the maintainer address of Debian's Java team
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>.
Please use
debian-j...@lists.debian.org for discussions and questions.
