FS#65431 - pacman does not see an update if the newer version of the package is in the new repo

Attached to Project: Pacman
Opened by Alex (__AlexL__) - Sunday, 09 February 2020, 09:01 GMT
Last edited by Allan McRae (Allan) - Sunday, 09 February 2020, 10:46 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version 5.2.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:
pacman does not see an update if the newer version of the package is in the new repo.
For example: now I have autoconf-2.69-6 installed.
core has autoconf-2.69-6
extra has autoconf-2.69-7
But pacman -Syu updates nothing.

Steps to Reproduce:
have autoconf-2.69-6 installed
execute pacman -Syu
This task depends upon

Closed by  Allan McRae (Allan)
Sunday, 09 February 2020, 10:46 GMT
Reason for closing:  Not a bug
Comment by morganamilo (morganamilo) - Sunday, 09 February 2020, 09:16 GMT
This is how pacman checks for upgrades and is by design. What you've described is either an issue with a mirror or a packing error.

You should probably file a bug against core instead.
Comment by Alex (__AlexL__) - Sunday, 09 February 2020, 10:25 GMT
It is very bad designb and it is very possible situation when two (or more then two) different repos can have the same packages with the different versions.
If these packages have the same versions the user must be asked about his/her preference and if there is the one with higher version then this one must be treated as a update.
You just don't want fixing this.
Comment by Allan McRae (Allan) - Sunday, 09 February 2020, 10:46 GMT
The user is given a choice. They can order repos with their preferred priority. And if they want to install from the other repo, they can do that manually.

Loading...