You are not logged in.
I am not sure if this question is on the proper question.
Plz move it - if necessary.
I've made a custom repo and build a package from abs, changing first the version.
$ sudo pacman -Ss ntfs-3g
extra/ntfs-3g 2012.1.15-4
Stable read and write NTFS driver
repo/ntfs-3g 2012.1.15-5
Stable read and write NTFS driverbut when i am trying to install ntfs-3g, it chooses the smaller version
$ sudo pacman -S ntfs-3g
resolving dependencies...
looking for inter-conflicts...
Targets (1): ntfs-3g-2012.1.15-4
Total Download Size: 0,24 MiB
Total Installed Size: 0,87 MiB
Proceed with installation? [Y/n] nWhat i am doing wrong ?
Last edited by ebal (2012-12-21 18:59:24)
https://balaskas.gr
Linux System Engineer - Registered Linux User #420129
Offline
pacman will choose the package from the repo that is defined first in you pacman.conf.
Offline
why not choosing the package with the greater version ?
is that a bug ?
https://balaskas.gr
Linux System Engineer - Registered Linux User #420129
Offline
yes, i understand that - i've read pacman.conf already.
I just dont understand why from the repos pacman dont choose the greater version.
If the packages have the same version, it's clear that pacman should choose the package by order.
But with diferrent versions .... it should choose the greater version.
https://balaskas.gr
Linux System Engineer - Registered Linux User #420129
Offline
....pacman should choose...
...is wrong. User should chose what computer will do, not the other way around. In your pacman.conf, you gave pacman the order of preference for your repositories, and now pacman follows and respects that order of prefference.
Are you saying that pacman is faulty cause it does exactly what you told him to do?
...why from the repos pacman dont choose the greater version...
Guess what, some people actually want pacman to choose lesser version, cause that lesser version might be explicit dependancy for a package from same repo (greater version won't work).
And, again, that's not pacman's fault. Sometimes you have to go with the flow, see the whole picture to understand it, instead of complaining right away.
Offline
i'm pretty sure it's not the version that matters.
let's take pacman -S foo as example.
pacman searches for foo in the first configured repo, if foo is present there it STOPS searching and will install that version.
If foo is not found in the first repo, it searches the 2nd . if present foo will be installed, if not, onto 3rd repo etc .
In short , if you have the same package in multiple repos, pacman only sees the first one it finds.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
pamcan -Ss
doesnt stop on the first repo, why pacman -S should ?
I dont have an actual problem - i am trying to understand the logic behind that.
In my opinion (and if i am the only one - i'll stop, it shouldnt stop at the first repo)
https://balaskas.gr
Linux System Engineer - Registered Linux User #420129
Offline
Imagine you add a custom repo of the end of your pacman.conf. Now that repo thinks they are awesome and adds a linux-9999-1 package. With [core] above that repo in pacman.conf, you are safe and using the Arch Linux kernel package.
You can always explicitly install from a repo further down the list if needed.
Offline
(i am not sure) but isnt that the same with a custom build of linux-9999-1 package and use pacman -U linux.pkg.tar.xz ?
I think that if you are using a custom repo is to do exactly this. Build a package that you want to "upgrade/overwrite" from a "default" repo.
Move it above core repo ... is like breaking your own system and then blame ... you !
https://balaskas.gr
Linux System Engineer - Registered Linux User #420129
Offline