The package information is present in db, but the package itself is absent on the servers:
To upgrade (4):
fzf 0.28.0-1 (0.27.3-1) community 997.5 kB
kpmcore 21.08.3-1.1 (21.08.2-1.1) extra 691.4 kB
libreoffice-still 7.1.7-1 (7.1.6-3) extra 142.3 MB
npm 8.1.3-1 (8.1.2-1) community 1.4 MB
Total download size: 145.4 MB
Total installed size: -43 bytes
Apply transaction ? [y/N] y
Download of fzf (0.28.0-1) started
171.8 kB/145.4 MB
https://manjaro.mirrors.lavatech.top/unstable/extra/x86_64/kpmcore-21.08.3-1.1-x86_64.pkg.tar.zst: Error 404
515.8 kB/145.4 MB
https://mirror.koddos.net/manjaro/unstable/extra/x86_64/kpmcore-21.08.3-1.1-x86_64.pkg.tar.zst: Error 404
Download of npm (8.1.3-1) started
Download of fzf (0.28.0-1) finished
1.2 MB/145.4 MB
https://ftp.nluug.nl/pub/os/Linux/distr/manjaro/unstable/extra/x86_64/kpmcore-21.08.3-1.1-x86_64.pkg.tar.zst: Error 404
Download of libreoffice-still (7.1.7-1) started
Download of npm (8.1.3-1) finished
25.6 MB/145.4 MB
...
What’s the proper way to report an mirror problem?
Or just do not report it and server maintainer will know that problem or such problem will be automatically resolved with no any report needed?
The question covers only Manjaro infrastructure, I know that a user can switch to another server in order to get a package from them if it was not deleted by some broadcast command from all servers but unfortunately leaved a db file untouched so it continues containing that package info.
PS
Probably I got it: it is the problem which should be report: I assume that issues goes like this: a central server lacks the package and all mirror servers just downloads all the stuff: DBs, package files from central server and the error is that central server lacks the file, so it should be reported. Am I right on that assume or how the infrastructure works and what’s the error propagation source?
