<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> <div class="moz-cite-prefix">On 07/14/2013 07:26 PM, Chow Loong Jin wrote: </div> <blockquote cite="mid:20130715002607.GC3476@gmail.com" type="cite"> <pre wrap="">On Sun, Jul 14, 2013 at 12:23:30PM -0400, Scott Howard wrote: </pre> <blockquote type="cite"> <pre wrap="">On Sun, Jul 14, 2013 at 12:17 PM, Anton Balashov <a class="moz-txt-link-rfc2396E" href="mailto:sicness@darklogic.ru"><sicness@darklogic.ru></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">Hello. I'm trying to make automatic daily builds if there is new commits in git. So, many commits have version 1.1.1 and I should to have many debs with different orig.tar.gz I want to have some like pkg-1.1.1-<date>ppa1 But when I'm trying to upload new version, I get an error: pkg-1.1.1.orig.tar.gz was changes. And it's true. I can put some part of commit hash in version (1.1.1~hash-date..) but it's breaks order. I can't have increment system here (or can but non-trivial). </pre> </blockquote> <pre wrap=""> use a + instead of ~ ,and put date first since hash is random and date is ordered (higher dates are newer than lower dates). 1.1.1+date-hash </pre> </blockquote> <pre wrap=""> Use date.hash instead of date-hash. '-' is reserved for separating the debian revision from the upstream version of a package. </pre> </blockquote> Per Policy 5.6.12 [1]: <dl> <dt><var>upstream_version</var></dt> <dd> This is the main part of the version number. It is usually the version number of the original ("upstream") package from which the <code>.deb</code> file has been made, if this is applicable. Usually this will be in the same format as that specified by the upstream author(s); however, it may need to be reformatted to fit into the package management system's format and comparison scheme. The comparison behavior of the package management system with respect to the <var>upstream_version</var> is described below. The <var>upstream_version</var> portion of the version number is mandatory. The <var>upstream_version</var> may contain only alphanumerics[<a href="http://www.debian.org/doc/debian-policy/footnotes.html#f36" name="fr36">36</a>] and the characters <samp>.</samp> <samp>+</samp> <samp>-</samp> <samp>:</samp> <samp>~</samp> (full stop, plus, hyphen, colon, tilde) and should start with a digit. If there is no <var>debian_revision</var> then hyphens are not allowed; if there is no <var>epoch</var> then colons are not allowed. </dd> </dl> So, hyphens are allowed in upstream versions as long as there is a Debian revision. Micah [1] <a class="moz-txt-link-freetext" href="http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version">http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version</a> </body> </html>