Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 377503 - Failed to emerge sys-apps/policycoreutils-2.1.0
Summary: Failed to emerge sys-apps/policycoreutils-2.1.0
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Hardened (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: The Gentoo Linux Hardened Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-03 06:42 UTC by Dave
Modified: 2011-08-05 12:51 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dave 2011-08-03 06:42:36 UTC
sys-apps/policycoreutils-2.1.0 fails with 

!!! Couldn't download 'policycoreutils-extra-1.21.tar.bz2'. Aborting.
 * Fetch failed for 'sys-apps/policycoreutils-2.1.0', Log file:
 *  '/var/tmp/portage/sys-apps/policycoreutils-2.1.0/temp/build.log'
Comment 1 Anthony Basile gentoo-dev 2011-08-03 09:11:15 UTC
This is in the mirrors.  Test in about 4 hours.
Comment 2 Dave 2011-08-04 03:55:55 UTC
I've had to setenforce=0 before emerging because it failed:


 * Converting shebang in 'usr/bin/audit2allow-2.7'
sed: warning: failed to set default file creation context to system_u:object_r:portage_tmp_t: Permission denied * Converting shebang in 'usr/bin/chcat-2.7'
sed: warning: failed to set default file creation context to system_u:object_r:portage_tmp_t: Permission denied * Converting shebang in 'usr/bin/sepolgen-ifgen-2.7'
sed: warning: failed to set default file creation context to system_u:object_r:portage_tmp_t: Permission denied * Converting shebang in 'usr/sbin/semanage-2.7'
sed: warning: failed to set default file creation context to system_u:object_r:portage_tmp_t: Permission deniedcp: failed to set default file creation context to `unconfined_u:object_r:portage_tmp_t': Permission denied
cp: failed to set default file creation context to `unconfined_u:object_r:portage_tmp_t': Permission denied
cp: failed to set default file creation context to `unconfined_u:object_r:portage_tmp_t': Permission denied
cp: failed to set default file creation context to `system_u:object_r:portage_tmp_t': Permission denied
cp: failed to set default file creation context to `unconfined_u:object_r:portage_tmp_t': Permission denied
cp: failed to set default file creation context to `system_u:object_r:portage_tmp_t': Permission denied
cp: failed to set default file creation context to `unconfined_u:object_r:portage_tmp_t': Permission denied
cp: failed to set default file creation context to `system_u:object_r:portage_tmp_t': Permission denied
cp: failed to set default file creation context to `unconfined_u:object_r:portage_tmp_t': Permission denied
cp: failed to set default file creation context to `system_u:object_r:portage_tmp_t': Permission denied
cp: failed to set default file creation context to `system_u:object_r:portage_tmp_t': Permission denied
cp: failed to set default file creation context to `system_u:object_r:portage_tmp_t': Permission denied
cp: failed to set default file creation context to `unconfined_u:object_r:portage_tmp_t': Permission denied
cp: failed to set default file creation context to `system_u:object_r:portage_tmp_t': Permission denied
cp: failed to set default file creation context to `system_u:object_r:portage_tmp_t': Permission denied
cp: failed to set default file creation context to `unconfined_u:object_r:portage_tmp_t': Permission denied
cp: failed to restore the default file creation context: Permission denied
 * ERROR: sys-apps/policycoreutils-2.1.0 failed (install phase):
 *   Merging of intermediate installation image for Python ABI '2.7 into installation image failed
 * 
 * Call stack:
 *     ebuild.sh, line   56:  Called src_install
 *   environment, line 4784:  Called python_merge_intermediate_installation_images '/var/tmp/portage/sys-apps/policycoreutils-2.1.0/temp/images'
 *   environment, line 4144:  Called die
 * The specific snippet of code:
 *               cp -fr --preserve=all "${intermediate_installation_images_directory}/${PYTHON_ABI}/"* "${D}" || die "Merging of intermediate installation image for Python ABI '${PYTHON_ABI} into installation image failed";
 * 
 * If you need support, post the output of 'emerge --info =sys-apps/policycoreutils-2.1.0',
 * the complete build log and the output of 'emerge -pqv =sys-apps/policycoreutils-2.1.0'.
 * The complete build log is located at '/var/tmp/portage/sys-apps/policycoreutils-2.1.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/policycoreutils-2.1.0/temp/environment'.
 * S: '/var/tmp/portage/sys-apps/policycoreutils-2.1.0/work/policycoreutils-2.1.0'

>>> Failed to emerge sys-apps/policycoreutils-2.1.0, Log file:

>>>  '/var/tmp/portage/sys-apps/policycoreutils-2.1.0/temp/build.log'

 * Messages for package sys-apps/policycoreutils-2.1.0:

 * ERROR: sys-apps/policycoreutils-2.1.0 failed (install phase):
 *   Merging of intermediate installation image for Python ABI '2.7 into installation image failed
 * 
 * Call stack:
 *     ebuild.sh, line   56:  Called src_install
 *   environment, line 4784:  Called python_merge_intermediate_installation_images '/var/tmp/portage/sys-apps/policycoreutils-2.1.0/temp/images'
 *   environment, line 4144:  Called die
 * The specific snippet of code:
 *               cp -fr --preserve=all "${intermediate_installation_images_directory}/${PYTHON_ABI}/"* "${D}" || die "Merging of intermediate installation image for Python ABI '${PYTHON_ABI} into installation image failed";
 * 
 * If you need support, post the output of 'emerge --info =sys-apps/policycoreutils-2.1.0',
 * the complete build log and the output of 'emerge -pqv =sys-apps/policycoreutils-2.1.0'.
 * The complete build log is located at '/var/tmp/portage/sys-apps/policycoreutils-2.1.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/policycoreutils-2.1.0/temp/environment'.
 * S: '/var/tmp/portage/sys-apps/policycoreutils-2.1.0/work/policycoreutils-2.1.0'
Comment 3 Dave 2011-08-05 12:51:52 UTC
On another Gentoo based server I've had no problems with policycoreutils-2.1.0.

SELINUX=enforcing
SELINUXTYPE=strict

So it seems to have been my own misconfiguration.