Summary: | sys-process/psmisc-22.20 fails to build on selinux systems | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Amadeusz Sławiński <amade> |
Component: | SELinux | Assignee: | SE Linux Bugs <selinux> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | base-system, stsander |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://sourceforge.net/p/psmisc/code/ci/89fa40f0a55096a62809e852244d7db3f445b0cd/ | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build log
security_context_t scontext upstream's patch |
Description
Amadeusz Sławiński
2012-10-05 17:51:31 UTC
Created attachment 325738 [details]
build log
Created attachment 325760 [details, diff]
security_context_t scontext
I have the same problem.
This reported to upstream bug tracking system at sourceforge yet? I think most invocations towards scontext there can be changed to NULL. They're mostly referenced when no process exists or cannot be queried and the application creates a psmisc-process-structure (PROC) with unknown name ("?"). If it is for viewing purposes, it'll eventually hit out_string() which I believe will happily ignore a NULL (in the way that it exists gracefully without displaying any cruft). You shouldn't take my word on it though - a patch to validate is always welcome ;-) Created attachment 325930 [details, diff]
upstream's patch
emerges fine here after including upstreams patch from Jory. should be all set now in the tree; thanks for the report! Commit message: Add fix from upstream for building on selinux systems http://sources.gentoo.org/sys-process/psmisc/files/psmisc-22.20-selinux.patch?rev=1.1 http://sources.gentoo.org/sys-process/psmisc/psmisc-22.20.ebuild?r1=1.1&r2=1.2 |