[rhn-users] up2date does not work
Alfred Hovdestad
alfred.hovdestad at usask.ca
Wed Mar 23 19:27:32 UTC 2005
I had the same problem. I manually downloaded the rpm* packages
(up2date -d rpm-libs which also downloaded rpm, rpm-build, rpm-devel and
rpm-python). I then upgraded these packages manually (rpm -Uvh
rpm*.rpm) and I still had problems when I tried to do an up2date:
# rpm --rebuilddb
rpmdb: Program version 4.2 doesn't match environment version
I ended up removing the -__db* files in /var/lib/rpm
# cd /var/lib/rpm
# rm __db*
After that, I was able to do a regular up2date:
# up2date -u --nox
You might want to try removing the /var/lib/rpm/__db* files first to see
if that works. You might also want to try to update the package list
after you install the rpm rpm's (up2date -p).
Alfred Hovdestad
University of Saskatchewan
Greiner Thomas wrote:
> Here’s my problem. I run up2date and find the following items that need
> updating:
>
>
>
> rpm v. 4.2.3-13
>
> rpm-build
>
> rpm-devel
>
> rpm-python
>
>
>
> When I select these items for installation up2date indicates that there
> is an:
>
> “unresolvable chain of dependencies:
>
> rpm-libs 4.2.3-13 requires libelf.so.1
>
> rpm-libs 4.2.3-13 requires libeld.so.1”
>
>
>
> So I download libelf.so.1 as part of elfutils-lifelf-0.76-3.i386.rpm.
>
>
>
> I try to install that and am told that:
>
> “package elfutils-libelf-0.94-1 (which is newer than
> elfutils-libelf-0.76-3) is already installed.”
>
>
>
> So, it would seem that I have the most up-to-date version of libelf,
> cannot overinstall a different version, and cannot result the updates
> indicated from up2date.
>
>
>
> What do I do now? Do I permanently ignore the updates indicated in
> up2date? If so, what’s the point in the program?
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> rhn-users mailing list
> rhn-users at redhat.com
> https://www.redhat.com/mailman/listinfo/rhn-users
More information about the rhn-users
mailing list