Problems with update -- redhat-lsb conflicts

[Michael Schwendt]

On Mon, 18 Jun 2012 19:48:37 -0400, Jayson Rowe wrote:

> On Fri, Jun 15, 2012 at 4:15 PM, Jonathan Ryshpan wrote:
> > Yum upgrade reports that redhat-lsb needs to be updated, but can't
> > because of a an error, to wit:
> >> Protected multilib versions: redhat-lsb-4.1-4.fc17.x86_64 != redhat-lsb-4.0-11.fc17.i686
> > What's going on?  Can I fix it, or must I wait on the repo managers?  If
> > the repo managers, when will a fix be available?
> 
> I'm still seeing this - should I remove/re-install Chrome as someone
> suggested, or just wait it out?

Well, do whatever works for you. ;) "yum remove redhat-lsb.i686" should
give a hint what would happen. If any package actually *strictly* (!) requires
redhat-lsb.i686 (with exactly that arch) you still won't be able to update
afterwards. Fixing the redhat-lsb breakage has been put onto the shoulders
of the redhat-lsb packager(s) as one can read in the Fedora releng ticket #5220
(as they think the update is not really suitable for a stable release).

-- 
Fedora release 17 (Beefy Miracle) - Linux 3.4.2-4.fc17.x86_64
loadavg: 0.43 0.61 0.58