Pavel Raiskup

Doesn't accept relative include paths in ld.so.conf.

``` $ cat /etc/ld.so.conf include ld.so.conf.d/*.conf ``` (edit, that's actually Fedora 26, where we need to add '/usr/lib64' manually, that's not listed within ld.so.conf*)

> Does Fedora26 not include /usr/lib64 in any of the confs at all ? Nope, but I kind of "hoped" that we could add `/usr/lib64` into the list of standard...

> Is /usr/local/lib64 also a thing ? Definitely less important than `/usr/lib64`. Nothing is really installed (by system packages) under /usr/local on FHS distro. > This probably makes sense as...

Thank you for the report. Yes, I think only the first occurrence of ExclusiveArch is taken into account ATM.

Data backed-up here: https://download.copr.fedorainfracloud.org/archive/issues/copr-3163/

https://github.com/rpm-software-management/createrepo_c/issues/327

Today @Conan-Kudo reported that his projects in the `@asahi/*` group fail to build in fedora-40 chroots. E.g. the `[@asahi](https://copr.fedorainfracloud.org/groups/g/asahi/coprs/)/[mesa](https://copr.fedorainfracloud.org/coprs/g/asahi/mesa/) uses manual createrepo feature. ``` coprdb=# select id, result, action_type, data...

If nothing, we should at least add the "manual_createrepo=True" attribute to the action'đ `data`, and generate an empty repo.

I tried to check whether the service was restarted, ... positive: ``` [root@copr-be-dev ~][STG]# systemctl status copr-backend-action ● copr-backend-action.service - Copr Backend service, Action Dispatcher component Loaded: loaded (/usr/lib/systemd/system/copr-backend-action.service; disabled;...