Bug#768426: developers-reference: codenanamen version scheme in §5.13.3 (“Direct updates to testing”)
Stefano Rivera stefa...@debian.org (2015-03-10): Control: tags -1 + patch Here's a patch, implementing this change. I just proposed a t-p-u upload, following the scheme in dev-ref, and was reprimanded :) SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 diff --git a/pkgs.dbk b/pkgs.dbk index 5a34b95..a21c24b 100644 --- a/pkgs.dbk +++ b/pkgs.dbk @@ -2741,11 +2741,11 @@ updates through literalunstable/literal are possible, if the upload via literalunstable/literal does not pull in any new dependencies. /para para -Version numbers are usually selected by adding the codename of the -literaltesting/literal distribution and a running number, like -literal1.2squeeze1/literal for the first upload through -literaltesting-proposed-updates/literal of package version -literal1.2/literal. +Version numbers are usually selected by appending +literal+deb/literalreplaceableX/replaceableliteralu1/literal, ^^ This should be uY instead. +where replaceableX/replaceable is the major release number and +replaceableY/replaceable is a counter starting at literal1/literal. +e.g. literal1:2.4.3-4+deb8u1/literal. “Major release number” looks slightly ambiguous to me, I would have thought about 1:2.4.3 instead of 1:2.4.3-4 in the example. Other than that, the patch looks like a good idea. Mraw, KiBi. signature.asc Description: Digital signature
Bug#768426: developers-reference: codenanamen version scheme in §5.13.3 (“Direct updates to testing”)
Control: tags -1 + patch Here's a patch, implementing this change. I just proposed a t-p-u upload, following the scheme in dev-ref, and was reprimanded :) SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 diff --git a/pkgs.dbk b/pkgs.dbk index 5a34b95..a21c24b 100644 --- a/pkgs.dbk +++ b/pkgs.dbk @@ -2741,11 +2741,11 @@ updates through literalunstable/literal are possible, if the upload via literalunstable/literal does not pull in any new dependencies. /para para -Version numbers are usually selected by adding the codename of the -literaltesting/literal distribution and a running number, like -literal1.2squeeze1/literal for the first upload through -literaltesting-proposed-updates/literal of package version -literal1.2/literal. +Version numbers are usually selected by appending +literal+deb/literalreplaceableX/replaceableliteralu1/literal, +where replaceableX/replaceable is the major release number and +replaceableY/replaceable is a counter starting at literal1/literal. +e.g. literal1:2.4.3-4+deb8u1/literal. /para para Please make sure you didn't miss any of these items in your upload:
Bug#768426: developers-reference: codenanamen version scheme in §5.13.3 (“Direct updates to testing”)
Package: developers-reference Version: 3.4.14 Rebecca N. Palmer noticed[0] that §5.13.3 (“Direct updates to testing”) still recommends codenamen version suffix for t-p-u uploads: “Version numbers are usually selected by adding the codename of the testing distribution and a running number, like 1.2squeeze1 for the first upload through testing-proposed-updates of package version 1.2.” This scheme is obsolete, and +debXuY should be used instead (as §5.8.5.4 and §5.11.2 already do). [0] https://lists.debian.org/545c7c60.8050...@zoho.com -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
