Am Montag, den 13.08.2007, 22:26 +0200 schrieb Julian Andres Klode:
Am Montag, den 13.08.2007, 15:50 -0400 schrieb Joey Hess:
Policy is actually careful to set up the invarient that - anywhere in
a version number means the package is not native. I don't know why the
developers reference
(Please keep debian-devel in the CC. This issue is a project-wide
isssue.)
Bart Martens wrote:
How do other tools this?
Other well-respected tools in debhelper's situation, such as?
yada
It introduces a completely nonstandard Upstream-Source field in
debian/control which it
On Tue, Aug 14, 2007 at 13:38:04 -0400, Joey Hess wrote:
Bart Martens wrote:
Policy states that if there is no debian_revision then hyphens - are
not allowed in the upstream_version.
http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version
Policy also states that native
On Tue, Aug 14, 2007 at 19:45:11 +0200, Julien Cristau wrote:
It also implies that if there is no debian_revision, upstream_version
can contain a hyphen.
No it doesn't. Sorry about that...
Cheers,
Julien
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
On Tue, Aug 14, 2007 at 01:38:04PM -0400, Joey Hess wrote:
Bart Martens wrote:
Policy does not explicitly state that the presence/absence of a
debian_revision or that the presence/absence of hyphen(s) - indicate
whether or not the package is a native Debian package.
debian_revision
(For the second time, please preserve my CC.)
Bart Martens wrote:
Yes, lintian. Two examples where lintian seems to follow/accept the
numbering described in developer's reference:
Example one: Try doing an NMU of dh-make-php with adding .0.1. Then
lintian produces this warning:
W:
Julien Cristau wrote:
It also implies that if there is no debian_revision, upstream_version
can contain a hyphen.
Utterly false:
The upstream_version may contain only alphanumerics[1] and the
characters `.' `+' `-' `:' (full stop, plus, hyphen, colon) and
should
Thank you for the additional information you have supplied regarding
this problem report. It has NOT been forwarded to the package
maintainers, but will accompany the original report in the Bug
tracking system. Please ensure that you yourself have sent a copy of
the additional information to any
[EMAIL PROTECTED] wrote:
Because it may be more important to be able to identify an NMU from the
version number than to be able to identify a native package from the
version number...
I don't see why it's important to be able to tell that from a version
number at all. It's also not the
Joey Hess [EMAIL PROTECTED] writes:
(For the second time, please preserve my CC.)
Bart Martens wrote:
Yes, lintian. Two examples where lintian seems to follow/accept the
numbering described in developer's reference:
Example one: Try doing an NMU of dh-make-php with adding .0.1. Then
Bart Martens wrote:
Now imagine that someone would do an NMU of dh-make-php. The right
version would be 0.2.3-0.1 according to Debian Policy.
Actually, policy doesn't say any such thing. That syntax was invented by
the developer's reference. And it's IMHO dubious.
Consider two packages:
foo
Am Montag, den 13.08.2007, 15:50 -0400 schrieb Joey Hess:
Policy is actually careful to set up the invarient that - anywhere in
a version number means the package is not native. I don't know why the
developers reference choses to ignore that. Is there something wrong
with using a version
12 matches
Mail list logo
