<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
David Dyer-Bennet wrote:
<blockquote TYPE=CITE>Nathan Davis <davisn@mailandnews.com> writes:
<p>> David Dyer-Bennet wrote:
<br>>
<br>> > "Matthew S. Hallacy" <poptix@techmonkeys.org> writes:
<br>> >
<br>> > > On Tue, Aug 06, 2002 at 01:19:24PM -0500, David Dyer-Bennet wrote:
<br>> > >
<br>> > > > I'm upgrading to glibc 2.2.4-27 (including the usual -common
and
<br>> > > > -devel; I don't use -profile). In fact I have it running
now. rpm
<br>> > > > --verify reports all three are installed fine.
<br>> > > >
<br>> > > > However, if I try to reinstall glibc using "rpm -U --replacepkgs
<br>> > > > glibc-2.2.4-27.i386.rpm" I get "% post scriptlet failed", and
if I try
<br>> > > > -common I get "% pre scriptlet failed". When the first,
at least,
<br>> > > > happens, *everything* stops working (well, presumably every
program
<br>> > > > that depends on the glibc dynamic library; in fact a couple
of
<br>> > > > staticly linked programs I found do still run).
<br>> > > >
<br>> > >
<br>> > > [snip]
<br>> > >
<br>> > > > I'm running now, but I believe my next upgrade will fail in
the same
<br>> > > > way, so I'd really like to figure out WTF is going on and fix
it.
<br>> > > > Anybody got a spare clue?
<br>> > >
<br>> > > Yes, I suspect you're using --nodeps and/or --force somewhere,
that's
<br>> > > a bad idea, instead you should use apt, or up2date to upgrade
all of
<br>> > > the packages that depend on $XYZ version of glibc at the same
time.
<br>> >
<br>> > I didn't override any dependencies in the basic install.
I certainly
<br>> > have tried that when playing around trying to *recover* from the
basic
<br>> > install, but the problem appeared without that.
<br>> >
<br>> > Given that *every* dynamic process died in the bad cases, I don't
<br>> > think it's a dependency of a particular program on a particular
glibc
<br>> > version. And the same dynamic binaries work when I copy over
the
<br>> > binaries from my alternate root.
<br>> >
<br>>
<br>> Well, what version are you upgrading from? If it's a different
so number, then
<br>> binaries linked against the old version won't work with the new.
Given that
<br>> the installation was built against the old version, it is very likely
that the
<br>> cause of your problem is a version mismatch. You can try installing
the new
<br>> version, instead of upgrading it.
<p>Old version was 2.2.4-19, if I remember correctly. Might have
been
<br>-14; anyway 2.2.4 still.
<br> </blockquote>
<p><br>Okay then, it looks like my hunch about different versions was wrong.
<br>
<blockquote TYPE=CITE>
<br>Is it actually possible to remove glibc and then install a new
<br>version? If so how? I thought the upgrade path was the
only possible
<br>route, since pretty much everything, including the tools rpm calls,
<br>stop working when there's no glibc.
<br>--</blockquote>
<p><br>I've only tried to upgrade glibc once, and I ran into problems because
I used rpm -U. This caused the machine to essentially no longer boot
(because the new library had a different so-name, so there were dynamic
linker errors). After fixing it via rescue disk, I believe I successfully
"upgraded" by doing rpm -i. At least I remember this working for
something (note: may have had to use --force, I don't remember).
Basically, two versions of the package were installed -- satisfying the
requirements for both old and new packages. FYI, the -U (--upgrade)
option is really just a -e and -i, but done atomically from a dependency
point of view.
<br>
<blockquote TYPE=CITE>
<br>David Dyer-Bennet, dd-b@dd-b.net / New TMDA anti-spam in
test
<br> John Dyer-Bennet 1915-2002 Memorial Site <a href="http://john.dyer-bennet.net">http://john.dyer-bennet.net</a>
<br> Book log: <a href="http://www.dd-b.net/dd-b/Ouroboros/booknotes/">http://www.dd-b.net/dd-b/Ouroboros/booknotes/</a>
<br> New Dragaera mailing
lists, see <a href="http://dragaera.info">http://dragaera.info</a>
<br><a href="https://mailman.mn-linux.org/mailman/listinfo/tclug-list"></a> </blockquote>
</html>