FS#56300 - [networkmanager] incorrect dnssec-trigger script path

Attached to Project: Arch Linux
Opened by hexchain (hexchain) - Saturday, 11 November 2017, 12:43 GMT
Last edited by Jan Alexander Steffens (heftig) - Sunday, 12 November 2017, 19:01 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
In the configure script of NetworkManager, the "--with-dnssec-trigger" option value should be the actual script path according to the source code[1], which is "/usr/lib/dnssec-trigger/dnssec-trigger-script". The file is provided by aur/dnssec-trigger, though, but the path is the same as in Debian package dnssec-trigger[2] (Fedora still has libexec even in Rawhide).

I am fully aware of the fact that AUR packages are not officially supported. But, since our NetworkManager build does not explicitly disable unbound support, maybe something can be done to make the experience more smooth, if no one wants to maintain dnssec-trigger in [community]?

Additional info:
* package version(s)
networkmanager 1.10.0-1

[1] https://github.com/NetworkManager/NetworkManager/commit/a07f1000bafedaebe2bfffbf631e4e1b75963811
[2] https://packages.debian.org/stretch/amd64/dnssec-trigger/filelist
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Sunday, 12 November 2017, 19:01 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in trunk; thanks.

Loading...