Package: ntpsec
Version: 1.1.0+dfsg1-1
Followup-For: Bug #901439
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
As suggested, running:
dpkg-reconfigure ntpsec
resulted in the creation of symlinks:
/etc$ ls -l rc*d/*ntp
lrwxrwxrwx 1 root root 13 Jun 20 01:37 rc2.d/S03ntp -> ../init.d/ntp
lrwxrwxrwx 1 root root 13 Jun 20 01:37 rc3.d/S03ntp -> ../init.d/ntp
lrwxrwxrwx 1 root root 13 Jun 20 01:37 rc4.d/S03ntp -> ../init.d/ntp
lrwxrwxrwx 1 root root 13 Jun 20 01:37 rc5.d/S03ntp -> ../init.d/ntp
What appears to have happened is when I installed ntpsec and ntpsec-ntpdate,
I also selected in aptitude to purge the packages ntp and ntpdate.
The sequence of actions reported by aptitude was:
Performing actions...
(Reading database ... 613417 files and directories currently installed.)
Removing ntp (1:4.2.8p11+dfsg-1) ...
[ ok ] Stopping NTP server: ntpd.
Removing ntpdate (1:4.2.8p11+dfsg-1) ...
Removing sntp (1:4.2.8p11+dfsg-1) ...
Selecting previously unselected package python3-ntp.
(Reading database ... 613342 files and directories currently installed.)
Preparing to unpack .../python3-ntp_1.1.0+dfsg1-1_amd64.deb ...
Unpacking python3-ntp (1.1.0+dfsg1-1) ...
Selecting previously unselected package ntpsec.
Preparing to unpack .../ntpsec_1.1.0+dfsg1-1_amd64.deb ...
Unpacking ntpsec (1.1.0+dfsg1-1) ...
Selecting previously unselected package ntpsec-ntpdate.
Preparing to unpack .../ntpsec-ntpdate_1.1.0+dfsg1-1_amd64.deb ...
Unpacking ntpsec-ntpdate (1.1.0+dfsg1-1) ...
Setting up python3-ntp (1.1.0+dfsg1-1) ...
Setting up ntpsec-ntpdate (1.1.0+dfsg1-1) ...
Installing new version of config file /etc/network/if-up.d/ntpdate ...
Processing triggers for man-db (2.8.3-2) ...
Setting up ntpsec (1.1.0+dfsg1-1) ...
Installing new version of config file /etc/apparmor.d/usr.sbin.ntpd ...
Installing new version of config file /etc/default/ntp ...
Installing new version of config file /etc/init.d/ntp ...
Installing new version of config file /etc/ntp.conf ...
[....] Starting NTP server: ntpd06-20T01:49:19 ntpd[32431]: INIT: ntpd
ntpsec-1.1.0+419 2018-03-14T12:03:57-0700: Starting
06-20T01:49:19 ntpd[32431]: INIT: Command line: /usr/sbin/ntpd -p /run/ntpd.pid
-g -N -u 108:112
. ok
(Reading database ... 613404 files and directories currently installed.)
Purging configuration files for ntp (1:4.2.8p11+dfsg-1) ...
userdel: user ntp is currently used by process 32433
/usr/sbin/deluser: `/usr/sbin/userdel ntp' returned error code 8. Exiting.
Purging configuration files for ntpdate (1:4.2.8p11+dfsg-1) ...
Press Return to continue, 'q' followed by Return to quit.
This purging action apparently removed the symlinks, and I had to run
dpkg-reconfigure again to restore the symlinks.
I'm not sure how Debian is supposed to handle switching between two mutually
exclusive packages like ntp and ntpsec and selecting to purge the package
being removed. Maybe the package ntp wasn't aware of another package claiming
the symlinks when package ntp was being purged or should have called
dpkg-reconfigure ntpsec?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: buster/sid
APT prefers experimental
APT policy: (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.18.0-rc1+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE= (charmap=UTF-8), LANGUAGE=en_GB
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)
Versions of packages ntpsec depends on:
ii adduser 3.117
ii libc6 2.27-3
ii libcap2 1:2.25-1.2
ii libssl1.1 1.1.0h-4
ii lsb-base 9.20170808
ii netbase 5.4
ii python3 3.6.5-3
ii python3-ntp 1.1.0+dfsg1-1
ii tzdata 2018e-1
Versions of packages ntpsec recommends:
ii cron [cron-daemon] 3.0pl1-130
Versions of packages ntpsec suggests:
ii apparmor 2.12-4
pn ntpsec-doc <none>
pn ntpsec-ntpviz <none>
-- no debconf information
