[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#942075: marked as done (buster-pu: package cyrus-imapd/3.0.8-6+deb10u1)

Your message dated Sat, 16 Nov 2019 10:08:47 +0000
with message-id <83c9ffab6f08361485f70dda4733a7a24aeec09b.camel@adam-barratt.org.uk>
and subject line Closing bugs for 10.2 point release fixes
has caused the Debian Bug report #942075,
regarding buster-pu: package cyrus-imapd/3.0.8-6+deb10u1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
942075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942075
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian.org@packages.debian.org
Usertags: pu

Hi all,

cyrus-imapd ≤ 3.0.8 has a RC bug: it may loss data during upgrade from
stretch to buster. The fix is very simple, then I think it is low risky
to upgrade it in next Buster point release.

Cheers,
Xavier

diff --git a/debian/changelog b/debian/changelog
index 8e0033c..ecc4273 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+cyrus-imapd (3.0.8-6+deb10u1) buster; urgency=medium
+
+  * Fix data loss (Closes: #933163)
+
+ -- Xavier Guimard <yadd@debian.org>  Wed, 09 Oct 2019 22:38:07 +0200
+
 cyrus-imapd (3.0.8-6) unstable; urgency=medium
 
   [ Anthony Prades ]
diff --git a/debian/patches/0024-dont-skip-records-with-modseq-0.patch b/debian/patches/0024-dont-skip-records-with-modseq-0.patch
new file mode 100644
index 0000000..d284089
--- /dev/null
+++ b/debian/patches/0024-dont-skip-records-with-modseq-0.patch
@@ -0,0 +1,20 @@
+Description: mailbox: don't skip records with modseq == 0
+Author: Bron Gondwana <brong@fastmailteam.com>
+Origin: upstream, https://github.com/cyrusimap/cyrus-imapd/commit/02840505
+Bug: https://github.com/cyrusimap/cyrus-imapd/issues/2839
+Bug-Debian: https://bugs.debian.org/933163
+Forwarded: not-needed
+Reviewed-By: Xavier Guimard <yadd@debian.org>
+Last-Update: 2019-10-09
+
+--- a/imap/mailbox.c
++++ b/imap/mailbox.c
+@@ -6513,7 +6513,7 @@
+         const struct index_record *record = msg_record(iter->msg);
+         if (!record->uid) continue; /* can happen on damaged mailboxes */
+         if ((record->system_flags & iter->skipflags)) continue;
+-        if (record->modseq <= iter->changedsince) continue;
++        if (iter->changedsince && record->modseq <= iter->changedsince) continue;
+         return iter->msg;
+     }
+ 
diff --git a/debian/patches/series b/debian/patches/series
index c5d71b5..e9631e4 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -22,3 +22,4 @@
 0022-close-backups-on-failure.patch
 0023-fix-memory-leak-on-ldap-failure.patch
 CVE-2019-11356.patch
+0024-dont-skip-records-with-modseq-0.patch

--- End Message ---
--- Begin Message --- 
Package: release.debian.org
Version: 10.2

Hi,

The fixes referenced by these bugs were included in today's 10.2 stable
point release.

Regards,

Adam

--- End Message ---
Reply to: