Bug#542288: Version numbering: native packages, NMU's, and binary only uploads
On Sun, Jan 8, 2012 at 12:17 PM, Russ Allbery wrote:
> In the long run, what we want is something that satisfies:
>
> package < binNMU < stable/security update < NMU < maintainer upload
>
> with all stable/security updates sorting in Debian release order.
>
> The current convention of .1 satisfies this requirement except for native
> packages where it can't be used, and except for the fact that our
> stable/security updates don't have a good sorting pattern because of the
> use of codenames (which is true of any possible scheme right now).
>
> The +nmu convention doesn't satisfy this because of conflicts with the
> stable/security updates.
>
> A scheme that would always satisfy this would be to use +<letter><version>
> for stable/security updates where <version> is the Debian version being
> targeted similar to how that's done for backports (so 50 for lenny or 60
> for squeeze), and <letter> is some letter between b and n. (Alternately,
> we could use a different convention for NMUs than +nmu, but that's so
> self-explanatory that it would be nice to stick with it.)
>
> If I had to propose something, I'd propose +d60 or +dist60 for the
> stable/security updates, but there are probably better and more memorable
> terms than "dist".
It sounds like +debXuY is now the plan for stable/security updates in
wheezy and future releases. I wonder if the part about +nmuN as an
optional versioning for non-native packages could be re-added?
Best wishes,
Mike
Reply to: