Package: dnssec-trigger
Version: 0.13~svn685-4
Severity: normal

Dear Maintainer,
I get the following message when installing dnssec-trigger :-

sudo aptitude install unbound dnssec-trigger -y

The following NEW packages will be installed:
  dnssec-trigger libldns1{a} libunbound2{a} unbound unbound-anchor{a}
0 packages upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/1,150 kB of archives. After unpacking 3,344 kB will be used.
Retrieving bug reports... Done
Parsing Found/Fixed information... Done

----
----

Setting up dnssec-trigger (0.13~svn685-4) ...
D000001: deferred_configure updating conffiles
setup in directory /etc/dnssec-trigger
generating dnssec_trigger_server.key
Generating RSA private key, 1536 bit long modulus
.....................................................++++
..........++++
e is 65537 (0x10001)
generating dnssec_trigger_control.key
Generating RSA private key, 1536 bit long modulus
...........................++++
.....................................................................................................................++++
e is 65537 (0x10001)
create dnssec_trigger_server.pem (self signed certificate)
create dnssec_trigger_control.pem (signed client certificate)
Signature ok
subject=/CN=dnssec-trigger-control
Getting CA Private Key
Setup success. Certificates created.

run this script again with -i to:
        - enable remote-control in unbound.conf
        - start unbound-control-setup
        - add root trust anchor to unbound.conf
if you have not done this already


The ---- were basically to say lot of messages in-between as I have
put aptitude in verbose mode.

My query is the last 5th line

"run this script again with -i to:"

which script is it talking about ?

Looking via dpkg -L dnssec-trigger shows this :-

/usr/lib/dnssec-trigger/dnssec-trigger-script

Looking via file it confirms that it's a python script :-

[$] file /usr/lib/dnssec-trigger/dnssec-trigger-script

/usr/lib/dnssec-trigger/dnssec-trigger-script: Python script, UTF-8
Unicode text executable

So guessing it's the same script that is being talked about. It would
make it much much better if the line could be changed to :-

"run dnssec-trigger-script script again with -i to :-

Please fix this if possible.

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (600, 'testing'), (500, 'testing-updates'), (1,
'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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  0.9.10.0-7
ii  init-system-helpers        1.22
ii  libc6                      2.19-17
ii  libgdk-pixbuf2.0-0         2.31.3-1
ii  libglib2.0-0               2.44.0-1
ii  libgtk2.0-0                2.24.25-3
ii  libldns1                   1.6.17-5+b1
ii  libssl1.0.0                1.0.1k-3
ii  python                     2.7.9-1
ii  python-gi                  3.14.0-1
ii  python-lockfile            1:0.8-2
ii  unbound                    1.4.22-3

dnssec-trigger recommends no packages.

dnssec-trigger suggests no packages.

-- no debconf information
-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8


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

Reply via email to