Hello community,
here is the log from the commit of package getmail for openSUSE:Factory checked in at 2019-11-04 17:15:33
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/getmail (Old)
and /work/SRC/openSUSE:Factory/.getmail.new.2990 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "getmail"
Mon Nov 4 17:15:33 2019 rev:28 rq:745026 version:5.14
Changes:
--------
--- /work/SRC/openSUSE:Factory/getmail/getmail.changes 2019-03-05 12:26:24.612830729 +0100
+++ /work/SRC/openSUSE:Factory/.getmail.new.2990/getmail.changes 2019-11-04 17:15:46.904862084 +0100
@@ -1,0 +2,8 @@
+Sun Oct 27 12:00:00 UTC 2019 - cunix@mail.de
+
+- Update to 5.14
+ * Remove socket setblocking() calls which should be no longer
+ needed, and which may have caused hangup.
+ * Correct version number string in error message.
+
+-------------------------------------------------------------------
Old:
----
getmail-5.13.tar.gz
New:
----
getmail-5.14.tar.gz
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ getmail.spec ++++++
--- /var/tmp/diff_new_pack.lMssFB/_old 2019-11-04 17:15:47.460862678 +0100
+++ /var/tmp/diff_new_pack.lMssFB/_new 2019-11-04 17:15:47.464862683 +0100
@@ -17,7 +17,7 @@
Name: getmail
-Version: 5.13
+Version: 5.14
Release: 0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
Url: http://pyropus.ca/software/getmail/
++++++ _service ++++++
--- /var/tmp/diff_new_pack.lMssFB/_old 2019-11-04 17:15:47.500862721 +0100
+++ /var/tmp/diff_new_pack.lMssFB/_new 2019-11-04 17:15:47.504862725 +0100
@@ -1,7 +1,7 @@
<services>
<service name="verify_file" mode="localonly">
<param name="verifier">sha256</param>
- <param name="checksum">04d52f6475f09e9f99b4e3d2f1d2eb967a68b67f09af2a6a5151857f060b0a9d</param>
- <param name="file">getmail-5.13.tar.gz</param>
+ <param name="checksum">f3a99fe74564237d12ca8d4582e113c067c9205b5ab640f72b4e8447606a99c1</param>
+ <param name="file">getmail-5.14.tar.gz</param>
</service>
</services>
++++++ getmail-5.13.tar.gz -> getmail-5.14.tar.gz ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/getmail-5.13/PKG-INFO new/getmail-5.14/PKG-INFO
--- old/getmail-5.13/PKG-INFO 2019-02-23 04:18:43.000000000 +0100
+++ new/getmail-5.14/PKG-INFO 2019-08-19 17:51:32.000000000 +0200
@@ -1,6 +1,6 @@
Metadata-Version: 1.1
Name: getmail
-Version: 5.13
+Version: 5.14
Summary: a mail retrieval, sorting, and delivering system
Home-page: http://pyropus.ca/software/getmail/
Author: Charles Cazabon
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/getmail-5.13/docs/CHANGELOG new/getmail-5.14/docs/CHANGELOG
--- old/getmail-5.13/docs/CHANGELOG 2019-02-23 04:18:36.000000000 +0100
+++ new/getmail-5.14/docs/CHANGELOG 2019-08-19 17:51:18.000000000 +0200
@@ -1,3 +1,10 @@
+Version 5.14
+19 August 2019
+ -remove socket setblocking() calls which should be no longer needed,
+ and which may have caused hangups. Thanks: Viacheslav Chimishuk.
+ -correct version number string in error message. Thanks: Piet van
+ Oostrum.
+
Version 5.13
22 February 2019
-second attempt at fixing SNI change with Python < 2.7. Thanks: "Cimbal".
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/getmail-5.13/docs/faq.html new/getmail-5.14/docs/faq.html
--- old/getmail-5.13/docs/faq.html 2019-02-23 04:18:42.000000000 +0100
+++ new/getmail-5.14/docs/faq.html 2019-08-19 17:51:30.000000000 +0200
@@ -1271,10 +1271,19 @@
<p>
getmail has no problems running multiple instances in parallel, though you
shouldn't attempt to use the same getmail rc file from two different
- instances at the same time. If you need to prevent two instances of getmail
- from running simultaneously, use any standard Unix method of providing a
- mutex for this purpose. One example would be to run getmail under a
- program like
+ instances at the same time; it will probably cause getmail to deliver duplicate
+ copies of messages, "forget" that it has seen particular messages before,
+ and other similar problems.
+</p>
+<p>
+ In particular, if you're running getmail from a crontab, you <strong>must</strong> do
+ something to prevent cron from starting getmail if the previous invocation is still
+ running.
+</p>
+<p>
+ If you need to prevent two instances of getmail from running simultaneously, use
+ any standard Unix method of providing a mutex for this purpose. One example would
+ be to run getmail under a program like
<span class="file">setlock</span>
(part of the
<a href="http://cr.yp.to/daemontools.html"><span class="file">daemontools</span></a>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/getmail-5.13/docs/faq.txt new/getmail-5.14/docs/faq.txt
--- old/getmail-5.13/docs/faq.txt 2019-02-23 04:18:42.000000000 +0100
+++ new/getmail-5.14/docs/faq.txt 2019-08-19 17:51:31.000000000 +0200
@@ -868,12 +868,19 @@
getmail has no problems running multiple instances in parallel, though
you shouldn't attempt to use the same getmail rc file from two
- different instances at the same time. If you need to prevent two
- instances of getmail from running simultaneously, use any standard Unix
- method of providing a mutex for this purpose. One example would be to
- run getmail under a program like setlock (part of the daemontools
- package). Change your script or crontab file to invoke getmail like
- this:
+ different instances at the same time; it will probably cause getmail to
+ deliver duplicate copies of messages, "forget" that it has seen
+ particular messages before, and other similar problems.
+
+ In particular, if you're running getmail from a crontab, you must do
+ something to prevent cron from starting getmail if the previous
+ invocation is still running.
+
+ If you need to prevent two instances of getmail from running
+ simultaneously, use any standard Unix method of providing a mutex for
+ this purpose. One example would be to run getmail under a program like
+ setlock (part of the daemontools package). Change your script or
+ crontab file to invoke getmail like this:
/path/to/setlock -n /path/to/lockfile /path/to/getmail [getmail options]
There are other programs that provide functionality similar to setlock.
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/getmail-5.13/getmail.spec new/getmail-5.14/getmail.spec
--- old/getmail-5.13/getmail.spec 2019-02-23 04:18:42.000000000 +0100
+++ new/getmail-5.14/getmail.spec 2019-08-19 17:51:31.000000000 +0200
@@ -2,7 +2,7 @@
Summary: POP3 mail retriever with reliable Maildir delivery
Name: getmail
-Version: 5.13
+Version: 5.14
Release: 1
License: GPL
Group: Applications/Internet
@@ -52,6 +52,9 @@
%{python_sitelib}/getmailcore/
%changelog
+* Mon Aug 19 2019 Charles Cazabon