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#69287 - [xlockmore] pkgbuild improvements

Attached to Project: Community Packages
Opened by . (bugwranglerwrangler) - Monday, 11 January 2021, 11:15 GMT
Last edited by Levente Polyak (anthraxx) - Monday, 11 January 2021, 11:44 GMT
Task Type Support Request
Category Packages
Status Assigned
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

1) use https in source=() and url=, sillycycle.com is https-enabled

2) use sha512sums as that is also provided upstream:
https://sillycycle.com/xlock/xlockmore-5.66.tar.xz.sha512

3) please take a look and fix the distro LDFLAGS usage of those 2 compilation targets as seen via checksec:
xlockmore W: ELF file ('usr/bin/xlock') lacks FULL RELRO, check LDFLAGS.
xlockmore W: ELF file ('usr/bin/xmlock') lacks FULL RELRO, check LDFLAGS.

4) it looks like we do not need to override DLAGENTS, it seems to work without
This task depends upon

Comment by Levente Polyak (anthraxx) - Monday, 11 January 2021, 11:37 GMT
xlockmore W: ELF file ('usr/bin/xlock') lacks FULL RELRO, check LDFLAGS.
xlockmore W: ELF file ('usr/bin/xmlock') lacks FULL RELRO, check LDFLAGS.

1) please take a look and fix the distro LDFLAGS usage of those 2 compilation targets.

2) to me it looks like we also do not need to override DLAGENTS, it works without

Loading...