how to use version and debian revison
im trieng to understand the way to use version and debian revison
the orignal softwere wasn't made specialy for debian and it's version is 2.
as i understand we debian revisions when only the package is changed and
not the actual software.
as stated in
The version number of a package. The format is:
The three components here are:
This is a single (generally small) unsigned integer. It may be omitted,
in which case zero is assumed. If it is omitted then the
upstream_version may not contain any colons.
It is provided to allow mistakes in the version numbers of older
versions of a package, and also a package's previous version numbering
schemes, to be left behind.
This is the main part of the version number. It is usually the version
number of the original ("upstream") package from which the .deb 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
The comparison behavior of the package management system with respect
to the upstream_version is described below. The upstream_version portion
of the version number is mandatory.
The upstream_version may contain only alphanumerics and the
characters . + - : (full stop, plus, hyphen, colon) and should start
with a digit. If there is no debian_revision then hyphens are not
allowed; if there is no epoch then colons are not allowed.
This part of the version number specifies the version of the Debian
package based on the upstream version. It may contain only alphanumerics
and the characters + and . (plus and full stop) and is compared in the
same way as the upstream_version is.
It is optional; if it isn't present then the upstream_version may not
contain a hyphen. This format represents the case where a piece of
software was written specifically to be turned into a Debian package,
and so there is only one "debianisation" of it and therefore no revision
indication is required.
It is conventional to restart the debian_revision at 1 each time the
upstream_version is increased.
The package management system will break the version number apart at
the last hyphen in the string (if there is one) to determine the
upstream_version and debian_revision. The absence of a debian_revision
compares earlier than the presence of one (but note that the
debian_revision is the least significant part of the version number).
The upstream_version and debian_revision parts are compared by the
package management system using the same algorithm:
The strings are compared from left to right.
First the initial part of each string consisting entirely of non-digit
characters is determined. These two parts (one of which may be empty)
are compared lexically. If a difference is found it is returned. The
lexical comparison is a comparison of ASCII values modified so that all
the letters sort earlier than all the non-letters.
Then the initial part of the remainder of each string which consists
entirely of digit characters is determined. The numerical values of
these two parts are compared, and any difference found is returned as
the result of the comparison. For these purposes an empty string (which
can only occur at the end of one or both version strings being compared)
counts as zero.
These two steps (comparing and removing initial non-digit strings and
initial digit strings) are repeated until a difference is found or both
strings are exhausted.
Note that the purpose of epochs is to allow us to leave behind mistakes
in version numbering, and to cope with situations where the version
numbering scheme changes. It is not intended to cope with version
numbers containing strings of letters which the package management
system cannot interpret (such as ALPHA or pre-), or with silly orderings
(the author of this manual has heard of a package whose versions went
1.1, 1.2, 1.3, 1, 2.1, 2.2, 2 and so forth).
so as i under stand from the text the version should be :
#6 is the current debian_revison number
so in control file :
and in a changelog
package name (2-6) ;....
but when i do that i get the error (from lintian):
W: smser source: native-package-with-dash-version
N: Native packaging should only be used if a piece of software was
N: written specifically to be turned into a Debian package. In this case,
N: the version number should not contain a debian revision part.
N: Native source packages are sometimes created by accident. In most
N: cases the reason is the location of the original source tarball.
N: dpkg-source searches for this in
but i don't store the orignal file in this format .
control file :
Maintainer: Jabka Atu <>
Description: a command-line application that lets you send SMS
messages to a list of phone numbers located in a file.
It places all the messages in the CenterICQ's queue and when CenterICQ
is invoked all the messages are sent to the recipients.
smser (2-6) stable; urgency=low
* fixed lintien errors :
dash error - fixed by changing the revsion from -5 to .5
* fixed the man file (add the option for accounts)
-- Jabka Atu <> Mon, 03 Sep 2007 21:27:38 +0300
smser (2.000-3) stable; urgency=low
* fixed some lintian errors but (still can't fix the 3 warnings):
W: smser source: package-uses-deprecated-debhelper-compat-version 1
W: smser source: native-package-with-dash-version
W: smser: description-starts-with-leading-spaces
-- Jabka Atu <> Mon, 03 Sep 2007 18:27:38 +0300
smser (2.000-2) stable; urgency=low
* Spelling errors
-- Jabka Atu <firstname.lastname@example.org> Mon, 03 Sep 2007 08:27:38 +0300
smser (2.000-1) experimental; urgency=low
* Initial debian release
-- Jabka Atu <email@example.com> Mon, 21 May 2007 08:27:38 +0300
Could you at least use man ?
Jabka Atu (aka mha13/Mashrom Head)