Bug 2097538
| Summary: | Screenhots in appdata reference 'master', while upstream changed the branch name to 'main' | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Peter Stone <fedora-topics-562353> |
| Component: | appstream-data | Assignee: | Richard Hughes <rhughes> |
| Status: | CLOSED MIGRATED | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | klember, mcatanza, rhughes, tpopela |
| Target Milestone: | rc | Keywords: | MigratedToJIRA |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-17 14:55:30 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Peter Stone
2022-06-15 22:11:58 UTC
Thanks for a bug report. It's a problem in the appstream data of the respective applications. I'll move this to the evince, open a bug to other apps as needed. When you run gnome-software with its verbose debug mode: $ gnome-software --quit; gnome-software --verbose and search for the evince and then select it, you'll see something like this: 06:17:32:0986 Gs Result of screenshot downloading attempt with status code '404': Not Found 06:17:33:0046 Gs Result of screenshot downloading attempt with status code '404': Not Found and several lines above: screenshot-00: https://gitlab.gnome.org/GNOME/evince/raw/master/data/screenshots/evince-1.png [<none>] screenshot-01: https://gitlab.gnome.org/GNOME/evince/raw/master/data/screenshots/evince-2.png [<none>] The problem is that the evince upstream renamed its `master` branch to the `main` branch, which is not reflected in the RHEL appstream data. When I change the path it finds the screenshots. Such change might need to update RHEL package with the appstream data, I think. I suspect that more applications renamed their branch from master to main in GNOME. Michael do you have a way to find what repositories in GNOME moved from using master to main so we can look if something needs to be changed? Another option would be to ask QE to go through the applications that we have in RHEL and see whether they have screenshots available. (In reply to Tomas Popela from comment #2) > I suspect that more applications renamed their branch from master to main in > GNOME. Michael do you have a way to find what repositories in GNOME moved > from using master to main so we can look if something needs to be changed? Definitely not. I could only tell you about core applications tracked by release team. RHEL has way more applications than that. We need to keep up with all applications in RHEL. It's expected that applications that delete their master branch will not have any screenshots until RHEL 10 if they stored screenshots on the master branch, which was/is best practice. That's just a predictable consequence of the ongoing branch name sabotage. As applications continue to switch branch names, more and more screenshots will disappear over time, so it's something that has to be actively kept up with. Suffice to say I'm glad I'm not maintaining our appstream data right now. Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |