On 07/19/2017 08:49 AM, Peter Robinson wrote: >>> You worded it differently to that, it was a known problem, they were >>> having issues rebuilding due to the breakage in s390x, so it was >>> already in progress. >> >> Can you help explain to me what I did wrong? >> >> AFAIK I found a problem and opened a bug against the correct component. >> I had no prior knowledge of ongoing efforts mainly because they weren't >> announced anywhere (at least I can't find it anywhere) and I looked at >> previous bugs against qemu before filing this one. Maybe one exists, but >> I wasn't looking for the right text? > > "dnf repoquery --whatprovides libxenctrl.so.4.8" told me the problem > package was xen, looking in koji [1] showed that it was upgraded a few > days ago, then the combination of qemu build failures since [2] (see > build -4 and associated changelog) coupled with the fact we'd not had > a compose in a few days provided the remainder of the info. > > [1] https://koji.fedoraproject.org/koji/packageinfo?packageID=7 > [2] https://koji.fedoraproject.org/koji/packageinfo?packageID=3685 > I agree maybe I could have done more, but I maintain that I didn't do anything incorrect. It would be great if we actually notified when there are issues with rawhide (or any compose really) so many different people don't have to investigate it. Example. Oh crap compose X didn't build last night. I wonder what the problem is. Go to canonical location where discussion about compose X should happen and see if anyone added any notes there. Yes, I see dep issues around new version of xen and it's being worked on - great. Don't have to ask anyone or email anywhere. In Bodhi there is one place to go to look at discussion for a particular rpm (update) and if it is working or not. It would be great if we had something like this for pungi. Dusty _______________________________________________ cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
