Well, in this case, rpm did not require rpmbuild to be upgraded before I upgraded it to 4.1.1. It did require popt, and one other. :) I don't do --nodeps unless I'm installing a package that really isn't tied into what it is requiring. This is usually due installing an rpm that requires an older /lib/libblah.so.0 and only /lib/libblah.so.2 is available. I then make the softlink for .so.0, install with --nodeps and then see if it runs. If it doesn't, then the package is removed. :) On Mon, 8 Dec 2003, Michael Schwendt wrote: > Date: Mon, 8 Dec 2003 19:00:09 +0100 > From: Michael Schwendt <ms-nospam-0306@xxxxxxxx> > Reply-To: fedora-legacy-list@xxxxxxxxxx > To: fedora-legacy-list@xxxxxxxxxx > Subject: Re: build > > On 08 Dec 2003 09:09:31 -0600, Bret Hughes wrote: > > > > > > rpmbuild: relocation error: rpmbuild: undefined symbol: freeSpecVec > > > > > > > > > > > > > > > here is my rpm list for redhat 8.0. Note that the rpm was upgraded > > > > > because of the hang problem that the standard 4.x rpm from redhat has > > > > > under 8.0. With 4.1.1, the problem does not occur. > > > > > > > > > > [root@rh80 SPECS]# rpm -qa | grep rpm > > > > > > > > > > rpmdb-redhat-8.0-0.20020910 > > > > > rpm-python-4.1.1-1.8x > > > > > rpm2html-1.7-8 > > > > > librpm404-devel-4.0.4-8x.27 > > > > > redhat-rpm-config-8.0-1 > > > > > rpm-4.1.1-1.8x > > > > > rpm404-python-4.0.4-8x.27 > > > > > rpm-build-4.1-1.06 > > > > > > > > This should be rpm-build-4.1.1-1.8x, so it matches your version of RPM. > > > > > > > > > Excellent! DOH! Yes, that was it. I had never heard of rpmbuild > > > before, it appears to be a neat tool. > > > > > > > Isn't this a symptom of a packaging error? seems like there should be a > > dependency built into rpmbuild to match the rpm version. > > The error is to assume that there's no such dependency: ;) > > $ rpm -qR rpm-build | grep rpm > rpm = 4.1.1 > rpmlib(VersionedDependencies) <= 3.0.3-1 > rpmlib(CompressedFileNames) <= 3.0.4-1 > librpm-4.1.so > librpmbuild-4.1.so > librpmdb-4.1.so > librpmio-4.1.so > > Some users play too much with --nodeps/--force while installing or > upgrading packages. > >
