July 2014 - macports-tickets - lists.macosforge.org

[MacPorts] #43704: unify the use of +threads as a variant name
by MacPorts 03 Jul '14

03 Jul '14

#43704: unify the use of +threads as a variant name -------------------------+------------------------------------------------- Reporter: mojca@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: boost, cherokee, gauche, hdf, raxml -------------------------+------------------------------------------------- From #43593: would it make sense to unify the variant names used across different ports? Here are some variant names from different ports: {{{ boost: variant no_single description {Disable building single- threaded libraries} gauche: variant no_threads { configure.args-delete --enable- threads=pthreads } raxml: variant pthreads conflicts hybrid description {Pthreads implementation} cherokee: variant no_pthread description {Disable threading support} sbcl: variant threads description {Enable multi-threaded runtime using the Mach pthreads interface.} tcl: variant threads description {add multithreading support} yap: variant threads abinit: variant threads description {Build with support for multi- thread support (openMP)} openmpi: variant threads description {enable threads for MPI applications} wannier90: variant threads description {Build with threaded ATLAS} hdf5: variant threadsafe description {Enable threadsafety (experimental, fails unit-tests)} }}} If this doesn't apply to your port (that is: if the keyword `+threads` misses the point – I'm not sure if `+threads` and `+threadsafe` have "compatible" meanings for example), please say so and remove your port from the list of affected ports. But variants like `+no_threads` should certainly be inverted. -- Ticket URL: <https://trac.macports.org/ticket/43704> MacPorts <http://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #43638: py27-virtualenvwrapper: Does not use virtualenv with appropriate suffix
by MacPorts 03 Jul '14

03 Jul '14

#43638: py27-virtualenvwrapper: Does not use virtualenv with appropriate suffix ------------------------------------------+-------------------------------- Reporter: audvare@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: virtualenv virtualenvwrapper | Port: ------------------------------------------+-------------------------------- {{{ virtualenvwrapper.sh-2.7 }}} is installed and can be sourced but it does not seem to want to use {{{ virtualenv-2.7 }}} but instead wants to use {{{ virtualenv }}} (no suffix). Maybe this is hard-coded. It may be unnecessary to suffix {{{ virtualenvwrapper.sh }}} with a version for these reasons: - It is inconsistent to not have {{{ mkvirtualenv-2.7 }}}, {{{ rmvirtualenv-2.7 }}} as commands - {{{ virtualenvwrapper }}} is made for all relevant versions of Python (although I have no idea if it is a separate package per version, especially 2 vs 3) - {{{ mkvirtualenv }}} accepts a {{{-p}}} argument for the path of which Python implementation to use: {{{mkvirtualenv -p /usr/bin/python some- name}}} (if you really wanted to) - If {{{virtualenvwrapper.sh}}} is not suffixed, it means shell configurations (bashrc) that are made to be compatible with many OS's do not need a special clause for the MacPorts version The 'fix' to {{{virtualenvwrapper.sh-2.7}}}'s {{{mkvirtualenv}}} is to use symlinks to virtualenv and relevant applications like pip. I have a script attached that creates such symlinks assuming that the version desired is 2.7. I am currently running it every so often with launchd or manually. -- Ticket URL: <https://trac.macports.org/ticket/43638> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #38421: BeautifulSoup version collision?
by MacPorts 03 Jul '14

03 Jul '14

#38421: BeautifulSoup version collision? ----------------------------+---------------------------------------- Reporter: jens.troeger@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: Pyhon | Port: py-lxml, py-beautifulsoup4 ----------------------------+---------------------------------------- I am not sure if this is an actual issue, or my fault of installing packages incorrectly. Although there's nothing wrong with the Port itself. First, I installed py-beautifulsoup4 in its current version of 4.1.1, without the +lxml variant. Worked just fine and I could run scripts against that drop. Then, some time later, I installed py-lxml 2.3.2 and suddenly my scripts broke without me having touched them. My suspicion now is that lxml brings its own drop of BeautifulSoup with it, based on this file: /opt/local/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2 /site-packages/beautifulsoup4-4.1.3-py3.2.egg-info/PKG-INFO The official MacPorts bs4 is still at 4.1.1. There seems to be some inconsistency here? Shouldn't installing lxml at least trigger bs4 to be rebuilt with the +lxml variant, or remove bs4 from the system, or shouldn't both port files be at the same version? Something is off, I would think. Cheers! -- Ticket URL: <https://trac.macports.org/ticket/38421> MacPorts <http://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #36269: py27-httplib2 fails to upgrade
by MacPorts 03 Jul '14

03 Jul '14

#36269: py27-httplib2 fails to upgrade ------------------------------+-------------------------------- Reporter: david.w.watson@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: py27-httplib2 ------------------------------+-------------------------------- Permission error - see log -- Ticket URL: <https://trac.macports.org/ticket/36269> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #40946: fortrancl, ImageMagick, and xapian-core missing from web site's port database
by MacPorts 03 Jul '14

03 Jul '14

#40946: fortrancl, ImageMagick, and xapian-core missing from web site's port database ----------------------------+------------------------- Reporter: ryandesign@… | Owner: wsiegrist@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Keywords: | Port: ----------------------------+------------------------- The web site's port database is missing [https://www.macports.org/ports.php?by=name&substr=fortrancl fortrancl], [https://www.macports.org/ports.php?by=name&substr=ImageMagick ImageMagick], and [https://www.macports.org/ports.php?by=name&substr =xapian-core xapian-core] — the three ports which set the new `destroot.delete_la_files` property which was added in MacPorts 2.2.0. Is the server that generates the portindex that gets imported into the database not updated to MacPorts 2.2? The 2.2.1 release is being prepared today, so the server could be updated to that version. -- Ticket URL: <https://trac.macports.org/ticket/40946> MacPorts <http://www.macports.org/> Ports system for OS X

1 14

[MacPorts] #42993: proctools staging failure
by MacPorts 03 Jul '14

03 Jul '14

#42993: proctools staging failure ------------------------+-------------------------------- Reporter: rharwood@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: | Port: proctools ------------------------+-------------------------------- In a non-root context on 10.6.8: {{{ robbie@osxserver:~$ port install proctools ---> Computing dependencies for proctools ---> Fetching distfiles for proctools ---> Verifying checksums for proctools ---> Extracting proctools ---> Applying patches to proctools ---> Configuring proctools ---> Building proctools ---> Staging proctools into destroot Error: org.macports.destroot for port proctools returned: command execution failed Please see the log file for port proctools for details: /Network/Servers/osxserver.b-aassoc.edu/Volumes/ServerDrive/NetUsers/robbie/var/macports/logs/_Volume s_ServerDrive_NetUsers_robbie_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_proctools/proctools/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port proctools failed }}} main.log is attached. -- Ticket URL: <https://trac.macports.org/ticket/42993> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #42202: py*cython multiple upstream versions of Cython-9.20.tar.gz
by MacPorts 03 Jul '14

03 Jul '14

#42202: py*cython multiple upstream versions of Cython-9.20.tar.gz ----------------------------+-------------------------------- Reporter: gnwiii@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: upstream snafu | Port: py-cython ----------------------------+-------------------------------- The version of Cython-0.20.tar.gz at cython.org does not agree with the Portfile checksums: {{{ ---> Fetching distfiles for py27-cython ---> Attempting to fetch Cython-0.20.tar.gz from http://www.cython.org/release/ ---> Verifying checksums for py27-cython Error: Checksum (rmd160) mismatch for Cython-0.20.tar.gz Error: Checksum (sha256) mismatch for Cython-0.20.tar.gz Error: org.macports.checksum for port py27-cython returned: Unable to verify file checksums }}} The update works using the (larger) version of Cython-0.20.tar.gz from pypi.python.org. Comparing the contents of the two archives reveals that the larger archive (the one that matches the Portfile) contains some extra files: {{{ $ diff -bw *.list | less 33a34 > Cython-0.20/Cython/Compiler/Code.c 40a42 > Cython-0.20/Cython/Compiler/FlowControl.c 45a48 > Cython-0.20/Cython/Compiler/Lexicon.c 55a59 > Cython-0.20/Cython/Compiler/Parsing.c 59a64 > Cython-0.20/Cython/Compiler/Scanning.c 80a86 > Cython-0.20/Cython/Compiler/Visitor.c 214a221 > Cython-0.20/Cython/Plex/Actions.c 221a229 > Cython-0.20/Cython/Plex/Scanners.c 228a237 > Cython-0.20/Cython/Runtime/refnanny.c 234a244 > Cython-0.20/Cython/Tempita/_tempita.c (END) }}} -- Ticket URL: <https://trac.macports.org/ticket/42202> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #39575: py-eventlet: update to 0.12.1
by MacPorts 03 Jul '14

03 Jul '14

#39575: py-eventlet: update to 0.12.1 --------------------+------------------------- Reporter: jmr@… | Owner: akitada@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: py-eventlet --------------------+------------------------- Released 2013-01-26: https://pypi.python.org/pypi/eventlet -- Ticket URL: <https://trac.macports.org/ticket/39575> MacPorts <http://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #39558: py-decoratortools: update to 1.8
by MacPorts 03 Jul '14

03 Jul '14

#39558: py-decoratortools: update to 1.8 --------------------+------------------------------- Reporter: jmr@… | Owner: akitada@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: py-decoratortools --------------------+------------------------------- https://pypi.python.org/pypi/DecoratorTools -- Ticket URL: <https://trac.macports.org/ticket/39558> MacPorts <http://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #39216: py-ipython: include offline copy of MathJax
by MacPorts 03 Jul '14

03 Jul '14

#39216: py-ipython: include offline copy of MathJax -------------------------+------------------------ Reporter: aronnax@… | Owner: akitada Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: py-ipython -------------------------+------------------------ The IPython Notebook offers an option to install an offline copy of MathJax. This is really helpful for using the IPython Notebook without internet access. The installation instructions say that you do this by running the following Python snippet: {{{ from IPython.external.mathjax import install_mathjax install_mathjax() }}} However, this requires write access to the {{{site-packages}}} directory. As such, it would be handy if this was offered as a port variant, {{{+mathjax}}}. I noticed another ticket, #39197, that has a dependency on MathJax. Perhaps a MathJax port would be in order here? -- Ticket URL: <https://trac.macports.org/ticket/39216> MacPorts <http://www.macports.org/> Ports system for OS X

1 9