Am 01.03.24 um 09:34 schrieb Michael J Gruber:
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
This was the list of packages depending on gumbo for f39.
In rawhide, for reasons, I don't know, python3-PyMuPDF and
python3-PyMuPDF do not seem to depend on gumbo, anymore.
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.
The version of mupdf in rawhide seems to have dropped libmupdf-third,
which seems to be the origin of qpdfview's FTBFS.
I don't know, if this change is intentional or happened by accident.
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.
Give me a couple of hours - I am working on this right now.
AFAICS, the only problem qpdfview has is mupdf-third.
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.
I don't know - I am a proven-packager and have almost universal
permissions ;-)
Ralf
--
_______________________________________________
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
