[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#542288: debian-policy: Version numbering: native packages, NMU's, and binary only uploads



On Wed, Aug 26 2009, Steve Langasek wrote:

> On Tue, Aug 18, 2009 at 04:25:37PM -0500, Manoj Srivastava wrote:
>>         Given that devscripts,  lintian,  and the dev-ref
>>  all advocate  or implement  +nmu\d+, and that debhelper and  cdbs look
>>  at the hyphen for determining native vs non-native,  I have tried to do
>>  so.  I think the proposed practice is strictly better  than not
>>  specifying any conventions, and where possible, Ihave tried to stick to
>>  best practices as documented in the dev-ref to base policy on.
>
>>         Having said that, there are a lot of packages that seem to still
>>  use versions like m/\-\d+\.\d+$/, so perhaps we should be couching this
>>  policy change as a 'recommends', and letting lintian warn about the
>>  version number.
>
> I don't agree that this is something that should be recommended.
> Changing the convention for NMU versioning of non-native packages is
> not necessary in order to correct the use of confusing version numbers
> for NMUs of native packages.  If the dev-ref is recommending +nmuN for
> non-native packages, then I think that's a bug in the dev-ref - a
> common enough problem given the lack of a public process for dev-ref
> change reviews.

        I think they changed that in a newer release than the one
 referred to in the bug report I saw.

> Recommending use of +nmuN for native packages seems like an
> appropriate thing for Policy to standardize, since using hyphens makes
> the package versions appear non-native and appending ".N" to the
> version collides with ordinary versioning conventions for native
> packages.

        So, we should have:

,----
|  Format:
|     Version:=  [<epoch>`:']<upstream_version>[`-'<debian_revision>]
|  Native Package NMU's:
|     Version =~ m/\+nmu\d+$/
|  Binary Only NMU's:
|    Version =~ m/\+b\d+$/
`----

        The next tgree are tentative:
,----
|  Non-native package NMU:
|    Version =~ m/\-\.\d+$/
`----
        This is tentative since I can't see why we need to outlaw
 packages adding \+nmu\d+ even on non-native packages. Perhaps policy
 should butt out here, if the pattern is different for non-native NMU's
 than for Native package NMU's.

,----
|  Stable Security NMU's
|    Version =~  m/\+deb\d\d.\d+$/
|  Testing Security NMU's
|   Version =~ m/\+debt\d\d.\d+$/
`----
        These last two do not have buy in from the security team, as far
 as I can tell.

        How does that sound?

        manoj
-- 
Most people's favorite way to end a game is by winning.
Manoj Srivastava <srivasta@acm.org> <http://www.golden-gryphon.com/>  
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C



Reply to: