Bug 1193634 - Fedora Rawhide, 34, 35 show up as "Unknown" on software.opensuse.org
Summary: Fedora Rawhide, 34, 35 show up as "Unknown" on software.opensuse.org
Status: NEW
: 1194021 (view as bug list)
Alias: None
Product: openSUSE.org
Classification: openSUSE
Component: BuildService (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Benjamin Weber
QA Contact: Adrian Schröter
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-11 15:28 UTC by Paul McAuley
Modified: 2022-05-19 00:15 UTC (History)
1 user (show)

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

Attachments
more damage (69.47 KB, image/png)
2022-02-24 12:30 UTC, Juergen Weigert 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul McAuley 2021-12-11 15:28:40 UTC 
This used to work up until a few months ago, but Fedora Rawhide packages show up as an "Unknown" OS on the package download page.

For example: https://software.opensuse.org/download/package?package=classik&project=home%3Apaul4us
Comment 1 Andreas Stieger 2021-12-22 21:03:35 UTC 
*** Bug 1194021 has been marked as a duplicate of this bug. ***
Comment 2 Juergen Weigert 2022-01-12 18:24:10 UTC 
Ping. 
Can we get that fixed please?
Comment 3 Juergen Weigert 2022-02-24 09:42:05 UTC 
Is there anything I can do to push that forward?

Is the code for the website public?
Comment 4 Juergen Weigert 2022-02-24 12:30:04 UTC 
Since I last looked, more damage happened:

The download instructions for Fedora 34 and 35 are now replaced with a single question mark. 
e.g. in https://software.opensuse.org//download.html?project=isv%3AownCloud%3Aserver%3A10.9.1&package=owncloud-complete-files
Comment 5 Juergen Weigert 2022-02-24 12:30:24 UTC 
Created attachment 856536 [details]
more damage
Comment 6 Juergen Weigert 2022-05-19 00:15:29 UTC 
It seems the issue was fixed, without mentioning the fix here. 
Is this bugzilla still the right way to reach OBS maintainers?

I get the feeling that issues are discussed and resolved elsewhere.