#975 [gnome-software] RPM packaged applications are presented in GNOME Software and preferred over Flatpaks on Silverblue | rhbz#2135289
Closed by blockerbot. Opened by blockerbot.

Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2135289 **
Information from BlockerBugs App:
2135289

Current vote summary

Commented but haven't voted yet: kparal, mclasen, nielsenb, coremodule, bittin

The votes have been last counted at 2022-10-24 09:18 UTC and the last processed comment was #comment-822581

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)


This is a huge problem for Silverblue, if I under it correctly. At the same time, patching gnome-software so shortly before a Final RC is very risky. I guess I'm leaning more towards
FinalFE +1
just because this would make fresh F37 Silverblue users install software in an incorrect way. But we have to make sure to test gnome-software very carefully before we greenlight the RC.

I find it hard to weigh the pros and cons on the available info. For now:

FinalFE 0

FinalFreezeException +1

I'm not a big fan of pulling in changes to gnome-software this close to release, but I would like it to work it's best on Silverblue. The linked MRs aren't too invasive, so I'm a "probably going to regret this later" +1.

FinalFE +1

FinalFE +1

but we should be very sure to test that this doesn't result in Software preferring flatpaks over RPMs for Workstation installs.

but we should be very sure to test that this doesn't result in Software preferring flatpaks over RPMs for Workstation installs.

Who would've thought, right? :-)
https://bugzilla.redhat.com/show_bug.cgi?id=2135289#c4

AGREED RejectedFinalFE

Discussed during the 2022-10-17 blocker review meeting: [0]

The decision to classify this bug as a "RejectedFreezeException (Final)" was made as there is support for this in principle, but testing indicates the current update has a severe problem, and that indicates it's probably too late to be poking this code even if a quick fix is found for that specific problem. We may re-consider this if the problem kparal identified is addressed and the release slips.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-10-17/f37-blocker-review.2022-10-17-16.01.txt

The following votes have been closed:

Re-proposing as a FE:
https://bugzilla.redhat.com/show_bug.cgi?id=2135289#c13

REVOTE FinalFreezeException

FinalFE +1
if FESCo approves and we're sure the update restores the same behaviour as F35 (would be good to check this).

Update: I have tested and confirmed that, AFAICS, the F37 update restores the same behaviour as F35.

Based on the current state of affairs:

FinalFE +1

I'm gonna give the FESCo ticket a bit longer since it's there, but if folks don't reply there by later tonight I'll accept this as an FE and file the request so we can hopefully get an RC tomorrow morning. We can always just build another if FESCo decides against this.

OK, we have +6 from FESCo and this didn't really need to go through them anyway, we have +4 here, I'm calling it good enough.

AGREED AcceptedFinalFE

The following votes have been closed:

Metadata Update from @blockerbot:
- Issue status updated to: Closed (was: Open)

Release F37 is no longer tracked by BlockerBugs, closing this ticket.

Log in to comment on this ticket.

Metadata