On 2025-01-20 09:38 +0000, Andrew Bower wrote: > Hi Jörg, > > On Mon, Jan 20, 2025 at 09:38:24AM +0100, Julien Plissonneau Duquène wrote: > > Le 2025-01-20 08:03, Jörg Frings-Fürst a écrit : > > > > > > Is it enough to change from 1.0.14-19 to 1.0.14-20+git[commit id]? > [...] > > 2. if the changes are extensive and you would rather repackage the whole > > source tree from git, then 1.0.14+git[date . commit id]-1 is appropriate.
> e.g. 1.0.15~git20241023.5c148771-1 Just to clarify the good advice above, the important thing to understand is that ~ always sorts/orders _lower_ than everything and other things sort as expected. so if current version is 1.0.14 you can either put out 1.0.14+gitnnn (and move to 1.0.15 when it is released) or 1.0.15~gitnnn (and move to 1.0.15 when it is released) but if you put out 1.0.15+gitnnn you would never be able to release 1.0.15 proper without an epoch. Obviously if you have debian -nn versions on the end this is much less of an issue because if you ruled out -20 by having a -20+git you can just put out -21. This was your original proposal, but I just thought it worth clarifying how this works, because if you don't understand it in advance you can find you messed yourself up on versions when you didn't need to (and yes this happened to me many years ago and I have been very careful since :-). Wookey -- Principal hats: Debian, Wookware http://wookware.org/
signature.asc
Description: PGP signature
