dependency hell, version 2,197,386.1

[A.Fadyushin at it-centre.ru]

The new iptables may be incompatible with the kernels which are older
than the kernel required by iptables package. Therefore, if the iptables
package requires the kernel version which is newer than the version of
your custom kernel, you should download the kernel (most probably, in
source form) which is required by the iptables. Then you should
customize and rebuild it similar to your older kernel and install as a
new kernel.
If the required kernel and the kernel customized by you have the same
version (the only difference is your customization) than you can use rpm
options which prevent dependency checking when installing iptables.

Alexey Fadyushin
Brainbench MVP for Linux
http://www.brainbench.com

> -----Original Message-----
> From: fedora-legacy-list-bounces at redhat.com
[mailto:fedora-legacy-list-
> bounces at redhat.com] On Behalf Of Stuart Low
> Sent: Wednesday, October 26, 2005 9:57 AM
> To: Discussion of the Fedora Legacy Project
> Subject: Re: dependency hell, version 2,197,386.1
> 
> Hey,
> 
> > How can I go about convincing yum to update the iptables install on
my
> > old firewall box when it reports this:
> > [root at gene etc]# yum update iptables
> > package iptables needs kernel that has been excluded
> > package iptables needs kernel that has been excluded
> > The kernel is in fact a 2.4.29, obviously new enough but locally
built.
> > Is this a case where the --nodeps --force options to rpm can be
used?
> 
> Probably not the smartest move. Be best to manually download the
latest
> kernel rpm and rpm -ivh it. Then modify your lilo/grub config back to
> booting your custom kernel by default.
> 
> That way you've avoided the dep issue but haven't lost your custom
> kernel.
> 
> Stuart
> 
> --
> fedora-legacy-list mailing list
> fedora-legacy-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-legacy-list