Bug#542288: debian-policy: Version numbering: native packages, NMU's, and binary only uploads
On Sat, 2017-07-01 at 16:00 +0100, Sean Whitton wrote:
> On Sun, Jun 25, 2017 at 04:01:43PM -0700, Russ Allbery wrote:
> > > One rarer case is missing here:
> >
> > > 1.2.3-4~deb9u1
> > > Everything in 1.2.3-4 from unstable was in fact needed in Debian
> > > 9, so it was simply rebuilt for Debian 9 and uploaded there
> > > (prominent examples: firefox-esr, intel-microcode)
> >
> > Is this widespread enough to be worth describing? It's kind of hard to
> > describe.
>
> I for one had assumed that there was no difference between -deb9u1 and
> ~deb9u1, so I'd like to see it documented.
fwiw, I can't think of situations where -deb9u1 would ever be used.
Either a selected set of changes were applied to the package in stable,
which would be +debXuY, or a newer upload was backported in its
entirety, which would be ~debXuY as above.
In terms of the use of ~ versions for stable updates being widespread,
there are currently eight packages in either stable-new or
proposed-updates using such versions and a further nine in the
corresponding suites for jessie. Several, but by no means all, of those
uses are in packages from the security archive.
Regards,
Adam
Reply to: