Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=1882863 **
Commented but haven't voted yet: kparal
The votes have been last counted at 2020-10-05 19:53 UTC and the last processed comment was #comment-693607
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review
FInalBlocker 0
I think I am generally -1 blocker on this bug based off my interpretation of this not violating the "default functionality" criterion, as one could still add the repo in gnome-software and then install whatever packages with dnf, but opened and proposed in case this in case this is a larger issue than just gnome-software.
Discussed during the 2020-09-28 blocker review meeting: [0]
The decision to delay the classification of this as a blocker bug was made as it's not clear what the scope of this bug is, so it's hard to make a blocker decision at this time.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2020-09-28/f33-blocker-review.2020-09-28-16.01.txt
We'll have to figure out if this is a packagekit issue or a package/repo appstream issue. Also, if it is a packagekit issue, how many (types of) packages it affects. Based on that, we can make a judgement whether it's considered a basic functionality. See the bug for some debugging information.
Looks like distribution-gpg-keys is missing the GPG key for the repo.
FinalBlocker +1
So, do we have a matching criterion? We could say this is violated: https://fedoraproject.org/wiki/Fedora_33_Beta_Release_Criteria#Installing.2C_removing_and_updating_software in the case of those additional repositories which are offered by default (just not enabled), but it's a bit of a stretch.
This is fine
FinalBlocker -1
AGREED RejectedFinalBlocker AcceptedFinalFE
Discussed during the 2020-10-05 blocker review meeting: [0]
The decision to classify this bug as a "RejectedBlocker (Final)" and an "AcceptedFreezeException (Final)" was made as we don't think this can really count as a violation of the criterion cited, the app's "basic functionality" is working fine, it is just rejecting a repo whose key it can't find, which is correct behavior. However, we definitely want these additional repos to work at release time as they are widely used, so accepted as a freeze exception issue.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2020-10-05/f33-blocker-review.2020-10-05-16.00.txt
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F33 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.