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

[MacPorts] #49721: dangerous bug in Qt5
by MacPorts 16 Jun '16

16 Jun '16

#49721: dangerous bug in Qt5 -------------------------+-------------------------------- Reporter: rjvbertin@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: qt5 -------------------------+-------------------------------- Last week I ran into a dangerous bug in Qt5, as a result of which I had to restore a large part of /Applications from backup. The bug is in QtCore::QStandardPaths (QSP) which provides applications with a way to obtain the paths to a range of standard locations, in readable ("system") and writable ("user") form. The class also has a switch to put it into testing mode that changes the returned locations, intended for use in unittests/autotests so that they don't overwrite or delete anything in the actual locations. On OS X, QSP returns locations that are compliant with the OS X way of doing things (app. data into ~/Library/Application Support, for instance) and App Store rules. For the `ApplicationsLocation` it returns `/Applications`, which seems reasonable (but in fact has nothing to do with the role of the ApplicationsLocation on Linux). This location makes no difference between readable and writable, and more importantly, not either between regular and testing mode. As a result, software tests that verify functionality involving reading and writing from ApplicationsLocation will - attempt to get the testing ApplicationsLocation - store files there, do stuff with them - cleanup afterwards The code that wreaked havoc on my machine did the cleanup with a `removeDir(ApplicationsLocation)`, in other words, `rm -rf /Applications`. Evidently it didn't print exactly what it was doing, it just seemed to hang (fortunately I have an HDD, not an SDD). (And of course I have since reverified all permissions in /Applications.) I reported the bug upstreams, but at the moment any fixing appears to be blocked by a single Qt dev, and a fix isn't likely to be included anytime soon anyway (5.7, maybe). I did include a fix in the QSP patch of my own [ticket:48967 port:qt5-kde], of course. I did run into this problem while developing a port, but I don't think there is much risk with published ports. `port test` probably doesn't run with elevated privileges, and port maintainers should just check any (auto)tests or keep/set `test.run no`. However, anyone using the installed Qt5 SDK should be aware of the risk. -- Ticket URL: <https://trac.macports.org/ticket/49721> MacPorts <https://www.macports.org/> Ports system for OS X

1 16

[MacPorts] #51618: GLFW3.2 has wrong lib dir when building with
by MacPorts 16 Jun '16

16 Jun '16

#51618: GLFW3.2 has wrong lib dir when building with -----------------------------------+-------------------------------- Reporter: sakari@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.3.4 Keywords: library,build,linking | Port: glfw -----------------------------------+-------------------------------- I just updated to GLFW 3.2 release from the previous one. Now when building my project, even when using pkg-config to get the correct library directories, the resulting binary points to lib/libglfw.3.dylib (compatibility version 3.0.0, current version 3.2.0) When obviously, it should point to '/opt/local/lib' pkg-config gives the correct info: pkg-config --libs glfw3 -L/opt/local/lib -lglfw And linkin works, but when I try to run my resulting binary, dyld: Library not loaded: lib/libglfw.3.dylib Referenced from: /Users/sakari/dvl/geometrify/geometrify/src/build/geometrify Reason: image not found fish: “build/geometrify -s scripts/t...” terminated by signal SIGTRAP (Trace or breakpoint trap) I can fix this temporarily easily of course, but I have no idea why this happens, maybe the path is wrong in the build process ? -- Ticket URL: <https://trac.macports.org/ticket/51618> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #51400: New port: rtl_433
by MacPorts 16 Jun '16

16 Jun '16

#51400: New port: rtl_433 ------------------------+-------------------------------- Reporter: kpreid@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: rtl_433 ------------------------+-------------------------------- "rtl_433 turns your Realtek RTL2832 based DVB dongle into a 433.92 MHz generic data receiver" Trivial portfile, first one I've submitted; let me know if I'm doing anything even slightly wrong. -- Ticket URL: <https://trac.macports.org/ticket/51400> MacPorts <https://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #51540: selfupdate failed: command execution failed
by MacPorts 16 Jun '16

16 Jun '16

#51540: selfupdate failed: command execution failed ------------------------+-------------------------------- Reporter: zmotiv@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: selfupdate | Port: ------------------------+-------------------------------- Machine is Mac laptop running El Capitan 10.11.2 '''Steps''' After initial install of Mac Ports, I opened XQuartz and ran the command via sudo mode port -d selfupdate '''Issue''' An error occurred: "command Execution failed" '''Steps''' I ran the command again in debug mode '''Issue''' DEBUG: Error synchronizing MacPorts sources: command execution failed while executing "macports::selfupdate [array get global_options] base_updated" Error: Error synchronizing MacPorts sources: command execution failed ++ '''Full terminal message error''' port -v selfupdate ---> Updating MacPorts base sources using rsync receiving file list ... done rsync: mkstemp "/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/.base.tar.QmfBdr" failed: Permission denied (13) inflate returned -3 (19 bytes) rsync error: error in rsync protocol data stream (code 12) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-47/rsync/token.c(419) [receiver=2.6.9] rsync: connection unexpectedly closed (31 bytes received so far) [generator] rsync error: error in rsync protocol data stream (code 12) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-47/rsync/io.c(453) [generator=2.6.9] Command failed: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs Exit code: 12 Error: Error synchronizing MacPorts sources: 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 synchronizing MacPorts sources: command execution failed port -d selfupdate DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs ---> Updating MacPorts base sources using rsync receiving file list ... done rsync: mkstemp "/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/.base.tar.Pmphrh" failed: Permission denied (13) inflate returned -3 (19 bytes) rsync error: error in rsync protocol data stream (code 12) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-47/rsync/token.c(419) [receiver=2.6.9] rsync: connection unexpectedly closed (31 bytes received so far) [generator] rsync error: error in rsync protocol data stream (code 12) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-47/rsync/io.c(453) [generator=2.6.9] Command failed: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs Exit code: 12 DEBUG: Error synchronizing MacPorts sources: command execution failed while executing "macports::selfupdate [array get global_options] base_updated" Error: Error synchronizing MacPorts sources: 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 synchronizing MacPorts sources: command execution failed -- Ticket URL: <https://trac.macports.org/ticket/51540> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #50982: openjpen won't install on Mac OS 10.11.4 El Capitan
by MacPorts 16 Jun '16

16 Jun '16

#50982: openjpen won't install on Mac OS 10.11.4 El Capitan --------------------------------+-------------------------------- Reporter: andrzejsemeniuk@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: openjpeg, platform | Port: imagemagick --------------------------------+-------------------------------- I get "unsupported platform" error when installing openjpen in log while trying to install ImageMagick: :info:build cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_openjpeg/openjpeg/work/build/src/lib/openjp2 && /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -Dopenjp2_EXPORTS -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_openjpeg/openjpeg/work/build/src/lib/openjp2 -pipe -Os -DNDEBUG -arch x86_64 -mmacosx-version-min=10.11 -fPIC -o CMakeFiles/openjp2.dir/bio.c.o -c /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_openjpeg/openjpeg/work/openjpeg-2.1.0/src/lib/openjp2/bio.c :info:build In file included from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_openjpeg/openjpeg/work/openjpeg-2.1.0/src/lib/openjp2/t1_generate_luts.c:39: :info:build In file included from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_openjpeg/openjpeg/work/openjpeg-2.1.0/src/lib/openjp2/opj_includes.h:139: :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_openjpeg/openjpeg/work/openjpeg-2.1.0/src/lib/openjp2/opj_inttypes.h:44:2: error: unsupported platform :info:build #error unsupported platform :info:build ^ -- Ticket URL: <https://trac.macports.org/ticket/50982> MacPorts <https://www.macports.org/> Ports system for OS X

1 7

[MacPorts] #51640: freecad: version 0.16 (and pretest for 0.17) is available
by MacPorts 16 Jun '16

16 Jun '16

#51640: freecad: version 0.16 (and pretest for 0.17) is available ---------------------+---------------------------- Reporter: mojca@… | Owner: mark.brethen@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: freecad ---------------------+---------------------------- A new version of FreeCAD is available (and most likely no longer depends on Fortran). It would be nice to update the port. -- Ticket URL: <https://trac.macports.org/ticket/51640> MacPorts <https://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #51622: emacs-app-devel distfiles do not appear in mirrors.
by MacPorts 16 Jun '16

16 Jun '16

#51622: emacs-app-devel distfiles do not appear in mirrors. ---------------------------------+-------------------------------- Reporter: joshua.kordani@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: distfiles not found | Port: emacs-app-devel ---------------------------------+-------------------------------- Fresh install of macports on a fresh 10.11 I have installed other ports successfully so far, and emacs-app-devel appares in port info, but installing with -vvv hangs at "fetching distfiles" upon inspecting the urls present in the log, there is no entry for emacs-app-devel. salient portion of log copied below: {{{ ---> Attempting to fetch emacs-app-devel-20151029_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/emacs-app-devel % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0---> Attempting to fetch emacs-app-devel- 20151029_0.darwin_15.x86_64.tbz2 from http://lil.fr.packages.macports.org /emacs-app-devel % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0---> Attempting to fetch emacs-app-devel- 20151029_0.darwin_15.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/emacs-app- devel % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 305 100 305 0 0 174 0 0:00:01 0:00:01 --:--:-- 174 ---> Fetching distfiles for emacs-app-devel }}} -- Ticket URL: <https://trac.macports.org/ticket/51622> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #51609: ldas-tools: update to 2.5.0, split into separate ports
by MacPorts 16 Jun '16

16 Jun '16

#51609: ldas-tools: update to 2.5.0, split into separate ports --------------------------+------------------------ Reporter: ryandesign@… | Owner: ed.maros@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: ldas-tools --------------------------+------------------------ ldas-tools 2.5.0 was released in April 2016, and has been split into separate projects. So we probably need separate ports now for the different projects: * ldas-tools-al * ldas-tools-diskcacheAPI * ldas-tools-filters * ldas-tools-frameAPI * ldas-tools-framecpp * ldas-tools-ldasgen * ldas-tools-utilities To assist users in upgrading to this new multiple-port suite, the existing ldas-tools port could become a meta port that only installs a readme file and declares dependencies on all the other ports. The new ports which actually install the files will need to use the [wiki:PortfileRecipes#deactivatehack deactivate hack] to deactivate any already-installed ldas-tools <= 2.4.2 port. Adding these separate projects as subports of the ldas-tools port, instead of creating separate portfiles, might be worthwhile, since some code, like the homepage, master_sites, livecheck, and deactivate hack, could be shared. -- Ticket URL: <https://trac.macports.org/ticket/51609> MacPorts <https://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #51638: Update Pandoc
by MacPorts 16 Jun '16

16 Jun '16

#51638: Update Pandoc ----------------------------+-------------------------------- Reporter: jens.troeger@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: ----------------------------+-------------------------------- The current version of MacPort Pandoc 1.12.4.2, whereas the official latest version is 1.17.1. Please update. -- Ticket URL: <https://trac.macports.org/ticket/51638> MacPorts <https://www.macports.org/> Ports system for OS X

1 1

Re: [MacPorts] #42725: Use modern tools for 'port pkg' on newer OS versions
by MacPorts 16 Jun '16

16 Jun '16

#42725: Use modern tools for 'port pkg' on newer OS versions --------------------------+-------------------------------- Reporter: rob@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.2.1 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by antonbachin@…): Fixing this would be very helpful. I am building packages inside Travis build workers, which don't seem to have PackageMaker installed. They do have pkgbuild and productbuild. I suppose I can ask Travis developers to install PackageMaker in OS X images, but it seems like the right place to fix this is MacPorts. I'm not aware of any legitimate way to separately install PackageMaker without logging in as a developer from the build workers, so this is a showstopper for that process. Travis build environment summary: https://docs.travis-ci.com/user/osx-ci- environment/#OS-X-Version -- Ticket URL: <https://trac.macports.org/ticket/42725#comment:13> MacPorts <https://www.macports.org/> Ports system for OS X

1 0