Warning: Repository metadata expired

English Install/Boot/Login
1

So, I’m on 15.6 Leap Beta. At the command line to do a dup:

# zypper -vvvv dup
Verbosity: 3
Initializing Target
Checking whether to refresh metadata for Brave Browser - Beta
Checking whether to refresh metadata for google-chrome
Checking whether to refresh metadata for Update repository of openSUSE Backports
Checking whether to refresh metadata for Non-OSS Repository
Checking whether to refresh metadata for Open H.264 Codec (openSUSE Leap)
Checking whether to refresh metadata for Update repository with updates from SUSE Linux Enterprise 15
Checking whether to refresh metadata for Main Update Repository
Checking whether to refresh metadata for Update Repository (Non-Oss)
Loading repository data...
Warning: Repository 'Update Repository (Non-Oss)' metadata expired since 2023-09-21 07:47:58 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...
Warning: You are about to do a distribution upgrade
...
#

So there is the “metadata expired since 2023-09-21 07:47:58 CDT” error

I DID DO a “zypper ref” just before that output we see above, because I had done a zypper dup just moments before and read the error and suggestion, so executed the “ref”, then the “dup” again and still see the same error. If this is 15.6 beta, I wouldn’t think the metadata would be expired seven months ago.
Any hints for this?

2

Ignore this. This version is not even released yet, what updates do you expect?

3

Since this is beta software there is no need for a update repo so it may be that it is empty and unsigned until it reaches gold

1 Like
4

It’s a Beta, so I assume as development moves along to reach the final release , I would expect updates, here and there, as things are corrected or enhanced.

But okay, I’ll ignore it.

5

Do not confuse “updates” in its colloquial usage and “updates” in the SUSE repository management sense.

6

Thanks for the succinct answer.

Sidenote: it’s odd, then, that when I installed 15.6 Beta, it set this repo as Active … if it NEVER participates in a “dup” (during a Beta) , it should never have been added to begin with.

7

But then you would need to manually add it after the final software release. It does no harm, other than a message that you can ignore.

1 Like
8

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.