On 04 Feb 2001 05:04:47 +0000, Richard -Gilligan- Uschold wrote:...
> Bill Piety wrote:
>
>I forgot your note about bzip2 when I upgraded, but I have since restored the original bzip2 package I had.
> 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.
The dependancy errors I was getting are also caused by kpackage, and are not issued when I use rpm from the command line.
dependancy errors;
rpmlib(PayloadFilesHavePrefix) <= 4.0-1rint11
rpmlib(CompressedFileNames) <= 3.0.4-1
I was going to upgrade my kpackage, but I have the latest version available for KDE 1.1.x. While I didn't actually solve the problem, I have isolated it and I have a solid workaround.
Thanks for your assistance.
-- Gilligan | __o .oooO /| _ \<,_ ( ) /p|\ (_)/ (_) \ ( Oooo. / | \ ------------ \_) ( ) ======== ) / ======== [EMAIL PROTECTED] (_/ ~~~~~~~~~~~~~~~~ [EMAIL PROTECTED]
