$ mock -r fedora-26-i386 init INFO: mock.py version 1.3.4 starting (python version = 3.5.3)... Start: init plugins INFO: selinux enabled Finish: init plugins Start: run Start: clean chroot Finish: clean chroot Start: chroot init INFO: calling preinit hooks INFO: enabled root cache INFO: enabled dnf cache Start: cleaning dnf metadata Finish: cleaning dnf metadata INFO: enabled HW Info plugin Mock Version: 1.3.4 INFO: Mock Version: 1.3.4 Start: dnf install Failed to synchronize cache for repo 'fedora', disabling. 100% [======================================================================] 1.2 MB/s | 442 kB 00:00 ETA Warning: Group 'buildsys-build' does not exist. Error: Nothing to do. ERROR: Command failed: # /usr/bin/dnf --installroot /var/lib/mock/fedora-26-i386/root/ --releasever 26 --disableplugin=local --setopt=deltarpm=false install @buildsys-build --setopt=tsflags=nocontexts Failed to synchronize cache for repo 'fedora', disabling. Warning: Group 'buildsys-build' does not exist. Error: Nothing to do.
Seems a temporary issue, switching from metalink to baseurl allow to workaround it
Odd. I dont see anything off hand wrong with the metalink.
@adrian do you see anything here?
Hmm, no idea. I just tried the mock command from above in Fedora 26 and it worked without any problem:
$ mock -r fedora-26-i386 init INFO: mock.py version 1.3.4 starting (python version = 3.6.0)...
The version is a bit newer but the metalink looks correct.
Looks like a temporary failure.. seems ok now
Yeah, not sure what was going on. Please do re-open or file a new ticket if you see this again...
:full_moon_with_face:
Metadata Update from @kevin: - Issue close_status updated to: Insufficient data - Issue status updated to: Closed (was: Open)
There was similar error with rawhide aarch64 today. @ignatenkobrain mentioned a possible bug in librepo where repomd.xml and the actual database files are downloaded from different mirrors. Assuming that a mirror could have one of the older alternates repomd.xml files but not all database files it tries the older database files on all mirrors which might have older or newer repomd.xml files with different databases. This is a possible explanation which would match the seen behaviour.