On Thu, 2020-08-13 at 17:10 -0700, Adam Williamson wrote: > A new build of libreport was done for all releases today by mfabik: > > https://koji.fedoraproject.org/koji/buildinfo?buildID=1592551 > https://koji.fedoraproject.org/koji/buildinfo?buildID=1592550 > https://koji.fedoraproject.org/koji/buildinfo?buildID=1592524 > https://koji.fedoraproject.org/koji/buildinfo?buildID=1592531 > > This build changes the soname of libreport from libreport.so.0 to > libreport.so.1 (and indeed does introduce several API and ABI changes). > > It was sent out as a 'stable' update for F31 and F32 (despite the > soname bump). None of libreport's dependencies - notably including abrt > - have been rebuilt for any release, AFAIK. > > This means abrt is uninstallable in F33 and Rawhide build roots at > present and probably will break subsequent F33 and Rawhide composes > because there are probably release-blocking images with abrt in them. I > have filed negative karma on the F31 and F32 updates, which failed > openQA testing due to this issue. > > It seems a new release of abrt has been made upstream, but at least one > commit *after* that release looks necessary for the latest libreport. > Additionally my first attempt to build the new release failed because > the tarball was missing a file: > https://github.com/abrt/abrt/issues/1519 > I am continuing to try and get a successful abrt build, but if we can't > manage at least that, we will need to untag this build for F33 and > Rawhide. Follow up: couldn't get an abrt build to fly. It appears that the spec file is lying about the source tarball locations. It points to the github archive, but the tarball that's in dist-git for 2.14.2 is clearly *not* the one you get from the github archive: [adamw@adam abrt (master %)]$ spectool -g abrt.spec Downloading: https://github.com/abrt/abrt/archive/2.14.2/abrt-2.14.2.tar.gz [adamw@adam abrt (master %)]$ sha256sum abrt-2.14.2.tar.gz df9ae2e649319ceffa64a301d946c6cfc6e8c7156566ec783fb6bf3c7c8c8249 abrt-2.14.2.tar.gz [adamw@adam abrt (master %)]$ rm -f abrt-2.14.2.tar.gz [adamw@adam abrt (master %)]$ fedpkg srpm Downloading abrt-2.14.2.tar.gz [adamw@adam abrt (master %)]$ sha256sum abrt-2.14.2.tar.gz 735b97f6e6ae5af431aa68abd39c185f6de6afcbfe29453d26d696eeab24c0e4 abrt-2.14.2.tar.gz 'spectool -g' downloads the tarball from wherever the spec file claims it is from, 'fedpkg srpm' command downloads the tarball from dist-git; as you can see, the two are not the same. The one from github is just a github auto-generated source tree dump, without the autogen.sh script run on it; the one from dist-git is a "real" release tarball, which clearly did have autogen.sh run on it, but I can find no indication anywhere of where such "real" release tarballs can actually be downloaded, hence nowhere to get one for 2.14.3. It seems they used to be published on fedorahosted.org, but that is shut down now, and I can't find any other location mentioned anywhere. If I use the github tarball and try to run `autoreconf -i -f` on it I get a weirdly broken configure which has just a '.' command in the middle of the comments at the top, and doesn't work. No idea why that happens. Anyway, since I can't get abrt to build, mboddu has untagged libreport 2.14.0 from F33 and Rawhide for now. They can be retagged once someone sorts this mess out. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ 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
