If you have rpm-3.0.3x I don't believe you'll be able to directly
upgrade to rpm-4.x via rpm itself. To simplify the thread on this, you
can get to 3.0.5-27 via pre-built rpm's. Tho Gilligan seems to have a
system-specific issue with his Kpackage, it shouldn't make any
difference whether you're at a term prompt or using an X gui for the
job. Considering the number of threads on this subject lately, I'm
surprised noone's come up with some sort of faq on the subject. When it
comes to rpm itself, I started my upgrade with an abundance of caution -
went to the rpm ftp site & incrementally upgraded (via RH rpm's) until I
hit 3.0.5-27. rpm --rebuilddb after each. Don't know which ones you can
skip - I wanted to make sure that no dependency was overlooked. Only had
to upgrade menu & install libbzip2 - stay away from upgrading bzip2
itself. That's a dependency headache. I've yet to see anyone come forth
with a compelling reason to upgrade to 4.0x itself. You'll leave your
odd messages behind with 3.0.5-27. But my point of origin was 7.1's
3.0.4x, not 3x. You may have other libs to address.
On 12 Feb 2001 15:30:19 -1000, Dan Jones wrote:
> Actually, I have the same problem, and running from the command line
> does *not* solve it...
>
> Richard -Gilligan- Uschold wrote:
> >
> > Piero Caracciolo wrote:
> >
> > > The problem I'm submitting to the competent and kind mandrake
> > > community
> > > seems to have been fairly common fìof late.
> > > May be somedy who solved it can help me.
> > >
> > > I have Mandrake 7.0 and Rpm 3.03-43mdk.
> > > A few days ago I attempted to install a new package using Rpm -i,
> > > and got
> > > the answer:
> > >
> > > "Only packages witn major numbers <=3 are supported by this
> > > version of Rpm".
> > >
> > > I then tried to install a more recent version of Rpm (version 4.02)
> > > and
> > > which has been my surprise when I got the same answer.
> > >
> > > How did you solve this problem? Richard -Gilligan- Uschold seems to
> > > have
> > > found a solution, but may-be He could give me a more detailed
> > > explanation.
> > > Did he upgrade first from 3.03 to 3.04, then 3.05, and so on, until
> > > version
> > > 4? And what he mens whe he says he rebuilded the database at every
> > > step?
> > >
> > > Is'nt there a quicker and more human way to do it?
> > >
> > > Thank you very much, anyway.
> > >
> > > By the way, do you know what a major number is in the Rpm context?
> >
> > Near as I can tell, the above a problem and the one below, are caused
> > by kpackage, and are not caused by rpm. These errors do not exist
> > when running rpm from the command line.
> >
> > dependency errors;
> > rpmlib(PayloadFilesHavePrefix) <= 4.0-1rint11
> > rpmlib(CompressedFileNames) <= 3.0.4-1
> >
> > I have kpackage-1.3.10-1mdk, the latest available for KDE 1.1.x I get
> > these same errors with all versions of rpm between 3.0.3-43mdk and
> > 3.0.5-17mdk. I tried it as I upgraded one at a time. I've only tried
> > rpm-3.0.5-27mdk from the command line, though, I suspect the other
> > versions won't show the problem either.
> >
> > Perhaps other GUI package managers don't have this problem. I tried
> > several others, but they failed for other reasons, and I haven't
> > bothered looking into that.
> >
> > While I didn't actually solve the problem, I have isolated it and I
> > have a solid workaround.
> >
> > I know, runing rpm from the command line is a bit harder, but it
> > works!
> >
> > --
> >
> > Gilligan | __o .oooO
> > /| _ \<,_ ( )
> > /p|\ (_)/ (_) \ ( Oooo.
> > / | \ ------------ \_) ( )
> > ======== ) /
> > ======== [EMAIL PROTECTED] (_/
> > ~~~~~~~~~~~~~~~~ [EMAIL PROTECTED]
> >
