Description of problem: Zukiwi packages is not available for F18, I know that the gnome shell theme is not compatible with gnome 3.6, but the gtk2, gtk3 & xfce theme is very useful for XFCE users. You could optional leave the gnome-shell theme out for F18 and only build zukiwi-common.noarch zukiwi-gtk2-theme.noarch zukiwi-gtk3-theme.noarch zukiwi-xfwm4-theme.noarch Same issue with zukitwo :) just try to add %if 0%{?fedora} < 18 .. .. %endif around the gnome shell parts, and they will not be build for F18 & F19
Created attachment 630451 [details] Don't build gnome-shell theme for Fedora > 17 Here is a patch there does the trick
Thanks for your suggestions. Anyway, I wrote to the creator and he assured me he would make the Gnome Shell themes compatible with Gnome 3.6 after the release of its final version. I think it's worth waiting for him to do so, so to be able to provide Fedora 18 users with complete themes.
Thanks, nice to know :)
News by lassekongo83, the creator of the Zuki* themes: http://lassekongo83.deviantart.com/#/d5it5lp
Thanks for the update, If he skip the Zukiwi for gnome-shell, we still can have packages for xfce, gtk2 & gtk3 and leave the gnome-shell theme for F17.
That'd be a great idea. I've had to switch to XFCE recently, due to GNOME Shell hogging the CPU (with the concomitant heat and loss of battery life -- https://bugzilla.redhat.com/show_bug.cgi?id=812624); and find that I resorted to using one of lassekongo's XFCE window decorations since the default ones don't play that well with Adwaita GTK themes. Mattia, could you adjust the spec to the relevant packages, to make the packaging of the gnome-shell theme conditional? e.g. %if 0%{?fedora} < 18 %package -n gnome-shell-theme-%{name} ... %endif ... %if 0%{?fedora} < 18 %files -n gnome-shell-theme-%{name} ... %endif
OK. First of all, I'll ask Release Engineering to un-block the Zuki* packages for Fedora > 17; then I'll submit the packages, modified as you are suggesting.
(In reply to comment #7) > First of all, I'll ask Release Engineering to un-block the Zuki* packages > for Fedora > 17; then I'll submit the packages, modified as you are > suggesting. In order for the packages to be un-blocked, I have to submit new review requests for them. Here they are: - Zukini: https://bugzilla.redhat.com/show_bug.cgi?id=874718 - Zukitwo: https://bugzilla.redhat.com/show_bug.cgi?id=874719 - Zukiwi: https://bugzilla.redhat.com/show_bug.cgi?id=874721
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.
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.