Skip to content

Conversation

@ldwgchen
Copy link

@ldwgchen ldwgchen commented Nov 21, 2025

Testing the changes

  • I tested the changes in this PR: briefly

Local build testing

  • I built this PR locally for my native architecture, (x86_64-glibc)
  • I built this PR locally for these architectures (crossbuilds):
    • armv6l
    • x86_64-musl

Notes: I'm terribly sorry for closing and reopening the PR instead of force pushing. It won't happen again.

arcan and fbpdf already do not build without the introduced changes. They should be fixed in separate PRs.

@dogknowsnx
Copy link
Contributor

Can you bump zathura-pdf-mupdf to 0.4.6 ?

@ldwgchen
Copy link
Author

ldwgchen commented Dec 1, 2025

Can you bump zathura-pdf-mupdf to 0.4.6 ?

Yes that should be easy. But should it be a separate PR? I'm not sure about the rules on this... (I'll do it here anyway)

@dogknowsnx
Copy link
Contributor

dogknowsnx commented Dec 1, 2025

Can you bump zathura-pdf-mupdf to 0.4.6 ?

Yes that should be easy. But should it be a separate PR? I'm not sure about the rules on this... (I'll do it here anyway)

In this case, you might just as well update zathura-pdf-mupdf instead of revbumping, it doesn't provide any shared objects and it (the updated version) requires mupdf 1.26 anyway.

@ldwgchen ldwgchen force-pushed the mupdf-1.26.11 branch 3 times, most recently from 543a3e5 to f1e8386 Compare December 2, 2025 04:19
@ldwgchen
Copy link
Author

ldwgchen commented Dec 2, 2025

Update on zathura-pdf-mupdf was briefly tested with zathura-0.5.13_1 (current version) and #57776 on x86_64-glibc.

@ldwgchen ldwgchen changed the title mupdf: update to 1.26.11 mupdf: update to 1.26.12 Dec 7, 2025
@ldwgchen ldwgchen closed this Dec 7, 2025
@ldwgchen ldwgchen deleted the mupdf-1.26.11 branch December 7, 2025 01:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants