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#22664 - Pacman wants to install older package version
Attached to Project:
Pacman
Opened by sinister99 (sinister99) - Sunday, 30 January 2011, 03:40 GMT
Last edited by Dan McGee (toofishes) - Friday, 04 February 2011, 14:25 GMT
Opened by sinister99 (sinister99) - Sunday, 30 January 2011, 03:40 GMT
Last edited by Dan McGee (toofishes) - Friday, 04 February 2011, 14:25 GMT
|
DetailsSummary and Info:
I compiled and installed newer versions of e17 svn packages than are available in community (with makepkg), and pacman should mention that these packages are newer than community, but not replace them. However, for one of the packages I compiled, it wants to replace my newer version of the package with the older version in community. I can't see anything which would confuse pacman with version numbers being abnormal. Pacman correctly ignores all of the other new version of e17 packages I have installed, it just wants to downgrade evas-svn Steps to Reproduce: Compile and install the latest svn version of evas-svn. Pacman will want to downgrade the package on the next pacman -Syu 
error
(1.6 KiB)
|
This task depends upon
Closed by Dan McGee (toofishes)
Friday, 04 February 2011, 14:25 GMT
Reason for closing: Deferred
Additional comments about closing: epoch in 3.5 will make this less of a hassle in the future
Friday, 04 February 2011, 14:25 GMT
Reason for closing: Deferred
Additional comments about closing: epoch in 3.5 will make this less of a hassle in the future
Comment by Allan McRae (Allan) -
Sunday, 30 January 2011, 06:13 GMT
The PKGBUILD for evas-svn package in [community] has options=('force') in it, so this is expected behaviour.
Comment by Xavier (shining) -
Sunday, 30 January 2011, 11:13 GMT
This is just one of the annoying aspect of force that should be fixed with epoch in 3.5