ANNOUNCE: fetchmail 6.4.13 release candidate #1 is now available (lock file fixes)

--===============4129364554147407663==
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="UugvWAfsgieZRqgk"
Content-Disposition: inline


--UugvWAfsgieZRqgk
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Greetings,

Fetchmail's 6.4.13 release CANDIDATE is now available at the usual location,
<https://downloads.sourceforge.net/project/fetchmail/branch_6.4/>.

Please test it and report back. I'll send it off to the translation project=
 in parallel.

The source archive is available at:
<https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6=
=2E4.13.rc1.tar.xz>
<https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6=
=2E4.13.rc1.tar.lz>

Detached GnuPG signatures for the respective tarballs are at:
<https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6=
=2E4.13.rc1.tar.xz.asc>
<https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6=
=2E4.13.rc1.tar.lz.asc>

SHA256 hash values for the tarballs:
SHA256(fetchmail-6.4.13.rc1.tar.lz)=3D ff9c11c806570ae0f21f78c6e33a9ef434b2=
77454eb1b24043f73b774d579a35
SHA256(fetchmail-6.4.13.rc1.tar.xz)=3D fc74e83b71c2ad7129db288fe511d4e4f6de=
94cfcda189705cf61402cd811389

Here are the release notes:

---------------------------------------------------------------------------=
------
fetchmail-6.4.13 (work in progress):

# BUG FIXES:
* Errors about lock file (=3D pidfile) creation could be lost in daemon=20
  configurations (-d option, or set daemon) when using syslog. Now they are=
 also=20
  logged to syslog.  Found verifying a pidfile creation issue on 6.4.12 tha=
t was=20
  previously reported by Alex Hall of Automatic Distributors.
* If the lock file cannot be removed (no write permission on directory), try
  to truncate it, and if that fails, report error.
* If the pidfile was non-default, fetchmail -q or --quit would malfunction =
and
  claim no other fetchmail were running, because it did not read the=20
  configuration files or merge the command line options, thus it would look=
 for=20
  the PID in the wrong file.

# CHANGES:
* Lockfile (=3D pidfile) creation errors are now logged with filename and r=
eason.
---------------------------------------------------------------------------=
------

Happy fetches,
Matthias

--UugvWAfsgieZRqgk
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE3EplW9mTzUhx+oIQ5BKxVu/zhVoFAl+GLwUACgkQ5BKxVu/z
hVromxAAz8GjUXlzBUv/QfIdqCntUpE8vIWpdqAbzBBPdvZLFKZ/CYsLXi9qcOgg
AxAmQ537+RfV70AYBuyelRJ+gwawdF8tZubjXTDIuDMQWPoA98K23L0RbxRryYre
r7xs0AojN1VcEDmOgU8MD4GsaYGALNrgz/Kw4Plop+P5fAxfYfPuMLzFzlzWL8pm
XMgx2ptMbPDZ3ZhjOJvOcZgN3q+pPuQRHcpOYr5S9P7ou/hdkbe43j38hmXeGd4m
dH3IqlcPa1gxYT04BLn2VCnAsKjW3/9OUpozX6RpAcwDM6HGZA7mgs9tUzFaDNLb
EjNX1AtNtWSC7Asib8NqXqYHy/Krxck/siAC4MQNCy1VUcEjF6fzP7CVRswyETFm
3GVA7P6x62zx/OBxkmmBT8LlplOkibjPDnQa6q2aBUvzT0x0TVEZJL+OIvjQ7wpk
Yx7pdZ747Dr5/w9zDuobbVTDuAA3XTFTqeWFhLlK4G1dORYH7XTRsM1LzHnb3K76
Cx355al2PwGiPLj2bHYeCU1nLsX5wqnTqECGJ97OWePzb/s7dQ4ONm1yRwUL+Ybf
k2623cWuCPjPaPGSUKQOt17gLPpM+XFwoXa5+qRXZh9b+88k2+amU/+f55MtBj9i
XEVV9oBeMliHsxpWEtoqSROIuc9o5L7/HG99KW6SFLbdMOVdYAk=
=3l7d
-----END PGP SIGNATURE-----

--UugvWAfsgieZRqgk--


--===============4129364554147407663==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============4129364554147407663==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Fetchmail-announce mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fetchmail-announce

--===============4129364554147407663==--