Hi Tobias and Phil, On Wed, Nov 01, 2023 at 01:50:04PM +0100, Tobias Frost wrote: > this seems to be a NMU, and for NMUs there is a set of rules [0], for > example it needs to fix (important) bugs.
Policy section 5.11.1. explicitly says even whishlist bugs are fair game:
pol> ("Bugs" means any kind of bugs, e.g. wishlist bugs for packaging a new
pol> upstream version, but care should be taken to minimize the impact to the
pol> maintainer.)
> Maybe I am missing something but I think this upload is outside of the
> scope of an NMU. Please let me know if I missed something.
Note policy sections 5.11.2. and 5.11.4. also explicitly talk about this
NMU-with-new-upstream-version scenario:
pol> If a new upstream version is packaged in the NMU, the Debian revision is
pol> set to 0, for example 1.6-0.1.
and
pol> Note that if you ever need to revert a NMU that packages a new upstream
pol> version, it is recommended to use a fake upstream version like
pol> CURRENT+reallyFORMER until one can upload the latest version again.
So I hardly think we can claim this is out of scope for NMUs if policy
deals with the nitty gritty of how to do it :)
--Daniel
signature.asc
Description: PGP signature
