On Fri, 2019-02-01 at 11:07 +0100, Miro Hrončok wrote: > On 01. 02. 19 11:01, Miro Hrončok wrote: > > On 31. 01. 19 11:43, Miro Hrončok wrote: > > > On 31. 01. 19 11:18, Miro Hrončok wrote: > > > > On 31. 01. 19 10:56, Adam Williamson wrote: > > > > > Just as a note, what's in the 'rawhide' repo right now differs quite a > > > > > lot from what's in the buildroot as we haven't had a successful compose > > > > > since 2019-01-21. This is for various reasons - most recently > > > > > libreoffice needed rebuilding for the poppler soname bump and did not > > > > > build successfully for nearly a week, and now lorax has a dependency > > > > > issue. > > > > > > > > Oh I was so happy that I managed to build libreoffice this night after it > > > > timeouted on arm yesterday, and now it's lorax :( > > > > > > Anyway: > > > > > > Successfully waited 8:31 for lorax-30.13-2.fc30 to appear in the f30-build repo > > > > > > If somebody has the powers to initiate a compose, please use them. > > > > Another DOMMED one. > > > > Do you have a tip where to look for the problem? > > > > Is this file the correct start point? > > > > https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20190131.n.1/logs/global/traceback.global.log > > > > > > That brings me to > > > > https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20190131.n.1/logs/armhfp/liveimage-Fedora-Xfce-armhfp-Rawhide-20190131.n.1.armhfp.log > > > > > > And that says "see root.log or appliance.log for more information" yet I'm not > > sure where to see those. > > Oh, on the Koji link from that log: > > Unable to create appliance : Failed to build transaction : > Problem: package abiword-1:3.0.2-13.fc29.armv7hl requires libabiword-3.0.so, > but none of the providers can be installed > - package abiword-1:3.0.2-13.fc29.armv7hl requires libabiword = > 1:3.0.2-13.fc29, but none of the providers can be installed > - conflicting requests > - nothing provides libwmflite-0.2.so.7 needed by > libabiword-1:3.0.2-13.fc29.armv7hl > - nothing provides libwmf-0.2.so.7 needed by libabiword-1:3.0.2-13.fc29.armv7hl It is usually easier to just look here: https://pagure.io/dusty/failed-composes/issues the tickets there are filed automatically by a script dusty wrote; they provide useful information on each failure, including usually a direct link to the relevant task. We also often do the debugging there too. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
