Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2011291 Information from BlockerBugs App: <img alt="2011291" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2011291" />
The votes have been last counted at 2021-10-07 19:26 UTC and the last processed comment was #comment-756872
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
There are several problems mentioned. I'd say the most problematic one is #1. If flatpak repos are displayed, their status (enabled/disabled) should be correct. I was fully convinced that both repos are enabled, until it occurred to me to also check flatpak remotes output. We can get many users falsely believing they're running with testing flatpaks. Showing a correct state seems like a basic functionality to me.
#1
flatpak remotes
#2 is about being able to enable/disable flatpak repos. If Discover can't do that, I don't think that's a problem, it's simply a missing functionality.
#2
#3 is about not being able to delete disabled repos. That's a moderately bad bug in my eyes. It should either not show the trash can button, or it should work. But if the repo could be enabled manually and then you'd be able to delete it (see #2), I think that would be sufficient as a documented workaround.
#3
FinalBlocker +1
This is not only confusing for the user but it surely greatly limits the functionality of the desktop's default package manager.
FinalBlocker +1 AGREED AcceptedFinalBlocker
The following votes have been closed:
Note I'm specifically +1 blocker to the first problem in @kparal 's list. The others I think probably don't make the cut.
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F35 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.