Spec URL: https://copr-be.cloud.fedoraproject.org/results/luya/f28-backgrounds/fedora-rawhide-x86_64/00721636-f28-backgrounds/f28-backgrounds.spec
SRPM URL: https://copr-be.cloud.fedoraproject.org/results/luya/f28-backgrounds/fedora-rawhide-x86_64/00721636-f28-backgrounds/f28-backgrounds-28.0.0-1.fc28.src.rpm
Description: This package contains desktop backgrounds for the Fedora 28 default
theme. Pulls in themes for GNOME, KDE, Mate and Xfce desktops.
Fedora Account System Username: luya
- https://fedoraproject.org/wiki/F28_Artwork is empty
- [!]: Package must own all directories that it creates.
Note: Directories without known owners:
Check out whether you own these directories correctly. I think one that should be owned in the extras subpackage is:
I can review today
fyi, embedded metadata.desktop for the kde wallpaper still says Twenty-Seven/f27, but I can help fix that post review so that it's more future proof (ie, will minimize or remove any need for manual editing for future releases).
first off: (more thorough items coming soon)
1. file ownership referenced in comment #1
could be replaced by simple:
/usr/share/wallpapers is already owned by kde-filesystem
/usr/share/backgrounds/f28 is owned by -base subpkg
For /usr/share/xfce4/backdrops, I think those should be added here (I don't see anything else better to provide ownership)
Same for /usr/share/gnome-background-properties, add to
Same for -mate,
Thanks Robert-André and Rex. Here is the updated spec and srpm based on feedback:
I realize the deadline for packaging the default wallpaper is on March 5. Due to job related, I will be unable to update during weekday until evening Pacific time due to lack of access to my laptop.
Thanks, looks good, the rest if fairly simple, clean, and templated from prior release packages in general.
(fedrepo-req-admin): The Pagure repository was created at https://src.fedoraproject.org/rpms/f28-backgrounds
(In reply to Rex Dieter from comment #3)
> fyi, embedded metadata.desktop for the kde wallpaper still says
> Twenty-Seven/f27, but I can help fix that post review so that it's more
> future proof (ie, will minimize or remove any need for manual editing for
> future releases).
I took opportunity to quickly fix the versionin on metadata.desktop. Feel free to further bring enhancement.
Proposed as a Blocker for 28-beta by Fedora user luya using the blocker tracking app because:
Default beta wallpapers for Fedora 28 is recently packaged for the beta release that just got frozen.
The release criterion here states "The default desktop background must be different from that of the last two stable releases." Without this update, is the F28 background the same as the F26 or F27 backgrounds? If so, this is a blocker, if not, FE.
(In reply to Adam Williamson from comment #11)
> is the F28 background the same as the F26 or F27 backgrounds? If so, this is
> a blocker, if not, FE.
In this case, F28 backgrounds differ from the previous release so assigning to FE.
desktop-backgrounds-28.0.0-1.fc28, f28-backgrounds-28.1.0-1.fc28 has been pushed to the Fedora 28 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-2018-f86f6e9857
Luya: the question isn't whether the *new* backgrounds are different, of course they are. The question is whether the backgrounds *currently* in F28 - before this update - are the same as F27 or F26. And it looks to me like they're the same as F27:
which would make this a blocker.
Discussed during the 2018-03-12 blocker review meeting: 
The decision to classify this bug as an AcceptedBlocker was made as it violates the following blocker criteria:
"The default desktop background must be different from that of the last two stable releases"
desktop-backgrounds-28.0.0-1.fc28, f28-backgrounds-28.1.0-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.