* Anthony Towns aj@azure.humbug.org.au [031101 06:53]:
I'd be more inclined to fix the tools, personally, or to say that
within Debian, we'll translate upstream colons to something else
than removing the support from dpkg or changing its meaning.
Sorry, I have problems parsing this. Does this
Richard Braakman [EMAIL PROTECTED] wrote:
This just means that colons are _sometimes_ allowed in the upstream
version (namely when the package already has an epoch for some reason).
No they're always allowed. You just have to prefix them with an epoch.
--
Debian GNU/Linux 3.0 is out! (
On Sun, Oct 26, 2003 at 01:53:26PM +0100, Bernhard R. Link wrote:
Policy 5.6.11 describes the upstream version part as:
| if there is no epoch then colons are not allowed.
~
Thus I suggest 5.6.11 to be changed so that colons are no longer
On Sat, Nov 01, 2003 at 01:19:51AM +0100, Josip Rodin wrote:
On Sun, Oct 26, 2003 at 01:53:26PM +0100, Bernhard R. Link wrote:
Policy 5.6.11 describes the upstream version part as:
| if there is no epoch then colons are not allowed.
~
On Sat, Nov 01, 2003 at 02:51:48AM +0200, Richard Braakman wrote:
On Sat, Nov 01, 2003 at 01:19:51AM +0100, Josip Rodin wrote:
On Sun, Oct 26, 2003 at 01:53:26PM +0100, Bernhard R. Link wrote:
Policy 5.6.11 describes the upstream version part as:
| if there is no epoch then colons are not
While looking in policy and the implementing code I found
a little discrepancy, I wanted to discuss:
Policy 5.6.11 describes the upstream version part as:
| The upstream_version may contain only alphanumerics[28] and
| the characters . + - : (full stop, plus, hyphen, colon)
| and should start
6 matches
Mail list logo