Re: [expert] rpm-3.0 to rpm-4.0 catch 22
On 04 Feb 2001 05:04:47 +, Richard -Gilligan- Uschold wrote: Bill Piety wrote: On 04 Feb 2001 01:18:55 +, Richard -Gilligan- Uschold wrote: Bill Piety wrote: On 03 Feb 2001 19:30:26 +, 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.rpmkpackage doesn't display, older than 3.0.3-43mdk ignore: rpm-3.0.3-6x.i386.rpmkpackage 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
Re: [expert] rpm-3.0 to rpm-4.0 catch 22
Bill Piety wrote: On 04 Feb 2001 05:04:47 +, Richard -Gilligan- Uschold wrote: > Bill Piety wrote: > ... > > 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. I forgot your note about bzip2 when I upgraded, but I have since restored the original bzip2 package I had. 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]
Re: [expert] rpm-3.0 to rpm-4.0 catch 22
On 04 Feb 2001 21:46:32 +, Richard -Gilligan- Uschold wrote: Bill Piety wrote: On 04 Feb 2001 05:04:47 +, Richard -Gilligan- Uschold wrote: Bill Piety wrote: ... 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.rpmkpackage doesn't display, older than 3.0.3-43mdk ignore: rpm-3.0.3-6x.i386.rpmkpackage 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. I forgot your note about bzip2 when I upgraded, but I have since restored the original bzip2 package I had. 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 Sure hope all is OK with rpm - that's a b___ of a pkg to have a problem with. Tho I'm sure you did, don't forget the rebuilddb. (Aside: I, too, love to sail)
[expert] rpm-3.0 to rpm-4.0 catch 22
I've been having problems installing rpm packages for several months, finally, someone recognized the symptoms and told me the problem. Now I need to know how to fix it. 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! I've been told that this is because rpm-4.0 generated package files that are incompatible with, and can't be read by rpm-3.0 Some other packages won't install because of these dependencies: rpmlib(PayloadFilesHavePrefix) = 4.0-1 rpmlib(CompressedFileNames) = 3.0.4-1 First of all, searches for: "rpmlib", "PayloadFilesHavePrefix", "CompressedFileNames", on rpmfind.net and www.linux-mandrake.com found nothing. I did a search for string "PayloadFilesHavePrefix" and "CompressedFileNames" on my machine from /usr, both were found in: /usr/bin/rmp2cpio /usr/lib/librpm.so.0 /usr/lib/librpm.so.0.0.0 /usr/lib/librpm.a /usr/lib/librpm.so So, I suspect that this dependency error message is WRONG, and "rpmlib" should really be "librpm". At the time, I had rpm-3.0.5-27mdk.i586.rpm, so I down graded to rpm-3.0.3-43mdk.i586.rpm (from my Mandrake 7.0 install CDROM) With this older than 3.0.4-1 version o rpm. I still get these same dependencies messages: rpmlib(PayloadFilesHavePrefix) = 4.0-1 rpmlib(CompressedFileNames) = 3.0.4-1 So, I also suspect that the "= 4.0-1" and "= 3.0.4-1" are incorrect too, and should be ">=". Of course, rpm-4.0-8mdk.rpm has these same dependencies: rpmlib(PayloadFilesHavePrefix) = 4.0-1 rpmlib(CompressedFileNames) = 3.0.4-1 glibc >= 2.1.92 So, it seems that rpm-4.0 has dependencies of itself! But doesn't recognize that it is itself because of error in the dependency list. I downloaded glibc-2.2.1-3mdk.i586.rpm, but I can not install this because the package was built with rpm-4.0, which I don't have. One final gotcha: There seems to be no way to determine what version of rpm was used to build a particular package, without downloading it and trying to install it. I could download packages for months before I find the right one! (and I have been, but I haven't found it yet!) Questions: 1. Is there a rpm package distributor that identifies which version of rpm was used to build the packages? Who? 2. How is one supposed to upgrade from rpm-3.0 to rpm-4.0? 3. It there a version of rpm-3.0.x that can read packages built by rpm-4.0? -- Gilligan | __o .oooO /| _ \,_ ( ) /p|\ (_)/ (_) \ ( Oooo. / | \ \_) ( ) ) / [EMAIL PROTECTED] (_/ [EMAIL PROTECTED]
RE: [expert] rpm-3.0 to rpm-4.0 catch 22
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) 2. How is one supposed to upgrade from rpm-3.0 to rpm-4.0? If you install rpm v4 from the cooker dir, you will have to rename your rpm database files to the new v4 naming convention. In /var/lib/rpm Old Names: -rw-r--r--1 root root16384 Jan 31 10:20 conflictsindex.rpm -rw-r--r--1 root root 2613248 Jan 31 10:20 fileindex.rpm -rw-r--r--1 root root16384 Jan 31 10:20 groupindex.rpm -rw-r--r--1 root root24576 Jan 31 10:20 nameindex.rpm -rw-r--r--1 root root 14446216 Jan 31 10:20 packages.rpm -rw-r--r--1 root root94208 Jan 31 10:20 providesindex.rpm -rw-r--r--1 root root 110592 Jan 31 10:20 requiredby.rpm -rw-r--r--1 root root16384 Jan 31 10:20 triggerindex.rpm New Names: -rw---1 root root 2646016 Feb 2 22:15 Basenames -rw---1 root root12288 Feb 1 12:33 Conflictname -rw---1 root root12288 Feb 2 22:15 Group -rw---1 root root24576 Feb 2 22:15 Name -rw---1 root root 11169792 Feb 2 22:15 Packages -rw---1 root root94208 Feb 2 22:15 Providename -rw---1 root root 126976 Feb 2 22:15 Requirename -rw---1 root root12288 Feb 1 12:26 Triggername Note the file sizes are a little off because I've installed/removed some packages since upgrading to cooker. 3. It there a version of rpm-3.0.x that can read packages built by rpm-4.0? See answer to question one. Regards, Chris - Chris Freeze Email: [EMAIL PROTECTED] Web: http://www.cs.clemson.edu/~cfreeze
Re: [expert] rpm-3.0 to rpm-4.0 catch 22
[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! > 2. How is one supposed to upgrade from rpm-3.0 to rpm-4.0? If you install rpm v4 from the cooker dir, you will have to rename your rpm database files to the new v4 naming convention. In /var/lib/rpm Old Names: -rw-r--r-- 1 root root 16384 Jan 31 10:20 conflictsindex.rpm -rw-r--r-- 1 root root 2613248 Jan 31 10:20 fileindex.rpm -rw-r--r-- 1 root root 16384 Jan 31 10:20 groupindex.rpm -rw-r--r-- 1 root root 24576 Jan 31 10:20 nameindex.rpm -rw-r--r-- 1 root root 14446216 Jan 31 10:20 packages.rpm -rw-r--r-- 1 root root 94208 Jan 31 10:20 providesindex.rpm -rw-r--r-- 1 root root 110592 Jan 31 10:20 requiredby.rpm -rw-r--r-- 1 root root 16384 Jan 31 10:20 triggerindex.rpm New Names: -rw--- 1 root root 2646016 Feb 2 22:15 Basenames -rw--- 1 root root 12288 Feb 1 12:33 Conflictname -rw--- 1 root root 12288 Feb 2 22:15 Group -rw--- 1 root root 24576 Feb 2 22:15 Name -rw--- 1 root root 11169792 Feb 2 22:15 Packages -rw--- 1 root root 94208 Feb 2 22:15 Providename -rw--- 1 root root 126976 Feb 2 22:15 Requirename -rw--- 1 root root 12288 Feb 1 12:26 Triggername Note the file sizes are a little off because I've installed/removed some packages since upgrading to cooker. > 3. It there a version of rpm-3.0.x that can read packages built by > rpm-4.0? See answer to question one. Regards, Chris - Chris Freeze Email: [EMAIL PROTECTED] Web: http://www.cs.clemson.edu/~cfreeze -- Gilligan | __o .oooO /| _ \,_ ( ) /p|\ (_)/ (_) \ ( Oooo. / | \ \_) ( ) ) / [EMAIL PROTECTED] (_/ [EMAIL PROTECTED]
Re: [expert] rpm-3.0 to rpm-4.0 catch 22
On 03 Feb 2001 19:30:26 +, 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.
Re: [expert] rpm-3.0 to rpm-4.0 catch 22
On 03-Feb-2001 Richard -Gilligan- Uschold wrote: 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! There may be logic errors or unneeded version checking in your version of RPM. What I'm trying to say is that binarywise they are the same. I would say look at a late model version of RPM 3.x. The unneeded version check may be gone. Regards, Chris - Chris Freeze Email: [EMAIL PROTECTED] Web: http://www.cs.clemson.edu/~cfreeze
Re: [expert] rpm-3.0 to rpm-4.0 catch 22
Bill Piety wrote: On 03 Feb 2001 19:30:26 +, 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 /| _ \,_ ( ) /p|\ (_)/ (_) \ ( Oooo. / | \ \_) ( ) ) / [EMAIL PROTECTED] (_/ [EMAIL PROTECTED]
Re: [expert] rpm-3.0 to rpm-4.0 catch 22
On 04 Feb 2001 01:18:55 +, Richard -Gilligan- Uschold wrote: Bill Piety wrote: On 03 Feb 2001 19:30:26 +, 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.
Re: [expert] rpm-3.0 to rpm-4.0 catch 22
Bill Piety wrote: On 04 Feb 2001 01:18:55 +, Richard -Gilligan- Uschold wrote: > Bill Piety wrote: > > > On 03 Feb 2001 19:30:26 +, 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
