Hello community,

here is the log from the commit of package fetchmail for openSUSE:Factory 
checked in at 2012-09-23 17:04:25
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/fetchmail (Old)
 and      /work/SRC/openSUSE:Factory/.fetchmail.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "fetchmail", Maintainer is "[email protected]"

Changes:
--------
--- /work/SRC/openSUSE:Factory/fetchmail/fetchmail.changes      2012-07-04 
13:51:49.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.fetchmail.new/fetchmail.changes 2012-09-23 
17:04:27.000000000 +0200
@@ -1,0 +2,30 @@
+Tue Sep 11 09:09:21 UTC 2012 - [email protected]
+
+- update to 6.3.22
+  # SECURITY FIXES
+    * CVE-2012-3482 (bnc#775988)
+    * CVE-2011-3389
+  # BUG FIX
+    * The Server certificate: message in verbose mode now appears on stdout 
like the
+      remainder of the output. Reported by Henry Jensen, to fix Debian Bug 
#639807.
+    * The GSSAPI-related autoconf code now matches gssapi.c better, and uses
+      a different check to look for GSS_C_NT_HOSTBASED_SERVICE.
+      This fixes the GSSAPI-enabled build on NetBSD 6 Beta.
+  # CHANGES
+    * The security and errata notices fetchmail-{EN,SA}-20??-??.txt are now
+      under the more relaxed CC BY-ND 3.0 license (the noncommercial clause
+      was dropped). The Creative Commons address was updated.
+    * The Python-related Makefile.am parts were simplified to avoid an automake
+      1.11.X bug around noinst_PYTHON, Automake Bug #10995.
+    * Configuring fetchmail without SSL now triggers a configure warning,
+      and asks the user to consider running configure --with-ssl.
+  # WORKAROUNDS
+    * Some servers, notably Zimbra, return A1234 987 FETCH () in response to
+      a header request, in the face of message corruption.  fetchmail now 
treats
+      these as temporary errors. Report and Patch by Mikulas Patocka, Red Hat.
+    * Some servers, notably Microsoft Exchange, return "A0009 OK FETCH 
completed."
+      without any header in response to a header request for meeting reminder
+      messages (with a "meeting.ics" attachment). fetchmail now treats these as
+      transient errors.  Report by John Connett, Patch by Sunil Shetye.
+
+-------------------------------------------------------------------

Old:
----
  README-security.txt
  fetchmail-6.3.21-repacked.tar.bz2

New:
----
  fetchmail-6.3.22.tar.bz2

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ fetchmail.spec ++++++
--- /var/tmp/diff_new_pack.N7JNH4/_old  2012-09-23 17:04:28.000000000 +0200
+++ /var/tmp/diff_new_pack.N7JNH4/_new  2012-09-23 17:04:28.000000000 +0200
@@ -30,19 +30,19 @@
 %if 0%{?with_krb5}
 BuildRequires:  krb5-devel
 %endif
-Version:        6.3.21
+Version:        6.3.22
 Release:        0
 Summary:        Full-Featured POP and IMAP Mail Retrieval Daemon
 License:        GPL-2.0+
 Group:          Productivity/Networking/Email/Utilities
 Url:            http://fetchmail.berlios.de/
-# Always repack upstream tarball without fetchmail-{EN,SA}-*.txt
-# bnc#713698
-Source:         %{name}-%{version}-repacked.tar.bz2
+# The fetchmail-{EN,SA}-*.txt security advisories
+# were relicensed to CC BY-ND 3.0, so there's no need
+# to repack the tarball without them anymore (bnc#713698)
+Source:         %{name}-%{version}.tar.bz2
 Source1:        %{name}.init
 Source2:        %{name}.logrotate
 Source3:        sysconfig.%{name}
-Source4:        README-security.txt
 Patch0:         fetchmail-6.3.8-smtp_errors.patch
 PreReq:         %fillup_prereq
 PreReq:         %insserv_prereq
@@ -78,7 +78,7 @@
 %prep
 %setup -q -n %{name}-%{version}
 %patch0 -p1
-cp -a %{SOURCE1} %{SOURCE2} %{SOURCE3} %{SOURCE4} .
+cp -a %{SOURCE1} %{SOURCE2} %{SOURCE3} .
 
 %build
 %if 0%{?suse_version} > 1010

++++++ fetchmail-6.3.21-repacked.tar.bz2 -> fetchmail-6.3.22.tar.bz2 ++++++
++++ 34322 lines of diff (skipped)

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to