mailman 2.1.2 upgrade warning on OS X.
barry:
FYI: while trying to update from CVS tonight, I got errors during the make. "msgmerge -U" was erroring out as an unknown option.
turns out (a) msgmerge (and gettext) aren't installed on OS X as part of the disto. I'd previously installed them through fink -- but fink is distributing a really old version (0.10.something instead of 0.11.5). So this change to the gettext stuff is going to break OS X installations as they try to upgrade, and they're going to have to track down and install the current gettext to make things work again (I'm in process now, it's unclear that's all I'll find....)
perhaps the README should be updated for this?
On Wed, 2003-05-07 at 23:46, Chuq Von Rospach wrote:
barry:
FYI: while trying to update from CVS tonight, I got errors during the make. "msgmerge -U" was erroring out as an unknown option.
I think this is just a buglet in the Makefile.in on the cvs trunk. I thought I checked in a fix for this but 1) maybe I didn't (will check shortly), or 2) you didn't pick it up because you need to re-run configure or config.status to regen the Makefile.
You guys (end users installing from source) should never have to run msgmerge. You /will/ have to run msgfmt but that's why I include a pure-Python version in bin (which I think you have to re-run configure also to get).
-Barry
On Wednesday, May 7, 2003, at 08:59 PM, Barry Warsaw wrote:
I think this is just a buglet in the Makefile.in on the cvs trunk. I thought I checked in a fix for this but 1) maybe I didn't (will check shortly), or 2) you didn't pick it up because you need to re-run configure or config.status to regen the Makefile.
did that. updated from CVS and got the makefile.in update...
% make clean % config.status % make
/usr/bin/python ../build/bin/msgfmt.py -o nl/LC_MESSAGES/mailman.mo
nl/LC_MESSAGES/mailman.po
/usr/bin/python ../build/bin/msgfmt.py -o no/LC_MESSAGES/mailman.mo
no/LC_MESSAGES/mailman.po
Merging new template file with existing translations
msgmerge -U pl/LC_MESSAGES/mailman.po mailman.pot
msgmerge: invalid option -- U
Try msgmerge --help' for more information. make[1]: *** [pl/LC_MESSAGES/mailman.po] Error 1 make[1]: Nothing to be done for
all'.
still failing.
nope. make distclean, configure, make still fails:
/usr/bin/python ../build/bin/msgfmt.py -o ko/LC_MESSAGES/mailman.mo
ko/LC_MESSAGES/mailman.po
/usr/bin/python ../build/bin/msgfmt.py -o lt/LC_MESSAGES/mailman.mo
lt/LC_MESSAGES/mailman.po
/usr/bin/python ../build/bin/msgfmt.py -o nl/LC_MESSAGES/mailman.mo
nl/LC_MESSAGES/mailman.po
/usr/bin/python ../build/bin/msgfmt.py -o no/LC_MESSAGES/mailman.mo
no/LC_MESSAGES/mailman.po
Merging new template file with existing translations
msgmerge -U pl/LC_MESSAGES/mailman.po mailman.pot
msgmerge: invalid option -- U
Try msgmerge --help' for more information. make[1]: *** [pl/LC_MESSAGES/mailman.po] Error 1 make[1]: Nothing to be done for
all'.
37.950u 19.490s 1:01.09 94.0% 0+0k 0+55io 0pf+0w
On Wednesday, May 7, 2003, at 09:17 PM, Chuq Von Rospach wrote:
On Wednesday, May 7, 2003, at 08:59 PM, Barry Warsaw wrote:
I think this is just a buglet in the Makefile.in on the cvs trunk. I thought I checked in a fix for this but 1) maybe I didn't (will check shortly), or 2) you didn't pick it up because you need to re-run configure or config.status to regen the Makefile.
did that. updated from CVS and got the makefile.in update...
% make clean % config.status % make
/usr/bin/python ../build/bin/msgfmt.py -o nl/LC_MESSAGES/mailman.mo nl/LC_MESSAGES/mailman.po /usr/bin/python ../build/bin/msgfmt.py -o no/LC_MESSAGES/mailman.mo no/LC_MESSAGES/mailman.po Merging new template file with existing translations msgmerge -U pl/LC_MESSAGES/mailman.po mailman.pot msgmerge: invalid option -- U Try
msgmerge --help' for more information. make[1]: *** [pl/LC_MESSAGES/mailman.po] Error 1 make[1]: Nothing to be done for
all'.still failing.
Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers
On Wednesday, May 7, 2003, at 11:04 PM, Chuq Von Rospach wrote:
yippee!
that last set of changes seems to have fixed it.
new problem. started up 2.1.2+, and...
File "/usr/local/mailman/bin/qrunner", line 270, in ? main() File "/usr/local/mailman/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman/Mailman/Queue/Runner.py", line 76, in run self._snooze(filecnt) File "/usr/local/mailman/Mailman/Queue/RetryRunner.py", line 44, in _snooze time.sleep(self.SLEEPTIME) NameError: global name 'time' is not defined
it actually seems to be delivering, though..
*** /Users/mailman/logs/smtp *** May 07 23:21:45 2003 (6938) 000f01c3151e$57b381d0$0a02a8c0@budjens.org smtp for 211 recips, completed in 38.212 seconds
*** /Users/mailman/logs/post *** May 07 23:21:45 2003 (6938) post to sharks from jimbudler@earthlink.net, size=2029, message-id=000f01c3151e$57b381d0$0a02a8c0@budjens.org, success
adding
import time
to the RetryRunner.py file fixes this. I seem to be up on 2.1.2+
On Wednesday, May 7, 2003, at 11:23 PM, Chuq Von Rospach wrote:
File "/usr/local/mailman/Mailman/Queue/RetryRunner.py", line 44, in _snooze time.sleep(self.SLEEPTIME) NameError: global name 'time' is not defined
On Thursday, May 8, 2003, at 02:29 AM, Chuq Von Rospach wrote:
adding
import time
to the RetryRunner.py file fixes this. I seem to be up on 2.1.2+
Fixed in cvs (on the trunk). Thanks.
BTW, RetryRunner will be (mostly) no-op if you never get temporary failures from your MTA. If you know it can never happen, you can disable the RetryRunner in your mm_cfg.py file.
-Barry
participants (2)
-
Barry Warsaw
-
Chuq Von Rospach