[Spacewalk-list] Force install, still looking for any answers
John Hodrien
J.H.Hodrien at leeds.ac.uk
Wed Apr 8 12:49:44 UTC 2009
On Wed, 8 Apr 2009, mark wrote:
> John Hodrien wrote:
>> This is part of the 'ick' I found once redhat went multiarch. Two
>> packages:
>>
>> nss_ldap-253-13.el5_2.1.i386
>> nss_ldap-253-13.el5_2.1.x86_64
>>
>> What I assume is happening is an upgrade to nss_ldap-253-17.el5.x86_64
>> (say).
>>
>> What needs to happen is a simultaneous upgrade of i386 and x86_64 packages,
>> just to get yum to swallow it (allowing clashing files between like named
>> packages is a dirty solution if you ask me).
>
> Hmmm.... I'll have to read that more closely when I get into work. I
> shouldn't think, though, if I'm trying to upgrade a 64-bit system, it would
> need the same package for i386.
Just look at your system before thinking that.
>> What happens if you do a yum upgrade on the client?
>
> I suppose I could try that for debugging, but I can *not* do that once we
> put this into production. It *must* go from the server; otherwise, there's
> no point to spacewalk.
Hey, issue it as a remote command if that makes you feel better.
--
"If you sometimes feel depressed or let down, if you're suffering from the
pressures of life, or simply having a plain old grey day, my advice is to
roast a chicken." -- Delia Smith
More information about the Spacewalk-list
mailing list