Re: [Mailman-Developers] version mismatch?
--On 20 July 2005 14:57:26 -0400 Barry Warsaw <barry@python.org> wrote:
On Wed, 2005-07-20 at 12:16, Ian Eiloart wrote:
Am I right in thinking this means that I need to downgrade my python version to make this work?
No, but apparently does mean that you'll have to rebuild the codec extensions that come with Mailman. I /think/ if you run Mailman's config.status and then run make install again (against Python 2.4.1 of course) you should be golden.
Let us know if that works and I'll update the release notes.
-Barry
OK. I'm having a go at this. I'm not sure how that's supposed to work, though.
I've built Mailman 2.1.6 with Python 2.4.1, and it didn't work when installed with Python 2.4.1, and run along side Python 2.4.1
I've built Mailman 2.1.6 with Python 2.2.3, and it works fine. Doesn't matter whether I have Python 2.2.3 or 2.4.1.
I'm trying again - but why would config.status do anything?
Well, blimey. Everything seems hunky-dory now. Thanks, Barry!
-- Ian Eiloart Servers Team Sussex University ITS
--On 21 July 2005 15:32:14 +0100 Ian Eiloart <iane@sussex.ac.uk> wrote:
Well, blimey. Everything seems hunky-dory now. Thanks, Barry!
Ah, I spoke too soon.
If I build with --prefix=foo where foo is an empty directory, then everything is OK. If foo is /local/mailman (my operational location), then building Mailman 2.1.6 with Python 2.4.1 doesn't work.
So, I guess the way to do this is to make sure I use --prefix=/local/mailman-2.1.6, test the cgi scripts there, link <prefix>/lists and so on, then link /local/mailman so that my startup scripts work.
-- Ian Eiloart Servers Team Sussex University ITS
On Thu, 2005-07-21 at 10:32, Ian Eiloart wrote:
OK. I'm having a go at this. I'm not sure how that's supposed to work, though.
I've built Mailman 2.1.6 with Python 2.4.1, and it didn't work when installed with Python 2.4.1, and run along side Python 2.4.1
What happens? Please provide more details about what "didn't work"!
I've built Mailman 2.1.6 with Python 2.2.3, and it works fine. Doesn't matter whether I have Python 2.2.3 or 2.4.1.
I'm trying again - but why would config.status do anything?
config.status rebuilds the Makefiles and other .in files based on your original ./configure invocation. You can always just re-run configure with your original options for a similar effect.
Well, blimey. Everything seems hunky-dory now. Thanks, Barry!
I'm not sure what I did, but yay! :) Getting it working is probably more imporatnt that whether you're using Python 2.3 or 2.4. :)
-Barry
--On 24 July 2005 16:26:08 -0400 Barry Warsaw <barry@python.org> wrote:
On Thu, 2005-07-21 at 10:32, Ian Eiloart wrote:
OK. I'm having a go at this. I'm not sure how that's supposed to work, though.
I've built Mailman 2.1.6 with Python 2.4.1, and it didn't work when installed with Python 2.4.1, and run along side Python 2.4.1
What happens? Please provide more details about what "didn't work"!
Well, it's the same API version number error that I reported before.
-- Ian Eiloart Servers Team Sussex University ITS
participants (2)
-
Barry Warsaw -
Ian Eiloart