On Thu, Nov 22, 2018 at 02:14:13PM +0100, Guillem Jover wrote: > Having an explicit check for the symbols stuff would be nice, but I > think it's besides the point. In the same way epochs in upstream > version are problematic, dashes in upstream versions are too IMO.
Since a few Policy revisions epochs (well, colons actually) are
forbidden in the upstream part of a version string.
And IIRC the reasoning was very similar to the dashes you are talking
about in this bug: confusion for human, and easy for programs to get
them wrong (think about people .split(':') or version string forgetting
to limit the split to 1, same for the dashes...).
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
