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#41847 - [mksh] version numbering prevents pacman detecting 50-1 -> 50b-1 upgrade
Attached to Project:
Community Packages
Opened by Steven Honeyman (stevenhoneyman) - Saturday, 06 September 2014, 14:29 GMT
Last edited by Thorsten Töpper (Atsutane) - Sunday, 07 September 2014, 20:39 GMT
Opened by Steven Honeyman (stevenhoneyman) - Saturday, 06 September 2014, 14:29 GMT
Last edited by Thorsten Töpper (Atsutane) - Sunday, 07 September 2014, 20:39 GMT
|
DetailsDescription:
This is not detected as an upgrade because of the "b" in the version number. > warning: mksh: local (50-1) is newer than community (50b-1) > there is nothing to do Steps to reproduce: $ pacman -Syu :: Synchronising package databases... core is up to date extra is up to date community is up to date multilib is up to date :: Starting full system upgrade... warning: firefox: local (32.0-6) is newer than extra (32.0-1) warning: less: local (466-1) is newer than core (458-1) warning: mksh: local (50-1) is newer than community (50b-1) warning: parcellite: ignoring package upgrade (1.1.7-2 => 1.1.8-1) warning: xz: local (5.1.3alpha-1) is newer than core (5.0.5-2) there is nothing to do |
This task depends upon
Closed by Thorsten Töpper (Atsutane)
Sunday, 07 September 2014, 20:39 GMT
Reason for closing: Fixed
Additional comments about closing: Followed Dave's advise, thank you.
Sunday, 07 September 2014, 20:39 GMT
Reason for closing: Fixed
Additional comments about closing: Followed Dave's advise, thank you.
No amount of refreshing sync DBs will fix this. "50b" sorts older than "50" according to vercmp, but "50.b" does not:
$ printf %s\\n 50 50b 50.b | pacsort
50b
50
50.b