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

[MacPorts] #48422: Xcode_7_beta_4 - Error: The installed version of Xcode (2.0orlower) is too old to use ...
by MacPorts 24 Jul '15

24 Jul '15

#48422: Xcode_7_beta_4 - Error: The installed version of Xcode (2.0orlower) is too old to use ... --------------------------------------+-------------------------------- Reporter: t.mehlhart@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Not set | Milestone: Component: ports | Version: 2.3.3 Keywords: Xcode_7_beta_4 too old | Port: any i tried --------------------------------------+-------------------------------- With Xcode_7_beta_4 installed, macports does not compile any package The following Error occurs (Example: port install smartmontools, but any other I tried did the same) Error: The installed version of Xcode (2.0orlower) is too old to use on the installed OS version. Version 4.6.3 or later is recommended on Mac OS X 10.8. -- Ticket URL: <https://trac.macports.org/ticket/48422> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #48427: Maxima 5.34.1 No gcl variant available
by MacPorts 24 Jul '15

24 Jul '15

#48427: Maxima 5.34.1 No gcl variant available -------------------------+-------------------------------- Reporter: ephemeris@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: maxima -------------------------+-------------------------------- Port will not build Maxima to use gcl. Only lisp variants listed for building Maxima are sbcl and abcl. Maxima can use several lisp implementations which include MacPorts supported gcl and clisp. I am using OSX 10.10.3 and xcode 6.3.1 -- Ticket URL: <https://trac.macports.org/ticket/48427> MacPorts <https://www.macports.org/> Ports system for OS X

1 1

Re: [MacPorts] #42220: py-netcdf4 @1.0.4_1: build failure when using ccache
by MacPorts 23 Jul '15

23 Jul '15

#42220: py-netcdf4 @1.0.4_1: build failure when using ccache -------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: py-netcdf4 | -------------------------+-------------------------------- Comment (by zanderpower@…): P.S. Why does py27-netcdf4 apparently insist on using ccache? Could there be a permissions problem on the .ccache directory for this particular port? -- Ticket URL: <https://trac.macports.org/ticket/42220#comment:8> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

Re: [MacPorts] #42220: py-netcdf4 @1.0.4_1: build failure when using ccache
by MacPorts 23 Jul '15

23 Jul '15

#42220: py-netcdf4 @1.0.4_1: build failure when using ccache -------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: py-netcdf4 | -------------------------+-------------------------------- Comment (by zanderpower@…): I see that this is an old ticket, but I too am getting the same error when trying to upgrade py27-netcdf4. I have tried deactivating ccache, and even uninstalling ccache (of course along with appropriately modifying the settings on macports.conf and the PATH variable in my .bash_profile. All to no avail. The first--and the only previous--install of py27-netcdf4 worked okay, and I do not remember having to mess around with ccache, which was almost certainly active at the time. Now no matter what I have tried thus far gives me the same build error: {{{ :info:build {ccache /mp2/local/bin/gcc-mp-4.7} -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -arch ppc -I/mp2/local/include -I/mp2/local/include -I/mp2/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/numpy/core/include -I/mp2/local/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c netCDF4/_netCDF4.c -o build/temp.macosx-10.5-ppc-2.7/netCDF4/_netCDF4.o :info:build unable to execute '{ccache': No such file or directory :info:build error: command '{ccache' failed with exit status 1 }}} Note: I have also tried deactivating the old py27-netcdf4 and building from scratch. Still the same error. Weird! Any ideas? I am attaching the build log. -- Ticket URL: <https://trac.macports.org/ticket/42220#comment:7> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #46183: okular @4.13.3_0 Cannot open files directly from the command line
by MacPorts 23 Jul '15

23 Jul '15

#46183: okular @4.13.3_0 Cannot open files directly from the command line ---------------------------+-------------------------------- Reporter: dsfrancis03@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: Okular ---------------------------+-------------------------------- Hello, I have a Late 2008 15" Macbook Pro. I recently installed Yosemite (clean install) on my Macbook and also installed kde4-kile through macports 2.3.3. The installations of all the related ports seemed fine except for two ports, okular @4.13.3_0 and kde4-kile @2.1.3_1. In this post, I'd like to discuss my problem regarding okular. If I open okular first and then open a file from File - Open menu, then okular opens the file with no problem. However, if I try to open a file using okular from kile, or if I try to open a file using okular from the command line (e.g, '/Applications/MacPorts/KDE4/okular.app/Contents/MacOS/okular abc.pdf'), then okular fails to open the file. Here is the error message: {{{ okular(609)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: okular(609)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: okular(609)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: okular(609)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: okular(609)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: KCrash: Application 'okular' crashing... KCrash: Attempting to start directly KCrash failed to exec(), errno = 2 }}} And, here are more about okular: {{{ $ /Applications/MacPorts/KDE4/okular.app/Contents/MacOS/okular --version Qt: 4.8.6 KDE Development Platform: 4.13.3 Okular: 0.19.3 }}} Please help me solve this issue and let me know if more information is needed. I have another issue regarding kile, which doesn't open a file by drag- and-drop, and I'll probably open a new ticket later. But, before I open a new ticket, if anyone is familiar with this issue, please advise. -- Ticket URL: <https://trac.macports.org/ticket/46183> MacPorts <https://www.macports.org/> Ports system for OS X

1 10

[MacPorts] #48421: openmpi @1.7.5 update to version 1.8.7
by MacPorts 22 Jul '15

22 Jul '15

#48421: openmpi @1.7.5 update to version 1.8.7 --------------------------------------+-------------------------------- Reporter: giovanni.cabass@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: "version", "late", "new" | Port: openmpi --------------------------------------+-------------------------------- As from http://www.open-mpi.org/software/ompi/v1.8/, the most recent stable version of openmpi is 1.8.7 -- Ticket URL: <https://trac.macports.org/ticket/48421> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #48322: Update py-powerline to version 2.2 (current port is broken!)
by MacPorts 22 Jul '15

22 Jul '15

#48322: Update py-powerline to version 2.2 (current port is broken!) --------------------------+-------------------------------- Reporter: mdeaudelin@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: py-powerline --------------------------+-------------------------------- The current port of py-powerline is outdated and fails to install with a checksum error. Proposed fix: - Change the source GitHub repository from Lokaltog/powerline to powerline/powerline (where all development is now done). - Upgrade to the latest stable version (2.2). -- Ticket URL: <https://trac.macports.org/ticket/48322> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #47980: mu: mu 0.9.12 produce 0.9.11 while running mu --version
by MacPorts 22 Jul '15

22 Jul '15

#47980: mu: mu 0.9.12 produce 0.9.11 while running mu --version -------------------------+-------------------- Reporter: chunyang@… | Owner: sean@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: haspatch | Port: mu -------------------------+-------------------- I guess the author of mu forget to update version number before tagging. -- Ticket URL: <https://trac.macports.org/ticket/47980> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #47681: `hg status' crashes on newly created repository
by MacPorts 22 Jul '15

22 Jul '15

#47681: `hg status' crashes on newly created repository --------------------------+-------------------------------- Reporter: veedeehjay@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: mercurial --------------------------+-------------------------------- this happens with mercurial(a)3.3.3 under OSX 10.10.3. the following should reproducibly crash if the `hggit'` is requested in `~/.hgrc` {{{ mkdir new cd new hg init hg status }}} with the message: {{{ ** unknown exception encountered, please report by visiting ** http://mercurial.selenic.com/wiki/BugTracker ** Python 2.7.9 (default, Dec 13 2014, 15:13:49) [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.56)] ** Mercurial Distributed SCM (version 3.3.3) ** Extensions loaded: convert, rebase, fetch, graphlog, extdiff, hgk, color, hgsubversion, hggit, churn, pager, strip, mq, transplant Traceback (most recent call last): File "/opt/local/bin/hg", line 43, in <module> ... LOTS MORE ... File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/mercurial/scmutil.py", line 1105, in finddirs pos = path.rfind('/') AttributeError: 'tuple' object has no attribute 'rfind' }}} two observations: 1. without the `hggit` extension the problem goes away here 2. using the `mercurial-devel` instead of the`mercurial` port also makes the problem go away even in the presence of `hggit`. whether it's a problem of mercurial or the `py-hggit` port I canot say... -- Ticket URL: <https://trac.macports.org/ticket/47681> MacPorts <https://www.macports.org/> Ports system for OS X

1 8

[MacPorts] #47604: watchman builds with datatype mismatch in clang
by MacPorts 22 Jul '15

22 Jul '15

#47604: watchman builds with datatype mismatch in clang -----------------------+-------------------------------- Reporter: siulung@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: -----------------------+-------------------------------- $ sudo port install watchman ---> Computing dependencies for watchman ---> Fetching archive for watchman ---> Attempting to fetch watchman-3.1_0+universal.darwin_14.i386-x86_64.tbz2 from http://packages.macports.org/watchman [...] Error: org.macports.build for port watchman returned: command execution failed Please see the log file for port watchman for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_watchman/watchman/main.log :info:build watcher/fsevents.c:133:67: error: values of type 'FSEventStreamEventFlags' should not be used as format arguments; add an explicit cast to 'unsigned int' instead [-Werror,-Wformat] :info:build w_log(W_LOG_DBG, "fse_thread: add %s %" PRIx32 "\n", pathbuf, evt->flags); :info:build ~~~ ^~~~~~~~~~ :info:build (unsigned int) :info:build 1 error generated. -- Ticket URL: <https://trac.macports.org/ticket/47604> MacPorts <https://www.macports.org/> Ports system for OS X

1 5