Bug#685663: unblock nordugrid-arc/2.0.0-3
Hi, Jonathan Nieder wrote (03 Jan 2013 07:31:25 GMT) : If I understand correctly then nordugrid-arc was not part of squeeze, so stable users are not relying on it yet. In that case I would suggest considering providing the package for wheezy through wheezy-backports after the release, which should make later fixes easier. What do you think? Same as #683142 (and dependent on it, since nordugrid-arc-aris Depends: bdii): no reply from Mattias for months, and nordugrid-arc was removed from testing last July, so I recommend the release team rejects this unblock request, and the maintainer uses backports after the release as they see fit to provide packages for stable users. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/85obf0rx9t@boum.org
Bug#685663: unblock nordugrid-arc/2.0.0-3
tags 685663 + moreinfo quit Hi Mattias, Mattias Ellert wrote: Since there was an RC bug reported against version 2.0.0-3 (some missing Replaces/Breaks), allowing this version back in to testing again would not be a good idea. I created a 2.0.0-3+wheezy1 version with the same fix that is in 2.0.0-5 and uploaded it to testing-proposed-updates. If I understand correctly then nordugrid-arc was not part of squeeze, so stable users are not relying on it yet. In that case I would suggest considering providing the package for wheezy through wheezy-backports after the release, which should make later fixes easier. What do you think? Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130103073125.GA665@elie.Belkin
Bug#685663: unblock nordugrid-arc/2.0.0-3
tor 2012-08-23 klockan 17:54 +0200 skrev Cyril Brulebois: Hi Mattias, Mattias Ellert mattias.ell...@fysast.uu.se (23/08/2012): The nordugrid-arc 2.0.0-3 package had already migrated to testing before the freeze, but was kicked out because a dependency of one of its binary packages was removed due to an RC classified bug. That package (bdii) has since been fixed and an unblock request for the fix has been filed. I'm not sure we're going to consider unblocking bdii, at least in its current form. It looks like a package which pretty much fails to comply with the freeze policy, so unless you come up with minimal changes to only fix actual bugs… (Hint: new upstream release, changing configuration, adding features, fixing lintian warnings, rewriting copyright, etc. are *not* things to do in unstable when you have RC bug fixes you want to get into testing.) Mraw, KiBi. Hi! bdii 5.2.5-2+wheezy3 was accepted into testing proposed updates on Nov 2. So the missing dependency of nordugrid-arc is back. Could nordugrid-arc be added to testing proposed updates too? Mattias signature.asc Description: This is a digitally signed message part
Bug#685663: unblock nordugrid-arc/2.0.0-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Control: block -1 by 683142 unblock nordugrid-arc/2.0.0-3 The nordugrid-arc 2.0.0-3 package had already migrated to testing before the freeze, but was kicked out because a dependency of one of its binary packages was removed due to an RC classified bug. That package (bdii) has since been fixed and an unblock request for the fix has been filed. This is a request to unblock this package so that it can get back in when its currently blocked dependency (bdii) is unblocked. Mattias signature.asc Description: This is a digitally signed message part
Bug#683142: Bug#685663: unblock nordugrid-arc/2.0.0-3
Hi Mattias, Mattias Ellert mattias.ell...@fysast.uu.se (23/08/2012): The nordugrid-arc 2.0.0-3 package had already migrated to testing before the freeze, but was kicked out because a dependency of one of its binary packages was removed due to an RC classified bug. That package (bdii) has since been fixed and an unblock request for the fix has been filed. I'm not sure we're going to consider unblocking bdii, at least in its current form. It looks like a package which pretty much fails to comply with the freeze policy, so unless you come up with minimal changes to only fix actual bugs… (Hint: new upstream release, changing configuration, adding features, fixing lintian warnings, rewriting copyright, etc. are *not* things to do in unstable when you have RC bug fixes you want to get into testing.) Mraw, KiBi. signature.asc Description: Digital signature
