Hi MT Julianto!

 On 2012.11.16 at 08:41:20 +0100, MT Julianto wrote next:

> Do you really need to use epel-testing repo?
> This might the source of your problem.
> For me, epel repo is enough.
> 
> 
> 
> > ---> Package qemu-img.x86_64 2:0.12.1.2-2.295.el6_3.2 will be updated
> > ---> Package qemu-img.i686 2:1.2.0-19.el6.1 will be an update
> >
> 
> Do you have i686 version installed before updating?
> What is the result of
>  yum list installed | grep qemu

No, I don't have i686 version installed, but you are exactly right:
epel-testing repo is the source of the problem. Silly me for not
noticing it before. Turning off epel-testing helped, thanks!


I had to use few packages from epel-testing in the past (I needed newer
versions which weren't making their way into regular epel for months),
and since I use only small amount of epel packages and none of others
came from testing, I just turned it on in config so I wouldn't have to
turn it on yum commandline from time to time.


Anyhow this has really surprised me. I assumed that epel won't be
publishing packages that are in base distro! I know that SL has some
extra packages compared to other EL distros, so it is possible to
encounter these packages in epel, but qemu is upstream package, so I
never expected it to be in epel.

Probably I've read epel policy on packages wrong, I should re-read it
more carefully. It always was least problematic add-on repo for me
(compared to atrpms or rpmforge).

-- 

Vladimir