On 26/08/2022 01:28, Kevin Fenzi wrote:
Everything should be back to working. Try a 'dnf --refresh...' or a
'dnf clean all'.
Yes, the packages are no longer in the update list. So the errors are
gone for now. Thanks!
It's not fully clear yet some of the events. ;(
The person who used to update this has moved to another group.
The SOP (standard operating procedure) for doing this update was incorrect/out of date/wrong.
Current update used the wrong process in the SOP and unsigned rpms were sent instead of signed ones.
Something caused a zchunk error (the first one you saw, but perhaps this was just out of date repodata?)
Something caused mirrormanager to not update for the new repodata.
When updated, it started seeing the new unsigned rpms and gave an error about that.
I've pushed repodata that just points to the older h264 version thats signed (in f36/f37) and empty repodata (rawhide/f38).
In my testing everything is back to working.
I've submitted a PR to update the SOP.
Sorry for the trouble.
kevin
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
