Bug 225654 - Merge Review: control-center
Summary: Merge Review: control-center
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: 23
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Fedora Package Reviews List
Depends On:
TreeView+ depends on / blocked
Reported: 2007-01-31 17:51 UTC by Nobody's working on this, feel free to take it
Modified: 2016-12-20 11:55 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-12-20 11:55:19 UTC
Type: ---

Attachments (Terms of Use)

Description Nobody's working on this, feel free to take it 2007-01-31 17:51:53 UTC
Fedora Merge Review: control-center

Initial Owner: rstrode@redhat.com

Comment 1 Ray Strode [halfline] 2007-02-05 21:45:55 UTC
There is an icky sed replace for bug 171059.  This got veto'd upstream, so I'm
going to drop it.

Comment 2 Ray Strode [halfline] 2007-02-05 21:47:09 UTC
there is a comment:

# desktop-file-install really should not be generating this
rm -f $RPM_BUILD_ROOT%{_datadir}/applications/mimeinfo.cache

But it won't, because desktop-file-install isn't being called with

so I'm going to drop that line.

Comment 3 Ray Strode [halfline] 2007-02-05 21:49:35 UTC
we already pass --disable-static so we shouldn't need to worry about .a files,
and we're being very particular about the .la files we're deleting.

I'm going to drop most of the 

rm -f $RPM_BUILD_ROOT%{_libdir}/.../*.*a

lines and replace them with 

find $RPM_BUILD_ROOT -name '*.la' -exec rm -f {} \;

Comment 4 Ray Strode [halfline] 2007-02-05 21:57:55 UTC
I ran

for f in control-center*.patch; do grep -q $f control-center.spec || cvs rm -f
$f; done

to drop unused patches.  There are some other keyboad-drawing patches that I
don't know what the fate of them should be.

CCing matthias to see what he thinks.

Comment 5 Matthias Clasen 2007-02-06 02:16:19 UTC
the keyboard drawing patches have all been ported to libgnomekbd and can safely
be deleted here.

Comment 6 Matthias Clasen 2007-11-18 06:00:28 UTC
I've just done some more patch cleanups.
Here is what rpmlint currently says:

[mclasen@localhost devel]$ rpmlint control-center-2.21.2-2.fc9.i386.rpm 
control-center.i386: W: devel-file-in-non-devel-package

Could perhaps be moved to the -devel package, I guess

control-center.i386: W: non-conffile-in-etc
control-center.i386: W: non-conffile-in-etc
control-center.i386: W: non-conffile-in-etc
control-center.i386: W: non-conffile-in-etc
control-center.i386: W: non-conffile-in-etc
control-center.i386: W: non-conffile-in-etc /etc/gconf/schemas/themus.schemas
control-center.i386: W: non-conffile-in-etc /etc/xdg/menus/gnomecc.menu
control-center.i386: W: non-conffile-in-etc
control-center.i386: W: non-conffile-in-etc
control-center.i386: W: non-conffile-in-etc /etc/gconf/schemas/fontilus.schemas
control-center.i386: W: file-not-utf8 /usr/share/doc/control-center-2.21.2/NEWS
control-center.i386: W: non-conffile-in-etc

All of these follow established practise, I think

control-center.i386: E: explicit-lib-dependency libgail-gnome

This is rpmlint being too stupid. libgail-gnome doesn't actually
contain a library, but only a module.

control-center.i386: W: incoherent-version-in-changelog 2.21.2-2 1:2.21.2-2.fc9

Should probably be cleaned up

control-center.i386: W: obsolete-not-provided gnome
control-center.i386: W: obsolete-not-provided fontilus

Not a big deal, but I believe these obsoletes can be removed without harm.

control-center.i386: E: invalid-desktopfile
control-center.i386: E: invalid-desktopfile

Not sure what to do about these. 
We need some way to totally hide these desktop files from the menus.

[mclasen@localhost devel]$ rpmlint control-center-devel-2.21.2-2.fc9.i386.rpm 
control-center-devel.i386: W: no-documentation

This is ignorable.

Comment 7 Cole Robinson 2015-02-11 20:35:45 UTC
Mass reassigning all merge reviews to their component. For more details, see this FESCO ticket:


If you don't know what merge reviews are about, please see:


How to handle this bug is left to the discretion of the package maintainer.

Comment 8 Jan Kurik 2015-07-15 15:27:13 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:

Comment 9 Fedora End Of Life 2016-11-24 10:17:34 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 10 Fedora End Of Life 2016-12-20 11:55:19 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.