On 8/29/07, Todd Zullinger <tmz(a)pobox.com> wrote:
Andras Simon wrote:
> While trying to yum update this morning, I got
>
> Transaction Check Error:
> file /usr/include/popt.h from install of popt-1.10.2.1-1.fc7
> conflicts with file from package popt-1.10.2-46.fc7
I'm not sure why that'd cause an error. FWIW, I updated popt to
1.10.2.1-1.fc7 on 8/14 without error, so I don't think it's a generic
packaging bug.
On 8/14??? I'm running yum update at least twice a day, and popt
hasn't showed up until today!
> Apparently, yum is trying to update popt-1.10.2-46.fc7 with
> popt-1.10.2.1-1.fc7, which looks strange to me.
1.10.2.1 is newer than 1.10.2, so the versioning is sane.
The one that's installed is popt-1.10.2-46.fc7, the one to be
installed is popt-1.10.2-1.fc7, and judging from release numbers, the
latter looks older. Or it's too early in the morning here :-(
Does running yum update with the debugging[1] turned up help?
It doesn't help _me_, but at least it gives a different error message:
Member: popt.x86_64 0-1.10.2-46.fc7 - None
Member: popt.x86_64 0-1.10.2.1-1.fc7 - u
Adding Package popt - 1.10.2.1-1.fc7.x86_64 in mode u
---> Package popt.x86_64 0:1.10.2.1-1.fc7 set to be updated
ERROR with rpm_check_debug vs depsolve:
Package rpm-libs needs rpm = 4.4.2-46.fc7, this is not available.
Package rpm-devel needs rpm = 4.4.2-46.fc7, this is not available.
Complete!
Actually, now I get this same error without debugging turned on.
But wait! I got this last error message while doing
yum update popt
But now, prompted by this new error I tried
yum update popt rpm*
and it worked! But perhaps it was a syncing problem, as Stuart
Murray-Smith said, and it wasn't the different arguments but the
elapsed 10 seconds that helped.
Andras