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

[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

[MacPorts] #48997: py34-numpy incompatible subtype on Mac OS X Tiger G3
by MacPorts 30 Sep '15

30 Sep '15

#48997: py34-numpy incompatible subtype on Mac OS X Tiger G3 ----------------------------+-------------------------------- Reporter: benoit.rivet@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: ----------------------------+-------------------------------- I've been trying to install numpy, scipy and matplotlib for python3.4 on a G3 ibook running Mac OS X.4. py34-scipy does not build yet (and py34-matplotlib requires py34-pyobjc-cocoa which won't compile on G3); however, investigating the scipy install bug led me to discover that, though py34-numpy seems to build successfully, I can't use it on my G3 ibook. Precisely : {{{ cd /opt/local/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4 /site-packages/numpy/ lipo -info */*.so }}} gives the following results : {{{ Non-fat file: core/_dotblas.so is architecture: ppc7400 Non-fat file: core/_dummy.so is architecture: ppc Non-fat file: core/multiarray.so is architecture: ppc Non-fat file: core/multiarray_tests.so is architecture: ppc Non-fat file: core/operand_flag_tests.so is architecture: ppc Non-fat file: core/scalarmath.so is architecture: ppc Non-fat file: core/struct_ufunc_test.so is architecture: ppc Non-fat file: core/test_rational.so is architecture: ppc Non-fat file: core/umath.so is architecture: ppc Non-fat file: core/umath_tests.so is architecture: ppc Non-fat file: fft/fftpack_lite.so is architecture: ppc Non-fat file: lib/_compiled_base.so is architecture: ppc Non-fat file: linalg/_umath_linalg.so is architecture: ppc7400 Non-fat file: linalg/lapack_lite.so is architecture: ppc7400 Non-fat file: random/mtrand.so is architecture: ppc }}} -- Ticket URL: <https://trac.macports.org/ticket/48997> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #47283: Backslashes in file names in destroot cause activate to fail
by MacPorts 30 Sep '15

30 Sep '15

#47283: Backslashes in file names in destroot cause activate to fail ---------------------------------+-------------------------------- Reporter: jpo@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.3 Keywords: backslash, activate | Port: ---------------------------------+-------------------------------- Seems like a simple enough fix for anyone who is familiar with TCL and the base plumbing. I'm not unfortunately. Consider the following: {{{ PortSystem 1.0 name backslash-test version 1 categories devel platforms darwin description tests backslashes in filenames for the activate target fetch {} checksum {} use_configure no build {} destroot { touch "${destroot}${prefix}/share/back\\slash" } }}} Which produces the following results {{{ $ sudo port destroot backslash-test ---> Fetching distfiles for backslash-test ---> Verifying checksums for backslash-test ---> Extracting backslash-test ---> Configuring backslash-test ---> Building backslash-test ---> Staging backslash-test into destroot $ find backslash-test -type f backslash-test/work/.macports.backslash-test.state backslash-test/work/destroot/opt/local/share/back\slash $ sudo port activate backslash-test $ sudo port install backslash-test ---> Activating backslash-test @1_0 Error: org.macports.activate for port backslash-test returned: Image error: Source file /opt/local/var/macports/software/backslash- test/mpextractFapBvhDF/opt/local/share/back lash does not appear to exist (cannot lstat it). Unable to activate port backslash-test. Please see the log file for port backslash-test for details: /opt/local/var/macports/logs /_Volumes_case_src_macports_devel_backslash-test/backslash-test/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port backslash-test failed }}} I've attached a full log of an install of the above portfile from a clean state. -- Ticket URL: <https://trac.macports.org/ticket/47283> MacPorts <https://www.macports.org/> Ports system for OS X

1 11

[MacPorts] #48887: ssdeep: update to 2.13
by MacPorts 30 Sep '15

30 Sep '15

#48887: ssdeep: update to 2.13 --------------------------+----------------------------- Reporter: ryandesign@… | Owner: jessekornblum@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: ssdeep --------------------------+----------------------------- {{{ $ port livecheck ssdeep ssdeep seems to have been updated (port version: 2.10, new version: 2.13) }}} -- Ticket URL: <https://trac.macports.org/ticket/48887> MacPorts <https://www.macports.org/> Ports system for OS X

1 6

[MacPorts] #49003: libomp should be built for both i386 and x86_64
by MacPorts 30 Sep '15

30 Sep '15

#49003: libomp should be built for both i386 and x86_64 -----------------------------------+-------------------------------- Reporter: howarth.at.macports@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: libomp -----------------------------------+-------------------------------- The attached Portfile diff updates libomp to the r248588 to pick up the new lit-based test suite support for running 'check-libomp' as well as appends -DLIBOMP_OSX_ARCHITECTURES="x86_64;i386" to the cmake flags to build the fat libomp supporting both i386 and x86_64 targets. % file libomp.dylib libomp.dylib: Mach-O universal binary with 2 architectures libomp.dylib (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64 libomp.dylib (for architecture i386): Mach-O dynamically linked shared library i386 -- Ticket URL: <https://trac.macports.org/ticket/49003> MacPorts <https://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #48987: Mythtv port file checksum problem
by MacPorts 30 Sep '15

30 Sep '15

#48987: Mythtv port file checksum problem ------------------------+-------------------------------- Reporter: gsulsh57@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: mythtv-core.27 ------------------------+-------------------------------- --> Computing dependencies for mythtv-core.27 ---> Verifying checksums for mythtv-core.27 Error: Checksum (rmd160) mismatch for mythtv-e9b577d3.tar.gz Error: Checksum (sha256) mismatch for mythtv-e9b577d3.tar.gz Error: org.macports.checksum for port mythtv-core.27 returned: Unable to verify file checksums Please see the log file for port mythtv-core.27 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_multimedia_mythtv-core.27/mythtv- core.27/main.log Error: Unable to upgrade port: 1 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets -- Ticket URL: <https://trac.macports.org/ticket/48987> MacPorts <https://www.macports.org/> Ports system for OS X

1 8

[MacPorts] #48759: llvm-3.7: Update to release and add +openmp
by MacPorts 29 Sep '15

29 Sep '15

#48759: llvm-3.7: Update to release and add +openmp -------------------------+------------------------ Reporter: eborisch@… | Owner: jeremyhu@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: clang-3.7 -------------------------+------------------------ (Note) This discussion started on mailing list while trac was offline. https://lists.macosforge.org/pipermail/macports- dev/2015-September/031349.html Attached are a Portfile patch and patchfile to add OpenMP support to clang-3.7 as well as update llvm/clang to the 3.7.0 release. The openmp-locations.patch adds -L<prefix>/lib/libomp and -I<prefix>/include/libomp to the appropriate compilation commands in tools/clang/lib/Driver/Tools.cpp such that, when combined with configure option (--with-clang-default-openmp-runtime=libomp), 'clang[++] -fopenmp' will 'just work'. I've updated (r139987) libomp to install into <prefix>(include|lib)/libomp/ such that the impact to compilation is minimized (by not using -I<prefix>/include and -L<prefix>/lib directly). Please review and comment. -- Ticket URL: <https://trac.macports.org/ticket/48759> MacPorts <https://www.macports.org/> Ports system for OS X

1 9

[MacPorts] #49000: gimp2 will not build - fails while trying to create cursors: can't recognize source png
by MacPorts 29 Sep '15

29 Sep '15

#49000: gimp2 will not build - fails while trying to create cursors: can't recognize source png ----------------------+-------------------------------- Reporter: briank@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: cursor | Port: gimp2 ----------------------+-------------------------------- After having just done a `selfupdate` and `upgrade outdated`, I'm trying to install ufraw which requires gimp2. I didn't previously have gimp installed. After the compilation fail, I tried to `sudo port clean --all gimp2` and then reinstall, but the error remains the same. From the install log: {{{ tool-text-bw.png tool-zoom.png tool-zoom-bw.png; do \ :info:build echo $image | \ :info:build sed -e 's|.*/||' -e 's|-|_|g' -e 's|\.png$||' >> tool-cursors.list; \ :info:build echo " ./$image" >> tool-cursors.list; \ :info:build done ) :info:build ( rm -f color-picker-cursors.list; \ :info:build for image in cursor-color-picker.png cursor-color- picker-bw.png; do \ :info:build echo $image | \ :info:build sed -e 's|.*/||' -e 's|-|_|g' -e 's|\.png$||' >> color-picker-cursors.list; \ :info:build echo " ./$image" >> color-picker-cursors.list; \ :info:build done ) :info:build /opt/local/bin/gdk-pixbuf-csource --raw --build-list `cat color-picker-cursors.list` > gimp-color-picker-cursors.h :info:build failed to load "./cursor-color-picker.png": Couldn't recognize the image file format for file './cursor-color-picker.png' :info:build make[2]: *** [gimp-color-picker-cursors.h] Error 1 :info:build make[2]: *** Waiting for unfinished jobs.... :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_gimp2/gimp2/work/gimp-2.8.14/cursors' :info:build make[1]: *** [all-recursive] Error 1 }}} I attempt to run the gdk-pixbuf-csource command myself, but still get the same problem. In the error message (both when run by hand or when done via ports), it complains about the file `cursor-color-picker.png`. I can view that file with Preview - it looks like a color picker. I can identify the file with ports' ImageMagick. Because I just updated, I have the most recent port of libpng if that matters: {{{ $ port installed libpng The following ports are currently installed: libpng @1.6.18_0 (active) }}} Install log attached -- Ticket URL: <https://trac.macports.org/ticket/49000> MacPorts <https://www.macports.org/> Ports system for OS X

1 1

Re: [MacPorts] #29393: gdk-pixbuf2: loader does not recognize apple-red.png, thus gtk2 does not build
by MacPorts 29 Sep '15

29 Sep '15

#29393: gdk-pixbuf2: loader does not recognize apple-red.png, thus gtk2 does not build -------------------------------+---------------------- Reporter: mvondavier@… | Owner: devans@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Resolution: fixed | Keywords: Port: gdk-pixbuf2 gtk2 | -------------------------------+---------------------- Changes (by ryandesign@…): * cc: ryandesign@… (added) Comment: Replying to [comment:14 egall@…]: > Replying to [comment:13 larryv@…]: > > Replying to [comment:12 egall@…]: > > > When were these patches removed? > > > > r91990 > > Thanks. Anyways, hm... Ryan didn't seem to mention why he removed them... I'm assuming it's because they must've been integrated upstream or something? That is what I am assuming as well, but it is 2 years ago now and I don't remember. -- Ticket URL: <https://trac.macports.org/ticket/29393#comment:15> MacPorts <https://www.macports.org/> Ports system for OS X

1 0