Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1319865 - Consider better per-release automation
Summary: Consider better per-release automation
Keywords:
Status: CLOSED DUPLICATE of bug 1435423
Alias: None
Product: Fedora
Classification: Fedora
Component: desktop-backgrounds
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Martin Sourada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-21 17:12 UTC by Paul W. Frields
Modified: 2018-11-27 19:53 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-27 19:53:39 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Paul W. Frields 2016-03-21 17:12:32 UTC 
Description of problem:
When new background images come late, or maintainers don't notice or aren't notified about the changes, it can cause a bit of a fire drill at Alpha release.  At this release point, there is a criterion requiring the default background to be different for the new release.  Ray suggested this:

<halfline> so if we wanted to automate this we could move 0_org.gnome.desktop.background.fedora.gschema.override from desktop-backgrounds-gnome to fedora-release
<halfline> and then have it write in the current fedora release at build time
<halfline> if the backgrounds aren't ready yet the url will point to nothing of course
<halfline> which will make it fall back and we'll have a background that automatically meets alpha criteria (something differen than the last release)

We should consider this kind of solution, but also need to look at what this change would imply for LXDE/Xfce/others (via the -compat subpackage?), and whether a better solution for KDE would be possible as well.
Comment 1 Jan Kurik 2016-07-26 04:39:46 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.
Comment 2 Adam Williamson 2017-09-11 20:53:33 UTC 
Note that the release-blocking desktops at present are GNOME, KDE and Xfce. Any solution that works for those three will make us happy so far as the release process is concerned. Making things work for other desktops is great but less important.
Comment 3 Ben Cotton 2018-11-27 18:27:03 UTC 
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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.
Comment 4 Adam Williamson 2018-11-27 19:53:39 UTC 
Let's dupe this into 1435423 ...

*** This bug has been marked as a duplicate of bug 1435423 ***
Note You need to log in before you can comment on or make changes to this bug.