Bug 875144 - please change system-logos requirement to "Recommends"
Summary: please change system-logos requirement to "Recommends"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-09 16:13 UTC by Matthew Miller
Modified: 2018-05-31 14:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-31 14:26:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Matthew Miller 2012-11-09 16:13:30 UTC
It would be nice to have grub2 on cloud images (at least where pv-grub isn't used) so that we're consistent with the "normal" non virtualized Fedora.

I notice that in F18, /boot/grub2/themes/system/ from fedora-logos is 5.6MB, 4MB of which is from the single bootsplash image.

I removed the fedora-logos package manually, and grub seems to not break if this is missing?

Can we get an alternate, tiny theme that won't pull this in? We could then put fedora-logos in the standard package set so it's installed by default -- or even in @core, where it would be installed by default but could be removed specifically, without breaking deps.

Comment 1 Mads Kiilerich 2012-11-09 16:37:43 UTC
generic-logos should perhaps be suitable as provider of system-logos for that usecase.

Comment 2 Matthew Miller 2012-11-09 17:41:53 UTC
(In reply to comment #1)
> generic-logos should perhaps be suitable as provider of system-logos for
> that usecase.

Much, much smaller. But it happens that it's working just fine with *no* logos, so I'm not seeing the need for the requirement at all.

Comment 3 Mads Kiilerich 2012-11-10 20:38:50 UTC
I guess most Fedora packages are very useful even without some of the dependencies. But Fedora packages should in general list enough dependencies to make sure that everything in the package works as intended. From that point of view it is right that grub2-tools requires system-logos.

But in my opinion /boot/grub2/themes/system shouldn't be in grub2-tools. The dependency to system-logos should thus also be in some other (optional) package. It should perhaps all be in fedora-logos.

I guess a graphical boot with fedora-logos missing would require user interaction when booting. I guess your cloud machine is 'headless' and thus doesn't boot with graphics and thus gives biased test results.

Comment 4 Matthew Miller 2012-11-11 00:14:53 UTC
(In reply to comment #3)
> I guess a graphical boot with fedora-logos missing would require user
> interaction when booting. I guess your cloud machine is 'headless' and thus
> doesn't boot with graphics and thus gives biased test results.

I'm booting with KVM locally right now and looking at the console, so it's not completely headless. It's true that it's not an X-based boot. There are no errors, just no graphic. That seems like a pretty reasonable fallback.

We could even put fedora-logos in @core, so it's installed by default but could be intentionally de-selected for the perfectly valid "biased" cases.

Comment 5 Fedora End Of Life 2013-12-21 09:20:53 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 6 Fedora End Of Life 2014-02-05 12:57:52 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.

Comment 7 Matthew Miller 2015-08-06 17:01:22 UTC
Can we revisit this? Extlinux is increasingly frustrating on the cloud images. And, now we have weak dependencies, https://fedoraproject.org/wiki/Packaging:WeakDependencies, this seems like a good candidate.

Comment 8 Matthew Miller 2015-09-21 16:38:22 UTC
As noted above, package is perfectly functional without logos even in default config and when you have a screen which could theoretically show logos. Please change to "Recommends" rather than "Requires".

Comment 9 Dusty Mabe 2016-05-05 03:27:54 UTC
Hi,

Any progress on moving from Requires to Recommends ? 

Dusty

Comment 10 Fedora End Of Life 2016-11-24 10:51:10 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 11 Fedora End Of Life 2016-12-20 12:29:57 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.

Comment 12 Jan Kurik 2018-05-31 09:02:29 UTC
This bug is currently reported against a Fedora version which is already unsuported.
I am changing the version to '27', the latest supported release.

Please check whether this bug is still an issue on the '27' release.
If you find this bug not being applicable on this release, please close it.

Comment 13 Matthew Miller 2018-05-31 14:26:09 UTC
I believe this was addressed (by dropping entirely, not changing to recommends) in this commit: https://src.fedoraproject.org/rpms/grub2/c/ecef1ed7b50ed05b65574c8b8815d7ae66e5a0a9

The changelogs (git and rpm) don't mention it, so maybe this was an accident. In any case, seems addressed now.


Note You need to log in before you can comment on or make changes to this bug.