Please, consider generating appstream-data for F33. The current one was generated by releng from old F32 AppStream metadata.
Furthermore, moving from F32 to F33 requires a downgrade of appstream-data. F32 has appstream-data-32-8.fc32, but F33 has appstream-data-32-7.fc33.
I guess this one should this be a release blocker / candidate for freeze exception?
From IRC discussion: Sep 30 13:48:06 <AsciiWolf> kalev, hi! any chance someone could update appstream-data for F33? :) the latest f33 package is still based on the old f32 metadata and was automatically generated by releng Sep 30 13:49:07 <kalev> AsciiWolf: hey, sorry, I can't do that :( I asked hughsie two weeks ago, but I think he got sidetracked with other stuff Sep 30 13:49:42 <AsciiWolf> ah :( ok, thanks anyway :) Sep 30 13:50:34 <kalev> AsciiWolf: maybe it's best to leave it alone for now and I'll ask him again once we're frozen for F33 Final so we ship with fully up to date metadata Sep 30 13:51:06 <kalev> that would be next week :)
But feel free to propose this bz as a blocker.
> I'll ask him again once we're frozen for F33 Final I can generate some metadata whenever required; just grab me on irc.
Should this bz be proposed as a blocker/freeze exception?
There's no need to _propose_ it: appstream-data updates have an automatic FE exception that doesn't need proposing/discussion.
Ah! Thanks for the info. :-)
Richard, I think now would be a good time to regenerate it if you have time for it. F33 is now in the final freeze and the GNOME and KDE megaupdates have both landed and should be synced out to repositories.
Can we get a new appstream-data build please? I think this really should be a blocker ... how is it possible that we release F33 without any of the appdata changes from the past 6 months of development?
+1 blocker
This is an automatic freeze exception, by FESCo vote: https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process#Automatic_freeze_exceptions https://pagure.io/fesco/issue/2374#comment-642102 by implication it should not be a blocker, or else FESCo would have voted that these should be automatic blockers.
-3 blocker votes in https://pagure.io/fedora-qa/blocker-review/issue/172 , rejecting (it is still an accepted freeze exception, and Richard says he'll do a new build tomorrow).
FEDORA-2020-c55c7caacb has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-c55c7caacb
The needinfo request is not needed anymore.
FEDORA-2020-c55c7caacb has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-c55c7caacb` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-c55c7caacb See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-c55c7caacb has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.