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#4010 - Pacman and weblist says different version of bmp
Attached to Project:
Arch Linux
Opened by Roman Kyrylych (Romashka) - Monday, 20 February 2006, 08:35 GMT
Opened by Roman Kyrylych (Romashka) - Monday, 20 February 2006, 08:35 GMT
|
DetailsToday my pacman said:
:: bmp: local (0.9.7.1-3) appears to be newer than repo (extra/0.9.7.1-2) But on http://www.archlinux.org/packages.php?id=3280 and in CVS there is bmp-0.9.7.1-3 |
This task depends upon
I removed all .lastupdate files from /var/lib/pacman and -Syu again, but result is the same.
Oh, I see today is a huge update of [extra] and cleanup of [testing].
But why to update packages for Xorg7 while not incrementing build version?
It forces [testing] users to downgrade some packages.
For example, there is artwiz-fonts-1.3-2 in [extra] but it is exactly the same as artwiz-fonts-1.3-3 from [testing] (which is now deleted).
But it would be useful if Pacman could handle such situations.
Shame on me! :-)