On 04 Feb 2001 05:04:47 +0000, Richard -Gilligan- Uschold wrote:
> Bill Piety wrote:
>
> > On 04 Feb 2001 01:18:55 +0000, Richard -Gilligan- Uschold wrote:
> > > Bill Piety wrote:
> > >
> > > > On 03 Feb 2001 19:30:26 +0000, Richard -Gilligan- Uschold wrote:
> > > > > [EMAIL PROTECTED] wrote:
> > > > >
> > > > > > On 03-Feb-2001 Richard -Gilligan- Uschold wrote:
> > > > > > > Questions:
> > > > > > >
> > > > > > > 1. Is there a rpm package distributor that identifies which version of
> > > > > > > rpm was used to build the packages? Who?
> > > > > >
> > > > > > Doesn't matter, the rpm package itself is binary compatible between
>version 3
> > > > > > and 4. (See the list archieves on cooker)
> > > > >
> > > > > If that is the case, please explain the following error message to me, and
>how I
> > > > > correct it. Several other people have said I need to upgrade to rpm-4.0, or
> > > > > perhaps only 3.0.5 or 3.0.6. I get this error with both 3.0.3 and 3.0.5.
> > > > >
> > > > > The original symptoms:
> > > > > rpm gives this error message with some packages
> > > > > "only packages with major numbers <=3 are supported by this version of RPM"
> > > > >
> > > > > NOTE: this is not the usual dependency problem, the RPM program itself,
> > > > > fails to open "Guppi-0.35.2-1.i586.rpm", even for query!
> > > > <snip>
> > > >
> > > > 3.0.3 - forget. I solved my rpm problems by going to the rpm ftp site,
> > > > finding my version (which was at 3.0.4 at the time) and incrementally
> > > > upgrading until I reached 3.0.5-27. If you decide to try this, don't
> > > > worry about using the intermediate RH rpm's along the way. I did a
> > > > manual rebuilddb with each. There may be 2 dependency issues along the
> > > > way - don't disregard them. 1 will be a menu upgrade, the 2nd bzip2.
> > > > It's not necessary to address upgrading bzip itself - that's a
> > > > dependency nightmare. There's a libbzip that'll solve your problem. Not
> > > > a single pkg number warning since. I also haven't seen a convincing
> > > > argument to go all the way to 4.0.x either.
> > > >
> > > > This route may be tedious but it's safe - rpm's not a proggy to
> > > > mishandle.
> > >
> > > My current version is: rpm-3.03-43mdk.i586.rpm
> > >
> > > On ftp.rpm.org/pub/rpm/dist/rpm-3.0.x/ among others, there are:
> > > rpm-3.0.3-4x.i386.rpm
> > > rpm-3.0.3-5x.i386.rpm
> > > rpm-3.0.3-6x.i386.rpm
> > > rpm-3.0.4-4x.i386.rpm
> > > rpm-3.0.4-5x.i386.rpm
> > > rpm-3.0.4-6x.i386.rpm
> > > rpm-3.0.5-7.5x.i386.rpm
> > > rpm-3.0.5-7.6x.i386.rpm
> > >
> > > In late November, I upgraded from 3.0.3-43mdk to 3.0.5-27mdk. There were no
> > > dependency issues then. Yesterday, I downgraded back to 3.0.3-43mdk (which came
>with
> > > Mandrake 7.0), as a test to see what would happen. Are you saying I should
>upgrade
> > > to each of the following in sequence?
> > >
> > > rpm-3.0.3-43mdk.i586.rpm current version
> > > rpm-3.0.3-5x.i386.rpm
> > > rpm-3.0.3-6x.i386.rpm
> > > rpm-3.0.4-4x.i386.rpm
> > > rpm-3.0.4-5x.i386.rpm
> > > rpm-3.0.4-6x.i386.rpm
> > > rpm-3.0.5-27mdk.i586.rpm
> > >
> > > If there are no dependencies going directly from rpm-3.0.3-5x.i386.rpm to
> > > rpm-3.0.5-27mdk.i586.rpm, why go through all of the steps? What does it by you?
> If
> > > there is an intermediate dependency that eventually goes away, who cares?
> > >
> > > --
> > >
> > > Gilligan | __o .oooO
> > I started from Mandrake 7.1, 3.0.4-4x, so had 2 intermediate steps.
> >
> > Tho I found many threads with problems, no clear-cut solutions were
> > offered. I opted for
> > caution because of the nature of the prog. Besides, rpm's not that large
> > a download. And
> > I don't know that the 'intermediate' dependencies would have gone away
> > on my system.
> > In this instance, rather 1 or 2 'unnecessary' steps that take only a few
> > minutes than 1 misstep
> > that'll take a lot longer to correct.
>
> I did most of this from kpackage, except the --rebuilddb, and where noted.
> Here's what I did:
>
> ignore: rpm-3.0.3-5x.i386.rpm kpackage doesn't display, older than 3.0.3-43mdk
> ignore: rpm-3.0.3-6x.i386.rpm kpackage doesn't display, older than 3.0.3-43mdk
> uninstall: rpm-devel-3.0.3-43mdk.i586.rpm
> no dependencies, so update: rpm-3.0.4-4x.i386.rpm
> rpm --rebuilddb
> no dependencies, so update: rpm-3.0.4-5x.i386.rpm
> rpm --rebuilddb
> rpm-3.0.4-6x.i386.rpm requires libbz2.so.0 in bzip2-0.9.5d-2.i386.rpm this is
>older
> than my current: bzip2-1.0.1-6mdk and there are several packages that require
>this,
> also, there are several conflicting files between the two versions, although,
> bzip2-1.0.1-6mdk does not have libbz2.so.0, so from the command line:
> rpm -i --force bzip2-0.9.5d-2.i386.rpm
> rpm -i --force bzip2-1.0.1-6mdk.i586.rpm
> rpm --rebuilddb
> no dependencies, so update: rpm-3.0.4-6x.i386.rpm
> rpm --rebuilddb
> no dependencies, so update: rpm-3.0.5-27mdk.i586.rpm
> rpm --rebuilddb
> no dependencies, so update: rpm-devel-3.0.5-27mdk.i586.rpm
>
> So, now I'm back to where I was two months ago, except I have a few old bzip2-0.9.5d
> libraries that are not overwritten by bzip2-1.0.1-6mdk
>
> After each upgrade step of rpm, I tried to view Guppi-0.35.2-1.i586.rpm in kpackage
>and I
> got the exact same error every time, up through and including the final 3.0.5-27mdk.
> Error:
> "only packages with major numbers <=3 are supported by this version of RPM"
>
> So, this did no good.
>
> On the other hand, from the command line:
> rpm -U --test Guppi-0.35.2-1.i586.rpm
> Does give a bunch of failed dependencies! kpackage never got that far. kpackage
>never
> listed any dependencies and never listed any of the files included in the package.
> Perhaps this is a kpackage problem?
>
>
> --
>
> Gilligan | __o .oooO
>
I don't use kpackage, so I can't answer that. I did all of my rpm
upgrades from a term window. However, I did not upgrade bzip2 (which I
advised against) - there were too many dependency issues involved. I did
install libbzip2_1-1.0.1-7mdk which fulfilled the dependency issue with
rpm. I also have a rule - if I have to force a pkg I have to be prepared
for the worst, sooner or later. From everything I've seen on the
newsgroups rpm 3.0.5-27 is the version that you need. If you're still
getting error msgs then there's a collateral problem.
libbzip2_1 provides libbz2.so.1 and libbz2.so.1.0.1
Get further input on your bzip2 upgrade. If it were my system I'd
probably try restore my original bzip2.
