Candidates for removal from testing (2012-10-30)

2012-10-30 Thread Niels Thykier
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

We are considering removing the following packages from testing as
they have unfixed RC bugs filed against them. The packages can be
found in the attached dd-list.  The bugs that put them on this list
can be found in the removals file (also attached) just above the
package name.  We have BCC'ed this email to pkg@packages.debian.org
for the relevant packages.

The packages have been selected based on the following criteria:
 * The package had at least one RC bug without activity for the past
   14 days.
 * If a bug is assigned to multiple packages, both packages will be
   affected.
 * The RC bug affects both unstable and testing.
 * The affected package does not have any reverse dependencies in
   testing.

If the relevant RC bugs in the affected packages are not dealt with
/before/ Wednesday the 7th of Nov.[1], the packages will be removed
from testing.  Note that dealt with may also include downgrading a
severity-inflated bug or fixing affected versions in the BTS.

Please remember to file unblock bugs for packages fixed via uploads to
unstable (and tpu bugs for requests to fix the package via a tpu
upload).

Should you need a bit more time than given, please do not hesitate to
contact us.  It is also easier for us if we can avoid having to
reintroduce a removed package.

We will check the DELAYED queues before activing the removal hints, so
NMUs in the DELAYED queues will be given a chance to reach unstable.

Thanks,
Niels (on behalf of the Release Team)

The bugs were found using the tools from:
  svn://svn.debian.org/svn/collab-qa/rc-buggy-leaf-packages


http://release.debian.org/wheezy/freeze_policy.html


[1] We intend to do the removal with the 10:00 UTC run of Britney of
that day.


 --8-- dd-list --8--
Aurélien GÉRÔME a...@roxor.cx
   dancer-ircd

Al Stone a...@debian.org
   lmbench

Chris Lamb la...@debian.org
   python-django-extensions

Debian PHP Maintainers pkg-php-ma...@lists.alioth.debian.org
   xcache (U)

Debian XMPP Maintainers pkg-xmpp-de...@lists.alioth.debian.org
   jabber-muc

Ghe Rivero ghe.riv...@stackops.com
   quantum (U)

Jesus Climent jesus.clim...@hispalinux.es
   distmp3

Jorge Salamero Sanz ben...@debian.org
   jabber-muc (U)

Jose Luis Tallon jltal...@adv-solutions.net
   couriergraph

Julien Danjou a...@debian.org
   quantum (U)

Kai Storbeck k...@xs4all.nl
   roundup

Loic Dachary (OuoU) l...@debian.org
   quantum (U)

Ludovic Brenta lbre...@debian.org
   polyorb (U)

Martin Loschwitz madk...@debian.org
   ircd-ircu

Mehdi Abaakouk sil...@sileht.net
   quantum (U)

Michal Čihař ni...@debian.org
   xcache

Mike Markley m...@markley.org
   dk-milter

Peter Krefting pet...@debian.org
   lyskom-server

PKG OpenStack openstack-de...@lists.alioth.debian.org
   quantum

Thomas Goirand z...@debian.org
   quantum (U)

Toni Mueller t...@debian.org
   roundup (U)

Xavier Grave xavier.gr...@ipno.in2p3.fr
   polyorb
 --8-- end of dd-list --8--

 --8-- removals.txt --8--
# #689884
remove couriergraph/0.25-4.1

# #689886
remove dancer-ircd/1.0.36-8

# #689887
remove distmp3/0.1.9.ds1-4.4

# #689888
remove dk-milter/1.0.0.dfsg-1.2

# #689893
remove ircd-ircu/2.10.12.10.dfsg1-1

# #689894
remove jabber-muc/0.8-3

# #689897
remove lmbench/3.0-a9-1

# #689898
remove lyskom-server/2.1.2-12

# #688299
remove polyorb/2.8~20110207-4

# #690425
remove python-django-extensions/0.6+git201107051902-1

# #685251
remove quantum/2012.1-5

# #689257
remove roundup/1.4.20-1

# #690409
remove xcache/2.0.0-2

 --8-- end of removals.txt --8--
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQj9XpAAoJEAVLu599gGRCilQP/0Pzrbiq2Qi5xRdN2Auk7mzr
Clqbt9nStd0ZDR6ju2lxVj9emkOIRMUAp5Oq2c/+lC5pg2+AgZD57ijKMJqJLDTM
o8Fr8oIVdAcyMgNt7hKo8vXcIz0gBh6qwLWRXdR37pTd4jNqjCGnTtxbS5ZMIcz0
x9J2LjvIPLE+KEsjmAw185W8YVvvkaqVQqfwQ6K0xGdXvv23gfhlimlFHQUs8ElG
yljmcRl0e+xBlFxa+zmueBeAPcwPCjUv5haJQWXEZVUjxXezO4FEdwcHZFDeLKYy
1DzpOFcd6wycjqsdizQQtzNGGF726Fdj2nSKc7RjZ2oMr34lYQPKgN233t+QK8f9
aHatHySzcj6etlmsjdHmHreSnzzMxrf08OqWKW8O7AmrWkUdWnQFnUuDXc1A+Dwf
ESBG51fbHVj/wCNQ3vq9WyNwZpXqn2VxtHceMhiNdjbjkh/hjr2/k6hUeLADxBqG
dwwLA1p3UVk35R19rk5C2qaJIV8INZXfnsg7qZ7rS+JoO0+ZNyRwbxQFuE6Wf1+2
fAvyjmB6qiqHoZ+tSBP44PTzN2uPofZbfe6GTcRVQGJW3JxUSNmjNgefAmXl5367
KJxQKhb6Y3fDbWEl+sum6cV5QMriPxtNY8NnaEBgeGlzWFSlI5s+ozMUrSOTKOV/
E6STJCINXJEOKmcx1ogj
=4EtK
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121030133215.e95cf3...@thykier.net



Re: Candidates for removal from testing (2012-10-30)

2012-10-30 Thread Jerome BENOIT

Hello List,

does it make sense to establish a list of candidates for reintroduction to 
testing ?

I have in mind packages that were discarded too quickly because
an easy to fix a RC appeared a some point while it was unofficially orphaned.

Jerome

On 30/10/12 14:32, Niels Thykier wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

We are considering removing the following packages from testing as
they have unfixed RC bugs filed against them. The packages can be
found in the attached dd-list.  The bugs that put them on this list
can be found in the removals file (also attached) just above the
package name.  We have BCC'ed this email topkg@packages.debian.org
for the relevant packages.

The packages have been selected based on the following criteria:
  * The package had at least one RC bug without activity for the past
14 days.
  * If a bug is assigned to multiple packages, both packages will be
affected.
  * The RC bug affects both unstable and testing.
  * The affected package does not have any reverse dependencies in
testing.

If the relevant RC bugs in the affected packages are not dealt with
/before/ Wednesday the 7th of Nov.[1], the packages will be removed
from testing.  Note that dealt with may also include downgrading a
severity-inflated bug or fixing affected versions in the BTS.

Please remember to file unblock bugs for packages fixed via uploads to
unstable (and tpu bugs for requests to fix the package via a tpu
upload).

Should you need a bit more time than given, please do not hesitate to
contact us.  It is also easier for us if we can avoid having to
reintroduce a removed package.

We will check the DELAYED queues before activing the removal hints, so
NMUs in the DELAYED queues will be given a chance to reach unstable.

Thanks,
Niels (on behalf of the Release Team)

The bugs were found using the tools from:
   svn://svn.debian.org/svn/collab-qa/rc-buggy-leaf-packages


http://release.debian.org/wheezy/freeze_policy.html


[1] We intend to do the removal with the 10:00 UTC run of Britney of
that day.


  --8-- dd-list --8--
Aurélien GÉRÔMEa...@roxor.cx
dancer-ircd

Al Stonea...@debian.org
lmbench

Chris Lambla...@debian.org
python-django-extensions

Debian PHP Maintainerspkg-php-ma...@lists.alioth.debian.org
xcache (U)

Debian XMPP Maintainerspkg-xmpp-de...@lists.alioth.debian.org
jabber-muc

Ghe Riveroghe.riv...@stackops.com
quantum (U)

Jesus Climentjesus.clim...@hispalinux.es
distmp3

Jorge Salamero Sanzben...@debian.org
jabber-muc (U)

Jose Luis Tallonjltal...@adv-solutions.net
couriergraph

Julien Danjoua...@debian.org
quantum (U)

Kai Storbeckk...@xs4all.nl
roundup

Loic Dachary (OuoU)l...@debian.org
quantum (U)

Ludovic Brentalbre...@debian.org
polyorb (U)

Martin Loschwitzmadk...@debian.org
ircd-ircu

Mehdi Abaakouksil...@sileht.net
quantum (U)

Michal Čihařni...@debian.org
xcache

Mike Markleym...@markley.org
dk-milter

Peter Kreftingpet...@debian.org
lyskom-server

PKG OpenStackopenstack-de...@lists.alioth.debian.org
quantum

Thomas Goirandz...@debian.org
quantum (U)

Toni Muellert...@debian.org
roundup (U)

Xavier Gravexavier.gr...@ipno.in2p3.fr
polyorb
  --8-- end of dd-list --8--

  --8-- removals.txt --8--
# #689884
remove couriergraph/0.25-4.1

# #689886
remove dancer-ircd/1.0.36-8

# #689887
remove distmp3/0.1.9.ds1-4.4

# #689888
remove dk-milter/1.0.0.dfsg-1.2

# #689893
remove ircd-ircu/2.10.12.10.dfsg1-1

# #689894
remove jabber-muc/0.8-3

# #689897
remove lmbench/3.0-a9-1

# #689898
remove lyskom-server/2.1.2-12

# #688299
remove polyorb/2.8~20110207-4

# #690425
remove python-django-extensions/0.6+git201107051902-1

# #685251
remove quantum/2012.1-5

# #689257
remove roundup/1.4.20-1

# #690409
remove xcache/2.0.0-2

  --8-- end of removals.txt --8--
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQj9XpAAoJEAVLu599gGRCilQP/0Pzrbiq2Qi5xRdN2Auk7mzr
Clqbt9nStd0ZDR6ju2lxVj9emkOIRMUAp5Oq2c/+lC5pg2+AgZD57ijKMJqJLDTM
o8Fr8oIVdAcyMgNt7hKo8vXcIz0gBh6qwLWRXdR37pTd4jNqjCGnTtxbS5ZMIcz0
x9J2LjvIPLE+KEsjmAw185W8YVvvkaqVQqfwQ6K0xGdXvv23gfhlimlFHQUs8ElG
yljmcRl0e+xBlFxa+zmueBeAPcwPCjUv5haJQWXEZVUjxXezO4FEdwcHZFDeLKYy
1DzpOFcd6wycjqsdizQQtzNGGF726Fdj2nSKc7RjZ2oMr34lYQPKgN233t+QK8f9
aHatHySzcj6etlmsjdHmHreSnzzMxrf08OqWKW8O7AmrWkUdWnQFnUuDXc1A+Dwf
ESBG51fbHVj/wCNQ3vq9WyNwZpXqn2VxtHceMhiNdjbjkh/hjr2/k6hUeLADxBqG
dwwLA1p3UVk35R19rk5C2qaJIV8INZXfnsg7qZ7rS+JoO0+ZNyRwbxQFuE6Wf1+2
fAvyjmB6qiqHoZ+tSBP44PTzN2uPofZbfe6GTcRVQGJW3JxUSNmjNgefAmXl5367
KJxQKhb6Y3fDbWEl+sum6cV5QMriPxtNY8NnaEBgeGlzWFSlI5s+ozMUrSOTKOV/
E6STJCINXJEOKmcx1ogj
=4EtK
-END PGP SIGNATURE-






--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/508ff7f4.2070...@rezozer.net



Re: Candidates for removal from testing (2012-10-30)

2012-10-30 Thread Jon Dowland
On Tue, Oct 30, 2012 at 04:53:24PM +0100, Jerome BENOIT wrote:
 does it make sense to establish a list of candidates for reintroduction to 
 testing ?

Is this not something best managed on a case-by-case basis?


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121030163630.GA20675@debian



Re: Candidates for removal from testing (2012-10-30)

2012-10-30 Thread Jerome BENOIT



On 30/10/12 17:36, Jon Dowland wrote:

On Tue, Oct 30, 2012 at 04:53:24PM +0100, Jerome BENOIT wrote:

does it make sense to establish a list of candidates for reintroduction to 
testing ?


Is this not something best managed on a case-by-case basis?



my experience as potential sponsoree for such a package answers me no because
it is hard to get a sponsor.

Jerome







--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/509004b9.1060...@rezozer.net



Re: Candidates for removal from testing (2012-10-30)

2012-10-30 Thread Neil Williams
On Tue, 30 Oct 2012 17:47:53 +0100
Jerome BENOIT g62993...@rezozer.net wrote:

 On 30/10/12 17:36, Jon Dowland wrote:
  On Tue, Oct 30, 2012 at 04:53:24PM +0100, Jerome BENOIT wrote:
  does it make sense to establish a list of candidates for reintroduction to 
  testing ?
 
  Is this not something best managed on a case-by-case basis?
 
 my experience as potential sponsoree for such a package answers me no because
 it is hard to get a sponsor.

As a former sponsor, the most common problem I saw was that packages
prepared for sponsoring during a release freeze took no account of the
freeze policy and introduced lame or undesirable changes which were not
suitable as RC bug fixes. If there's little chance of getting an
unblock, there is no point sponsoring.

Sponsoring can be more of a burden for the sponsor than just fixing
the bug, especially during a release freeze. I have, on occasion, moved
on to investigate a different RC bug in a more interesting package
rather than go through the process of sponsoring a stale fix merely
because it exists. This is as much a reflection of the kind of
packages involved - most are leaf packages which are of little interest
to most potential sponsors. Just because there is a potential fix
(which still needs testing by the sponsor), doesn't always mean that
the package is worth keeping in Debian. 

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgpfSzUwtD0pP.pgp
Description: PGP signature


Re: Candidates for removal from testing (2012-10-30)

2012-10-30 Thread Michael Gilbert
On Tue, Oct 30, 2012 at 12:47 PM, Jerome BENOIT wrote:
 Is this not something best managed on a case-by-case basis?

 my experience as potential sponsoree for such a package answers me no
 because
 it is hard to get a sponsor.

If it fixes *only* rc bugs, then send a bug to sponsorship-requests.
I have already committed to reviewing all rc sponsorship-requests, so
if it looks good, I will likely sponsor it.

Best wishes,
Mike


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CANTw=mmghcuyor9lytgboosdw6un8in_anjnutdadqzebhc...@mail.gmail.com