Your message dated Thu, 17 Dec 2015 18:46:22 +0000
with message-id <[email protected]>
and subject line Bug#785208: fixed in adjtimex 1.29-7
has caused the Debian Bug report #785208,
regarding adjtimex postinst adjusts clock
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 [email protected]
immediately.)


-- 
785208: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785208
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: adjtimex
Version: 1.29-3
Severity: normal

The postinst script for the adjtimex package insists on running
adjtimex to perform some clock adjustment.  This is silly.  At the time
the package is installed or upgraded, the system is already running,
quite likely with the clock already well regulated (especially if this
was an upgrade).  In my case, I'm regulating the clock with ntpd, so
adjtimex should never be automatically run outside the boot sequence.
The postinst script should not be performing any clock adjustment.

It seems that, as with ntpdate in Bug#714997, the package is conflating
the desire to install a tool with the desire to use it in a particular
way.  adjtimex is useful for much more than just the automatic adjustment
that the postinst script contemplates.  I use it mainly in read-only
mode to watch what in fine detail what ntpd and the kernel are doing
with the clock.

-zefram

--- End Message ---
--- Begin Message ---
Source: adjtimex
Source-Version: 1.29-7

We believe that the bug you reported is fixed in the latest version of
adjtimex, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Roger Shimizu <[email protected]> (supplier of updated adjtimex 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 [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 17 Dec 2015 01:38:08 +0900
Source: adjtimex
Binary: adjtimex
Architecture: source
Version: 1.29-7
Distribution: unstable
Urgency: medium
Maintainer: Roger Shimizu <[email protected]>
Changed-By: Roger Shimizu <[email protected]>
Description:
 adjtimex   - kernel time variables configuration utility
Closes: 688933 724929 785208
Changes:
 adjtimex (1.29-7) unstable; urgency=medium
 .
   * remove the wrong debian/dirs line in changelog of previous version 1.29-6
   * debian/patches:
       - Replace patch 03 with the one by Bjarni I. Gislason, which also
         minimizes the time of lock over "/dev/rtc" (Closes: #724929).
       - Fix potential uninitialized memory accessing
         (thanks peppe <[email protected]>, Closes: #688933).
       - Avoid a few gcc warnings
   * debian/copyright: Add copyright for newly added patch
   * debian/adjtimexconfig:
       - Move tmp file during executing from /etc to /tmp.
       - Code clean up.
   * debian/templates + debian/config + debian/po + debian/NEWS:
       - Remove the debconf whether to start adjtimex on startup, which now
         depends on the existence of /etc/default/adjtimex file. By default,
         there's no /etc/default/adjtimex, which is generated by running:
         adjtimexconfig.
       - adjtimexconfig is still a choice in defconf, but change to false by
         default because it takes 70 seconds to excute on install/upgrade.
   * debian/postinst:
       - Refrain from running adjtimexconfig on configure, which is triggered by
         each install/upgrade
       - Refrain from starting adjtimex service on configure (Closes: #785208).
       - Code clean up.
   * debian/postrm:
       - Code clean up.
   * debian/adjtimex.init + debian/adjtimex.service: Start adjtimex service
       on startup only if config file /etc/default/adjtimex is ready.
   * debian/adjtimexconfig.8: Update man page
Checksums-Sha1:
 1c4020f9e3cbe40e2c3de7c2ef3614f4850a5f8d 1842 adjtimex_1.29-7.dsc
 30ac3a940f33bcc24b8bbc321dbc2c34f3a0f8e1 27736 adjtimex_1.29-7.debian.tar.xz
Checksums-Sha256:
 deb94b028d51151f9cea8368277ea6a94dcc2800891d4d7a616713d958af0e00 1842 
adjtimex_1.29-7.dsc
 c2276c0d4de6e6226033aa27041a013d4c60a331bab1f81c2b70ab49cc358329 27736 
adjtimex_1.29-7.debian.tar.xz
Files:
 b2301038b8be9b53050e592b46a0508f 1842 admin optional adjtimex_1.29-7.dsc
 ebfcbd045132c289d1ea728115a91d15 27736 admin optional 
adjtimex_1.29-7.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJWcvezAAoJEEsEP825REVAb9UP/RVxb4fkzRDRA71T8Fc7iCRc
mKXPtOivIiKK7hLxpXoGYx8EF6LBAlMI7qEeIN9yVf8xoxpDwvut6rCU1r1XEIhv
rQ00PcLSr+zk01893tAgQWTCmHrJbRqlk2iLGe/LGz3Jqz8CVqymaOxcR31DssCG
narAp7eTjHK7MqPCHycS2OOvQX7LNY5Vn7CFpspgh0rc9Wgz/SYF0cZa+o9/6yvZ
sY3aMbO0IfecFnyWQwa7Yr93cL2jYN7Oos6IFpDns2I5KgRrcve4hx9V/2OrcLk+
AyNEiz4MvfF2GNSJcRy4d2IPOsQVd04bBil5w51TEFoXZr2GqjEL4mHVDr8ZdH4D
9KsVWyiBuqNqGj09DfFvAnQrVb576t7LBczkO6nhuptGJXF3z7DdGQZU/0/m5MM8
MA1/aX3ewn7N3aie4soxP0TU8A6tw6oal627XTuI+PRYUW/3ncjEtsHT9DC5YE9G
FR/10LeRqMRyneSxYdmioMKSul8HUZsF8z6xOWXLbmKFh4D9UCBgXrLDkd2YEo+1
bDo365b1fvmqSm2Pq5J6E2LM0ffpnJfOHBaXvtoKlCDuwccmUESJEogpdnD+5upq
hzf3OvZUOipIrxzgXESh4WjD2yjj+gLR2as44dN8r5G5pc3hfea1V9sJDgEnUt12
P61SzNZuWddLWTfSeLQu
=e38Y
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to