Bug#757320: Wrong dnssec-trigger-script path in /etc/NetworkManager/dispatcher.d/01-dnssec-trigger

2014-09-22 Thread Ralf Jung
Hi,

 The path to dnssec-trigger-script in the NetworkManager dispatcher hook
 is wrong. It seems that with NetworkManager 0.9.10.0-1, the shell script
 fallback fails, which means that DHCP-supplied DNS server notification
 does not work.

There are also some dependencies missing for this script:
gir1.2-networkmanager-1.0 and python-lockfile.
Also, upstream tells me that the script in this snapshot is quite
outdated by now and should be updated (which will also remove the
lockfile dependency).

Kind regards
Ralf


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#757320: Wrong dnssec-trigger-script path in /etc/NetworkManager/dispatcher.d/01-dnssec-trigger

2014-08-07 Thread Nicolas Dandrimont
Package: dnssec-trigger
Version: 0.13~svn685-1
Severity: important
Control: tags -1 patch

Dear maintainer,

The path to dnssec-trigger-script in the NetworkManager dispatcher hook
is wrong. It seems that with NetworkManager 0.9.10.0-1, the shell script
fallback fails, which means that DHCP-supplied DNS server notification
does not work.

Please find attached a patch that fixes the issue.

Cheers,
Nicolas Dandrimont

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages dnssec-trigger depends on:
ii  init-system-helpers  1.20
ii  libc62.19-7
ii  libgdk-pixbuf2.0-0   2.30.7-1
ii  libglib2.0-0 2.40.0-3
ii  libgtk2.0-0  2.24.24-1
ii  libldns1 1.6.17-5
ii  libssl1.0.0  1.0.1h-3
ii  python   2.7.8-1
ii  unbound  1.4.22-1

dnssec-trigger recommends no packages.

dnssec-trigger suggests no packages.

-- no debconf information
From d834d37f068a31c6ea93f71e7ee7e03a4ddb56a1 Mon Sep 17 00:00:00 2001
From: Nicolas Dandrimont nicolas.dandrim...@crans.org
Date: Thu, 7 Aug 2014 08:39:00 +0200
Subject: [PATCH] Fix path to dnssec-trigger-script in the NetworkManager hook

---
 debian/patches/debian-quirks.patch | 11 +++
 1 file changed, 11 insertions(+)

diff --git a/debian/patches/debian-quirks.patch b/debian/patches/debian-quirks.patch
index c81b084..9d890e0 100644
--- a/debian/patches/debian-quirks.patch
+++ b/debian/patches/debian-quirks.patch
@@ -1,5 +1,16 @@
 --- dnssec-trigger.orig/01-dnssec-trigger.in
 +++ dnssec-trigger/01-dnssec-trigger.in
+@@ -11,8 +11,8 @@ fi
+ 
+ # Exec the dnssec-trigger update script that uses NetworkManager API to gather
+ # all the necessary information.
+-if [ -x @libexecdir@/dnssec-trigger-script ]; then
+-exec @libexecdir@/dnssec-trigger-script --update
++if [ -x /usr/lib/dnssec-trigger/dnssec-trigger-script ]; then
++exec /usr/lib/dnssec-trigger/dnssec-trigger-script --update
+ fi
+ 
+ # When dnssec-trigger-script is absent or not executable, the original
 @@ -23,7 +23,7 @@ fi
  # set PATH correctly instead of absolute paths to binaries
  PATH=@sbindir@:@bindir@:/sbin:/usr/sbin:/bin:/usr/bin
-- 
2.1.0.rc1