The website says "Fedora Atomic", but the uses branding that says "Fedora Cloud" <img alt="Screenshot_from_2017-11-16_12-13-00.png" src="/atomic-wg/issue/raw/b9344f781a8b1fbfca86a4a8ef1d61c19c53ce3b9d8b2a1df0447fc909109559-Screenshot_from_2017-11-16_12-13-00.png" />
Thanks for the report we'll try to get the media updated in a future 2 week release.
Metadata Update from @dustymabe: - Issue tagged with: host
Metadata Update from @dustymabe: - Issue tagged with: F27, jira
request for logos package to include atomic logos in it: https://pagure.io/fedora-logos/issue/3
Metadata Update from @dustymabe: - Issue assigned to dustymabe
upstream fedora-logos issue is fixed: https://pagure.io/fedora-logos/issue/3#comment-486747
should be able to update the productimg rpm soon.
Is it not pulled from fedora-logos rpm? Or is that a deprecated package that happens to have it's content pulled into the product-image-$NAME packages?
fedora-logos
product-image-$NAME
It is pulled from the fedora-logos rpm, but then that rpm is used as a Buildrequires for the productimg rpm (believe me, i was confused at first too). so we have to get the new fedora-logos rpm and then we can update the productimg rpm to use the new atomic logos.
@spot mind adding a build for the fedora-logos package? I started to do so but don't have access to that package:
Update requested to fix branding for Fedora Atomic Host. Updates: - Move CSS for logos in the graphical installer into fedora-logos - create atomic files for anaconda to use (https://pagure.io/atomic-wg/issue/385)
https://pagure.io/releng/issue/7213#comment-489888
the fix for this should be in the next builds of f27 atomic host.
Officially in Fedora 27 now: https://openqa.fedoraproject.org/tests/187354#step/_boot_to_anaconda/3. Will be in the next release.
Metadata Update from @dustymabe: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.