I love playing catchup after a long hiatus :-)...
Seems like somethings out of sync here... While doing the make install, update appears to blow chunks, because of PortableUnixMailbox..
Compiling /home/mailman/Mailman/aliases.py ... Compiling /home/mailman/Mailman/htmlformat.py ... Compiling /home/mailman/Mailman/i18n.py ... Listing /home/mailman/Mailman/pythonlib ... Compiling /home/mailman/Mailman/versions.py ... Traceback (most recent call last): File "bin/update", line 47, in ? from Mailman import MailList File "/home/mailman/Mailman/MailList.py", line 49, in ? from Mailman.Archiver import Archiver File "/home/mailman/Mailman/Archiver/__init__.py", line 17, in ? from Archiver import * File "/home/mailman/Mailman/Archiver/Archiver.py", line 32, in ? from Mailman import Mailbox File "/home/mailman/Mailman/Mailbox.py", line 40, in ? class Mailbox(mailbox.PortableUnixMailbox): AttributeError: PortableUnixMailbox *** Error code 1 make: Fatal error: Command failed for target `update' 55.0u 111.0s 3:17 84% 0+0k 0+0io 0pf+0w
"RJ" == Ron Jarrell <jarrell@vt.edu> writes:
RJ> I love playing catchup after a long hiatus :-)...Fun, ain't it? :)
RJ> Seems like somethings out of sync here... While doing the make
RJ> install, update appears to blow chunks, because of
RJ> PortableUnixMailbox..Shite. Be sure you're using at least Python 2.1. I think this will be a requirement. Py2.0 is getting pretty long in the teeth (yes, yet another reason to get MM2.1 out the freakin' door asap!).
-Barry
At 03:25 PM 2/25/02 -0500, you wrote:
"RJ" == Ron Jarrell <jarrell@vt.edu> writes:
RJ> I love playing catchup after a long hiatus :-)...
Fun, ain't it? :)
RJ> Seems like somethings out of sync here... While doing the make RJ> install, update appears to blow chunks, because of RJ> PortableUnixMailbox..
Shite. Be sure you're using at least Python 2.1. I think this will be a requirement. Py2.0 is getting pretty long in the teeth (yes, yet another reason to get MM2.1 out the freakin' door asap!).
Ahhh. Yet another python upgrade just for mailman :-). Yup, still running 2.0... Ok, time to shelve mailman for a bit while we go hunt down python 2.1, and remember all the things we had to beat on to make it work the first time (since python has *never* compiled the way I want it the first time, not being on a linux box... Sigh.)
Will 2.0* run fine on python 2.1? I'll probably upgrade my production machines python sooner, rather than later, if I'm going to need to be doing it.
BTW, install or update probably should note that the user has a installed Mailman/pythonlib and delete the apps, before that bites someone on the ass. Or at least make a note in the upgrade instructions to go do it yourself.
"RJ" == Ron Jarrell <jarrell@vt.edu> writes:
RJ> Ahhh. Yet another python upgrade just for mailman :-). Yup,
RJ> still running 2.0... Ok, time to shelve mailman for a bit
RJ> while we go hunt down python 2.1, and remember all the things
RJ> we had to beat on to make it work the first time (since python
RJ> has *never* compiled the way I want it the first time, not
RJ> being on a linux box... Sigh.)Python 2.1 /should/ be better than 2.0. For one thing, you shouldn't have to mess with the Setup file, since by default Python 2.1 will auto-detect and build all the shared libraries it can. It uses a new build machinery that 2.0 didn't have, so it should be much less error prone. Of course, it's been a /long/ time since I did an install on anything other than a Linux box (or the occasional *BSD box).
RJ> Will 2.0* run fine on python 2.1? I'll probably upgrade my
RJ> production machines python sooner, rather than later, if I'm
RJ> going to need to be doing it.2.0.8 should run fine on anything from Python 1.5.2 to Python 2.2. If you're going to use Python 2.1, I'd recommend 2.1.2 which is the latest patch release.
RJ> BTW, install or update probably should note that the user has
RJ> a installed Mailman/pythonlib and delete the apps, before that
RJ> bites someone on the ass. Or at least make a note in the
RJ> upgrade instructions to go do it yourself.bin/update should already zap an installed Mailman/pythonlib, but it won't get called by default until I bump the version numbers. For now (running from cvs), manually run "bin/update -f". You can't do any harm from running this multiple times.
-Barry
At 03:25 PM 2/25/02 -0500, Barry A. Warsaw wrote:
Shite. Be sure you're using at least Python 2.1. I think this will be a requirement. Py2.0 is getting pretty long in the teeth (yes, yet another reason to get MM2.1 out the freakin' door asap!).
Actually, come to think of it, will mm 2.1* work ok on python 2.2? Since it's out, I might just as well go straight there!
"RJ" == Ron Jarrell <jarrell@vt.edu> writes:
RJ> Actually, come to think of it, will mm 2.1* work ok on python
RJ> 2.2? Since it's out, I might just as well go straight there!I develop primarily using Python 2.2 these days, with occasional forays back into 2.1.2 land.
-Barry
At 03:25 PM 2/25/02 -0500, you wrote:
Shite. Be sure you're using at least Python 2.1. I think this will be a requirement. Py2.0 is getting pretty long in the teeth (yes, yet
I hate installing python. All those 80 gazillion modules, each of which thinks it knows more about your system than you do, and wants to taunt you with it. I remembered that my big problems in the past have been the fact that I'm a Berkeley 3.N shop (soon to be 4.N) and pythin is still thinking 1.85... So I remembered to with the --without-libdb and compiled cleanly the first try. Now I discover that 2.2 is pissed at my libz, which I haven't changed since I started compiling python 1.whatever, and works fine with 2.0. Did I mention I hate installing python?
"RJ" == Ron Jarrell <jarrell@vt.edu> writes:
RJ> I hate installing python. All those 80 gazillion modules,
RJ> each of which thinks it knows more about your system than you
RJ> do, and wants to taunt you with it. I remembered that my big
RJ> problems in the past have been the fact that I'm a Berkeley
RJ> 3.N shop (soon to be 4.N) and pythin is still thinking 1.85...Berkeley db support is the sorest point for me, but BDB support on most Linuxes is a mess anyway. On my Linux box, with multiple BDB libraries installed, Python 2.1.x always worked just fine for me. It's completely broken in Python 2.2; won't even build. But unless you need BDB support for something other than Mailman, I wouldn't worry about it. I changed the Postfix MTA module to not depend on the bsddb module, so that fragile piece of brokenness is gone.
(Aside: if you're doing serious work with Berkeley DB in Python, do yourself a favor and go to pybsddb.sf.net, download and install Robin Dunn's new wrapper. It's a little tricky getting to build correctly, but read the docs carefully and you should be okay.)
RJ> So I remembered to with the --without-libdb and compiled
RJ> cleanly the first try. Now I discover that 2.2 is pissed at
RJ> my libz, which I haven't changed since I started compiling
RJ> python 1.whatever, and works fine with 2.0. Did I mention I
RJ> hate installing python?Sigh, I dimly remember something about zlib compatibility, it's got to be version 1.0.4 or better, right? I've got zlib 1.1.3 on my ancient RH6.1 Linux box, and Python 2.2 built against it no sweat.
-Barry
At 02:02 AM 2/26/02 -0500, Barry A. Warsaw wrote:
RJ> So I remembered to with the --without-libdb and compiled RJ> cleanly the first try. Now I discover that 2.2 is pissed at RJ> my libz, which I haven't changed since I started compiling RJ> python 1.whatever, and works fine with 2.0. Did I mention I RJ> hate installing python?
Sigh, I dimly remember something about zlib compatibility, it's got to be version 1.0.4 or better, right? I've got zlib 1.1.3 on my ancient RH6.1 Linux box, and Python 2.2 built against it no sweat.
Turns out, the autodetect worked fine on berkeleydb, but picked up the wrong libraries (ones it couldnt' understand, being too new), so I had to override that, to get it to work. However the autodetect stuff apparently did *not* work on zlib (which was 1.1.3, and has been for a while on my machine). It then proceeded to give me three pages of library errors on linking. I'm thinking it didn't build the interface module, but tried to link in the library anyway. Eventually I figured out that I had to manually enable it in Setup (btw, the docs have a certain "tail chasing" quality to them, with various files point you at files that have comments that say "Well, nothing *really* uses this file anymore, you should go look at X." I found my self wandering from Setup to Setup.config to setup.py following the bread crumbs...
Eventually my 2.2 passed all its tests. Which leads to an entirely different issue of me wanting a word or two with the person who developed the sunaudiodev test... Which had never properly built before, but 2.2 figured out I had one and auto-enabled it. I was building and testing on the workstation, and doing some abuse tracking on my laptop. Suddenly, after visiting a spam site my laptop yelled "Noooo one expects the spanish inquisition." Regular python builders on sun boxes will already know the resolution to this story. I freaked, figuring I'd let some applet through my security software and into my laptop. After searching for a while, and revisiting websites, looking at (bad) html code, (and starting another test run on python going, after trying another library fix), my laptop suddenly did it again.
I dragged out ever ip and file descriptor tracking program I had, and was watching the machine like a hawk. Did another python test on the sun workstation. Which, by the way, is in a tower, under my desk, coincidentally right under my laptop. Laptop does the monty python bit again, and now I'm confused, because not a single blip registered on the monitors - how in hell did the sound get to the speakers, when I can see none of the audio devices were touched?
Suddenly I have an epiphany... And start cursing. And type "python Lib/blahblahblah/test_sunaudiodev" and hear "Nooo one expects the spanish inquisition" coming from, I know realize, under my table...
ARRGH!
Two hours later, it was really funny...
BTW, either update needs to do something, or issue a warning, or install needs to refer to it, or something, but even knowing exactly what caused it, I got bit by the "en" was installed in my list directory.
Took me a while to realize it was happening, because, screwing around, I selected Russian as my language of choice. Which, BTW, displayed everything in English. Does that mean I'm missing something in the install? When I switched to English for real, I got the *old* web pages... And immediately realized what was going on...
"Ron" == Ron Jarrell <jarrell@vt.edu> writes:
Ron> Took me a while to realize it was happening, because,
Ron> screwing around, I selected Russian as my language of choice.
Ron> Which, BTW, displayed everything in English. Does that mean
Ron> I'm missing something in the install? When I switched to
Ron> English for real, I got the *old* web pages... And
Ron> immediately realized what was going on...You'll notice that some of the messages, not many, are actually in Russian. (Like the language pull-down box).
That means that the Russian translation has been started, but is missing a lot of translated strings, so Mailman uses the English defaults for those.
Ben
-- Brought to you by the letters C and H and the number 5. "Elate means having wings." Debian GNU/Linux maintainer of Gimp and Nethack -- http://www.debian.org/
Hello Ben,
On Wed, Feb 27, 2002 at 02:07:29PM +0900, Ben Gertzfield wrote:
"Ron" == Ron Jarrell <jarrell@vt.edu> writes:
Ron> Took me a while to realize it was happening, because, Ron> screwing around, I selected Russian as my language of choice. Ron> Which, BTW, displayed everything in English. Does that mean Ron> I'm missing something in the install? When I switched to Ron> English for real, I got the *old* web pages... And Ron> immediately realized what was going on...You'll notice that some of the messages, not many, are actually in Russian. (Like the language pull-down box).
That means that the Russian translation has been started, but is missing a lot of translated strings, so Mailman uses the English defaults for those.
Who does the translation? Depending on the message pack size, I could help and/or channel the work to folks over our Russian distro (ALT) posse.
-- Stay tuned, MhZ JID: mookid@jabber.org
I live the way I type; fast, with a lot of mistakes.
I believe, mailman-i18n is a better forum for this question. :))
I'd say it's me who try to translate the mailman messages to Russian with help of others...
I created a list mailman-ru@only.mawhrin.net, it's pretty quiet at the moment, but it's there for discussing the translation...
-- Misha
I seem to i the translation effor On Tue, Mar 12, 2002 at 12:48:21PM +0300, Mikhail Zabaluev wrote:
Hello Ben,
On Wed, Feb 27, 2002 at 02:07:29PM +0900, Ben Gertzfield wrote:
> "Ron" == Ron Jarrell <jarrell@vt.edu> writes:
Ron> Took me a while to realize it was happening, because, Ron> screwing around, I selected Russian as my language of choice. Ron> Which, BTW, displayed everything in English. Does that mean Ron> I'm missing something in the install? When I switched to Ron> English for real, I got the *old* web pages... And Ron> immediately realized what was going on...You'll notice that some of the messages, not many, are actually in Russian. (Like the language pull-down box).
That means that the Russian translation has been started, but is missing a lot of translated strings, so Mailman uses the English defaults for those.
Who does the translation? Depending on the message pack size, I could help and/or channel the work to folks over our Russian distro (ALT) posse.
-- Stay tuned, MhZ JID: mookid@jabber.org
I live the way I type; fast, with a lot of mistakes.
"MS" == Mikhail Sobolev <mss@mawhrin.net> writes:
MS> I believe, mailman-i18n is a better forum for this
MS> question. :))
MS> I'd say it's me who try to translate the mailman messages to
MS> Russian with help of others...
MS> I created a list mailman-ru@only.mawhrin.net, it's pretty
MS> quiet at the moment, but it's there for discussing the
MS> translation...I've added this mailing list to the i18n page. -Barry
participants (5)
-
barry＠zope.com -
Ben Gertzfield -
Mikhail Zabaluev -
mss＠mawhrin.net -
Ron Jarrell