Bug 705032 - compose blocked by gnome-themes
Summary: compose blocked by gnome-themes
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-themes
Version: rawhide
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-05-16 13:05 UTC by Ales Kozumplik
Modified: 2014-09-30 23:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-16 13:15:36 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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
Note You need to log in before you can comment on or make changes to this bug.