Bug 1187327 - [riscv64] Tumbleweed update repository does not exist
Summary: [riscv64] Tumbleweed update repository does not exist
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Current
Hardware: Other openSUSE Tumbleweed
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Andreas Schwab
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on: 1187257
Blocks:
  Show dependency treegraph
 
Reported: 2021-06-14 20:39 UTC by Andreas Färber
Modified: 2022-05-03 09:56 UTC (History)
4 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Färber 2021-06-14 20:39:17 UTC
The image openSUSE-Tumbleweed-RISC-V-JeOS-hifiveunmatched.riscv64-2021.05.31-Build9.3.raw.xz from http://download.opensuse.org/repositories/home:/Andreas_Schwab:/riscv:/unmatched/images/
prints the following zypper errors:

[repo-update|http://download.opensuse.org/ports/riscv/update/tumbleweed/] Valid metadata not found at specified URL
History:
 - [repo-update|http://download.opensuse.org/ports/riscv/update/tumbleweed/] Repository type can't be determined.

Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'openSUSE-Tumbleweed-Update' because of the above error.
Some of the repositories have not been refreshed because of an error.


Indeed http://download.opensuse.org/ports/riscv/ does not have an update/ subdir yet.

Should this repo be removed/disabled in images for now? (didn't find where in https://build.opensuse.org/package/show/home:Andreas_Schwab:riscv:unmatched/JeOS this originates)

Or should we get https://build.opensuse.org/project/show/openSUSE:Factory:Update to build and publish updates for riscv64 at that URL, to avoid workarounds?
Comment 1 Andreas Schwab 2021-06-23 12:13:23 UTC
Neither do the debug and source repositories.  Please open an issue on progress.o.o.
Comment 2 Matthias Brugger 2022-04-21 08:02:38 UTC
Is this fixed by now?
Comment 3 Andreas Schwab 2022-05-03 09:56:29 UTC
No.  The repository setup is borken.