The "obviously correct" fix in commit ab601b882b9d9d8248250111317615db1aa7b7c6
causes rpm --root installs to spit out errors that were not there before, eg
> error: setexecfilecon: (/usr/sbin/glibc_post_upgrade.x86_64) No such file or
> directory
15:bash-4.4.19-2.fc28 ################################# [ 94%]
16:libsepol-2.7-6.fc28 ################################# [100%]
error: setexecfilecon: (/bin/sh) No such file or directory
error: setexecfilecon: (/bin/sh) No such file or directory
error: setexecfilecon: (/bin/sh) No such file or directory
So setexecfilecon() has been routinely returning -1 but the buggy condition
previously masked this.
Our own code that does seemingly the exact same thing "manually" does not
exhibit this behavior on chroot installs. Whether its a bug in libselinux or
rpm, it needs investigating and fixing.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1077
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
