This is by design - the Policy Manual says that you should not use
versions like this. I realise that this may not match the upstream
author's version numbering conventions, but we're trying to produce a
single coherent system here and sometimes that means overriding upstream
in order to integrate with the conventions of our system.
Policy 5.6.12 says:
<upstream_version>
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 comparison scheme.
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[1] and the
characters `.' `+' `-' `:' `~' (full stop, plus, hyphen, colon,
tilde) 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.
** Changed in: dh-make (Ubuntu)
Status: Incomplete => Won't Fix
--
dh_make doesn't recognize versions with no numbers
https://bugs.launchpad.net/bugs/186890
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
