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

Andreas Tille tille at debian.org
Tue Oct 21 09:46:05 BST 2025


Hi Adrian,

Am Mon, Oct 20, 2025 at 10:56:38PM +0300 schrieb Adrian Bunk:
> > 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).

Thank you for confirming this.  I admit I simply consider it an extra
manual step that has no real value once there is a higher version right
inside the archive, thought.  Please correct my if you might see this
differently.
 
> > 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.

That's correct.
 
> I have seen people doing a maintainer upload with an NMU version for 
> this reason.

Good idea.  I should have read this hint before todays lambda-align
upload.
 
> 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.

I agree and we should probably write this down in policy.
 
> 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.

I admit I prefer the ~exp1 way ... but this is probably a matter of
taste / team policy.

BTW, as a general note regarding the CMake 4 bugs:  I prefered adding
-DCMAKE_POLICY_VERSION_MINIMUM=3.5 to override_dh_auto_configure target
in d/rules over patching.  The effect is more or less the same but
works without an additional patch that might need maintenance later.
Do you have any reason to prefer a patch?

Thanks again for all your great work.  Its really appreciated.

Kind regards
    Andreas.

-- 
https://fam-tille.de



More information about the Debian-med-packaging mailing list