Your message dated Wed, 25 Dec 2013 22:36:01 +0100 with message-id <20131225213601.GP4822@betterave.cristau.org> and subject line Re: Bug#711345: transition: cyrus-sasl2 has caused the Debian Bug report #711345, regarding transition: cyrus-sasl2 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.) -- 711345: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711345 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: transition: cyrus-sasl2
- From: Ondřej Surý <ondrej@debian.org>
- Date: Thu, 06 Jun 2013 14:39:46 +0200
- Message-id: <20130606123946.16290.74280.reportbug@howl.nic.cz>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: transition -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Upstream SOVER change to fix #665476. Ben file: title = "cyrus-sasl2"; is_affected = .depends ~ "libsasl2-2" | .depends ~ "libsasl2-3"; is_good = .depends ~ "libsasl2-3"; is_bad = .depends ~ "libsasl2-2"; - -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlGwgw8ACgkQ9OZqfMIN8nNodgCgokg2I0b/2RkrgWW0yK/uzEyv 7UEAnR1kf4uLgBEqbbXIBMX+nlICh7Ys =c+jH -----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
- To: Ondřej Surý <ondrej@debian.org>, 711345-done@bugs.debian.org
- Subject: Re: Bug#711345: transition: cyrus-sasl2
- From: Julien Cristau <jcristau@debian.org>
- Date: Wed, 25 Dec 2013 22:36:01 +0100
- Message-id: <20131225213601.GP4822@betterave.cristau.org>
- In-reply-to: <CALjhHG-Bv7ZyC8vv2FHvZvwRibzzfQT1hF7KnaxJa+SCV8GGmg@mail.gmail.com>
- References: <20130606123946.16290.74280.reportbug@howl.nic.cz> <20130709214806.GB28839@betterave.cristau.org> <CALjhHG-Bv7ZyC8vv2FHvZvwRibzzfQT1hF7KnaxJa+SCV8GGmg@mail.gmail.com>
On Tue, Jul 16, 2013 at 15:20:14 +0200, Ondřej Surý wrote: > On Tue, Jul 9, 2013 at 11:48 PM, Julien Cristau <jcristau@debian.org> wrote: > > > On Thu, Jun 6, 2013 at 14:39:46 +0200, Ondřej Surý wrote: > > > > > Package: release.debian.org > > > Severity: normal > > > User: release.debian.org@packages.debian.org > > > Usertags: transition > > > > > > Upstream SOVER change to fix #665476. > > > > > So, err. If we've shipped the new ABI in wheezy already, do we really > > want to go through the pain of an unnecessary SONAME bump now? > > Or is there some more ABI breakage in this release? > > > > I don't think so. > > But: > > a) do we really want to divert from upstream? > b) I think it's nice to know that we are actually able to bump the SONAME > at all, because the packages were not ready for SONAME bump at all. > > Anyway I will not struggle hard if you decide it's not worth it. > Let's table this one, I don't think there's much point. Cheers, JulienAttachment: signature.asc
Description: Digital signature
--- End Message ---