On Thursday, March 26, 2020 11:09:21 PM CET Jean-Marc Liger wrote:Le 21/03/2020 à 17:26, Jean-Marc Liger a écrit :Le 21/03/2020 à 16:57, Pavel Raiskup a écrit :On Saturday, March 21, 2020 12:08:52 AM CET Kevin Fenzi wrote:On Fri, Mar 20, 2020 at 06:35:08PM +0100, Jean-Marc Liger wrote:Le 20/03/2020 à 13:27, Pavel Raiskup a écrit :On Friday, March 20, 2020 12:30:06 PM CET Jean-Marc Liger wrote:I've had a look to the above issue and it's not the same, the failing build requireshttp://mirror.centos.org/altarch/7/sclo/aarch64/rh/devtoolset-6/ repo which hasn't been build yet. Anyway to bypass ?How it comes that it wasn't built yet? If it was not, we wouldn't have metadata pointing at the non-existing RPMs, or? PavelI agree it probably has been built, I have no way to investigate or help more, but the copy of this repo is missing.This may have been a EOL repo that was removed? https://lists.centos.org/pipermail/centos-devel/2020-March/036649.htmlThanks for the link! I'm still not sure, there must be something wrong. If the mirror(s) were correctly rsynced, there wouldn't be single moment in time when the metadata referenced non-existing files? Jean-Marc, do you have link to the build?I've suppressed it, but I've just tried to build my package again an the problem is over as there is no more link to old devtoolset-6 metadatas !Hi Pavel, This problem is back again, here is the link to the build : https://download.copr.fedorainfracloud.org/results/ligenix/enterprise-virtualization/epel-7-aarch64/01320592-glusterfs/Thanks for letting us know, I filled CentOS bug report: https://bugs.centos.org/view.php?id=17187 And perhaps we should invent some easy-to-tweak DNS mirror blacklist on builders (e.g. etc/hosts hacks). This is going to be discussed on Monday team meeting...
Hi,
The devtoolset-6 stack, non-existent in
sclo-rh repository for epel-7-x86_64 chroot, is still required, any
progress here ?
JM
PavelJMJMPavel