bin/update: "cannot import name SimpleCookie" in mailman cvs
So, when updating from 2.0 to cvs, make install ran fine up to update: Compiling /var/local/mailman/Mailman/pythonlib/StringIO.py ... Compiling /var/local/mailman/Mailman/pythonlib/__init__.py ... Compiling /var/local/mailman/Mailman/pythonlib/cgi.py ... Compiling /var/local/mailman/Mailman/pythonlib/mailbox.py ... Compiling /var/local/mailman/Mailman/pythonlib/rfc822.py ... Compiling /var/local/mailman/Mailman/versions.py ... Traceback (most recent call last): File "bin/update", line 47, in ? from Mailman import MailList File "/var/local/mailman/Mailman/MailList.py", line 58, in ? from Mailman.SecurityManager import SecurityManager File "/var/local/mailman/Mailman/SecurityManager.py", line 62, in ? from Cookie import SimpleCookie as Cookie ImportError: cannot import name SimpleCookie make: *** [update] Error 1
I have python 2.1.1
I move the lists off, completed the install, brought a list back, ran update by hand, and it worked.
Marc
Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key
"MM" == Marc MERLIN <marc_news@valinux.com> writes:
MM> So, when updating from 2.0 to cvs, make install ran fine up to
MM> update: Compiling
| ImportError: cannot import name SimpleCookie
| make: *** [update] Error 1
MM> I have python 2.1.1
MM> I move the lists off, completed the install, brought a list
MM> back, ran update by hand, and it worked.This one should be shallow, and I think fixed in MM21a4. You need to remove all traces of Cookie.py from the Mailman installed directories. We used to provide a very old version of Cookie.py, but as of Python 2.0, a better version comes with the Python distro. Mailman won't pick that up though if the one from misc is still installed.
bin/update should now delete this old file.
-Barry
On Tue, Jan 01, 2002 at 09:08:12AM -0500, Barry A. Warsaw wrote:
"MM" == Marc MERLIN <marc_news@valinux.com> writes:
MM> So, when updating from 2.0 to cvs, make install ran fine up to MM> update: Compiling | ImportError: cannot import name SimpleCookie | make: *** [update] Error 1 MM> I have python 2.1.1 MM> I move the lists off, completed the install, brought a list MM> back, ran update by hand, and it worked.This one should be shallow, and I think fixed in MM21a4. You need to remove all traces of Cookie.py from the Mailman installed directories. We used to provide a very old version of Cookie.py, but as of Python 2.0, a better version comes with the Python distro. Mailman won't pick that up though if the one from misc is still installed.
bin/update should now delete this old file.
I found out in the meantime that even in beta 3, update failed the first time but seemed to delete Cookie.py (or something else did), so it succeeded the second time
I'll try to upgrade another list server from 2.0 to 2.1cvs when I get home next week and report back if there is still a problem.
Thanks Marc
Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key
mercoledì, 02 gennaio 2002 alle 09:50:03, Marc MERLIN ha scritto:
| ImportError: cannot import name SimpleCookie | make: *** [update] Error 1
This one should be shallow, and I think fixed in MM21a4. You need to remove all traces of Cookie.py from the Mailman installed
I found out in the meantime that even in beta 3, update failed the first time but seemed to delete Cookie.py (or something else did), so it succeeded the second time
I've just upgraded from 2.1a3(CVS) to 2.1a4(CVS) and the same problem occurred (even re-issuing make install) I had to remove Cookie.py by hand.
-- if (shakespeare) { the_problem = (2 * b) || !(2 * b); }
"SP" == Simone Piunno <pioppo@ferrara.linux.it> writes:
SP> I've just upgraded from 2.1a3(CVS) to 2.1a4(CVS) and the same
SP> problem occurred (even re-issuing make install) I had to
SP> remove Cookie.py by hand.I was able to reproduce the problem when upgrading from 2.1a2 to current cvs. It was an import problem which is now fixed now in CVS.
-Barry
participants (4)
-
barry＠zope.com -
Marc MERLIN -
Marc MERLIN -
Simone Piunno