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

[MacPorts] #46893: Coffescript does not compile js anymore
by MacPorts 09 Oct '15

09 Oct '15

#46893: Coffescript does not compile js anymore -----------------------------------------+-------------------------------- Reporter: andrew@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.3.3 Keywords: coffeescript, coffee-script | Port: coffee-script -----------------------------------------+-------------------------------- Hi The latest updates seem to have broken coffeescript. $ coffee -b -c -o working/js coffee TypeError: undefined is not a function at writeJs (/opt/local/lib/coffee-script/lib/coffee- script/command.js:413:17) at compileScript (/opt/local/lib/coffee-script/lib/coffee- script/command.js:185:18) at /opt/local/lib/coffee-script/lib/coffee-script/command.js:150:18 at fs.js:336:14 at FSReqWrap.oncomplete (fs.js:99:15) -- Ticket URL: <https://trac.macports.org/ticket/46893> MacPorts <https://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #45980: fail2ban version is rather old
by MacPorts 08 Oct '15

08 Oct '15

#45980: fail2ban version is rather old -----------------------------+-------------------------------- Reporter: luc_j_bourhis@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: fail2ban -----------------------------+-------------------------------- Current version of fail2ban according to the official page at [http://www.fail2ban.org/wiki/index.php/Main_Page] is 0.9.1 whereas Macports ships 0.8.10. -- Ticket URL: <https://trac.macports.org/ticket/45980> MacPorts <https://www.macports.org/> Ports system for OS X

1 6

[MacPorts] #46334: Ghostscript build failure on Yosemite
by MacPorts 06 Oct '15

06 Oct '15

#46334: Ghostscript build failure on Yosemite ------------------------------+-------------------------------- Reporter: brookemgilbert@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: ------------------------------+-------------------------------- Hi, on a fresh install of macports 2.3.3 following upgrade to Yosemite (10.10.1), Ghostscript was failing to build/install (but I found a workaround). This appears to be a different problem from this other similar ticket https://trac.macports.org/ticket/46332 on examination of the log files. My output was... {{{ $ sudo port clean ghostscript ---> Cleaning ghostscript $ $ $ sudo port install -d ghostscript ---> Computing dependencies for ghostscript ---> Fetching archive for ghostscript Warning: Your DNS servers incorrectly claim to know the address of nonexistent hosts. This may cause checksum mismatches for some ports. See this page for more information: <https://trac.macports.org/wiki/MisbehavingServers> ---> Attempting to fetch ghostscript-9.10_2+x11.darwin_14.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/ghostscript ---> Attempting to fetch ghostscript-9.10_2+x11.darwin_14.x86_64.tbz2 from http://lil.fr.packages.macports.org/ghostscript ---> Attempting to fetch ghostscript-9.10_2+x11.darwin_14.x86_64.tbz2 from http://nue.de.packages.macports.org/macports/packages/ghostscript ---> Fetching distfiles for ghostscript ---> Verifying checksums for ghostscript ---> Extracting ghostscript ---> Applying patches to ghostscript ---> Configuring ghostscript Error: org.macports.configure for port ghostscript returned: autoreconf failure: command execution failed Please see the log file for port ghostscript for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_print_ghostscript/ghostscript/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port ghostscript failed }}} The main.log is attached; of interest was: {{{ :info:configure aclocal: error: aclocal: file '/opt/local/share/aclocal/wxwin.m4' does not exist :info:configure autoreconf: aclocal failed with exit status: 1 }}} Since wxwin.m4 is part of wxWidgets, I tried installing wxWidgets-3.0 manually. Then I tried again to install ghostscript and it worked just fine! So I guess that means ghostscript needs wxWidgets-3.0 but it isn't identified as a dependency in the ports tree. I can replicate the failure by uninstalling ghostscript and wxWidgets-3.0, then trying to re-install ghostscript. Cheers -- Ticket URL: <https://trac.macports.org/ticket/46334> MacPorts <https://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #46646: update ed to 1.10
by MacPorts 04 Oct '15

04 Oct '15

#46646: update ed to 1.10 ----------------------------------+-------------------------------- Reporter: michael.bryniarski@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: ed ----------------------------------+-------------------------------- ed has been updated 1.10: http://www.gnu.org/software/ed/ -- Ticket URL: <https://trac.macports.org/ticket/46646> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #47314: Error: org.macports.fetch for port mesa returned: fetch failed
by MacPorts 04 Oct '15

04 Oct '15

#47314: Error: org.macports.fetch for port mesa returned: fetch failed ------------------------+-------------------------------- Reporter: diochnos@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: mesa ------------------------+-------------------------------- I have installed macports in a custom directory in this machine. Unfortunately it can not fetch mesa. (In another machine without a custom installation directory I had no problems with selfupdate / upgrade outdated ) Log attached -- Ticket URL: <https://trac.macports.org/ticket/47314> MacPorts <https://www.macports.org/> Ports system for OS X

1 26

[MacPorts] #45470: botan: needs revision update for universal builds
by MacPorts 03 Oct '15

03 Oct '15

#45470: botan: needs revision update for universal builds ------------------------+------------------- Reporter: mcalhoun@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.2 Keywords: | Port: botan ------------------------+------------------- The build.h file merges incorrectly in a universal build due to nested comments.[[BR]] This is similar to #25439.[[BR]] A fix similar to r79694 should fix the problem. -- Ticket URL: <https://trac.macports.org/ticket/45470> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #47102: sleuthkit: disable java bindings
by MacPorts 01 Oct '15

01 Oct '15

#47102: sleuthkit: disable java bindings -----------------------+-------------------------------- Reporter: jul_bsd@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: sleuthkit -----------------------+-------------------------------- on yosemite, build fails because of absence of java. not sure when it started to be a problem {{{ checking for uudecode... yes checking if uudecode can decode base 64 file... yes checking if java works... configure: error: The Java VM java failed (see config.log, check the CLASSPATH?) Command failed: cd "/opt/local/var/macports/build/_Users_julien_tmp_myports_sysutils_sleuthkit/sleuthkit/work/sleuthkit-4.1.3" && ./configure --prefix=/opt/local --mandir=/opt/local/share/man Exit code: 1 Error: Failed to configure sleuthkit, consult /opt/local/var/macports/build/_Users_julien_tmp_myports_sysutils_sleuthkit/sleuthkit/work/sleuthkit-4.1.3/config.log }}} fix with java variant and disable by default -- Ticket URL: <https://trac.macports.org/ticket/47102> MacPorts <https://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #46483: installation stopped accidentally
by MacPorts 30 Sep '15

30 Sep '15

#46483: installation stopped accidentally -------------------------------+-------------------------------- Reporter: pritish.naik.04@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: -------------------------------+-------------------------------- pritishs-MacBook-Pro-3:~ pritish04$ sudo port install netcdf-fortran ---> Computing dependencies for netcdf-fortran ---> Dependencies to be installed: libgcc cctools llvm-3.5 cloog gmp isl gcc_select ld64 libmpc mpfr ---> Extracting llvm-3.5 Error: org.macports.extract for port llvm-3.5 returned: Failed to locate 'xz' in path: '/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin' or at its MacPorts configuration time location, did you move it? Error: Failed to install llvm-3.5 Please see the log file for port llvm-3.5 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.5/llvm-3.5/main.log Error: The following dependencies were not installed: libgcc cctools llvm-3.5 cloog gmp isl gcc_select ld64 libmpc mpfr To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port netcdf-fortran failed -- Ticket URL: <https://trac.macports.org/ticket/46483> MacPorts <https://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #45737: dbus +no_root deleted my root account on MacOSX 10.5.8
by MacPorts 30 Sep '15

30 Sep '15

#45737: dbus +no_root deleted my root account on MacOSX 10.5.8 ------------------------+-------------------------------- Reporter: newchief@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.2 Keywords: | Port: ------------------------+-------------------------------- Although installation of dbus with +no_root use flag ended with error message that +no_root should not be used on my system, still actions were taken! my "System Administrator (root)" user with uid 0 was replaced by "Message Bus (root)" with uid 503. As a result, I couldn't do "sudo" anymore! Apart from shell commands that require root, all other system administrative operations seem to work. I deleted "Message Bus (root)" user from list of users being logged as my usual user (which is Administrator of this system). Now sudo says there's no root user entry in password file (well, root IS listed in /etc/passwd file, but I guess it is not where MacOSX keeps user info). System is doomed, wihout sudo, no macports anymore. -- Ticket URL: <https://trac.macports.org/ticket/45737> MacPorts <https://www.macports.org/> Ports system for OS X

1 13

[MacPorts] #46733: Multiple definitons of flock TCL command cause problems, e.g., with restore_ports.tcl
by MacPorts 30 Sep '15

30 Sep '15

#46733: Multiple definitons of flock TCL command cause problems, e.g., with restore_ports.tcl --------------------+-------------------------------- Reporter: mta@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.99 Keywords: | Port: --------------------+-------------------------------- When I ran restore_ports.tcl after upgrading to Yosemite it failed with the error {{{ expected integer but got "-exclusive" obtaining lock on /opt/local/var/macports/registry/.registry.lock while executing "registry::exclusive_lock" (procedure "mportexec" line 32) invoked from within "mportexec $workername $install_target" Unable to execute target 'install' for port 'fftw-3-single': expected integer but got "-exclusive" obtaining lock on /opt/local/var/macports/registry/.registry.lock while executing "install_ports $operationList" (file "restore_ports/restore_ports.tcl" line 300) }}} I tracked this down to the fact that there are two definitions of the flock TCL command installed as part of MacPorts. One is defined in TclX_FlockObjCmd which is in base/vendor/tclx8.4/generic/tclXflock.c. The other is defined in FlockCmd which is in base/src/pextlib1.0/flock.c. Macports seems to want, and get, the latter one. For some reason restore_ports sometimes, but not always, gets the other. Commenting out the call to TclX_FlockInit in Tclxcmd_Init which is in base/vendor/tclx8.4/generic/tclXinit.c seems to have fixed the problem. Unfortunately this isn't all that easy to do as part of the build since these files are installed unchanged from vendor archives. Perhaps a new archive with the appropriate change needs to be part of the MacPorts package. -- Ticket URL: <https://trac.macports.org/ticket/46733> MacPorts <https://www.macports.org/> Ports system for OS X

1 5