Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#9226 - perl-anyevent version format change confuses pacman
Attached to Project:
Arch Linux
Opened by Petros Moisiadis (Ernest0x) - Wednesday, 16 January 2008, 10:33 GMT
Last edited by Tobias Kieslich (tobias) - Friday, 18 January 2008, 03:01 GMT
Opened by Petros Moisiadis (Ernest0x) - Wednesday, 16 January 2008, 10:33 GMT
Last edited by Tobias Kieslich (tobias) - Friday, 18 January 2008, 03:01 GMT
|
DetailsDescription:
With 'pacman -Syu', I get the following: warning: perl-anyevent: local (2.54-2) is newer than extra (2.8-1) Perhaps, pacman thinks that 2.54 > 2.8, which is wrong in this case (version format changed for perl-anyevent?). So, the update should be forced by default. Additional info: Pacman v3.1.0 - libalpm v2.0.0 perl-anyevent 2.54-2 -> perl-anyevent 2.8-1 Steps to reproduce: With perl-anyevent 2.54-2 already installed, run 'pacman -Syu'. |
This task depends upon
It's a problem in perl-anyevent, which is an extra package.
As Petros clearly explained, this update should be forced, there is no other way.
2.8 is > 2.5 and IMHO it shouldn't matter if it's 2.5 or 2.5678.
Moving back. Sorry. :(