Package Details: libselinux 3.0-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: http://userspace.selinuxproject.org
Keywords: selinux
Licenses: custom
Groups: selinux
Conflicts: selinux-usr-libselinux
Provides: selinux-usr-libselinux=3.0-1
Submitter: Siosm
Maintainer: IooNag
Last Packager: IooNag
Votes: 108
Popularity: 1.28
First Submitted: 2013-11-03 20:05
Last Updated: 2019-12-13 19:59

Latest Comments

1 2 3 4 5 6 Next › Last »

tallero commented on 2020-02-17 00:39

@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

@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.

tallero commented on 2020-02-12 17:56

@IooNag: I agree with you. In any case libselinux-python2 packages just bindings and until the tool has not been replaced/ported to pygobject (if ever) it could simply stabilize on 3.0. This was packaged because of this question. Can't find the original git repo, only tarballs, check this.

IooNag commented on 2020-02-12 07:46

tallero : is system-config-users maintained? The upstream of this project (Red Hat) seems to no longer maintain it (and the RPM seems not to exist for "recent" releases such as CentOS 8 or Fedora 31 on https://rpmfind.net/linux/rpm2html/search.php?query=system-config-users).

If system-config-users is no longer maintained upstream, I do not want to spend time to support libselinux-python2, for the sake of using old software for which bugs will never be fixed upstream.

tallero commented on 2020-02-11 22:17

@IooNag: I know of Python 2.x EOL; the library (same tar of this package) can still produce 2.x bindings. The software that needs it is system-config-users, the users/groups GUI manager included in Red Hat/CentOS 7.x.

I just noticed gnome-system-tools.

IooNag commented on 2020-02-11 19:41

tallero: Python 2 is no longer supported by SELinux userspace tools and libraries, since commit https://github.com/SELinuxProject/selinux/commit/214cb61d539f75e5290928cb7bba5b2646632d0b that is included in release 3.0. This is why I removed Python 2 library from libselinux package.

What software are you using that requires Python 2's bindings of libselinux? This software needs be updated to Python 3 compatibility anyway, as Python 2 is no longer updated "even if someone finds a security problem in it" (cf. https://www.python.org/doc/sunset-python-2/).

tallero commented on 2020-02-11 18:09

I forked the package to build and install only python 2.x bindings in libselinux-python2. Could you add the option to build them into this one so that I can drop the newborn depedency?

IooNag commented on 2020-01-12 16:34

paperfolder: As far as I understand, this warning appears for every package that provides a Python library. If you know of a way to bytecode-compile Python scripts without introducing the full path of the scripts in the resulting .pyc files, I will gladly modify the PKGBUILD accordingly.

paperfolder commented on 2020-01-10 15:59

makepkg returns a warning that the built package contains a reference to $pkgdir - is this a problem during compiling? (archwiki says that this error means the literal string $pkgdir is contained in these files)

==> WARNING: Package contains reference to $pkgdir
usr/lib/python3.8/site-packages/selinux/__pycache__/__init__.cpython-38.opt-1.pyc
usr/lib/python3.8/site-packages/selinux/__pycache__/__init__.cpython-38.pyc

xuanwo commented on 2019-11-22 05:37

Please bump a pkgrel for python 3.8 rebuild~