Bug 704727

Summary: upgrade from F-14 broken due to conflicts with gnome-themes
Product: [Fedora] Fedora Reporter: Peter Robinson <pbrobinson>
Component: gnome-themes-standardAssignee: Cosimo Cecchi <ccecchi>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: awilliam, ccecchi, jlaska, mclasen, zaitcev
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: RejectedBlocker
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-11 14:16:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Peter Robinson 2011-05-14 12:25:59 UTC
The upgrade (using yum in this case) is broken from F-14 on a standard gnome desktop install due to package conflicts with the old gnome-themes package.

  file /usr/share/themes/HighContrast/gtk-2.0/gtkrc from install of gnome-themes-standard-3.0.1-1.fc15.i686 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.1-1.fc15.i686 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.1-1.fc15.i686 conflicts with file from package gnome-themes-2.32.0-1.fc14.noarch
  file /usr/share/icons/HighContrast/index.theme from install of gnome-themes-standard-3.0.1-1.fc15.i686 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.1-1.fc15.i686 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.1-1.fc15.i686 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.1-1.fc15.i686 conflicts with file from package gnome-themes-2.32.0-1.fc14.noarch

Comment 1 Adam Williamson 2011-05-14 15:25:24 UTC
same story again: current f15 gnome-themes is gnome-themes-2.32.0-6.fc15 and does not conflict with gnome-themes-standard. again, need to know how your upgrade missed this.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 2 James Laska 2011-05-16 16:23:15 UTC
Discussed during 2011-05-16 Fedora QA blocker review meeting [1].  Reserving decision until additional yum update information is available.  Note, that yum updates are not the supported/recommended upgrade procedure.  Therefore, it is unlikely that this issue would block the release.  Day-0 updates to the 'updates' repository may be sufficient to address a 'yum' distro-sync upgrade issue.

[1] http://meetbot.fedoraproject.org/fedora-meeting/2011-05-16/fedora-qa.2011-05-16-15.00.html

Comment 3 Cosimo Cecchi 2011-05-16 17:12:49 UTC
*** Bug 704358 has been marked as a duplicate of this bug. ***

Comment 4 Adam Williamson 2011-05-16 19:55:30 UTC
a thought occurs...did you do 'yum update yum', and hit the issue at that point?



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 5 Adam Williamson 2011-05-17 21:25:34 UTC
Discussed at the go/no-go meeting of 2011-05-17. Agreed that this is not a blocker; as described it affects only yum upgrades, which are explicitly not supported and not specified in the release criteria. Additionally, no-one claims to be able to reproduce this while several say they have done yum upgrades and _not_ seen this, and no-one has seen a similar issue using any supported upgrade mechanism.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 6 Pete Zaitcev 2011-05-18 01:02:26 UTC
I don't care if anything is blocker or not, but I need to know how to
resolve the problem. What do I need to remove/update/reinstall to create
a system that continues to upgrade? Also, I don't know about Peter, but
my bug was reported against Rawhide, where release criteria not not even
applicable in the first place.

Comment 7 Pete Zaitcev 2011-05-18 01:04:18 UTC
Er, I take this back, somewhat. Just saw Adam's update for bz#704358, this
might have been an erroneous dup by Cosimo.

Comment 8 Peter Robinson 2011-06-11 14:16:56 UTC
Going to close these as I don't have the full logs. It seems I forced removal with rpm and let yum clean up the problem by pulling in the associated deps.