Summary: | app-emulation/qemu-1.4.0 - fcaps on /usr/libexec/virtfs-proxy-helper dies. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | eroen <erikdenstore+gbugs> |
Component: | Current packages | Assignee: | Doug Goldstein (RETIRED) <cardoe> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | qemu+disabled |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
fcaps.patch
fcaps.patch |
Description
eroen
2013-02-25 14:00:17 UTC
You should post full Build.log: * If you need support, post the output of *snip* * the complete build log *snip* * The complete build log is located at '/tmp/portage/app-emulation/qemu-1.4.0/temp/build.log'. No need for a build log when it is clear what needs to be patched.
> * app-emulation/qemu
> Matched Files: /usr/bin/virtfs-proxy-helper;
Yes, since other qemu files are in /usr/libexec it appears they have accidentally typed that for virtfs-proxy-helper as well.
Fixed in tree. (In reply to comment #2) > No need for a build log when it is clear what needs to be patched. Sorry, didn't noticed that. (In reply to comment #3) > Fixed in tree. >>> Regenerating /etc/ld.so.cache... >>> Original instance of package unmerged safely. * If you don't have kvm compiled into the kernel, make sure you have * the kernel module loaded before running kvm. The easiest way to * ensure that the kernel module is loaded is to load it on boot. * For AMD CPUs the module is called 'kvm-amd' * For Intel CPUs the module is called 'kvm-intel' * Please review /etc/conf.d/modules for how to load these * * Make sure your user is in the 'kvm' group * Just run 'gpasswd -a <USER> kvm', then have <USER> re-login. * chmod: cannot access ‘/cap_dac_override’: No such file or directory * ERROR: app-emulation/qemu-1.4.0 failed (postinst phase): * (no error message) * * Call stack: * ebuild.sh, line 93: Called pkg_postinst * environment, line 3676: Called fcaps 'cap_chown' 'cap_dac_override' 'cap_fowner' 'cap_fsetid' 'cap_setgid' 'cap_mknod' 'cap_setuid' '/usr/bin/virtfs-proxy-helper' * environment, line 2343: Called die * The specific snippet of code: * chmod ${caps_mode} "${file}" || die; * * If you need support, post the output of `emerge --info '=app-emulation/qemu-1.4.0'`, * the complete build log and the output of `emerge -pqv '=app-emulation/qemu-1.4.0'`. * This ebuild used the following eclasses from overlays: * /usr/local/portage/eclass/toolchain-funcs.eclass * /usr/local/portage/eclass/flag-o-matic.eclass * The complete build log is located at '/var/log/portage/build/app-emulation/qemu-1.4.0:20130225-184200.log'. * For convenience, a symlink to the build log is located at '/var/tmp/portage/app-emulation/qemu-1.4.0/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-emulation/qemu-1.4.0/temp/environment'. * Working directory: '/var/tmp/portage/app-emulation/qemu-1.4.0' * S: '/var/tmp/portage/app-emulation/qemu-1.4.0/work/qemu-1.4.0' !!! FAILED postinst: 1 Created attachment 340102 [details, diff]
fcaps.patch
Reopening for visibility. Error is no longer printed if capabilities are comma-separated, like Alphat's patch (and fcaps.eclass and cap_from_text(3) suggest). That wasn't what I meant to do /at all/. Sorry about that. The ebuild in portage still generates the error. >>> Original instance of package unmerged safely.
* If you don't have kvm compiled into the kernel, make sure you have
* the kernel module loaded before running kvm. The easiest way to
* ensure that the kernel module is loaded is to load it on boot.
* For AMD CPUs the module is called 'kvm-amd'
* For Intel CPUs the module is called 'kvm-intel'
* Please review /etc/conf.d/modules for how to load these
*
* Make sure your user is in the 'kvm' group
* Just run 'gpasswd -a <USER> kvm', then have <USER> re-login.
*
* Setting caps 'cap_chown,cap_dac_override,cap_fowner,cap_fsetidcap_setgid,cap_mknod,cap_setuid=ep' on file '/usr/bin/virtfs-proxy-helper' failed:
* fatal error: Invalid argument
* usage: setcap [-q] [-v] (-r|-|<caps>) <filename> [ ... (-r|-|<capsN>) <filenameN> ]
*
* Note <filename> must be a regular (non-symlink) file.
* ERROR: app-emulation/qemu-1.4.0 failed (postinst phase):
* could not set caps
*
* Call stack:
* ebuild.sh, line 93: Called pkg_postinst
* environment, line 3499: Called fcaps 'cap_chown,cap_dac_override,cap_fowner,cap_fsetidcap_setgid,cap_mknod,cap_setuid' '/usr/bin/virtfs-proxy-helper'
* environment, line 2063: Called die
* The specific snippet of code:
* die "could not set caps";
*
* If you need support, post the output of `emerge --info '=app-emulation/qemu-1.4.0'`,
* the complete build log and the output of `emerge -pqv '=app-emulation/qemu-1.4.0'`.
* This ebuild used the following eclasses from overlays:
* /usr/local/portage/eclass/toolchain-funcs.eclass
* /usr/local/portage/eclass/flag-o-matic.eclass
* /usr/local/portage/eclass/pax-utils.eclass
* This ebuild is from an overlay named 'custom': '/usr/local/portage/'
* The complete build log is located at '/var/log/portage/build/app-emulation/qemu-1.4.0:20130226-081316.log'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/app-emulation/qemu-1.4.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/app-emulation/qemu-1.4.0/temp/environment'.
* Working directory: '/var/tmp/portage/app-emulation/qemu-1.4.0'
* S: '/var/tmp/portage/app-emulation/qemu-1.4.0/work/qemu-1.4.0'
!!! FAILED postinst: 1
Created attachment 340148 [details, diff]
fcaps.patch
missing comma...
Seeing the same error as in comment 9. It goes away when fixing the comma separation/concatenation thing. On a tangential note; since these "failures" complete their installations and portage later pretends they were successes, shouldn't the fix be accompanied by a rev-bump? I'm assuming having incorrect caps set on a file is less-than-desired, otherwise why would they be set in the first place? Thanks for fixing! |