Bug 697303 - gnome-themes update conflicts with installed gnome-themes-standard
Summary: gnome-themes update conflicts with installed gnome-themes-standard
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-themes
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-17 15:54 UTC by Michal Jaegermann
Modified: 2013-05-26 02:10 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-26 02:10:01 UTC
Type: ---


Attachments (Terms of Use)

Description Michal Jaegermann 2011-04-17 15:54:45 UTC
Description of problem:

An attempt to update produces the following:

Transaction Check Error:
  file /usr/share/icons/HighContrast/index.theme from install of gnome-themes-2.32.0-5.fc16.noarch conflicts with file from package gnome-themes-standard-3.0.0-1.fc15.x86_64
  file /usr/share/icons/HighContrastInverse/index.theme from install of gnome-themes-2.32.0-5.fc16.noarch conflicts with file from package gnome-themes-standard-3.0.0-1.fc15.x86_64
  file /usr/share/themes/HighContrast/index.theme from install of gnome-themes-2.32.0-5.fc16.noarch conflicts with file from package gnome-themes-standard-3.0.0-1.fc15.x86_64
  file /usr/share/themes/HighContrastInverse/index.theme from install of gnome-themes-2.32.0-5.fc16.noarch conflicts with file from package gnome-themes-standard-3.0.0-1.fc15.x86_64
  file /usr/share/themes/HighContrast/gtk-2.0/gtkrc from install of gnome-themes-2.32.0-5.fc16.noarch conflicts with file from package gnome-themes-standard-3.0.0-1.fc15.x86_64
  file /usr/share/themes/HighContrastInverse/gtk-2.0/gtkrc from install of gnome-themes-2.32.0-5.fc16.noarch conflicts with file from package gnome-themes-standard-3.0.0-1.fc15.x86_64
  file /usr/share/themes/LowContrast/gtk-2.0/gtkrc from install of gnome-themes-2.32.0-5.fc16.noarch conflicts with file from package gnome-themes-standard-3.0.0-1.fc15.x86_64

A missing "obsoletes" or a real conflct?

Version-Release number of selected component (if applicable):
gnome-themes-2.32.0-5.fc16
gnome-themes-standard-3.0.0-1.fc15

How reproducible:
always unless gnome-themes-standard is removed

Comment 1 Michal Jaegermann 2011-04-17 16:02:29 UTC
OK, "themes/Adwaita" from gnome-themes-standard is missing in gnome-themes-2.32.0-5.fc16.noarch; so this is not exactly a replacement.

Comment 2 Michal Jaegermann 2011-04-24 20:02:46 UTC
gnome-themes-2.32.0-5.fc16 and new gnome-themes-standard-3.0.0-4.fc16 suffer from the same file conflicts.

Comment 3 Paul Bolle 2011-05-15 11:24:33 UTC
(In reply to comment #2)
> gnome-themes-2.32.0-5.fc16 and new gnome-themes-standard-3.0.0-4.fc16 suffer
> from the same file conflicts.

Ditto gnome-themes-2.32.0-5.fc16 and gnome-themes-standard-3.1.1-1.fc16.

Comment 4 Paul Bolle 2011-05-20 20:54:11 UTC
0) Fixed in 2.32.0-6. See its changelog:

* Mon May 16 2011 Matthias Clasen <mclasen> - 2.32.0-6
- Drop accessibility themes to avoid conflict with gnome-themes-standard
- [...]

1) Please close.

Comment 5 Peter H. Jones 2011-08-25 05:19:46 UTC
I'm seeing a similar problem after trying to upgrade from F14 to F15. Here's the actual output I am getting:
"	file /usr/share/icons/HighContrast/index.theme from install of gnome-themes-standard-3.0.2-1.fc15.x86_64 conflicts with file from package gnome-themes-2.32.0-1.fc14.noarch
	file /usr/share/icons/HighContrastInverse/index.theme from install of gnome-themes-standard-3.0.2-1.fc15.x86_64 conflicts with file from package gnome-themes-2.32.0-1.fc14.noarch
	file /usr/share/themes/HighContrast/index.theme from install of gnome-themes-standard-3.0.2-1.fc15.x86_64 conflicts with file from package gnome-themes-2.32.0-1.fc14.noarch
	file /usr/share/themes/HighContrastInverse/index.theme from install of gnome-themes-standard-3.0.2-1.fc15.x86_64 conflicts with file from package gnome-themes-2.32.0-1.fc14.noarch
	file /usr/share/themes/HighContrast/gtk-2.0/gtkrc from install of gnome-themes-standard-3.0.2-1.fc15.x86_64 conflicts with file from package gnome-themes-2.32.0-1.fc14.noarch
	file /usr/share/themes/HighContrastInverse/gtk-2.0/gtkrc from install of gnome-themes-standard-3.0.2-1.fc15.x86_64 conflicts with file from package gnome-themes-2.32.0-1.fc14.noarch
	file /usr/share/themes/LowContrast/gtk-2.0/gtkrc from install of gnome-themes-standard-3.0.2-1.fc15.x86_64 conflicts with file from package gnome-themes-2.32.0-1.fc14.noarch
	file /usr/share/gnome/help/fdl/ca/fdl.xml from install of gnome-desktop3-3.0.1-2.fc15.x86_64 conflicts with file from package gnome-desktop-2.32.0-2.fc14.x86_64
	file /usr/share/gnome/help/gpl/zh_CN/gpl.xml from install of gnome-desktop3-3.0.1-2.fc15.x86_64 conflicts with file from package gnome-desktop-2.32.0-2.fc14.x86_64
	file /usr/share/gnome/help/lgpl/zh_CN/lgpl.xml from install of gnome-desktop3-3.0.1-2.fc15.x86_64 conflicts with file from package gnome-desktop-2.32.0-2.fc14.x86_64
	file /usr/share/omf/gpl/gpl-zh_CN.omf from install of gnome-desktop3-3.0.1-2.fc15.x86_64 conflicts with file from package gnome-desktop-2.32.0-2.fc14.x86_64
	file /usr/share/omf/lgpl/lgpl-zh_CN.omf from install of gnome-desktop3-3.0.1-2.fc15.x86_64 conflicts with file from package gnome-desktop-2.32.0-2.fc14.x86_64
"

This problem is preventing me from updating my system.

Comment 6 Fedora End Of Life 2013-04-03 16:07:58 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

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

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 7 Matthias Clasen 2013-05-26 02:10:01 UTC
the f19 packages of gnome-themes-standard and gnome-themes don't conflict anymore


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