Re: The i830 saga

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Jon,

I am glad I could help somehow. Comments below.

On 17 Jan 2003 14:49:12 +0100
Jon Haugsand <Jon-H.Haugsand@norges-bank.no> wrote:

> Thank you very much.  I am perhaps closer now.  When trying out only
> your packages, a lot was kissing, but this is due to all the old
> packages I have installed that has to be upgraded.
> 
> Therefore I tryied the big one once more:
> 
>  rpm -Uvh --test *.rpm
> warning: fontconfig-2.1-1.i386.rpm: V3 DSA signature: NOKEY, key ID
> 897da07a warning: package redhat-config-xfree86 = 0.7.1-3 was already
> added, replacing with redhat-config-xfree86 <= 0.7.1-5 error: Failed
> dependencies:
>         libstdc++.so.5(GLIBCPP_3.2.2) is needed by ttmkfdir-3.0.5-1
>         kernel-drm = 4.2.99.2 is needed by XFree86-4.2.99.3-20021230.4
>         libc.so.6(GLIBC_2.3.2) is needed by
>         XFree86-libs-4.2.99.3-20021230.4 libpthread.so.0(GLIBC_2.3.2)
>         is needed by XFree86-tools-4.2.99.3-20021230.4
> 
> However, I'll try to use --force or something.

Be careful since you're dealing with "sensitive" packages such as glibc.
It could be just RPM inter-dependencies database gone mad, but you don't
want to risk doing a big mess. Generally speaking, I only go for --force
if I am absolutely sure I can ignore RPM warnings (such as in this
kernel-drm case).

One hint: you're installing pre-compiled RPMs, right? It seems latest
RawHide packages were built with gcc 3.2 (which makes sense, since RH
8.0 is based on gcc 3.2; the "libstdc++.so.5(GLIBCPP_3.2.2)" above also
suggests this). Maybe you should consider upgrading gcc first. If that's
the case, I would consider using Hao Li's SRPMs (www.haoli.org/rpm),
this is how I upgraded gcc on my box. I have these installed here on my
RH 7.1:

gcc-3.2.1-1
compat-libstdc++-3.2-1
compat-glibc-6.2-2.1.3.2

Before actually doing this, try the upgrade with "--test" first, because
gcc comes with many critical libs that could break apps compiled with
gcc 2.x (basically, your whole system ;) ) The "compat-*" RPMs above
should handle this, though. Anyway, being extra careful wouldn't hurt.

> Yes, that is a little bit irritating with rpm.

Yeah, it is its biggest drawback IMHO =/

> Anyway, thank you very much.  I'll try this out.

Good luck, hope you are successful. It is indeed possible to manually
update old RH systems as I did with my RH 7.1 (which is nowadays closer
to 8.x than anything else), but I can't remember all the steps I had to
take -- I know it's been a *long* way... Maybe you should consider, if
at all possible, to do a full upgrade to RH 8.0.

Best,

Andre

-- 
Andre Oliveira da Costa



_______________________________________________
xfree86-list mailing list
xfree86-list@redhat.com
https://listman.redhat.com/mailman/listinfo/xfree86-list
IRC: #xfree86 on irc.redhat.com

[Red Hat General]     [Red Hat Watch]     [Red Hat Development]     [Kernel Development]     [Yosemite Camping]

  Powered by Linux