diff options
author | Matthias Andree <matthias.andree@gmx.de> | 2020-05-04 11:13:36 +0200 |
---|---|---|
committer | Matthias Andree <matthias.andree@gmx.de> | 2020-05-04 11:15:14 +0200 |
commit | a0a6b190226dde33827e5508864c34c8bb73bb83 (patch) | |
tree | 19c237a5c0c4d707bc0560d41bf302c6ec6b51fd /NEWS | |
parent | 11ba27271f8e085b06c79b732cf92f88e492f487 (diff) | |
download | fetchmail-a0a6b190226dde33827e5508864c34c8bb73bb83.tar.gz fetchmail-a0a6b190226dde33827e5508864c34c8bb73bb83.tar.bz2 fetchmail-a0a6b190226dde33827e5508864c34c8bb73bb83.zip |
Release 6.4.5-rc1.
Initial tests done by David Hough, now formal release candidate for translators.
Diffstat (limited to 'NEWS')
-rw-r--r-- | NEWS | 22 |
1 files changed, 22 insertions, 0 deletions
@@ -65,6 +65,28 @@ removed from a 6.5.0 or newer release.) -------------------------------------------------------------------------------- +fetchmail-6.4.5 (unreleased): + +## REGRESSION FIX: +* fetchmail 6.4.0 and 6.4.1 changed the resolution of the home directory + in a way that requires SUSv4 semantics of realpath(), which leads to + 'Cannot find absolute path for... directory' error messages followed by aborts + on systems where realpath() follows strict SUSv2 semantics and returns + EINVAL if the 2nd argument is NULL. + + On such systems, for instance, Solaris 10, fetchmail requires PATH_MAX to be + defined, and will then work again. Regression reported by David Hough. + + On systems that neither provide auto-allocation semantics for realpath(), + nor PATH_MAX, fetchmail will print this error and abort. Such systems + are unsupported, see README. + +## CHANGES: +* Add a test program fm_realpath, and a t.realpath script, neither to be + installed. These will test resolution of the current working directory. + +-------------------------------------------------------------------------------- + fetchmail-6.4.4 (released 2020-04-26, 27530 LoC): ## UPDATED TRANSLATIONS - WITH THANKS TO THE TRANSLATOR: |