Bug 331421 - a bunch of little issues withe bluecurve
Summary: a bunch of little issues withe bluecurve
Alias: None
Product: Fedora
Classification: Fedora
Component: bluecurve-icon-theme
Version: 8
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2007-10-14 19:35 UTC by Matthias Clasen
Modified: 2009-01-09 07:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-01-09 07:19:12 UTC

Attachments (Terms of Use)

Description Matthias Clasen 2007-10-14 19:35:14 UTC
I see several sizes of foo.png - is that intentional ?!

Typo in symlink-manifest: this should be ltr, not lrt (several times)
16x16/stock/gtk-redo-lrt.png ../../16x16/actions/edit-redo.png

Also, why do ltr and rtl links pint to the same file ? that cannot be right...
16x16/stock/gtk-redo-rtl.png ../../16x16/actions/edit-redo.png

Similar for 
20x20/stock/gtk-jump-to-rtl.png ../../20x20/stock/go-jump.png
20x20/stock/gtk-jump-to-ltr.png ../../20x20/stock/go-jump.png

Also, what is temp-home ?!
16x16/apps/temp-home.icon ../../16x16/mimetypes/user-home.icon

In retrospect, it would have been better to strictly separate splitting and
reorganizing symlinks...

Comment 1 Ray Strode [halfline] 2007-10-14 21:24:40 UTC
Most of these issues aren't fallout from the split.  The old redhat-artwork
package had these problems as well.

I have no idea what temp-home is.  I just moved it over since it was there before.

gtk-redo-rtl and ltr probably point to the same file because they both had the
same md5sum.  I tried to remove redundancy where I could to save space. 

The question is why do they have the same md5sum? I'm guessing there was some
brokeness in the %install section of doom in the old redhat-artwork packaage,
such that they didn't get flipped.

(I believe we actually automatically flipped some icons with imagemagick or some
such before, that mechanism may have been broken).

Would probably be better to file these issues as separate reports, no?

Comment 2 Bug Zapper 2008-04-04 14:06:03 UTC
Based on the date this bug was created, it appears to have been reported
during the development of Fedora 8. In order to refocus our efforts as
a project we are changing the version of this bug to '8'.

If this bug still exists in rawhide, please change the version back to
(If you're unable to change the bug's version, add a comment to the bug
and someone will change it for you.)

Thanks for your help and we apologize for the interruption.

The process we're following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

Comment 3 Bug Zapper 2008-11-26 07:58:40 UTC
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  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 '8'.

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 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 

Comment 4 Bug Zapper 2009-01-09 07:19:12 UTC
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 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.

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.