Quoting Ron ([email protected]):
> On Sat, Jan 15, 2011 at 05:30:22PM +0100, Christian PERRIER wrote:
> > Dear maintainer,
> > 
> > I've prepared and upload an NMU for vpb-driver (versioned as 4.2.49-1.1). 
> > The diff
> > is attached to this message.
> > 
> > This has been uploaded to t-p-u as a new upstream version is in
> > unstable.
> > 
> > This upload fixes a broken encoding of a debconf translation. See
> > https://lists.debian.org/debian-devel/2011/01/msg00288.html for details.
> 
> Erm, wait.  Let me be sure I've got this straight...

There were like 20 packages in the same situation, reported by Julien
Cristau in -devel.

I announced the possible NMUs in -devel and CC'ed -release. There have
been no formal objection by the release team to this specific and
kinda extraordinary process (I think they roughly give me credit for
not doing stupid things when it comes at i18n stuff). This in about
3-4 days. Then I announced that I would be uploading these NMUs
"before the end of the week-end"...then confirmed that with mails to 
<package>@packages.debian.org

Given the available free time, I agree that no bugs were reported for
these problems but, again, this has been accepted as very exceptional
situation and, given that the release might happen any time now, we
had no time for a detailed process. The lack of objection by the
release team has been taken as an approval.

I don't really see much problem: the NMU is correct...and you, as
maintainer, have the diff. And, more importantly, the problem is
fixed.

No need to tell me "don't do this again". For two reasons: in normal
time, I wouldn't follow this process....and if the very same situation
happened, I would do *exactly* the same.


Attachment: signature.asc
Description: Digital signature

Reply via email to