On 12/06/2014 01:57 PM, Adam D. Barratt wrote:
> On Sat, 2014-12-06 at 12:38 +0100, Sebastiaan Couwenberg wrote:
>> Hi Uwe,
>> On 12/05/2014 07:13 PM, Sebastiaan Couwenberg wrote:
>>>>> In the mean time I'm updating my clone of the repo to
>>>>> incorporate the recent NMUs and prepare a new upload for unstable
>>>>> if Uwe is unable to do so.
>>>> I can do the upload if you like.
>>> Yes, please. All my changes are available in the git repository on Alioth.
>> The above changes were uploaded to testing-proposed-updates instead of
>> unstable,
> I'm rather confused as to how that happened.

So am I. I though it was caused by the last distribution being reused by
dch, but -1 went to unstable, so that's unlikely.

>> so I've prepared a new upload for unstable with the following
>> changes:
>>  * Restructure control file with cme.
>>  * Bump Standards-Version to 3.9.6, no changes.
>>  * Use canonical Vcs-* URLs.
>>  * Add patch to use hardening build flags.
>>  * Remove period from package description.
>> Uwe, can you sponsor the upload to unstable too?
>> Release Team,
>> I believe that the changes in 2.7.2-2 & -3 are compliant with the Freeze
>> Policy,
> I'm not convinced that they are right now. OMMV.
>> but the changes between 2.7-1.2 in testing and 2.7.2-2 in
>> testing-proposed-updates does contain a new upstream release not
>> complaint with the Freeze Policy.
>> The debdiff between 2.7-1.2 and 2.7.2-3 is attached.
>> Would the -3 upload to unstable be eligible for an unblock despite the
>> new upstream release?
> Actually, it's _two_ new upstream releases. I've not examined the diff
> in great detail, but at first glance there appeared to be quite a number
> of changes.

If the other RMs also consider the changes for 2.7.2 unacceptable for
jessie, I think 2.7.2-2 should then be removed from testing-proposed
updates, and keep blocking the migration of 2.7.2-2 and subsequent
uploads to testing.

Kind Regards,


 GPG Key ID: 4096R/E88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Pkg-grass-devel mailing list

Reply via email to