zathura 2026

[dkwo]

• I tested the changes in this PR: YES
• I built this PR locally for my native architecture, (aarch64-glibc)

The only thing I noticed is blurry text when scrolling PDFs, pwmt/zathura#864

cc maintainer @lemmi

[dogknowsnx]

Regarding girara: Upstream moved Gtk+-specific parts to zathura

Regarding musl: #57776 (comment)

[fanyx]

can be rebased on master, meson fix is merged.

[dkwo]

@dogknowsnx I believe girara soname was already taken care, and disabled seccomp on musl for now (issue upstream), since we already use landlock that should be fine. What do you think?
@fanyx Thanks, rebased.

[dogknowsnx]

girara builds fine w/o gtk+3-devel last time I tried, should probably be moved to zathura's makedepends?

EDIT (post-thumbs-up):

disabled seccomp on musl for now

Some thoughts: Not entirely sure, but personally I'd still prefer (temporarily) disabling tests (waiting for fix by upstream) over switching off a built-in security measure, given that the zathura-sandbox binary still runs fine on a native musl system (can't test myself) despite the one failing weston-based test - again, we currently don't even run tests for weston itself.

[dkwo]

@dogknowsnx Sure, I can do that. Note that the musl fix has been merged upstream, so it will be in the next release, and also that the landlock snadbox (imho better) is always enabled.

[dogknowsnx]

There don't seem to be any advantages of updating right now, imho. Personally I'm happy to keep using zathura-0.5.13_1 as long as the issues mentioned above aren't sorted out upstream.