On Tue, Apr 28, 2020 at 09:22:56PM -0700, Michel Alexandre Salim wrote: > My epel8 build for python-extras succeeded just fine (using python-testtools > from a build override as a dependency - > https://bodhi.fedoraproject.org/overrides/python-testtools-2.4.0-3.el8), but > the epel8-playground build claims python-testtools is not available: > > epel8: > https://koji.fedoraproject.org/koji/buildinfo?buildID=1499241 > > epel8-playground: > https://koji.fedoraproject.org/koji/taskinfo?taskID=43889481 > > DEBUG util.py:600: No matching package to install: 'python3-testtools' > DEBUG util.py:600: Not all dependencies satisfied > DEBUG util.py:600: Error: Some packages could not be found. > > Does the playground setup not take overrides into account? > playground is an independent build target and thus overrides in epel8 and epel8-playground are independent. But you don't need to create overrides in epel8-playground because builds there appears in a build root automatically on next repository regeneration. However, your problem is not in overrides. Your problem is that python-testtools package has never been successfully built for epel8.playground: https://koji.fedoraproject.org/koji/packageinfo?packageID=11850 That's probably because of Carl George <carl@george.computer> deleted the package.cfg configuration from epel8 branch to mirror the builds into epel8-buildroot: commit dd46fcc88a92241e2aa776208cf7ef0dddbab541 Author: Carl George <carl@george.computer> Date: Fri Apr 24 01:06:33 2020 -0500 Revert ""Adding package.cfg file"" This reverts commit 6a8c5775eb802cc8acfb93dfbe7e00d8e92a24a3. -- Petr
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ 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
