I checked the autorefresh, is it broken mirror or the server ?
paulparker@7400K-hxi52:~> sudo zypper up
Loading repository data...
Warning: Repository 'Update Repository (Debug)' metadata expired since 2024-09-19 23:35:41 AEST.
Warning: Repository 'Main Update Repository' metadata expired since 2024-09-19 23:35:39 AEST.
Warning: Repository metadata expired: Check if 'autorefresh' is turned on (zypper lr), otherwise
manually 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.
Reading installed packages...
Nothing to do.
paulparker@7400K-hxi52:~>
I wonder why you have a repo for debugging switched on.
I assume that there where no changes on that repo since long time. Then zypper warns because that could be because it is not refreshed, when only because of no activity on the repo it is only a remark.
The same could be true for the main update repo, except that it is logical to have it active, contrary to the one above.
Most updates to Leap come through SLE, the “Main Update Repository” (assuming it refers to the expected location) contains very few packages which are updated infrequently. So, it is sort of normal.
You may consider submitting bug report, but the only “solution” would be to push fake update (e.g. rebuilding some package just to bump its version).
I am not sure whether it is possible to change timeout or completely disable this check.
And for the future - repository names without URL are meaningless. Always show the output of zypper lr -d when you have some questions related to your repositories.
For a couple of days, I am getting similar messages. Thought they would just clear but hasn’t. No debug repo enabled. No recent changes made in repos.
(base) tom@mydesktop: ~ $ sudo zypper patch
Refreshing service 'NVIDIA'.
Refreshing service 'openSUSE'.
Loading repository data...
Warning: Repository 'oss-update(15.6)' metadata expired since 2024-09-19 08:35:39 CDT.
Warning: Repository 'update-oss (15.6)' metadata expired since 2024-09-19 08:35:39 CDT.
Warning: Repository metadata expired: Check if 'autorefresh' is turned on (zypper lr),
otherwise manually 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.
Reading installed packages...
Resolving package dependencies...
The following 2 items are locked and will not be changed by any action:
Available:
Mesa-dri-nouveau vlc-beta
Nothing to do.
(base) tom@mydesktop: ~ $
Apart from the fact that these warnings point to the same: no changes in those repos for a long time, thus no change to the metadata. Just a warning, I am wondering why you have two repos called oss-update and update-oss. Aren’t they the same? Better look at
zypper lr -d
or post it here when you want help with the interpretation.
Didn’t that thread explain that you can delete those two services and live on like before?
Or remove your old ones, that are now duplicates of those installed by the services and use those.
There is no need to have such a confusing long list, but you decide.
To summarize: 1-No repo rpms installed or installable; 2-immutable empty repo*repo files; 3-no installed packages with case insensitive string “nvidia” in name, not even firmware.
Yes added repos are not enabled. I did see about removing these services and moving on as before but did not get it done yet.
If I delete
openSUSE-repos-Leap
openSUSE-repos-Leap-NVIDIA
do I need to “taboo” them or will they keep getting added back in with updates?
If you have Nvidia hardware, the openSUSE-repos-<yourflavorhere>-NVIDIA package gets installed automatically (as recommends) which also pulls in openSUSE-repos-<yourflavorhere>.
These packages makes repo management way easier for ppl which have difficulties to maintain a proper set of repos. Simply use these two packages which will take care (via a service) that you always have valid repos and URLS for openSUSE.
If you have experience how to add, remove, modify and maintain a proper set of openSUSE repos you may decide to uninstall the two packages which in return will remove the service and managed repos.
But as long as you don’t know how to do this…stick to the repo packages.
I saw the same error, but only yesterday (it expired yesterday about 9:30am) … but it’s been fixed now … it’s because the key expired (read the output) yesterday. If you read the following , it shows that it’s been updated (for us, anyway)
Look for the “details here” section I highlighted.
# zypper -vvvv up
Verbosity: 3
Initializing Target
Checking whether to refresh metadata for Leap 15.6 Main repo
Retrieving: https://download.opensuse.org/geoip .....................................................................[done (84 B/s)]
Retrieving: https://download.opensuse.org/distribution/leap/15.6/repo/oss/repodata/repomd.xml ...................[done (11.1 KiB/s)]
Checking whether to refresh metadata for Brave Browser - Beta
Retrieving: https://brave-browser-rpm-beta.s3.brave.com/x86_64/repodata/repomd.xml ...........................................[done]
Checking whether to refresh metadata for google-chrome
Retrieving: https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/repomd.xml .........................................[done]
Checking whether to refresh metadata for Update repository of openSUSE Backports
Retrieving: http://download.opensuse.org/update/leap/15.6/backports/repodata/repomd.xml ......................................[done]
Checking whether to refresh metadata for Non-OSS Repository
Retrieving: http://download.opensuse.org/distribution/leap/15.6/repo/non-oss/repodata/repomd.xml .............................[done]
Checking whether to refresh metadata for Open H.264 Codec (openSUSE Leap)
Retrieving: http://codecs.opensuse.org/openh264/openSUSE_Leap/repodata/repomd.xml ................................[done (1.7 KiB/s)]
Checking whether to refresh metadata for Update repository with updates from SUSE Linux Enterprise 15
Retrieving: http://download.opensuse.org/update/leap/15.6/sle/repodata/repomd.xml ............................................[done]
Retrieving: http://download.opensuse.org/update/leap/15.6/sle/repodata/repomd.xml.asc ..............................[done (827 B/s)]
Retrieving: http://download.opensuse.org/update/leap/15.6/sle/repodata/repomd.xml.key ............................[done (1.6 KiB/s)]
Retrieving: http://download.opensuse.org/update/leap/15.6/sle/repodata/repomd.xml ................................[done (3.0 KiB/s)]
Repository: Update repository with updates from SUSE Linux Enterprise 15
Key Fingerprint: 7F00 9157 B127 B994 D5CF BE76 F74F 09BC 3FA1 D6CE
Key Name: SUSE Package Signing Key <build@suse.de>
Key Algorithm: RSA 4096
Key Created: Thu Jan 19 07:39:40 2023
Key Expires: Mon Jan 18 07:39:40 2027
Rpm Name: gpg-pubkey-3fa1d6ce-63c9481c
Retrieving: http://cdn.opensuse.org/update/leap/15.6/sle/repodata/703ca0cfb5bfa83e19b11c0561ed3eeda0b4a27143bc03[done (901.3 KiB/s)]
Retrieving: http://cdn.opensuse.org/update/leap/15.6/sle/repodata/0b2523855b1743c7f216a6e570c7fb2a38d9d1dd8b3f306[done (14.1 MiB/s)]
Retrieving: http://cdn.opensuse.org/update/leap/15.6/sle/repodata/421ba96672fee04ae7a6727e2e689567d662503e2eb0f9[done (184.9 KiB/s)]
Retrieving: http://cdn.opensuse.org/update/leap/15.6/sle/repodata/8ba9a86b788e246e13d8b64992cd52e02b1e2a7f94ce1aff190781606526[done]
Retrieving repository 'Update repository with updates from SUSE Linux Enterprise 15' metadata ................................[done]
Building repository 'Update repository with updates from SUSE Linux Enterprise 15' cache .....................................[done]
Checking whether to refresh metadata for Main Update Repository
Retrieving: http://download.opensuse.org/update/leap/15.6/oss/repodata/repomd.xml ................................[done (3.0 KiB/s)]
Retrieving: http://download.opensuse.org/update/leap/15.6/oss/repodata/repomd.xml.asc ..............................[done (827 B/s)]
Retrieving: http://download.opensuse.org/update/leap/15.6/oss/repodata/repomd.xml.key ............................[done (1.6 KiB/s)]
Retrieving: http://download.opensuse.org/update/leap/15.6/oss/repodata/repomd.xml ................................[done (1.1 KiB/s)]
Repository: Main Update Repository
Key Fingerprint: AD48 5664 E901 B867 051A B15F 35A2 F86E 29B7 00A4
Key Name: openSUSE Project Signing Key <opensuse@opensuse.org>
Key Algorithm: RSA 4096
vvvvvvvvvvvvvv---- details here ----vvvvvvvvvvv
Key Created: Mon Jun 20 09:03:14 2022
Key Expires: Fri Jun 19 09:03:14 2026
^^^^^^^^^^^^^^---- details here ----^^^^^^^^^^
Rpm Name: gpg-pubkey-29b700a4-62b07e22
Retrieving: http://cdn.opensuse.org/update/leap/15.6/oss/repodata/10d67de38212e51de0222802c227f48da1c882beb8e8cb47df5647d45fcc[done]
Retrieving: http://cdn.opensuse.org/update/leap/15.6/oss/repodata/fe3a3e74929e2d69f49983e0fcb58aaa0e03dd7e77bed862c096dcac2614[done]
Retrieving: http://cdn.opensuse.org/update/leap/15.6/oss/repodata/5afc6cb78c11733eb7ae0cd9dfefc5a37fba3d6530ec285484cf419be9bc[done]
Retrieving: http://cdn.opensuse.org/update/leap/15.6/oss/repodata/0f5245a8406590ca5bb330ece7dcb37a5f95452bd86b60d0c017a8fb30da[done]
Retrieving repository 'Main Update Repository' metadata ......................................................................[done]
Building repository 'Main Update Repository' cache ...........................................................................[done]
Checking whether to refresh metadata for Update Repository (Non-Oss)
Retrieving: http://download.opensuse.org/update/leap/15.6/non-oss/repodata/repomd.xml ............................[done (2.6 KiB/s)]
Loading repository data...
Reading installed packages...
Force resolution: No
The following package is going to be upgraded:
wpa_supplicant
2.10-150600.5.4 -> 2.10-150600.7.3.1 x86_64 Update repository with updates from SUSE Linux Enterprise 15
SUSE LLC <https://www.suse.com/>
1 package to upgrade.
Package download size: 1.4 MiB
Package install size change:
| 6.1 MiB required by packages that will be installed
374 B | - 6.1 MiB released by packages that will be removed
Backend: classic_rpmtrans
Continue?
This is from yesterday, showing the error
Checking whether to refresh metadata for Update Repository (Non-Oss)
Loading repository data...
Warning: Repository 'Main Update Repository' metadata expired since 2024-09-19 08:35:39 CDT.
Warning: Repository metadata expired: Check if 'autorefresh' is turned on (zypper lr), otherwise
manually 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.
Reading installed packages...
I removed the packages:
openSUSE-repos-Leap
openSUSE-repos-Leap-NVIDIA
I readjusted the repos and rebooted.
Now I am getting nvidia repo error:
(base) tom@mydesktop: ~ $ sudo zypper patch
[sudo] password for root:
Refreshing service 'NVIDIA'.
Specified path '/usr/share/zypp/local/service/NVIDIA' is not a directory: dir:/usr/share/zypp/local/service/NVIDIA?cookies=0
Abort, retry, ignore? [a/r/i/...? shows all options] (a): i
Unexpected exception.
SKIP request: User-requested skipping of a file
History:
- Specified path '/usr/share/zypp/local/service/NVIDIA' is not a directory: dir:/usr/share/zypp/local/service/NVIDIA?cookies=0
Please file a bug report about this.
See http://en.opensuse.org/Zypper/Troubleshooting for instructions.
(base) tom@mydesktop: ~ $
There is no directory /usr/share/zypp/local… Only directory under zypp is /schemas
I removed and re-added nvida repo through community repo steps in yast software.
I checked and all nvidia G06 apps are still installed.
Here’s what happened on your machine, as well as all our machines … check my previous post ( #14 ) … yesterday, in the morning, the key expired , which is why we all got the error (we got the same exact error you show in your first post) .
openSUSE updated the key today ( check post #14 ) … so while you were busy making changes, the key was changed , and of course, now you do not see any errors anymore … it was just ironic that while you were attempting a fix, the key was updated, so why you don’t see the error anymore
The fact is, the key expired, which is a potential security concern - that’s enough of an issue to focus on (a warning and an error are both considered an ‘issue’). As a 30+ year software engineer, I was a bit concerned of the expiration.
Warnings call your attention to an exception condition. The condition might not be an error, but can cause problems if not resolved.