Conflicts in latest update

[Ankur Sinha]

hey,

Trying a "yum update" gives me this. Broken update?


Transaction Check Error:
  file /usr/lib64/gstreamer-0.10/libgstshapewipe.so from install of
gstreamer-plugins-good-0.10.21-1.fc12.x86_64 conflicts with file from
package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/bin/gst-camera from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/bin/gst-camera-perf from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstadpcmdec.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstaiff.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstalsaspdif.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstapexsink.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstassrender.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstbayer.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstbz2.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstcamerabin.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstcdaudio.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstcdxaparse.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstcelt.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstdc1394.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstdccp.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstdebugutilsbad.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstdirac.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstdvb.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstfestival.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstfreeze.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstfrei0r.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstgsm.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgsth264parse.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgsthdvparse.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstid3tag.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstjp2k.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstkate.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstladspa.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstlegacyresample.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstlv2.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstmetadata.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstmodplug.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstmpeg4videoparse.so from install
of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstmpegvideoparse.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstmusepack.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstmve.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstmxf.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstnsf.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstnuvdemux.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstofa.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstpcapparse.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstpnm.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstrawparse.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstrfbsrc.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstrsvg.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstscaletempoplugin.so from install
of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstsdpelem.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstsndfile.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstspeed.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgststereo.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstsubenc.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgsttta.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstvcdsrc.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstvideomeasure.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstvideosignal.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstvmnc.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libgstzbar.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/gstreamer-0.10/libresindvd.so from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/libgstbasevideo-0.10.so.0.0.0 from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/libgstphotography-0.10.so.0.0.0 from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/lib64/libgstsignalprocessor-0.10.so.0.0.0 from install of
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts with file
from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/af/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/az/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/bg/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/ca/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/cs/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/da/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/de/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/en_GB/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/es/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/eu/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/fi/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/fr/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/hu/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/id/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/it/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/ja/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/ky/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/lt/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/lv/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/mt/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/nb/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/nl/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/or/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/pl/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/pt_BR/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/ru/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/sk/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/sq/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/sr/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/sv/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/tr/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/uk/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/vi/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
  file /usr/share/locale/zh_CN/LC_MESSAGES/gst-plugins-bad-0.10.mo from
install of gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 conflicts
with file from package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64

Error Summary
-------------

-- 
regards,
Ankur 
- FAS : ankursinha ; franciscod @ Freenode
- gpg --keyserver pgp.mit.edu --recv-keys 5E9BF638

[Till Maas]

On Tue, Mar 16, 2010 at 12:19:56PM +0530, Ankur Sinha wrote:

>  Trying a "yum update" gives me this. Broken update?
>  
>  
>  Transaction Check Error:
>    file /usr/lib64/gstreamer-0.10/libgstshapewipe.so from install of
>  gstreamer-plugins-good-0.10.21-1.fc12.x86_64 conflicts with file from
>  package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
>    file /usr/bin/gst-camera from install of 
If you look closer, you will notice that one of the packages comes from
RPMFusion.

Regards
Till

[Ankur Sinha]

On Tue, 2010-03-16 at 08:51 +0100, Till Maas wrote:
>  On Tue, Mar 16, 2010 at 12:19:56PM +0530, Ankur Sinha wrote:
>  
>  > Trying a "yum update" gives me this. Broken update?
>  > 
>  > 
>  > Transaction Check Error:
>  >   file /usr/lib64/gstreamer-0.10/libgstshapewipe.so from install of
>  > gstreamer-plugins-good-0.10.21-1.fc12.x86_64 conflicts with file from
>  > package gstreamer-plugins-bad-0.10.17-2.fc12.x86_64
>  >   file /usr/bin/gst-camera from install of
>  
>  If you look closer, you will notice that one of the packages comes from
>  RPMFusion.
>  
>  Regards
>  Till
>  --  
hey,

I did notice that. I wasn't sure why a package from rpmfusion would
conflict with one from fedora repos. (It's in rpmfusion for a reason)
Is it being obsoleted by a fedora package (license been cleared or
something)? 

What I'm saying is that this conflict makes users uninstall manually to
proceed with the update. I use yum and know a little bit about this
stuff. What about normal users who wouldn't understand why an update
using a GUI is breaking?

Isn't there a better way to handle whatever transition is taking place
here?

-- 
regards,
Ankur 
- FAS : ankursinha ; franciscod @ Freenode
- gpg --keyserver pgp.mit.edu --recv-keys 5E9BF638

[Matej Cepl]

Dne 16.3.2010 09:50, Ankur Sinha napsal(a):
>  I did notice that. I wasn't sure why a package from rpmfusion
> would
>  conflict with one from fedora repos. (It's in rpmfusion for a reason)
>  Is it being obsoleted by a fedora package (license been cleared or
>  something)? 
There are constantly modules moving between -good, -bad, -ugly packages 
of gstreamer, and sometimes rpmfusion packages are not in sync with 
Fedora ones. Give rpmfusion packagers some time to fix it (or join them 
and help to fix it on your own).

Matěj

-- 
http://www.ceplovi.cz/matej/, Jabber: mcepl<at>ceplovi.cz
GPG Finger: 89EF 4BC6 288A BF43 1BAB  25C3 E09F EF25 D964 84AC

He uses statistics as a drunken man uses lamp-posts... for
support, rather than illumination.
       -- Andrew Lang

[Jon Masters]

On Tue, 2010-03-16 at 11:16 +0100, Matěj Cepl wrote:
>  Dne 16.3.2010 09:50, Ankur Sinha napsal(a):
>  > I did notice that. I wasn't sure why a package from rpmfusion would
>  > conflict with one from fedora repos. (It's in rpmfusion for a reason)
>  > Is it being obsoleted by a fedora package (license been cleared or
>  > something)?
>  
>  There are constantly modules moving between -good, -bad, -ugly packages 
>  of gstreamer, and sometimes rpmfusion packages are not in sync with 
>  Fedora ones. Give rpmfusion packagers some time to fix it (or join them 
>  and help to fix it on your own). 
I'd just add those gstreamer packages to my exclude config in yum for
the moment, if you don't want to deal with the breakage each time. Then
you can remove those excludes when the repos catch up with each other.

/etc/yum.conf:

exclude=gstreamer-plugins-bad-free gstreamer-plugins-good

Jon.

[Matej Cepl]

Dne 16.3.2010 13:04, Jon Masters napsal(a):
>  I'd just add those gstreamer packages to my exclude config in yum
> for
>  the moment, if you don't want to deal with the breakage each time. Then
>  you can remove those excludes when the repos catch up with each other.
>
>  /etc/yum.conf:
>
>  exclude=gstreamer-plugins-bad-free gstreamer-plugins-good 
It's safer to use --skip-broken parameter of yum for awhile. These lines 
in /etc/yum.conf tends to be forgotten.

Matěj

-- 
http://www.ceplovi.cz/matej/, Jabber: mcepl<at>ceplovi.cz
GPG Finger: 89EF 4BC6 288A BF43 1BAB  25C3 E09F EF25 D964 84AC

He uses statistics as a drunken man uses lamp-posts... for
support, rather than illumination.
       -- Andrew Lang

[Ralf Corsepius]

On 03/16/2010 01:37 PM, Matěj Cepl wrote:
>  Dne 16.3.2010 13:04, Jon Masters napsal(a):
> > I'd just add those gstreamer packages to my exclude config in yum for
> > the moment, if you don't want to deal with the breakage each time. Then
> > you can remove those excludes when the repos catch up with each other.
> >
> > /etc/yum.conf:
> >
> > exclude=gstreamer-plugins-bad-free gstreamer-plugins-good
>
>  It's safer to use --skip-broken parameter of yum for awhile. 
Doesn't work in this particular case, because yum doesn't catch the file 
conflicts this update causes.

[Jon Masters]

On Tue, 2010-03-16 at 13:44 +0100, Ralf Corsepius wrote:
>  On 03/16/2010 01:37 PM, Matěj Cepl wrote:
>  > Dne 16.3.2010 13:04, Jon Masters napsal(a):
>  >> I'd just add those gstreamer packages to my exclude config in yum for
>  >> the moment, if you don't want to deal with the breakage each time. Then
>  >> you can remove those excludes when the repos catch up with each other.
>  >>
>  >> /etc/yum.conf:
>  >>
>  >> exclude=gstreamer-plugins-bad-free gstreamer-plugins-good
>  >
>  > It's safer to use --skip-broken parameter of yum for awhile.
>  
>  Doesn't work in this particular case, because yum doesn't catch the file 
>  conflicts this update causes. 
Right, that would be why I suggested the exclude and not skip-broken. I
didn't file a bug because I thought this naming issue/conflict was well
known by now. I've seen similar in the past, apologies for assuming.

Jon.

[Thorsten Leemhuis]

Jon Masters wrote on 16.03.2010 13:04:
>  On Tue, 2010-03-16 at 11:16 +0100, Matěj Cepl wrote:
> > Dne 16.3.2010 09:50, Ankur Sinha napsal(a):
> > > I did notice that. I wasn't sure why a package from rpmfusion would
> > > conflict with one from fedora repos. (It's in rpmfusion for a reason)
> > > Is it being obsoleted by a fedora package (license been cleared or
> > > something)?
> > 
> > There are constantly modules moving between -good, -bad, -ugly packages 
> > of gstreamer, and sometimes rpmfusion packages are not in sync with 
> > Fedora ones. Give rpmfusion packagers some time to fix it (or join them 
> > and help to fix it on your own).
>  
>  I'd just add those gstreamer packages to my exclude config in yum for
>  the moment, if you don't want to deal with the breakage each time. Then
>  you can remove those excludes when the repos catch up with each other.
>  
>  /etc/yum.conf:
>  
>  exclude=gstreamer-plugins-bad-free gstreamer-plugins-good 
There are so many developers around on this list that know: reporting
bugs is the right way to get problems fixed and fixing things is way
better than posting workarounds to public places for various reasons --
nevertheless nobody filed a bug yet afaics  :-/

CU
thl

P.S.: A updated gst-plugins-bad package that afaik solves the problem in
question was pushed to the proper RPM Fusion repos one or two hours ago,
so there is no need to report a bug anymore afaics -- but people will
continue to see the problem for the next ~24 hours or so due to
mirror-lag and caching issues

[Ankur Sinha]

On Tue, 2010-03-16 at 13:45 +0100, Thorsten Leemhuis wrote:
>  Jon Masters wrote on 16.03.2010 13:04:
>  > On Tue, 2010-03-16 at 11:16 +0100, Matěj Cepl wrote:
>  >> Dne 16.3.2010 09:50, Ankur Sinha napsal(a):
>  >> > I did notice that. I wasn't sure why a package from rpmfusion would
>  >> > conflict with one from fedora repos. (It's in rpmfusion for a reason)
>  >> > Is it being obsoleted by a fedora package (license been cleared or
>  >> > something)?
>  >> 
>  >> There are constantly modules moving between -good, -bad, -ugly packages 
>  >> of gstreamer, and sometimes rpmfusion packages are not in sync with 
>  >> Fedora ones. Give rpmfusion packagers some time to fix it (or join them 
>  >> and help to fix it on your own).
>  > 
>  > I'd just add those gstreamer packages to my exclude config in yum for
>  > the moment, if you don't want to deal with the breakage each time. Then
>  > you can remove those excludes when the repos catch up with each other.
>  > 
>  > /etc/yum.conf:
>  > 
>  > exclude=gstreamer-plugins-bad-free gstreamer-plugins-good
>  
>  There are so many developers around on this list that know: reporting
>  bugs is the right way to get problems fixed and fixing things is way
>  better than posting workarounds to public places for various reasons --
>  nevertheless nobody filed a bug yet afaics  :-/
>  
>  CU
>  thl
>  
>  P.S.: A updated gst-plugins-bad package that afaik solves the problem in
>  question was pushed to the proper RPM Fusion repos one or two hours ago,
>  so there is no need to report a bug anymore afaics -- but people will
>  continue to see the problem for the next ~24 hours or so due to
>  mirror-lag and caching issues 
Hey,

I'm really grateful for the info. I didn't have enough knowledge on the
transitions going on wrt gst packages which is why I hadn't reported a
bug yet. The intention of the thread here was to get more info on what
was going on. 

-- 
regards,
Ankur 
- FAS : ankursinha ; franciscod @ Freenode
- gpg --keyserver pgp.mit.edu --recv-keys 5E9BF638

[Thorsten Leemhuis]

Ankur Sinha wrote on 16.03.2010 14:33:
>  On Tue, 2010-03-16 at 13:45 +0100, Thorsten Leemhuis wrote:
> > Jon Masters wrote on 16.03.2010 13:04:
> > > On Tue, 2010-03-16 at 11:16 +0100, Matěj Cepl wrote:
> > >> Dne 16.3.2010 09:50, Ankur Sinha napsal(a):
> > >> > I did notice that. I wasn't sure why a package from rpmfusion
> would
> > >> > conflict with one from fedora repos. (It's in rpmfusion for a
> reason)
> > >> > Is it being obsoleted by a fedora package (license been cleared or
> > >> > something)?
> > >> There are constantly modules moving between -good, -bad, -ugly packages 
> > >> of gstreamer, and sometimes rpmfusion packages are not in sync with 
> > >> Fedora ones. Give rpmfusion packagers some time to fix it (or join them 
> > >> and help to fix it on your own).
> > > I'd just add those gstreamer packages to my exclude config in yum for
> > > the moment, if you don't want to deal with the breakage each time. Then
> > > you can remove those excludes when the repos catch up with each other.
> > > /etc/yum.conf:
> > > exclude=gstreamer-plugins-bad-free gstreamer-plugins-good
> > There are so many developers around on this list that know: reporting
> > bugs is the right way to get problems fixed and fixing things is way
> > better than posting workarounds to public places for various reasons --
> > nevertheless nobody filed a bug yet afaics  :-/
>  [...]
>  I'm really grateful for the info. 
np

>  I didn't have enough knowledge on the transitions going on wrt
> gst packages 
In case you got it wrong: my "There are so many developers around on
this list that know..." rant was not sent in your direction ;-)

>  which is why I hadn't reported a bug yet. The intention of the
> thread
>  here was to get more info on what was going on. 
That's fine, but OTOH: A lot of people seem to think like that and that
afaics often leads to a situation where nobody reports the bug :-/ Note
that this is not specific to RPM Fusion, it's a general problem that
just worse when it comes to RPM Fusion, as it only has a quite small
number of contributors...

CU
knurd

[Till Maas]

On Tue, Mar 16, 2010 at 01:45:33PM +0100, Thorsten Leemhuis wrote:

>  There are so many developers around on this list that know:
> reporting
>  bugs is the right way to get problems fixed and fixing things is way
>  better than posting workarounds to public places for various reasons --
>  nevertheless nobody filed a bug yet afaics  :-/ 
Imho it was not that obvious that there is a bug present, because these
kind of delays are usual with RPMFusion, because the repos are not
directly synced. E.g. I just expected it to work within some days and if
it did not, then I would have thought there might be something wrong.

Regards
Till

[Thorsten Leemhuis]

On 16.03.2010 17:42, Till Maas wrote:
>  On Tue, Mar 16, 2010 at 01:45:33PM +0100, Thorsten Leemhuis wrote:
> > There are so many developers around on this list that know: reporting
> > bugs is the right way to get problems fixed and fixing things is way
> > better than posting workarounds to public places for various reasons --
> > nevertheless nobody filed a bug yet afaics  :-/
>  Imho it was not that obvious that there is a bug present, because these
>  kind of delays are usual with RPMFusion, because the repos are not
>  directly synced. 
That IMHO something that needs fixing on the Fedora side (e.g. in yum)
http://www.redhat.com/archives/fedora-devel-list/2008-August/msg00041.html
But I lost energy driving a solution forward.

>  E.g. I just expected it to work within some days and if
>  it did not, then I would have thought there might be something wrong. 
Well, there were a few cases in the past where problems like this one
persisted for a few days because everybody thought like you outline :-/
But I have no solution for that apart from "if in a doubt file a bug" :-(

CU
knurd

[James Antill]

On Tue, 2010-03-16 at 20:09 +0100, Thorsten Leemhuis wrote:
>  On 16.03.2010 17:42, Till Maas wrote:
>  > On Tue, Mar 16, 2010 at 01:45:33PM +0100, Thorsten Leemhuis wrote:
>  >> There are so many developers around on this list that know: reporting
>  >> bugs is the right way to get problems fixed and fixing things is way
>  >> better than posting workarounds to public places for various reasons --
>  >> nevertheless nobody filed a bug yet afaics  :-/
>  > Imho it was not that obvious that there is a bug present, because these
>  > kind of delays are usual with RPMFusion, because the repos are not
>  > directly synced.
>  
>  That IMHO something that needs fixing on the Fedora side (e.g. in yum)
>  http://www.redhat.com/archives/fedora-devel-list/2008-August/msg00041.html
>  But I lost energy driving a solution forward. 
 I'm not sure what you want us to do, the main problem is that splitting
a DB of packages and then stitching it back together doesn't work 100%
of the time ... this isn't us being stupid:

http://en.wikipedia.org/wiki/CAP_Theorem

...yum repo DBs are AP and not C.
 Skip-broken helps in all cases apart from file conflicts, which is a
packaging bug. Your idea of "timed skip-broken by default" doesn't work
because we don't have a "date package was released" ... although PK
currently does skip-broken by default, all the time.

>  > E.g. I just expected it to work within some days and if
>  > it did not, then I would have thought there might be something wrong.
>  
>  Well, there were a few cases in the past where problems like this one
>  persisted for a few days because everybody thought like you outline :-/
>  But I have no solution for that apart from "if in a doubt file a bug" :-(
 Rpmfusion can run auto QA like tests on rpmfusion and Fedora (I don't
think we can legally do the same ... but I'm not sure). Finding the file
conflicts automatically is harder (you need to download all the rpms),
and it's not fast, but it's possible (Seth has a script, IIRC).

-- 
James Antill - james(a)fedoraproject.org
http://yum.baseurl.org/wiki/releases
http://yum.baseurl.org/wiki/whatsnew/3.2.27
http://yum.baseurl.org/wiki/YumMultipleMachineCaching

[Seth Vidal]

On Tue, 16 Mar 2010, James Antill wrote:

>  Rpmfusion can run auto QA like tests on rpmfusion and Fedora (I don't
>  think we can legally do the same ... but I'm not sure). Finding the file
>  conflicts automatically is harder (you need to download all the rpms),
>  and it's not fast, but it's possible (Seth has a script, IIRC). 
The script does this:

1. look up any potential conflicts in the filelists metadata
2. download the headers from those pkgs and see if the conflicts are real 
or fake conflicts (ie: multilib-allowed)

it's not fast - it has to traverse a lot of data, of course.
-sv

[Jesse Keating]

On Tue, 2010-03-16 at 15:46 -0400, James Antill wrote:
>  but it's possible (Seth has a script, IIRC). 
I do believe seth's script works purely from metadata without
downloading the rpms.

-- 
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating

[Seth Vidal]

On Tue, 16 Mar 2010, Jesse Keating wrote:

>  On Tue, 2010-03-16 at 15:46 -0400, James Antill wrote:
> > but it's possible (Seth has a script, IIRC).
>
>  I do believe seth's script works purely from metadata without
>  downloading the rpms. 
it gets the headers from the pkgs w/o downloading the whole package.

the magic of byte-ranges

-sv

[Thorsten Leemhuis]

On 16.03.2010 20:46, James Antill wrote:
>  On Tue, 2010-03-16 at 20:09 +0100, Thorsten Leemhuis wrote:
> > On 16.03.2010 17:42, Till Maas wrote:
> >> On Tue, Mar 16, 2010 at 01:45:33PM +0100, Thorsten Leemhuis wrote:
> >>> There are so many developers around on this list that know: reporting
> >>> bugs is the right way to get problems fixed and fixing things is way
> >>> better than posting workarounds to public places for various reasons --
> >>> nevertheless nobody filed a bug yet afaics  :-/
> >> Imho it was not that obvious that there is a bug present, because these
> >> kind of delays are usual with RPMFusion, because the repos are not
> >> directly synced.
> > That IMHO something that needs fixing on the Fedora side (e.g. in yum)
> > http://www.redhat.com/archives/fedora-devel-list/2008-August/msg00041.html
> > But I lost energy driving a solution forward.
>   I'm not sure what you want us to do, 
Actually I'm not sure myself what to do and haven't put much thought
into it lately...

>  the main problem is that splitting
>  a DB of packages and then stitching it back together doesn't work 100%
>  of the time ... this isn't us being stupid:
>  http://en.wikipedia.org/wiki/CAP_Theorem
>  ...yum repo DBs are AP and not C. 
Well, the big hammer solution to make it work 100% of the time then
would be: RPM Fusion should disable the Fedora repos and provide the
matching repodata for Fedora itself.

But that solution would be over designed, complicated and inflexible, so
don't take that suggestion seriously ;-)

But I don't think 100% of the time is needed, but maybe it could be made
a lot whole lot better with some fine tuning. The simple solution that
would fix most of the problems afaics: an additional config value flag
in (say) rpmfusion-free-updates.repo that expresses "if repo
fedora-updates gets updated repodata then check for updated
rpmfusion-free-repodata not only on the mirrors of this configured repo,
but also on server download1.rpmfusion.org (master repo for RPM
Fusion)". Then everything should just work for people as long as RPM
Fusion pushed matching updates in parallel. Note that the stuff needs to
work vice versa as -- e.g. if yum sees updated repo data for RPM Fusion
then check for new fedora-updates repodata as well.

>   Skip-broken helps in all cases apart from file conflicts, which is
> a
>  packaging bug.  
Or a mirror lag and cache problems, like it would have happened with
gst-plugins-bad if we had pushed it at the right time, as in some cases
a freshly updated fedora-updates repo will get combined with a outdated
rpmfusion updates repo from a not-yet-updated mirror (or vice versa).

>  Your idea of "timed skip-broken by default" doesn't
> work 
That was just me thinking out loud ;-) and it's not my preferred
solution for the problem at hand these days...

>  because we don't have a "date package was released" ...
And would that be needed at all? The timer could simply start locally
then yum sees the problem seen for the first time.

But as I said: Not sure if that worth investigating, but it might, as
yum bailing out when a problem happens seems to confuse quite a lot of
people (a colleague of mine for example always gets annoyed by that and
asks for help). Sure, those that don't know how to deal with it might
better be using PK, but we can't force them to do that and those
problems make us look bad :-/


Anyway: the "timed skip-broken by default" has a big downside in any
case: you might lose features temporary. Let's assume new gstreamer
packages where a plugin was moved from -bad to -good. Let's further
assume Fedora and RPM Fusion would have shipped the new matching and
updated packages in parallel. Then yum on some systems will install the
new -bad package from rpmfusion (which lacks the plugin now) but not the
new -good package from Fedora, if the mirror yum chose was not updated
yet (or updated a few hours earlied and was not checked for updated
repodata due to caching). Than the user temporary looses a feature --
bad :-/

> >> E.g. I just expected it to work within some days and if
> >> it did not, then I would have thought there might be something wrong.
> > Well, there were a few cases in the past where problems like this one
> > persisted for a few days because everybody thought like you outline :-/
> > But I have no solution for that apart from "if in a doubt file a bug" :-(
>   Rpmfusion can run auto QA like tests on rpmfusion and Fedora (I don't
>  think we can legally do the same ... but I'm not sure). Finding the file
>  conflicts automatically is harder (you need to download all the rpms),
>  and it's not fast, but it's possible (Seth has a script, IIRC). 
Yeah, sure, that's right, but there were other information that made be
write the above:

RPM Fusion has just a few contributors and so little man-power, it
didn't even manage to get the repo closure scripts running on their own
hosts regularly -- there were some attempts over the years, but nothing
came out of it :-/

I fear that the lack of man power and contributors will result in RPM
Fusion falling apart sooner or later, but I really hope I'm wrong with that.

CU
knurd

[Michael Schwendt]

On Tue, 16 Mar 2010 15:46:16 -0400, James wrote:

>   Rpmfusion can run auto QA like tests on rpmfusion and Fedora (I
> don't
>  think we can legally do the same ... but I'm not sure). Finding the file
>  conflicts automatically is harder (you need to download all the rpms),
>  and it's not fast, but it's possible (Seth has a script, IIRC). 
I've created and published a proof-of-concept script a couple of times
before. It's the one I've used to file all those bugs about conflicts
in Rawhide.
http://mschwendt.fedorapeople.org/confcheck-remote-split2.py
(that's a more experimental version that tries to work with just 1GB of RAM)
It does not download all packages, but just the headers. For packages
stored in a local mirror, the speed isn't too bad. It ran approx. 11 minutes
with remote Rawhide, though, on an average dual core machine.

Will Woods/autoqa features a conflicts checker, too,
https://fedorahosted.org/pipermail/autoqa-results/2010-March/date.html
which is why I haven't continued with filing further tickets or with
enhancing my script.

[Ankur Sinha]

On Tue, 2010-03-16 at 21:46 +0100, Michael Schwendt wrote:
>  On Tue, 16 Mar 2010 15:46:16 -0400, James wrote:
>  
>  >  Rpmfusion can run auto QA like tests on rpmfusion and Fedora (I don't
>  > think we can legally do the same ... but I'm not sure). Finding the file
>  > conflicts automatically is harder (you need to download all the rpms),
>  > and it's not fast, but it's possible (Seth has a script, IIRC).
>  
>  I've created and published a proof-of-concept script a couple of times
>  before. It's the one I've used to file all those bugs about conflicts
>  in Rawhide.
>  http://mschwendt.fedorapeople.org/confcheck-remote-split2.py
>  (that's a more experimental version that tries to work with just 1GB of RAM)
>  It does not download all packages, but just the headers. For packages
>  stored in a local mirror, the speed isn't too bad. It ran approx. 11 minutes
>  with remote Rawhide, though, on an average dual core machine.
>  
>  Will Woods/autoqa features a conflicts checker, too,
>  https://fedorahosted.org/pipermail/autoqa-results/2010-March/date.html
>  which is why I haven't continued with filing further tickets or with
>  enhancing my script. 

hi,

Is there a wiki page with more info on this script please? How it's to
be used etc.?

-- 
regards,
Ankur 
- FAS : ankursinha ; franciscod @ Freenode
- gpg --keyserver pgp.mit.edu --recv-keys 5E9BF638

[Michael Schwendt]

On Wed, 17 Mar 2010 09:32:19 +0530, Ankur wrote:

>  On Tue, 2010-03-16 at 21:46 +0100, Michael Schwendt wrote:
>  > On Tue, 16 Mar 2010 15:46:16 -0400, James wrote:
>  > 
>  > >  Rpmfusion can run auto QA like tests on rpmfusion and Fedora (I don't
>  > > think we can legally do the same ... but I'm not sure). Finding the file
>  > > conflicts automatically is harder (you need to download all the rpms),
>  > > and it's not fast, but it's possible (Seth has a script, IIRC).
>  > 
>  > I've created and published a proof-of-concept script a couple of times
>  > before. It's the one I've used to file all those bugs about conflicts
>  > in Rawhide.
>  > http://mschwendt.fedorapeople.org/confcheck-remote-split2.py
>  > (that's a more experimental version that tries to work with just 1GB of RAM)
>  > It does not download all packages, but just the headers. For packages
>  > stored in a local mirror, the speed isn't too bad. It ran approx. 11 minutes
>  > with remote Rawhide, though, on an average dual core machine.
>  > 
>  > Will Woods/autoqa features a conflicts checker, too,
>  > https://fedorahosted.org/pipermail/autoqa-results/2010-March/date.html
>  > which is why I haven't continued with filing further tickets or with
>  > enhancing my script.
>  
>  
>  hi,
>  
>  Is there a wiki page with more info on this script please? How it's to
>  be used etc.? 
My one reads the system's Yum repo configuration by default (and it only
has a few options explained by --help, such as restricting the check to
packages matching a regexp - and a multilib option could be added but it's
not really tested with x86_64 and multiarch repos). Probably the first thing
I'd change if I continued to work on it is to merge the file mode conflicts
with the file checksum conflicts for better readability.

As an example, with Fedora 12 i686 you currently would get:

$ ./confcheck-remote-split2.py
Target distribution:
    fedora
    rpmfusion-free
    rpmfusion-free-updates
    rpmfusion-free-updates-testing
    updates
    updates-testing
Reading repository metadata...
Pass 1: Potential duplicate files in metadata...
Sorting...
Pruning...
Pass 2: Examining duplicates closer...
WARNING: file mode conflict
    => /usr/share/java/maven2/poms
    => dumbster-1.6-9.fc12.noarch maven2-2.0.8-3.fc12.noarch
WARNING: file mode conflict
    => /usr/share/java/maven2/poms
    => maven2-2.0.8-3.fc12.noarch dumbster-1.6-9.fc12.noarch
WARNING: file mode conflict
    => /usr/lib/libpfm.so.3
    => libpfm-3.5-4.fc12.i686 papi-4.0.0-2.fc12.i686
WARNING: file mode conflict
    => /usr/lib/libpfm.so.3
    => papi-4.0.0-2.fc12.i686 libpfm-3.5-4.fc12.i686
WARNING: file mode conflict
    => /etc/redhat-release
    => fedora-release-12-2.noarch ovirt-node-1.9.0-0.fc12.i686
WARNING: file mode conflict
    => /etc/system-release
    => fedora-release-12-2.noarch ovirt-node-1.9.0-0.fc12.i686
WARNING: file mode conflict
    => /etc/redhat-release
    => generic-release-12-1.noarch ovirt-node-1.9.0-0.fc12.i686
WARNING: file mode conflict
    => /etc/system-release
    => generic-release-12-1.noarch ovirt-node-1.9.0-0.fc12.i686
WARNING: file mode conflict
    => /etc/redhat-release
    => ovirt-node-1.9.0-0.fc12.i686 fedora-release-12-2.noarch
WARNING: file mode conflict
    => /etc/redhat-release
    => ovirt-node-1.9.0-0.fc12.i686 generic-release-12-1.noarch
WARNING: file mode conflict
    => /etc/system-release
    => ovirt-node-1.9.0-0.fc12.i686 fedora-release-12-2.noarch
WARNING: file mode conflict
    => /etc/system-release
    => ovirt-node-1.9.0-0.fc12.i686 generic-release-12-1.noarch
=> plt-scheme-4.1.2-3.fc12.src.rpm
=> 1:plt-scheme-4.1.2-3.fc12.i686 in fedora
  File conflict with: batik-slideshow-1.7-6.fc12.noarch
     /usr/bin/slideshow

=> EMBOSS-6.1.0-6.fc12.src.rpm
=> EMBOSS-6.1.0-6.fc12.i686 in updates
  File conflict with: pscan-1.3-4.fc12.i686
     /usr/bin/pscan
  File conflict with: wcstools-3.8.1-1.fc12.i686
     /usr/bin/remap

=> amule-2.2.6-1.fc12.src.rpm
=> amule-2.2.6-1.fc12.i686 in rpmfusion-free
  File conflict with: cas-0.15-1.fc12.1.noarch
     /usr/bin/cas
     /usr/share/man/man1/cas.1.gz

=> anaconda-12.46-2.fc12.src.rpm
=> anaconda-12.46-2.fc12.i686 in fedora
  File conflict with: ovirt-node-1.9.0-0.fc12.i686
     /usr/sbin/gptsync
     /usr/sbin/showpart

=> asterisk-1.6.1.17-1.fc12.src.rpm
=> asterisk-1.6.1.17-1.fc12.i686 in updates-testing
  File conflict with: callweaver-1.2.1-2.fc12.i686
     /usr/sbin/smsq
     /usr/sbin/streamplayer

=> batik-1.7-6.fc12.src.rpm
=> batik-slideshow-1.7-6.fc12.noarch in fedora
  File conflict with: 1:plt-scheme-4.1.2-3.fc12.i686
     /usr/bin/slideshow

=> callweaver-1.2.1-2.fc12.src.rpm
=> callweaver-1.2.1-2.fc12.i686 in fedora
  File conflict with: asterisk-1.6.1.17-1.fc12.i686
     /usr/sbin/smsq
     /usr/sbin/streamplayer

=> cas-0.15-1.fc12.1.src.rpm
=> cas-0.15-1.fc12.1.noarch in updates
  File conflict with: amule-2.2.6-1.fc12.i686
     /usr/bin/cas
     /usr/share/man/man1/cas.1.gz

=> dcbd-0.9.15-7.fc12.src.rpm
=> dcbd-devel-0.9.15-7.fc12.i686 in updates
  File conflict with: lldpad-devel-0.9.29-1.fc12.i686
     /usr/lib/pkgconfig/dcbd.pc

=> fedora-release-12-2.src.rpm
=> fedora-release-12-2.noarch in updates
  File conflict with: ovirt-node-1.9.0-0.fc12.i686
     /etc/issue.net

=> foo2zjs-0.20080826-3.fc11.src.rpm
=> foo2oak-0.20080826-3.fc11.i586 in rpmfusion-free
  File conflict with: foomatic-db-4.0-8.20091126.fc12.noarch
     /usr/share/foomatic/db/source/driver/foo2oak-z1.xml

=> foomatic-db-4.0-8.20091126.fc12.src.rpm
=> foomatic-db-4.0-8.20091126.fc12.noarch in updates
  File conflict with: foo2oak-0.20080826-3.fc11.i586
     /usr/share/foomatic/db/source/driver/foo2oak-z1.xml

=> generic-release-12-1.src.rpm
=> generic-release-12-1.noarch in updates
  File conflict with: ovirt-node-1.9.0-0.fc12.i686
     /etc/issue.net

=> gnustep-base-1.18.0-5.fc12.src.rpm
=> gnustep-base-devel-1.18.0-5.fc12.i686 in fedora
  File conflict with: libFoundation-devel-1.1.3-11.fc9.i386
     /usr/include/Foundation/Foundation.h
     /usr/include/Foundation/NSArchiver.h
     /usr/include/Foundation/NSArray.h
     /usr/include/Foundation/NSAttributedString.h
     /usr/include/Foundation/NSAutoreleasePool.h
     /usr/include/Foundation/NSBundle.h
     /usr/include/Foundation/NSByteOrder.h
     /usr/include/Foundation/NSCalendarDate.h
     /usr/include/Foundation/NSCharacterSet.h
     /usr/include/Foundation/NSClassDescription.h
     /usr/include/Foundation/NSCoder.h
     /usr/include/Foundation/NSComparisonPredicate.h
     /usr/include/Foundation/NSCompoundPredicate.h
     /usr/include/Foundation/NSConnection.h
     /usr/include/Foundation/NSData.h
     /usr/include/Foundation/NSDate.h
     /usr/include/Foundation/NSDateFormatter.h
     /usr/include/Foundation/NSDebug.h
     /usr/include/Foundation/NSDecimal.h
     /usr/include/Foundation/NSDecimalNumber.h
     /usr/include/Foundation/NSDictionary.h
     /usr/include/Foundation/NSDistantObject.h
     /usr/include/Foundation/NSDistributedLock.h
     /usr/include/Foundation/NSEnumerator.h
     /usr/include/Foundation/NSError.h
     /usr/include/Foundation/NSException.h
     /usr/include/Foundation/NSExpression.h
     /usr/include/Foundation/NSFileHandle.h
     /usr/include/Foundation/NSFileManager.h
     /usr/include/Foundation/NSFormatter.h
     /usr/include/Foundation/NSGeometry.h
     /usr/include/Foundation/NSHashTable.h
     /usr/include/Foundation/NSHost.h
     /usr/include/Foundation/NSInvocation.h
     /usr/include/Foundation/NSKeyValueCoding.h
     /usr/include/Foundation/NSLock.h
     /usr/include/Foundation/NSMapTable.h
     /usr/include/Foundation/NSMethodSignature.h
     /usr/include/Foundation/NSNotification.h
     /usr/include/Foundation/NSNotificationQueue.h
     /usr/include/Foundation/NSNull.h
     /usr/include/Foundation/NSNumberFormatter.h
     /usr/include/Foundation/NSObjCRuntime.h
     /usr/include/Foundation/NSObject.h
     /usr/include/Foundation/NSPathUtilities.h
     /usr/include/Foundation/NSPort.h
     /usr/include/Foundation/NSPortCoder.h
     /usr/include/Foundation/NSPortMessage.h
     /usr/include/Foundation/NSPortNameServer.h
     /usr/include/Foundation/NSPredicate.h
     /usr/include/Foundation/NSProcessInfo.h
     /usr/include/Foundation/NSProxy.h
     /usr/include/Foundation/NSRange.h
     /usr/include/Foundation/NSRunLoop.h
     /usr/include/Foundation/NSScanner.h
     /usr/include/Foundation/NSSerialization.h
     /usr/include/Foundation/NSSet.h
     /usr/include/Foundation/NSSortDescriptor.h
     /usr/include/Foundation/NSStream.h
     /usr/include/Foundation/NSString.h
     /usr/include/Foundation/NSTask.h
     /usr/include/Foundation/NSThread.h
     /usr/include/Foundation/NSTimeZone.h
     /usr/include/Foundation/NSTimer.h
     /usr/include/Foundation/NSURL.h
     /usr/include/Foundation/NSURLHandle.h
     /usr/include/Foundation/NSUndoManager.h
     /usr/include/Foundation/NSUserDefaults.h
     /usr/include/Foundation/NSUtilities.h
     /usr/include/Foundation/NSValue.h
     /usr/include/Foundation/NSZone.h

=> libFoundation-1.1.3-11.fc9.src.rpm
=> libFoundation-devel-1.1.3-11.fc9.i386 in fedora
  File conflict with: gnustep-base-devel-1.18.0-5.fc12.i686
     /usr/include/Foundation/Foundation.h
     /usr/include/Foundation/NSArchiver.h
     /usr/include/Foundation/NSArray.h
     /usr/include/Foundation/NSAttributedString.h
     /usr/include/Foundation/NSAutoreleasePool.h
     /usr/include/Foundation/NSBundle.h
     /usr/include/Foundation/NSByteOrder.h
     /usr/include/Foundation/NSCalendarDate.h
     /usr/include/Foundation/NSCharacterSet.h
     /usr/include/Foundation/NSClassDescription.h
     /usr/include/Foundation/NSCoder.h
     /usr/include/Foundation/NSComparisonPredicate.h
     /usr/include/Foundation/NSCompoundPredicate.h
     /usr/include/Foundation/NSConnection.h
     /usr/include/Foundation/NSData.h
     /usr/include/Foundation/NSDate.h
     /usr/include/Foundation/NSDateFormatter.h
     /usr/include/Foundation/NSDebug.h
     /usr/include/Foundation/NSDecimal.h
     /usr/include/Foundation/NSDecimalNumber.h
     /usr/include/Foundation/NSDictionary.h
     /usr/include/Foundation/NSDistantObject.h
     /usr/include/Foundation/NSDistributedLock.h
     /usr/include/Foundation/NSEnumerator.h
     /usr/include/Foundation/NSError.h
     /usr/include/Foundation/NSException.h
     /usr/include/Foundation/NSExpression.h
     /usr/include/Foundation/NSFileHandle.h
     /usr/include/Foundation/NSFileManager.h
     /usr/include/Foundation/NSFormatter.h
     /usr/include/Foundation/NSGeometry.h
     /usr/include/Foundation/NSHashTable.h
     /usr/include/Foundation/NSHost.h
     /usr/include/Foundation/NSInvocation.h
     /usr/include/Foundation/NSKeyValueCoding.h
     /usr/include/Foundation/NSLock.h
     /usr/include/Foundation/NSMapTable.h
     /usr/include/Foundation/NSMethodSignature.h
     /usr/include/Foundation/NSNotification.h
     /usr/include/Foundation/NSNotificationQueue.h
     /usr/include/Foundation/NSNull.h
     /usr/include/Foundation/NSNumberFormatter.h
     /usr/include/Foundation/NSObjCRuntime.h
     /usr/include/Foundation/NSObject.h
     /usr/include/Foundation/NSPathUtilities.h
     /usr/include/Foundation/NSPort.h
     /usr/include/Foundation/NSPortCoder.h
     /usr/include/Foundation/NSPortMessage.h
     /usr/include/Foundation/NSPortNameServer.h
     /usr/include/Foundation/NSPredicate.h
     /usr/include/Foundation/NSProcessInfo.h
     /usr/include/Foundation/NSProxy.h
     /usr/include/Foundation/NSRange.h
     /usr/include/Foundation/NSRunLoop.h
     /usr/include/Foundation/NSScanner.h
     /usr/include/Foundation/NSSerialization.h
     /usr/include/Foundation/NSSet.h
     /usr/include/Foundation/NSSortDescriptor.h
     /usr/include/Foundation/NSStream.h
     /usr/include/Foundation/NSString.h
     /usr/include/Foundation/NSTask.h
     /usr/include/Foundation/NSThread.h
     /usr/include/Foundation/NSTimeZone.h
     /usr/include/Foundation/NSTimer.h
     /usr/include/Foundation/NSURL.h
     /usr/include/Foundation/NSURLHandle.h
     /usr/include/Foundation/NSUndoManager.h
     /usr/include/Foundation/NSUserDefaults.h
     /usr/include/Foundation/NSUtilities.h
     /usr/include/Foundation/NSValue.h
     /usr/include/Foundation/NSZone.h

=> libeina-0.9.9.063-6.fc12.src.rpm
=> libeina-devel-0.9.9.063-6.fc12.i686 in updates
  File conflict with: libftdi-devel-0.17-2.fc12.i686
     /usr/share/man/man3/deprecated.3.gz

=> libftdi-0.17-2.fc12.src.rpm
=> libftdi-devel-0.17-2.fc12.i686 in updates-testing
  File conflict with: libeina-devel-0.9.9.063-6.fc12.i686
     /usr/share/man/man3/deprecated.3.gz

=> libpfm-3.5-4.fc12.src.rpm
=> libpfm-devel-3.5-4.fc12.i686 in fedora
  File conflict with: papi-devel-4.0.0-2.fc12.i686
     /usr/include/perfmon/perfmon.h
     /usr/include/perfmon/perfmon_dfl_smpl.h
     /usr/include/perfmon/perfmon_pebs_core_smpl.h
     /usr/include/perfmon/pfmlib.h
     /usr/include/perfmon/pfmlib_gen_ia32.h
     /usr/share/man/man3/libpfm.3.gz
     /usr/share/man/man3/libpfm_core.3.gz
     /usr/share/man/man3/pfm_find_event.3.gz
     /usr/share/man/man3/pfm_get_event_name.3.gz
     /usr/share/man/man3/pfm_get_pmu_name.3.gz
     /usr/share/man/man3/pfm_strerror.3.gz

=> openwsman-2.2.0-3.fc12.src.rpm
=> libwsman1-2.2.0-3.fc12.i686 in updates
  File conflict with: openwsman-2.2.0-1.fc12.i686
     /usr/lib/libwsman.so.1.0.0
     /usr/lib/libwsman_client.so.1.0.0
     /usr/lib/libwsman_curl_client_transport.so.1.0.0

=> lldpad-0.9.29-1.fc12.src.rpm
=> lldpad-devel-0.9.29-1.fc12.i686 in updates-testing
  File conflict with: dcbd-devel-0.9.15-7.fc12.i686
     /usr/lib/pkgconfig/dcbd.pc

=> lsdvd-0.16-12.fc12.src.rpm
=> lsdvd-0.16-12.fc12.i686 in fedora
  File conflict with: streamdvd-streamanalyze-0.4-8.fc10.i386
     /usr/bin/lsdvd

=> openser-1.3.4-8.fc12.src.rpm
=> openser-db_berkeley-1.3.4-8.fc12.i686 in fedora
  File conflict with: opensips-db_berkeley-1.6.1-1.fc12.i686
     /usr/sbin/bdb_recover

=> opensips-1.6.1-1.fc12.src.rpm
=> opensips-db_berkeley-1.6.1-1.fc12.i686 in updates
  File conflict with: openser-db_berkeley-1.3.4-8.fc12.i686
     /usr/sbin/bdb_recover

=> openwsman-2.2.0-1.fc12.src.rpm
=> openwsman-2.2.0-1.fc12.i686 in fedora
  File conflict with: libwsman1-2.2.0-3.fc12.i686
     /usr/lib/libwsman.so.1.0.0
     /usr/lib/libwsman_client.so.1.0.0
     /usr/lib/libwsman_curl_client_transport.so.1.0.0
  File conflict with: openwsman-client-2.2.0-3.fc12.i686
     /usr/lib/libwsman_clientpp.so.0.0.0
  File conflict with: openwsman-server-2.2.0-3.fc12.i686
     /etc/openwsman/openwsman.conf
     /etc/openwsman/ssleay.cnf
     /usr/lib/libwsman_server.so.1.0.0
     /usr/lib/openwsman/authenticators/libwsman_file_auth.so.1.0.0
     /usr/lib/openwsman/authenticators/libwsman_pam_auth.so.1.0.0
     /usr/lib/openwsman/plugins/libwsman_cim_plugin.so.1.0.0
     /usr/lib/openwsman/plugins/libwsman_identify_plugin.so.1.0.0
     /usr/lib/openwsman/plugins/libwsman_test.so.1.0.0
     /usr/sbin/openwsmand

=> openwsman-2.2.0-3.fc12.src.rpm
=> openwsman-client-2.2.0-3.fc12.i686 in updates
  File conflict with: openwsman-2.2.0-1.fc12.i686
     /usr/lib/libwsman_clientpp.so.0.0.0

=> openwsman-2.2.0-3.fc12.src.rpm
=> openwsman-ruby-2.2.0-3.fc12.i686 in updates
  File conflict with: ruby-openwsman-2.2.0-1.fc12.i686
     /usr/lib/ruby/site_ruby/1.8/i386-linux/openwsman.so

=> openwsman-2.2.0-3.fc12.src.rpm
=> openwsman-server-2.2.0-3.fc12.i686 in updates
  File conflict with: openwsman-2.2.0-1.fc12.i686
     /etc/openwsman/openwsman.conf
     /etc/openwsman/ssleay.cnf
     /usr/lib/libwsman_server.so.1.0.0
     /usr/lib/openwsman/authenticators/libwsman_file_auth.so.1.0.0
     /usr/lib/openwsman/authenticators/libwsman_pam_auth.so.1.0.0
     /usr/lib/openwsman/plugins/libwsman_cim_plugin.so.1.0.0
     /usr/lib/openwsman/plugins/libwsman_identify_plugin.so.1.0.0
     /usr/lib/openwsman/plugins/libwsman_test.so.1.0.0
     /usr/sbin/openwsmand

=> ovirt-node-1.9.0-0.fc12.src.rpm
=> ovirt-node-1.9.0-0.fc12.i686 in updates-testing
  File conflict with: anaconda-12.46-2.fc12.i686
     /usr/sbin/gptsync
     /usr/sbin/showpart
  File conflict with: fedora-release-12-2.noarch
     /etc/issue.net
  File conflict with: generic-release-12-1.noarch
     /etc/issue.net
  File conflict with: postgresql-8.4.3-1.fc12.i686
     /usr/bin/createuser

=> papi-4.0.0-2.fc12.src.rpm
=> papi-devel-4.0.0-2.fc12.i686 in updates
  File conflict with: libpfm-devel-3.5-4.fc12.i686
     /usr/include/perfmon/perfmon.h
     /usr/include/perfmon/perfmon_dfl_smpl.h
     /usr/include/perfmon/perfmon_pebs_core_smpl.h
     /usr/include/perfmon/pfmlib.h
     /usr/include/perfmon/pfmlib_gen_ia32.h
     /usr/share/man/man3/libpfm.3.gz
     /usr/share/man/man3/libpfm_core.3.gz
     /usr/share/man/man3/pfm_find_event.3.gz
     /usr/share/man/man3/pfm_get_event_name.3.gz
     /usr/share/man/man3/pfm_get_pmu_name.3.gz
     /usr/share/man/man3/pfm_strerror.3.gz

=> pootle-2.0.1-2.fc12.src.rpm
=> pootle-2.0.1-2.fc12.noarch in updates
  File conflict with: python-djblets-0.5.6-0.fc12.noarch
     /usr/lib/python2.6/site-packages/djblets/__init__.py
     /usr/lib/python2.6/site-packages/djblets/__init__.pyc
     /usr/lib/python2.6/site-packages/djblets/__init__.pyo
     /usr/lib/python2.6/site-packages/djblets/siteconfig/__init__.pyc
     /usr/lib/python2.6/site-packages/djblets/siteconfig/__init__.pyo
     /usr/lib/python2.6/site-packages/djblets/siteconfig/admin.py
     /usr/lib/python2.6/site-packages/djblets/siteconfig/admin.pyc
     /usr/lib/python2.6/site-packages/djblets/siteconfig/admin.pyo
     /usr/lib/python2.6/site-packages/djblets/siteconfig/context_processors.py
     /usr/lib/python2.6/site-packages/djblets/siteconfig/context_processors.pyc
     /usr/lib/python2.6/site-packages/djblets/siteconfig/context_processors.pyo
     /usr/lib/python2.6/site-packages/djblets/siteconfig/django_settings.pyc
     /usr/lib/python2.6/site-packages/djblets/siteconfig/django_settings.pyo
     /usr/lib/python2.6/site-packages/djblets/siteconfig/forms.py
     /usr/lib/python2.6/site-packages/djblets/siteconfig/forms.pyc
     /usr/lib/python2.6/site-packages/djblets/siteconfig/forms.pyo
     /usr/lib/python2.6/site-packages/djblets/siteconfig/managers.py
     /usr/lib/python2.6/site-packages/djblets/siteconfig/managers.pyc
     /usr/lib/python2.6/site-packages/djblets/siteconfig/managers.pyo
     /usr/lib/python2.6/site-packages/djblets/siteconfig/middleware.py
     /usr/lib/python2.6/site-packages/djblets/siteconfig/middleware.pyc
     /usr/lib/python2.6/site-packages/djblets/siteconfig/middleware.pyo
     /usr/lib/python2.6/site-packages/djblets/siteconfig/models.py
     /usr/lib/python2.6/site-packages/djblets/siteconfig/models.pyc
     /usr/lib/python2.6/site-packages/djblets/siteconfig/models.pyo
     /usr/lib/python2.6/site-packages/djblets/siteconfig/views.py
     /usr/lib/python2.6/site-packages/djblets/siteconfig/views.pyc
     /usr/lib/python2.6/site-packages/djblets/siteconfig/views.pyo
     /usr/lib/python2.6/site-packages/djblets/util/__init__.py
     /usr/lib/python2.6/site-packages/djblets/util/__init__.pyc
     /usr/lib/python2.6/site-packages/djblets/util/__init__.pyo
     /usr/lib/python2.6/site-packages/djblets/util/context_processors.py
     /usr/lib/python2.6/site-packages/djblets/util/context_processors.pyc
     /usr/lib/python2.6/site-packages/djblets/util/context_processors.pyo
     /usr/lib/python2.6/site-packages/djblets/util/dates.py
     /usr/lib/python2.6/site-packages/djblets/util/dates.pyc
     /usr/lib/python2.6/site-packages/djblets/util/dates.pyo
     /usr/lib/python2.6/site-packages/djblets/util/db.py
     /usr/lib/python2.6/site-packages/djblets/util/db.pyc
     /usr/lib/python2.6/site-packages/djblets/util/db.pyo
     /usr/lib/python2.6/site-packages/djblets/util/dbevolution.py
     /usr/lib/python2.6/site-packages/djblets/util/dbevolution.pyc
     /usr/lib/python2.6/site-packages/djblets/util/dbevolution.pyo
     /usr/lib/python2.6/site-packages/djblets/util/decorators.pyc
     /usr/lib/python2.6/site-packages/djblets/util/decorators.pyo
     /usr/lib/python2.6/site-packages/djblets/util/fields.pyc
     /usr/lib/python2.6/site-packages/djblets/util/fields.pyo
     /usr/lib/python2.6/site-packages/djblets/util/http.py
     /usr/lib/python2.6/site-packages/djblets/util/http.pyc
     /usr/lib/python2.6/site-packages/djblets/util/http.pyo
     /usr/lib/python2.6/site-packages/djblets/util/misc.py
     /usr/lib/python2.6/site-packages/djblets/util/misc.pyc
     /usr/lib/python2.6/site-packages/djblets/util/misc.pyo
     /usr/lib/python2.6/site-packages/djblets/util/rooturl.py
     /usr/lib/python2.6/site-packages/djblets/util/rooturl.pyc
     /usr/lib/python2.6/site-packages/djblets/util/rooturl.pyo
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/__init__.pyc
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/__init__.pyo
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_deco.py
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_deco.pyc
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_deco.pyo
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_email.py
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_email.pyc
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_email.pyo
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_forms.py
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_forms.pyc
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_forms.pyo
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_images.py
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_images.pyc
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_images.pyo
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_js.py
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_js.pyc
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_js.pyo
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_utils.py
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_utils.pyc
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_utils.pyo
     /usr/lib/python2.6/site-packages/djblets/util/testing.py
     /usr/lib/python2.6/site-packages/djblets/util/testing.pyc
     /usr/lib/python2.6/site-packages/djblets/util/testing.pyo
     /usr/lib/python2.6/site-packages/djblets/util/tests.py
     /usr/lib/python2.6/site-packages/djblets/util/tests.pyc
     /usr/lib/python2.6/site-packages/djblets/util/tests.pyo

=> postgresql-8.4.3-1.fc12.src.rpm
=> postgresql-8.4.3-1.fc12.i686 in updates-testing
  File conflict with: ovirt-node-1.9.0-0.fc12.i686
     /usr/bin/createuser

=> pscan-1.3-4.fc12.src.rpm
=> pscan-1.3-4.fc12.i686 in fedora
  File conflict with: EMBOSS-6.1.0-6.fc12.i686
     /usr/bin/pscan

=> python-djblets-0.5.6-0.fc12.src.rpm
=> python-djblets-0.5.6-0.fc12.noarch in updates
  File conflict with: pootle-2.0.1-2.fc12.noarch
     /usr/lib/python2.6/site-packages/djblets/__init__.py
     /usr/lib/python2.6/site-packages/djblets/__init__.pyc
     /usr/lib/python2.6/site-packages/djblets/__init__.pyo
     /usr/lib/python2.6/site-packages/djblets/siteconfig/__init__.pyc
     /usr/lib/python2.6/site-packages/djblets/siteconfig/__init__.pyo
     /usr/lib/python2.6/site-packages/djblets/siteconfig/admin.py
     /usr/lib/python2.6/site-packages/djblets/siteconfig/admin.pyc
     /usr/lib/python2.6/site-packages/djblets/siteconfig/admin.pyo
     /usr/lib/python2.6/site-packages/djblets/siteconfig/context_processors.py
     /usr/lib/python2.6/site-packages/djblets/siteconfig/context_processors.pyc
     /usr/lib/python2.6/site-packages/djblets/siteconfig/context_processors.pyo
     /usr/lib/python2.6/site-packages/djblets/siteconfig/django_settings.pyc
     /usr/lib/python2.6/site-packages/djblets/siteconfig/django_settings.pyo
     /usr/lib/python2.6/site-packages/djblets/siteconfig/forms.py
     /usr/lib/python2.6/site-packages/djblets/siteconfig/forms.pyc
     /usr/lib/python2.6/site-packages/djblets/siteconfig/forms.pyo
     /usr/lib/python2.6/site-packages/djblets/siteconfig/managers.py
     /usr/lib/python2.6/site-packages/djblets/siteconfig/managers.pyc
     /usr/lib/python2.6/site-packages/djblets/siteconfig/managers.pyo
     /usr/lib/python2.6/site-packages/djblets/siteconfig/middleware.py
     /usr/lib/python2.6/site-packages/djblets/siteconfig/middleware.pyc
     /usr/lib/python2.6/site-packages/djblets/siteconfig/middleware.pyo
     /usr/lib/python2.6/site-packages/djblets/siteconfig/models.py
     /usr/lib/python2.6/site-packages/djblets/siteconfig/models.pyc
     /usr/lib/python2.6/site-packages/djblets/siteconfig/models.pyo
     /usr/lib/python2.6/site-packages/djblets/siteconfig/views.py
     /usr/lib/python2.6/site-packages/djblets/siteconfig/views.pyc
     /usr/lib/python2.6/site-packages/djblets/siteconfig/views.pyo
     /usr/lib/python2.6/site-packages/djblets/util/__init__.py
     /usr/lib/python2.6/site-packages/djblets/util/__init__.pyc
     /usr/lib/python2.6/site-packages/djblets/util/__init__.pyo
     /usr/lib/python2.6/site-packages/djblets/util/context_processors.py
     /usr/lib/python2.6/site-packages/djblets/util/context_processors.pyc
     /usr/lib/python2.6/site-packages/djblets/util/context_processors.pyo
     /usr/lib/python2.6/site-packages/djblets/util/dates.py
     /usr/lib/python2.6/site-packages/djblets/util/dates.pyc
     /usr/lib/python2.6/site-packages/djblets/util/dates.pyo
     /usr/lib/python2.6/site-packages/djblets/util/db.py
     /usr/lib/python2.6/site-packages/djblets/util/db.pyc
     /usr/lib/python2.6/site-packages/djblets/util/db.pyo
     /usr/lib/python2.6/site-packages/djblets/util/dbevolution.py
     /usr/lib/python2.6/site-packages/djblets/util/dbevolution.pyc
     /usr/lib/python2.6/site-packages/djblets/util/dbevolution.pyo
     /usr/lib/python2.6/site-packages/djblets/util/decorators.pyc
     /usr/lib/python2.6/site-packages/djblets/util/decorators.pyo
     /usr/lib/python2.6/site-packages/djblets/util/fields.pyc
     /usr/lib/python2.6/site-packages/djblets/util/fields.pyo
     /usr/lib/python2.6/site-packages/djblets/util/http.py
     /usr/lib/python2.6/site-packages/djblets/util/http.pyc
     /usr/lib/python2.6/site-packages/djblets/util/http.pyo
     /usr/lib/python2.6/site-packages/djblets/util/misc.py
     /usr/lib/python2.6/site-packages/djblets/util/misc.pyc
     /usr/lib/python2.6/site-packages/djblets/util/misc.pyo
     /usr/lib/python2.6/site-packages/djblets/util/rooturl.py
     /usr/lib/python2.6/site-packages/djblets/util/rooturl.pyc
     /usr/lib/python2.6/site-packages/djblets/util/rooturl.pyo
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/__init__.pyc
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/__init__.pyo
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_deco.py
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_deco.pyc
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_deco.pyo
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_email.py
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_email.pyc
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_email.pyo
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_forms.py
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_forms.pyc
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_forms.pyo
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_images.py
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_images.pyc
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_images.pyo
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_js.py
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_js.pyc
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_js.pyo
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_utils.py
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_utils.pyc
     /usr/lib/python2.6/site-packages/djblets/util/templatetags/djblets_utils.pyo
     /usr/lib/python2.6/site-packages/djblets/util/testing.py
     /usr/lib/python2.6/site-packages/djblets/util/testing.pyc
     /usr/lib/python2.6/site-packages/djblets/util/testing.pyo
     /usr/lib/python2.6/site-packages/djblets/util/tests.py
     /usr/lib/python2.6/site-packages/djblets/util/tests.pyc
     /usr/lib/python2.6/site-packages/djblets/util/tests.pyo

=> openwsman-2.2.0-1.fc12.src.rpm
=> ruby-openwsman-2.2.0-1.fc12.i686 in fedora
  File conflict with: openwsman-ruby-2.2.0-3.fc12.i686
     /usr/lib/ruby/site_ruby/1.8/i386-linux/openwsman.so

=> streamdvd-0.4-8.fc10.src.rpm
=> streamdvd-streamanalyze-0.4-8.fc10.i386 in rpmfusion-free
  File conflict with: lsdvd-0.16-12.fc12.i686
     /usr/bin/lsdvd

=> synergy-1.3.1-14.fc12.src.rpm
=> synergy-1.3.1-14.fc12.i686 in fedora
  File conflict with: synergy-plus-1.3.4-3.fc12.i686
     /usr/bin/synergyc
     /usr/bin/synergys

=> synergy-plus-1.3.4-3.fc12.src.rpm
=> synergy-plus-1.3.4-3.fc12.i686 in fedora
  File conflict with: synergy-1.3.1-14.fc12.i686
     /usr/bin/synergyc
     /usr/bin/synergys

=> wcstools-3.8.1-1.fc12.src.rpm
=> wcstools-3.8.1-1.fc12.i686 in updates
  File conflict with: EMBOSS-6.1.0-6.fc12.i686
     /usr/bin/remap

Done.

[Alexander Kahl]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thorsten Leemhuis from RPMFusion said why this is the case at the FUDCon
09 in Berlin and it will continue to be the case if nothing changes: No
collaboration and total underappreciation of RPMFusion's work. We cannot
legally endorse RPMFusion but we could very well collaborate with them
"under the hood", which doesn't happen at all - at least not to my
knowledge.

On 03/16/2010 09:50 AM, Ankur Sinha wrote:
>  I did notice that. I wasn't sure why a package from rpmfusion
> would
>  conflict with one from fedora repos. (It's in rpmfusion for a reason)
>  Is it being obsoleted by a fedora package (license been cleared or
>  something)? 
>   
- -- 
Alexander Kahl
GNU/Linux Software Developer
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkuffU0ACgkQVTRddCFHw11mVQCgv44KlLFxqfnJ6rCN33MGj4tL
> NBQAoKx790efBviXFZ4nkz6+RVJYVd0y
> =DbYv
> -----END PGP SIGNATURE-----

[Bastien Nocera]

On Tue, 2010-03-16 at 13:45 +0100, Alexander Kahl wrote:
>  -----BEGIN PGP SIGNED MESSAGE-----
>  Hash: SHA1
>  
>  Thorsten Leemhuis from RPMFusion said why this is the case at the FUDCon
>  09 in Berlin and it will continue to be the case if nothing changes: No
>  collaboration and total underappreciation of RPMFusion's work. We cannot
>  legally endorse RPMFusion but we could very well collaborate with them
>  "under the hood", which doesn't happen at all - at least not to my
>  knowledge. 
Except that that's not the case here, as Benjamin and I have been in
contact with Hans who takes care of the RPMFusion packages from the
start.

And top-posting FTL.

[Alexander Kahl]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/16/2010 03:34 PM, Bastien Nocera wrote:
>  Except that that's not the case here, as Benjamin and I have been
> in
>  contact with Hans who takes care of the RPMFusion packages from the
>  start. 
Thanks for the insight, didn't know this has changed in the meantime.

- -- 
Alexander Kahl
GNU/Linux Software Developer
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkufl6sACgkQVTRddCFHw12H2QCglNDY3SzP3NfVuKsbH8V7qtUa
> KgEAnRbZR0awwBYFeYqKYx4O+mw7+U1k
> =Pmtu
> -----END PGP SIGNATURE-----