At 09:32 PM 1/21/01, you wrote:
>On Sun, Jan 21, 2001 at 11:59:12AM -0500, David Relson wrote:
> > At 11:58 PM 1/20/01, Geoffrey Lee wrote:
> > >On Sun, Jan 21, 2001 at 04:29:01AM +0100, Dacobi Coding wrote:
> > > > I'm trying to get rpmdrake to work, but keep geting this error:
> > > >
> > > > rpmdrake: error while loading shared libraries: /usr/lib/librpm.so.0:
> > > > undefined symbol: fdio
> > > >
> > > > I have the following rpm's installed:
> > >
> > >Known problem if you had not installed rpm4 then nothing would have gone
> > >wrong ..
> >
> > Geoffrey,
> >
> > It's easy enough to say this, but...
> >
> > I updated to rpm4 because there were packages I wanted to install that
> > wouldn't install with earlier versions of rpm.  Some parts of command line
> > rpm work and, as far as I can recall, some parts don't.  MandrakeUpdate
> > definitely does not work.
> >
>
>rpm3.0.5 and 3.0.6 provided forward compat.
>
> > It would be a help to those of us who have upgraded to rpm4 if the
> > knowledgeable people at Mandrake could release a set of updated rpms that
> > would correct the fdio problem (and related problems, if there are any).
> >
>
>This is cooker, expect some things to break ..

Geoff,

I do expect things to break, but this one was not expected and a fix would 
be appreciated.

Earlier today, Richard Gilligan reported the same problem under the heading 
"RPM upgrade problems".  He was running rpm-3.0.5-27mdk and got the message 
"only packages with major numbers <=3 are supported by this version of RPM" 
while trying to install "glibc-2.2.1-3mdk.rpm".

If I understand his report correctly, glibc-2.2.1-3mdk.rpm has an rpm major 
version of 4 and, contrary to your statement of forward compatibility, 
rpm-3.0.5 couldn't handle it.  Please correct me if my understanding is 
incorrect.

David

--------------------------------------------------------
David Relson                   Osage Software Systems, Inc.
[EMAIL PROTECTED]       Ann Arbor, MI 48103
www.osagesoftware.com          tel:  734.821.8800


Reply via email to