[Debian-med-packaging] Bug#1113407: pizzly: diff for NMU version 0.37.3+ds-9.1

[Adrian Bunk]

On Mon, Oct 20, 2025 at 08:57:59PM +0200, Andreas Tille wrote:
> Hi Santiago,
> 
> Am Mon, Oct 20, 2025 at 06:33:08PM +0200 schrieb Santiago Vila:
> > On Mon, Oct 20, 2025 at 10:34:50AM +0300, Adrian Bunk wrote:
> > 
> > > I've prepared an NMU for pizzly (versioned as 0.37.3+ds-9.1) and 
> > > uploaded it to DELAYED/2. Please feel free to tell me if I should
> > > cancel it.
> > 
> > There is a pizzly version -10 in experimental.
> 
> Ahhh, good catch, thank you!
>  
> > If I wanted to make a maintainer upload from this, what would I be
> > supposed to do? Should we ask Adrian to cancel this one?
> 
> I think this will not be accepted anyway.  I do not see any reason to
> ask him for canceling.

FTR:
I do not have a problem with canceling an NMU, and any DD could cancel
an NMU from DELAYED when there is a reason (and the maintainer upload
is not anyway faster so that the NMU will just be rejected).

> > The experimental version is about seqan2, which I believe requires
> > coordinated uploads.
> 
> We had similar packages which ended up in experimental but its not clear
> to me how to proceed.  I now did the same (and force-pushed) as in other
> cases:  Keep the changelog entry for continuous history in d/changelog)
> and bumped the version of my upload to -11.
> 
> This is all a bit unfortunate and we do not have a good policy for such
> transitions via experimental.  For the moment I think it is better to
> have the RC bug fixed now.
>...

A side-effect of an NMU is that its version number stays below the 
version of a more recent maintainer upload in experimental.

I have seen people doing a maintainer upload with an NMU version for 
this reason.

For something that is more a test rebuild like in this case, I'd suggest 
in future cases to use a version like 0.37.3+ds-9+exp1 or 0.37.3+ds-10~exp1
in experimental and not include the changelog entry in the next upload 
to unstable if the changes were not (yet) included in that unstable upload.

There is even precedent of maintainers doing +exp1 uploads for some 
time every time they are doing an upload to unstable for maintaining
an experimental-only change until it is ready for unstable.

> Kind regards
>    Andreas.

cu
Adrian