Local package is newer than <repo>

Samisafool commented

2022-03-06 10:05:29 +01:00

warning: qt5-declarative: local (5.15.2+kde+r46-1.1) is newer than extra (5.15.2+kde+r46-1)
warning: qt5-multimedia: local (5.15.2-2.1) is newer than extra (5.15.2-2)
warning: qt5-networkauth: local (5.15.2-2.1) is newer than extra (5.15.2-2)
warning: qt5-quickcontrols2: local (5.15.2+kde+r11-2.1) is newer than extra (5.15.2+kde+r11-2)
warning: qt5-speech: local (5.15.2+kde+r3-1.1) is newer than extra (5.15.2+kde+r3-1)
warning: qt5-svg: local (5.15.2+kde+r16-2.1) is newer than extra (5.15.2+kde+r16-2)
warning: qt5-tools: local (5.15.2+kde+r17-6.1) is newer than extra (5.15.2+kde+r17-6)
warning: qt5-wayland: local (5.15.2+kde+r54-1.1) is newer than extra (5.15.2+kde+r54-1)
warning: qt5-webkit: local (5.212.0alpha4-11.1) is newer than extra (5.212.0alpha4-11)
warning: qt5-x11extras: local (5.15.2-2.1) is newer than extra (5.15.2-2)
warning: qt5-xmlpatterns: local (5.15.2-2.1) is newer than extra (5.15.2-2)

I keep getting this. Usually I fix it with pacman -Syuu, but I'm interested as to why it happens.

``` warning: qt5-declarative: local (5.15.2+kde+r46-1.1) is newer than extra (5.15.2+kde+r46-1) warning: qt5-multimedia: local (5.15.2-2.1) is newer than extra (5.15.2-2) warning: qt5-networkauth: local (5.15.2-2.1) is newer than extra (5.15.2-2) warning: qt5-quickcontrols2: local (5.15.2+kde+r11-2.1) is newer than extra (5.15.2+kde+r11-2) warning: qt5-speech: local (5.15.2+kde+r3-1.1) is newer than extra (5.15.2+kde+r3-1) warning: qt5-svg: local (5.15.2+kde+r16-2.1) is newer than extra (5.15.2+kde+r16-2) warning: qt5-tools: local (5.15.2+kde+r17-6.1) is newer than extra (5.15.2+kde+r17-6) warning: qt5-wayland: local (5.15.2+kde+r54-1.1) is newer than extra (5.15.2+kde+r54-1) warning: qt5-webkit: local (5.212.0alpha4-11.1) is newer than extra (5.212.0alpha4-11) warning: qt5-x11extras: local (5.15.2-2.1) is newer than extra (5.15.2-2) warning: qt5-xmlpatterns: local (5.15.2-2.1) is newer than extra (5.15.2-2) ``` I keep getting this. Usually I fix it with `pacman -Syuu`, but I'm interested as to why it happens.

anonfunc added the

question

label 2022-03-06 11:33:10 +01:00

anonfunc commented

2022-03-06 11:45:50 +01:00

Owner

This happens if ALHP removes a package (or packages) from the repo. There are multiple reasons why this can happen:

failing to build
some dependency is not up to date (and since ALHP does not know how long this goes on, removing is the saver option)
it is manually removed (which usually goes along with an issue here, showing some malfunction with the specific package)

This should overall happen seldom and even if they are removed they can reappear shortly after, so is the case with all packages you posted. They are currently waiting to go live as soon as the current build-cycle is finished.

EDIT: There is some room for improvement here of course. For example ALHP could drop them only after some time has passed and the missing dependency did not show up. Add that to the long todo list 😄

This happens if ALHP removes a package (or packages) from the repo. There are multiple reasons why this can happen: * failing to build * some dependency is not up to date (and since ALHP does not know how long this goes on, removing is the saver option) * it is manually removed (which usually goes along with an issue here, showing some malfunction with the specific package) This should overall happen seldom and even if they are removed they can reappear shortly after, so is the case with all packages you posted. [They are currently waiting to go live as soon as the current build-cycle is finished](https://alhp.harting.dev/packages.html#extra-x86-64-v3-qt5-declarative). *EDIT:* There is some room for improvement here of course. For example ALHP could drop them only after some time has passed and the missing dependency did not show up. Add that to the long todo list 😄

Samisafool commented

2022-03-06 14:57:21 +01:00

Author

Well, the same happened with gc and I don't think that showed up:

arch@arch ~ % pacman -Qi gc
Name            : gc
Version         : 8.2.0-2

Well, the same happened with `gc` and I don't think that showed up: ``` arch@arch ~ % pacman -Qi gc Name : gc Version : 8.2.0-2 ```

anonfunc commented

2022-03-06 15:32:00 +01:00

Owner

gc failed to build, as you can see here.

`gc` failed to build, as you can see [here](https://alhp.harting.dev/packages.html#core-x86-64-v3-gc).

Samisafool closed this issue

2022-03-06 16:46:10 +01:00

nojvspine commented

2025-06-06 07:49:57 +02:00

I think this is different issue than the one that was described. Packages in standart extra repo are tagged like version-1, while in ALHP extra it's version-1.1, and pacman thinks that it's a newer version, but compares with regular one, and says that local (from ALHP) is newer than official package.
Maybe there's some way to say pacman to look into these repos instead?

I think this is different issue than the one that was described. Packages in standart extra repo are tagged like version-1, while in ALHP extra it's version-1.1, and pacman thinks that it's a newer version, but compares with regular one, and says that local (from ALHP) is newer than official package. Maybe there's some way to say pacman to look into these repos instead?

Local package is newer than <repo> #104