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

[MacPorts] #48173: Lion buildbot builder: No space left on device
by MacPorts 11 Aug '16

11 Aug '16

#48173: Lion buildbot builder: No space left on device ----------------------------+--------------------- Reporter: ryandesign@… | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Keywords: | Port: ----------------------------+--------------------- The Lion buildbot builder (tenseven-slave.macports.org) ran out of disk space trying to build gcc6 during this build: https://build.macports.org/builders/buildports-lion-x86_64/builds/29508 {{{ In file included from /opt/local/var/macports/build/_opt_mports_dports_lang_gcc6/libgcc- devel/work/gcc-6-20150621/libstdc++-v3/include/precompiled/stdc++.h:94:0: /opt/local/var/macports/build/_opt_mports_dports_lang_gcc6/libgcc- devel/work/build/x86_64-apple- darwin11/libstdc++-v3/include/valarray:1233:1: error: while writing precompiled header: No space left on device } // namespace ^ /opt/local/var/macports/build/_opt_mports_dports_lang_gcc6/libgcc- devel/work/build/x86_64-apple- darwin11/libstdc++-v3/include/valarray:1233:1: fatal error: can't write PCH file: No space left on device compilation terminated. }}} How much disk space is free? Can we get more? Or can we investigate if there's anything taking up space unnecessarily? I imagine most of the disk space will be taken up by /opt/local/var/macports/software, because the way we have the buildbot builders set up is that all ports remain installed, but deactivated. This means that as more and more ports get added to MacPorts over time, more and more disk space is needed on the builders. I'm not certain how the buildbot builder's disk volumes are set up... I thought a SAN or file share might be involved, but I'm not sure what parts are on that and what parts are on each builder's local disk volumes. Is there a system in place that monitors our servers' disk space? It's important that we resolve low disk space issues before we run out completely, as happened here. -- Ticket URL: <https://trac.macports.org/ticket/48173> MacPorts <https://www.macports.org/> Ports system for OS X

1 9

[MacPorts] #47036: jython installation hardcodes JAVA_HOME such that jython will fail if a user upgrades the Java installation
by MacPorts 08 Aug '16

08 Aug '16

#47036: jython installation hardcodes JAVA_HOME such that jython will fail if a user upgrades the Java installation ---------------------+-------------------------------- Reporter: mtb19@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: jython ---------------------+-------------------------------- = To reproduce = * install an older version of Java (e.g., jdk1.7.0_67) * install jython * upgrade Java (e.g., to jdk1.7.0_75) * remove the older Java version * run `jython` * run `JAVA_HOME="$( /usr/libexec/java_home -v 1.7 )" jython` = Expected = Both `jython` and `JAVA_HOME="$( /usr/libexec/java_home -v 1.7 )" jython` should work. = Actual = Both fail, complaining that (e.g.) `/Library/Java/JavaVirtualMachines/jdk1.7.0_67.jdk/Contents/Home/bin/java` doesn't exist. = Additional Detail = An inspection of `cat $( which jython )` reveals: {{{ ... # This file was generated by the Jython installer # Created on ... JAVA_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_67.jdk/Contents/Home/jre" ... }}} These lines are not present in the [https://svn.code.sf.net/p/jython/svn/tags/Release_2_5_2/jython/src/shell/jy… original source file]. Setting `JAVA_HOME` in this manner: * a) may not be correct for very long; and * b) permanently overrides any external setting This leaves the user with hand-editing `$( which jython )` or reinstalling jython after every Java upgrade to get it to work, neither of which is ideal. -- Ticket URL: <https://trac.macports.org/ticket/47036> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #48145: castxml: add variants for different versions of clang toolchain, use corresponding toolchain for compilation
by MacPorts 03 Aug '16

03 Aug '16

#48145: castxml: add variants for different versions of clang toolchain, use corresponding toolchain for compilation ----------------------+------------------------ Reporter: mmoll@… | Owner: stromnov@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: haspatch | Port: castxml ----------------------+------------------------ castxml needs to be compiled with clang 3.6 or higher. It also needs the full install of llvm that MacPorts provides (Xcode is not complete enough). The attached patch fixes compilation problems on older OSs and adds the option to use clang-3.7. -- Ticket URL: <https://trac.macports.org/ticket/48145> MacPorts <https://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #48123: after installing ngrep, "Could not open /opt/local/lib/libpcap.A.dylib" causes rebuild on every install
by MacPorts 02 Aug '16

02 Aug '16

#48123: after installing ngrep, "Could not open /opt/local/lib/libpcap.A.dylib" causes rebuild on every install -----------------------+-------------------------------- Reporter: audvare@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: -----------------------+-------------------------------- Since installing ngrep, I get this every time I run `port install ...`: {{{ ---> Scanning binaries for linking errors Could not open /opt/local/lib/libpcap.A.dylib: Error opening or reading file (referenced from /opt/local/bin/ngrep) ---> Found 1 broken file(s), matching files to ports ---> Found 1 broken port(s), determining rebuild order ---> Rebuilding in order ngrep @1.45 }}} Looking at the file, it exists and is readable. {{{ lrwxr-xr-x 1 root admin 19 Apr 23 14:28 /opt/local/lib/libpcap.A.dylib -> libpcap.1.7.3.dylib }}} Also, `file` shows appropriate output: {{{ /opt/local/lib/libpcap.1.7.3.dylib: Mach-O 64-bit dynamically linked shared library x86_64 }}} -- Ticket URL: <https://trac.macports.org/ticket/48123> MacPorts <https://www.macports.org/> Ports system for OS X

1 10

[MacPorts] #47965: iTerm2 @2.1_0 upgrade to 2.1.1
by MacPorts 02 Aug '16

02 Aug '16

#47965: iTerm2 @2.1_0 upgrade to 2.1.1 --------------------------+-------------------- Reporter: and.damore@… | Owner: emer@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: haspatch | Port: iterm2 --------------------------+-------------------- Please upgrade port iTerm2 to 2.1.1 in order to fix cursor disappearance when emacs is running in tmux 2.0 session in iTerm2, [https://gitlab.com/gnachman/iterm2/issues/3539 see this bug]. -- Ticket URL: <https://trac.macports.org/ticket/47965> MacPorts <https://www.macports.org/> Ports system for OS X

1 8

[MacPorts] #45918: Update orfeotoolbox port to 4.2.1 version
by MacPorts 29 Jul '16

29 Jul '16

#45918: Update orfeotoolbox port to 4.2.1 version --------------------------------+-------------------------------- Reporter: mickael.savinaud@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.2 Keywords: | Port: --------------------------------+-------------------------------- A new version of OTB and its application is available 4.2.1. Could you please update the port to this new version. -- Ticket URL: <https://trac.macports.org/ticket/45918> MacPorts <https://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #47523: orfeotoolbox @4.0.0 +python27 Configure failure: command execution failed
by MacPorts 29 Jul '16

29 Jul '16

#47523: orfeotoolbox @4.0.0 +python27 Configure failure: command execution failed -------------------------+-------------------------------- Reporter: dgaleazzo@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: -------------------------+-------------------------------- {{{ macbook:~ daniel$ sudo port install orfeotoolbox +python27 ---> Computing dependencies for orfeotoolbox ---> Configuring orfeotoolbox Error: org.macports.configure for port orfeotoolbox returned: configure failure: command execution failed Please see the log file for port orfeotoolbox for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gis_orfeotoolbox/orfeotoolbox/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port orfeotoolbox failed }}} -- Ticket URL: <https://trac.macports.org/ticket/47523> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #46641: ogrinfo fails giving out the availabe formats and misses wfs format
by MacPorts 28 Jul '16

28 Jul '16

#46641: ogrinfo fails giving out the availabe formats and misses wfs format -------------------------------+-------------------------------- Reporter: c.strobl@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: ogrinfo --formats | Port: gdal -------------------------------+-------------------------------- ogrinfo --formats Usage: ogrinfo [--help-general] [-ro] [-q] [-where restricted_where] [-spat xmin ymin xmax ymax] [-geomfield field] [-fid fid] [-sql statement] [-dialect sql_dialect] [-al] [-so] [-fields={YES/NO}] [-geom={YES/NO/SUMMARY}][--formats] datasource_name [layer [layer ...]] FAILURE: Unknown option name '--formats' also the WFS format is missing -- Ticket URL: <https://trac.macports.org/ticket/46641> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #46806: gdal 1.11.1_3 vs. poppler 0.31.0
by MacPorts 28 Jul '16

28 Jul '16

#46806: gdal 1.11.1_3 vs. poppler 0.31.0 ----------------------------+-------------------------------- Reporter: mschamschula@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: gdal ----------------------------+-------------------------------- gdal @1.11.1_3 +poppler (in my case gdal @1.11.1_3+curl+expat+geos+hdf4+hdf5+jasper+lzma+mysql5+netcdf+poppler+sqlite3) fails to build against poppler @0.31.0_0. See attached log file. -- Ticket URL: <https://trac.macports.org/ticket/46806> MacPorts <https://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #46759: qgis library paths should consider additional qt4-mac plugins installation
by MacPorts 28 Jul '16

28 Jul '16

#46759: qgis library paths should consider additional qt4-mac plugins installation ------------------------+-------------------------------- Reporter: geosanak@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: qgis | Port: qgis ------------------------+-------------------------------- When I wanted to use "qt4-mac-sqlite3-plugin" ('QSQLITE' driver) in QGIS Python console,[[BR]] the following was necessary. {{{ sudo port install qt4-mac-sqlite3-plugin cd /Applications/MacPorts/QGIS.app/Contents/PlugIns sudo mkdir sqldrivers cd sqldrivers/ sudo cp /opt/local/share/qt4/plugins/sqldrivers/libqsqlite.dylib ./ }}} Because library paths were different between Python and QGIS.[[BR]] Python: {{{ $ python >>> from PyQt4.QtCore import QCoreApplication >>> list(QCoreApplication.libraryPaths()) [PyQt4.QtCore.QString(u'/opt/local/share/qt4/plugins')] }}} QGIS (Python Console): {{{ >>> from PyQt4.QtCore import QCoreApplication >>> QCoreApplication.libraryPaths() [u'/Applications/MacPorts/QGIS.app/Contents/PlugIns', u'/Applications/MacPorts/QGIS.app/Contents/PlugIns/qgis'] }}} I think that current '/Applications/MacPorts/QGIS.app/Contents/Plugins' can be changed to '/opt/local/share/qt4/plugins' and duplicate plugins (in codecs, iconengines and imageformats folders) can be removed. -- Ticket URL: <https://trac.macports.org/ticket/46759> MacPorts <https://www.macports.org/> Ports system for OS X

1 6