On 03 Feb 2001 19:30:26 +0000, Richard -Gilligan- Uschold wrote:My current version is: rpm-3.03-43mdk.i586.rpm
> [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.
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 /| _ \<,_ ( ) /p|\ (_)/ (_) \ ( Oooo. / | \ ------------ \_) ( ) ======== ) / ======== [EMAIL PROTECTED] (_/ ~~~~~~~~~~~~~~~~ [EMAIL PROTECTED]
