Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#57936 - [zathura] add libseccomp as optional dependency

Attached to Project: Community Packages
Opened by valoq (valoq) - Saturday, 24 March 2018, 16:07 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 25 March 2018, 14:42 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

- libseccomp is missing as a optional dependency

- Upstream now provides SHA256 hashes for all zathura packages


This task depends upon

Closed by  Doug Newgard (Scimmia)
Sunday, 25 March 2018, 14:42 GMT
Reason for closing:  Not a bug
Comment by Doug Newgard (Scimmia) - Sunday, 25 March 2018, 03:51 GMT
Why?
Comment by valoq (valoq) - Sunday, 25 March 2018, 10:34 GMT
Sorry, I just realised this is not needed as long as the package is build without -Denable-seccomp=true .

Please note that once some more testing has been done, seccomp will be enabled by default and libseccomp will be needed as a dependency.

https://git.pwmt.org/pwmt/zathura/blob/master/README
Comment by loqs (loqs) - Sunday, 25 March 2018, 11:40 GMT
@valoq from the link you posted "libseccomp (optional, for sandbox support)"
As zathura is not built on arch with libseccomp present in the build environment and with the enable-seccomp option then zathura will not use libseccomp even if it is present on the system as run time.
If libseccomp becomes a required dependency then
seccomp = dependency('libseccomp', required: false) in meson.build should be changed to true by upstream and the build will fail without libseccomp.

Loading...