December 2012 - macports-tickets - lists.macosforge.org

[MacPorts] #37239: New version of grib_api with valuable bugfixes available
by MacPorts 19 Dec '12

19 Dec '12

#37239: New version of grib_api with valuable bugfixes available -------------------------+-------------------------------- Reporter: peeter.as@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: grib_api -------------------------+-------------------------------- There is a new version of grib_api with valuable bugfixes available. Also starting from the version 1.9.5 there is Python interface available, it would be great if it was included: 14-10-2010 Enrico Fucile -- released version 1.9.5 * Python interface available with the configure option --enable- python. See http://www.ecmwf.int/publications/manuals/grib_api/namespacegribapi.html and http://www.ecmwf.int/publications/manuals/grib_api/grib_examples.html Note: the Python interface adds pyXX-numpy dependency. Thank you for providing the grib_api port! -- Ticket URL: <https://trac.macports.org/ticket/37239> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #37325: checksum problems with cctools-headers on 10.5
by MacPorts 18 Dec '12

18 Dec '12

#37325: checksum problems with cctools-headers on 10.5 ----------------------+-------------------------------- Reporter: gregbg@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: ----------------------+-------------------------------- Hi, cctools-headers fail to upgrade due to problems with checksums -- Ticket URL: <https://trac.macports.org/ticket/37325> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 9

[MacPorts] #37333: missing destroot and worksrcpath directories on destroot stage when creating binary + documentation port
by MacPorts 18 Dec '12

18 Dec '12

#37333: missing destroot and worksrcpath directories on destroot stage when creating binary + documentation port -------------------------+-------------------------------- Reporter: garymamon@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: destroot | Port: -------------------------+-------------------------------- I am trying to construct a port for a binary package plus documentation plus Makefile (for install), using MacPorts to force installation of dependent packages if missing. Because my package ("scamp") is already compiled (with a special compiler), my PortFile has: {{{ use_configure no build {} }}} But after running: % cd ~/ports; portindex; cd; sudo port clean scamp; sudo port uninstall scamp; sudo rm /opt/local/var/macports/distfiles/scamp/scamp-2.0b5.tbz2 ; sudo rm -rf /opt/local/var/macports/build/_Users_gam_ports_science_scamp/scamp; sudo port -v install scamp @2.0b5 after correct fetching, checksuming, extracting [from .tbz2 file], configuring, and building, I run into an error, whatever I try for the destroot stage in my Portfile. For example with (an empty) {{{ destroot { puts "prefix = ${prefix}" puts "workpath = ${workpath}" puts "worksrcpath = ${worksrcpath}" puts "destroot = ${destroot}" } }}} I get {{{ prefix = /opt/local workpath = /opt/local/var/macports/build/_Users_gam_ports_science_scamp/scamp/work worksrcpath = /opt/local/var/macports/build/_Users_gam_ports_science_scamp/scamp/work/scamp-2.0b5 destroot = /opt/local/var/macports/build/_Users_gam_ports_science_scamp/scamp/work/destroot Error: No files have been installed in the destroot directory! Error: Please make sure that this software supports 'make install DESTDIR=${destroot}' or implement an alternative destroot mechanism in the Portfile. Error: Files might have been installed directly into your system, check before proceeding. Error: org.macports.destroot for port scamp returned: Staging scamp into destroot failed }}} Now if I try {{{ ls -l /opt/local/var/macports/build/_Users_gam_ports_science_scamp/scamp/work/scamp-2.0b5 }}} or {{{ ls -l /opt/local/var/macports/build/_Users_gam_ports_science_scamp/scamp/work/destroot }}} the directories do not exist! On the other hand, the {{{workpath}}} directory exists and contains the root of the files I wish to have installed by the end user (i.e. Makefile, README, INSTALL, bin, doc, man...). Note that the Makefile has an install: {{{ install: cp -R bin $(DESTDIR) mkdir -p $(DESTDIR)/$(PACKAGE_NAME)-$(PACKAGE_VERSION) mkdir -p $(DESTDIR)/$(PACKAGE_NAME)-$(PACKAGE_VERSION)/share cp -R doc man [A-Z]* $(DESTDIR)/$(PACKAGE_NAME)-$(PACKAGE_VERSION)/share }}} Are these destroot issues normal or a bug in MacPorts? How can I work around them? -- Ticket URL: <https://trac.macports.org/ticket/37333> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #37311: CGAL 4.1 -- How do I set the "proper" CGAL_DIR environment variables?
by MacPorts 18 Dec '12

18 Dec '12

#37311: CGAL 4.1 -- How do I set the "proper" CGAL_DIR environment variables? -----------------------+-------------------------------- Reporter: cdenman@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: CGAL -----------------------+-------------------------------- In the CGAL installation manual at the CGAL.org site it lists the following description for the environment variable CGAL_DIR _________________________ Variables used only when building programs (such as demos or examples) Variable Description Type Default value CGAL_DIR Full-path to the binary directory where Cgal was configured Either CMake or Environment none _________________________ If I had downloaded, configured, and compiled on my own (which I have done in the past, but much prefer Macports) I know where the CGAL folder is. However, with the Macports installation of CGAL I am not sure what the "proper" path to the binary directory "where CGAL was configured. I would guess that it might be: CGAL_DIR = /opt/local/bin Also, there is not a CGAL folder in /Applications/Macports. I notice that the Demos and Examples are installed in /opt/local/share/cgal. Would it be better to have these in a CGAL folder, or others? I am trying to get CGAL to work properly with Scilab by using the Atoms Module called CGLAB. I am noticing that the Scilab environment variables pertaining to the CGLAB are not setting up properly. One such variable needed might be CGAL_DIR. Any help would be appreciated to better understand the environment to use CGAL via an application (Scilab.app), which is not running from Terminal but from the OSX. Thanks, Craig -- Ticket URL: <https://trac.macports.org/ticket/37311> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #37018: qt4-creator-mac: version bump to 2.6.0
by MacPorts 18 Dec '12

18 Dec '12

#37018: qt4-creator-mac: version bump to 2.6.0 ------------------------+-------------------------------- Reporter: macports@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: haspatch | Port: qt4-creator-mac ------------------------+-------------------------------- The attached patch updates the Portfile of qt4-creator-mac to build the latest version 2.6.0. Other changes include: * Update URLs for ''homepage'' and ''master_sites'' * Remove obsolete patches from "files" directory * Download source tarball instead of Zip archive -- Ticket URL: <https://trac.macports.org/ticket/37018> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #35512: OpenCV variant: OpenNI
by MacPorts 18 Dec '12

18 Dec '12

#35512: OpenCV variant: OpenNI -------------------------------+-------------------------------------------- Reporter: orgicus@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: openni | Port: opencv -------------------------------+-------------------------------------------- Hello, I was recently recently updating OpenCV and noticed there was no OpenNI variant. The majority of OpenCV developers might not use the OpenNI support, so it doesn't make sense that this option is on by default, but for developers using a sensor such as Kinect/Xtion Pro/etc. this would be very useful. It would be awesome if there would be an openni variant next to the existing OpenCV ones. Thank you, George P.S. This is as recommended in this thread: http://old.nabble.com/OpenCV- port-variants-td34239708.html P.S. I'm not experienced with MacPorts and not sure if adding OpenNI support also means adding an OpenNI port or not. -- Ticket URL: <https://trac.macports.org/ticket/35512> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #35529: kdesdk4 configure failure
by MacPorts 18 Dec '12

18 Dec '12

#35529: kdesdk4 configure failure --------------------------------------+------------------------------------- Reporter: marzoukiachref@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.1.2 Keywords: Mountain Lion 10.8 | Port: kdesdk 4.8.3 --------------------------------------+------------------------------------- Hi, Im trying ton install kdesdk4 from macports but i have problems when port try to configure kdesdk4. I have patched qt4-mac with "patch-ML.diff" and kdelibs4 by adding template at 3 lines of a file .h I have attached the main.log file, i hope that someone can help !! i'm trying to install it since three day's and no way. Thank's a lot. -- Ticket URL: <https://trac.macports.org/ticket/35529> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 8

[MacPorts] #37322: weechat update to 0.3.9
by MacPorts 17 Dec '12

17 Dec '12

#37322: weechat update to 0.3.9 --------------------------+--------------------- Reporter: and.damore@… | Owner: nefar@… Type: update | Status: new Priority: High | Milestone: Component: ports | Version: 2.1.2 Keywords: haspatch | Port: weechat --------------------------+--------------------- Version 0.3.9 of weechat solves some severe vulnerability issue (remote code execution). I'm attaching a patch to update current 0.3.8 to 0.3.9 . -- Ticket URL: <https://trac.macports.org/ticket/37322> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 1

[MacPorts] #35603: unable to build pango 1.30.1_1
by MacPorts 17 Dec '12

17 Dec '12

#35603: unable to build pango 1.30.1_1 ------------------------------------+--------------------------------------- Reporter: marco.stagno@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: build pango | Port: pango ------------------------------------+--------------------------------------- I'm unable to build pango; on a different mac, with the same configuration, I didn't had any problem.. any help? thank you in advance.. (build log attached) -- Ticket URL: <https://trac.macports.org/ticket/35603> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 8

[MacPorts] #37200: bowtie doesn't build on ML
by MacPorts 17 Dec '12

17 Dec '12

#37200: bowtie doesn't build on ML ----------------------+-------------------------------- Reporter: mesh89@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: ----------------------+-------------------------------- Trying to install bowtie 0.12.7 gives me this output {{{ ---> Computing dependencies for bowtie ---> Fetching archive for bowtie ---> Attempting to fetch bowtie-0.12.7_0.darwin_12.x86_64.tbz2 from http://lil.fr.packages.macports.org/bowtie ---> Attempting to fetch bowtie-0.12.7_0.darwin_12.x86_64.tbz2 from http://packages.macports.org/bowtie ---> Attempting to fetch bowtie-0.12.7_0.darwin_12.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/bowtie ---> Fetching distfiles for bowtie ---> Verifying checksum(s) for bowtie ---> Extracting bowtie ---> Configuring bowtie ---> Building bowtie Error: org.macports.build for port bowtie returned: command execution failed Please see the log file for port bowtie for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_bowtie/bowtie/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port bowtie failed }}} Attaching log -- Ticket URL: <https://trac.macports.org/ticket/37200> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5