Daniel J Walsh wrote:
On 01/31/2012 12:07 PM, Jerry James wrote:
After installing today's Rawhide updates on an x86_64 VM, I
started having troubles running programs. Nothing linked with
libselinux.so.1 could actually open that library; the programs were
getting EACCESS on the attempt. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/01/2012 12:49 PM, Kevin Kofler wrote:
Daniel J Walsh wrote:
Yes we have shipped a policy that requires the usrmove
functionality.
How many times do we have to tell you that you MUST build usrmove
stuff in the f17-usrmove build target, NOT
On Wed, Feb 1, 2012 at 14:16, Daniel J Walsh dwa...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
But as long as we live in the Rawhide/Non Rawhide world things are
going to be strange and mistakes are going to happen.
Why anyone is on Rawhide and not trying out usrmove
On 2012-02-01 15:16, Daniel J Walsh wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/01/2012 12:49 PM, Kevin Kofler wrote:
Daniel J Walsh wrote:
Yes we have shipped a policy that requires the usrmove
functionality.
How many times do we have to tell you that you MUST build usrmove
I'll note here a nice Help wanted...
If you have access to RHEL6 (or I suppose any of the binary compatible
variants) and some time:
rel-eng is looking for some quick regression testing of the rpm change
in https://bugzilla.redhat.com/show_bug.cgi?id=761000 to make sure it
doesn't break in any
After installing today's Rawhide updates on an x86_64 VM, I started
having troubles running programs. Nothing linked with libselinux.so.1
could actually open that library; the programs were getting EACCESS on
the attempt. I figured I needed to do a relabel, but since restorecon
is linked with
On Tue, 2012-01-31 at 14:09 -0500, Daniel J Walsh wrote:
On 01/31/2012 12:07 PM, Jerry James wrote:
After installing today's Rawhide updates on an x86_64 VM, I
started having troubles running programs. Nothing linked with
libselinux.so.1 could actually open that library; the programs were
On Tue, 2012-01-31 at 11:19 -0800, Adam Williamson wrote:
Yes we have shipped a policy that requires the usrmove functionality.
If you add
/lib64 /lib
to
/etc/selinux/targeted/contexts/files/file_contexts.subs_dist
Then run restorecon -R -v /lib64
It should fix
