Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2045200 Information from BlockerBugs App: <img alt="2045200" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2045200" />
Commented but haven't voted yet: adamwill
The votes have been last counted at 2022-04-19 16:12 UTC and the last processed comment was #comment-793257
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
FinalFE +1
If I understand it correctly, the appstream-data package is generated using this tool. AppStream metadata are important part of the Fedora Workstation, therefore I am proposing this not only as a FE, but also as a Blocker.
FinalBlocker +1 FinalFE +1
I am proposing this not only as a FE, but also as a Blocker.
You need to update the bugzilla, not just vote here. I just did.
For the blocker proposal, I think we had some policy about up-to-date appstream metadata, but I can't find it right now. Also, we need a confirmation that a broken appstream-generator actually blocks creating those metadata. @catanzaro @chrismurphy
I doubt FTBFS is going to stop metadata generation....
FinalFE +1 FinalBlocker -1
FinalBlocker -1 FinalFE -1
If it doesn't affect metadata generation, I don't see why this shouldn't wait until an update.
If this really does not prevent appstream-data from being generated, I agree with FinalBlocker -1, however why voting against the FinalFE? The fix for this issue is already in Bodhi.
Why does it merit a freeze exception? This has no impact on end users at all. It can be fixed in an update, right?
We generally don't want packages that don't build or install in GA repos if we can help it, hence the FE request.
+1 FinalFE
OK, fine.
A noble goal I guess...
AGREED AcceptedFinalFE RejectedFinalBlocker
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F36 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.