On Mon, 2018-05-07 at 09:27 +0200, Dominique Leuenberger / DimStar wrote:
On Sun, 2018-05-06 at 13:42 +0200, Daniele wrote:
HI, # zypper ref -f Forcing raw metadata refresh Retrieving repository 'Repository principale (NON-OSS)' metadata ............................................................................................................................................................................[done] Forcing building of repository cache Building repository 'Repository principale (NON-OSS)' cache .................................................................................................................................................................................[done] Forcing raw metadata refresh Retrieving repository 'Repository principale (OSS)' metadata -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------[|] File './repodata/a8542a7b35e96dad2d79bacc5f1d307ddace9cff19317893cf1269eb0238d9d2-appdata-icons.tar.gz' not found on medium 'http://download.opensuse.org/tumbleweed/repo/oss/' Abort, retry, ignore? [a/r/i/...? shows all options] (a):
Hi All - we're currently looking into this issue. That file did exist at one point (which is why it is totally correclty registered in the repo metadata) but got 'lost' on the server(s) - this is not a mirror issue, but comes from the central infra directly. Hope to be able to get you more information about this issue soon.
Good news: together with Ludwig Nussel the issue has been analyzed, identified and fixed - the repo should thus be working again (some openQA tests already confirmed it being ok again) Background: The script in use, that allows us to retain obsolete files once a new snapshot comes out (mainly used to keep the old RPMs around for immediate downgrades) was getting confused because the AppStream icon tarball had a name switch in one of the snapshots (so FOO->BAR->FOO). This is something that CAN happen (mainly happens when two packages provide the same application/icons - and the data flips between the two packages). The script thus knew that after the name changed to BAR, it could drop FOO, but missed the fact that FOO re-appeared later on in the FTP tree. This was further enhanced in the code to ensure the remover won't drop stuff that is supposed to exist in the target tree, even though it was marked earlier for removal. Cheers, Dominique