FS#21237 - Pacman incorrectly evaluates letters in package version

Attached to Project: Pacman
Opened by Dan Vratil (progdan) - Wednesday, 13 October 2010, 19:59 GMT
Last edited by Dan McGee (toofishes) - Wednesday, 13 October 2010, 20:06 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 3.4.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I just got this message from pacman:

warning: proftpd: local (1.3.3-5) is newer than extra (1.3.3b-1)

Which is obviously incorrect. Seems to me that pacman ignores the letter in version and therefor it considers local package newer.
This task depends upon

Closed by  Dan McGee (toofishes)
Wednesday, 13 October 2010, 20:06 GMT
Reason for closing:  Duplicate
Additional comments about closing:  We have like 6 reports already.
Comment by Dan McGee (toofishes) - Wednesday, 13 October 2010, 20:06 GMT
Fucking hell, can we look around first? It is not *obviously* anything. One person interprets the 'b' as beta, while the next person does it like OpenSSL and uses it as a patch level. The behavior, and this *exact* case, is clearly stated in the manpage:

When upgrading, pacman performs version comparison to determine which packages need upgrading. This behavior operates as follows:

Alphanumeric:
1.0a < 1.0alpha < 1.0b < 1.0beta < 1.0p < 1.0pre < 1.0rc < 1.0
Numeric:
1 < 1.0 < 1.1 < 1.1.1 < 1.2 < 2.0 < 3.0.0
Comment by Dan McGee (toofishes) - Wednesday, 13 October 2010, 20:08 GMT
And sorry for my attitude, but we just have a lot of these. I understand the problem, we have potential patches to make it better, but the "obviously incorrect" comment pushes my buttons.

Loading...