Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#19639 - Packages with RC are considered newer
Attached to Project:
Pacman
Opened by Fred Morcos (fredmorcos) - Saturday, 29 May 2010, 11:49 GMT
Last edited by Dan McGee (toofishes) - Wednesday, 12 January 2011, 05:46 GMT
Opened by Fred Morcos (fredmorcos) - Saturday, 29 May 2010, 11:49 GMT
Last edited by Dan McGee (toofishes) - Wednesday, 12 January 2011, 05:46 GMT
|
DetailsSummary and Info:
I get this when running sudo pacman -Syu :: Synchronizing package databases... arch-games is up to date testing 24.4K 344.0K/s 00:00:00 [#####################] 100% core is up to date extra 453.1K 121.1K/s 00:00:04 [#####################] 100% community-testing is up to date community 363.8K 156.4K/s 00:00:02 [#####################] 100% :: Starting full system upgrade... warning: cryptsetup: local (1.1.1_rc2-1) is newer than testing (1.1.1-1) Steps to Reproduce: Run sudo pacman -Syu Expected Output: 1.1.1_rc2 should not be considered newer than 1.1.1 |
This task depends upon
Closed by Dan McGee (toofishes)
Wednesday, 12 January 2011, 05:46 GMT
Reason for closing: Won't fix
Additional comments about closing: Won't fix directly, but will be fixable with epoch support in 3.5.0.
Wednesday, 12 January 2011, 05:46 GMT
Reason for closing: Won't fix
Additional comments about closing: Won't fix directly, but will be fixable with epoch support in 3.5.0.
Comment by Allan McRae (Allan) -
Saturday, 29 May 2010, 12:33 GMT
1.1.1rc2 is not considered newer... The problem is that version numbering is never consistent. 1.0_a might be and upgrade to 1.0 or it might be an alpha release. We provide the "force" to deal with this.