Main Repository (Non-OSS) and (OSS) Are Not Valid

stevekovacs · October 4, 2024, 3:17pm

Last night I got the usual update notice in the system tray. Tried the usual sudo zypper dup, got this:

Retrieving repository 'Main Repository (NON-OSS) (20240908)' metadata .................................................................................................................................................................................................[error]
Repository 'Main Repository (NON-OSS) (20240908)' is invalid.
[download.opensuse.org-non-oss|http://download.opensuse.org/history/20240908/tumbleweed/repo/non-oss/] Valid metadata not found at specified URL
History:
 - [download.opensuse.org-non-oss|http://download.opensuse.org/history/20240908/tumbleweed/repo/non-oss/] Repository type can't be determined.

Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'Main Repository (NON-OSS) (20240908)' because of the above error.
Retrieving repository 'Main Repository (OSS) (20240908)' metadata .....................................................................................................................................................................................................[error]
Repository 'Main Repository (OSS) (20240908)' is invalid.
[download.opensuse.org-oss|http://download.opensuse.org/history/20240908/tumbleweed/repo/oss/] Valid metadata not found at specified URL
History:
 - [download.opensuse.org-oss|http://download.opensuse.org/history/20240908/tumbleweed/repo/oss/] Repository type can't be determined.

Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'Main Repository (OSS) (20240908)' because of the above error.

Are the repositories down? Same situation this morning.

The weird part is that on my other box, the Beelink, the update went through fine. On the box with the problem, I can go into Yast and refresh the repositories without any problem.

Here is the output of zypper lr -d

# | Alias                            | Name                                   | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                    | Service
--+----------------------------------+----------------------------------------+---------+-----------+---------+----------+--------+------------------------------------------------------------------------+--------
1 | download.opensuse.org-non-oss    | Main Repository (NON-OSS) (20240908)   | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/history/20240908/tumbleweed/repo/non-oss/ | 
2 | download.opensuse.org-oss        | Main Repository (OSS) (20240908)       | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/history/20240908/tumbleweed/repo/oss/     | 
3 | download.opensuse.org-tumbleweed | Main Update Repository                 | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/tumbleweed/                        | 
4 | google-chrome                    | google-chrome                          | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | https://dl.google.com/linux/chrome/rpm/stable/x86_64                   | 
5 | microsoft-edge                   | microsoft-edge                         | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | https://packages.microsoft.com/yumrepos/edge/                          | 
6 | packman                          | Packman                                | Yes     | (r ) Yes  | Yes     |   90     | rpm-md | https://ftp.fau.de/packman//suse/openSUSE_Tumbleweed/                  | 
7 | repo-debug                       | openSUSE-Tumbleweed-Debug              | No      | ----      | ----    |   99     | N/A    | http://download.opensuse.org/debug/tumbleweed/repo/oss/                | 
8 | repo-openh264                    | Open H.264 Codec (openSUSE Tumbleweed) | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed                | 
9 | repo-source                      | openSUSE-Tumbleweed-Source             | No      | ----      | ----    |   99     | N/A    | http://download.opensuse.org/source/tumbleweed/repo/oss/

I went to this URL: http://download.opensuse.org/history/20240908/tumbleweed/repo/non-oss/ | and it says “Resource no long available”.

Are they migrating the repositories and there has been something messed up?

nrickert · October 4, 2024, 3:21pm

You are using history repos.

The history is not kept forever. Perhaps it has aged out.

malcolmlewis · October 4, 2024, 3:21pm

@stevekovacs Hi, yes, the history repositories only keep X days, so they disappear over time.

Disable/remove 1 and 2…

https://download.opensuse.org/history/ 20240909 is the oldest now…

stevekovacs · October 4, 2024, 3:26pm

I’m confused. Why would I be using “history repos”? I never even heard of that.

panorain · October 4, 2024, 3:35pm

What about remove ,

out of url in 1 and 2 ?

malcolmlewis · October 4, 2024, 3:40pm

@stevekovacs only you know , are you using tumbleweed-cli? So you would need to add the starndard oss and non-oss repos and zypper dup

stevekovacs · October 4, 2024, 3:44pm

I just now removed the Main OSS and Non-OSS and reinstalled them manually using the links from the openSUSE Repositories article. I did a refresh and a massive number of packages need to be updated, 1,030 to be exact. I’m going to be upgraded from openSUSE Tumbleweed 20240908-0 → 20241002-0.

I have been noticing lately that when I do updates on this box, they are not that big. On the other box, I’ve gotten updates that were bigger. I couldn’t figure out why I was getting updates on that box when I wasn’t getting the same updates on the main box.

So apparently I’ve been stuck on an old version of Tumbleweed? How does that happen? How can I prevent that from happening again?

hui · October 4, 2024, 3:46pm

Normaly it does not happen on its own. See how tumbleweed-cli affects your repos and upgrade procedure:

Do you remember to have done something like that?

stevekovacs · October 4, 2024, 3:52pm

I asked Llama 3.2 AI about this and this is what it said:

You were likely stuck on a “history repository” due to the automatic repository cleanup feature in openSUSE Tumbleweed. If ‘zypper’ or ‘zypper dup’ fails to update the repositories for an extended period, the system can switch to a history repository to maintain a working package state. This is done to prevent the system from becoming unstable or broken.

It’s possible that your internet connection or the repositories were temporarily unavailable, leading to the automatic switch to a history repository. This switch can happen without warning, and it may not be immediately apparent that you’re no longer on the main repositories.

The Github article referenced above is referring to the management of snapshots. I’ve never used tumbleweed-cli.

The only time I’ve ever used snapshots is when we had that issue with Mesa corrupting the system and I had to revert back to a previous snapshot. That was months ago. At that time I used the snapper utility to revert back.

How can zypper dup have been stuck on a month-old repository if I did regular zypper dups since?

hui · October 4, 2024, 4:14pm

The Llama output seems quite wrong. There is nothing like automatic repository cleanup feature.

stevekovacs · October 4, 2024, 4:25pm

Well, that wouldn’t surprise me; AIs get it wrong all the time.

Anyway I did the dup, and now everything is back to normal.

What command should I run periodically to make sure zypper hasn’t gotten “stuck” again? As an aside, I don’t think this should be possible, whether or not the AI got it right. I certainly never added the Main respositories from the archives at any time.

OrsoBruno · October 4, 2024, 4:55pm

Might be pure coincidence, but you had problems about that date:
https://forums.opensuse.org/t/firefox-129-0-1-tabs-crashing-frequently-after-last-update/178485
Did you try to recover old versions of something to solve that (or other) problem, and doing that inadvertently loaded the history repo?

stevekovacs · October 4, 2024, 7:36pm

I actually can’t remember what I did, but I’m pretty sure I didn’t do anything with the openSUSE repos for that issue. At some point the tabs crashing reduced to just occasionally now (had one yesterday), but nothing like it was at that time. I suspect I didn’t actually do anything. Maybe I reinstalled Firefox, but that wouldn’t have required doing anything with the repos.

I’m chalking it up to a random zypper glitch of some sort.

system · November 3, 2024, 7:37pm

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