[aur-general] Upstream version numbers that break pacman version comparison
baptiste at bitsofnetworks.org
Tue Nov 22 11:55:59 UTC 2016
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
> > 7.2p1 → 7.2p2 → 7.3 → 7.3p1 → etc
> >In the case of coq, I guess this is something that should ideally be fixed
> What a horrible, ugly way to version packages. If they could fix it upstream,
> its better. And it might even benefit other distributions.
I reported the bug upstream , and it turns out the maintainers have
already planned a more reasonable versioning scheme for the next version.
So, problem (most likely) solved!
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 801 bytes
Desc: not available
More information about the aur-general