April 2016 - macports-tickets - lists.macosforge.org

[MacPorts] #51133: Geant 4.10.1
by MacPorts 13 Apr '16

13 Apr '16

#51133: Geant 4.10.1 ----------------------+-------------------------------- Reporter: ith140@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: geant4.10.1 ----------------------+-------------------------------- Bug building the new version with the p03 patch. I've looked at log file and am not really sure how to diagnose problem further, so I've attached it. -- Ticket URL: <https://trac.macports.org/ticket/51133> MacPorts <https://www.macports.org/> Ports system for OS X

1 6

Re: [MacPorts] #33246: Package request: winexe
by MacPorts 13 Apr '16

13 Apr '16

#33246: Package request: winexe ----------------------+-------------------------------- Reporter: dave@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Resolution: | Keywords: Port: | ----------------------+-------------------------------- Comment (by irfandurmus@…): Anyone planning to add winexe to macports? I don't like to download a binary manually, would be great if we have it in our package manager! -- Ticket URL: <https://trac.macports.org/ticket/33246#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #51136: `port pkg` and `port dmg` do not agree on how to handle the port revision
by MacPorts 13 Apr '16

13 Apr '16

#51136: `port pkg` and `port dmg` do not agree on how to handle the port revision -------------------------+-------------------------------- Reporter: rjvbertin@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.4 Keywords: | Port: -------------------------+-------------------------------- Citing Ryan on a macports-dev thread I started (`port [m]dmg and PackageMaker`) : > there appears to be a bug where "port dmg" assumes that the package name > does not have a revision number, but "port pkg" adds a revision number to > the package name if the revision is not zero. I would argue that both need to take the revision number into account as there is no way of knowing what the revbump covers. -- Ticket URL: <https://trac.macports.org/ticket/51136> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

Re: [MacPorts] #42725: 'port pkg' still requires PackageMaker.app
by MacPorts 13 Apr '16

13 Apr '16

#42725: 'port pkg' still requires PackageMaker.app ---------------------+-------------------------------- Reporter: rob@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.2.1 Resolution: | Keywords: Port: | ---------------------+-------------------------------- Comment (by rjvbertin@…): Having found and used that PackageMaker version myself yesterday, I'd say that it calls pkgbuild and productbuild. The easy/evident quickfix (waiting for a release with a more proper fix) would be to check with Apple if MacPorts can redistribute the application, and ship it in a port. -- Ticket URL: <https://trac.macports.org/ticket/42725#comment:9> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #51126: armadillo @6.700.3_1: update to 6.700.4
by MacPorts 13 Apr '16

13 Apr '16

#51126: armadillo @6.700.3_1: update to 6.700.4 ---------------------------------+-------------------------------- Reporter: mschamschula@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: haspatch maintainer | Port: armadillo ---------------------------------+-------------------------------- armadillo has been updated to version 6.700.4. -- Ticket URL: <https://trac.macports.org/ticket/51126> MacPorts <https://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #51081: pango @1.40.0 - build failing
by MacPorts 12 Apr '16

12 Apr '16

#51081: pango @1.40.0 - build failing ---------------------------+-------------------------------- Reporter: russ.bubley@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: ---------------------------+-------------------------------- Pango build is failing (for me) with the following error: {{{ :info:build In file included from pangocairo-coretextfont.c:32: :info:build ./pangocairo-coretext.h:28:10: fatal error: 'cairo-quartz.h' file not found }}} The compile step failing is {{{ /usr/bin/clang -arch x86_64 -DHAVE_CONFIG_H -I. -I.. -DG_LOG_DOMAIN=\"Pango\" -DPANGO_ENABLE_BACKEND -DPANGO_ENABLE_ENGINE -DSYSCONFDIR=\"/Volumes/MacHD/opt/local/etc\" -DLIBDIR=\"/Volumes/MacHD/opt/local/lib\" -I.. -I.. -DG_DISABLE_CAST_CHECKS -D_REENTRANT -I/Volumes/MacHD/opt/local/include/glib-2.0 -I/Volumes/MacHD/opt/local/lib/glib-2.0/include -I/Volumes/MacHD/opt/local/include -I/opt/X11/include -I/opt/X11/include/freetype2 -I/Volumes/MacHD/opt/local/include/freetype2 -I/Volumes/MacHD/opt/local/include -I/Volumes/MacHD/opt/local/include/libpng16 -I/opt/X11/include -I/opt/X11/include/cairo -I/Volumes/MacHD/opt/local/include/pixman-1 -I/opt/X11/include -I/opt/X11/include/freetype2 -I/Volumes/MacHD/opt/local/include/freetype2 -I/Volumes/MacHD/opt/local/include -I/Volumes/MacHD/opt/local/include/libpng16 -I/opt/X11/include -I/Volumes/MacHD/opt/local/include/harfbuzz -I/Volumes/MacHD/opt/local/include/glib-2.0 -I/Volumes/MacHD/opt/local/lib/glib-2.0/include -I/Volumes/MacHD/opt/local/include -I/Volumes/MacHD/opt/local/include/freetype2 -I/Volumes/MacHD/opt/local/include -I/Volumes/MacHD/opt/local/include/libpng16 -I/opt/X11/include -I/opt/X11/include/freetype2 -I/Volumes/MacHD/opt/local/include/freetype2 -I/Volumes/MacHD/opt/local/include -I/Volumes/MacHD/opt/local/include/libpng16 -I/Volumes/MacHD/opt/local/include -pipe -Os -arch x86_64 -Wall -MT pangocoretext-shape.lo -MD -MP -MF .deps/pangocoretext-shape.Tpo -c pangocoretext-shape.c -o pangocoretext-shape.o >/dev/null 2>&1 }}} cairo-quartz.h does exist on my system as I have cairo @1.14.6_0+quartz+x11 installed, but this puts the file into /opt/local/include/cairo/cairo-quartz.h, which is not on the list of paths included on the compile command. -- Ticket URL: <https://trac.macports.org/ticket/51081> MacPorts <https://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #51107: gnuradio 3.7.9.1 ImportError: No module named gnuradio
by MacPorts 12 Apr '16

12 Apr '16

#51107: gnuradio 3.7.9.1 ImportError: No module named gnuradio ----------------------+-------------------------------- Reporter: ethicz@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: gnuradio ----------------------+-------------------------------- Successfully installed gnuradio and companion working fine but having issues running python script through terminal. {{{ ImportError: No module named gnuradio }}} Running OSX 10.11.4 and python 2.7. Following the troubleshooting steps mentioned in [https://trac.macports.org/ticket/28315 Ticket #28315], "ls /opt/local/lib/python2.7/site-packages" returns: {{{ xcbgen }}} And "port installed | grep gnuradio" returns: {{{ gnuradio-devel @20160331_0+docs+grc+jack+portaudio+qtgui+sdl+swig+uhd+wavelet+wxgui (active) }}} It appears the python modules were never installed? I appreciate the help. -- Ticket URL: <https://trac.macports.org/ticket/51107> MacPorts <https://www.macports.org/> Ports system for OS X

1 8

[MacPorts] #51129: pango: update to version 1.40.1
by MacPorts 12 Apr '16

12 Apr '16

#51129: pango: update to version 1.40.1 ----------------------+-------------------------- Reporter: devans@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: pango ----------------------+-------------------------- Version 1.40.1 (minor bugfixes) has been released as part of the GNOME 3.20.1 stable release process. {{{ Overview of changes between 1.40.0 and 1.40.1 ============================================= - Use $PKG_CONFIG consistently (#764191) - Fix a PangoWin32FontMap memory leak (#7640890) }}} -- Ticket URL: <https://trac.macports.org/ticket/51129> MacPorts <https://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #51118: fswatch @1.9.2: update to 1.9.2
by MacPorts 12 Apr '16

12 Apr '16

#51118: fswatch @1.9.2: update to 1.9.2 -----------------------------------+-------------------------------- Reporter: enrico.m.crisostomo@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: haspatch maintainer | Port: fswatch -----------------------------------+-------------------------------- fswatch 1.9.2 -- Ticket URL: <https://trac.macports.org/ticket/51118> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #50171: Update or remove PyWavelets?
by MacPorts 12 Apr '16

12 Apr '16

#50171: Update or remove PyWavelets? ------------------------------+-------------------------------- Reporter: Deil.Christoph@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: py-pywavelets ------------------------------+-------------------------------- Currently py-pywavelets is at 0.2.2 in Macports and has no maintainer. The latest stable version is 0.4, which has Python 3 support and many new features and changes: * http://pywavelets.readthedocs.org/en/latest/release.0.4.0.html * https://pypi.python.org/pypi/PyWavelets/0.4.0 If someone can update py-pywavelets to version 0.4 and add Python 3 ports, that would be great! Alternatively, given that pip install pywavelets works, I think removing the port would also be OK. Keeping the very outdated version is probably not helpful to most (all?) users, no? -- Ticket URL: <https://trac.macports.org/ticket/50171> MacPorts <https://www.macports.org/> Ports system for OS X

1 3