On Saturday 08 February 2003 02:39 pm, D. R. Evans wrote:
The current issue of Linux Journal has an interesting story about a
program called spambayes: interesting enough that I wanted to try it on
my gateway/firewall machine.
This machine is running LM 8.2 (on the grounds that if it ain't broke,
don't fix it; I have LM 9.0 running on another machine, but don't like to
make other than minimal changes on the machine that acts as my gateway to
the world).
The spambayes page says that it needs a later version of python than the
version 2.1.1 that came with LM 8.2.
OK, thought I, that's a minor upgrade that probably won't break
anything. But when I went to install the python 2.2.2-6mdk rpm from the
cooker, it wanted several more rpms. These looked innocuous enough (things
like python libraries). But then those wanted more. And then those wanted
things like a new version of kde-base and dhcpd. At which point I thought
why on Earth should I need to install a new version of dhcpd just because
I want to upgrade from python 2.1.1 to 2.2.2?
So the upshot of all this is: what is the recommended procedure for
upgrading from python 2.1.1 to 2.2.2 on an LM 8.2 machine without having to
mess with anything major and with a reasonable assurance that nothing will
break?
Doc Evans
Well get the source rpm and build it on your 8.2 machine with rpm --rebuild
what you are encountering is the fact that binaries are incompatible between
8.2 and 9.0 because there was a change in the glibc version, as well as a
host of dependencies.
You may not be out of the woods with the source but it should be
compatible--once you have used the rebuild, you should find a good rpm in
/usr/src/RPM/RPMS
Civileme
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
