When pacman syncs a package that is present in multiple repositories, it always does from the repo listed first, no matter if the package version is older in that repo.

But it doesn't happen the same while upgrading.

If you have the package already installed in your system, with the same or lower version than the first repo, pacman won't upgrade to the repo package.

This inconsistency can be problematic in a bunch of situation. For example if the repo has arranged the dependencies in certain way, or if the repo expected to link against certain soname.

I would argue that if the package in the repo has at least the same version than the one in the system, but it was installed from a different origin, it shall upgrade if the `--needed` option isn't present.

Otherwise the first behavior of syncing from the first repo package is effectively broken, and any personal repo rearranging deps or sonames must use `epoch` to force upgrade.