Your message dated Wed, 02 Aug 2006 03:48:47 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#380459: fixed in fetchmail 6.3.4-4
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: fetchmail
Version: 6.3.4-1
Severity: normal


I tried to awake the fetchmail process, obtaining this result:
---
 eddie:~# /etc/init.d/fetchmail awaken
 Awakening mail retrieval agent: fetchmaileddie:~#
---

First of all it isn't cosmetically pretty! :)
In second place seems "something weird is happening"(tm). I started
it with sh -x:
---
 [...]
 + echo -n 'Awakening mail retrieval agent: fetchmail'
 Awakening mail retrieval agent: fetchmail+ '[' -r 
/var/run/fetchmail/fetchmail.pid ']'
 + su -c /usr/bin/fetchmail fetchmail
 eddie:~#
---


Then I edited the script and removed error redirecting, changing
  su -c $DAEMON $USER <&- >/dev/null 2>&1
to
  su -c $DAEMON $USER
(redirecting stderr to /dev/null should be forbidden by law), and this
error was showed: "fetchmail: no mailservers have been specified", that
seems to be related with the absence of the command-line argument -f.

Infact, starting fetchmail by-hand with
  su fetchmail -c "fetchmail"
mutters about the same error, while using
  su fetchmail -c "fetchmail -f /etc/fetchmailrc"
works fine.

Because of the presence of a fetchmail process in background (so in the
awakening you can't start it with the same $OPTIONS), perhaps a good
solution may be using two variables, $OPTIONS and $AWAKENOPTIONS. The
latter should contain only "-f $CONFFILE" and --syslog (unless the user
specified "set no syslog", like you do for $OPTIONS).

regards,
Riccardo


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-2-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages fetchmail depends on:
ii  adduser                       3.87       Add and remove users and groups
ii  debianutils                   2.16.2     Miscellaneous utilities specific t
ii  gettext                       0.14.6-1   GNU Internationalization utilities
ii  libc6                         2.3.6-15   GNU C Library: Shared libraries
ii  libssl0.9.8                   0.9.8b-2   SSL shared libraries

Versions of packages fetchmail recommends:
ii  ca-certificates               20050804   Common CA Certificates PEM files

-- debconf information:
* fetchmail/initdefaultswarn:
* fetchmail/runasroot: false
* fetchmail/confwarn:
  fetchmail/fetchidswarn:
* fetchmail/systemwide: true


--- End Message ---
--- Begin Message ---
Source: fetchmail
Source-Version: 6.3.4-4

We believe that the bug you reported is fixed in the latest version of
fetchmail, which is due to be installed in the Debian FTP archive:

fetchmail_6.3.4-4.diff.gz
  to pool/main/f/fetchmail/fetchmail_6.3.4-4.diff.gz
fetchmail_6.3.4-4.dsc
  to pool/main/f/fetchmail/fetchmail_6.3.4-4.dsc
fetchmail_6.3.4-4_i386.deb
  to pool/main/f/fetchmail/fetchmail_6.3.4-4_i386.deb
fetchmailconf_6.3.4-4_all.deb
  to pool/main/f/fetchmail/fetchmailconf_6.3.4-4_all.deb



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.
Hector Garcia <[EMAIL PROTECTED]> (supplier of updated fetchmail 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: SHA1

Format: 1.7
Date: Tue,  1 Aug 2006 10:44:26 +0200
Source: fetchmail
Binary: fetchmailconf fetchmail
Architecture: source i386 all
Version: 6.3.4-4
Distribution: unstable
Urgency: low
Maintainer: Fetchmail Maintainers <[EMAIL PROTECTED]>
Changed-By: Hector Garcia <[EMAIL PROTECTED]>
Description: 
 fetchmail  - SSL enabled POP3, APOP, IMAP mail gatherer/forwarder
 fetchmailconf - fetchmail configurator
Closes: 376603 380459 380794
Changes: 
 fetchmail (6.3.4-4) unstable; urgency=low
 .
   [ Nico Golde ]
   * Fixed awakening bug in init script (Closes: #380459).
   * Fixed EOF handling, patch can be removed after fetchmail 6.3.5
     release (Closes: #376603).
   * Bumped Standards-Version.
 .
   [ Piotr Ozarowski ]
   * Updated for the new python policy (Closes: #380794).
   * Replaced /usr/bin/fetchmailconf shell script with symlink
       and thus removed 01.fetchmailconf patch.
 .
   [ Hector Garcia ]
   * Added bison to build-depends.
Files: 
 9771952c15be79c1154d9fc7a038012e 817 mail optional fetchmail_6.3.4-4.dsc
 93edd74363781d5f6457747077893f15 43060 mail optional fetchmail_6.3.4-4.diff.gz
 2231fcf8d1e22dd3639b89e331e4b926 59264 mail optional 
fetchmailconf_6.3.4-4_all.deb
 f7a836dd2b7917ab332bb4058c64c521 592898 mail optional 
fetchmail_6.3.4-4_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFE0GgsMwsDi2xjdG0RAsx3AKD3a6xKnGaWllZk4V3jIley/9cVOwCg8JI1
bexFtBnXfXhyaz++klPsaBw=
=xG2V
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to