Package: chrony
Version: 1.20-7
Severity: important

The latest release of the chrony .deb files try to send a mail to root
during configure to inform about the configuration of the package.  This
causes a number of problems:

   1. It fails if mailx is not installed (this happens in my case).

   2. It fails if there is (deliberately) no local MTA on the system
     (happened too in my case).

   3. It would misbehave if the MTA was not completely configured at the
     time, because both are being installed in a single run of dpkg or apt
     (this has happened to me for other packages in the past).

   4. It will misbehave if the MTA was not yet in an operational state even
     though the MTA package was technically configured (newly installed MTAs
     often need manual tuning of things like delivery of mail to root,
     relaying policies etc.)

I respectfully suggest that failure to send the mail message becomes
non-fatal, and that a debconf question (containing the same info as the mail
message) be asked first (to avoid the mail going somewhere inappropriate).

Something like:

   Chrony has disabled updating the RTC clock because ...
   
   And ...
   
   Should a copy of this message by mailed to root now?
      <Yes> <No>

Only if Yes is answered should chrony even try to look for or depend on
mailx (and maybe also delay sending until postinst).


Friendly

Jakob

      

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10jbj3.2.8
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)

Versions of packages chrony depends on:
ii  libc6                       2.3.2.ds1-21 GNU C Library: Shared libraries an
ii  libncurses5                 5.4-4        Shared libraries for terminal hand
ii  libreadline4                4.3-15       GNU readline and history libraries

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to