Requesting squeeze-backport of python-debian
Iain Lane
laney at debian.org
Wed Dec 28 23:04:04 UTC 2011
Hey,
On Wed, Dec 28, 2011 at 02:40:16PM -0800, John Wright wrote:
> On Sat, Dec 24, 2011 at 06:34:32PM +0000, Iain Lane wrote:
> > On Sat, Dec 24, 2011 at 07:00:19PM +0100, Julien Cristau wrote:
> > > On Sat, Dec 24, 2011 at 17:44:57 +0000, Iain Lane wrote:
> > >
> > > > Hiya,
> > > >
> > > > I'd quite like to fix #637524 in UDD, and for this we need the newer
> > > > python-debian on the UDD host with the fix for #597249.
> > > >
> > > Or you could just fix that bug in stable.
> >
> > Someone could. Thank you for your friendly reply.
>
> I didn't see any takers for the stable update. I'll start that now.
Thanks very much. I did start to do it — attached is the braindead
backport of the patch I did, if it's of any use to you. Passes the
tests, but I haven't done any more than that.
---
Regarding the unsuitability of backports, I am well aware that stable
updates should be tried if possible. However, I consulted devref[0],
which says (in part):
[…] Basically, a package should only be uploaded to stable if one of the
following happens:
* a truly critical functionality problem
* the package becomes uninstallable
* a released architecture lacks the package
and I fail to be able to interpret this issue as "truly critical". So
asking to go via backports.
SRMs, what is the barrier for bug fixes to be considered for stable
updates? If devref is misleading, can it be clarified?
Backports team, I get now that you expect stable updates to be tried if
the motivation of the backport is to get a specific bug fix out. But
would you accept such a backport if it is rejected for stable? i.e. is
there a gap here where there is no route to get a fix out 'officially'?
---
I realise that I was overly snippy in responsed to perceived discourtesy
in this thread. Please accept my apologies.
Ho ho ho,
--
Iain Lane [ iain at orangesquash.org.uk ]
Debian Developer [ laney at debian.org ]
Ubuntu Developer [ laney at ubuntu.com ]
PhD student [ ial at cs.nott.ac.uk ]
[0]
http://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable
-------------- next part --------------
A non-text attachment was scrubbed...
Name: spu.diff
Type: text/x-diff
Size: 1503 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-python-debian-maint/attachments/20111228/9feff45b/attachment.diff>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-python-debian-maint/attachments/20111228/9feff45b/attachment.pgp>
More information about the pkg-python-debian-maint
mailing list