Bug 1393945

Summary:	syslinux-splash.png and syslinux-vesa-splash.png are in the wrong directory
Product:	[Fedora] Fedora	Reporter:	Neal Gompa <ngompa13>
Component:	generic-logos	Assignee:	Bill Nottingham <notting>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	25	CC:	awilliam, ngompa13, notting, notting, sgallagh
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	AcceptedFreezeException
Fixed In Version:	generic-logos-18.0.0-1.fc25	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-18 08:23:29 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:
Embargoed:
Bug Depends On:
Bug Blocks:	1277290

Description Neal Gompa 2016-11-10 16:53:23 UTC

Description of problem:
The syslinux-splash.png and syslinux-vesa-splash.png files are currently in /usr/share/anaconda/pixmaps in generic-logos.

However, lorax and its templates expect them to be in /usr/share/anaconda/boot instead. The fedora-logos package has it in the right place, but generic-logos does not, which leads to debranded spins of Fedora failing to compose due to path mismatch.

The syslinux-splash.png and syslinux-vesa-splash.png files need to move to /usr/share/anaconda/boot, to match fedora-logos in its location, permitting the usage of standard lorax templates to compose live ISOs.

Version-Release number of selected component (if applicable):
17.0.0-8.fc24

How reproducible:
Always

Steps to Reproduce:
1. Fork any of the fedora kickstarts for any of the editions/spins and swap fedora-release* and fedora-logos for generic-release and generic logos
2. Use livemedia-creator to attempt an ISO compose.


Actual results:
ISO creation fails because file isn't found

Expected results:
ISO creation succeeds

Additional info:

This affects Fedora Rawhide, 24, and 23, too.

Comment 1 Fedora Blocker Bugs Application 2016-11-10 16:55:34 UTC

Proposed as a Freeze Exception for 25-final by Fedora user ngompa using the blocker tracking app because:

 Without moving the files to the correct location, building remixes/spins not using fedora-logos is not possible without forking lorax templates.

In most cases, this is complete overkill and a lot more work to keep up, especially in light of a rather simple fix.

Comment 2 Stephen Gallagher 2016-11-11 13:21:45 UTC

I'm inclined to vote +1 FE here. There should be no risk to blocking media at all, since of course they use the branded fedora-logos package.

Comment 3 Bill Nottingham 2016-11-14 03:33:27 UTC

Fixed in 18.0.0-1.

Comment 4 Fedora Update System 2016-11-14 03:41:10 UTC

generic-logos-18.0.0-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-9c546a3aa3

Comment 5 Adam Williamson 2016-11-14 19:43:41 UTC

Discussed at 2016-11-14 freeze exception review meeting: https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2016-11-14/f25-blocker-review.2016-11-14-17.00.html . Accepted as a freeze exception issue as this is useful for respins and, as it's only in generic-logos, cannot possibly affect any release blocking deliverables.

Comment 6 Fedora Update System 2016-11-15 13:26:33 UTC

generic-logos-18.0.0-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-9c546a3aa3

Comment 7 Fedora Update System 2016-11-18 08:23:29 UTC

generic-logos-18.0.0-1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.