| Summary: | grub2-starfield-theme should install to /boot/grub2/themes | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jannik <me> |
| Component: | grub2 | Assignee: | Peter Jones <pjones> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | bcl, dennis, mads, pjones |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-06-29 13:40:14 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Jannik
2013-12-20 18:07:54 UTC
With correct use of grub2, grub2-install will take care of placing the theme in the more right place. Fedora do however have its own way of doing it so many of the original upstream assumptions and ways of doing things are no longer valid. But the starfield theme is also not used by standard installations. If the user wants to customize things then he should be prepared to do whatever it takes to customize. I don't know how grub2-install is involved, because theming is done after installation in /etc/default/grub and with grub2-mkconfig.
> If the user wants to customize things then he should be prepared to do whatever it takes to customize.
But when "whatever" means break the package-management 'cause one must copy things around the filesystem, I think that's not a good idea and could be avoided with a different install location for themes.
If you don't agree, feel free to mark the bug as won't fix.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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. Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. |