Your message dated Mon, 30 Jul 2012 10:32:13 +0000
with message-id <e1svngn-0002hh...@franck.debian.org>
and subject line Bug#680349: fixed in binfmt-support 2.0.10
has caused the Debian Bug report #680349,
regarding binfmt-support: first update-binfmts --install call fails in chroot 
with update-binfmts: warning: unable to close 
/proc/sys/fs/binfmt_misc/register: Invalid argument
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.)


-- 
680349: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680349
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: binfmt-support
Version: 2.0.8
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed a failure in the jarwrapper
package whcih I traced to update-binfmts.

To reproduce:
* the host has the kernel module loaded and /proc/sys/fs/binfmt_misc is
  mounted, kernel: 3.2.0-2-amd64
* the chroot is a minimal sid or wheezy chroot and
  /proc/sys/fs/binfmt_misc is not yet mounted, but /proc is mounted
* apt-get install jarwrapper
[...]
Setting up binfmt-support (2.0.9) ...
invoke-rc.d: policy-rc.d denied execution of start.
Setting up fastjar (2:0.98-3) ...
Setting up jarwrapper (0.43) ...
update-binfmts: warning: unable to close /proc/sys/fs/binfmt_misc/register: 
Invalid argument
update-binfmts: warning: unable to enable binary format jarwrapper
update-binfmts: exiting due to previous errors
dpkg: error processing jarwrapper (--configure):
 subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
 jarwrapper
* now /proc/sys/fs/binfmt_misc got mounted and the foloowing succeeds:
* dpkg --configure --pending
Setting up jarwrapper (0.43) ...
The problem can be reproduced inside this chroot easily:

# umount /proc/sys/fs/binfmt_misc/
# update-binfmts --install jarwrapper /usr/bin/jarwrapper --magic 'PK\x03\x04' 
--detector /usr/bin/jardetector
update-binfmts: warning: unable to close /proc/sys/fs/binfmt_misc/register: 
Invalid argument
update-binfmts: warning: unable to enable binary format jarwrapper
update-binfmts: exiting due to previous errors
# update-binfmts --install jarwrapper /usr/bin/jarwrapper --magic 'PK\x03\x04' 
--detector /usr/bin/jardetector && echo success
success

I'm setting the severity to serious as this breaks installation
and testing of unrelated packages. (And I'll add here Affects/Found in 
the other packages s.t. piuparts can find this bugreport for automated
classification)

Looking at the code, /proc/sys/fs/binfmt_misc/register gets opened (but
does not exist), then /proc/sys/fs/binfmt_misc gets mounted and brings
its own /proc/sys/fs/binfmt_misc/register, thereafter the originally
opened /proc/sys/fs/binfmt_misc/register no longer seems to exist and
closing fails.

Andreas



--- End Message ---
--- Begin Message ---
Source: binfmt-support
Source-Version: 2.0.10

We believe that the bug you reported is fixed in the latest version of
binfmt-support, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 680...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson <cjwat...@debian.org> (supplier of updated binfmt-support package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 30 Jul 2012 10:36:59 +0100
Source: binfmt-support
Binary: binfmt-support
Architecture: source i386
Version: 2.0.10
Distribution: unstable
Urgency: low
Maintainer: Colin Watson <cjwat...@debian.org>
Changed-By: Colin Watson <cjwat...@debian.org>
Description: 
 binfmt-support - Support for extra binary formats
Closes: 680349
Changes: 
 binfmt-support (2.0.10) unstable; urgency=low
 .
   * If a binary format is already enabled according to the kernel, which can
     happen in chroots if it was installed in the host system, then continue
     as gracefully as we can manage rather than exiting non-zero (closes:
     #680349).
   * Upgrade to Automake 1.11.6.
Checksums-Sha1: 
 fc0b4726f35ed3752a0585b6cff0d29a827cbac7 1602 binfmt-support_2.0.10.dsc
 e49ed41a5d2dcdcb26aa5a871067b05a134e9051 583483 binfmt-support_2.0.10.tar.gz
 526b536683667db12c6e155b6662ab81fde4a161 82078 binfmt-support_2.0.10_i386.deb
Checksums-Sha256: 
 94e4a0a43ca1551bf4d88710956c3053b8a5ca9300a50e42624a5c5ac3c2024d 1602 
binfmt-support_2.0.10.dsc
 78f7c87984b6dc3d0331a8099c8bbde40850b874da337703a0fb090a2425bafc 583483 
binfmt-support_2.0.10.tar.gz
 3572de686d3050d123ee382779573443f154542a5eb5d437cf601ee893ab6f93 82078 
binfmt-support_2.0.10_i386.deb
Files: 
 17786ae49f3c08eb8e07badeeb6846bd 1602 admin optional binfmt-support_2.0.10.dsc
 a2e5084eb516bc3adf0e0d8704964c8e 583483 admin optional 
binfmt-support_2.0.10.tar.gz
 9149efcd0abeaf49f26f23b169bdeb45 82078 admin optional 
binfmt-support_2.0.10_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Colin Watson <cjwat...@debian.org> -- Debian developer

iQIVAwUBUBZhKjk1h9l9hlALAQhxVg//fy/rMfpgQoc8PJfQKLYDsJHSCyNoyKu1
sCcBi3E//TvX2sgWSHRBcFY8/KBFVFn634cm9uIaH9ndtMtDHu+UiLiRl5Vu9MLz
a1A4KEv1W3X5tyh/LPCLrl5bgHR8hKU4YpYcLCZ3EBkLs2TmJxpWbkXFSI4VsB3Z
GKSQ4o6trh1JxEUB7/D/gkAscPzD7EsmXvBtwB3J8ExXcq59uwOoQncYBCwE/OQt
VMaOMaOjn6oFZ4Jy1FCLqhM3pjt/nqgzkKt5l7JD6q1dCZLpaYrGH/cDHyqiGI1d
uLRI8wOXfggwRB71Lxr4UY3haCX4PaPLqyNNDi/Wir58+vYS2Em0XafbsuzGr3T7
fp454ZhG22LZr6IIdgTemFib1Xnt78vr8cnwmP6/2Z+3G+HS4GL2R1kuFKuWZ4MJ
gwkBm2uspqDAhjbbAxnr46v8XLruNXpVzX+eDtK4YyA25G0JC7BvWdtTSOrmbJO0
9//g/aOoTxfWTI4ssWQ0p0wDb8EqLRgznjiaUlQIa9LO1lr3mwHVXsElbFXxEWRV
ARr9JMCod/UM0e3+3l5+5tQwNN/vaszeLnvrL1z8gEjKVZk9M2x5Lf7GqqQLCVYU
pjCs0yiGyUS0i2YsQN8sz4I3xqDUTbGwBotdwb4WD/WARu2P1nd5uu7FeHZ8DFN5
QsuDmmHZJfk=
=awly
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to