Description of problem: Since I try to installed standard java packagae j2sdk- 1.4.2. And for some compatibility issue with linux kernels before 2.4.20, I attempted to upgrade my current kernel-2.4.18-14 to the lastest update kernel- 2.4.20-18.8.i686 but it fails due to dependency problems, even with --force option. However, it's fine with kernel-2.4.18-27. Would you plz tell me why? I found out that kernel-2.4.20 is also of Redhat 9, does it have anything to do with it? Would it be ok to install redhat 9 kernel on top of redhat 8's ? Version-Release number of selected component (if applicable): How reproducible: I basically get the same error of failed dependency everytime I tried installing it. Also, the md5 check isn't good regardless of where I get the kernel-2.4.20-18.8.i686.rpm file. In fact, I got couple of copies from mirror of uw-madison and of redhat too. Steps to Reproduce: 1. rpm -K kernel-2.4.20-18.8.i686.rpm -> NO KEY 2. rpm -ivh --force kernel-2.4.20-18.8.i686.rpm -> Failed Dependency 3. Actual results: Expected results: Additional info:
Please provide the exact messages printed
Sorry I didn't write down the error messages before, but it has to do with the dependency of oprofile and kernel files, and I managed to successfully update to kernel-2.4.20-8 by removing oprofile. However, I got another problem: without oprofile file, I don't seem to use mknode or anything involving sys files. So, I try to install oprofile-0.4- 44.i386.rpm, but it shows me the following messages ( I have no clue now ): warning: oprofile-0.4-44.i386.rpm: V3 DSA signature: NOKEY, key ID db42a60e Preparing ##########################################[100%] cannot handle file "libc.so.6" with TLS data Would you plz tell me what's wrong with it, and how to fix it? Appreciate it!
Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/