|Summary:||Requires python-smbios, which doesn't exist|
|Product:||[Fedora] Fedora||Reporter:||Adam Williamson <awilliam>|
|Component:||firmware-addon-dell||Assignee:||Michael E Brown <mebrown>|
|Status:||CLOSED EOL||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||28||CC:||gmarr, mebrown, praween.paladugu, redhat, robatino|
|Fixed In Version:||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|Last Closed:||2019-05-28 21:59:54 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Adam Williamson 2018-03-28 21:36:39 UTC
Comment 1 Adam Williamson 2018-03-28 21:38:02 UTC
Proposing as a Final blocker, as firmware-addon-dell is on the Server DVD, and thus this violates the Final criterion: "There must be no errors in any package on the release-blocking images which cause the package to fail to install." Note we waived a very similar issue for F27 which was discovered late: https://bugzilla.redhat.com/show_bug.cgi?id=1522905 but I've remembered to report this one early enough that we should probably fix it properly this time.
Comment 2 Geoffrey Marr 2018-04-02 17:14:51 UTC
Discussed during the 2018-04-02 blocker review meeting:  The decision to classify this bug as an AcceptedBlocker was made as it violates the following blocker criteria: "There must be no errors in any package on the release-blocking images which cause the package to fail to install." We note that removing the package from the DVD would be a sufficient fix.  https://meetbot.fedoraproject.org/fedora-blocker-review/2018-04-02/f28-blocker-review.2018-04-02-16.00.txt
Comment 3 Adam Williamson 2018-04-09 18:20:30 UTC
https://pagure.io/fedora-comps/pull-request/254 should render this non-blocking, if merged.
Comment 4 Adam Williamson 2018-04-09 20:25:54 UTC
That's merged, so I'm gonna drop blocker status for this now.
Comment 5 João Carlos Mendes Luís 2018-07-30 17:51:25 UTC
Any news on this?
Comment 6 João Carlos Mendes Luís 2018-07-30 17:53:49 UTC
Duplicate of 1555752 ?
Comment 7 Adam Williamson 2018-07-30 18:16:15 UTC
No, it's not a duplicate, though they're somewhat related.
Comment 8 João Carlos Mendes Luís 2018-07-31 00:28:29 UTC
Anyway, I think it will not be solved: https://src.fedoraproject.org/rpms/firmware-addon-dell/c/23f8bab6e1a3dc30b6a49ed46e6b2b8c430ea4c0?branch=master "The recommendation from Dell is to drop it. Other distros have dropped it too" -- Charles Rose, Dell Somebody told me to use fwupd, instead...
Comment 9 Ben Cotton 2019-05-02 21:14:07 UTC
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Comment 10 Ben Cotton 2019-05-28 21:59:54 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.