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 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.

Regards,

Adam

_______________________________________________
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Reply via email to