zaptel-1.0.x (including -1.0.6) fails to emerge, due to errors related to context violations from what I can see. Someone with a bit more knowledge on the internals of selinux might be able to shed some more light on this... Reproducible: Always Steps to Reproduce: 1. emerge zaptel 2. 3. Actual Results: http://www.nightsys.net/zaptel-selinux-issues Expected Results: Successful emerge. http://www.nightsys.net/zaptel-selinux-issues
Nathan: Please stop setting the severity to blocker, just because an ebuild does not compile.
as this looks like its most likely an selinux related issue, reassigning... i would assume that the hardened herd could give more insight to this faster also :)
Stefan: please add the following 2 lines in all present and future zaptel ebuilds: # disable external SELinux labeling sed -i -e "s:\(.*restorecon.*\):#\1:" Makefile if you wish I can do that with the present ones, I just don't wanna play with strange ebuilds without being welcome to. the thing here was that portage handles all labeling needed by a selinux system and it shouldn't be handled by the Makefile Nathan: there is an ~x86 asterisk policy in the portage tree. I just grabbed it from the nsa cvs, so it's problably not working as it should on a gentoo. if you make it work (I don't have that funny hardware), please send a bug my way with a patch ;)
selinux line gets removed by -gentoo patch in zaptel-1.0.7
old bug cleanup, closing
