First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 81862
Alias:
Product:
Component:
Status: RESOLVED
Resolution: UPSTREAM
Assigned To: Gentoo KDE team <kde@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Diego E. 'Flameeyes' Pettenò <flameeyes@gentoo.org>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
k3b.patch Patch over current ebuild. patch Diego E. 'Flameeyes' Pettenò 2005-02-13 08:01 0000 898 bytes Details | Diff
k3b-hicolor-icons.tar.bz2 Hicolor icons for k3b. application/octet-stream Diego E. 'Flameeyes' Pettenò 2005-02-13 08:01 0000 3.03 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 81862 depends on: Show dependency tree
Bug 81862 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2005-02-13 08:01 0000 
K3B's ebuild at the moment copies the crystalsvg icon into the nonstandard
/usr/share/pixmaps directory to fix bug #55272.
The attached patch applied over the current ebuild (and the tarball attached,
which is referred in mirror://gentoo on SRC_URI in the patched ebuild), fixes
the problem in a better way, adding the real hicolor neutral icons to the
hicolor structure.

This is just temporary: I already commited the fix on both HEAD and 0.11 branch
on k3b cvs, so next version won't need this at all, and will be correct from
scratch.

HTH, Diego

------- Comment #1 From Diego E. 'Flameeyes' Pettenò 2005-02-13 08:01:28 0000 ------- 
Created an attachment (id=51126) [details]
Patch over current ebuild.

------- Comment #2 From Diego E. 'Flameeyes' Pettenò 2005-02-13 08:01:55 0000 ------- 
Created an attachment (id=51127) [details]
Hicolor icons for k3b.

------- Comment #3 From Gregorio Guidi (RETIRED) 2005-02-17 07:18:39 0000 ------- 
I think we will just wait for the next version, then. There's really no need 
to push out a new revision if it will be properly fixed soon.
First Last Prev Next    No search results available      Search page      Enter new bug