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

Re: [MacPorts] #42732: mpfr @3.1.1-p2: test suite fails on x86_64 Snow Leopard (when run with `port test gmp mpfr libmpc`)
by MacPorts 26 Jun '15

26 Jun '15

#42732: mpfr @3.1.1-p2: test suite fails on x86_64 Snow Leopard (when run with `port test gmp mpfr libmpc`) ----------------------+---------------------- Reporter: egall@… | Owner: larryv@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: mpfr | ----------------------+---------------------- Changes (by mf2k@…): * owner: macports-tickets@… => larryv@… -- Ticket URL: <https://trac.macports.org/ticket/42732#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #48170: mpfr 3.1.2-P10_3: update to 3.1.3
by MacPorts 26 Jun '15

26 Jun '15

#48170: mpfr 3.1.2-P10_3: update to 3.1.3 ----------------------------+-------------------------------- Reporter: mschamschula@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: haspatch | Port: mpfr ----------------------------+-------------------------------- mpfr has been updated to verison 3.1.3. New this version: * Better support for Automake 1.13+ (now used to generate the tarball). * Improved MPFR manual. * Bug fixes Yosemite libtool fix has been include upstream. -- Ticket URL: <https://trac.macports.org/ticket/48170> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #48152: wxMaxima will not launch unless explicitly called with "open" command
by MacPorts 26 Jun '15

26 Jun '15

#48152: wxMaxima will not launch unless explicitly called with "open" command -------------------------+-------------------------------- Reporter: m74z00219@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: wxmaxima -------------------------+-------------------------------- I was asked to open a new ticket after today posting to ticket #47755. Here's what I said: I would like to report that I can no longer launch wxmaxima directly. It'll launch if I use "open /path/to/wxmaxima.app," though not just by inputting "wxmaxima" as with other ports. Inputting "maxima" works just fine. Why might this be? I figure it has something to do with the removal of the above symlink and I know for a fact that "/Applications/MacPorts/" was never part of my PATH variable. Even so, I did try, in succession, adding "/Applications/MacPorts/" and "/Applications/MacPorts/wxMaxima.app" to my PATH and still it would not launch with "wxmaxima." Here's some other stuff I tried. I "sudo port selfupdate" and "sudo port upgrade outdated". I did it once more just to be sure. Unfortunately, the problem persists. Initially, I also had a problem with wxmaxima not being able to connect to maxima. This was resolved by making sure that wxMaxima was listening to the default port of xmaxima. Or, at least I think that's what did it. Actually, I just played around with the port option and apparently it still works, so...mystery. It connects so whatever. I thought briefly about nuking my Macports installation, but that seems like overkill as it seems that the problem is just with maxima. Honestly, I'm so confused. There's also xmaxima -- where does that fit it in?? To sum up, what might explain the inability to launch wxmaxima from command line? Here's my PATH: {{{ PATH=/opt/local/bin:/opt/local/sbin:/opt/local/etc/php56:/opt/local/apache2/bin:/opt/local/lib/mysql56/bin:~/bin:~/.composer/vendor/bin:${PATH} }}} Thanks! -- Ticket URL: <https://trac.macports.org/ticket/48152> MacPorts <https://www.macports.org/> Ports system for OS X

1 18

[MacPorts] #48172: tiff @4.0.3_4: update to 4.0.4
by MacPorts 26 Jun '15

26 Jun '15

#48172: tiff @4.0.3_4: update to 4.0.4 ----------------------------+-------------------------------- Reporter: mschamschula@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: haspatch | Port: tiff ----------------------------+-------------------------------- tiff has been updated to version 4.0.4. patch-tiffgt.c.diff has been included upstream. -- Ticket URL: <https://trac.macports.org/ticket/48172> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

Re: [MacPorts] #42858: [NEW] suricata 1.4.7
by MacPorts 25 Jun '15

25 Jun '15

#42858: [NEW] suricata 1.4.7 -------------------------+-------------------------------- Reporter: jul_bsd@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: suricata | -------------------------+-------------------------------- Comment (by mschamschula@…): Replying to [comment:18 mk@…]: > There is no port {{{oinkmaster}}} up to now and you copied its perl code into your {{{~/bin}}}!? {{{oinkmaster}}} is just a perl script. I put it in {{{~/bin}}} to keep it out of the {{{/usr}}} and the {{{/opt}}} trees. Needless to say, once there is a port it will be in {{{/opt/local/bin}}} > But [https://trac.macports.org/attachment/ticket/42858/org.macports .oinkmaster-suricata.plist org.macports.oinkmaster-suricata.plist] seems to assume it being installed below the MacPorts prefix. Obviously I am missing something here. There is not such a thing (yet). At least it didn't get installed on my machines. > What about the SC_ERR_MAGIC_LOAD error? Is that fixed? I don't see that issue with 2.0.7 or 2.0.8. I've got File 5.23. I just ran the 'test' mode and saw no errors. -- Ticket URL: <https://trac.macports.org/ticket/42858#comment:19> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

Re: [MacPorts] #42858: [NEW] suricata 1.4.7
by MacPorts 25 Jun '15

25 Jun '15

#42858: [NEW] suricata 1.4.7 -------------------------+-------------------------------- Reporter: jul_bsd@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: suricata | -------------------------+-------------------------------- Comment (by mk@…): There is no port {{{oinkmaster}}} up to now and you copied its perl code into your {{{~/bin}}}!? But [https://trac.macports.org/attachment/ticket/42858/org.macports .oinkmaster-suricata.plist org.macports.oinkmaster-suricata.plist] seems to assume it being installed below the MacPorts prefix. Obviously I am missing something here. What about the SC_ERR_MAGIC_LOAD error? Is that fixed? -- Ticket URL: <https://trac.macports.org/ticket/42858#comment:18> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #48167: llvm-3.3 @3.3_8 fails configuring
by MacPorts 25 Jun '15

25 Jun '15

#48167: llvm-3.3 @3.3_8 fails configuring ----------------------------------------+-------------------------------- Reporter: braumann@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: python version check fails | Port: llvm-3.3 ----------------------------------------+-------------------------------- Upgrading {{{llvm-3.3 @3.3_7}}} to {{{llvm-3.3 @3.3_8}}} fails since the configure script by mistake is not recognizing that python has an accepted version. The relevant lines in the config.log: {{{ ... configure:12343: checking for python configure:12361: found /opt/local/bin/python configure:12378: result: /opt/local/bin/python configure:12388: checking for python >= 2.5 configure:12399: result: not found configure:12402: error: found python (/opt/local/bin/python); required >= 2.5 ... }}} However, manually checking the version gives: {{{ $ /opt/local/bin/python --version Python 3.4.3 }}} BTW, llvm-3.4 was smoothly upgrading to {{{llvm-3.4 @3.4.2_7}}} a minute before. -- Ticket URL: <https://trac.macports.org/ticket/48167> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

Re: [MacPorts] #32575: llvm-X.Y: fail to build with python3 selected
by MacPorts 25 Jun '15

25 Jun '15

#32575: llvm-X.Y: fail to build with python3 selected -----------------------------------------+---------------------- Reporter: jonesc@… | Owner: larryv@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Resolution: | Keywords: python3 Port: llvm-3.1 llvm-3.2 llvm-3.3 | -----------------------------------------+---------------------- Changes (by larryv@…): * cc: braumann@… (added) * port: llvm-3.1 llvm-3.2 => llvm-3.1 llvm-3.2 llvm-3.3 Comment: Has duplicate #48167. -- Ticket URL: <https://trac.macports.org/ticket/32575#comment:45> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #48164: port request: 'asciinema'
by MacPorts 25 Jun '15

25 Jun '15

#48164: port request: 'asciinema' ----------------------------+-------------------------------- Reporter: kurt.pfeifle@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: ----------------------------+-------------------------------- The 'asciinema' utility is very handy for recording terminal key strokes and related output for later demonstration or teaching/sharing purposes. The following command will start the recording of a terminal session (which can be ended by typing "exit" or hitting 'ctrl+D'): asciinema rec -w 1 my.session The `-w 1` parameter will limit periods of non-activity to 1 second max. The next command will replay the same session: asciinema play my.session The software is Free (GPL3), with source code (written in Go and JavaScript) on GitHub: https://github.com/asciinema/asciinema The files it writes ('my.session' above) are Unicode text files, and can easily be edited after recording (f.e. to fix typos). You can view one asciinema screencast which I made yesterday here: https://asciinema.org/a/22364 -- Ticket URL: <https://trac.macports.org/ticket/48164> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

Re: [MacPorts] #36522: commons-daemon java 1.7 mountain lion fails
by MacPorts 25 Jun '15

25 Jun '15

#36522: commons-daemon java 1.7 mountain lion fails ------------------------------+-------------------------------- Reporter: eamonn.kearns@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: Port: commons-daemon | ------------------------------+-------------------------------- Comment (by malcolm@…): I'm one month down the line and still I've got commons-daemon broken. Could somebody please write some SPECIFIC INSTRUCTIONS as to how to fix this? I patched commons-daemon ok, but where the hell is or what is location.c ?? PLEASE, this just needs someone to write minimal help, I'm risking a broken system here. Thanks. -- Ticket URL: <https://trac.macports.org/ticket/36522#comment:8> MacPorts <https://www.macports.org/> Ports system for OS X

1 0