#1387 [pciutils] /usr/bin/lspci symlink missing, causes Dying Light game not to launch | rhbz#1858437
Closed by blockerbot. Opened by blockerbot.

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

Current vote summary

Commented but haven't voted yet: coremodule

The votes have been last counted at 2023-10-11 17:11 UTC and the last processed comment was #comment-878287

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)


For the reason given in the BZ, I think we could grant FE here.

FinalFE +1

I think this could stay as a 0-day update, honestly. People can do almost anything with an installed system, but I think it's reasonable to expect them to update first. Dying Light is an old game now, reviewers are not likely to try it (rather its sequel, if anything).

For the moment:
FinalFE -1
but feel free to try to convince me, if you have a different opinion.

This can be fixed by a zero day. The bodhiupdate is already out according to BZ , so
FinalFE -1

but feel free to try to convince me, if you have a different opinion.

I don't know all the games that rely on /usr/bin/lspci. That path has been where lspci(8) was installed on Debian systems for a very long time, so there's an array of games that would expect it there. Dying Light just happens to be the one reported here.

FinalFE +1

There is no harm in adding symlink to a package, not all users might update the system immediately after installing the GA, it may affect other apps/games.

We've somehow made it since 2020 with this issue, I feel like it can wait a bit longer and be a 0 day fix.

FinalFE -1

Discussed during the 2023-10-09 blocker review meeting: [0]

The decision to delay the classification of this as a freeze exception was made as we cannot agree on a decision. Note that the effect of a punt is similar to a rejection, which is intended; active acceptance must be the requirement to break the freeze.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2023-10-09/f39-blocker-review.2023-10-09-16.00.txt

As this is a clear issue, and it has a fix, I think it makes sense to get the fix out ASAP, especially as it is unlikely to have a negative effect (a symlink is minor).

FinalFE +1

FinalFE -1

The definition of a freeze is you don't change things unless there is a clear reason to do so. Nobody has provided any justification yet for why this needs to break the freeze as opposed to simply being a 0-day update.

FinalFE -1

What Adam said.

FinalFE -1

Nothing to add from what Adam said. I don't see any reason this can't be a 0-day update.

I think for a game a 0-day update is an acceptable way to go. People without Internet would be a seriously rare use case these days.

FinalFE -1

The following votes have been closed:

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

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

Log in to comment on this ticket.

Metadata