Sorry if this is an old one; I'm soooo behind on mailman-developers.. I skimmed through, and didn't see anything that lept out at me.
Trying to build 2.1.4.
/usr/local/bin/python ../build/bin/msgfmt.py -o ca/LC_MESSAGES/mailman.mo ca/LC_MESSAGES/mailman.po Traceback (most recent call last): File "../build/bin/msgfmt.py", line 203, in ? main() File "../build/bin/msgfmt.py", line 199, in main make(filename, outfile) File "../build/bin/msgfmt.py", line 151, in make l = eval(l) File "<string>", line 1 """"" >Python regular expression</a>. When entering backslashes, do so\n" ^ SyntaxError: invalid token *** Error code 1 (ignored)
It *was* doing this on nearly every file. I wiped out the messages directory, re synced it with cvs, did a distclean and a make, and got it down to just the one error in the ca set. It was the same invalid token for the others too, before.
Running Python 2.2, not 2.2.1...
Ron Jarrell Wrote:
[snip, there is an error compiling LC_MESSAGES]
""""" >Python regular expression</a>. When enteringbackslashes, do so\n"
^
SyntaxError: invalid token *** Error code 1 (ignored)
I can confirm this on a fresh CVS checkout of the sourceforge cvs tree, the ca/LC_MESSAGES/mailman.po file seems to contain an error it has 5 double qoutes instead of one in lines 5590 and 5622. If you change these to one it builds correctly again. This seems to be a mistake in the 1.3 cvs checkin for ca/LC_MESSAGES/mailman.po.
The 2.1.4 tgz file on the sourceforge file download page does not have this problem, as it contains the 1.1.2.2 cvs revision.
-- Gijs
On Fri, 2004-01-02 at 07:03, Gijs Hollestelle wrote:
I can confirm this on a fresh CVS checkout of the sourceforge cvs tree, the ca/LC_MESSAGES/mailman.po file seems to contain an error it has 5 double qoutes instead of one in lines 5590 and 5622. If you change these to one it builds correctly again. This seems to be a mistake in the 1.3 cvs checkin for ca/LC_MESSAGES/mailman.po.
The 2.1.4 tgz file on the sourceforge file download page does not have this problem, as it contains the 1.1.2.2 cvs revision.
Remember that if you're working from CVS, you definitely want to be on the Release_2_1-maint branch. The CVS trunk is not guaranteed to be stable.
-Barry
participants (3)
-
Barry Warsaw -
Gijs Hollestelle -
Ron Jarrell