We are tracking this in ALHP/alhp-keyring#4. I'll try to get a new cache purge mechanism going this weekend.
You would need to modify ALHP to use Manjaro's "stable" repository. Since ALHP uses the (state repository)[https://gitlab.archlinux.org/archlinux/packaging/state], you would have to find a Manjaro…
@mihalycsaba You seem to have a different problem, have a look at ALHP/alhp-keyring#4.
Not sure its a good idea to close this, I think we should try to solve this instead of recommending switching mirrors. The CDNs probably have a cache purge problem, I'll try to implement a…
Not sure how you jumped to the conclusion its expired, because its certainly not:
pacman-key -l cie@harting.dev …
Yes I considered that. Would add a lot of packages of course, but it would present at least some of these windows where one can potentially break something. Need to think about that, because its…
Hm, seems to be a cache purge problem. We had a few reports in the last weeks that signatures didn't match the database (or vice versa). Maybe the purging needs to be more explicit, I think that's…
Good news :)
Did you maybe hit https://gitlab.archlinux.org/archlinux/packaging/packages/gettext/-/issues/3?
Yes.
Does it work with
0.22.5-2.1?Well, the files are still not there,…
and then update with
pacman -Syu --assume-installed tinysparqlThat looks cleaner, but I also have no way to test that atm.
wouldn't that leave the…
To come back to the underlying problem, I'm not sure we can do much here that would not involve PKGBUILD editing.
If this stays an isolated case, then I think pinning this issue should suffice.
Would it be possible to first remove tracker3 with
pacman -R tracker3 --assume-installed tracker3
and then update with
pacman -Syu --assume-installed tinysparql
That…
Is this solved by adding --assume-installed tinysparql and/or --assume-installed tracker3?