Does copr cache mock roots? Can I clean the cache somehow?
New gdb build from Fedora requires Python 3.7, but I had 3.8 in the buildroot. I've deleted my 3.8 builds, so i can rebuild gdb --without python, but apparently Python 3.8 stays in the buildroot and I get --allowerasing errors when I try to build anything.
Error: Problem: package gdb-headless-8.3.50.20190319-2.fc31.x86_64 requires libpython3.7m.so.1.0()(64bit), but none of the providers can be installed - cannot install both python3-libs-3.8.0~a2-2.fc31.x86_64 and python3-libs-3.7.2-7.fc30.x86_64 - cannot install both python3-libs-3.7.2-7.fc30.x86_64 and python3-libs-3.8.0~a2-2.fc31.x86_64 - cannot install the best update candidate for package python3-libs-3.7.2-7.fc30.x86_64 - cannot install the best update candidate for package gdb-headless-8.3.50.20190319-2.fc31.x86_64 (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages)
https://copr.fedorainfracloud.org/coprs/g/python/python3.8/builds/
Maybe I left something undeleted, but it is hard to see what.
Thanks for help,
On 21. 03. 19 7:50, Miro Hrončok wrote:
Does copr cache mock roots? Can I clean the cache somehow?
New gdb build from Fedora requires Python 3.7, but I had 3.8 in the buildroot. I've deleted my 3.8 builds, so i can rebuild gdb --without python, but apparently Python 3.8 stays in the buildroot and I get --allowerasing errors when I try to build anything.
I think I found a workaround:
- rebuild gdb --without python in another copr - add that copr as external repo - continue as usual
However I'd still like to know if I forget to delete something, or if there's indeed a root cache that is not invalidated when I delete builds.
copr-devel@lists.fedorahosted.org