Bug 1807254
Summary: | RFE: allow allow/deny-lists for packages from broken external repos | ||
---|---|---|---|
Product: | [Community] Copr | Reporter: | aressem |
Component: | backend | Assignee: | Copr Team <copr-team> |
Status: | CLOSED UPSTREAM | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | praiskup, thrnciar |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-04-03 14:15:54 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
aressem
2020-02-25 22:17:06 UTC
Hello, thank you for reporting this bug. We will look at it and inform you ASAP. Have a nice day, Tomas Hi, I have been investigating this a bit more. We have an additional repository added for the Software Collections: http://mirror.centos.org/centos/7/sclo/$basearch/rh/ What seems to have changed is that this repository is enabled when installing yum as part of setting up the chroot. We require this repository to be added because we have dependencies on packages from the Software Collections. Another issue is that even with the Software Collections enabled, I can not understand why an installation of yum (one of the first steps in setting up the chroot) should pull in devtoolset-3-elfutils* packages. Best regards, Arnstein The repo is broken, see this mock hack: https://github.com/rpm-software-management/mock/commit/fd78b04112ec95164c8118ace4a7925b093ec99e We add the sclo repository ourselves, in mock-core-configs package. But we only allow packages from developer toolset by: `includepkgs=devtoolset*` So you are basically re-adding the problem we hacked-around. This so far only broke `use_bootstrap` option. Don't you want to disable it in your project? Thanks. I did try to remove the sclo repository we provided and the build broke on installing rh-maven35. But this is explained if you provide the repo and only include 'devtoolset*' packages. This would actually have worked if you allowed 'rh*' packages as well. However, I have now disabled the 'use_bootstrap' option and it seems to be able to progress with the build. Thanks for helping out, Arnstein > However, I have now disabled the 'use_bootstrap' option and it seems to be able to progress with the build.
Thanks for confirmation.
I'm not going to close this because it still is an valid use-case, and we should
make bootstrap work in such situation:
* re-add the sclo repositories with broken 'libelf' provides
* build something which depends on libelf
* see that wrong libelf is installed
This is known problem, but the fix in the CentOS repo is not going to happen
unfortunately. So we should be able to work-around such problems in copr project/chroot
configuration.
The bugs related to Copr build system are now migrated to the default Copr team tracker: https://github.com/fedora-copr/copr/issues/2615 |