- WLUG - wlug.mailman3.com

Re: [Wlug] libcrypto.so.4

by Michael Long

I found what looks like the source files from a tar package in /usr/src/packages/BUILD/Python-2.2.3. It appears that I could build it by running the usual ./configure make ... process. There are no rpms in /usr/src/packages/RPMS/. Do I need to build the rpm from this? As a reminder I am using the SuSE 8.2 distro so the directory structure is slightly different. --Mike > > Did you install the resulting i386.rpm files from the rebuild step? > They should have ended up in /usr/src/redhat/RPMS/i386 > > -- > Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ > PGP Key ID: 49BB5886 > Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886 > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > > >

Aug. 7, 2003

Re: [Wlug] libcrypto.so.4

by Charles R. Anderson

On Thu, Aug 07, 2003 at 04:48:04PM -0400, Michael Long wrote: mlong> I have discovered that the files in the expat-devel package are already mlong> installed on the system so I ran rpmbuild --rebuild --nodeps .... mlong> It appeared to compile with a lot of warnings about anti-aliasing. mlong> Unfortunately the warnings scrolled out of the term buffer so I don't mlong> have the exact warning. This process is very verbose and I don't know if mlong> it completed successfully or not. When I query the rpm database it still mlong> shows the old version of python. Did I miss a step? Did you install the resulting i386.rpm files from the rebuild step? They should have ended up in /usr/src/redhat/RPMS/i386 -- Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886

Aug. 7, 2003

Re: [Wlug] libcrypto.so.4

by Michael Long

I have discovered that the files in the expat-devel package are already installed on the system so I ran rpmbuild --rebuild --nodeps .... It appeared to compile with a lot of warnings about anti-aliasing. Unfortunately the warnings scrolled out of the term buffer so I don't have the exact warning. This process is very verbose and I don't know if it completed successfully or not. When I query the rpm database it still shows the old version of python. Did I miss a step? > > I should mention, that if you find one that has the expat include > files, but isn't named expat-devel, you can force the build with: > > rpmbuild --rebuild --nodeps .... > > Actually, it might be easier to grab the SuSE python2 src.rpm, and > modify that one to use the new python2-2.2.3 tar source. That way, > your src.rpm will be based on the SuSE one, with all the correct > dependencies for expat, etc: > > rpm -i the-suse-python2-2.2.2.src.rpm > > cd /usr/src/redhat/SPECS > > edit python2.spec to change the version to 2.2.3 and release to > 1custom or similar. > > copy the new python2-2.2.3.tar.gz into /usr/src/redhat/SOURCES > > rpmbuild -ba /usr/src/redhat/SPECS/python2.spec > > -- > Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ > PGP Key ID: 49BB5886 > Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886 > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > > >

Aug. 7, 2003

Re: [Wlug] libcrypto.so.4

by Michael Long

What has me concerned is that there is an expat package and it is installed on the system, but I am still getting the missing expat-devel error. The following are the results of the rpm queries: rpm -ql expat | grep include /usr/include/expat.h rpm -qa | grep expat expat-1.95.6-11 --Mike > Do you have an expat package? Most likely then the expat-devel stuff > is in the expat package. List it to see if there are any include > files: > > rpm -ql expat | grep include > > Or see if any other package mentions "expat": > > rpm -qa | grep expat > > If SuSE doesn't have any expat packages available at all, then > rebuilding one probably won't hurt. > > > -- > Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ > PGP Key ID: 49BB5886 > Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886 > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > > >

Aug. 7, 2003

Re: [Wlug] libcrypto.so.4

by Charles R. Anderson

On Thu, Aug 07, 2003 at 11:00:11AM -0400, Charles R. Anderson wrote: cra> If SuSE doesn't have any expat packages available at all, then cra> rebuilding one probably won't hurt. I should mention, that if you find one that has the expat include files, but isn't named expat-devel, you can force the build with: rpmbuild --rebuild --nodeps .... Actually, it might be easier to grab the SuSE python2 src.rpm, and modify that one to use the new python2-2.2.3 tar source. That way, your src.rpm will be based on the SuSE one, with all the correct dependencies for expat, etc: rpm -i the-suse-python2-2.2.2.src.rpm cd /usr/src/redhat/SPECS edit python2.spec to change the version to 2.2.3 and release to 1custom or similar. copy the new python2-2.2.3.tar.gz into /usr/src/redhat/SOURCES rpmbuild -ba /usr/src/redhat/SPECS/python2.spec -- Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886

Aug. 7, 2003

Re: [Wlug] libcrypto.so.4

by Charles R. Anderson

On Thu, Aug 07, 2003 at 10:40:12AM -0400, Michael Long wrote: mlong> I have yet another question...when rebuilding the source rpm I get an mlong> error saying that I need the expat-devel libraries. My distribution mlong> either doesn't come with them or they are part of another package and I mlong> am not seeing it. If I download and rebuild the source rpm package for mlong> expat-devel from rpmfind.net what is the risk that it will break mlong> something on my system. Do you have an expat package? Most likely then the expat-devel stuff is in the expat package. List it to see if there are any include files: rpm -ql expat | grep include Or see if any other package mentions "expat": rpm -qa | grep expat If SuSE doesn't have any expat packages available at all, then rebuilding one probably won't hurt. -- Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886

Aug. 7, 2003

Re: [Wlug] libcrypto.so.4

by Michael Long

I have yet another question...when rebuilding the source rpm I get an error saying that I need the expat-devel libraries. My distribution either doesn't come with them or they are part of another package and I am not seeing it. If I download and rebuild the source rpm package for expat-devel from rpmfind.net what is the risk that it will break something on my system. Thanks, Mike > I am using SuSE 8.2 and I found the rpm's on rpmfind.net. The > distribution came with python 2.2.2 but I need python 2.2.3. I looked > for new SuSE packages but did not find them. I will follow your > suggestion and download the src rpm and rebuild it. > > Mike >

Aug. 7, 2003

Re: [Wlug] libcrypto.so.4

by Michael Long

I am using SuSE 8.2 and I found the rpm's on rpmfind.net. The distribution came with python 2.2.2 but I need python 2.2.3. I looked for new SuSE packages but did not find them. I will follow your suggestion and download the src rpm and rebuild it. Mike > > What Linux distribution and release are you using? Where did you get > those RPM packages from? You really should only use RPM packages for > your specific distribution and release. Ideally, you should use the > ones that came as a part of your distribution, if available. > > For example, Red Hat Linux 7.3 has python2 RPMs that come with it, and > newer bug-fixed ones available as errata updates > (ftp://updates.redhat.com/) > > python2-2.2.2-3.7.3.i386.rpm > python2-devel-2.2.2-3.7.3.i386.rpm > python2-docs-2.2.2-3.7.3.i386.rpm > > and Red Hat Linux 9 already has python 2 as the default: > > python-2.2.2-26.i386.rpm > python-optik-1.4-2.noarch.rpm > python-docs-2.2.2-26.i386.rpm > python-devel-2.2.2-26.i386.rpm > python-tools-2.2.2-26.i386.rpm > > If you just grabbed whatever RPM packages you could find, they are > probably not built against the proper versions of your system > libraries, which in your case are openssl and rpm. You cannot just > upgrade system libraries without breaking much of the rest of your > system. > > If you must have that particular version of python2, consider > recompiling the src.rpm so that it will be built against your exact > system library versions: > > rpmbuild --rebuild python2-2.2.3-1.src.rpm > > Then install the resulting binary rpms that are built: > > rpm -Uvh /usr/src/redhat/RPMS/i386/python2-2.2.3-1.i386.rpm > > -- > Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ > PGP Key ID: 49BB5886 > Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886 > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > > >

Aug. 6, 2003

Re: [Wlug] libcrypto.so.4

by Charles R. Anderson

On Wed, Aug 06, 2003 at 02:37:27PM -0400, Michael Long wrote: mlong> I am attempting to install the rpm python2-2.2.3-1 and get the following mlong> error: mlong> mlong> edev:/home/mlong # rpm -Uvh python2-2.2.3-1.i386.rpm mlong> error: failed dependencies: mlong> libcrypto.so.4 is needed by python2-2.2.3-1 mlong> libssl.so.4 is needed by python2-2.2.3-1 mlong> rpmlib(PartialHardlinkSets) <= 4.0.4-1 is needed by mlong> python2-2.2.3-1 mlong> mlong> I then tried updating openssl-0.9.6i-12 with openssl-0.9.7a-16 mlong> and got a large list of failed dependencies. The two files I need are a mlong> part of the latest openssl package. How should I go about resolving the mlong> python dependencies? What Linux distribution and release are you using? Where did you get those RPM packages from? You really should only use RPM packages for your specific distribution and release. Ideally, you should use the ones that came as a part of your distribution, if available. For example, Red Hat Linux 7.3 has python2 RPMs that come with it, and newer bug-fixed ones available as errata updates (ftp://updates.redhat.com/) python2-2.2.2-3.7.3.i386.rpm python2-devel-2.2.2-3.7.3.i386.rpm python2-docs-2.2.2-3.7.3.i386.rpm and Red Hat Linux 9 already has python 2 as the default: python-2.2.2-26.i386.rpm python-optik-1.4-2.noarch.rpm python-docs-2.2.2-26.i386.rpm python-devel-2.2.2-26.i386.rpm python-tools-2.2.2-26.i386.rpm If you just grabbed whatever RPM packages you could find, they are probably not built against the proper versions of your system libraries, which in your case are openssl and rpm. You cannot just upgrade system libraries without breaking much of the rest of your system. If you must have that particular version of python2, consider recompiling the src.rpm so that it will be built against your exact system library versions: rpmbuild --rebuild python2-2.2.3-1.src.rpm Then install the resulting binary rpms that are built: rpm -Uvh /usr/src/redhat/RPMS/i386/python2-2.2.3-1.i386.rpm -- Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886

Aug. 6, 2003

libcrypto.so.4

by Michael Long

Hi, I am attempting to install the rpm python2-2.2.3-1 and get the following error: edev:/home/mlong # rpm -Uvh python2-2.2.3-1.i386.rpm error: failed dependencies: libcrypto.so.4 is needed by python2-2.2.3-1 libssl.so.4 is needed by python2-2.2.3-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 is needed by python2-2.2.3-1 I then tried updating openssl-0.9.6i-12 with openssl-0.9.7a-16 and got a large list of failed dependencies. The two files I need are a part of the latest openssl package. How should I go about resolving the python dependencies? Thanks, Mike

Aug. 6, 2003