On 2/12/22 11:54 AM, Steven A. Falco wrote:
I'm still having problems building - vtk-9.1.0-6.fc36 is present in the x86_64 chroot on copr, but it is not present in the ppc64le chroot as shown in the failure in [0]. Is there any way to tell why the ppc64le chroot hasn't picked up vtk-9.1.0-6.fc36? It looks like the build of vtk succeeded [1], and it looks like the compose of F36 succeeded [2]. Steve [0] https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/3476205/ [1] https://koji.fedoraproject.org/koji/buildinfo?buildID=1915642 [2] https://kojipkgs.fedoraproject.org/compose/branched/Fedora-36-20220212.n.0/
Alright - it is getting even more strange. On another (later) copr run [3], we have the fedora-36-x86_64 chroot failing because it got vtk-9.1.0-5.fc36.x86_64, while the fedora-36-ppc64le chroot managed to get vtk-9.1.0-6.fc36.ppc64le. That is exactly backwards from what happened on the earlier copr run described above. So while this is just a guess on my part, it is looking like copr is picking different mirrors at different times, and it is random as to whether one will get the -5 or -6 version of vtk. Is it just a question of waiting a day or two, or is something really wrong here? Steve [3] https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/3476752/ _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
