Summary: | net-mail/mailman ebuild depends on python 2 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jack Eids_no_google_me_ness <jack> |
Component: | New packages | Assignee: | Hanno Böck <hanno> |
Status: | RESOLVED DUPLICATE | ||
Severity: | minor | CC: | daniel, jdavid.ibp, net-mail+disabled |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
mailman ebuild that works when Python default is 3
Updated ebuild for 2.1.14 version (based on /usr/portage/net-mail/mailman files) |
Description
Jack Eids_no_google_me_ness
2011-07-07 01:13:48 UTC
I get it not starting with both 2.7 & 3.1 You have not stipulated which version of mailman. The one I have emerged has no exes in /bin. they are all in /usr/lib64/mailman/bin/ I have the same problem. I have rented a server with a bare Gentoo pre-installed, it has Python 3 as the default. When emerging mailman 2.1.14 I get many syntax errors, though it emerges anyway. Then : mailman@foobar ~ $ ./bin/mailmanctl -s start File "./bin/mailmanctl", line 149 except (IOError, ValueError), e: ^ SyntaxError: invalid syntax Created attachment 310793 [details] mailman ebuild that works when Python default is 3 Available in this overlay : https://github.com/hforge/overlay I confirm this bug to be happening: mailman@ethereal ~ $ bin/mailmanctl -s start File "bin/mailmanctl", line 149 except (IOError, ValueError), e: ^ SyntaxError: invalid syntax mailman@ethereal ~ $ logout ethereal layman # eselect python list Available Python interpreters: [1] python2.7 [2] python3.2 * ethereal layman # profile: [9] hardened/linux/amd64 * Created attachment 315565 [details]
Updated ebuild for 2.1.14 version (based on /usr/portage/net-mail/mailman files)
Here is an updated ebuild. I've just installed it here naming it as staging/mailman-2.1.14, copied the needed files from /usr/portage/net-mail/mailman/files (all files pointed by ${FILESDIR} in the ebuild file) and voila, it works!. No more syntax errors out of the blue.
*** This bug has been marked as a duplicate of bug 315335 *** |