Bugzilla – Bug 1211775
repo http://download.opensuse.org/update/leap/15.4/oss : metadata expired
Last modified: 2023-05-29 17:56:15 UTC
zypper up reports the following warning Loading repository data... Warning: Repository 'Main Update Repository' metadata expired since 2023-05-27 05:03:47 CDT. Warning: Repository metadata expired: Check if 'autorefresh' is turned on (zypper lr), otherwise manualy refresh the repository (zypper ref). If this does not solve the issue, it could be that you are using a broken mirror or the server has actually discontinued to support the repository. A). zypper ref does not solve the issue B). repo definitions/info Name : Main Update Repository URI : http://download.opensuse.org/update/leap/15.4/oss Enabled : Yes GPG Check : (r ) Yes Priority : 99 (default priority) Autorefresh : On Keep Packages : Off Type : rpm-md
From https://download.opensuse.org/update/leap/15.4/oss/repodata/5afc6cb78c11733eb7ae0cd9dfefc5a37fba3d6530ec285484cf419be9bc7e84-suseinfo.xml.gz > <suseinfo xmlns="http://linux.duke.edu/metadata/repo"> > <expire>2592000</expire> > </suseinfo> That's 60*60*24*30. > $ osc log openSUSE:Leap:15.4:Update | head > ---------------------------------------------------------------------------- > r35 | maintenance-robot | 2023-04-27 10:01:45 | cb6bface00303365ed2a5f7be61f1982 | > None | rq1080165 > > Releasing from project openSUSE:Maintenance:17889 the update openSUSE-2023-95 So this is expected, we simply have not released anything into this repository in 30 days. The code reference: https://github.com/openSUSE/zypper/blob/9430047c4c608248a3a7b5b8cfa0a24d2b8d7b83/src/repos.cc#L1825 So the message itself is harmless. Maintenance team, you could make a one-off noop change to the repo to make it re-publish the metadata. Otherwise this will self-correct upon the next update. One thing is strange: zypper knows from it's own configuration whether auto-refresh is enabled. Why does it tell the user to check it? Worth a split-out bug to the zypper team
*** Bug 1211776 has been marked as a duplicate of this bug. ***
i deleted a incorrect update instead, but will also push a refresh of yast2-theme anyway.
(In reply to Marcus Meissner from comment #3) > i deleted a incorrect update instead, but will also push a refresh of > yast2-theme anyway. The problem is fixed sudo zypper up -r xx [sudo] password for root: Retrieving repository 'Main Update Repository' metadata ................................................................................[done] Building repository 'Main Update Repository' cache .....................................................................................[done] Loading repository data... Reading installed packages... Nothing to do. Thanks. ND