Daniel Lintott dan...@serverb.co.uk wrote:
On 10/12/13 19:21, Dominik George wrote:
[2] http://qa.debian.org/cgi-bin/watch?pkg=vpcs_0.5b0-1
In that special case, I'd even say your versioning mistake is
good because upstream's ~ notation is a mess. That char is reserved
for Debian ;) (yes,
~b0-1.
I have seen some discussion on correcting the version number, either
by using an epoch or by adding an additional part to the version number.
- From what I can see, the only way to fix the version number here is to
use an epoch, but from what I've this should be avoided if possible,
so does
have seen some discussion on correcting the version number, either
by using an epoch or by adding an additional part to the version number.
- From what I can see, the only way to fix the version number here is to
use an epoch, but from what I've this should be avoided if possible,
so does anyone
Hi,
I have realised that in an earlier package upload, I made a blunder
with regards the version of the package.
Where is that package now? On mentors, or in Debian?
-nik
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/12/13 18:59, Dominik George wrote:
Hi,
I have realised that in an earlier package upload, I made a
blunder with regards the version of the package.
Where is that package now? On mentors, or in Debian?
-nik
The package is in
[2] http://qa.debian.org/cgi-bin/watch?pkg=vpcs_0.5b0-1
In that special case, I'd even say your versioning mistake is good because
upstream's ~ notation is a mess. That char is reserved for Debian ;) (yes,
that's false and not so humble ;))!
Why not keep your version numbering as it is and use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/12/13 19:21, Dominik George wrote:
[2] http://qa.debian.org/cgi-bin/watch?pkg=vpcs_0.5b0-1
In that special case, I'd even say your versioning mistake is
good because upstream's ~ notation is a mess. That char is reserved
for Debian ;)
7 matches
Mail list logo
