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

[MacPorts] #46859: libgpod 0.8.0 Unknown SWIG preprocessor directive
by MacPorts 17 Feb '15

17 Feb '15

#46859: libgpod 0.8.0 Unknown SWIG preprocessor directive -----------------------------------+-------------------------------- Reporter: james_robertson2000@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: libgpod -----------------------------------+-------------------------------- Trying to install digikam, all proceeds well up to the libgpod install and it then fails with a series of errors "Unknown SWIG preprocessor directive". Log attached. Hopefully the log is sufficiently clean - I've done: {{{ sudo port clean digikam sudo port clean libgpod sudo port selfupdate sudo port install digikam }}} and that doesn't fix the issue. Don't know if this is related in any way to #42874 -- Ticket URL: <https://trac.macports.org/ticket/46859> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #46880: Let different versions of lua coexist in an uniform way.
by MacPorts 17 Feb '15

17 Feb '15

#46880: Let different versions of lua coexist in an uniform way. ---------------------------+-------------------------------- Reporter: yszhou4tech@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: lua lua50 lua51 ---------------------------+-------------------------------- Hi, I noticed that header files of `lua5.1` was installed to `/opt/local/include/lua-5.1`, while that of both `lua5.0` and `lua5.2` were supposed to be installed into `/opt/loca/include/`. I think that each of them installed into its own subdirectory within `/opt/local/include` with appropriate pkg-config definition should be more preferable. That way, those packages depending on `lua5.1` can have `-I/opt/local/include` and `-I/opt/local/lua5.1` in their `CPPFLAGS` without having to worry about the order of presence. -- Ticket URL: <https://trac.macports.org/ticket/46880> MacPorts <https://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #46878: Error with the update from version 2.2.1 to 2.3.3
by MacPorts 17 Feb '15

17 Feb '15

#46878: Error with the update from version 2.2.1 to 2.3.3 --------------------------+-------------------------------- Reporter: benjii.lac@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: | Port: --------------------------+-------------------------------- I installed Macports one year ago. I need library in order to run FreeFem on my MacBook. It appears that I need to update it so I used the command sudo port selfupdate An error pops up and I didn't succeed to solve it. I precise that I'm new on computer science. I've few knowledges but not enough to understand everything yet. So I took a look in the difference tickets (for example Ticket #46193) and try the command sudo port -v selfupdate and I got this : [...] sent 64 bytes received 636 bytes 280.00 bytes/sec total size is 512 speedup is 0.73 ---> MacPorts base is outdated, installing new version 2.3.3 Installing new MacPorts release in /opt/local as root:admin; permissions 0755; Tcl-Package in /Library/Tcl configure: WARNING: unrecognized options: --with-tclpackage checking build system type... i386-apple-darwin13.4.0 checking host system type... i386-apple-darwin13.4.0 checking target system type... i386-apple-darwin13.4.0 checking MacPorts version... 2.3.3 checking for sw_vers... /usr/bin/sw_vers checking for defaults... /usr/bin/defaults checking for xcode-select... /usr/bin/xcode-select checking Mac OS X version... 10.9.5 checking Xcode location... /Applications/Xcode.app/Contents/Developer checking Xcode version... 6.1.1 checking whether the C compiler works... no configure: error: in `/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base': configure: error: C compiler cannot create executables See `config.log' for more details Command failed: cd /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base && CC=/usr/bin/cc OBJC=/usr/bin/cc ./configure --prefix=/opt/local --with- tclpackage=/Library/Tcl --with-install-user=root --with-install- group=admin --with-directory-mode=0755 --enable-readline && make SELFUPDATING=1 && make install SELFUPDATING=1 Exit code: 77 Error: Error installing new MacPorts base: command execution failed To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: command execution failed Have you an idea of what is going wrong? -- Ticket URL: <https://trac.macports.org/ticket/46878> MacPorts <https://www.macports.org/> Ports system for OS X

1 7

[MacPorts] #45959: Portfile for Salt 2014.7.0
by MacPorts 17 Feb '15

17 Feb '15

#45959: Portfile for Salt 2014.7.0 ------------------------+-------------------------------- Reporter: cr@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: salt ------------------------+-------------------------------- Attached is a Portfile for 2014.7.0. This port depends on raet (ticket #45958), ioflo (ticket #45957), libnacl (ticket #45898), and libsodium (already present in MacPorts). Both this version and the version for 2014.1.13 (ticket #44300) should be included in MacPorts as some users may wish to stay with the pre-2014.7 branch until 2014.7.xx has matured a little more. -- Ticket URL: <https://trac.macports.org/ticket/45959> MacPorts <https://www.macports.org/> Ports system for OS X

1 7

[MacPorts] #46882: signify @1.2
by MacPorts 17 Feb '15

17 Feb '15

#46882: signify @1.2 ---------------------------------+-------------------------------- Reporter: jpo@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: maintainer haspatch | Port: signify ---------------------------------+-------------------------------- also updating my email -- Ticket URL: <https://trac.macports.org/ticket/46882> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

Re: [MacPorts] #44804: Update protobuf-cpp to 2.6.0
by MacPorts 16 Feb '15

16 Feb '15

#44804: Update protobuf-cpp to 2.6.0 ---------------------------+--------------------- Reporter: nomis52@… | Owner: blair@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: protobuf-cpp | ---------------------------+--------------------- Comment (by adfernandes@…): I've updated '''and tested''' `protobuf-cpp`, `protobuf-java`, `protobuf-c`, and `py-protobuf`. Unfortunately, python3 still isn't supported. Oh well. Patch is attached. I can merge, if that's okay with blair and landonf. -- Ticket URL: <https://trac.macports.org/ticket/44804#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #46861: mpd won't start: No such audio output plugin: osx" at startup
by MacPorts 16 Feb '15

16 Feb '15

#46861: mpd won't start: No such audio output plugin: osx" at startup --------------------------+-------------------------------- Reporter: bnilsson11@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: mpd --------------------------+-------------------------------- Music Player Daemon 0.19.9 OSX 10.10.2 When starting mad on mac OS X, I get this: No such audio output plugin: OS X If OS X is not supported, why port it to mac? -- Ticket URL: <https://trac.macports.org/ticket/46861> MacPorts <https://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #46857: update rNMR to 1.1.8 using new xvfb-run port and xvfb subport as well as return to ${prefix}/lib/R/library
by MacPorts 16 Feb '15

16 Feb '15

#46857: update rNMR to 1.1.8 using new xvfb-run port and xvfb subport as well as return to ${prefix}/lib/R/library -----------------------------------+-------------------------------- Reporter: howarth.at.macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: rNMR -----------------------------------+-------------------------------- The attached Portfile diff relies on the following tickets... 1) Ticket #46849 which restores the ability of the R package to find R packages placed in ${prefix}/lib/R/library 2) Ticket #46842 which adds the new xvfb-run package which provides the Debian xvfb-run utility. 3) Ticket #46856 which adds the new xvfb subport to the xorg-server package which the new xvfb-run package depends_run on. The new rNMR Portfile.diff implements the following changes... a) Moves the location of the installed rNMR R package back to its previous location in ${prefix}/lib/R/library. b) Adds the missing "require_active_variants tk x11" as the rNMR package requires a tk to use X11. c) Updates the rNMR package to the 1.1.8 release. d) passes the "${prefix}/bin/R CMD INSTALL -l pkg --byte-compile --build ${distpath}/[lindex ${distfiles} 0]" command through "`which xvfb-run`" to avoid build failures due to the use of X11 in newer version of rNMR.r. -- Ticket URL: <https://trac.macports.org/ticket/46857> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

Re: [MacPorts] #45294: Request for a new port - toxcore
by MacPorts 16 Feb '15

16 Feb '15

#45294: Request for a new port - toxcore ---------------------------+-------------------------------- Reporter: lubodiakov@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: toxcore | ---------------------------+-------------------------------- Comment (by lubodiakov@…): Sorry for the delay, missed the email copy of this comment and had not logged in here for a while. Replying to [comment:12 khindenburg@…]: > I have a working version Not sure how that relates? > > Where did you get the version 0.5.2? The versioning is a bit complicated and mixed up, not by my choice. I.e. it is that way in the upstream project. There is a build number for toxcore, it can be seen from the projects Jenkins server: https://jenkins.libtoxcore.so/job/Sync%20Tox/ As of now (Feb. 16, 2015 it is at build 500. This is the same build number I'm using in my newest portfiles for toxcore, which I'm attaching. There are separate version numbers (such as 0.5.2) which appear inside clients that use toxcore, such as toxic: https://github.com/Tox/toxic > Are there any clients that use this library working on OSX? Yes I have built Toxic (CLI and audio, no video) myself, and others have built GUI clients on newer versions of OS X. -- Ticket URL: <https://trac.macports.org/ticket/45294#comment:13> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #46743: vcs_blackbox @1.20150203 New contribution
by MacPorts 16 Feb '15

16 Feb '15

#46743: vcs_blackbox @1.20150203 New contribution ------------------------+-------------------------------- Reporter: tal@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: vcs_blackbox ------------------------+-------------------------------- -- Ticket URL: <https://trac.macports.org/ticket/46743> MacPorts <https://www.macports.org/> Ports system for OS X

1 8