openSUSE / openSUSE/MirrorCache

Failed to retrieve new repository metadata from http://mr.heru.id (OpenSUSE Tumbleweed Non OSS)

Open
#595 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Perl
Stars
50
Forks
23
PR merge metrics
No merged PRs in 30d

Description

I tried to update my OpenSUSE Tumbleweed on 4 June 2025, but when I ran sudo zypper up, this message showed up:

`Retrieving repository 'Main Repository (NON-OSS)' metadata .............................................................................................................................[error]
Repository 'Main Repository (NON-OSS)' is invalid.
[download.opensuse.org-non-oss|http://download.opensuse.org/tumbleweed/repo/non-oss/] Failed to retrieve new repository metadata.
History:

  • File './repodata/f0c3eae9ed28db3b70a2740fe48f9e3b4f1b8a4feb20fb5540b4359d7d2f28f3-primary.xml.gz' not found on medium 'http://mr.heru.id/opensuse/tumbleweed/repo/non-oss/'
    Please check if the URIs defined for this repository are pointing to a valid repository.
    Skipping repository 'Main Repository (NON-OSS)' because of the above error.`

This error is only found in the Non-OSS repo, there is no issue in any other repos.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by checking the MirrorCache redirect for the non-OSS repository URL and whether the referenced metadata is available through the selected mirror, using the reported zypper error as the reproduction. Compare this repository with the other working repositories. Done means the non-OSS repository metadata can be retrieved successfully without the reported missing-file error.

Written by the indexing model from the issue text.

Assessment

Tech stack
perl
Domain
infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.