Package Details: libselinux 3.7-1

Git Clone URL: https://aur.archlinux.org/libselinux.git (read-only, click to copy)
Package Base: libselinux
Description: SELinux library and simple utilities
Upstream URL: https://github.com/SELinuxProject/selinux
Keywords: selinux
Licenses: custom
Groups: selinux
Conflicts: selinux-usr-libselinux
Provides: libselinux.so, selinux-usr-libselinux
Submitter: Siosm
Maintainer: IooNag
Last Packager: IooNag
Votes: 131
Popularity: 0.164276
First Submitted: 2013-11-03 20:05 (UTC)
Last Updated: 2024-08-11 16:17 (UTC)

Dependencies (11)

Sources (3)

Latest Comments

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

IooNag commented on 2022-01-03 21:21 (UTC)

@tallero: It seems that python-selinux, Python package was created to work in Python virtualenv, in order to provide Python bindings to libselinux.so (according to "Pure-python selinux shim module for use in virtualenvs in order to avoid failure to load selinux in Ansible modules." in https://github.com/pycontribs/selinux/blob/321d66619ed59bec00a9dc6216ce417d7befec41/README.rst ). These bindings are provided system-wide by the AUR package selinux-python in the AUR, and I understand for a need of a shim module in virtualenvs. This is why python-selinux includes a "selinux" Python module. However the fact that this module is installed system-wide is strange.

Moreover I do not understand how Arch Linux's python-selinux is supposed to work system-wide: it is supposed to provides transparent Python bindings to libselinux... but require libselinux to be installed too (with its Python bindings). Therefore, in my humble opinion, instead of packaging python-selinux in community, the AUR packages libselinux and selinux-python should be migrated to community if some official packages start to depend on them.

Could you please contact python-selinux's package maintainers in order to understand how this package is supposed to be used on systems with SELinux?

tallero commented on 2022-01-03 20:04 (UTC) 

libselinux: /usr/lib/python3.10/site-packages/selinux/__init__.py exists in filesystem (owned by python-selinux)
libselinux: /usr/lib/python3.10/site-packages/selinux/__pycache__/__init__.cpython-310.pyc exists in filesystem (owned by python-selinux)

bred commented on 2020-03-03 08:37 (UTC) (edited on 2020-03-03 09:51 (UTC) by bred)

@IooNag Ok, thanks

But considering that pkgconf is not so frequently used, maybe is better if you add it in the makedepends.

IooNag commented on 2020-03-03 08:10 (UTC)

@bred Yes, pkgconf needs to be installed before building this package, as well as make, gcc (for a C compiler)... All these packages are in group base-devel, which is always required for AUR packages.

bred commented on 2020-03-03 07:49 (UTC)

@IooNag

It seems that the package "pkgconf" is a mandatory dependency for building "libselinux".

After the installation of "pkgconf" it has compiled correctly.

IooNag commented on 2020-03-02 21:07 (UTC)

@bred : What version of package pcre have you installed? What is the output of "pkg-config --libs libpcre" (this is the command which is used to normally insert "-lpcre" in the command line that failed)?

bred commented on 2020-03-02 13:11 (UTC) (edited on 2020-03-02 14:00 (UTC) by bred)

I've this error during the linking: (pcre is installed!)


cc -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -I../include -D_GNU_SOURCE -DDISABLE_RPM -DNO_ANDROID_BACKEND  -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -shared -o libselinux.so.1 avc.lo avc_internal.lo avc_sidtab.lo booleans.lo callbacks.lo canonicalize_context.lo checkAccess.lo check_context.lo checkreqprot.lo compute_av.lo compute_create.lo compute_member.lo compute_relabel.lo compute_user.lo context.lo deny_unknown.lo disable.lo enabled.lo fgetfilecon.lo freecon.lo freeconary.lo fsetfilecon.lo get_context_list.lo get_default_type.lo get_initial_context.lo getenforce.lo getfilecon.lo getpeercon.lo init.lo is_customizable_type.lo label.lo label_db.lo label_file.lo label_media.lo label_support.lo label_x.lo lgetfilecon.lo load_policy.lo lsetfilecon.lo mapping.lo matchmediacon.lo matchpathcon.lo policyvers.lo procattr.lo query_user_context.lo regex.lo reject_unknown.lo selinux_check_securetty_context.lo selinux_config.lo selinux_restorecon.lo sestatus.lo setenforce.lo setexecfilecon.lo setfilecon.lo setrans_client.lo seusers.lo sha1.lo stringrep.lo validatetrans.lo   -ldl -Wl,-soname,libselinux.so.1,-z,defs,-z,relro

/usr/bin/ld: regex.lo: in function `regex_version':
regex.c:(.text+0x12): undefined reference to `pcre_version'
/usr/bin/ld: regex.lo: in function `regex_writef':
regex.c:(.text+0x79): undefined reference to `pcre_fullinfo'
/usr/bin/ld: regex.c:(.text+0xf0): undefined reference to `pcre_fullinfo'
/usr/bin/ld: regex.lo: in function `regex_data_free':
regex.c:(.text+0x1eb): undefined reference to `pcre_free'
/usr/bin/ld: regex.c:(.text+0x1fc): undefined reference to `pcre_free_study'
/usr/bin/ld: regex.lo: in function `regex_prepare_data':
regex.c:(.text+0x26e): undefined reference to `pcre_compile'
/usr/bin/ld: regex.c:(.text+0x294): undefined reference to `pcre_study'
/usr/bin/ld: regex.lo: in function `regex_load_mmap':
regex.c:(.text+0x39c): undefined reference to `pcre_fullinfo'
/usr/bin/ld: regex.c:(.text+0x414): undefined reference to `pcre_fullinfo'
/usr/bin/ld: regex.lo: in function `regex_match':
regex.c:(.text+0x4bf): undefined reference to `pcre_exec'
/usr/bin/ld: regex.lo: in function `regex_cmp':
regex.c:(.text+0x53e): undefined reference to `pcre_fullinfo'
/usr/bin/ld: regex.c:(.text+0x558): undefined reference to `pcre_fullinfo'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:148: libselinux.so.1] Errore 1

tallero commented on 2020-02-17 00:39 (UTC) (edited on 2020-02-17 00:42 (UTC) by tallero)

@IooNag:

You are of course still free to work on package libselinux-python2 and backport bug fixes that could happen in libselinux's Python bindings.

I am not that interested, too. I just needed an easy-to-use tool and someone adviced system-config-users. It seemed natural to me to package it, even if arch is slowly deprecating all python2-* packages.

If someone will ever want to use it in the future (for whatever reason) now can do it easily (because PKGBUILDs won't be lost even when SELinux will end support).

I did this for screem, too.

IooNag commented on 2020-02-12 21:00 (UTC)

@tallero: it seems that system-config-users could be installed on RHEL/CentOS 7, but not on CentOS 8 according to https://unix.stackexchange.com/questions/547437/centos-8-system-config-users. Moreover this question suggests using Cockpit instead, which has already been packaged for Arch Linux (https://www.archlinux.org/packages/community/x86_64/cockpit/).

Anyway, if you want to fork/adopt system-config-users and maintain it on https://gitlab.com/tallero/system-config-users, that's nice. Nevertheless I do not want to maintain a libselinux-python2-v3.0 package because this version is not supported upstream (by SELinux developers) and the future releases of libselinux are likely to break Python 2 compatibility. This is a matter of personal choices in the way I define how I spend my time. You are of course still free to work on package libselinux-python2 and backport bug fixes that could happen in libselinux's Python bindings.

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