[aur-general] Upstream version numbers that break pacman version comparison

[Baptiste Jonglez]

On Tue, Nov 22, 2016 at 11:28:40AM +0000, Giancarlo Razzolini wrote:
> Em novembro 22, 2016 6:35 Baptiste Jonglez escreveu:
> >Interesting, thanks.  However, upstream starts each new minor version at
> >p1, so it looks like:
> >
> >    7.2p1 → 7.2p2 → 7.3p1 → etc
> >
> 
> Worth nothing that OpenSSH releases the so called "portable" versions. Hence
> the 'p'.

You're right, it's not the same semantic.

> >which works fine for pacman.  The problematic behaviour for pacman would
> >be:
> >
> >    7.2p1 → 7.2p2 → 7.3 → 7.3p1 → etc
> >
> >In the case of coq, I guess this is something that should ideally be fixed
> >upstream.
> >
> 
> What a horrible, ugly way to version packages. If they could fix it upstream,
> its better. And it might even benefit other distributions.

Totally agreed.

I reported the bug upstream [1], and it turns out the maintainers have
already planned a more reasonable versioning scheme for the next version.
So, problem (most likely) solved!

Thanks,
Baptiste

[1] https://coq.inria.fr/bugs/show_bug.cgi?id=5221
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <https://lists.archlinux.org/pipermail/aur-general/attachments/20161122/dc5aab61/attachment.asc>