Bug 705032

Summary: compose blocked by gnome-themes
Product: [Fedora] Fedora Reporter: Ales Kozumplik <akozumpl>
Component: gnome-themesAssignee: Matthias Clasen <mclasen>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: jzeleny, mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-16 13:15:36 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 Ales Kozumplik 2011-05-16 13:05:22 UTC
It is not possible to make a proper compose with pungi on rawhide recently. 
Below is how pungi bombs out, but basically it's about files existing with both gnome-themes-standard and gnome-themes. Perhaps one of the packages should be dropped?

Traceback (most recent call last):
  File "/usr/bin/pungi", line 216, in <module>
    main()
  File "/usr/bin/pungi", line 120, in main
    mypungi.doBuildinstall()
  File "/usr/lib/python2.7/site-packages/pypungi/__init__.py", line 799, in doBuildinstall
    workdir=workdir, outputdir=outputdir)
  File "/usr/lib/python2.7/site-packages/pylorax/__init__.py", line 263, in run
    self.installtree.yum.process_transaction(skipbroken)
  File "/usr/lib/python2.7/site-packages/pylorax/yumhelper.py", line 146, in process_transaction
    rpmDisplay=LoraxRpmCallback())
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 4501, in processTransaction
    self._doTestTransaction(callback,display=rpmTestDisplay)
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 4600, in _doTestTransaction
    raise Errors.YumTestTransactionError, errstring
yum.Errors.YumTestTransactionError: Test Transaction Errors:   file /usr/share/icons/HighContrast/index.theme conflicts between attempted installs of gnome-themes-standard-3.1.1-1.fc16.i686 and gnome-themes-2.32.0-5.fc16.noarch
  file /usr/share/icons/HighContrastInverse/index.theme conflicts between attempted installs of gnome-themes-standard-3.1.1-1.fc16.i686 and gnome-themes-2.32.0-5.fc16.noarch
  file /usr/share/themes/HighContrast/gtk-2.0/gtkrc conflicts between attempted installs of gnome-themes-standard-3.1.1-1.fc16.i686 and gnome-themes-2.32.0-5.fc16.noarch
  file /usr/share/themes/HighContrast/index.theme conflicts between attempted installs of gnome-themes-standard-3.1.1-1.fc16.i686 and gnome-themes-2.32.0-5.fc16.noarch
  file /usr/share/themes/HighContrastInverse/gtk-2.0/gtkrc conflicts between attempted installs of gnome-themes-standard-3.1.1-1.fc16.i686 and gnome-themes-2.32.0-5.fc16.noarch
  file /usr/share/themes/HighContrastInverse/index.theme conflicts between attempted installs of gnome-themes-standard-3.1.1-1.fc16.i686 and gnome-themes-2.32.0-5.fc16.noarch
  file /usr/share/themes/LowContrast/gtk-2.0/gtkrc conflicts between attempted installs of gnome-themes-standard-3.1.1-1.fc16.i686 and gnome-themes-2.32.0-5.fc16.noarch

Comment 1 Matthias Clasen 2011-05-16 13:15:36 UTC
Should be fixed in gnome-themes-2.32.0-6.fc16