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!
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!
FS#53587 - [lldpd] Enhance systemd unit file
Attached to Project:
Community Packages
Opened by Tim (bastelfreak) - Thursday, 06 April 2017, 09:28 GMT
Last edited by Sébastien Luttringer (seblu) - Saturday, 08 July 2017, 11:07 GMT
Opened by Tim (bastelfreak) - Thursday, 06 April 2017, 09:28 GMT
Last edited by Sébastien Luttringer (seblu) - Saturday, 08 July 2017, 11:07 GMT
|
DetailsHi,
the shipped unit file differs from the upstream one: https://github.com/vincentbernat/lldpd/blob/master/src/daemon/lldpd.service.in It has a lot of security related settings (which are enabled if the systemd version matches). Should we drop the archlinux PKGBUILD and use the upstream one? |
This task depends upon
Closed by Sébastien Luttringer (seblu)
Saturday, 08 July 2017, 11:07 GMT
Reason for closing: Fixed
Additional comments about closing: lldpd 0.9.7-4
Saturday, 08 July 2017, 11:07 GMT
Reason for closing: Fixed
Additional comments about closing: lldpd 0.9.7-4
Comment by Jelle van der Waa (jelly) -
Thursday, 06 April 2017, 09:36 GMT
Yes, Arch should always follow upstream.
Comment by Sébastien Luttringer (seblu) -
Saturday, 08 April 2017, 18:05 GMT
Not always, when it makes sense, like in this br.
Comment by Sébastien Luttringer (seblu) -
Saturday, 08 April 2017, 18:17 GMT
I didn't see the auto enabling of systemd feature based on version. So we will have to keep a synced version or patching it.