Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 14 Jun 2020 18:31:44 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 247261] mail/fetchmail: update to 6.4.8 to update many translations, and add new Serbian translation
Message-ID:  <bug-247261-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D247261

            Bug ID: 247261
           Summary: mail/fetchmail: update to 6.4.8 to update many
                    translations, and add new Serbian translation
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Keywords: buildisok, patch-ready
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: mandree@FreeBSD.org
                CC: chalpin@cs.wisc.edu
                CC: chalpin@cs.wisc.edu
             Flags: maintainer-feedback?(chalpin@cs.wisc.edu)
 Attachment #215555 maintainer-approval?(chalpin@cs.wisc.edu)
             Flags:
             Flags: merge-quarterly?

Created attachment 215555
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D215555&action=
=3Dedit
update fetchmail port to 6.4.8 (from 6.4.4)

Note that the 6.4.5 regression fix was irrelevant to supported FreeBSD
versions.
I intend to MFH this to 2020Q2 (unless this would only be committed after
maintainer timeout, then the hassle wouldn't make sense for three days befo=
re
July 1st)

These are the release notes for new releases:

---------------------------------------------------------------------------=
------
fetchmail-6.4.8 (released 2020-06-14, 27596 LoC):

## NEW TRANSLATION, with thanks to the translator:
* sr:    =D0=9C=D0=B8=D1=80=D0=BE=D1=81=D0=BB=D0=B0=D0=B2 =D0=9D=D0=B8=D0=
=BA=D0=BE=D0=BB=D0=B8=D1=9B (Miroslav Nikoli=C4=87) [Serbian]
- Sorry, this was missed earlier because my translation scripts did not
properly
  report new translations.
---------------------------------------------------------------------------=
------
fetchmail-6.4.7 (released 2020-06-14, 27596 LoC):

## TRANSLATION UPDATE, with thanks to the translator:
* sv:    G=C3=B6ran Uddeborg [Swedish]
---------------------------------------------------------------------------=
----
fetchmail-6.4.6 (released 2020-05-29, 27596 LoC):

## TRANSLATION UPDATE, with thanks to the translator:
* eo:    Felipe Castro [Esperanto]
---------------------------------------------------------------------------=
-----
fetchmail-6.4.5 (released 2020-05-07, 27596 LoC):

## 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.

## TRANSLATION UPDATES in reverse alphabetical order of language codes,
## with my thanks to the translators:
* zh_CN: Boyuan Yang [Chinese (simplified)]
* sv:    G=C3=B6ran Uddeborg [Swedish]
* sq:    Besnik Bleta [Albanian]
* pl:    Jakub Bogusz [Polish]
* ja:    Takeshi Hamasaki [Japanese]
* fr:    Fr=C3=A9d=C3=A9ric Marchal [French]
* cs:    Petr Pisar [Czech]
---------------------------------------------------------------------------=
-----

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-247261-7788>