Your message dated Wed, 22 Feb 2017 14:48:52 +0000
with message-id <e1cgyds-0005es...@fasolo.debian.org>
and subject line Bug#854991: fixed in dnssec-trigger 0.13-6
has caused the Debian Bug report #854991,
regarding dnssec-triggerd: wrong path to dnssec-trigger-script (/usr/libexec vs 
/usr/lib)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
854991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dnssec-trigger
Version: 0.13-5
Severity: serious
File: /usr/sbin/dnssec-triggerd

I recently noticed this error in the systemd journal for dnssec-triggerd:

Feb 13 07:55:24 chianamo dnssec-triggerd[23003]: sh: 1: 
/usr/libexec/dnssec-trigger-script: not found
Feb 13 07:55:24 chianamo dnssec-triggerd[23003]: ok

Looks like the libexecdir was attempted to be set correctly but wasn't:

pabs@chianamo ~ $ dpkg -L dnssec-trigger  | xargs zgrep libexec
/usr/sbin/dnssec-triggerd:Binary file (standard input) matches
/usr/share/doc/dnssec-trigger/changelog.Debian.gz:  * Correctly set libexecdir 
to /usr/lib/dnssec-trigger to avoid patching
pabs@chianamo ~ $ strings /usr/sbin/dnssec-triggerd | grep libexec
/usr/libexec/dnssec-trigger-script --setup
/usr/libexec/dnssec-trigger-script --restore

-- System Information:
Debian Release: 9.0
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dnssec-trigger depends on:
ii  gir1.2-networkmanager-1.0  1.6.0-1
ii  init-system-helpers        1.47
ii  libc6                      2.24-9
ii  libgdk-pixbuf2.0-0         2.36.4-1
ii  libglib2.0-0               2.50.2-2
ii  libgtk2.0-0                2.24.31-2
ii  libldns2                   1.7.0-1
ii  libssl1.1                  1.1.0d-2
ii  python                     2.7.13-2
ii  python-gi                  3.22.0-2
ii  python-lockfile            1:0.12.2-2
ii  unbound                    1.6.0-2

dnssec-trigger recommends no packages.

dnssec-trigger suggests no packages.

-- debconf-show failed

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
--- Begin Message ---
Source: dnssec-trigger
Source-Version: 0.13-6

We believe that the bug you reported is fixed in the latest version of
dnssec-trigger, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 854...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Surý <ond...@debian.org> (supplier of updated dnssec-trigger package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 22 Feb 2017 15:11:05 +0100
Source: dnssec-trigger
Binary: dnssec-trigger
Architecture: source
Version: 0.13-6
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Packaging <pkg-dns-de...@lists.alioth.debian.org>
Changed-By: Ondřej Surý <ond...@debian.org>
Description:
 dnssec-trigger - reconfiguration tool to make DNSSEC work
Closes: 854991
Changes:
 dnssec-trigger (0.13-6) unstable; urgency=medium
 .
   * Unhardcode libexec dir in riggerd/reshook.c (Closes: #854991)
Checksums-Sha1:
 5dbac0ad3642fd9e1824bf02c9dc30c0e7ce3d9e 2254 dnssec-trigger_0.13-6.dsc
 8e6b0649aa0c9dded4dd939b232b026102f87ee4 11960 
dnssec-trigger_0.13-6.debian.tar.xz
 07919ae5d7e7250f83b163243d15845a126e1f98 9684 
dnssec-trigger_0.13-6_amd64.buildinfo
Checksums-Sha256:
 e1e03ae1037bf4e6cfbd3dd10db4ac8742771827452ad75424be9d7e0be61f24 2254 
dnssec-trigger_0.13-6.dsc
 6f7cd800bc7431dcc114de4fc962f52b0c39397fc6988e0d14e4f4848448c942 11960 
dnssec-trigger_0.13-6.debian.tar.xz
 25ce9219541f98c710a5e98fd2cfb80f4f7bce8da45889230ad08c401653c9a9 9684 
dnssec-trigger_0.13-6_amd64.buildinfo
Files:
 f12b4757e28604c2fb59b5f8ab5babbb 2254 net optional dnssec-trigger_0.13-6.dsc
 f09ba70aa5c2e6b7d934ad82bc170c43 11960 net optional 
dnssec-trigger_0.13-6.debian.tar.xz
 50beb614c8e0586ff4bd042083f83880 9684 net optional 
dnssec-trigger_0.13-6_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEEMLkz2A/OPZgaLTj7DJm3DvT8uwcFAlitnapfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDMw
QjkzM0Q4MEZDRTNEOTgxQTJEMzhGQjBDOTlCNzBFRjRGQ0JCMDcACgkQDJm3DvT8
uwdF7xAAmGyUOQ4su5hcUPFXKUZ56H09deOVRt6e1rRZlYc0rjtrA2PTTEC0+tj6
19Tbfzy/a6XJWiWK+ooFes9uoNcFJ5kAo5Yjs24Ahv/rU9FAj5y/Rch2wwbPH4sB
muuxZ9PyRagxrJVr2nWeCTcXureDgJnUHnS6xjTyZP9vKe3t+GrdrQcD5n4r59GV
a1dmawakNjtZQ/D0ryG83Qv064SRByT8DJP+3cuq8YQYvFxdTKOOa/bdehdDa1hW
SqqjU7tCGNJ1fILwIOEu/j5+IjF12VZbbTFbcyO1Tv5mpvdcCcs6EnBU1RXCqEAt
DZgb+/X4wMXZ0BoE5mrsuc+1nRPLYhX8s7IiQkWyoWnDB4q3cS4Stt93+mqOjHcy
GtZ+gtE2rSxBOYmqF9F+5AkW3qAOhMRZaT2azUtmkpzcJTz49lh5SnGCuxF8a1CD
XbuVI3GVgziMIs4yxjGDHPoc4sxpnhaRssV0CLMC3DAvuaqZgFtvPYzkLTjbEw8z
lrmt+99jV2mf0b00q6GLGiv0mE1sliU9Dyafcwqk1h1dnfiVhWlcmdn/FE1piFCV
riS5b27AjHExus6gMsjf5MN/2tRTghENt9La6BxpbdlzrENwuA/obDpfiyHt2uI5
u4GE6lLZXpwCOJXQNij+JAEzn+9mcP9LytQO9tJi8DHBOjz3xQM=
=i8o0
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to