[arch-general] Which version gets installed by pacman?
Can someone explain this to me: 1) Check available versions $ pacman -Si kdepim | grep Version Version : 3.5.9-2 Version : 3.5.9.20080501-0.1 Ok, which version is newest? $ vercmp '3.5.9-2' '3.5.9.20080501-0.1' -1 Hmmm $ vercmp usage: vercmp <ver1> <ver2> return values: < 0 : if ver1 < ver2 0 : if ver1 == ver2
0 : if ver1 > ver2
Ok, version 3.5.9.20080501-0.1 is newer, so try to install it: $ sudo pacman -S kdepim :: kdepim is in IgnorePkg/IgnoreGroup. Install anyway? [Y/n] warning: kdepim-3.5.9-2 is up to date -- reinstalling resolving dependencies... looking for inter-conflicts... Targets: kdepim-3.5.9-2 Total Download Size: 0,00 MB Total Installed Size: 20,52 MB Proceed with installation? [Y/n] n $ Why did not pacman choose the newer version to install?
On Tue, 2008-05-06 at 08:45 +0200, Karolina Lindqvist wrote:
Can someone explain this to me: 1) Check available versions $ pacman -Si kdepim | grep Version Version : 3.5.9-2 Version : 3.5.9.20080501-0.1
Ok, which version is newest?
$ vercmp '3.5.9-2' '3.5.9.20080501-0.1' -1
Hmmm
$ vercmp usage: vercmp <ver1> <ver2>
return values: < 0 : if ver1 < ver2 0 : if ver1 == ver2
0 : if ver1 > ver2
Ok, version 3.5.9.20080501-0.1 is newer, so try to install it:
$ sudo pacman -S kdepim :: kdepim is in IgnorePkg/IgnoreGroup. Install anyway? [Y/n] warning: kdepim-3.5.9-2 is up to date -- reinstalling resolving dependencies... looking for inter-conflicts...
Targets: kdepim-3.5.9-2
Total Download Size: 0,00 MB Total Installed Size: 20,52 MB
Proceed with installation? [Y/n] n $
Why did not pacman choose the newer version to install?
Simple: it installs the first entry it finds in the repositories that are in pacman.conf. There's no such thing as installing the latest available version.
tisdagen den 6 maj 2008 skrev Jan de Groot:
Simple: it installs the first entry it finds in the repositories that are in pacman.conf. There's no such thing as installing the latest available version.
Ok, that explains a lot of things. I reorder my pacman.conf entries, and then it does it right. But I have to keep track on updates myself, I guess.
On Tue, 2008-05-06 at 09:54 +0200, Karolina Lindqvist wrote:
tisdagen den 6 maj 2008 skrev Jan de Groot:
Simple: it installs the first entry it finds in the repositories that are in pacman.conf. There's no such thing as installing the latest available version.
Ok, that explains a lot of things. I reorder my pacman.conf entries, and then it does it right. But I have to keep track on updates myself, I guess.
In standard pacman.conf this behaviour is necessary, because otherwise pacman would install testing-packages (for example) just because they have higher version. And that wouldn't be too good in some cases.
On Tue, May 6, 2008 at 4:00 PM, Timm Preetz <timm@preetz.us> wrote:
In standard pacman.conf this behaviour is necessary, because otherwise pacman would install testing-packages (for example) just because they have higher version.
And that wouldn't be too good in some cases.
If you want to use testing, it's recommended to use all of it, for obvious linking reasons. That's why testing appears first in pacman.conf (but is disabled by default).
2008/5/6 Xavier <shiningxc@gmail.com>:
On Tue, May 6, 2008 at 4:00 PM, Timm Preetz <timm@preetz.us> wrote:
In standard pacman.conf this behaviour is necessary, because otherwise pacman would install testing-packages (for example) just because they have higher version.
And that wouldn't be too good in some cases.
If you want to use testing, it's recommended to use all of it, for obvious linking reasons. That's why testing appears first in pacman.conf (but is disabled by default).
Sometimes it is useful to have testing after all other repos though. For example, I have testing after all repos and when a dev asks to signoff some package - I just do pacman -S testing/somepackage to download only that package. -- Roman Kyrylych (Роман Кирилич)
participants (5)
-
Jan de Groot
-
Karolina Lindqvist
-
Roman Kyrylych
-
Timm Preetz
-
Xavier