Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2270397 ** Information from BlockerBugs App:
Commented but haven't voted yet: adelton, kparal
The votes have been last counted at 2024-04-08 10:06 UTC and the last processed comment was #comment-904589
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)
BetaBlocker +1
BetaBlocker
FinalBlocker
BetaFE
FinalFE
0Day
PreviousRelease
+1
0
-1
BetaFE +1
For sure. It looks bad, but isn't super blockery... it would still be very nice to fix sooner rather than later tho.
BetaFE +1 retroactively (we went ahead and landed the attempted fix for this ahead of running 1.10). AGREED AcceptedBetaFE
The following votes have been closed:
The issue got fixed two weeks ago and https://bugzilla.redhat.com/show_bug.cgi?id=2270397 got closed, but now the problem is back on registry.fedoraproject.org/fedora:40:
$ podman pull registry.fedoraproject.org/fedora:40 Trying to pull registry.fedoraproject.org/fedora:40... Getting image source signatures Copying blob c6405a39eed1 skipped: already exists Copying config 71a9aee84c done | Writing manifest to image destination 71a9aee84c30bdd96c84be43693f6d74ba56f1d71c278f383ef1524f0ec86903 $ podman run --rm registry.fedoraproject.org/fedora:40 rpm -qi rpm | grep Signature Signature : (none)
Should I file a new bugzilla / Pagure issue, or will we track it in this one?
I reopened the bugzilla and proposed it for a Final freeze exception.
The new discussion ticket is in #1573 (not sure why it created another one, honestly).
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F40 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.