On Tue, Sep 15, 2020 at 1:53 AM Pavel Raiskup <praiskup@xxxxxxxxxx> wrote: > > Hi, we ship epelplayground-8-x86_64.cfg file in mock-core-configs so users can > reproduce builds locally with mock. Initially the configuration worked, but it > has been failing for quite some time now. Dnf isn't able to --installroot: > > No matches found for the following disable plugin patterns: local, spacewalk > CentOS-8 - Base 12 MB/s | 2.2 MB 00:00 > CentOS-8 - AppStream 21 MB/s | 5.8 MB 00:00 > CentOS-8 - PowerTools 11 MB/s | 1.9 MB 00:00 > CentOS-8 - Extras 33 kB/s | 7.3 kB 00:00 > Extra Packages for Enterprise Linux 8 - Playgro 15 MB/s | 6.1 MB 00:00 > Error: > Problem: conflicting requests > - nothing provides fpc-srpm-macros needed by epel-rpm-macros-8-16.playground.noarch > (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) > > I'm not sure we miss something there, but it looks like the shipped chroot is > broken. The mock bug report [1], and fpc-srpm-macros report [2]. > > Local mock builds are done against CentOS repositories, so I'm not sure where to > report this problem, if here or to CentOS (but starting here as I believe that > fpc-srpm-macros should go to the playground repo). > > Also another question is whether we can fix the chroot, or not (dropping the > config file from mock-core-configs is an option, too). > > [1] https://github.com/rpm-software-management/mock/issues/620 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1875057 > > Pavel > I guess here is probably going to be the best place to start. EPEL Playground is in the middle of changing. It will no longer be a "stand alone" repository. It will be for only those packages that people are using to "play with" large changes to their packages. There will be no more automatic builds of all packages. Because of this, you will need to have the regular EPEL repository enabled in order to use the EPEL-Playground repository. We're right in the middle of this change, but fixing mock now is the best time to do it. It won't hurt anything to add the regular EPEL repository now, when doing the EPEL-Playground mock. Troy p.s. I'll put this in the bugzilla and the issue. _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
