Gentoo Archives: gentoo-hardened

From: Mike Edenfield <kutulu@××××××.org>
To: gentoo-hardened@l.g.o
Subject: [gentoo-hardened] SELinux failure during emerge: setfscreatecon() takes exactly 1 argument
Date: Fri, 18 Sep 2009 18:58:52
Message-Id: 4AB3D867.6060702@kutulu.org
1 For about the past two weeks I've been receiving the
2 following error on our SELinux-enabled web server, any time
3 I attempt to upgrade or install a package from portage.
4
5 File "/usr/lib/portage/pym/portage/_selinux.py", line 50,
6 in mkdir
7 selinux.setfscreatecon()
8 TypeError: setfscreatecon() takes exactly 1 argument (0 given)
9
10 In each case, if I re-run the emerge command, the package
11 installs successfully the second time, but portage complains
12 about file collisions during the final merge step. The
13 attached build log shows this condition: the previous
14 upgrade attempt failed during timezone-data. The log shows
15 the second upgrade attempt, where timezone-data installs
16 correctly but README.bz2 indicates a collision.
17
18 I have reinstalled portage, python-selinux, and libselinux
19 successfully (by disabling selinux in FEATURES) but the
20 problem persists. I have the most recent selinux userland
21 from portage (:
22
23 [I] dev-python/python-selinux (2.16-r2@09/17/2009)
24 [I] dev-python/sepolgen (1.0.17@08/03/2009)
25 [I] sys-libs/libselinux (2.0.85@09/17/2009)
26 [I] sys-libs/libsemanage (2.0.33-r1@09/18/2009)
27 [I] sys-libs/libsepol (2.0.37@08/04/2009)
28 [I] sys-apps/portage (2.2_rc40@09/17/2009)

Attachments

File name MIME type
setfscreatecon_failure.log text/plain

Replies