March 2013 - macports-tickets - lists.macosforge.org

[MacPorts] #34571: upgrade outdated loops.
by MacPorts 20 May '14

20 May '14

#34571: upgrade outdated loops. ---------------------------+------------------------------------------------ Reporter: macrbg@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Keywords: | Port: ---------------------------+------------------------------------------------ {{{ # port selfupdate ---> Updating MacPorts base sources using rsync MacPorts base version 2.0.4 installed, MacPorts base version 2.1.1 downloaded. ---> Updating the ports tree ---> MacPorts base is outdated, installing new version 2.1.1 Installing new MacPorts release in /opt/local as root:wheel; permissions 0755; Tcl-Package in /Library/Tcl The ports tree has been updated. To upgrade your installed ports, you should run port upgrade outdated # port upgrade outdated }}} Things progress until i hit this loop. {{{ Warning: No port pcre++ found in the index; can't rebuild ---> Found 0 broken port(s), determining rebuild order ---> Rebuilding in order ---> Scanning binaries for linking errors: 100.0% ---> Found 1 broken file(s), matching files to ports }}} -- Ticket URL: <https://trac.macports.org/ticket/34571> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #37636: gearmand @0.41 Startup item defect
by MacPorts 19 May '14

19 May '14

#37636: gearmand @0.41 Startup item defect ---------------------+-------------------------------- Reporter: remko@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: gearmand ---------------------+-------------------------------- The startup-item for gearmand 0.41 is not working since it adds an invalid option to the startup command (-vv instead of --verbose=WARNING). I added a patch to fix the issue. -- Ticket URL: <https://trac.macports.org/ticket/37636> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #33160: py27-hachoir-urwid
by MacPorts 19 May '14

19 May '14

#33160: py27-hachoir-urwid -------------------------------+-------------------------------------------- Reporter: m.haller@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: py27-hachoir-urwid -------------------------------+-------------------------------------------- Binary file explorer using Hachoir and urwid libraries [http://pypi.python.org/pypi/hachoir-urwid/1.1] -- Ticket URL: <https://trac.macports.org/ticket/33160> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #33159: py27-hachoir-parser
by MacPorts 19 May '14

19 May '14

#33159: py27-hachoir-parser -------------------------------+-------------------------------------------- Reporter: m.haller@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: py27-hachoir-parser -------------------------------+-------------------------------------------- hachoir-parser is a package of most common file format parsers written for the Hachoir framework. Currently, 78 parsers are supported (some only partially). [http://pypi.python.org/pypi/hachoir-parser] -- Ticket URL: <https://trac.macports.org/ticket/33159> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #33157: py27-hachoir-core
by MacPorts 19 May '14

19 May '14

#33157: py27-hachoir-core -------------------------------+-------------------------------------------- Reporter: m.haller@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: py27-hachoir-core -------------------------------+-------------------------------------------- Hachoir is a Python library used to represent of a binary file as a tree of Python objects. Each object has a type, a value, an address, etc. The goal is to be able to know the meaning of each bit in a file. [http://pypi.python.org/pypi/hachoir-core] -- Ticket URL: <https://trac.macports.org/ticket/33157> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #34271: python27 2.7.3_0 py27-gtk 2.22.0_1 etc -- pkg-config files not installed correctly for python 2.6 and 2.7 versions of pygtk and pygobject
by MacPorts 18 May '14

18 May '14

#34271: python27 2.7.3_0 py27-gtk 2.22.0_1 etc -- pkg-config files not installed correctly for python 2.6 and 2.7 versions of pygtk and pygobject -------------------------------------+-------------------------------------- Reporter: stephen.langer@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Keywords: | Port: py25-gtk py27-gtk py26-gtk py27-gobject py26-gobject py25-gobject python26 python27 -------------------------------------+-------------------------------------- I don't know which port this bug belongs to, so I've included all of the possibilities. I hope that's not bad etiquette. The ports py26-gtk, py27-gtk, py26-gobject, and py27-gobject do not install their .pc files (pygtk-2.0.pc and pygobject-2.0.pc) in /opt/local/lib/pkgconfig. Instead, they leave the files in /opt/local/Library/Frameworks/Python.framework/Versions/2.*/lib/pkgconfig/. Shouldn't "port select --set python python2.7" copy the appropriate files to /opt/local/lib/pkgconfig? The problem may be that py25-gtk and py25-gobject install their .pc files directly into /opt/local/lib/pkgconfig, which means that port select can't install the py26 or py27 files without trashing the py25 files. Background: I develop and distribute software that uses pkg-config in its installation script, and works with python 2.5, 2.6, or 2.7. I therefore have py25-gtk, py26-gtk, and py27-gtk all installed. When I build the software locally it uses the python 2.5 version of pygtk-2.0.pc and pygobject-2.0.pc no matter which python version I'm currently using. This doesn't actually seem to cause a problem. However, the build fails for users who have never installed py25-gtk and py25-gobject, unless they explicitly set PKG_CONFIG_PATH. I don't think this should be necessary. -- Ticket URL: <https://trac.macports.org/ticket/34271> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 13

[MacPorts] #20309: qt4-x11 doesn't support 10.6 yet
by MacPorts 15 May '14

15 May '14

#20309: qt4-x11 doesn't support 10.6 yet ------------------------------+--------------------------------------------- Reporter: snc@… | Owner: mcalhoun@… Type: defect | Status: new Priority: Low | Milestone: Component: ports | Version: 1.8.0 Keywords: | Port: qt4-x11 ------------------------------+--------------------------------------------- qt4-x11 builds while build, citing an unsupported version of 10.6. Might be an upstream issue? Setting to low priority as 10.6 is not out yet. {{{ /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_qt4-x11/work/qt-x11 -opensource- src-4.4.3/include/QtCore/../../src/corelib/global/qglobal.h:290:6: error: #error "This version of Mac OS X is unsupported" }}} -- Ticket URL: <http://trac.macports.org/ticket/20309> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 28

[MacPorts] #36906: osgeo [python-gdal] module missing from qgis install port
by MacPorts 15 May '14

15 May '14

#36906: osgeo [python-gdal] module missing from qgis install port ------------------------------------+-------------------------------- Reporter: drew.mueller@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: osgeo python-gdal qgis | Port: qgis ------------------------------------+-------------------------------- I get the following error message upon opening QGIS. The GdalTools plugin is part of the standard install of QGIS. Unable to load GdalTools plugin. The required "osgeo [python-gdal]" module is missing. Install it and try again. Is there a way to port install this missing module? I'm a total newbie to macports I don't see this as a variant -- Ticket URL: <https://trac.macports.org/ticket/36906> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 7

[MacPorts] #34171: Add cling variant to ROOT port
by MacPorts 13 May '14

13 May '14

#34171: Add cling variant to ROOT port --------------------------------------+------------------------------------- Reporter: Deil.Christoph@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Keywords: | Port: root --------------------------------------+------------------------------------- Would it be possible to optionally enable cling via a Macports variant? http://root.cern.ch/drupal/content/cling Note that I haven't found out how to configure ROOT with --enable-cling yet. I've asked for help in the ROOT forum: http://root.cern.ch/phpBB3/viewtopic.php?f=21&t=14550 Thanks! -- Ticket URL: <https://trac.macports.org/ticket/34171> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 19

[MacPorts] #37688: New Port - root-devel giving a snapshot of the ROOT6 development.
by MacPorts 13 May '14

13 May '14

#37688: New Port - root-devel giving a snapshot of the ROOT6 development. ------------------------+-------------------------------- Reporter: jonesc@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: maintainer | Port: root-devel ------------------------+-------------------------------- Hi, Attached is the port file (and two patch files) for a proposed new port root-devel. It should I guess live in the science section, along side the root port. It provides access to a snapshot of the ROOT 6 development cycle. This is a major development over ROOT 5 and most notably replaces the CINT interpreter with cling, a new one based on llvm/clang. This is a big change so it is likely we will want to maintain ROOT5 and ROOT6 versions for some time, even once ROOT6 is first released. No actual releases are made yet, so this port grabs an a particular (fixed) svn revision from the ROOT svn server. Other than the changes needed to do this the port is essentially the same as the root port, and provides most of the same variants. I have though removed the various gcc and clang variants, as it simply does not compile with these compilers. I have only got it working with clang and llvm-gcc4.2 in OSX10.8 Xcode 4.5.2. I don't have access to any other OSX versions, so have no idea if it will compile on them or not ... This port conflicts with the root port (and thus if committed the root port should be updated at the same time to conflict with this one). Allowing them to be installable side by side might be possible, but quite a bit of effort and I am not sure if it would be worth it. One thing I wasn't completely sure on was how to update the livecheck section, so please take a look at that part. cheers Chris -- Ticket URL: <https://trac.macports.org/ticket/37688> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 46