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

[MacPorts] #44143: Do You Want To Avoid Skin Irritation
by MacPorts 26 Jun '14

26 Jun '14

#44143: Do You Want To Avoid Skin Irritation ---------------------------+-------------------------------- Reporter: joebuster66@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.0 Keywords: | Port: ---------------------------+-------------------------------- Herbal injure want products use born oils that are institute within a tracheophyte of seeds or nuts, much as grapevine humor oil and citrus oil. These ingredients incline to unclog pores, as recovered as comfortableness the appearing of blemishes and dry wound. There are lashings of recipes for herbal pare aid that you can use at institution, [http://brillartupiel.com/ BellaVeì]which are created by production up a few unprocessed products from the grocery keep, eudaemonia content marketplace, as fountainhead as herbal injure mind stores and websites. To create chromatic oil for the rind, you present pauperization two cups of chromatic flowers, 2 sprigs of rosemary, 1 portion of chromatic flavor, as considerably as 1 cups of olive or grapevine participant oil. Using a mortar or keen board, you can create the herbal strip care variety by blow the chromatic, rosemary and orange season unitedly. Succeeding, you bundle the herbs into a 2-cup power jar and add the oil.Initiate and kindle the ingredients together before leaving the jar in a sunny window for two weeks. Raise the jar at slightest erstwhile a day during these two weeks. After the case is up, you testament poverty to exertion the herbal rind mending creation and have it refrigerated when not in use. http://brillartupiel.com/ -- Ticket URL: <https://trac.macports.org/ticket/44143> MacPorts <http://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #44117: rsync-3.1.1 : Diffs to bring port up to 3.1.1
by MacPorts 26 Jun '14

26 Jun '14

#44117: rsync-3.1.1 : Diffs to bring port up to 3.1.1 ----------------------+-------------------------------- Reporter: jimjag@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.0 Keywords: rsync | Port: rsync ----------------------+-------------------------------- -- Ticket URL: <https://trac.macports.org/ticket/44117> MacPorts <http://www.macports.org/> Ports system for OS X

1 15

Re: [MacPorts] #13606: New cross/x86_64-pc-mingw32-binutils port
by MacPorts 26 Jun '14

26 Jun '14

#13606: New cross/x86_64-pc-mingw32-binutils port -----------------------------+--------------------------------------------- Reporter: jljusten | Owner: macports-tickets@… macports@… | Status: new Type: submission | Milestone: Priority: Normal | Version: 1.5.2 Component: ports | Keywords: cross mingw x86_64 x64 binutils Resolution: | Port: | -----------------------------+--------------------------------------------- Comment (by mojca@…): There is also #40174 (which I modified before I have found/remembered this ticket). One of the two tickets should become a duplicate. -- Ticket URL: <https://trac.macports.org/ticket/13606#comment:8> MacPorts <http://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #43586: py27-pyobjc @2.5.1: build fails with py27-setuptools @3.5.1
by MacPorts 26 Jun '14

26 Jun '14

#43586: py27-pyobjc @2.5.1: build fails with py27-setuptools @3.5.1 -----------------------------+-------------------------------- Reporter: md14-macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: | Port: py-pyobjc -----------------------------+-------------------------------- Building py27-pyobjc @2.5.1 fails after I upgraded to py27-setuptools @3.5.1: {{{ $ port installed py27-setuptools The following ports are currently installed: py27-setuptools @3.5.1_0 (active) $ sudo port -vs install py27-pyobjc ---> Computing dependencies for py27-pyobjc. ---> Fetching distfiles for py27-pyobjc ... copying build/lib.macosx-10.6-x86_64-2.7/PyObjCTest/testclassandinst.so -> PyObjCTest copying build/lib.macosx-10.6-x86_64-2.7/PyObjCTest/testoutputinitializer.so -> PyObjCTest copying build/lib.macosx-10.6-x86_64-2.7/PyObjCTest/voidpointer.so -> PyObjCTest running install_lib Traceback (most recent call last): File "setup.py", line 574, in <module> zip_safe = False, File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/core.py", line 152, in setup dist.run_commands() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/dist.py", line 953, in run_commands self.run_command(cmd) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/dist.py", line 972, in run_command cmd_obj.run() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/setuptools/command/install.py", line 59, in run return orig.install.run(self) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/command/install.py", line 575, in run self.run_command(cmd_name) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/cmd.py", line 326, in run_command self.distribution.run_command(command) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/dist.py", line 972, in run_command cmd_obj.run() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/setuptools/command/install_lib.py", line 9, in run outfiles = self.install() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/command/install_lib.py", line 115, in install outfiles = self.copy_tree(self.build_dir, self.install_dir) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/setuptools/command/install_lib.py", line 34, in copy_tree exclude = self.get_exclusions() File "setup.py", line 271, in get_exclusions for fn in install_lib._install_lib.get_outputs(self): AttributeError: 'module' object has no attribute '_install_lib' Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_python_py-pyobjc/py27-pyobjc/work/pyobjc- core-2.5.1" && /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 setup.py --no-user-cfg install --prefix=/opt/local/Library/Frameworks/Python.framework/Versions/2.7 --root=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_python_py-pyobjc/py27-pyobjc/work/destroot Exit code: 1 Error: org.macports.destroot for port py27-pyobjc returned: command execution failed Warning: targets not executed for py27-pyobjc: org.macports.activate org.macports.destroot org.macports.install Please see the log file for port py27-pyobjc for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_python_py-pyobjc/py27-pyobjc/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port py27-pyobjc failed }}} -- Ticket URL: <https://trac.macports.org/ticket/43586> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #31578: i386-mingw32-gcc
by MacPorts 25 Jun '14

25 Jun '14

#31578: i386-mingw32-gcc --------------------------------------------+------------------------------- Reporter: mojca.miklavec.lists@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: i386-mingw32-gcc --------------------------------------------+------------------------------- The port ships gcc 3.4.5 from 2006, almost 6 years old. I would like to request updating to a more recent version. Sources for 4.6.1-2 are available on sourceforge at the moment. https://sourceforge.net/projects/mingw/files/MinGW/BaseSystem/GCC/Version4/… -- Ticket URL: <https://trac.macports.org/ticket/31578> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[MacPorts] #40174: upgrade mingw and add win64 cross-compiler
by MacPorts 25 Jun '14

25 Jun '14

#40174: upgrade mingw and add win64 cross-compiler ----------------------------+-------------------------------- Reporter: sam.halliday@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: | Port: ----------------------------+-------------------------------- the MingW cross-compiler for windows is quite old and there is currently no cross-compiler for Windows 64. Packages for both would be fantastic! -- Ticket URL: <https://trac.macports.org/ticket/40174> MacPorts <http://www.macports.org/> Ports system for OS X

1 6

[MacPorts] #36748: ext2fuse: mounted filesystem not readable (PPC or 32bit issue?)
by MacPorts 25 Jun '14

25 Jun '14

#36748: ext2fuse: mounted filesystem not readable (PPC or 32bit issue?) -----------------------------+-------------------------------- Reporter: michael.klein@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: haspatch | Port: ext2fuse -----------------------------+-------------------------------- * ext2fuse 0.8.1 * fuse4x 0.9.2 File systems mount ok on 10.5.8/PPC, but any operation on the mounted file system results in an Input/output error. {{{ $ pkg-config fuse --cflags -D_FILE_OFFSET_BITS=64 -D_DARWIN_USE_64_BIT_INODE -I/opt/local/include/fuse }}} After rebuilding ext2fuse with -D_DARWIN_USE_64_BIT_INODE everything seems to work fine -- Ticket URL: <https://trac.macports.org/ticket/36748> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 8

[MacPorts] #44060: Erlang binaries missing from the PATH environment
by MacPorts 25 Jun '14

25 Jun '14

#44060: Erlang binaries missing from the PATH environment ------------------------+-------------------------------- Reporter: conradwt@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.0 Keywords: 17.0_1 | Port: erlang ------------------------+-------------------------------- Hi, epmd isn't being added to the PATH environment and not automatically started for the Erlang process. This issue appears to have started with R17.0_1 because I haven't seen this issue in prior releases. -- Ticket URL: <https://trac.macports.org/ticket/44060> MacPorts <http://www.macports.org/> Ports system for OS X

1 6

[MacPorts] #42792: py27-python-daemon @1.5.5: missing dependency
by MacPorts 25 Jun '14

25 Jun '14

#42792: py27-python-daemon @1.5.5: missing dependency -----------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: py-python-daemon -----------------------------+-------------------------------- The port does not declare some dependency. It might be `py-lockfile`, but I after installing, it I still get some error, see below. Note: The port is `nomaintainer`, so I leave CC empty. {{{ In [1]: import daemon.runner --------------------------------------------------------------------------- ImportError Traceback (most recent call last) <ipython-input-1-af5e622233f1> in <module>() ----> 1 import daemon.runner /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/daemon/runner.py in <module>() 23 import errno 24 ---> 25 import pidlockfile 26 27 from daemon import DaemonContext /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/daemon/pidlockfile.py in <module>() 17 import errno 18 ---> 19 from lockfile import ( 20 LinkFileLock, 21 AlreadyLocked, LockFailed, ImportError: No module named lockfile }}} With lockfile installed: {{{ In [1]: import daemon.runner --------------------------------------------------------------------------- TypeError Traceback (most recent call last) <ipython-input-1-af5e622233f1> in <module>() ----> 1 import daemon.runner /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/daemon/runner.py in <module>() 23 import errno 24 ---> 25 import pidlockfile 26 27 from daemon import DaemonContext /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/daemon/pidlockfile.py in <module>() 31 32 ---> 33 class PIDLockFile(LinkFileLock, object): 34 """ Lockfile implemented as a Unix PID file. 35 TypeError: Error when calling the metaclass bases function() argument 1 must be code, not str }}} -- Ticket URL: <https://trac.macports.org/ticket/42792> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #16336: Allow multiple ports to satisfy a single dependency
by MacPorts 25 Jun '14

25 Jun '14

#16336: Allow multiple ports to satisfy a single dependency ---------------------------------+------------------------------------------ Reporter: rhwood(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Keywords: | ---------------------------------+------------------------------------------ Currently there is no mechanism to specify that multiple ports may satisfy a single dependency requirement. It would be nice to be able to do so. I can think of two ways this can be done: OR dependencies:: Allow dependencies to be specified in the following fashion:[[BR]]{{{port:able|baker|charlie}}}[[BR]]where the pipe is used to separate one or more ports that may satisfy a single dependency. The first port would be used if none of the ports are installed. There should be no limit to the number of pipes, nor should there be any requirement that any pipes be used (ie, no pipes = no alternate dependencies). This should also wotk with ''bin:'' and ''path:'' type dependencies. "provides" capability in ports:: Use a "provides" key to specify that a port satisfies a particular requirement. Use the name of the port if a provides keyword is not specified. For example, if port '''able-devel''' specifies that it {{{ provides able }}} then port '''able-devel''' would be able satisfy the dependency {{{ port:able }}} in another port, without that other port having to be aware of port '''able-devel''' -- Ticket URL: <http://trac.macports.org/ticket/16336> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 12