Package: qemu-user-static Version: 1:2.7+dfsg-3 When I upgrade from the previous (working) version in 'testing', I get a configure failure:
/-------- | # dpkg --configure -a | Setting up qemu-user-static (1:2.7+dfsg-3) ... | update-binfmts: warning: unable to close /proc/sys/fs/binfmt_misc/register: Invalid argument | update-binfmts: warning: unable to enable binary format qemu-mips | update-binfmts: exiting due to previous errors | dpkg: error processing package qemu-user-static (--configure): | subprocess installed post-installation script returned error exit status 2 \-------- Running 'update-binfmts' by hand causes similar complaints: /-------- | # update-binfmts --enable | update-binfmts: warning: unable to close /proc/sys/fs/binfmt_misc/register: Invalid argument | update-binfmts: warning: unable to close /proc/sys/fs/binfmt_misc/register: Invalid argument | update-binfmts: warning: unable to close /proc/sys/fs/binfmt_misc/register: Invalid argument | update-binfmts: exiting due to previous errors \-------- I was able to work around this issue by hand-editing the postinst it to add '|mips*' to the end of $omit (luckily, I don't need MIPS emulation on my systems). The one thing that stands out about the MIPS registration is that the magic and mask are much longer than for other systems - is it possible that the kernel can't handle such long patterns? If so, can this be detected and avoided? -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (900, 'stable'), (400, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armel Kernel: Linux 3.16.7-ckt2-balti (SMP w/8 CPU cores; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) qemu-user-static depends on no packages. Versions of packages qemu-user-static recommends: ii binfmt-support 2.1.6-1 Versions of packages qemu-user-static suggests: ii sudo 1.8.17p1-2 -- no debconf information
