#51417: mailman @2.1.22_0: ImportError: cannot import name C_ ----------------------+------------------- Reporter: gotow@… | Owner: mps@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: mailman | ----------------------+------------------- Changes (by ryandesign@…): * owner: macports-tickets@… => mps@… * port: => mailman Old description:

I have tried to update mailman from 2.1.20_0 to 2.1.22_0, and got an error message as follows.

The current version of mailman on my system is 2.1.20_0, and it seems to work fine. The version of python is 2.7.11_2.

$ sudo port clean mailman Password: ---> Cleaning mailman $ sudo port upgrade mailman ---> Computing dependencies for mailman ---> Fetching archive for mailman ---> Attempting to fetch mailman-2.1.22_0.darwin_12.x86_64.tbz2 from http://sea.us.packages.macports.org/macports/packages/mailman ---> Attempting to fetch mailman-2.1.22_0.darwin_12.x86_64.tbz2 from https://packages.macports.org/mailman ---> Attempting to fetch mailman-2.1.22_0.darwin_12.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/mailman [ ] 0.0 % speed: 0 B/s ---> Fetching distfiles for mailman ---> Verifying checksums for mailman ---> Extracting mailman ---> Applying patches to mailman ---> Configuring mailman ---> Building mailman ---> Staging mailman into destroot Error: org.macports.destroot for port mailman returned: command execution failed Please see the log file for port mailman for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_mail_mailman/mailman/main.log Error: Unable to upgrade port: 1 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets

New description: I have tried to update mailman from 2.1.20_0 to 2.1.22_0, and got an error message as follows. The current version of mailman on my system is 2.1.20_0, and it seems to work fine. The version of python is 2.7.11_2. {{{ $ sudo port clean mailman Password: ---> Cleaning mailman $ sudo port upgrade mailman ---> Computing dependencies for mailman ---> Fetching archive for mailman ---> Attempting to fetch mailman-2.1.22_0.darwin_12.x86_64.tbz2 from http://sea.us.packages.macports.org/macports/packages/mailman ---> Attempting to fetch mailman-2.1.22_0.darwin_12.x86_64.tbz2 from https://packages.macports.org/mailman ---> Attempting to fetch mailman-2.1.22_0.darwin_12.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/mailman [ ] 0.0 % speed: 0 B/s ---> Fetching distfiles for mailman ---> Verifying checksums for mailman ---> Extracting mailman ---> Applying patches to mailman ---> Configuring mailman ---> Building mailman ---> Staging mailman into destroot Error: org.macports.destroot for port mailman returned: command execution failed Please see the log file for port mailman for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_mail_mailman/mailman/main.log Error: Unable to upgrade port: 1 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets }}} -- Comment: Relevant error from log appears to be: {{{ :info:destroot Traceback (most recent call last): :info:destroot File "./bin/check_perms", line 48, in <module> :info:destroot from Mailman.i18n import C_ :info:destroot ImportError: cannot import name C_ }}} -- Ticket URL: <https://trac.macports.org/ticket/51417#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X

#51417: mailman @2.1.22_0: ImportError: cannot import name C_ ----------------------+------------------- Reporter: gotow@… | Owner: mps@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: mailman | ----------------------+------------------- Comment (by mps@…): I'm stumped: I just cleanly installed mailman in my Mountain Lion VM w/o any problems. Is there anything non-standard, i.e. are you using MacPorts clang or some such thing? -- Ticket URL: <https://trac.macports.org/ticket/51417#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X

#51417: mailman @2.1.22_0: ImportError: cannot import name C_ ----------------------+------------------- Reporter: gotow@… | Owner: mps@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: mailman | ----------------------+------------------- Comment (by macports-bug-report-yf@…): It seems that ./bin/check_perms script tries to import module function Mailman.i18n from previously installed version of Mailman module, in mailman 2.1.20. (C_ function has been introduced since 2.1.21 for i18n improvement of command line tools.) Please check which module is imported on checkperm processing. (I'm sorry but I don't have MacPorts environment, so this is my mere conjecture....) -- Ticket URL: <https://trac.macports.org/ticket/51417#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X

#51417: mailman @2.1.22_0: ImportError: cannot import name C_ ----------------------+------------------- Reporter: gotow@… | Owner: mps@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: mailman | ----------------------+------------------- Comment (by macports-bug-report-yf@…): To reproduce the problem, (1) Install mailman 2.1.20 or earlier in the same path the MacPorts will install mailman-2.1.22 or (2) Place empty file as Mailman/i18n.py to the path the mailman-2.1.22 MacPorts will install Mailman/i18n.py module to. then try to install mailman-2.1.22 via MacPorts. To fix it, (A) Abandon to run check_perms before install or (B) For destroot phase, create special version of check_perms which refers modules from under ${destroot} precedingly -- Ticket URL: <https://trac.macports.org/ticket/51417#comment:8> MacPorts <https://www.macports.org/> Ports system for OS X

#51417: mailman @2.1.22_0: ImportError: cannot import name C_ ----------------------+------------------- Reporter: gotow@… | Owner: mps@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: mailman | ----------------------+------------------- Comment (by gotow@…): I tried to upgrade mailman-2.1.22_0 with new ports r149540 from mailman-2.1.20_0, and got an error message as follows. I confirmed that new ports r149540 is in /opt/local/var/macports/sources/rsync.macports.org/relese/tarballs/ports/mail.man/Portfile. The current version of Python on my system is 2.7.12_1. I attached the main.log for your reference. I would appreciate if you could give any comments or advices. $ sudo port clean --all mailman[[BR]] Password:[[BR]] ---> Cleaning mailman[[BR]] dependencies for mailman[[BR]] ---> Fetching archive for mailman[[BR]] ---> Attempting to fetch mailman-2.1.22_0.darwin_12.x86_64.tbz2 from https://packages.macports.org/mailman ---> Attempting to fetch mailman-2.1.22_0.darwin_12.x86_64.tbz2 from http://jog.id.packages.macports.org/macports/packages/mailman ---> Attempting to fetch mailman-2.1.22_0.darwin_12.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/mailman [ ] 0.0 % speed: 0 B/s ---> Fetching distfiles for mailman ---> Attempting to fetch mailman-2.1.22.tgz from https://distfiles.macports.org/mailman [[BR]] ---> Verifying checksums for mailman[[BR]] ---> Extracting mailman[[BR]] ---> Applying patches to mailman[[BR]] ---> Configuring mailman[[BR]] ---> Building mailman[[BR]] ---> Staging mailman into destroot[[BR]] Error: org.macports.destroot for port mailman returned: command execution failed Please see the log file for port mailman for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_mail_mailman/mailman/main.log Error: Unable to upgrade port: 1 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets -- Ticket URL: <https://trac.macports.org/ticket/51417#comment:10> MacPorts <https://www.macports.org/> Ports system for OS X

#51417: mailman @2.1.22_0: ImportError: cannot import name C_ ----------------------+------------------- Reporter: gotow@… | Owner: mps@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: mailman | ----------------------+------------------- Comment (by macports-bug-report-yf@…): Replying to [comment:11 mps@…]:

I've thrown the towel on {{{check_perms}}}: r149823

IMO, there is no mean to run check_perms on post-destroot phase, because (1) It checks files/dirs permission of installed environment, including /etc, working directories, archive directories, etc., with absolute paths (i.e. not checking under staging root dir).[[BR]] (2) Without option -f bin/check_perms do nothing but printinting bogus permissions or groupownership, not correcting them actually. (exit status is always 0 except on invalid arguments or Python exception). So, I think the change of r149823 is appropriate for this problem. -- Ticket URL: <https://trac.macports.org/ticket/51417#comment:12> MacPorts <https://www.macports.org/> Ports system for OS X

#51417: mailman @2.1.22_0: ImportError: cannot import name C_ ----------------------+------------------- Reporter: gotow@… | Owner: mps@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: mailman | ----------------------+------------------- Comment (by gotow@…): Finally mailman has been upgraded to 2.1.22_0 from 2.1.20_0 with port r149823 on OSX 10.8.5. I made no further modification. After upgrade I ran "check_perms -f" command, and got a reply of "No problems found". The new mailman 2.1.22_0 appears to be working properly so far. Thank everyone who discussed the problem and provided the revised port r149823. -- Ticket URL: <https://trac.macports.org/ticket/51417#comment:14> MacPorts <https://www.macports.org/> Ports system for OS X