Am Fr., 1. März 2024 um 07:55 Uhr schrieb Ralf Corsépius <rc040203@xxxxxxxxxx>: > > Hi, > > I intend to update gumbo-parser to 0.12.1 in rawhide. > This comes along with an soname bump libgumbo to libgumbo.so.2 > > This requires a rebuilt of several dependent packages, AFAICT: > claws-mail > litehtml > mupdf > perl-HTML-Gumbo > python3-PyMuPDF > qpdfview > zathura-pdf-mupdf > > I'll try to rebuild these packages on side-tag f41-build-side-84865 > (Please, bear with me, I haven't used side-tags, before. I couldn't find > any usable docs on how to use them) > > Preliminary tests indicate, something unrelated to libgumbo.so.* has > changed with these packages (Probably mupdf), causing gpdfview to FTBFS > and dependency changes in rawhide. Interesting. I wasn't aware of that dependency - I guess I have to re-run detection more often. Speaking of - do we have a policy about this? This is not about blaming, but how do we ensure that everyone is aware of new dependencies? Frequent re-runs to detect them or announcements the other way round? I switched mupdf from the old static build (which required many side-tag rebuilds) to a shared rebuild which will reduce dependency rebuilds in the future (and follows upstream's choice for their dependent package). I coordinated this with all dependent packages that I was aware of. qpdfview.spec will need some changes and will most probably lose the direct dependency on gumbo, tesseract etc. I'll look into that today, or over the weekend at the latest. In particular, qpdfview would not have needed a rebuild against gumbo etc if it had been built against mupdf shared already. And no, side-tags don't hurt, they are fun :) Only caveat: permissions, i.e. who can build into which side-tags. I ended up with commit rights to all mupdf dependencies at that time. That's a none-issue for a pp, of course. Michael -- _______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
