Package Details: setools 4.4.0-1

Git Clone URL: (read-only, click to copy)
Package Base: setools
Description: Policy analysis tools for SELinux
Upstream URL:
Keywords: selinux
Licenses: GPL, LGPL
Groups: selinux
Conflicts: selinux-setools
Provides: selinux-setools=4.4.0-1
Submitter: Siosm
Maintainer: IooNag
Last Packager: IooNag
Votes: 20
Popularity: 0.001218
First Submitted: 2013-11-03 20:05
Last Updated: 2021-07-03 14:43

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

farmerdave commented on 2013-08-18 03:13

Does this actually depend on selinux-refpolicy-src? Because according to all the current PKGBUILDs
selinux-usr-policycoreutils depends on selinux-setools
selinux-setools depends on selinux-refpolicy-src
selinux-refpolicy-src depends on selinux-usr-policycoreutils.

This does successfully build without specifying "depends=('selinux-refpolicy-src')

rd1381 commented on 2013-07-25 03:22

in PKGBUILD ,there is an error.
it should be swig>=2.0.4 instead of swig=2.0.4

Draadmachine commented on 2013-07-24 17:22

If you try to install selinux-setools via Yaourt it goes in regression because the packages are dependencies of each other. A possible fix is to remove the dependency selinux-usr-policycoreutils>=2.1.10 from the PKGBUILD of this package.

Nicky726 commented on 2013-07-20 17:21

So I finally got to update this...

hi117 commented on 2013-06-10 19:07

apol requires bwidget to run.

Anonymous comment on 2013-04-28 00:07

Also, for those trying to compile: you must downgrade SWIG to 2.0.4-3. The latest versions of SWIG end up causing the selinux-setools compile to eat itself.

Nicky726 commented on 2013-04-20 19:22

Thank you for your feedback. I'll try to incorporate it into the PKGBUILD, but unfortunately, I am very busy lately.

Anonymous comment on 2013-04-20 17:41

The makefile for libqpol is looking for but the file doesn't exist. It's referenced on line 442 of the libqpol/swig/java/Makefile.

Nicky726 commented on 2013-02-23 16:04

I can't get over qpol_wrap.c build error. Both with 3.3.7 and 3.3.8. Fedora doesn't fix it in any of its patches in current version, so I guess it may be due to something being newer in Arch.

Nicky726 commented on 2013-02-11 19:51

Yes, this will need some work, it is on my TODO list...