Package Details: systemd-sysvcompat-selinux 246.6-1

Git Clone URL: (read-only, click to copy)
Package Base: systemd-selinux
Description: sysvinit compat for systemd with SELinux support
Upstream URL:
Keywords: selinux
Licenses: GPL2
Groups: selinux
Conflicts: selinux-systemd-sysvcompat, systemd-sysvcompat, sysvinit
Provides: selinux-systemd-sysvcompat=246.6-1, systemd-sysvcompat=246.6-1
Submitter: Siosm
Maintainer: IooNag
Last Packager: IooNag
Votes: 16
Popularity: 0.187867
First Submitted: 2013-11-03 20:05
Last Updated: 2020-09-26 13:57

Required by (9)

Sources (20)

Latest Comments

1 2 3 4 Next › Last »

ZhangHua commented on 2020-07-05 11:18

I think I meet some problems. I am trying to upgrade systemd-selinux from 245.6-7 to 245.6-8. However, when I started building this package, I always get an error from ninja, it says failed to compile systemd-journal-remote@exe/src_journal-remote_journal-remote-main.c.o. This is github issue address: So is there anyone can help me? Thanks for your help. What's more, I also met a issiue that system cannot unmount /run/user/1000 when powering off, it results that system spends too much time on stopping. I am trying to upgrade systemd-selinux to try to solve this problem because I have googled this problem and it may be systemd's fault, but I find that I can't finish compiling new version...

NobodyDBG commented on 2020-05-29 20:12

IooNAg: "if you want help, please report error messages in English (you can override your locale using "export LANG=C" before running "makepkg", for example)." Thank you it does help :-)

IooNag commented on 2020-05-22 18:56

NobodyDBG: if you want help, please report error messages in English (you can override your locale using "export LANG=C" before running "makepkg", for example). Moreover for copying large error messages, opening an issue on is more appropriate.

NobodyDBG commented on 2020-05-22 12:49

I need your help:

Found ninja-1.10.0 at /usr/bin/ninja ninja: Entering directory `build' [1555/1921] Linking target test-load-fragment FAILED: test-load-fragment cc -o test-load-fragment 'test-load-fragment@exe/src_test_test-load-fragment.c.o' -flto -Wl,--as-needed -Wl,--no-undefined -pie -Wl,-z,relro -Wl,-z,now -fstack-protector -Wl,--gc-sections -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -Wl,--start-group src/core/libcore.a src/core/libcore-shared.a src/shared/ -pthread -lrt /usr/lib/ /usr/lib/ /usr/lib/ /usr/lib/ -lpam /usr/lib/ /usr/lib/ -Wl,--end-group '-Wl,-rpath,$ORIGIN/src/core:$ORIGIN/src/shared' -Wl,-rpath-link,/tmp/yaourt-tmp-kevin/aur-systemd-selinux/src/build/src/core -Wl,-rpath-link,/tmp/yaourt-tmp-kevin/aur-systemd-selinux/src/build/src/shared lto1: schwerwiegender Fehler: Bytecode-Strom in Datei »src/core/libcore.a«, mit einem älteren GCC-Compiler als 10.0 erzeugt Kompilierung beendet. lto-wrapper: schwerwiegender Fehler: /usr/bin/cc gab Ende-Status 1 zurück Kompilierung beendet. /usr/bin/ld: error: lto-wrapper failed collect2: Fehler: ld gab 1 als Ende-Status zurück [1564/1921] Linking target src/udev/scsi_id ninja: build stopped: subcommand failed. ==> FEHLER: Ein Fehler geschah in build(). Breche ab... ==> FEHLER:Makepkg konnte systemd-selinux nicht erstellen. ==> Erstellen von systemd-selinux neu starten?[j/N] ==> ----------------------------------------------- ==> n

IooNag commented on 2019-07-20 12:39

sorin-mihai: I have updated the package. For your information, when you update your system and a dependency of systemd gets updated, you need to check whether systemctl still works and whether "ldd /usr/lib/systemd/systemd" does not report any library with "=> not found". If there are issues there, rebuilding systemd-selinux should be enough in order to fix the broken library dependencies, like any package in the AUR that depends on libraries that are upgraded to a different ".so version".

In case it helps someone, I am using a script that works like Gentoo's revdep-rebuild tool in order to detect such breakage on my system. I have published it on

sorin-mihai commented on 2019-07-18 22:45

Just marked the package as out-of date

  • core/systemd is now 242.32-3
  • when trying to update iptables to 1:1.8.3-1 I got this error: /usr/bin/systemctl: error while loading shared libraries: cannot open shared object file: No such file or directory

As a result the rebuilt initramfs is unbootable. The only workaround I used so far is to keep iptables at 1:1.8.2-1 blacklisting it from upgrade in /etc/pacman.conf

Anyone that needs to recover from an unbootable system related to this, can get the previous iptables from\:1.8.2-1-x86_64.pkg.tar.xz and install it from a live usb in a mounted chroot. Usuall recovery I'd say, while in chroot just install the package and rebuild the initramfs with mkinitcpio

yar commented on 2019-05-12 17:55

Arch's systemd has already backported 2 patches to fix and I've submitted a pull request for you to do the same. Thanks!

taro-yamada commented on 2019-02-07 14:58


journalctl --vacuum-size=100M

may fix the problem.

IooNag commented on 2019-01-06 15:44

@kvnbai Does the issue also exist when you build the offical systemd package from source? This does not looks like something specific to modifications related to SELinux.

@yar: the last time I tried to use makechrootpkg, it required root privileged. Which is why I tried to use it with fakeroot+fakechroot and proot ( + Unfortunately it does not work with systemd package, cf. For information, this is the major bug preventing me to set up a "user package repository" with SELinux packages which would be compiled by an Continuous Integration system every time a package is built.

yar commented on 2019-01-05 19:51

I highly recommend building with makechrootpkg