New Upstream Release 0.5.2

[Omer Akram]

What's New?
===========
This new release is a stable bug fix release.

Fixes:
  * Use the right policy reference when requesting security token (fdo #31004)
  * Set the peer end-points before requesting his display picture (fdo #30411)
  * Don't queue all P2P chunks right away when using SB transport (fdo #29512)
  * Don't send invalid command when contact is in Allow and Block lists
  * Don't fail when current media that is not music (fdo #30625)

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: python-papyon 0.5.1-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sun Oct 24 13:40:32 2010
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Beta i386 (20100902.1)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: papyon

[Omer Akram (om26er)]

debdiff from 0.5.1-0ubuntu2 to 0.5.2-0ubuntu1

[Martin Pitt (pitti)]

Please fix in natty first. SRU ack for maverick, please get it uploaded.

[Artur Rona (ari-tczew)]

Generally we don't accept new upstream releases, if we can sync or merge package with Debian. 0.5.2 is in Debian experimental. Omer, could you consider merge/sync with Debian experimental?

https://wiki.ubuntu.com/UbuntuDevelopment/Merging

For maverick I'd like to get a stricte patch for fix major issues. However, if we get package from experimental, I propose to reconsider a backport.

[Artur Rona (ari-tczew)]

I've requested sync papyon 0.5.2 from Debian unstable. bug #681967

[Omer Akram (om26er)]

i talked to telepathy developers on IRC and they too recommend that we should backport this to maverick and also papyon 0.5.2 apparently fixes bug 665526

[Artur Rona (ari-tczew)]

papyon (0.5.2-1) experimental; urgency=low

  * New upstream release
    - Fix connection to MSN (Closes: #600928)
 -- Artur Rona <email address hidden> Mon, 29 Nov 2010 13:12:32 +0000

[Artur Rona (ari-tczew)]

Omer, please now follow with backport policy for maverick: https://help.ubuntu.com/community/UbuntuBackports.

[Omer Akram (om26er)]

when its only a bug fix release(no new features) i have seen other packages going into maverick-updates e.g. empathy 2.32.1 and then 2.32.2. since the quality of msn in empathy is not upto the standards as one could arguably say about the quality of gtalk/jabber so i would say it would be better for users to have this bug fix release from proper update channel.

[Artur Rona (ari-tczew)]

Omer, so what's the decision? Backport or fix bugs by patches in SRU?

[Omer Akram (om26er)]

> so what's the decision? Backport or fix bugs by patches in SRU?
since there has been no serious bugs reported for papyon i guess we can defer this SRU.

[Omer Akram (om26er)]

i will work on bug 665526 SRU if its needed.

[Omer Akram (om26er)]

closing the maverick task as wontfix, doing SRU for bug 665526

[Martin Pitt (pitti)]

Omer Akram [2010-11-29 16:09 -0000]:
> when its only a bug fix release(no new features) i have seen other
> packages going into maverick-updates

Correct. As long as all the changes in an upstream microrelease are
compatible with our SRU policy, we can take the whole thing.