> I would like your consideration as to whether to update Section 5.11.1 of the
> Developer's Reference to incorporate some of the views of Stefano Zacchiroli
> concerning "When and how to do an NMU". 
> For background as to why this came up, there's recently been discussion about
> several packages in Debian that are quite out of date compared to upstream,
> including the WINE packages -- this thread starts at . If you browse the
> 'wine' source package at , you can see what has transpired: there used to
> be several people collaborating on the wine packages, but for whatever reason
> it ended up being left to only one maintainer doing the work. This maintainer
> has stated  that he has time overloaded elsewhere so that he doesn't have
> time to work on the packages now, but simultaneously has QA requirements such
> that all of the older pre-1.2 wine versions must be packaged first before
> packaging versions 1.2 and 1.4.
> It seems like NMU(s) on the package(s) would be a reasonable course of action,
> but the current wording of Section 5.11.1 in the Developer's Reference 
> would seem to discourage this -- or at least that's how I personally interpret
> the current wording. This is the reason I would like to revisit this issue to
> see whether updating the wording in this section would be appropriate.
Could you be a bit more specific about what you believe is not allowed
to do using NMUs?