Package Details: systemd-selinux 256.7-1

Git Clone URL: https://aur.archlinux.org/systemd-selinux.git (read-only, click to copy)
Package Base: systemd-selinux
Description: system and service manager with SELinux support
Upstream URL: https://www.github.com/systemd/systemd
Keywords: selinux
Licenses: CC0-1.0, GPL-2.0-or-later, LGPL-2.1-or-later, MIT-0
Groups: selinux
Conflicts: nss-myhostname, selinux-systemd, systemd, systemd-tools, udev
Provides: nss-myhostname, systemd, systemd-tools, udev
Submitter: Siosm
Maintainer: IooNag
Last Packager: IooNag
Votes: 18
Popularity: 0.001610
First Submitted: 2013-11-03 20:05 (UTC)
Last Updated: 2024-11-01 09:59 (UTC)

Required by (1526)

Sources (17)

Latest Comments

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

IooNag commented on 2020-05-22 18:56 (UTC)

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 https://github.com/archlinuxhardened/selinux is more appropriate.

NobodyDBG commented on 2020-05-22 12:49 (UTC)

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/libsystemd-shared-245.so -pthread -lrt /usr/lib/libseccomp.so /usr/lib/libselinux.so /usr/lib/libmount.so /usr/lib/libblkid.so -lpam /usr/lib/libaudit.so /usr/lib/libkmod.so -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 (UTC)

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 https://github.com/fishilico/home-files/blob/master/bin/find-broken-libdep

sorin-mihai commented on 2019-07-18 22:45 (UTC) (edited on 2019-07-18 22:54 (UTC) by sorin-mihai)

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: libip4tc.so.0: 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 https://archive.org/download/archlinux_pkg_iptables/iptables-1\: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 (UTC) (edited on 2019-05-12 17:55 (UTC) by yar)

Arch's systemd has already backported 2 patches to fix https://bugs.archlinux.org/task/62483 and I've submitted a pull request for you to do the same. Thanks! https://github.com/archlinuxhardened/selinux/pull/22

taro-yamada commented on 2019-02-07 14:58 (UTC)

@kvnbai

journalctl --vacuum-size=100M

may fix the problem.

IooNag commented on 2019-01-06 15:44 (UTC)

@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 (https://github.com/fishilico/home-files/blob/master/bin/makecleanpkg + https://github.com/archlinuxhardened/selinux/blob/master/build_cleanpkg.sh). Unfortunately it does not work with systemd package, cf. https://github.com/archlinuxhardened/selinux/blob/master/build_cleanpkg.sh#L137-L147 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 (UTC)

I highly recommend building with makechrootpkg https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_clean_chroot

kvnbai commented on 2019-01-05 19:43 (UTC)

@IooNag

The build only fails when using 1 CPU (using VM), giving my VM atleast 2 CPUs solves the issue. I'm not sure if this is a large issue, so I'll just leave a comment here:

Is your system up-to-date? Yes tested on the newest stable manjaro-i3 release. I updated the system before following the wiki.

Are you using an x86-64 CPU? Yes

Did you try building systemd-selinux in a freshly installed system? Yes

Does /home/test/.cache/yay/systemd-selinux/src/build/test-journal-flush exist, and if yes, does it show the same error when you run it directly? Yes it exists and it shows the same error when executed, the files that the script wish to create are also created in /tmp

Is SELinux enabled on your system? SELinux is disabled

Prep before isntalling SELinux: Removed mlocate because the AUR helper I use can only remove findutils while installing findutils-selinux

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