After upgrading to the latest in the severn-updates channel, I had one dependency unfilled -- libcom_err.so.3. This was required by my totem package so I removed that until the update was complete. Now, prior to the update that was provided by the kerberos packages but now it doesn't seem to be provided anymore. I'm assuming that it has been moved to another package that wasn't in my upgrade path, so I wonder if anyone can provide any insight on that.
Thanks,
- Scott
I got around it by rebuilding the source RPMS of totem. I don't know what caused it, but this is what Matthias suggested.
Cheers,
Phil
Scott Bell (sebell@shaw.ca) said:
After upgrading to the latest in the severn-updates channel, I had one dependency unfilled -- libcom_err.so.3. This was required by my totem package so I removed that until the update was complete. Now, prior to the update that was provided by the kerberos packages but now it doesn't seem to be provided anymore. I'm assuming that it has been moved to another package that wasn't in my upgrade path, so I wonder if anyone can provide any insight on that.
e2fsprogs and krb5 used to provide separate slightly different versions of libcom_err. With krb5-1.3, the need for a separate one was removed, so it just uses the one from e2fsprogs. Hence, you'll need to rebuild totem so it picks up that one as a dependency.
Bill
Thanks a lot, that makes perfect sense. Rebuild was successful.
- Scott
On Thu, 2003-08-28 at 09:44, Bill Nottingham wrote:
Scott Bell (sebell@shaw.ca) said:
After upgrading to the latest in the severn-updates channel, I had one dependency unfilled -- libcom_err.so.3. This was required by my totem package so I removed that until the update was complete. Now, prior to the update that was provided by the kerberos packages but now it doesn't seem to be provided anymore. I'm assuming that it has been moved to another package that wasn't in my upgrade path, so I wonder if anyone can provide any insight on that.
e2fsprogs and krb5 used to provide separate slightly different versions of libcom_err. With krb5-1.3, the need for a separate one was removed, so it just uses the one from e2fsprogs. Hence, you'll need to rebuild totem so it picks up that one as a dependency.
Bill
-- Rhl-beta-list mailing list Rhl-beta-list@redhat.com http://www.redhat.com/mailman/listinfo/rhl-beta-list