Your message dated Sat, 15 Sep 2012 12:02:20 +0100
with message-id <1347706940.28617.44.camel@jacala.jungle.funky-badger.org>
and subject line Re: Bug#687635: unblock: telepathy-gabble/0.16.1-2
has caused the Debian Bug report #687635,
regarding unblock: telepathy-gabble/0.16.1-2
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.)
--
687635: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687635
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
Please consider:
unblock telepathy-gabble/0.16.1-2
telepathy-gabble (0.16.1-2) unstable; urgency=low
* Add patch from 0.16.2 to fix a potential use-after-free when
disconnecting with TLS verification channels open
* Add patches from 0.16.3 to avoid triggering repeated capability discovery
in iChat (Closes: #687370, LP: #984132)
-- Simon McVittie <smcv@debian.org> Fri, 14 Sep 2012 12:39:01 +0100
This contains the functional changes from upstream releases 0.16.2 and
0.16.3, but not the updated regression tests or autoreconf noise.
Full debdiff attached (telepathy-gabble_0.16.1-2.diff), plus broken-out
patches for your convenience.
In future, how would you feel about us using Telepathy upstream
stable-branch releases for this sort of thing, rather than individual patches?
This would generally mean adding unintrusive fixes for 'normal' bugs (like
the first one mentioned in this upload's changelog), some noise from
autoreconf and gtk-doc (which I could pass through filterdiff if you want),
and changes to the regression tests that don't affect the binary packages
(likewise).
(Before you ask, the change in Mission Control 5.12.1 to avoid deprecated
functions was indeed not suitable for a stable branch, and I've reverted it
upstream already. It should have only been in the 5.13 development branch.)
Thanks,
S

On Fri, 2012-09-14 at 13:19 +0100, Simon McVittie wrote:
> telepathy-gabble (0.16.1-2) unstable; urgency=low
>
> * Add patch from 0.16.2 to fix a potential use-after-free when
> disconnecting with TLS verification channels open
> * Add patches from 0.16.3 to avoid triggering repeated capability discovery
> in iChat (Closes: #687370, LP: #984132)
Unblocked; thanks.
> Full debdiff attached (telepathy-gabble_0.16.1-2.diff), plus broken-out
> patches for your convenience.
>
> In future, how would you feel about us using Telepathy upstream
> stable-branch releases for this sort of thing, rather than individual patches?
> This would generally mean adding unintrusive fixes for 'normal' bugs (like
> the first one mentioned in this upload's changelog), some noise from
> autoreconf and gtk-doc (which I could pass through filterdiff if you want),
> and changes to the regression tests that don't affect the binary packages
> (likewise).
>From what I've seen so far, that should be okay. In that case, filtered
diffs would be appreciated though.
Regards,
Adam