Red Hat Bugzilla – Bug 132762
rhn, up2date discrepancy
Last modified: 2007-11-30 17:07:04 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)
Gecko/20040820 Galeon/1.3.17 (Debian package 1.3.17-1)
Description of problem:
Through the rhn.redhat.com web interface, crash shows up as a package
that needs to be updated (3.7-5 -> 3.8-3). But running 'up2date -u' on
the system shows nothing to be upgraded. If you try to run 'up2date
crash' it claims the package is up to date.
Something is confused...
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install RHEL 3.0 update 3
2. see rhn.redhat.com say there is a new crash package
3. try to update the crash package
My disk3 of RHEL3-U3 has crash-3.8-3 on it. What does "rpm -q crash
I apologize, I installed update 2, and now am trying to get the
latest packages. rpm -q crash shows 3.7-5.
I'm the author and maintainer of the crash utility, but have
absolutely nothing to do with installation issues. All I can
tell you is that 3.7-5 came out with the initial version of
RHEL3, but it did not support x86_64. In RHEL3-U3, crash 3.8-3
introduced x86_64 support. So there shouldn't have even been
an x86_64 crash utility with any RHEL3 x86_64 kernel before U3.
Ok, I guess the problem is that I have the i386 version installed and
so up2date wants to upgrade it, but since the architectures are
different it can't...
I bet if I remove the package and then reinstall it, it will be fine.
Yep. Removing the installed crash, and then running up2date crash
seems to have worked. I think up2date needs better bi-arch support...
(Maybe this should be a bug for up2date).
Right -- there's nothing I can do (at least that I know about...)
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.