mupdf: update to 1.27.0

[ldwgchen]

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):
  • x86_64-musl
  • aarch64

Renaming the branch automatically closed my previous PR #57974 which initially updated mupdf to 1.26.11.

[dogknowsnx]

You don't have to rename the branch every time you update the PR

[ahesford]

Please ping the template maintainer when you update a package.

@cinerea0

[dogknowsnx]

There's a new release (1.27.0) - if you do the update, could you try w/o zathura-pdf-mupdf?

[ldwgchen]

There's a new release (1.27.0) - if you do the update, could you try w/o zathura-pdf-mupdf?

Sure. Is this because you intend to update zathura-pdf-mupdf in #57776?

[dogknowsnx]

Sure. Is this because you intend to update zathura-pdf-mupdf in #57776?

Yes, because it needs to be rebuilt against a new girara release

[ahesford]

Why are you revbumping these packages?

[ldwgchen]

Why are you revbumping these packages?

I misunderstood the part about revbump in the contributing guide. These commits are dropped now.

[dogknowsnx]

Maybe also adjust the title (and checks will be enabled eventually)

[leahneukirchen]

@ahesford dependencies need to be revbumped since mupdf is linked statically.

[ahesford]

Is that also the case for the zathura package?

[leahneukirchen]

@ahesford only for zathura-pdf-mupdf i think?

[ahesford]

@ahesford only for zathura-pdf-mupdf i think?

In that case, all of the revbumps should be restored, including zathura-pdf-mupdf.

@dogknowsnx please do not advise contributors to remove revbumps from PRs when you are working on independent updates. Each pull request must be self-sufficient and not introduce breakage or interdependencies between pull requests.

[dogknowsnx]

@ahesford only for zathura-pdf-mupdf i think?

In that case, all of the revbumps should be restored, including zathura-pdf-mupdf.

@dogknowsnx please do not advise contributors to remove revbumps from PRs when you are working on independent updates. Each pull request must be self-sufficient and not introduce breakage or interdependencies between pull requests.

Well, sorry, but I'm still learning myself..

[ldwgchen]

Why are you revbumping these packages?

I misunderstood the part about revbump in the contributing guide. These commits are dropped now.

To clarify, I initially applied revbumps because of the comment in the second line of the template.

[leahneukirchen]

I don't understand why you removed depends= on mupdf-devel and added the stuff manually to the other templates?

[ldwgchen]

I don't understand why you removed depends= on mupdf-devel and added the stuff manually to the other templates?

I thought that it'd be better to have the other packages explicitly including jbig2dec-devel as a make dependency, as the fulfilment of that build requirement is independent of mupdf itself and of its use since all third party libraries are statically linked to via libmupdf-third.a.

The other two dependencies of mupdf-devel I removed are likely dependencies of other packages in makedepends. I didn't add them explicitly because I found that jbig2dec-devel was the only dependency that'd be missing.

I can revert these changes if they're inappropriate or unnecessary.

[leahneukirchen]

That's not true, libmupdf.a links against unresolved symbols of jbig_* etc. The former way was correct.