From noreply at macports.org Thu Dec 1 00:43:47 2016 From: noreply at macports.org (MacPorts) Date: Wed, 30 Nov 2016 23:43:47 -0000 Subject: [MacPorts] #52703: git: git-gui crashing In-Reply-To: <041.41563308f2c85adc3d982e5601a537ca@macports.org> References: <041.41563308f2c85adc3d982e5601a537ca@macports.org> Message-ID: <056.66f12a5525c4d7cac20d4c1f06f147b6@macports.org> #52703: git: git-gui crashing ---------------------+-------------------- Reporter: mkae | Owner: ci42 Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: sierra Port: git | ---------------------+-------------------- Comment (by stevenwei): This has been reported in a few other places: http://stackoverflow.com/questions/39833961/git-gui-crashes-on-mac- os-x-sierra https://github.com/git/git-scm.com/issues/853 Seems related to a broken version of Tk 8.5 that shipped with Sierra. I worked around this by installing Tk 8.6.6 via MacPorts, and then reinstalling Git: {{{ sudo port uninstall git sudo port install tk sudo port install git }}} So far it seems to be working again. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 00:52:11 2016 From: noreply at macports.org (MacPorts) Date: Wed, 30 Nov 2016 23:52:11 -0000 Subject: [MacPorts] #52982: p7zip @16.02: fix CVE-2016-9296 In-Reply-To: <041.ca2f9857b6e52157c083a5b403bc256f@macports.org> References: <041.ca2f9857b6e52157c083a5b403bc256f@macports.org> Message-ID: <056.8defbf650d1bef74b1adab8b210fd7db@macports.org> #52982: p7zip @16.02: fix CVE-2016-9296 ---------------------+---------------------- Reporter: l2dy | Owner: larryv Type: defect | Status: accepted Priority: High | Milestone: Component: ports | Version: Resolution: | Keywords: Port: p7zip | ---------------------+---------------------- Changes (by larryv): * cc: stuartwesterman (added) * owner: stuartwesterman => larryv * status: assigned => accepted * priority: Normal => High -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 01:35:58 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 00:35:58 -0000 Subject: [MacPorts] #52982: p7zip @16.02: fix CVE-2016-9296 In-Reply-To: <041.ca2f9857b6e52157c083a5b403bc256f@macports.org> References: <041.ca2f9857b6e52157c083a5b403bc256f@macports.org> Message-ID: <056.6383b41d75d28fc721f8848ecf8416c5@macports.org> #52982: p7zip @16.02: fix CVE-2016-9296 ---------------------+-------------------- Reporter: l2dy | Owner: larryv Type: defect | Status: closed Priority: High | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: p7zip | ---------------------+-------------------- Changes (by larryv): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"63e2886d7c5bbdc3ac84e6a67751743d6319a4bc/macports-ports" 63e2886/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="63e2886d7c5bbdc3ac84e6a67751743d6319a4bc" p7zip: Avoid potential null pointer dereference Backported from 7-Zip 16.03 for Windows, but p7zip is still on 16.02. Closes https://trac.macports.org/ticket/52982 (maintainer override to address security vulnerability). }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 02:09:46 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 01:09:46 -0000 Subject: [MacPorts] #52985: buildbot: dependency calculation sometimes prohibitively expensive Message-ID: <042.82c02616dc3faf0568ebc12b946c1b94@macports.org> #52985: buildbot: dependency calculation sometimes prohibitively expensive ----------------------------+--------------------- Reporter: mojca | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: 2.3.5 Keywords: buildbot | Port: ----------------------------+--------------------- Sometimes even the presence of failcache doesn't prevent the build jobs to finish in a timely manner. See for example [https://build.macports.org/builders/ports-10 .5_ppc_legacy-builder/builds/11578 this build] where `install-dependency` needed 45 minutes to calculate dependencies before it was interrupted by the build mater. That time would be more than sufficient to actually install all other dependencies :) Some people say that the time increases with dependencies in a non-linear (quadratic?) way. This ticket might belong to base, not sure. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 02:15:18 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 01:15:18 -0000 Subject: [MacPorts] #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc Message-ID: <042.20cc8359ea93c50d17385aa98946848c@macports.org> #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc ----------------------------+--------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Keywords: buildbot | Port: ----------------------------+--------------------- The 10.6-i386 buildbot avoids building many packages: {{{ #!tcl if [[ $exclude -eq 0 && "${os_version}" = "10.6" && "${is_64bit_capable}" = "0" ]]; then supported_archs=$("${option_prefix}/bin/port-tclsh" "${thisdir}/tools /supported-archs.tcl" "${port}") if [[ -n "${supported_archs}" && ! ("${supported_archs}" == *"x86_64"* && "${supported_archs}" == *"i386"*) ]]; then exclude=1 exclude_reasons+=("the ${os_version}_x86_64 builder will build it") fi fi }}} I believe that a similar strategy could be used to avoid building packages that are declared not to be supported on PPC. See [https://build.macports.org/builders/ports-10.5_ppc_legacy- builder/builds/11580/steps/install-port/logs/stdio an example] of the libvpx port which doesn't even start to build: {{{ Error: libvpx cannot be installed for the configured build_arch 'ppc' because it only supports the arch(s) 'x86_64 i386'. Error: Processing of port libvpx failed Build of 'libvpx' failed. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 02:37:01 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 01:37:01 -0000 Subject: [MacPorts] #52984: Upgrade camlp5 to 6.17 In-Reply-To: <045.ddb82586225397b126b9aaad119905ca@macports.org> References: <045.ddb82586225397b126b9aaad119905ca@macports.org> Message-ID: <060.3520e9e0d827bbe5afedde864748aa75@macports.org> #52984: Upgrade camlp5 to 6.17 -----------------------+---------------------- Reporter: pmetzger | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: haspatch Port: camlp5 | -----------------------+---------------------- Comment (by raimue): The github port group contains documentation in the [https://github.com/macports/macports- ports/blob/master/_resources/port1.0/group/github-1.0.tcl code]. There are also plenty of ports using this port group in the ports tree. The [https://guide.macports.org/chunked/reference.portgroup.html section on port groups] in the guide could include more port groups and there are plenty of open requests: #25170, #32428, #39412. Although, most port groups have good documentation inline, where it is less likely to go out of sync. Contributions to the guide are very welcome, I recently added some docs on [https://guide.macports.org/chunked/project.docs.html how the guide can be updated] by anyone. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 02:48:41 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 01:48:41 -0000 Subject: [MacPorts] #52908: Remove configure, Makefiles and other generated files from repository In-Reply-To: <047.e3f05b23b4f70cbb54f4e9dd69e7b025@macports.org> References: <047.e3f05b23b4f70cbb54f4e9dd69e7b025@macports.org> Message-ID: <062.eba4d17873b7df44566cec7b86159ee9@macports.org> #52908: Remove configure, Makefiles and other generated files from repository --------------------------+-------------------------------- Reporter: ryandesign | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.4 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by mojca): I'm also strongly in favour of keeping some generated files like `configure` in the repository as long as we can keep them up to date. (Obviously not `Makefile`, but I guess you had `Makefile.in` in mind.) The chicken-and-egg argument makes my preference even stronger. Creating & checking out tags (releases) is also more straightforward if those files are included. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 03:03:31 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 02:03:31 -0000 Subject: [MacPorts] #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc In-Reply-To: <042.20cc8359ea93c50d17385aa98946848c@macports.org> References: <042.20cc8359ea93c50d17385aa98946848c@macports.org> Message-ID: <057.27b564d10ed15f07ce60f843bcda210f@macports.org> #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Old description: > The 10.6-i386 buildbot avoids building many packages: > {{{ > #!tcl > if [[ $exclude -eq 0 && "${os_version}" = "10.6" && "${is_64bit_capable}" > = "0" ]]; then > supported_archs=$("${option_prefix}/bin/port-tclsh" "${thisdir}/tools > /supported-archs.tcl" "${port}") > if [[ -n "${supported_archs}" && ! ("${supported_archs}" == > *"x86_64"* && "${supported_archs}" == *"i386"*) ]]; then > exclude=1 > exclude_reasons+=("the ${os_version}_x86_64 builder will build > it") > fi > fi > }}} > I believe that a similar strategy could be used to avoid building > packages that are declared not to be supported on PPC. > > See [https://build.macports.org/builders/ports-10.5_ppc_legacy- > builder/builds/11580/steps/install-port/logs/stdio an example] of the > libvpx port which doesn't even start to build: > {{{ > Error: libvpx cannot be installed for the configured build_arch 'ppc' > because it only supports the arch(s) 'x86_64 i386'. > Error: Processing of port libvpx failed > Build of 'libvpx' failed. > }}} New description: The 10.6-i386 buildbot avoids building many packages: {{{ #!bash if [[ $exclude -eq 0 && "${os_version}" = "10.6" && "${is_64bit_capable}" = "0" ]]; then supported_archs=$("${option_prefix}/bin/port-tclsh" "${thisdir}/tools /supported-archs.tcl" "${port}") if [[ -n "${supported_archs}" && ! ("${supported_archs}" == *"x86_64"* && "${supported_archs}" == *"i386"*) ]]; then exclude=1 exclude_reasons+=("the ${os_version}_x86_64 builder will build it") fi fi }}} I believe that a similar strategy could be used to avoid building packages that are declared not to be supported on PPC. See [https://build.macports.org/builders/ports-10.5_ppc_legacy- builder/builds/11580/steps/install-port/logs/stdio an example] of the libvpx port which doesn't even start to build: {{{ Error: libvpx cannot be installed for the configured build_arch 'ppc' because it only supports the arch(s) 'x86_64 i386'. Error: Processing of port libvpx failed Build of 'libvpx' failed. }}} -- Comment (by larryv): Most of this fiddling should be done in the Buildbot configuration and not in mpbb. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 03:06:26 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 02:06:26 -0000 Subject: [MacPorts] #52844: Upgrade ocaml to 4.04.0 In-Reply-To: <045.a805fab4a5fcd1f92a13fbe620399494@macports.org> References: <045.a805fab4a5fcd1f92a13fbe620399494@macports.org> Message-ID: <060.35f3de7410d34b82f095fdefa6494b94@macports.org> #52844: Upgrade ocaml to 4.04.0 -----------------------+---------------------- Reporter: pmetzger | Owner: larryv Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: ocaml | -----------------------+---------------------- Changes (by larryv): * owner: mww@… => larryv * status: assigned => accepted * version: 2.3.4 => * cc: mww@… (added) Comment: Does 4.04.0 introduce any incompatibilities (compared to 4.02.2) that we should know about? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 03:18:04 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 02:18:04 -0000 Subject: [MacPorts] #52965: [Port Abandoned] usbutils In-Reply-To: <043.9d8737abf2452a0c9c427e9d1cc93905@macports.org> References: <043.9d8737abf2452a0c9c427e9d1cc93905@macports.org> Message-ID: <058.ba88c67ffebd24ec50561f9d58242f26@macports.org> #52965: [Port Abandoned] usbutils -----------------------+------------------------ Reporter: larryv | Owner: bernhard@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: usbutils | -----------------------+------------------------ Comment (by larryv): Abandoned as per the [https://guide.macports.org/chunked/project.update- policies.html#project.update-policies.abandonment policy]. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 03:42:02 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 02:42:02 -0000 Subject: [MacPorts] #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc In-Reply-To: <042.20cc8359ea93c50d17385aa98946848c@macports.org> References: <042.20cc8359ea93c50d17385aa98946848c@macports.org> Message-ID: <057.83be912409adfc96c647f4a22ed12084@macports.org> #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Comment (by mojca): (Thanks for fixing my stupid mistake.) No, I don't believe that the buildbot can possibly do that. Buildbot is just a stupid python script that doesn't know anything about ports unless we create an up-to-date database of all ports with all the required meta information on the build master ... or install MacPorts on the build master, but then it has to be able to switch between different OS versions for the portindex etc. Until we implement that, the decision about whether or not a port is installable should be done by the build slave in my opinion. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 04:02:25 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 03:02:25 -0000 Subject: [MacPorts] #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc In-Reply-To: <042.20cc8359ea93c50d17385aa98946848c@macports.org> References: <042.20cc8359ea93c50d17385aa98946848c@macports.org> Message-ID: <057.b17b8f8050e72fb23f78df49bd1346aa@macports.org> #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Comment (by larryv): The build step that invokes `mpbb list-subports` can specify the architecture(s) it can build, and mpbb can compare that to the ports’ `supported_archs` and filter appropriately. mpbb’s knowledge of which buildslaves we are running (and any limitations thereof) is needlessly tight coupling that we should eliminate. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 04:07:21 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 03:07:21 -0000 Subject: [MacPorts] #52965: [Port Abandoned] usbutils In-Reply-To: <043.9d8737abf2452a0c9c427e9d1cc93905@macports.org> References: <043.9d8737abf2452a0c9c427e9d1cc93905@macports.org> Message-ID: <058.32f90021e1865692a3786f109e908a8d@macports.org> #52965: [Port Abandoned] usbutils -----------------------+------------------------ Reporter: larryv | Owner: bernhard@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: usbutils | -----------------------+------------------------ Changes (by larryv): * status: new => closed * resolution: => fixed Comment: In [changeset:"e2d210e4f05794c881a6fdeca4be45b495154953/macports-ports" e2d210e/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="e2d210e4f05794c881a6fdeca4be45b495154953" usbutils: Rescind maintainership Closes https://trac.macports.org/ticket/52965. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 04:19:14 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 03:19:14 -0000 Subject: [MacPorts] #52844: Upgrade ocaml to 4.04.0 In-Reply-To: <045.a805fab4a5fcd1f92a13fbe620399494@macports.org> References: <045.a805fab4a5fcd1f92a13fbe620399494@macports.org> Message-ID: <060.71228f1a6e321dd8477b40479381e3e7@macports.org> #52844: Upgrade ocaml to 4.04.0 -----------------------+---------------------- Reporter: pmetzger | Owner: larryv Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: ocaml | -----------------------+---------------------- Comment (by pmetzger): I have (in parallel) also submitted an update to camlp5 that should be applied at the same time. I'm unaware of any others, though likely an update to ocaml-camlp4 would be useful as one is available. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 04:20:10 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 03:20:10 -0000 Subject: [MacPorts] #52984: Upgrade camlp5 to 6.17 In-Reply-To: <045.ddb82586225397b126b9aaad119905ca@macports.org> References: <045.ddb82586225397b126b9aaad119905ca@macports.org> Message-ID: <060.f27f195d9d8e7101da675004c653e269@macports.org> #52984: Upgrade camlp5 to 6.17 -----------------------+---------------------- Reporter: pmetzger | Owner: larryv Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: haspatch Port: camlp5 | -----------------------+---------------------- Changes (by larryv): * owner: => larryv * status: new => accepted Comment: I’ll do this at the same time as #52844. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 04:31:27 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 03:31:27 -0000 Subject: [MacPorts] #52987: octave (4.0.3) fails on texi2dvi check Message-ID: <049.4c68a01d87f052bb2890b79944795f42@macports.org> #52987: octave (4.0.3) fails on texi2dvi check --------------------------+-------------------- Reporter: claudiopolis | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: octave --------------------------+-------------------- See error below: Making install in interpreter make[3]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/work/octave-4.0.3/doc/interpreter' ./config-images.sh ../.. ../../doc/interpreter/images.mk is unchanged MAKEINFO octave.info TEXI2DVI octave.dvi /opt/local/bin/texi2dvi: TeX neither supports -recorder nor outputs \openout lines in its log file make[3]: *** [octave.dvi] Error 1 make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/work/octave-4.0.3/doc/interpreter' make[2]: *** [install-recursive] Error 1 make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/work/octave-4.0.3/doc' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/work/octave-4.0.3' make: *** [install] Error 2 make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/work/octave-4.0.3' Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/work/octave-4.0.3" && /usr/bin/make -w install DESTDIR=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/work/destroot Exit code: 2 Error: org.macports.destroot for port octave returned: command execution failed Warning: targets not executed for octave: org.macports.activate org.macports.destroot org.macports.install Error: Failed to install octave Please see the log file for port octave for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/main.log Error: The following dependencies were not installed: octave To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port octave-benchmark failed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 04:36:10 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 03:36:10 -0000 Subject: [MacPorts] #52987: octave (4.0.3) fails on texi2dvi check In-Reply-To: <049.4c68a01d87f052bb2890b79944795f42@macports.org> References: <049.4c68a01d87f052bb2890b79944795f42@macports.org> Message-ID: <064.dba7c10ad9d7b89833cab5f2825b0ef3@macports.org> #52987: octave (4.0.3) fails on texi2dvi check ---------------------------+-------------------- Reporter: claudiopolis | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: duplicate | Keywords: Port: octave | ---------------------------+-------------------- Changes (by larryv): * status: new => closed * resolution: => duplicate Old description: > See error below: > > Making install in interpreter > make[3]: Entering directory > `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/work/octave-4.0.3/doc/interpreter' > ./config-images.sh ../.. > ../../doc/interpreter/images.mk is unchanged > MAKEINFO octave.info > TEXI2DVI octave.dvi > /opt/local/bin/texi2dvi: TeX neither supports -recorder nor outputs > \openout lines in its log file > make[3]: *** [octave.dvi] Error 1 > make[3]: Leaving directory > `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/work/octave-4.0.3/doc/interpreter' > make[2]: *** [install-recursive] Error 1 > make[2]: Leaving directory > `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/work/octave-4.0.3/doc' > make[1]: *** [install-recursive] Error 1 > make[1]: Leaving directory > `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/work/octave-4.0.3' > make: *** [install] Error 2 > make: Leaving directory > `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/work/octave-4.0.3' > Command failed: cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/work/octave-4.0.3" > && /usr/bin/make -w install > DESTDIR=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/work/destroot > Exit code: 2 > Error: org.macports.destroot for port octave returned: command execution > failed > Warning: targets not executed for octave: org.macports.activate > org.macports.destroot org.macports.install > Error: Failed to install octave > Please see the log file for port octave for details: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/main.log > Error: The following dependencies were not installed: octave > To report a bug, follow the instructions in the guide: > http://guide.macports.org/#project.tickets > Error: Processing of port octave-benchmark failed New description: See error below: {{{ Making install in interpreter make[3]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/work/octave-4.0.3/doc/interpreter' ./config-images.sh ../.. ../../doc/interpreter/images.mk is unchanged MAKEINFO octave.info TEXI2DVI octave.dvi /opt/local/bin/texi2dvi: TeX neither supports -recorder nor outputs \openout lines in its log file make[3]: *** [octave.dvi] Error 1 make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/work/octave-4.0.3/doc/interpreter' make[2]: *** [install-recursive] Error 1 make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/work/octave-4.0.3/doc' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/work/octave-4.0.3' make: *** [install] Error 2 make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/work/octave-4.0.3' Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/work/octave-4.0.3" && /usr/bin/make -w install DESTDIR=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/work/destroot Exit code: 2 Error: org.macports.destroot for port octave returned: command execution failed Warning: targets not executed for octave: org.macports.activate org.macports.destroot org.macports.install Error: Failed to install octave Please see the log file for port octave for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave/octave/main.log Error: The following dependencies were not installed: octave To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port octave-benchmark failed }}} -- Comment: Probably a duplicate of #46105. As a workaround, install `latex` and `pdflatex` manually. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 04:36:46 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 03:36:46 -0000 Subject: [MacPorts] #46105: texinfo @5.2_2 has unlisted dependency on TeX In-Reply-To: <058.87b4d5eecfba33ee9ee3897544e24e91@macports.org> References: <058.87b4d5eecfba33ee9ee3897544e24e91@macports.org> Message-ID: <073.8a9b6fd1bb2e85710b236d8917504192@macports.org> #46105: texinfo @5.2_2 has unlisted dependency on TeX ------------------------+---------------------- Reporter: karsten@… | Owner: larryv Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: texinfo | ------------------------+---------------------- Changes (by larryv): * cc: claudiopolis (added) Comment: Has likely duplicate #52987. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 06:22:12 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 05:22:12 -0000 Subject: [MacPorts] #52988: the_silver_searcher @0.32.0: update to 1.0.1 Message-ID: <041.b5b3237b1fa0fc182be78c96bd22586c@macports.org> #52988: the_silver_searcher @0.32.0: update to 1.0.1 --------------------+--------------------------------- Reporter: l2dy | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: the_silver_searcher --------------------+--------------------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 06:36:36 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 05:36:36 -0000 Subject: [MacPorts] #52987: octave (4.0.3) fails on texi2dvi check In-Reply-To: <049.4c68a01d87f052bb2890b79944795f42@macports.org> References: <049.4c68a01d87f052bb2890b79944795f42@macports.org> Message-ID: <064.8a2f7bcd962087ec00823478b040c9bf@macports.org> #52987: octave (4.0.3) fails on texi2dvi check ---------------------------+-------------------- Reporter: claudiopolis | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: duplicate | Keywords: Port: octave | ---------------------------+-------------------- Comment (by claudiopolis): Thanks. Workaround does the trick. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 09:04:19 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 08:04:19 -0000 Subject: [MacPorts] #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc In-Reply-To: <042.20cc8359ea93c50d17385aa98946848c@macports.org> References: <042.20cc8359ea93c50d17385aa98946848c@macports.org> Message-ID: <057.72428767b0bddcc3063e313db5dc5e25@macports.org> #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Comment (by mojca): I only partially agree. The above mentioned step only avoids building ports like `wine` on 10.6-i386 because 10.6-x86_64 already builds it and you cannot delegate the job of building wine to the i386 builder as you wouldn't get all the dependencies built universally. It's not really clear to me how you would simplify the code by telling the i386 builder to build for i386. Just about the only thing that could be simplified is the need for testing: {{{ #!bash is_64bit_capable="$(sysctl -n hw.cpu64bit_capable)" ... if [[ ... "${is_64bit_capable}" = "0"... ]]; then }}} For 10.5 we would currently run `uname -m`. With your suggested changes we would have to call {{{ mpbb list-subports -arch ppc ... }}} or provide an environmental variable, but I don't see how that simplifies things in any way. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 10:13:16 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 09:13:16 -0000 Subject: [MacPorts] #52982: p7zip @16.02: fix CVE-2016-9296 In-Reply-To: <041.ca2f9857b6e52157c083a5b403bc256f@macports.org> References: <041.ca2f9857b6e52157c083a5b403bc256f@macports.org> Message-ID: <056.88a5efc2e91c4eb5b73143fdba27f7e3@macports.org> #52982: p7zip @16.02: fix CVE-2016-9296 ---------------------+-------------------- Reporter: l2dy | Owner: larryv Type: defect | Status: closed Priority: High | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: p7zip | ---------------------+-------------------- Comment (by stuartwesterman): Woohoo! Thank you! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 10:54:43 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 09:54:43 -0000 Subject: [MacPorts] #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc In-Reply-To: <042.20cc8359ea93c50d17385aa98946848c@macports.org> References: <042.20cc8359ea93c50d17385aa98946848c@macports.org> Message-ID: <057.b122b39baab7a7771a53a51eb72091e3@macports.org> #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Comment (by jmroot): One note: `uname -m` is not correct here (or in the buildbot README.md). It tells you the architecture of the kernel, and K64 is sufficient but not necessary for running 64-bit programs. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 11:35:33 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 10:35:33 -0000 Subject: [MacPorts] #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc In-Reply-To: <042.20cc8359ea93c50d17385aa98946848c@macports.org> References: <042.20cc8359ea93c50d17385aa98946848c@macports.org> Message-ID: <057.3a5142e8ff5f1c7388388305018f697e@macports.org> #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Comment (by mojca): That's already nitpicking. I'm talking about determining whether computer's architecture is PPC. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 11:45:24 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 10:45:24 -0000 Subject: [MacPorts] #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc In-Reply-To: <042.20cc8359ea93c50d17385aa98946848c@macports.org> References: <042.20cc8359ea93c50d17385aa98946848c@macports.org> Message-ID: <057.57a3ba093b599bf1bdbd41786bfd3384@macports.org> #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Comment (by mojca): The problem with `tools/supported-archs.tcl` is that it only returns something when the port specifies `supported_archs` explicitly. So one can get `i386 ppc` or `i386 x86_64` or `i386 ppc x86_64`, ... or `noarch` or an empty string as the answer. I'm not sure how to reliably tell whether a port builds on PPC. Just guessing: * If the answer is not empty and not `noarch`, then `ppc` must be present, else skip building the port. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 11:55:11 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 10:55:11 -0000 Subject: [MacPorts] #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc In-Reply-To: <042.20cc8359ea93c50d17385aa98946848c@macports.org> References: <042.20cc8359ea93c50d17385aa98946848c@macports.org> Message-ID: <057.c9fe7072bec3a8d6afc094058185f610@macports.org> #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Comment (by mojca): Off-topic. I just wanted to add one strange observation: {{{ > time /opt/local/bin/port-tclsh ./tools/supported-archs.tcl wine i386 real 0m26.122s }}} What's the deal with the super long waiting time? Sure, I don't have SSD yet and any subsequent run is much faster, but I'm still completely puzzled why it was so long in the first place (and we are experiencing super long time for trivial tasks on the buildbot all the time). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 12:42:26 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 11:42:26 -0000 Subject: [MacPorts] #52989: buildbot: allow building 'pseudoports' Message-ID: <042.6cfc157f40fe588b534a4b9ad4fd7128@macports.org> #52989: buildbot: allow building 'pseudoports' ----------------------------+--------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Keywords: buildbot | Port: ----------------------------+--------------------- I would find it useful if we would allow building a subset of ports with simple expressions, so that we could rebuild all ports (either in one go or incrementally) every now and then. In particular it would be helpful if we could build `category:shells` or `all` or similar things. We are currently using the following expression to list the subports: {{{ port info --index --line --name wxWidgets-3.0 subportof:wxWidgets-3.0 }}} The following works: {{{ port info --index --line --name 'category:shells' }}} but {{{ port info --index --line --name 'category:shells' subportof:'category:shells' port info --index --line --name all subportof:all }}} doesn't. What would be needed to get this working? After inspecting the source code I see that a list of ports is generated with {{{ #!bash for p in "$@"; do print-subports "$p" && success=1 done }}} and `print-subports` does {{{ #!bash ports=$("${option_prefix}/bin/port" -q info --index --line --name "${portname}" "subportof:${portname}" 2>/dev/null) || return }}} which fails if the argument of `subportof:` is not a proper port name. One possible solution would be to run `port info` first, for example {{{ > port info --index --line --name maintainer:mojca and category:math aquaterm gnuplot libcerf }}} or {{{ > port info --index --line --name wxWidgets-2.8 wxWidgets-3.0 wxWidgets-2.8 wxWidgets-3.0 }}} and then iterate over that result rather than on the list of arguments (three in the example `maintainer:mojca and category:math`) to print all subports. At the same time we should be a bit careful about code injections to prevent logged in users from executing arbitrary shell code on the build slaves. Any thoughts? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 12:48:56 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 11:48:56 -0000 Subject: [MacPorts] #52989: buildbot: allow building 'pseudoports' In-Reply-To: <042.6cfc157f40fe588b534a4b9ad4fd7128@macports.org> References: <042.6cfc157f40fe588b534a4b9ad4fd7128@macports.org> Message-ID: <057.fedef42b851093552bd22acb3ac13451@macports.org> #52989: buildbot: allow building 'pseudoports' -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Description changed by mojca: Old description: > I would find it useful if we would allow building a subset of ports with > simple expressions, so that we could rebuild all ports (either in one go > or incrementally) every now and then. > > In particular it would be helpful if we could build `category:shells` or > `all` or similar things. > > We are currently using the following expression to list the subports: > {{{ > port info --index --line --name wxWidgets-3.0 subportof:wxWidgets-3.0 > }}} > > The following works: > {{{ > port info --index --line --name 'category:shells' > }}} > but > {{{ > port info --index --line --name 'category:shells' > subportof:'category:shells' > port info --index --line --name all subportof:all > }}} > doesn't. > > What would be needed to get this working? > > After inspecting the source code I see that a list of ports is generated > with > {{{ > #!bash > for p in "$@"; do > print-subports "$p" && success=1 > done > }}} > and `print-subports` does > {{{ > #!bash > ports=$("${option_prefix}/bin/port" -q info --index --line --name > "${portname}" "subportof:${portname}" 2>/dev/null) || return > }}} > which fails if the argument of `subportof:` is not a proper port name. > One possible solution would be to run `port info` first, for example > {{{ > > port info --index --line --name maintainer:mojca and category:math > aquaterm > gnuplot > libcerf > }}} > or > {{{ > > port info --index --line --name wxWidgets-2.8 wxWidgets-3.0 > wxWidgets-2.8 > wxWidgets-3.0 > }}} > and then iterate over that result rather than on the list of arguments > (three in the example `maintainer:mojca and category:math`) to print all > subports. > > At the same time we should be a bit careful about code injections to > prevent logged in users from executing arbitrary shell code on the build > slaves. > > Any thoughts? New description: I would find it useful if we would allow building a subset of ports with simple expressions, so that we could rebuild all ports (either in one go or incrementally) every now and then. In particular it would be helpful if we could build `category:shells` or `all` or similar things. We are currently using the following expression to list the subports: {{{ port info --index --line --name wxWidgets-3.0 subportof:wxWidgets-3.0 }}} The following works: {{{ port info --index --line --name 'category:shells' }}} but {{{ port info --index --line --name 'category:shells' subportof:'category:shells' port info --index --line --name all subportof:all }}} doesn't. What would be needed to get this working? After inspecting the source code I see that a list of ports is generated with {{{ #!bash for p in "$@"; do print-subports "$p" && success=1 done }}} and `print-subports` does {{{ #!bash ports=$("${option_prefix}/bin/port" -q info --index --line --name "${portname}" "subportof:${portname}" 2>/dev/null) || return }}} which fails if the argument of `subportof:` is not a proper port name. One possible solution would be to run `port info` first, for example {{{ > port info --index --line --name maintainer:mojca and category:math aquaterm gnuplot libcerf }}} or {{{ > port info --index --line --name wxWidgets-2.8 wxWidgets-3.0 wxWidgets-2.8 wxWidgets-3.0 }}} and then iterate over that result rather than on the list of arguments (three in the example `maintainer:mojca and category:math`) to print all subports. The only problem is that `category:foo` would already list all subports, so additional measures would be needed to make sure that we don't end up with duplicates of build jobs. At the same time we should be a bit careful about code injections to prevent logged in users from executing arbitrary shell code on the build slaves. Any thoughts? -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 13:09:36 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 12:09:36 -0000 Subject: [MacPorts] #52990: g95 install failed on Mac OS Sierra 10.12.1 Message-ID: <050.9748c7c0e6b23164c36f5cb2b8157983@macports.org> #52990: g95 install failed on Mac OS Sierra 10.12.1 ---------------------------+------------------- Reporter: AliceBreeveld | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: g95 ---------------------------+------------------- I have tried cleaning, uninstalling, removing any gfortran from my computer and any g95 references. I repeatedly get this: {{{ /Users/aab$ sudo port install g95 ---> Computing dependencies for g95 ---> Fetching archive for g95 ---> Attempting to fetch g95-0.93_4.darwin_16.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/g95 ---> Attempting to fetch g95-0.93_4.darwin_16.x86_64.tbz2 from https://packages.macports.org/g95 ---> Attempting to fetch g95-0.93_4.darwin_16.x86_64.tbz2 from http://lil.fr.packages.macports.org/g95 ---> Fetching distfiles for g95 ---> Verifying checksums for g95 ---> Extracting g95 ---> Applying patches to g95 ---> Configuring g95 Error: org.macports.configure for port g95 returned: command execution failed Please see the log file for port g95 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_g95/g95/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port g95 failed }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 13:12:12 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 12:12:12 -0000 Subject: [MacPorts] #52990: g95 install failed on Mac OS Sierra 10.12.1 In-Reply-To: <050.9748c7c0e6b23164c36f5cb2b8157983@macports.org> References: <050.9748c7c0e6b23164c36f5cb2b8157983@macports.org> Message-ID: <065.548f4ceb548f143d80ec5a2a13c6a3e5@macports.org> #52990: g95 install failed on Mac OS Sierra 10.12.1 ----------------------------+------------------- Reporter: AliceBreeveld | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: g95 | ----------------------------+------------------- Changes (by AliceBreeveld): * Attachment "main.log" added. Log file for port g95 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 14:01:02 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 13:01:02 -0000 Subject: [MacPorts] #52990: g95 install failed on Mac OS Sierra 10.12.1 In-Reply-To: <050.9748c7c0e6b23164c36f5cb2b8157983@macports.org> References: <050.9748c7c0e6b23164c36f5cb2b8157983@macports.org> Message-ID: <065.e1f7619392fedb97a19163237ab075bf@macports.org> #52990: g95 install failed on Mac OS Sierra 10.12.1 ----------------------------+---------------------- Reporter: AliceBreeveld | Owner: tenomoto Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: g95 | ----------------------------+---------------------- Changes (by ryandesign): * status: new => assigned * owner: => tenomoto Comment: {{{ :info:configure ../../../libgomp/config/posix/time.c: In function 'omp_get_wtime': :info:configure ../../../libgomp/config/posix/time.c:56: warning: implicit declaration of function 'clock_gettime' :info:configure ../../../libgomp/config/posix/time.c:56: error: 'CLOCK_REALTIME' undeclared (first use in this function) :info:configure ../../../libgomp/config/posix/time.c:56: error: (Each undeclared identifier is reported only once :info:configure ../../../libgomp/config/posix/time.c:56: error: for each function it appears in.) :info:configure ../../../libgomp/config/posix/time.c: In function 'omp_get_wtick': :info:configure ../../../libgomp/config/posix/time.c:73: warning: implicit declaration of function 'clock_getres' :info:configure ../../../libgomp/config/posix/time.c:73: error: 'CLOCK_REALTIME' undeclared (first use in this function) :info:configure make[4]: *** [time.lo] Error 1 :info:configure make[3]: *** [all-recursive] Error 1 :info:configure make[2]: *** [all] Error 2 :info:configure make[1]: *** [all-target-libgomp] Error 2 :info:configure make: *** [all] Error 2 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 15:37:36 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 14:37:36 -0000 Subject: [MacPorts] #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc In-Reply-To: <042.20cc8359ea93c50d17385aa98946848c@macports.org> References: <042.20cc8359ea93c50d17385aa98946848c@macports.org> Message-ID: <057.ad45df058149f792f6a45bd336bb4cab@macports.org> #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Comment (by ryandesign): Replying to [ticket:52986 mojca]: > The 10.6-i386 buildbot avoids building many packages: > {{{ > #!bash > if [[ $exclude -eq 0 && "${os_version}" = "10.6" && "${is_64bit_capable}" = "0" ]]; then > supported_archs=$("${option_prefix}/bin/port-tclsh" "${thisdir}/tools/supported-archs.tcl" "${port}") > if [[ -n "${supported_archs}" && ! ("${supported_archs}" == *"x86_64"* && "${supported_archs}" == *"i386"*) ]]; then > exclude=1 > exclude_reasons+=("the ${os_version}_x86_64 builder will build it") > fi > fi > }}} This code is there because it is buildbot-specific. The i386 builder ''could'' build i386-only ports, but we don't want it to, because want to build them on the x86_64 builder, so that their dependencies get built universal. > I believe that a similar strategy could be used to avoid building packages that are declared not to be supported on PPC. We've discussed before that this is a generic MacPorts problem, not a buildbot-specific one. Instead of adding code for this to our buildbot system, we should write code in MacPorts base so that a client (e.g. a user or the buildbot) can determine in advance whether a port is buildable on a particular system. Then the buildbot can simply avoid attempting to build ports that are known not to be buildable on a particular system. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 16:18:20 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 15:18:20 -0000 Subject: [MacPorts] #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc In-Reply-To: <042.20cc8359ea93c50d17385aa98946848c@macports.org> References: <042.20cc8359ea93c50d17385aa98946848c@macports.org> Message-ID: <057.6839f799cb22bf03eb122d025c4d6da7@macports.org> #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Comment (by mojca): I fully agree that the base should tell whether a port is "buildable". But until we have a working code to do that (which might take quite a while - both discussing and implementing), it might be a matter of just a few lines of code to avoid building some ports – similar to what we do with obsolete ports. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 16:54:55 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 15:54:55 -0000 Subject: [MacPorts] #52813: [Port Abandoned] libfwbuilder In-Reply-To: <041.4036e983f392200834f73f40f6978486@macports.org> References: <041.4036e983f392200834f73f40f6978486@macports.org> Message-ID: <056.46757a5f1a5a38849194abf26dc69af9@macports.org> #52813: [Port Abandoned] libfwbuilder ---------------------------+----------------------- Reporter: mf2k | Owner: gongloo@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: libfwbuilder | ---------------------------+----------------------- Changes (by kurthindenburg): * cc: kurthindenburg (added) * status: new => closed * resolution: => fixed Comment: This port was removed {{{ commit c18e3eba56f23981a0f69beee26f6e467d374f27 Author: David B. Evans Date: Wed Nov 9 01:08:10 2016 -0800 libfwbuilder: remove obsolete glib1 port, maintainer timeout Closes https://trac.macports.org/ticket/52746 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 17:04:13 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 16:04:13 -0000 Subject: [MacPorts] #52710: [Port Abandoned] Ports maintained by mac.com:quest In-Reply-To: <041.acaeee1024ec8a9af8ee0ffe308ac061@macports.org> References: <041.acaeee1024ec8a9af8ee0ffe308ac061@macports.org> Message-ID: <056.03bcef8c24c03b04d5dd31dc6acea9ae@macports.org> #52710: [Port Abandoned] Ports maintained by mac.com:quest ------------------------------------------+--------------------- Reporter: mf2k | Owner: quest@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: percona percona-server QiII | ------------------------------------------+--------------------- Changes (by kurthindenburg): * status: new => closed * resolution: => fixed Comment: In [changeset:"546ae2361f8bf0e046268c9a021462036f503ee5/macports-ports" 546ae236/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="546ae2361f8bf0e046268c9a021462036f503ee5" percona/QiII: set nomaintainer closes https://trac.macports.org/ticket/52710 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 17:04:32 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 16:04:32 -0000 Subject: [MacPorts] #40018: Error in mysqld_safe script prevents startup In-Reply-To: <060.a99e0b9c27abd4db2bf791867a472b6a@macports.org> References: <060.a99e0b9c27abd4db2bf791867a472b6a@macports.org> Message-ID: <075.09aad07d22a1d74d8e6e8e31ce005c67@macports.org> #40018: Error in mysqld_safe script prevents startup ----------------------------+-------------------------------- Reporter: modemmonkey@… | Owner: macports-tickets@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: percona | ----------------------------+-------------------------------- Changes (by kurthindenburg): * owner: quest@… => macports-tickets@… * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 17:04:43 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 16:04:43 -0000 Subject: [MacPorts] #47614: percona: should build with InnoDB memcache like mysql56 In-Reply-To: <059.3a78b543f9587dd49006c17f4eba25ba@macports.org> References: <059.3a78b543f9587dd49006c17f4eba25ba@macports.org> Message-ID: <074.2acb05a433eff50ff8e0963756cbf378@macports.org> #47614: percona: should build with InnoDB memcache like mysql56 -----------------------------+-------------------------------- Reporter: inspiration3@… | Owner: macports-tickets@… Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: percona | -----------------------------+-------------------------------- Changes (by kurthindenburg): * owner: quest@… => macports-tickets@… * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 17:22:55 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 16:22:55 -0000 Subject: [MacPorts] #40018: Error in mysqld_safe script prevents startup In-Reply-To: <060.a99e0b9c27abd4db2bf791867a472b6a@macports.org> References: <060.a99e0b9c27abd4db2bf791867a472b6a@macports.org> Message-ID: <075.43e8fcd5c89f81c8e2831fc77de26034@macports.org> #40018: Error in mysqld_safe script prevents startup ----------------------------+---------------------- Reporter: modemmonkey@… | Owner: pixilla Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: percona | ----------------------------+---------------------- Changes (by pixilla): * cc: pixilla (removed) * owner: macports-tickets@… => pixilla -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 19:36:30 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 18:36:30 -0000 Subject: [MacPorts] #46105: texinfo @5.2_2 has unlisted dependency on TeX In-Reply-To: <058.87b4d5eecfba33ee9ee3897544e24e91@macports.org> References: <058.87b4d5eecfba33ee9ee3897544e24e91@macports.org> Message-ID: <073.28879ef97225e6395e9ba21b64d829dc@macports.org> #46105: texinfo @5.2_2 has unlisted dependency on TeX ------------------------+---------------------- Reporter: karsten@… | Owner: larryv Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: texinfo | ------------------------+---------------------- Comment (by raimue): Adding a `texlive-*` dependency to texinfo is quite heavy, especially when most dependents do not seem to need it. Maintainers of dependent ports should evaluate whether building documentation as DVI/PDF is actually useful. If so, add appropriate dependencies, otherwise disable building DVI/PDF. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 20:54:40 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 19:54:40 -0000 Subject: [MacPorts] #52988: the_silver_searcher @0.32.0: update to 1.0.1 In-Reply-To: <041.b5b3237b1fa0fc182be78c96bd22586c@macports.org> References: <041.b5b3237b1fa0fc182be78c96bd22586c@macports.org> Message-ID: <056.1a805186fc9748c60b5ec756846613aa@macports.org> #52988: the_silver_searcher @0.32.0: update to 1.0.1 ----------------------------------+---------------------- Reporter: l2dy | Owner: g5pw Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: the_silver_searcher | ----------------------------------+---------------------- Changes (by larryv): * cc: g5pw (removed) * owner: => g5pw * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 21:29:33 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 20:29:33 -0000 Subject: [MacPorts] #52989: buildbot: allow building 'pseudoports' In-Reply-To: <042.6cfc157f40fe588b534a4b9ad4fd7128@macports.org> References: <042.6cfc157f40fe588b534a4b9ad4fd7128@macports.org> Message-ID: <057.c6c5dd352de81d05eb1575dba19a4951@macports.org> #52989: buildbot: allow building 'pseudoports' -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Low | Milestone: Component: server/hosting | Version: Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Changes (by larryv): * priority: Normal => Low Comment: I don’t think this is a technical problem at all; it seems simple to rework mpbb to handle this safely. The actual question is whether we want to allow people to do this. Then: Why stop at pseudoports? Why not allow arbitrary `port(1)` expressions, including Boolean operators and grouping parentheses? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 22:16:53 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 21:16:53 -0000 Subject: [MacPorts] #52989: buildbot: allow building 'pseudoports' In-Reply-To: <042.6cfc157f40fe588b534a4b9ad4fd7128@macports.org> References: <042.6cfc157f40fe588b534a4b9ad4fd7128@macports.org> Message-ID: <057.e6cedca87c88aea131035faa9524334d@macports.org> #52989: buildbot: allow building 'pseudoports' -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Low | Milestone: Component: server/hosting | Version: Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Comment (by mojca): We are not discussing about allowing random users to do this, but allowing a limited set of trusted developers to do so. We are not discussing adding anything that's not already possible: these users can already copy paste a super long list of ports to the force build field. What I would like is a simple way to do things that are otherwise very tedious to do. We've been holding off the commit with `$Id` field for some time also because we would like to misuse that to rebuild all ports and were afraid to do so without success cache is place. I would prefer if we had an official easy way to launch a rebuild of some/all ports without tedious copy-pasting of tens of thousands of ports. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 22:24:11 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 21:24:11 -0000 Subject: [MacPorts] #52989: buildbot: allow building 'pseudoports' In-Reply-To: <042.6cfc157f40fe588b534a4b9ad4fd7128@macports.org> References: <042.6cfc157f40fe588b534a4b9ad4fd7128@macports.org> Message-ID: <057.b1d2e64e799cfe6aeee4c321e6ed8c5a@macports.org> #52989: buildbot: allow building 'pseudoports' -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Low | Milestone: Component: server/hosting | Version: Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Comment (by larryv): I would argue that force-building large numbers of ports should be a rare and significant event that ought not be easy to do at all. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 22:36:34 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 21:36:34 -0000 Subject: [MacPorts] #52989: buildbot: allow building 'pseudoports' In-Reply-To: <042.6cfc157f40fe588b534a4b9ad4fd7128@macports.org> References: <042.6cfc157f40fe588b534a4b9ad4fd7128@macports.org> Message-ID: <057.0b7dca72e6691b904a42be4191424453@macports.org> #52989: buildbot: allow building 'pseudoports' -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Low | Milestone: Component: server/hosting | Version: Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Comment (by mojca): How exactly would you handle the situation after a new build slave gets added? I'm not saying that we should do that on a weekly basis. But I claim that current situation is worse. Some people are in favour of letting the builds go through after modifying all ports. At the moment we have zero experience of the consequences of such action. It would be much much much safer if we could try building a subset of ports (but still a large enough sample) to even get a rough idea of problems that we might want to address before trying to let such a huge build go through. Some people also say that we should let the build go through because that's a rare occasion that lets us fill in the missing builds, also because it's currently not easy to do so. In my opinion it would be better if we could start partial builds ten times rather than doing them all at once. A random committer may already just touch all ports (for example add a blank line at the end; or replace the formatting of maintainer or anything else, ...). So it's already "easy enough". -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 22:42:42 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 21:42:42 -0000 Subject: [MacPorts] #52989: buildbot: allow building 'pseudoports' In-Reply-To: <042.6cfc157f40fe588b534a4b9ad4fd7128@macports.org> References: <042.6cfc157f40fe588b534a4b9ad4fd7128@macports.org> Message-ID: <057.af1d33c6b8a2d941bdec3021164b25a1@macports.org> #52989: buildbot: allow building 'pseudoports' -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Low | Milestone: Component: server/hosting | Version: Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Comment (by mojca): And yes, I wouldn't mind support for arbitrary expressions. It doesn't seem to be any more difficult to support (as shown in the above example). The only thing that we need to make sure is not to make it too easy to ''accidentally'' end up with too many ports being built. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 22:47:56 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 21:47:56 -0000 Subject: [MacPorts] #52989: buildbot: allow building 'pseudoports' In-Reply-To: <042.6cfc157f40fe588b534a4b9ad4fd7128@macports.org> References: <042.6cfc157f40fe588b534a4b9ad4fd7128@macports.org> Message-ID: <057.4fbae4e2d1502a5a4b22a658bee3690d@macports.org> #52989: buildbot: allow building 'pseudoports' -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Low | Milestone: Component: server/hosting | Version: Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Comment (by larryv): Replying to [comment:6 mojca]: > How exactly would you handle the situation after a new build slave > gets added? I don’t know. What have we been doing so far? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 22:53:25 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 21:53:25 -0000 Subject: [MacPorts] #52989: buildbot: allow building 'pseudoports' In-Reply-To: <042.6cfc157f40fe588b534a4b9ad4fd7128@macports.org> References: <042.6cfc157f40fe588b534a4b9ad4fd7128@macports.org> Message-ID: <057.75a0526634f63bb97e0435c68922bf12@macports.org> #52989: buildbot: allow building 'pseudoports' -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Low | Milestone: Component: server/hosting | Version: Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Comment (by larryv): Replying to [comment:6 mojca]: > A random committer may already just touch all ports (for example add > a blank line at the end; or replace the formatting of maintainer or > anything else, ...). Just because it is possible in some fashion does not mean we endorse it. Allowing pseudoports in the Buildbot interface would be an explicit endorsement of large builds. It says “we have designed our UI to permit this and make it easy”. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 23:06:44 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 22:06:44 -0000 Subject: [MacPorts] #52989: buildbot: allow building 'pseudoports' In-Reply-To: <042.6cfc157f40fe588b534a4b9ad4fd7128@macports.org> References: <042.6cfc157f40fe588b534a4b9ad4fd7128@macports.org> Message-ID: <057.b20c16705e6045d7fcd58bab52f483db@macports.org> #52989: buildbot: allow building 'pseudoports' -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Low | Milestone: Component: server/hosting | Version: Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Comment (by mojca): Replying to [comment:8 larryv]: > Replying to [comment:6 mojca]: > > How exactly would you handle the situation after a new build slave > > gets added? > > I don’t know. What have we been doing so far? Ryan often built all ports (maybe in batches?). I'm not sure how exactly he did it. Maybe he came up with a list of all ports (or a list of directories) and split it in parts. Or at least I believe he did that on the old buildbot where this was less problematic. I don't think we ever did it on the new infrastructure so far, I'm only aware of [https://lists.macports.org/pipermail/macports- dev/2016-September/033693.html this build of python modules] plus some hand-picked list of ports to make life on 10.5, 10.7 and 10.12 easier. Also note that manual interventions are pretty rare and not many developers really care about forcing builds, I wouldn't worry about problems here. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 23:12:27 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 22:12:27 -0000 Subject: [MacPorts] #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc In-Reply-To: <042.20cc8359ea93c50d17385aa98946848c@macports.org> References: <042.20cc8359ea93c50d17385aa98946848c@macports.org> Message-ID: <057.586ce48da1d5da5b82b5917afe265351@macports.org> #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Comment (by jmroot): Replying to [comment:8 mojca]: > Off-topic. > > I just wanted to add one strange observation: > {{{ > > time /opt/local/bin/port-tclsh ./tools/supported-archs.tcl wine > i386 > > real 0m26.122s > }}} > What's the deal with the super long waiting time? Sure, I don't have SSD yet and any subsequent run is much faster, but I'm still completely puzzled why it was so long in the first place (and we are experiencing super long time for trivial tasks on the buildbot all the time). I would again suggest becoming familiar with using the profiler package. This series of blog posts isn't a bad introduction, though the sample code may need some tweaking: https://wuhrr.wordpress.com/2011/01/14/simple-profile-for-your-tcl-script/ https://wuhrr.wordpress.com/2011/01/15/profiling-your-tcl-show-profilers- summary/ https://wuhrr.wordpress.com/2011/01/19/profiling-your-tcl-output-to-csv/ -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 23:59:45 2016 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2016 22:59:45 -0000 Subject: [MacPorts] #52844: Upgrade ocaml to 4.04.0 In-Reply-To: <045.a805fab4a5fcd1f92a13fbe620399494@macports.org> References: <045.a805fab4a5fcd1f92a13fbe620399494@macports.org> Message-ID: <060.0b24e4d85f5b531758d5ad161343b9a5@macports.org> #52844: Upgrade ocaml to 4.04.0 -----------------------+---------------------- Reporter: pmetzger | Owner: larryv Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: ocaml | -----------------------+---------------------- Comment (by larryv): Ocamlbuild was split out from OCaml in 4.03, so I’ll have to test all OCaml ports before committing this. Ugh. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 01:59:23 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 00:59:23 -0000 Subject: [MacPorts] #52991: Error upon installing the GHC Message-ID: <046.0310b609922306b86c4cc90415e2c8d2@macports.org> #52991: Error upon installing the GHC -----------------------+------------------- Reporter: DennyBeck | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: -----------------------+------------------- Received error after building ghc: sudo port install ghc Error: org.macports.build for port ghc returned: command execution failed Please see the log file for port ghc for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_ghc/ghc/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port ghc failed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 02:07:01 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 01:07:01 -0000 Subject: [MacPorts] #52991: Error upon installing the GHC In-Reply-To: <046.0310b609922306b86c4cc90415e2c8d2@macports.org> References: <046.0310b609922306b86c4cc90415e2c8d2@macports.org> Message-ID: <061.d7f22cf7ca4417e27981795917cfd34b@macports.org> #52991: Error upon installing the GHC ------------------------+------------------- Reporter: DennyBeck | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: | ------------------------+------------------- Changes (by DennyBeck): * Attachment "CDC_UP_Requirements_Traceability_Matrix_Template.xls" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 04:04:09 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 03:04:09 -0000 Subject: [MacPorts] #52844: Upgrade ocaml to 4.04.0 In-Reply-To: <045.a805fab4a5fcd1f92a13fbe620399494@macports.org> References: <045.a805fab4a5fcd1f92a13fbe620399494@macports.org> Message-ID: <060.ba3019e2d1df4d27b90d079d0e6cd2e0@macports.org> #52844: Upgrade ocaml to 4.04.0 -----------------------+---------------------- Reporter: pmetzger | Owner: larryv Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: ocaml | -----------------------+---------------------- Comment (by pmetzger): If I can be of some help in speeding this up let me know. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 06:01:44 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 05:01:44 -0000 Subject: [MacPorts] #52991: Error upon installing the GHC In-Reply-To: <046.0310b609922306b86c4cc90415e2c8d2@macports.org> References: <046.0310b609922306b86c4cc90415e2c8d2@macports.org> Message-ID: <061.ce66b996254ca7c5241727640bc3b895@macports.org> #52991: Error upon installing the GHC ------------------------+------------------------ Reporter: DennyBeck | Owner: neverpanic Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ghc | ------------------------+------------------------ Changes (by larryv): * owner: => neverpanic * status: new => assigned * version: 2.3.5 => * port: => ghc Old description: > Received error after building ghc: > > sudo port install ghc > > > Error: org.macports.build for port ghc returned: command execution failed > Please see the log file for port ghc for details: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_ghc/ghc/main.log > To report a bug, follow the instructions in the guide: > http://guide.macports.org/#project.tickets > Error: Processing of port ghc failed New description: Received error after building ghc: {{{ sudo port install ghc }}} {{{ Error: org.macports.build for port ghc returned: command execution failed Please see the log file for port ghc for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_ghc/ghc/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port ghc failed }}} -- Comment: This is likely a duplicate of an existing ticket, but we can’t say for sure without the `main.log`. Please attach that file. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 09:21:17 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 08:21:17 -0000 Subject: [MacPorts] #52988: the_silver_searcher @0.32.0: update to 1.0.1 In-Reply-To: <041.b5b3237b1fa0fc182be78c96bd22586c@macports.org> References: <041.b5b3237b1fa0fc182be78c96bd22586c@macports.org> Message-ID: <056.29769b4c49b8bd7df59c6644d4e28914@macports.org> #52988: the_silver_searcher @0.32.0: update to 1.0.1 ----------------------------------+-------------------- Reporter: l2dy | Owner: g5pw Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: the_silver_searcher | ----------------------------------+-------------------- Changes (by g5pw): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"c6a73698f1d5561a76e8edd17fdb111368f27bcf/macports-ports" c6a73698/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="c6a73698f1d5561a76e8edd17fdb111368f27bcf" textproc/the_silver_searcher: update to 1.0.1 Fixes https://trac.macports.org/ticket/52988 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 10:25:42 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 09:25:42 -0000 Subject: [MacPorts] #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc In-Reply-To: <042.20cc8359ea93c50d17385aa98946848c@macports.org> References: <042.20cc8359ea93c50d17385aa98946848c@macports.org> Message-ID: <057.3127559d637b611b28325ed14a10ca9a@macports.org> #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Comment (by mojca): (Sorry to everyone for the off-topic discussion.) Thank you, I ended up with the following script (suggestions welcome): {{{ #!tcl #!/opt/local/bin/port-tclsh # File: profile_me package require profiler profiler::init proc srcx {} { set argv $::argv set argc $::argc set file [lindex $::argv 0] set ::argv [lreplace $::argv 0 0] set ::argc [llength $::argv] set code [catch {uplevel [list source $file]} return] set ::argv $argv set ::argc $argc return -code $code $return } srcx # Display profiler info puts "\n[string repeat - 40]" puts [::profiler::print] }}} and `time ./profileme.tcl ./tools/supported-archs.tcl wine` but I need to wait. There seems to be some cache somewhere and only the first call is super slow, any subsequent calls are fast. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 13:07:53 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 12:07:53 -0000 Subject: [MacPorts] #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc In-Reply-To: <042.20cc8359ea93c50d17385aa98946848c@macports.org> References: <042.20cc8359ea93c50d17385aa98946848c@macports.org> Message-ID: <057.b72bff5edc19fb835cdcce2207e99db1@macports.org> #52986: buildbot: don't add ports that declare not to support ppc to the build queue of 10.5-ppc -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Comment (by mojca): I absolutely love the results of profiling (this was a fast run though): {{{ Functions that are sorted by exclusiveRuntime: - 15312828 - ::lshift - 12601898 - ::puts - 7224617 - ::ldindex - 2379654 - ::lpush - 1840049 - ::lpop - 1336408 - ::_source_is_snapshot - 816458 - ::ditem_key ... - 0 - ::intersect - -138321 - ::macports::setxcodeinfo - -270916 - ::macports::set_developer_dir - -479661 - ::mportinit - -554829 - ::_mports_load_quickindex - -558463 - ::mportclose - -564781 - ::macports::ui_init - -666930 - ::macports::getindex - -688013 - ::mportlookup - -1302686 - ::msgcat::Init - -2878285 - ::mportopen - -26476148 - ::try }}} We have negative times, yay! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 13:53:58 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 12:53:58 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts Message-ID: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------+------------------------------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: maintainer | Port: fluid-soundfont-gm_gs fluid- haspatch | soundfont-gu_gs -------------------------+------------------------------------------------- I'm opening a new ticket for discussing new packages for fluidsynth sound fonts. This was originally mentioned in #51842 as a potential dependency for TiMidity++. Here's the code contributed by René: * [https://github.com/RJVB/macstrop/tree/2fb8aab3edbf8c0bd00604b87efa351c761d0cc5/multimedia/fluidsynth multimedia/fluidsynth] (from [https://github.com/RJVB/macstrop/tree/master/multimedia/fluidsynth master]) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 14:23:09 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 13:23:09 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.cada5cabed62578cf0cc7a3f17429861@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: maintainer Port: fluid-soundfont-gm_gs fluid- | haspatch soundfont-gu_gs | -------------------------------------------------+------------------------- Comment (by RJVB): I'm all in favour for this :) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 14:26:15 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 13:26:15 -0000 Subject: [MacPorts] #50426: geant4.10.2: broken links of dylibs In-Reply-To: <042.b5f6bba382554cc384de7f3c332fc60e@macports.org> References: <042.b5f6bba382554cc384de7f3c332fc60e@macports.org> Message-ID: <057.4b25d7e6a906bc883467e616ced795ec@macports.org> #50426: geant4.10.2: broken links of dylibs --------------------------+-------------------- Reporter: mojca | Owner: mojca Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: geant4.10.2 | --------------------------+-------------------- Comment (by RJVB): Re: https://github.com/macports/macports- ports/pull/26#issuecomment-264447506 I think that with the current (my...) cmake-1.1.tcl you ought to be able to replace the setting for `CMAKE_INSTALL_NAME_DIR ` in configure.pre_args, and add the Geant libdir (${prefix}/lib/Geant4/Geant4.10.2) to `cmake.install_rpath`. I don't think this is a very common thing, but we *could* add an options variable for `CMAKE_INSTALL_NAME_DIR` (which sets the `string specifying the directory portion of the “install_name” field of shared libraries on Mac OSX to use in the installed targets.`). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 14:46:06 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 13:46:06 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.eece2ae7a2b3f7e248c5c387009021dc@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: maintainer Port: fluid-soundfont-gm_gs fluid- | haspatch soundfont-gu_gs | -------------------------------------------------+------------------------- Comment (by mojca): * I don't see any reason to keep the two sound fonts as subports of fluidsynth. They have different descriptions, different master sites, different everything. You could just as well make three ports. * The names are confusing enough already. I would (slightly?) prefer `fluid-soundfont-gm` and `fluid-soundfont-gs`. If you take all the patches from Debian, we could keep the naming somewhat consistent. I don't want to insist on that though. * Where did you get the [https://github.com/RJVB/macstrop/blob/9d365dc3cd26c3c1242fbfe651319bf9b7b20d9e/multimedia/fluidsynth/files /fluid-soundfont_3.1-5.1.diff patch] from? From [http://debian.inode.at/debian/pool/main/f/fluid-soundfont/fluid- soundfont_3.1-5.1.diff.gz Debian]? I super hate the form it has at the moment and would be much happier if we would split it. Else let's just fetch the patch from Debian directly rather than including it as a whole in our MP repo. * In particular I would prefer to provide `fluidr3_gm.cfg` and `fluidr3_gs.cfg` as a separate standalone file rather than a patch, but all other files are annoying as well and people would get temptation to modify them. Less annoying if we take them directly though. * [https://docs.fedoraproject.org/en-US/Fedora/15/html/Musicians_Guide /sect-Musicians_Guide-FluidSynth-Req_and_Inst.html Fedora] recommends using `${prefix}/share/soundfonts`. You picked `${prefix}/share/sounds/sf2`. I'm not sure what other conventions are used elsewhere and I don't know if MacPorts already provides any sound fonts at all. * What's the relation between fluitsynth and General User GL? Is `${destroot}${prefix}/share/docs/fluidsynth/GeneralUser-GS/${version}` justified? I would kind of expect fluidsynth's documentation there and if the two projects are unrelated this might not be the most appropriate path. Same is true for other paths. But I'm not sure and I don't have any better idea. * I guess that we should be able to come up with a livecheck for http://www.schristiancollins.com/generaluser.php Random thoughts: * The original link ([http://www.musescore.org/download/fluid- soundfont.tar.gz here]) contains `FluidR3 GM2-2.SF2` from 2013 rather than `FluidR3_GM.sf2` and `FluidR3_GS.sf2` from 2008, but I would ignore that fact and simply take things from Debian. * Now that we have an example of packaging an SF2 font, the added bonus (once this work gets finished) would be to take a look at [http://freepats.zenvoid.org/SoundSets/general-midi.html#FreePatsGM FreePats2] again. That's also an `.sf2` file. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 15:08:42 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 14:08:42 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.977646ee3ef1411438622effea32317c@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: maintainer Port: fluid-soundfont-gm_gs fluid- | haspatch soundfont-gu_gs | -------------------------------------------------+------------------------- Comment (by RJVB): Replying to [comment:2 mojca]: > * I don't see any reason to keep the two sound fonts as subports of fluidsynth. They have different descriptions, different master sites, different everything. You could just as well make three ports. Initially I went for a fluidsynth subport because of the functional link to fluidsynth made by Debian/Ubuntu. It was only while looking at the 2 fluid-soundfont packages that I realised that 1) we would be putting the GM and GS soundfonts in a single port, and 2) that there's a (much) newer version of the GS sound font that is much more elaborate. And has a different license. I'd still put both soundfonts in a single port myself, though. > * The names are confusing enough already. I would (slightly?) prefer `fluid-soundfont-gm` and `fluid-soundfont-gs`. If you take all the patches from Debian, we could keep the naming somewhat consistent. I don't want to insist on that though. Naming is open for discussion, but the point remains there are 2 GS sound fonts. We could of course put the 2 older soundfonts under the -gm label, and the GeneralUser GS font as -gs. > * Where did you get the [https://github.com/RJVB/macstrop/blob/9d365dc3cd26c3c1242fbfe651319bf9b7b20d9e/multimedia/fluidsynth/files /fluid-soundfont_3.1-5.1.diff patch] from? From [http://debian.inode.at/debian/pool/main/f/fluid-soundfont/fluid- soundfont_3.1-5.1.diff.gz Debian]? I super hate the form it has at the moment and would be much happier if we would split it. Else let's just fetch the patch from Debian directly rather than including it as a whole in our MP repo. Yes, I think so. It's a typical Debian patch that adds the whole debian subdir. We could strip out all the unused bits. Fetching from upstream is fine with me too, but (how) does that work with a gzipped patchfile? > * In particular I would prefer to provide `fluidr3_gm.cfg` and `fluidr3_gs.cfg` as a separate standalone file rather than a patch, but all other files are annoying as well and people would get temptation to modify them. Less annoying if we take them directly though. The only way to get those from upstream would be to download a binary package; they don't exist as such in the source package. > * [https://docs.fedoraproject.org/en-US/Fedora/15/html/Musicians_Guide /sect-Musicians_Guide-FluidSynth-Req_and_Inst.html Fedora] recommends using `${prefix}/share/soundfonts`. You picked `${prefix}/share/sounds/sf2`. I'm not sure what other conventions are used elsewhere and I don't know if MacPorts already provides any sound fonts at all. Hmmm, I picked sounds/sf2 because that's what Debian and Ubuntu use, and I think that by extension that's where many software will look for soundfonts. There are none in MacPorts, so we have all liberty. But it does seem reasonable to install these under the existing standard sounds directory rather than in a parallel location. > * What's the relation between fluitsynth and General User GL? Is `${destroot}${prefix}/share/docs/fluidsynth/GeneralUser-GS/${version}` justified? I would kind of expect fluidsynth's documentation there and if the two projects are unrelated this might not be the most appropriate path. Same is true for other paths. But I'm not sure and I don't have any better idea. Good points... > * I guess that we should be able to come up with a livecheck for http://www.schristiancollins.com/generaluser.php Maybe let's first try to assess how often this evolves? > * The original link ([http://www.musescore.org/download/fluid- soundfont.tar.gz here]) contains `FluidR3 GM2-2.SF2` from 2013 rather than `FluidR3_GM.sf2` and `FluidR3_GS.sf2` from 2008, but I would ignore that fact and simply take things from Debian. Have you checked if there's an actual difference? I have assumed that the Debian package maintainers would have picked that up (5 years is long, even for Debian). > * Now that we have an example of packaging an SF2 font, the added bonus (once this work gets finished) would be to take a look at [http://freepats.zenvoid.org/SoundSets/general-midi.html#FreePatsGM FreePats2] again. That's also an `.sf2` file. Yep. I looked at it and I don't see any advantage it could have over the original FreePats or the GeneralUser soundfont. Quality is maybe marginally better than the former but certainly not than the latter, and the number of voices is considerably more limited. It doesn't seem to be possible to load and merge multiple soundfonts, and if that's confirmed there doesn't seem to be much interest in providing options that aren't very appropriate as a generic choice. Users with special needs are likely to know where to find "specialty" soundfonts, don't you think? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 15:10:47 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 14:10:47 -0000 Subject: [MacPorts] #50426: geant4.10.2: broken links of dylibs In-Reply-To: <042.b5f6bba382554cc384de7f3c332fc60e@macports.org> References: <042.b5f6bba382554cc384de7f3c332fc60e@macports.org> Message-ID: <057.795952889090b6ec1e5367f67ae6aa0d@macports.org> #50426: geant4.10.2: broken links of dylibs --------------------------+-------------------- Reporter: mojca | Owner: mojca Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: geant4.10.2 | --------------------------+-------------------- Comment (by mojca): Is there something I should test now? (Else I would prefer to do the changes once a new version gets released.) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 15:26:32 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 14:26:32 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.9719744a5fe70f5d098ce720438d7e3f@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Changes (by mf2k): * keywords: maintainer haspatch => Comment: Removing redundant keywords. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 15:34:19 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 14:34:19 -0000 Subject: [MacPorts] #52718: [Port Abandoned] Ports maintained by gmail.com:naoya.n In-Reply-To: <041.1729c8677fb0cdd7b741a2547f939b50@macports.org> References: <041.1729c8677fb0cdd7b741a2547f939b50@macports.org> Message-ID: <056.e59dd412fa09b95f6ef4c350eff16467@macports.org> #52718: [Port Abandoned] Ports maintained by gmail.com:naoya.n -------------------------------------------------+------------------------- Reporter: mf2k | Owner: naoya.n@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: kumofs makuosan rb-msgpack rb- | tokyocabinet-ruby thrift thrift-devel | -------------------------------------------------+------------------------- Changes (by kurthindenburg): * status: new => closed * resolution: => fixed Comment: In [changeset:"fb767cfdbd5cd3658ff4e02d70ab857ab45b8d9e/macports-ports" fb767cfd/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="fb767cfdbd5cd3658ff4e02d70ab857ab45b8d9e" thrift-devel/thrift/kumofs/makuosan/rb-msgpack/rb-tokyocabinet-ruby set nomaintainer closes https://trac.macports.org/ticket/52718 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 15:34:55 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 14:34:55 -0000 Subject: [MacPorts] #31620: kumofs: update to 0.4.13 In-Reply-To: <047.8c84177485482400b251e8a91c56c006@macports.org> References: <047.8c84177485482400b251e8a91c56c006@macports.org> Message-ID: <062.cab7b8de66baa584f2ce9569218a1404@macports.org> #31620: kumofs: update to 0.4.13 -------------------------+-------------------------------- Reporter: ryandesign | Owner: macports-tickets@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: kumofs | -------------------------+-------------------------------- Changes (by kurthindenburg): * owner: naoya.n@… => macports-tickets@… * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 15:35:19 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 14:35:19 -0000 Subject: [MacPorts] #35096: thrift: add php53 and php54 variants In-Reply-To: <047.0afd65a01112eb83e2a6c2c6c277eb75@macports.org> References: <047.0afd65a01112eb83e2a6c2c6c277eb75@macports.org> Message-ID: <062.9b9a60fc9d87f7bf09f76d6c4a61f8f9@macports.org> #35096: thrift: add php53 and php54 variants --------------------------+-------------------------------- Reporter: ryandesign | Owner: macports-tickets@… Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Resolution: | Keywords: Port: thrift | --------------------------+-------------------------------- Changes (by kurthindenburg): * owner: naoya.n@… => macports-tickets@… * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 15:35:32 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 14:35:32 -0000 Subject: [MacPorts] #49145: thrift @0.9.2_1 (devel) Build failed In-Reply-To: <057.2d6a79858cbb358d059fc75d287ba987@macports.org> References: <057.2d6a79858cbb358d059fc75d287ba987@macports.org> Message-ID: <072.89259f2a05082bf019aaf8b974f87f5f@macports.org> #49145: thrift @0.9.2_1 (devel) Build failed ---------------------------+-------------------------------- Reporter: radegast13@… | Owner: macports-tickets@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: thrift | ---------------------------+-------------------------------- Changes (by kurthindenburg): * owner: naoya.n@… => macports-tickets@… * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 15:35:43 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 14:35:43 -0000 Subject: [MacPorts] #52452: thrift @0.9.2_2: update to 0.9.3 In-Reply-To: <048.d336f107942481903b0dbda18de9f586@macports.org> References: <048.d336f107942481903b0dbda18de9f586@macports.org> Message-ID: <063.f0bae21bbdb2a69e5b20a338eb547670@macports.org> #52452: thrift @0.9.2_2: update to 0.9.3 --------------------------+-------------------------------- Reporter: Schamschula | Owner: macports-tickets@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: thrift | --------------------------+-------------------------------- Changes (by kurthindenburg): * owner: naoya.n@… => macports-tickets@… * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 15:49:24 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 14:49:24 -0000 Subject: [MacPorts] #52490: [Port Abandoned] Ports maintained by hum In-Reply-To: <041.9d8ed880a58e228011e8b4ff5729ba02@macports.org> References: <041.9d8ed880a58e228011e8b4ff5729ba02@macports.org> Message-ID: <056.48ff04e1e8e6ef33437f72778e54e1c5@macports.org> #52490: [Port Abandoned] Ports maintained by hum -------------------------------------------------+------------------------- Reporter: mf2k | Owner: hum@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: apache-solr3 apache-solr4 arowpp | bact bayon brown-cluster cabocha caffe cedar | chasen chasen-base chasen-ipadic chasen- | ipadic-sjis chasen-ipadic-utf8 chasen-naist- | jdic chasen-naist-jdic-sjis chasen-naist- | jdic-utf8 cicada classias cpi00 crfpp crfpp- | devel crfsuite cutter darts darts-clone | dualist eda emacs-app emacs-mac-app expgram | extractopinion gibbslda giza-pp google-glog | groonga hadoop hts_engine_API irstlm jdepp | jubatus jubatus-mpio jubatus-msgpack-rpc | jubatus_core julius juman juman6 kakarot KNBC | knp knp3 kytea lader lda-c lda-d liblbfgs | liblinear libsvm libzookeeper lmdb lucene- | gosen2 lucene-gosen4 mahout mallet marisa- | trie mecab mecab-base mecab-ipadic mecab- | ipadic-neologd mecab-ipadic-sjis mecab- | ipadic-utf8 mecab-java mecab-jumandic mecab- | jumandic-sjis mecab-jumandic-utf8 mecab- | naist-jdic mecab-naist-jdic-sjis mecab-naist- | jdic-utf8 mecab-sjis mecab-utf8 mgizapp | MMDAgent mosesdecoder msgpack msgpack1 | normalizeNumexp oll oniguruma5 opal-ml | open_jtalk openfst p5-mecab p5-termextract p5 | -text-csv_xs palmkit pecco pficommon pialign | plda portaudio py-breadability py-chainer py- | docopt py-gensim py-jubatus-client py-langid | py-leveldb py-mecab py-mmh3 py-nltk py-nltk3 | py-pymc py-pymc3 py-sparqlwrapper py-sumy py- | word2vec rb-mecab rb19-mecab re2 rnnlm | seekanser sgd simstring sinsy slearp sofia-ml | sparsehash sptk ssrc stanford-ner stanford- | parser stanford-postagger syncha tinycdb | TinySVM unidic-mecab ux-trie vowpal_wabbit | wapiti word2vec yakmo yamcha zunda | -------------------------------------------------+------------------------- Changes (by kurthindenburg): * cc: kurthindenburg (added) Comment: That's a lot of ports - it would be nice to hear from him before removing him from them all -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 15:52:43 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 14:52:43 -0000 Subject: [MacPorts] #35096: thrift: add php53 and php54 variants In-Reply-To: <047.0afd65a01112eb83e2a6c2c6c277eb75@macports.org> References: <047.0afd65a01112eb83e2a6c2c6c277eb75@macports.org> Message-ID: <062.91940e64a74debe3567b9d7a5057e0a9@macports.org> #35096: thrift: add php53 and php54 variants --------------------------+---------------------- Reporter: ryandesign | Owner: blair Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: thrift | --------------------------+---------------------- Changes (by mf2k): * cc: blair (removed) * owner: macports-tickets@… => blair * version: 2.1.1 => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 15:54:50 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 14:54:50 -0000 Subject: [MacPorts] #49145: thrift @0.9.2_1 (devel) Build failed In-Reply-To: <057.2d6a79858cbb358d059fc75d287ba987@macports.org> References: <057.2d6a79858cbb358d059fc75d287ba987@macports.org> Message-ID: <072.b1d9ba720b96e69118578cef26c75127@macports.org> #49145: thrift @0.9.2_1 (devel) Build failed ---------------------------+---------------------- Reporter: radegast13@… | Owner: blair Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: thrift | ---------------------------+---------------------- Changes (by mf2k): * cc: blair (removed) * owner: macports-tickets@… => blair -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 15:55:57 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 14:55:57 -0000 Subject: [MacPorts] #52452: thrift @0.9.2_2: update to 0.9.3 In-Reply-To: <048.d336f107942481903b0dbda18de9f586@macports.org> References: <048.d336f107942481903b0dbda18de9f586@macports.org> Message-ID: <063.fcecad56c95b354304de2e129a983182@macports.org> #52452: thrift @0.9.2_2: update to 0.9.3 --------------------------+---------------------- Reporter: Schamschula | Owner: blair Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: thrift | --------------------------+---------------------- Changes (by mf2k): * cc: blair, khindenburg@… (removed) * cc: kurthindenburg (added) * owner: macports-tickets@… => blair -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 16:10:43 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 15:10:43 -0000 Subject: [MacPorts] #52993: GNOME girl 9.6.0 Message-ID: <045.04d8e8a96f5386b2efda1aea2d1aff35@macports.org> #52993: GNOME girl 9.6.0 ----------------------+---------------------------- Reporter: oleaamot | Owner: Type: update | Status: new Priority: Normal | Milestone: MacPorts 2.3.6 Component: ports | Version: 2.3.5 Keywords: gnome | Port: girl ----------------------+---------------------------- GNOME Internet Radio Locator (GIRL) version 9.6.0 was released on December 1st, 2016 with updated translations for Czech, Hungarian, Polish, Brazilian Portuguese and Swedish. The new feature in this release is gstreamer playback of audio. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 16:11:22 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 15:11:22 -0000 Subject: [MacPorts] #52993: GNOME girl 9.6.0 In-Reply-To: <045.04d8e8a96f5386b2efda1aea2d1aff35@macports.org> References: <045.04d8e8a96f5386b2efda1aea2d1aff35@macports.org> Message-ID: <060.f4b2f955a081507124910cd914e755a0@macports.org> #52993: GNOME girl 9.6.0 -----------------------+---------------------------- Reporter: oleaamot | Owner: Type: update | Status: new Priority: Normal | Milestone: MacPorts 2.3.6 Component: ports | Version: 2.3.5 Resolution: | Keywords: gnome Port: girl | -----------------------+---------------------------- Changes (by oleaamot): * Attachment "Portfile.9.6.0.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 16:16:36 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 15:16:36 -0000 Subject: [MacPorts] #52994: flake8 fails to run with pkg_resources.DistributionNotFound Message-ID: <047.b25efea66bf5ed87ff7e890a0c09040b@macports.org> #52994: flake8 fails to run with pkg_resources.DistributionNotFound ------------------------+----------------------- Reporter: rectalogic | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: py-flake8 ------------------------+----------------------- py-flake8 3.2.1 port fails to run: {{{ $ flake8 Traceback (most recent call last): File "/opt/local/bin/flake8", line 6, in from pkg_resources import load_entry_point File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/pkg_resources/__init__.py", line 3017, in @_call_aside File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/pkg_resources/__init__.py", line 3003, in _call_aside f(*args, **kwargs) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/pkg_resources/__init__.py", line 3030, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/pkg_resources/__init__.py", line 659, in _build_master ws.require(__requires__) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/pkg_resources/__init__.py", line 967, in require needed = self.resolve(parse_requirements(requirements)) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/pkg_resources/__init__.py", line 853, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'configparser' distribution was not found and is required by flake8 }}} `port install py-configparser` fixes that but results in: {{{ $ flake8 Traceback (most recent call last): File "/opt/local/bin/flake8", line 6, in from pkg_resources import load_entry_point File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/pkg_resources/__init__.py", line 3017, in @_call_aside File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/pkg_resources/__init__.py", line 3003, in _call_aside f(*args, **kwargs) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/pkg_resources/__init__.py", line 3030, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/pkg_resources/__init__.py", line 659, in _build_master ws.require(__requires__) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/pkg_resources/__init__.py", line 967, in require needed = self.resolve(parse_requirements(requirements)) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/pkg_resources/__init__.py", line 853, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'enum34' distribution was not found and is required by flake8 }}} `port install py-enum34` fixes that. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 16:17:29 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 15:17:29 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.265a14cd046cdd64d0e8040211209946@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Changes (by mojca): * Attachment "fluid-soundfont.Portfile" added. My proposal for fluid-soundfont -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 16:23:38 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 15:23:38 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.265a14cd046cdd64d0e8040211209946@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Changes (by mojca): * Attachment "fluid-soundfont.Portfile" removed. My proposal for fluid-soundfont -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 16:23:38 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 15:23:38 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.dcb74388bfbf3b4d094bc88d25b4f4ec@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Changes (by mojca): * Attachment "fluid-soundfont.Portfile" added. My proposal for fluid-soundfont -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 16:27:15 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 15:27:15 -0000 Subject: [MacPorts] #52994: flake8 fails to run with pkg_resources.DistributionNotFound In-Reply-To: <047.b25efea66bf5ed87ff7e890a0c09040b@macports.org> References: <047.b25efea66bf5ed87ff7e890a0c09040b@macports.org> Message-ID: <062.27dd03a9d63dbff50dbf5c5544f4b72b@macports.org> #52994: flake8 fails to run with pkg_resources.DistributionNotFound -------------------------+---------------------- Reporter: rectalogic | Owner: petrrr Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: py-flake8 | -------------------------+---------------------- Changes (by mf2k): * owner: => petrrr * status: new => assigned Comment: In the future, please Cc the port maintainers ({{{port info --maintainers py-flake8}}}), if any. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 16:39:20 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 15:39:20 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.b246d50e674358c371838d2f6fc53394@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Comment (by mojca): I attached my proposal for packaging what's in Debian (some files may be omitted from installation of course, but I felt it would be right to give some credit to Debian for making all the support files). Quick observations: * GS `fluidr3_gs.cfg` doesn't even provide support for accordion * GM `fluidr3_gm.cfg` is sometimes better and with more "natural" sound for accordion, but it sounds terrible when playing quickly and the balance between the high pitches for melody and the basses is not even bearable to listen to; so apparently I'll have to stick with FreePats. * `cfg` files use a mixture of LF & CRLF (may we depend on dos2unix for installation dependency?) I noticed that Debian probably puts the files to `etc/timidity`. I'm not sure what's better, but when I think about it, `etc` does make sense. > Have you checked if there's an actual difference? I have assumed that the Debian package maintainers would have picked that up (5 years is long, even for Debian). I have no clue how to inspect sound fonts. And anyway there is no GM and the licence is different and ... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 16:43:18 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 15:43:18 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.f896b6818ca6920b90fdc01280fd8470@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Changes (by mojca): * Attachment "fluid-soundfont.2.Portfile" added. My proposal for fluid-soundfont -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 16:53:38 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 15:53:38 -0000 Subject: [MacPorts] #52882: Removal of py26-apptools and py26-chaco left py26-blockcanvas broken In-Reply-To: <043.60283e312ce190d6a1b0058fd4c7f369@macports.org> References: <043.60283e312ce190d6a1b0058fd4c7f369@macports.org> Message-ID: <058.0331197792dd8f6b38cff5341bc02540@macports.org> #52882: Removal of py26-apptools and py26-chaco left py26-blockcanvas broken -------------------------------+----------------------- Reporter: jmroot | Owner: jjstickel Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: py26-blockcanvas | -------------------------------+----------------------- Comment (by jjstickel): OK. Please remove the py26 subport from blockcanvas. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 16:54:36 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 15:54:36 -0000 Subject: [MacPorts] #52883: Removal of py26-traits left dependents broken In-Reply-To: <043.af32dc7eb53036621308928d5e814906@macports.org> References: <043.af32dc7eb53036621308928d5e814906@macports.org> Message-ID: <058.444ffe2928e6b53c387024a7e6ec7e5d@macports.org> #52883: Removal of py26-traits left dependents broken -------------------------------------------------+------------------------- Reporter: jmroot | Owner: jjstickel Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: py26-scimath py26-etsdevtools | py26-codetools | -------------------------------------------------+------------------------- Comment (by jjstickel): OK. Please remove the py26 subport from these. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 17:04:27 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 16:04:27 -0000 Subject: [MacPorts] #51842: Timidity: request for a new port In-Reply-To: <042.0dbd8a1776b3b4d627b5a128a2c7cbc7@macports.org> References: <042.0dbd8a1776b3b4d627b5a128a2c7cbc7@macports.org> Message-ID: <057.b7ab134a710c8ec1b1c380298cc58e05@macports.org> #51842: Timidity: request for a new port -------------------------+------------------- Reporter: mojca | Owner: mojca Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: timidity | -------------------------+------------------- Comment (by mojca): Discussion about soundfonts moved to #52992. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 17:09:49 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 16:09:49 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.fdfc4a5da6c457a340d6c575b95216aa@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Comment (by RJVB): Replying to [comment:5 mojca]: I don't have time right now but will check out your proposal later. > it would be right to give some credit to Debian for making all the support files). Yes, that's why I installed a few of their files too (IIRC). > * GS `fluidr3_gs.cfg` doesn't even provide support for accordion No, this file can be used in addition to the gm .cfg file; it provides Roland patches. > * `cfg` files use a mixture of LF & CRLF (may we depend on dos2unix for installation dependency?) Not when you create them via the patchfile. I don't think you ought to be concerned with "people would get temptation to modify them". They might, but it will rather be the installed version, while others might think twice before they start hacking in patchfiles. > I noticed that Debian probably puts the files to `etc/timidity`. I'm not sure what's better, but when I think about it, `etc` does make sense. I don't recall patching timidity to use a location other than $prefix/share/timidity, so I guess it's Debian who patch timidity to look in under etc. I can imagine putting timidity.cfg under etc, but the other files seem better under share/something. > I have no clue how to inspect sound fonts. And anyway there is no GM and the licence is different and ... Size could be a good clue here. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 17:27:04 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 16:27:04 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.9b262e2acc1f4ec78aa44c9c2de74f1d@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Comment (by mojca): My suggestion would be to: * make the ports for sound fonts ready first * make sure that fluidsynth is up to date (I didn't look at it yet, I'm waiting to resolve this first), if nothing else add the maintainer * look at TiMidity++ next * you can update the PR for VLC any time * I'll need assistance with qsynth in case it's ready; I found a linux box where I installed it, but I have no clue what to do with it; but once it's ready you can also submit a pull request anyway Replying to [comment:6 RJVB]: > Replying to [comment:5 mojca]: > > it would be right to give some credit to Debian for making all the support files). > Yes, that's why I installed a few of their files too (IIRC). I didn't see any. Just `README` and `COPYING` from original. > > * GS `fluidr3_gs.cfg` doesn't even provide support for accordion > No, this file can be used in addition to the gm .cfg file; it provides Roland patches. In that case I admit that I don't even have a clue how to use the files. (I made a symlink from `timidity.cfg` to the file I wanted to use.) > > * `cfg` files use a mixture of LF & CRLF (may we depend on dos2unix for installation dependency?) > Not when you create them via the patchfile. They do when I fetch the patchfiles from Debian directly. > I don't think you ought to be concerned with "people would get temptation to modify them". In my attached example there is no separate patchfile (and thus no temptation :), the patchfile is fetched and applied on the fly from the Debian server. > I don't recall patching timidity to use a location other than $prefix/share/timidity, so I guess it's Debian who patch timidity to look in under etc. I can imagine putting timidity.cfg under etc, but the other files seem better under share/something. We can put them to `share/timidity` then. > > I have no clue how to inspect sound fonts. And anyway there is no GM and the licence is different and ... > Size could be a good clue here. {{{ 257 20 jun 2013 Changelog.txt 14848 21 jun 2013 Fluid R3- Readme.doc 148345256 20 jun 2013 FluidR3 GM2-2.SF2 }}} vs. {{{ 1086 19 feb 2008 COPYING 148398306 24 feb 2008 FluidR3_GM.sf2 3201926 24 feb 2008 FluidR3_GS.sf2 1042 20 feb 2008 README }}} and `Changelog.txt` {{{ FluidR3 GM Soundfont Changes Log Date Version Author Action 20/06/13 2.2 Church Organist Missing note (#94) added to Violin and range extended to G7 (MIDI#103) for compatibility with MuseScore 2 }}} and the readme starting with {{{ FLUID® R3 Released to Public Domain on 12/25/01 ©2000-2002 Frank Wen }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 18:15:13 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 17:15:13 -0000 Subject: [MacPorts] #52993: GNOME girl 9.6.0 In-Reply-To: <045.04d8e8a96f5386b2efda1aea2d1aff35@macports.org> References: <045.04d8e8a96f5386b2efda1aea2d1aff35@macports.org> Message-ID: <060.ffd6a38816f510decf6dd6788168dfb2@macports.org> #52993: GNOME girl 9.6.0 -----------------------+----------------- Reporter: oleaamot | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: girl | -----------------------+----------------- Changes (by mf2k): * keywords: gnome => * version: 2.3.5 => * milestone: MacPorts 2.3.6 => Comment: The Milestone field is for use by Macports team members only, please do not set it. Comments on your patch: - Are you the port maintainer? - Remove the no longer used {{{# $Id$}}} line - Is the decimal point at the end of the version number correct? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 18:16:33 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 17:16:33 -0000 Subject: [MacPorts] #52993: GNOME girl 9.6.0 In-Reply-To: <045.04d8e8a96f5386b2efda1aea2d1aff35@macports.org> References: <045.04d8e8a96f5386b2efda1aea2d1aff35@macports.org> Message-ID: <060.bf8f59de96f5097c57c7c345e13acb7b@macports.org> #52993: GNOME girl 9.6.0 -----------------------+----------------- Reporter: oleaamot | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: girl | -----------------------+----------------- Comment (by mf2k): Also, please keep the whitespace you are removing. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 18:40:28 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 17:40:28 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.046b24c6571cd3183c6efbf4e09152d5@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Comment (by RJVB): Replying to [comment:7 mojca]: > * make the ports for sound fonts ready first > * make sure that fluidsynth is up to date (I didn't look at it yet, I'm waiting to resolve this first), if nothing else add the maintainer OK and OK. According to livecheck fluidsynth and the website is up to date. > * you can update the PR for VLC any time Already done (I think), but that will have to be redone as a function of 1). > * I'll need assistance with qsynth in case it's ready; I found a linux box where I installed it, but I have no clue what to do with it; but once it's ready you can also submit a pull request anyway Did you test it already? I got it to build (with some convincing not to make an autonomous app bundle) but it doesn't work reliably. It does when I switch it to PortAudio instead CoreAudio + CoreMidi, and keeps working when I switch it back, but otherwise it only logs error messages in system.log. Googling suggests that could be a known issue on 10.9 . Either way it doesn't have a way to open other files (strange for a GUI app) and would require a patch to make it open files via the Finder. Its niche seems to be the control over certain playback parameters it gives, but as a tool for simply playing back MIDI files as if they were regular sound files VLC does much better. > > > * GS `fluidr3_gs.cfg` doesn't even provide support for accordion > > No, this file can be used in addition to the gm .cfg file; it provides Roland patches. > > In that case I admit that I don't even have a clue how to use the files. (I made a symlink from `timidity.cfg` to the file I wanted to use.) timidity.cfg shows how: you specify both. I think that if you look at the contents of these files you'll see that they don't specify exactly the same channels. > 20/06/13 2.2 Church Organist Missing note (#94) added to Violin and range extended to G7 (MIDI#103) That doesn't seem completely devoid of interest, but we can start with the older version shipped by Debian and then see if there are requests to push the newer version. That is if you yourself don't see a reason for it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 18:45:28 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 17:45:28 -0000 Subject: [MacPorts] #52452: thrift @0.9.2_2: update to 0.9.3 In-Reply-To: <048.d336f107942481903b0dbda18de9f586@macports.org> References: <048.d336f107942481903b0dbda18de9f586@macports.org> Message-ID: <063.3f031fed9afbceb5d3974f06c2705458@macports.org> #52452: thrift @0.9.2_2: update to 0.9.3 --------------------------+---------------------- Reporter: Schamschula | Owner: blair Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: thrift | --------------------------+---------------------- Comment (by n0ts): @kurthindenburg Hello, Now I use not thrift MacPorts. Could you change owner? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 19:22:31 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 18:22:31 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.7dae620a67c33889da7e7332e34d3289@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Comment (by mojca): I didn't test qsynt. I only started it on a linux box that I had at hand and had no clue what it does. I later figured out how you did the configuration of `timidity.cfg`. That makes it clear, one just has to `source` another configuration. I'll use that next time for testing. I wouldn't worry about anything about the font that's not in the Debian repository (unless someone complains - unlikely given that we don't currently provide any MIDI support and nobody ever complained at all). It's not worth the troubles. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 20:14:30 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 19:14:30 -0000 Subject: [MacPorts] #52995: py-pygraphviz: add suports for python 3 Message-ID: <042.815f705f74435eb2981ed161f4ff42b1@macports.org> #52995: py-pygraphviz: add suports for python 3 --------------------+--------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: py-pygraphviz --------------------+--------------------------- Not sure what type of ticket this is, but following [https://github.com/macports/macports-ports/pull/76 PR #76] I tried to add subports for python 3.4 and 3.5 to `py-pygraphviz` and failed. I tested versions 1.1, 1.3, 1.4rc1. I suspect that 1.1 is not compatible, 1.3 is most likely missing a file, 1.4rc1 fails with {{{ running install dpkg-query: no path found matching pattern *graphviz* Trying dpkg Traceback (most recent call last): File "setup.py", line 93, in tests_require=['nose>=0.10.1', 'doctest-ignore-unicode>=0.1.0', 'mock>=1.3'], File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/distutils/core.py", line 148, in setup dist.run_commands() File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/distutils/dist.py", line 955, in run_commands self.run_command(cmd) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/distutils/dist.py", line 974, in run_command cmd_obj.run() File "/path/to/py35-pygraphviz/work/pygraphviz-1.4rc1/setup_commands.py", line 44, in modified_run self.include_path, self.library_path = get_graphviz_dirs() File "/path/to/py35-pygraphviz/work/pygraphviz-1.4rc1/setup_extra.py", line 156, in get_graphviz_dirs include_dirs, library_dirs = _try_configure(include_dirs, library_dirs, _dpkg_config) File "/path/to/py35-pygraphviz/work/pygraphviz-1.4rc1/setup_extra.py", line 115, in _try_configure i, l = try_function() File "/path/to/py35-pygraphviz/work/pygraphviz-1.4rc1/setup_extra.py", line 47, in _dpkg_config output = S.check_output(['dpkg', '-S', 'graphviz']) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/subprocess.py", line 626, in check_output **kwargs).stdout File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/subprocess.py", line 708, in run output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '['dpkg', '-S', 'graphviz']' returned non-zero exit status 1 Command failed: cd "/path/to/py35-pygraphviz/work/pygraphviz-1.4rc1" && /opt/local/Library/Frameworks/Python.framework/Versions/3.5/bin/python3.5 setup.py --no-user-cfg install --prefix=/opt/local/Library/Frameworks/Python.framework/Versions/3.5 --root=/path/to/py35-pygraphviz/work/destroot Exit code: 1 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 20:18:11 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 19:18:11 -0000 Subject: [MacPorts] #52995: py-pygraphviz: add suports for python 3 In-Reply-To: <042.815f705f74435eb2981ed161f4ff42b1@macports.org> References: <042.815f705f74435eb2981ed161f4ff42b1@macports.org> Message-ID: <057.bd8b301332c8395ad9aa64a1c24b1cd9@macports.org> #52995: py-pygraphviz: add suports for python 3 ----------------------------+----------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-pygraphviz | ----------------------------+----------------- Description changed by mojca: Old description: > Not sure what type of ticket this is, but following > [https://github.com/macports/macports-ports/pull/76 PR #76] I tried to > add subports for python 3.4 and 3.5 to `py-pygraphviz` and failed. > > I tested versions 1.1, 1.3, 1.4rc1. I suspect that 1.1 is not compatible, > 1.3 is most likely missing a file, 1.4rc1 fails with > {{{ > running install > dpkg-query: no path found matching pattern *graphviz* > Trying dpkg > Traceback (most recent call last): > File "setup.py", line 93, in > tests_require=['nose>=0.10.1', 'doctest-ignore-unicode>=0.1.0', > 'mock>=1.3'], > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/distutils/core.py", > line 148, in setup > dist.run_commands() > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/distutils/dist.py", > line 955, in run_commands > self.run_command(cmd) > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/distutils/dist.py", > line 974, in run_command > cmd_obj.run() > File > "/path/to/py35-pygraphviz/work/pygraphviz-1.4rc1/setup_commands.py", line > 44, in modified_run > self.include_path, self.library_path = get_graphviz_dirs() > File "/path/to/py35-pygraphviz/work/pygraphviz-1.4rc1/setup_extra.py", > line 156, in get_graphviz_dirs > include_dirs, library_dirs = _try_configure(include_dirs, > library_dirs, _dpkg_config) > File "/path/to/py35-pygraphviz/work/pygraphviz-1.4rc1/setup_extra.py", > line 115, in _try_configure > i, l = try_function() > File "/path/to/py35-pygraphviz/work/pygraphviz-1.4rc1/setup_extra.py", > line 47, in _dpkg_config > output = S.check_output(['dpkg', '-S', 'graphviz']) > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/subprocess.py", > line 626, in check_output > **kwargs).stdout > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/subprocess.py", > line 708, in run > output=stdout, stderr=stderr) > subprocess.CalledProcessError: Command '['dpkg', '-S', 'graphviz']' > returned non-zero exit status 1 > Command failed: cd "/path/to/py35-pygraphviz/work/pygraphviz-1.4rc1" && > /opt/local/Library/Frameworks/Python.framework/Versions/3.5/bin/python3.5 > setup.py --no-user-cfg install > --prefix=/opt/local/Library/Frameworks/Python.framework/Versions/3.5 > --root=/path/to/py35-pygraphviz/work/destroot > Exit code: 1 > }}} New description: Not sure what type of ticket this is, but following [https://github.com/macports/macports-ports/pull/76 PR #76] I tried to add subports for python 3.4 and 3.5 to `py-pygraphviz` and failed. I tested versions 1.1, 1.3, 1.4rc1. I suspect that 1.1 is not compatible, 1.3 is most likely missing a file: {{{ DEBUG: system: cd "/path/to/py35-pygraphviz/work/pygraphviz-1.3" && /opt/local/Library/Frameworks/Python.framework/Versions/3.5/bin/python3.5 setup.py --no-user-cfg build Traceback (most recent call last): File "setup.py", line 16, in from setup_commands import AddExtensionDevelopCommand, AddExtensionInstallCommand ImportError: No module named 'setup_commands' }}} 1.4rc1 fails with {{{ running install dpkg-query: no path found matching pattern *graphviz* Trying dpkg Traceback (most recent call last): File "setup.py", line 93, in tests_require=['nose>=0.10.1', 'doctest-ignore-unicode>=0.1.0', 'mock>=1.3'], File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/distutils/core.py", line 148, in setup dist.run_commands() File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/distutils/dist.py", line 955, in run_commands self.run_command(cmd) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/distutils/dist.py", line 974, in run_command cmd_obj.run() File "/path/to/py35-pygraphviz/work/pygraphviz-1.4rc1/setup_commands.py", line 44, in modified_run self.include_path, self.library_path = get_graphviz_dirs() File "/path/to/py35-pygraphviz/work/pygraphviz-1.4rc1/setup_extra.py", line 156, in get_graphviz_dirs include_dirs, library_dirs = _try_configure(include_dirs, library_dirs, _dpkg_config) File "/path/to/py35-pygraphviz/work/pygraphviz-1.4rc1/setup_extra.py", line 115, in _try_configure i, l = try_function() File "/path/to/py35-pygraphviz/work/pygraphviz-1.4rc1/setup_extra.py", line 47, in _dpkg_config output = S.check_output(['dpkg', '-S', 'graphviz']) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/subprocess.py", line 626, in check_output **kwargs).stdout File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/subprocess.py", line 708, in run output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '['dpkg', '-S', 'graphviz']' returned non-zero exit status 1 Command failed: cd "/path/to/py35-pygraphviz/work/pygraphviz-1.4rc1" && /opt/local/Library/Frameworks/Python.framework/Versions/3.5/bin/python3.5 setup.py --no-user-cfg install --prefix=/opt/local/Library/Frameworks/Python.framework/Versions/3.5 --root=/path/to/py35-pygraphviz/work/destroot Exit code: 1 }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 20:35:32 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 19:35:32 -0000 Subject: [MacPorts] #52996: py35-setuptools @28.8.0: Install cannot fetch the py35-setuptools-28.8.0 distribution files Message-ID: <043.3005f07d3390429531f3561d8bc23ef9@macports.org> #52996: py35-setuptools @28.8.0: Install cannot fetch the py35-setuptools-28.8.0 distribution files --------------------+----------------------------- Reporter: o2plus | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: py35-setuptools --------------------+----------------------------- Installation of py35-setuptools is unable to fetch a setuptools-28.8.0.tar.gz distribution file. (This also occurs for py27-setuptools). The terminal record is: {{{% sudo port clean py35-setuptools ---> Cleaning py35-setuptools % sudo port install py35-setuptools ---> Computing dependencies for py35-setuptools ---> Fetching archive for py35-setuptools ---> Attempting to fetch py35-setuptools-28.8.0_0.darwin_8.noarch.tbz2 from http://packages.macports.org/py35-setuptools ---> Attempting to fetch py35-setuptools-28.8.0_0.darwin_8.noarch.tbz2 from http://sea.us.packages.macports.org/macports/packages/py35-setuptools ---> Attempting to fetch py35-setuptools-28.8.0_0.darwin_8.noarch.tbz2 from http://lil.fr.packages.macports.org/py35-setuptools ---> Fetching distfiles for py35-setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from https://pypi.python.org/packages/source/s/setuptools/ ---> Attempting to fetch setuptools-28.8.0.tar.gz from https://files.pythonhosted.org/packages/source/s/setuptools/ ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://distfiles.macports.org/py-setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://sea.us.distfiles.macports.org/macports/distfiles/py-setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/py-setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://cjj.kr.distfiles.macports.org/py-setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://nue.de.distfiles.macports.org/py-setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://lil.fr.distfiles.macports.org/py-setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/py- setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://osl.no.distfiles.macports.org/py-setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org /py-setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/py- setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/py- setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://jog.id.distfiles.macports.org/macports/distfiles/py-setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://jnb.za.distfiles.macports.org/distfiles/py-setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://her.gr.distfiles.macports.org/py-setuptools Error: org.macports.fetch for port py35-setuptools returned: fetch failed Please see the log file for port py35-setuptools for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_ports_python_py-setuptools/py35-setuptools/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port py35-setuptools failed }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 20:51:00 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 19:51:00 -0000 Subject: [MacPorts] #52882: Removal of py26-apptools and py26-chaco left py26-blockcanvas broken In-Reply-To: <043.60283e312ce190d6a1b0058fd4c7f369@macports.org> References: <043.60283e312ce190d6a1b0058fd4c7f369@macports.org> Message-ID: <058.ca1a925a9c13f80c7b19679c362438ef@macports.org> #52882: Removal of py26-apptools and py26-chaco left py26-blockcanvas broken -------------------------------+----------------------- Reporter: jmroot | Owner: jjstickel Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: py26-blockcanvas | -------------------------------+----------------------- Changes (by larryv): * status: new => closed * resolution: => fixed Comment: In [changeset:"0c6ccb0a8a52993994a09aee94e304b4e3618022/macports-ports" 0c6ccb0a/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="0c6ccb0a8a52993994a09aee94e304b4e3618022" py26-blockcanvas: Replace with py27-blockcanvas Closes https://trac.macports.org/ticket/52882 (maintainer permission). }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 20:51:00 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 19:51:00 -0000 Subject: [MacPorts] #52883: Removal of py26-traits left dependents broken In-Reply-To: <043.af32dc7eb53036621308928d5e814906@macports.org> References: <043.af32dc7eb53036621308928d5e814906@macports.org> Message-ID: <058.43e49fa633730e52b2a7638f04a6bd1e@macports.org> #52883: Removal of py26-traits left dependents broken -------------------------------------------------+------------------------- Reporter: jmroot | Owner: jjstickel Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: py26-scimath py26-etsdevtools | py26-codetools | -------------------------------------------------+------------------------- Comment (by larryv): In [changeset:"7f0147179b7064226e1b7fecd8d05816137a24c5/macports-ports" 7f014717/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="7f0147179b7064226e1b7fecd8d05816137a24c5" py26-codetools: Replace with py27-codetools See https://trac.macports.org/ticket/52883. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 20:51:00 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 19:51:00 -0000 Subject: [MacPorts] #52883: Removal of py26-traits left dependents broken In-Reply-To: <043.af32dc7eb53036621308928d5e814906@macports.org> References: <043.af32dc7eb53036621308928d5e814906@macports.org> Message-ID: <058.709099349e357a7fc1ac6d611030bb46@macports.org> #52883: Removal of py26-traits left dependents broken -------------------------------------------------+------------------------- Reporter: jmroot | Owner: jjstickel Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: py26-scimath py26-etsdevtools | py26-codetools | -------------------------------------------------+------------------------- Comment (by larryv): In [changeset:"37e6472bcf1744cab3729d919b078353d414755b/macports-ports" 37e6472b/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="37e6472bcf1744cab3729d919b078353d414755b" py26-etsdevtools: Replace with py27-etsdevtools See https://trac.macports.org/ticket/52883. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 20:51:00 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 19:51:00 -0000 Subject: [MacPorts] #52883: Removal of py26-traits left dependents broken In-Reply-To: <043.af32dc7eb53036621308928d5e814906@macports.org> References: <043.af32dc7eb53036621308928d5e814906@macports.org> Message-ID: <058.ebfbfb593552c2dad831d13bdd0248ab@macports.org> #52883: Removal of py26-traits left dependents broken -------------------------------------------------+------------------------- Reporter: jmroot | Owner: jjstickel Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: py26-scimath py26-etsdevtools | py26-codetools | -------------------------------------------------+------------------------- Changes (by larryv): * status: new => closed * resolution: => fixed Comment: In [changeset:"8ff7a492754398e7a7b31b279187102674beae27/macports-ports" 8ff7a492/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="8ff7a492754398e7a7b31b279187102674beae27" py26-scimath: Replace with py27-scimath Closes https://trac.macports.org/ticket/52883. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 20:52:22 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 19:52:22 -0000 Subject: [MacPorts] #52997: swi-prolog-devel @7.3.31: update to 7.3.32 Message-ID: <043.dcbb2252db3b572a66119f787c70493d@macports.org> #52997: swi-prolog-devel @7.3.31: update to 7.3.32 ---------------------------------+------------------------------ Reporter: pmoura | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch maintainer | Port: swi-prolog-devel ---------------------------------+------------------------------ Update the swi-prolog-devel portfile for the latest release. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 20:52:43 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 19:52:43 -0000 Subject: [MacPorts] #52997: swi-prolog-devel @7.3.31: update to 7.3.32 In-Reply-To: <043.dcbb2252db3b572a66119f787c70493d@macports.org> References: <043.dcbb2252db3b572a66119f787c70493d@macports.org> Message-ID: <058.a35c2655c46ea15f8d97ad54bd943b54@macports.org> #52997: swi-prolog-devel @7.3.31: update to 7.3.32 -------------------------------+--------------------------------- Reporter: pmoura | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: swi-prolog-devel | -------------------------------+--------------------------------- Changes (by pmoura): * Attachment "Portfile-swi-prolog-devel.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 20:54:22 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 19:54:22 -0000 Subject: [MacPorts] #52997: swi-prolog-devel @7.3.31: update to 7.3.32 In-Reply-To: <043.dcbb2252db3b572a66119f787c70493d@macports.org> References: <043.dcbb2252db3b572a66119f787c70493d@macports.org> Message-ID: <058.0bbe05793f3b6859d0bd3b60f455cf75@macports.org> #52997: swi-prolog-devel @7.3.31: update to 7.3.32 -------------------------------+--------------------------------- Reporter: pmoura | Owner: larryv Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: swi-prolog-devel | -------------------------------+--------------------------------- Changes (by larryv): * owner: => larryv * status: new => accepted Comment: Thanks! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 21:19:29 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 20:19:29 -0000 Subject: [MacPorts] #52996: py35-setuptools @28.8.0: Install cannot fetch the py35-setuptools-28.8.0 distribution files In-Reply-To: <043.3005f07d3390429531f3561d8bc23ef9@macports.org> References: <043.3005f07d3390429531f3561d8bc23ef9@macports.org> Message-ID: <058.ef65bc1cc92b361b095feb847915af15@macports.org> #52996: py35-setuptools @28.8.0: Install cannot fetch the py35-setuptools-28.8.0 distribution files ----------------------------+---------------------- Reporter: o2plus | Owner: jmroot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: py-setuptools | ----------------------------+---------------------- Changes (by mf2k): * owner: => jmroot * cc: jmr@… (removed) * status: new => assigned * port: py35-setuptools => py-setuptools Comment: In the future, please use WikiFormatting. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 21:19:44 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 20:19:44 -0000 Subject: [MacPorts] #52996: py35-setuptools @28.8.0: Install cannot fetch the py35-setuptools-28.8.0 distribution files In-Reply-To: <043.3005f07d3390429531f3561d8bc23ef9@macports.org> References: <043.3005f07d3390429531f3561d8bc23ef9@macports.org> Message-ID: <058.480df9f510682782826c93776cd5d1ca@macports.org> #52996: py35-setuptools @28.8.0: Install cannot fetch the py35-setuptools-28.8.0 distribution files ----------------------------+---------------------- Reporter: o2plus | Owner: jmroot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: py-setuptools | ----------------------------+---------------------- Description changed by mf2k: Old description: > Installation of py35-setuptools is unable to fetch a > setuptools-28.8.0.tar.gz distribution file. (This also occurs for > py27-setuptools). The terminal record is: > {{{% sudo port clean py35-setuptools > ---> Cleaning py35-setuptools > % sudo port install py35-setuptools > ---> Computing dependencies for py35-setuptools > ---> Fetching archive for py35-setuptools > ---> Attempting to fetch py35-setuptools-28.8.0_0.darwin_8.noarch.tbz2 > from http://packages.macports.org/py35-setuptools > ---> Attempting to fetch py35-setuptools-28.8.0_0.darwin_8.noarch.tbz2 > from > http://sea.us.packages.macports.org/macports/packages/py35-setuptools > ---> Attempting to fetch py35-setuptools-28.8.0_0.darwin_8.noarch.tbz2 > from http://lil.fr.packages.macports.org/py35-setuptools > ---> Fetching distfiles for py35-setuptools > ---> Attempting to fetch setuptools-28.8.0.tar.gz from > https://pypi.python.org/packages/source/s/setuptools/ > ---> Attempting to fetch setuptools-28.8.0.tar.gz from > https://files.pythonhosted.org/packages/source/s/setuptools/ > ---> Attempting to fetch setuptools-28.8.0.tar.gz from > http://distfiles.macports.org/py-setuptools > ---> Attempting to fetch setuptools-28.8.0.tar.gz from > http://sea.us.distfiles.macports.org/macports/distfiles/py-setuptools > ---> Attempting to fetch setuptools-28.8.0.tar.gz from > http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/py-setuptools > ---> Attempting to fetch setuptools-28.8.0.tar.gz from > http://cjj.kr.distfiles.macports.org/py-setuptools > ---> Attempting to fetch setuptools-28.8.0.tar.gz from > http://nue.de.distfiles.macports.org/py-setuptools > ---> Attempting to fetch setuptools-28.8.0.tar.gz from > http://lil.fr.distfiles.macports.org/py-setuptools > ---> Attempting to fetch setuptools-28.8.0.tar.gz from > http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/py- > setuptools > ---> Attempting to fetch setuptools-28.8.0.tar.gz from > http://osl.no.distfiles.macports.org/py-setuptools > ---> Attempting to fetch setuptools-28.8.0.tar.gz from > http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org > /py-setuptools > ---> Attempting to fetch setuptools-28.8.0.tar.gz from > http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/py- > setuptools > ---> Attempting to fetch setuptools-28.8.0.tar.gz from > http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/py- > setuptools > ---> Attempting to fetch setuptools-28.8.0.tar.gz from > http://jog.id.distfiles.macports.org/macports/distfiles/py-setuptools > ---> Attempting to fetch setuptools-28.8.0.tar.gz from > http://jnb.za.distfiles.macports.org/distfiles/py-setuptools > ---> Attempting to fetch setuptools-28.8.0.tar.gz from > http://her.gr.distfiles.macports.org/py-setuptools > Error: org.macports.fetch for port py35-setuptools returned: fetch failed > Please see the log file for port py35-setuptools for details: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports > .org_release_ports_python_py-setuptools/py35-setuptools/main.log > To report a bug, follow the instructions in the guide: > http://guide.macports.org/#project.tickets > Error: Processing of port py35-setuptools failed > }}} New description: Installation of py35-setuptools is unable to fetch a setuptools-28.8.0.tar.gz distribution file. (This also occurs for py27-setuptools). The terminal record is: {{{ % sudo port clean py35-setuptools ---> Cleaning py35-setuptools % sudo port install py35-setuptools ---> Computing dependencies for py35-setuptools ---> Fetching archive for py35-setuptools ---> Attempting to fetch py35-setuptools-28.8.0_0.darwin_8.noarch.tbz2 from http://packages.macports.org/py35-setuptools ---> Attempting to fetch py35-setuptools-28.8.0_0.darwin_8.noarch.tbz2 from http://sea.us.packages.macports.org/macports/packages/py35-setuptools ---> Attempting to fetch py35-setuptools-28.8.0_0.darwin_8.noarch.tbz2 from http://lil.fr.packages.macports.org/py35-setuptools ---> Fetching distfiles for py35-setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from https://pypi.python.org/packages/source/s/setuptools/ ---> Attempting to fetch setuptools-28.8.0.tar.gz from https://files.pythonhosted.org/packages/source/s/setuptools/ ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://distfiles.macports.org/py-setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://sea.us.distfiles.macports.org/macports/distfiles/py-setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/py-setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://cjj.kr.distfiles.macports.org/py-setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://nue.de.distfiles.macports.org/py-setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://lil.fr.distfiles.macports.org/py-setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/py- setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://osl.no.distfiles.macports.org/py-setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org /py-setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/py- setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/py- setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://jog.id.distfiles.macports.org/macports/distfiles/py-setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://jnb.za.distfiles.macports.org/distfiles/py-setuptools ---> Attempting to fetch setuptools-28.8.0.tar.gz from http://her.gr.distfiles.macports.org/py-setuptools Error: org.macports.fetch for port py35-setuptools returned: fetch failed Please see the log file for port py35-setuptools for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_ports_python_py-setuptools/py35-setuptools/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port py35-setuptools failed }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 21:51:06 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 20:51:06 -0000 Subject: [MacPorts] #52306: mozjs17 @17.0.0_4+universal: js17-config differs in i386 and x86_64 builds, cannot be merged In-Reply-To: <052.4f90720235627e6e89a2affd492ad992@macports.org> References: <052.4f90720235627e6e89a2affd492ad992@macports.org> Message-ID: <067.f5aa8f9db63f1f7caba3a1f49c4fd3aa@macports.org> #52306: mozjs17 @17.0.0_4+universal: js17-config differs in i386 and x86_64 builds, cannot be merged ------------------------------+--------------------- Reporter: MichalMisiaszek | Owner: dbevans Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: mosjz17 | ------------------------------+--------------------- Comment (by MichalMisiaszek): Hi, So 2 months passed and problem is not fixed still blocking my use of MacPorts. Anything I can do to fix it ? Regards Michal -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 21:55:51 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 20:55:51 -0000 Subject: [MacPorts] #52997: swi-prolog-devel @7.3.31: update to 7.3.32 In-Reply-To: <043.dcbb2252db3b572a66119f787c70493d@macports.org> References: <043.dcbb2252db3b572a66119f787c70493d@macports.org> Message-ID: <058.f8933a11ecab920eba2028b9d05c3fb9@macports.org> #52997: swi-prolog-devel @7.3.31: update to 7.3.32 -------------------------------+--------------------------------- Reporter: pmoura | Owner: larryv Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch maintainer Port: swi-prolog-devel | -------------------------------+--------------------------------- Changes (by pmoura): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"f379e42e9fe817065a6ee6c8782929488c02f02b/macports-ports" f379e42e/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="f379e42e9fe817065a6ee6c8782929488c02f02b" swi-prolog-devel: Update to 7.3.32 Closes https://trac.macports.org/ticket/52997. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 22:19:15 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 21:19:15 -0000 Subject: [MacPorts] #52306: mozjs17 @17.0.0_4+universal: js17-config differs in i386 and x86_64 builds, cannot be merged In-Reply-To: <052.4f90720235627e6e89a2affd492ad992@macports.org> References: <052.4f90720235627e6e89a2affd492ad992@macports.org> Message-ID: <067.616a877f8d67d93484f7d470e1c0fb07@macports.org> #52306: mozjs17 @17.0.0_4+universal: js17-config differs in i386 and x86_64 builds, cannot be merged ------------------------------+--------------------- Reporter: MichalMisiaszek | Owner: dbevans Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: mosjz17 | ------------------------------+--------------------- Comment (by raimue): As this stops you from using MacPorts, do you actually need the +universal variant (that means 32-bit and 64-bit in the same binary)? If not, you can simply remove it. {{{ sudo port clean mozjs17 sudo port -n upgrade --enforce-variants mozjs17 -universal }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 23:15:04 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 22:15:04 -0000 Subject: [MacPorts] #52306: mozjs17 @17.0.0_4+universal: js17-config differs in i386 and x86_64 builds, cannot be merged In-Reply-To: <052.4f90720235627e6e89a2affd492ad992@macports.org> References: <052.4f90720235627e6e89a2affd492ad992@macports.org> Message-ID: <067.f6cd41116788329900c60a83fdbbbef7@macports.org> #52306: mozjs17 @17.0.0_4+universal: js17-config differs in i386 and x86_64 builds, cannot be merged ------------------------------+--------------------- Reporter: MichalMisiaszek | Owner: dbevans Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: mosjz17 | ------------------------------+--------------------- Comment (by MichalMisiaszek): So I did tried your suggestion, but effect is the same: {{{ --> Attempting to fetch mozjs17-17.0.0_4+universal.darwin_14.i386-x86_64.tbz2 from https://packages.macports.org/mozjs17 ---> Attempting to fetch mozjs17-17.0.0_4+universal.darwin_14.i386-x86_64.tbz2 from http://sea.us.packages.macports.org/macports/packages/mozjs17 ---> Attempting to fetch mozjs17-17.0.0_4+universal.darwin_14.i386-x86_64.tbz2 from http://lil.fr.packages.macports.org/mozjs17 ---> Fetching distfiles for mozjs17 ---> Verifying checksums for mozjs17 ---> Extracting mozjs17 ---> Applying patches to mozjs17 ---> Configuring mozjs17 ---> Building mozjs17 ---> Staging mozjs17 into destroot Error: org.macports.destroot for port mozjs17 returned: js17-config differs in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_mozjs17/mozjs17/work/destroot-i386//opt/local/bin and /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_mozjs17/mozjs17/work /destroot-x86_64//opt/local/bin and cannot be merged Error: Failed to install mozjs17 Please see the log file for port mozjs17 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_mozjs17/mozjs17/main.log Error: The following dependencies were not installed: mozjs17 Error: Problem while installing policykit Error rebuilding gconf while executing "error "Error rebuilding $portname"" (procedure "revupgrade_scanandrebuild" line 395) invoked from within "revupgrade_scanandrebuild broken_port_counts $opts" (procedure "macports::revupgrade" line 5) invoked from within "macports::revupgrade $opts" (procedure "action_revupgrade" line 2) invoked from within "action_revupgrade $action $portlist $opts" (procedure "action_upgrade" line 25) invoked from within "$action_proc $action $portlist [array get global_options]" (procedure "process_cmd" line 103) invoked from within "process_cmd $remaining_args" invoked from within "if { [llength $remaining_args] > 0 } { # If there are remaining arguments, process those as a command set exit_status [process_cmd $remaining..." (file "/opt/local/bin/port" line 5286) }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 23:46:27 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 22:46:27 -0000 Subject: [MacPorts] #52306: mozjs17 @17.0.0_4+universal: js17-config differs in i386 and x86_64 builds, cannot be merged In-Reply-To: <052.4f90720235627e6e89a2affd492ad992@macports.org> References: <052.4f90720235627e6e89a2affd492ad992@macports.org> Message-ID: <067.0e4d3851b28aa36bcf33165eb9988773@macports.org> #52306: mozjs17 @17.0.0_4+universal: js17-config differs in i386 and x86_64 builds, cannot be merged ------------------------------+--------------------- Reporter: MichalMisiaszek | Owner: dbevans Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: mozjs17 | ------------------------------+--------------------- Changes (by raimue): * port: mosjz17 => mozjs17 Comment: Your log excerpt is still using +universal and is talking about policykit. I assume this is again an attempt to upgrade. This will fail in the same way unless you also remove +universal from all dependents of mozjs17. You should focus on why you even have it installed as +universal if you do not know that. You would have to find out which of the ports you want to have installed actually needs +universal (`port -q installed requested | grep '\+universal'`). Anyway, to add another data point, `mozjs17 @17.0.0_4+universal` installs fine for me on my macOS 10.12 Sierra with Xcode 8.1. I cannot reproduce the original report. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 23:56:21 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 22:56:21 -0000 Subject: [MacPorts] #52306: mozjs17 @17.0.0_4+universal: js17-config differs in i386 and x86_64 builds, cannot be merged In-Reply-To: <052.4f90720235627e6e89a2affd492ad992@macports.org> References: <052.4f90720235627e6e89a2affd492ad992@macports.org> Message-ID: <067.c94b6af4f3577d97afa83ea024f788b8@macports.org> #52306: mozjs17 @17.0.0_4+universal: js17-config differs in i386 and x86_64 builds, cannot be merged ------------------------------+--------------------- Reporter: MichalMisiaszek | Owner: dbevans Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: mozjs17 | ------------------------------+--------------------- Comment (by MichalMisiaszek): I executed commands you suggested. How I can enforce to install only 64 bit not universal. I think gtk3 and ploicykit is enforcing universal though your command pointed to something else. {{{ ---> Cleaning gtk3 ---> Computing dependencies for policykit ---> Dependencies to be installed: mozjs17 ---> Fetching archive for mozjs17 ---> Attempting to fetch mozjs17-17.0.0_4+universal.darwin_14.i386-x86_64.tbz2 from https://packages.macports.org/mozjs17 ---> Attempting to fetch mozjs17-17.0.0_4+universal.darwin_14.i386-x86_64.tbz2 from http://sea.us.packages.macports.org/macports/packages/mozjs17 ---> Attempting to fetch mozjs17-17.0.0_4+universal.darwin_14.i386-x86_64.tbz2 from http://lil.fr.packages.macports.org/mozjs17 ---> Fetching distfiles for mozjs17 ---> Verifying checksums for mozjs17 ---> Extracting mozjs17 ---> Applying patches to mozjs17 ---> Configuring mozjs17 ---> Building mozjs17 ---> Staging mozjs17 into destroot Error: org.macports.destroot for port mozjs17 returned: js17-config differs in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_mozjs17/mozjs17/work/destroot-i386//opt/local/bin and /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_mozjs17/mozjs17/work /destroot-x86_64//opt/local/bin and cannot be merged Error: Failed to install mozjs17 Please see the log file for port mozjs17 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_mozjs17/mozjs17/main.log Error: The following dependencies were not installed: mozjs17 Error: Problem while installing policykit Error rebuilding gconf while executing "error "Error rebuilding $portname"" (procedure "revupgrade_scanandrebuild" line 395) invoked from within "revupgrade_scanandrebuild broken_port_counts $opts" (procedure "macports::revupgrade" line 5) invoked from within "macports::revupgrade $opts" (procedure "action_revupgrade" line 2) invoked from within "action_revupgrade $action $portlist $opts" (procedure "action_target" line 96) invoked from within "$action_proc $action $portlist [array get global_options]" (procedure "process_cmd" line 103) invoked from within "process_cmd $remaining_args" invoked from within "if { [llength $remaining_args] > 0 } { # If there are remaining arguments, process those as a command set exit_status [process_cmd $remaining..." (file "/opt/local/bin/port" line 5286) Michals-MBP:USRP Michal$ port -q installed requested | grep '\+universal' boost @1.59.0_2+no_single+no_static+python27+universal (active) fftw-3 @3.3.4_1+universal }}} I am using Yosemite and Xcode 7.1, the OS Sierra is not supported by some of my development tools yet. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 00:09:08 2016 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2016 23:09:08 -0000 Subject: [MacPorts] #52996: py35-setuptools @28.8.0: Install cannot fetch the py35-setuptools-28.8.0 distribution files In-Reply-To: <043.3005f07d3390429531f3561d8bc23ef9@macports.org> References: <043.3005f07d3390429531f3561d8bc23ef9@macports.org> Message-ID: <058.3ff4b354acb1b49667afdf087538e08f@macports.org> #52996: py35-setuptools @28.8.0: Install cannot fetch the py35-setuptools-28.8.0 distribution files ----------------------------+-------------------- Reporter: o2plus | Owner: jmroot Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: duplicate | Keywords: tiger Port: py-setuptools | ----------------------------+-------------------- Changes (by jmroot): * keywords: => tiger * status: assigned => closed * resolution: => duplicate Comment: #46630 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 01:17:01 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 00:17:01 -0000 Subject: [MacPorts] #46432: scons messes up the environment and removes ${prefix}/bin from $PATH In-Reply-To: <045.96fe94e36d30d897f32b1283dd320144@macports.org> References: <045.96fe94e36d30d897f32b1283dd320144@macports.org> Message-ID: <060.919aef13ede4e1a0076a899f805f46f8@macports.org> #46432: scons messes up the environment and removes ${prefix}/bin from $PATH -----------------------+-------------------------------- Reporter: jeremyhu | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: scons | -----------------------+-------------------------------- Comment (by larryv): I’ve updated `scons` to 2.5.1. Is this still an issue? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 01:17:18 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 00:17:18 -0000 Subject: [MacPorts] #47476: scons does not properly add header guards to generated config header In-Reply-To: <061.6c27ebcd37eca92d21ebd426ffd9e308@macports.org> References: <061.6c27ebcd37eca92d21ebd426ffd9e308@macports.org> Message-ID: <076.1d3505ed885929e0642880686b1eb188@macports.org> #47476: scons does not properly add header guards to generated config header ------------------------------+-------------------------------- Reporter: Peter_Dyballa@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: scons | ------------------------------+-------------------------------- Comment (by larryv): I’ve updated `scons` to 2.5.1. Is this still an issue? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 02:00:55 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 01:00:55 -0000 Subject: [MacPorts] #52998: creduce @2.5.0: build requires C++11 and libc++ Message-ID: <043.127f66559e3a8c8bd757792b54431edf@macports.org> #52998: creduce @2.5.0: build requires C++11 and libc++ --------------------+--------------------- Reporter: larryv | Owner: larryv Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: creduce --------------------+--------------------- - https://build.macports.org/builders/ports-10.6_i386_legacy- builder/builds/11648 - https://build.macports.org/builders/ports-10.6_x86_64_legacy- builder/builds/12006 - https://build.macports.org/builders/ports-10.7_x86_64_legacy- builder/builds/17243 - https://build.macports.org/builders/ports-10.8_x86_64_legacy- builder/builds/11942 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 02:01:08 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 01:01:08 -0000 Subject: [MacPorts] #52998: creduce @2.5.0: build requires C++11 and libc++ In-Reply-To: <043.127f66559e3a8c8bd757792b54431edf@macports.org> References: <043.127f66559e3a8c8bd757792b54431edf@macports.org> Message-ID: <058.646171a8bac3a5c18e120fbd58fbf28f@macports.org> #52998: creduce @2.5.0: build requires C++11 and libc++ ----------------------+---------------------- Reporter: larryv | Owner: larryv Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: creduce | ----------------------+---------------------- Changes (by larryv): * status: new => accepted -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 03:06:53 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 02:06:53 -0000 Subject: [MacPorts] #52940: selfupdate @2.3.5: failing to connect to rsync.macports.org In-Reply-To: <047.25a06c334e7477dec599e2d5604a2844@macports.org> References: <047.25a06c334e7477dec599e2d5604a2844@macports.org> Message-ID: <062.ff513a18ba686b4c5b67783527311a02@macports.org> #52940: selfupdate @2.3.5: failing to connect to rsync.macports.org -------------------------+-------------------------------- Reporter: jrubinator | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.3.5 Resolution: invalid | Keywords: Port: | -------------------------+-------------------------------- Changes (by ryandesign): * status: new => closed * resolution: => invalid Comment: This doesn't sound like a MacPorts bug. If you need further help resolving your network and/or permissions issues, please write to the macports-users mailing list. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 05:36:17 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 04:36:17 -0000 Subject: [MacPorts] #48637: python25 @2.5.6_5: clang: error: unknown argument: '-mno-fused-madd' In-Reply-To: <046.65e2904ac57615f6bfa54ac76b898679@macports.org> References: <046.65e2904ac57615f6bfa54ac76b898679@macports.org> Message-ID: <061.2ea82c615f2864e3c834f19937d1b41f@macports.org> #48637: python25 @2.5.6_5: clang: error: unknown argument: '-mno-fused-madd' ------------------------+---------------------- Reporter: fhgwright | Owner: larryv Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: python25 | ------------------------+---------------------- Comment (by larryv): Relevant upstream bug report: http://bugs.python.org/issue1779871 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 08:08:31 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 07:08:31 -0000 Subject: [MacPorts] #52995: py-pygraphviz: add suports for python 3 In-Reply-To: <042.815f705f74435eb2981ed161f4ff42b1@macports.org> References: <042.815f705f74435eb2981ed161f4ff42b1@macports.org> Message-ID: <057.8832382e44eaffc9f8859846b921f76d@macports.org> #52995: py-pygraphviz: add suports for python 3 ----------------------------+----------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-pygraphviz | ----------------------------+----------------- Changes (by mojca): * cc: aric.hagberg@… (added) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 09:18:42 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 08:18:42 -0000 Subject: [MacPorts] #52490: [Port Abandoned] Ports maintained by hum In-Reply-To: <041.9d8ed880a58e228011e8b4ff5729ba02@macports.org> References: <041.9d8ed880a58e228011e8b4ff5729ba02@macports.org> Message-ID: <056.e4e8f8626a3998301caf35261e986371@macports.org> #52490: [Port Abandoned] Ports maintained by hum -------------------------------------------------+------------------------- Reporter: mf2k | Owner: humem Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: apache-solr3 apache-solr4 arowpp | bact bayon brown-cluster cabocha caffe cedar | chasen chasen-base chasen-ipadic chasen- | ipadic-sjis chasen-ipadic-utf8 chasen-naist- | jdic chasen-naist-jdic-sjis chasen-naist- | jdic-utf8 cicada classias cpi00 crfpp crfpp- | devel crfsuite cutter darts darts-clone | dualist eda emacs-app emacs-mac-app expgram | extractopinion gibbslda giza-pp google-glog | groonga hadoop hts_engine_API irstlm jdepp | jubatus jubatus-mpio jubatus-msgpack-rpc | jubatus_core julius juman juman6 kakarot KNBC | knp knp3 kytea lader lda-c lda-d liblbfgs | liblinear libsvm libzookeeper lmdb lucene- | gosen2 lucene-gosen4 mahout mallet marisa- | trie mecab mecab-base mecab-ipadic mecab- | ipadic-neologd mecab-ipadic-sjis mecab- | ipadic-utf8 mecab-java mecab-jumandic mecab- | jumandic-sjis mecab-jumandic-utf8 mecab- | naist-jdic mecab-naist-jdic-sjis mecab-naist- | jdic-utf8 mecab-sjis mecab-utf8 mgizapp | MMDAgent mosesdecoder msgpack msgpack1 | normalizeNumexp oll oniguruma5 opal-ml | open_jtalk openfst p5-mecab p5-termextract p5 | -text-csv_xs palmkit pecco pficommon pialign | plda portaudio py-breadability py-chainer py- | docopt py-gensim py-jubatus-client py-langid | py-leveldb py-mecab py-mmh3 py-nltk py-nltk3 | py-pymc py-pymc3 py-sparqlwrapper py-sumy py- | word2vec rb-mecab rb19-mecab re2 rnnlm | seekanser sgd simstring sinsy slearp sofia-ml | sparsehash sptk ssrc stanford-ner stanford- | parser stanford-postagger syncha tinycdb | TinySVM unidic-mecab ux-trie vowpal_wabbit | wapiti word2vec yakmo yamcha zunda | -------------------------------------------------+------------------------- Comment (by humem): I am very sorry for the delayed response. Unfortunately it became harder for me to maintain the ports, and I regret to abandon the ownership of the ports. (hum at macports.org) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 10:42:47 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 09:42:47 -0000 Subject: [MacPorts] #48967: submission: port:qt5-kde In-Reply-To: <041.6050f0f0647a2426eb0e97ebbbe77cbd@macports.org> References: <041.6050f0f0647a2426eb0e97ebbbe77cbd@macports.org> Message-ID: <056.e5ce8081c920c074b0d8a4d1944b4ccf@macports.org> #48967: submission: port:qt5-kde -------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: submission | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5-kde | -------------------------+---------------------- Changes (by RJVB): * Attachment "qt5-kde.tar.2.bz2" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 14:20:53 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 13:20:53 -0000 Subject: [MacPorts] #47476: scons does not properly add header guards to generated config header In-Reply-To: <061.6c27ebcd37eca92d21ebd426ffd9e308@macports.org> References: <061.6c27ebcd37eca92d21ebd426ffd9e308@macports.org> Message-ID: <076.14bed5c6f17cd68b23f12efdf2e1578e@macports.org> #47476: scons does not properly add header guards to generated config header ------------------------------+-------------------------------- Reporter: Peter_Dyballa@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: scons | ------------------------------+-------------------------------- Comment (by ballapete): Replying to [comment:6 larryv]: > I’ve updated `scons` to 2.5.1. Is this still an issue? No. Because the new Scones came as a compiled image to me … -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 15:04:00 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 14:04:00 -0000 Subject: [MacPorts] #52993: GNOME girl 9.6.0 In-Reply-To: <045.04d8e8a96f5386b2efda1aea2d1aff35@macports.org> References: <045.04d8e8a96f5386b2efda1aea2d1aff35@macports.org> Message-ID: <060.40e03fecb61a1c091213a6b50516bb0d@macports.org> #52993: GNOME girl 9.6.0 -----------------------+----------------- Reporter: oleaamot | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: girl | -----------------------+----------------- Changes (by oleaamot): * Attachment "Portfile-9.6.0-unstable" added. GNOME Internet Radio Locator 9.6.0 Portfile -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 15:12:06 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 14:12:06 -0000 Subject: [MacPorts] #52993: GNOME girl 9.6.0 In-Reply-To: <045.04d8e8a96f5386b2efda1aea2d1aff35@macports.org> References: <045.04d8e8a96f5386b2efda1aea2d1aff35@macports.org> Message-ID: <060.6e04daf5451157247e7520c672dbcf09@macports.org> #52993: GNOME girl 9.6.0 -----------------------+----------------- Reporter: oleaamot | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: girl | -----------------------+----------------- Comment (by oleaamot): I am the upstream author (ole at src.gnome.org) of this unstable 9.6.0 release of the GNOME Internet Radio Locator. GNOME Internet Radio Locator plays Internet radio streams for 78 Internet Radio stations with gstreamer if you search for the station with the Search button and enter a city name in the input field. Several Issues on Mac OS X 10.11.6: It crashes on Mac OS X 10.11.6 if you press the "New" button in order to add new Internet Radio stations. It crashes on Mac OS X 10.11.6 with "Illegal instruction: 4" if you select the Internet radio station with the Stations selector. The 9.6.0 version works perfectly without these issues on Fedora Linux Core 24. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 15:27:18 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 14:27:18 -0000 Subject: [MacPorts] #52999: php-uuid: add php71-uuid subport Message-ID: <047.1baaedcebc20348ef1eda3ffb1c02491@macports.org> #52999: php-uuid: add php71-uuid subport -------------------------+---------------------- Reporter: ryandesign | Owner: pixilla Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: haspatch | Port: php-uuid -------------------------+---------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 15:27:27 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 14:27:27 -0000 Subject: [MacPorts] #52999: php-uuid: add php71-uuid subport In-Reply-To: <047.1baaedcebc20348ef1eda3ffb1c02491@macports.org> References: <047.1baaedcebc20348ef1eda3ffb1c02491@macports.org> Message-ID: <062.4d9b778fdcf6bc14d9be776533fb8662@macports.org> #52999: php-uuid: add php71-uuid subport --------------------------+---------------------- Reporter: ryandesign | Owner: pixilla Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: haspatch Port: php-uuid | --------------------------+---------------------- Changes (by ryandesign): * Attachment "php-uuid.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 17:08:22 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 16:08:22 -0000 Subject: [MacPorts] #53000: git @2.10.2: update to 2.11.0 Message-ID: <041.332d173c24dfbe6d79d1d3026415c129@macports.org> #53000: git @2.10.2: update to 2.11.0 --------------------+----------------- Reporter: l2dy | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: git --------------------+----------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 17:20:33 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 16:20:33 -0000 Subject: [MacPorts] #53000: git @2.10.2: update to 2.11.0 In-Reply-To: <041.332d173c24dfbe6d79d1d3026415c129@macports.org> References: <041.332d173c24dfbe6d79d1d3026415c129@macports.org> Message-ID: <056.b5665bb818967f647ad9ae10220ae6bf@macports.org> #53000: git @2.10.2: update to 2.11.0 ------------------------+-------------------- Reporter: l2dy | Owner: Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: duplicate | Keywords: Port: git | ------------------------+-------------------- Changes (by raimue): * status: new => closed * resolution: => duplicate Comment: Pull Request: https://github.com/macports/macports-ports/pull/79 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 18:12:31 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 17:12:31 -0000 Subject: [MacPorts] #52993: GNOME girl 9.6.0 In-Reply-To: <045.04d8e8a96f5386b2efda1aea2d1aff35@macports.org> References: <045.04d8e8a96f5386b2efda1aea2d1aff35@macports.org> Message-ID: <060.7224438425f31f5535f3bec46c242e07@macports.org> #52993: GNOME girl 9.6.0 -----------------------+----------------- Reporter: oleaamot | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: girl | -----------------------+----------------- Comment (by raimue): I tried to build the Portfile, but the attached Portfile.9.6.0.diff​ has a trailing '.' at the version number and checksums are wrong as well. For Portfile-9.6.0-unstable​, I don't know what the original revision is supposed to be, it does not apply to what is currently in git master. I am attaching what I used now. With this, I can reproduce the crash when selecting a station and its cause on OS X 10.12: {{{ $ otool -tV /opt/local/bin/girl | grep -C5 '^0*100012b8c' 0000000100012b79 movq %rax, %rdi 0000000100012b7c movq %r14, %rsi 0000000100012b7f callq 0x100013d0a ## symbol stub for: _g_object_get_data 0000000100012b84 movq %rax, %rdi 0000000100012b87 callq 0x100013e78 ## symbol stub for: _g_strdup 0000000100012b8c ud2 _on_new_station_changed: 0000000100012b8e pushq %rbp 0000000100012b8f movq %rsp, %rbp 0000000100012b92 pushq %r14 0000000100012b94 pushq %rbx }}} This is under the symbol `_on_stations_selector_changed` and `ud2` is the opcode specifically used to raise an illegal instruction exception. I cannot say why it ends up in your binary. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 18:12:48 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 17:12:48 -0000 Subject: [MacPorts] #52993: GNOME girl 9.6.0 In-Reply-To: <045.04d8e8a96f5386b2efda1aea2d1aff35@macports.org> References: <045.04d8e8a96f5386b2efda1aea2d1aff35@macports.org> Message-ID: <060.752ac55da2637f5e5107ad198e354611@macports.org> #52993: GNOME girl 9.6.0 -----------------------+----------------- Reporter: oleaamot | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: girl | -----------------------+----------------- Changes (by raimue): * Attachment "0001-girl-Update-to-version-9.6.0.patch" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 18:35:19 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 17:35:19 -0000 Subject: [MacPorts] #52575: Report Xcode version and other useful information in main.log In-Reply-To: <042.42a78d4434d5451da0f8a52a3c448eb7@macports.org> References: <042.42a78d4434d5451da0f8a52a3c448eb7@macports.org> Message-ID: <057.8093fa8280c373c892fffd47f515ac46@macports.org> #52575: Report Xcode version and other useful information in main.log --------------------------+-------------------------------- Reporter: mojca | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.4 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Changes (by mkae): * cc: mkae (added) Comment: Replying to [comment:3 mojca]: > It might be useful to log the MacPorts version as well. +1 from me ad well. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 19:41:21 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 18:41:21 -0000 Subject: [MacPorts] #52441: Add dnsviz port In-Reply-To: <044.de9c1770163eac8bdc4bc15a2b37c7a1@macports.org> References: <044.de9c1770163eac8bdc4bc15a2b37c7a1@macports.org> Message-ID: <059.f2d57929eb67c16a66be3384706e9041@macports.org> #52441: Add dnsviz port -------------------------+-------------------------------- Reporter: cdeccio | Owner: macports-tickets@… Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: dnsviz | -------------------------+-------------------------------- Changes (by mojca): * status: new => closed * version: 2.3.4 => * resolution: => fixed Comment: Closed: * https://github.com/macports/macports-ports/pull/76 * https://github.com/macports/macports- ports/commit/042ee98371befc19ce67fc9e5fe41b3d368377d5 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 19:43:02 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 18:43:02 -0000 Subject: [MacPorts] #52306: mozjs17 @17.0.0_4+universal: js17-config differs in i386 and x86_64 builds, cannot be merged In-Reply-To: <052.4f90720235627e6e89a2affd492ad992@macports.org> References: <052.4f90720235627e6e89a2affd492ad992@macports.org> Message-ID: <067.df86c4bc106f7fb5eac7e9bd2ce61444@macports.org> #52306: mozjs17 @17.0.0_4+universal: js17-config differs in i386 and x86_64 builds, cannot be merged ------------------------------+--------------------- Reporter: MichalMisiaszek | Owner: dbevans Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: mozjs17 | ------------------------------+--------------------- Comment (by juanrgar): {{{mozjs17 @17.0.0_4+universal}}} also builds fine in El Capitan with Xcode 8.1. Unfortunately, I do not have a Yosemite installation... Could you please attach the log file? i.e. /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_mozjs17/mozjs17/main.log Or even run the command with the -d switch? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 21:01:12 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 20:01:12 -0000 Subject: [MacPorts] #52306: mozjs17 @17.0.0_4+universal: js17-config differs in i386 and x86_64 builds, cannot be merged In-Reply-To: <052.4f90720235627e6e89a2affd492ad992@macports.org> References: <052.4f90720235627e6e89a2affd492ad992@macports.org> Message-ID: <067.084dd9648672738faf8f5ac800d8d241@macports.org> #52306: mozjs17 @17.0.0_4+universal: js17-config differs in i386 and x86_64 builds, cannot be merged ------------------------------+--------------------- Reporter: MichalMisiaszek | Owner: dbevans Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: mozjs17 | ------------------------------+--------------------- Changes (by MichalMisiaszek): * Attachment "mozjs17.log" added. log "sudo port -d -n upgrade --enforce-variants mozjs17 -universal" -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 22:54:27 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 21:54:27 -0000 Subject: [MacPorts] #52827: yarn @0.16.1 In-Reply-To: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> References: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> Message-ID: <061.cf90b9a901580645605179da3ee96845@macports.org> #52827: yarn @0.16.1 -------------------------+-------------------------------- Reporter: isomarcte | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: yarn | -------------------------+-------------------------------- Comment (by isomarcte): Replying to [comment:3 jambonrose]: > This is somewhat embarrassing: I created a Portfile for yarn, having somehow missed this issue when I started work on this yesterday. Sorry about that, David. I did not mean to step on anybody's toes. > > I've opened a PR for my Portfile on Github: https://github.com/macports /macports-ports/pull/48 > > The Portfile in the PR (PPR) and the Portfile in this issue (PI) are quite different. > > 1. PI downloads package from Github; PPR uses the yarn website > 2. PI installs into lib and links yarn.js directly; PPR installs in libexec and links to the yarn shell script that calls yarn.js > 3. PI does not patch the code; PPR does (to allow for sym-linking) > 4. PPR supports variants of Node, allows for installations of Node outside of Macports > > I suspect there may be some discussion about the decisions each of us has made, and the pros and cons here. Feedback appreciated. > > David: would you like me to add you as a maintainer to the Portfile in the PR? Hey jambonrose, Thanks for the comment. I am not worried about you stepping on my toes. I like many of the decisions you made, perhaps we can combine efforts. > 1. PI downloads package from Github; PPR uses the yarn website I have no strong opinion on this. I noticed that your version lacks a livecheck, which is very nice to have. We get it for free by using the github PortGroup. If you want to get `yarn` directly from their site, you might consider adding a livecheck. > 2. PI installs into lib and links yarn.js directly; PPR installs in libexec and links to the yarn shell script that calls yarn.js Well, to be more accurate, the version I created installs it into `lib/node_modules`. This is where it would get installed if you ran `npm -g install yarn` and where `npm` itself is installed. I certainly don't think that there is anything wrong with installing it into `libexec`, but the `lib/node_modules` seems to adhear to the "Principle of Least Astonishment" > 3. PI does not patch the code; PPR does (to allow for sym-linking) Great idea! I noticed on the PR that it was suggested you put the modification into a patch. I have gone ahead with this. > 4. PPR supports variants of Node, allows for installations of Node outside of Macports Derp. I had the wrong `depends_run` line my `PortFile`. I have updated it to, {{{ depends_run bin:node:nodejs7 }}} This way as along as they have a `node` binary in one of the standard bin folders, they won't be prompted to install `nodejs7`. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 22:54:59 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 21:54:59 -0000 Subject: [MacPorts] #52827: yarn @0.16.1 In-Reply-To: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> References: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> Message-ID: <061.3c1e63b132e21b707353d616ecce07d9@macports.org> #52827: yarn @0.16.1 -------------------------+-------------------------------- Reporter: isomarcte | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: yarn | -------------------------+-------------------------------- Changes (by isomarcte): * Attachment "Portfile" removed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 22:54:59 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 21:54:59 -0000 Subject: [MacPorts] #52827: yarn @0.16.1 In-Reply-To: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> References: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> Message-ID: <061.f51e9ed1d48624437fc97f403254851c@macports.org> #52827: yarn @0.16.1 -------------------------+-------------------------------- Reporter: isomarcte | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: yarn | -------------------------+-------------------------------- Changes (by isomarcte): * Attachment "Portfile" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 22:55:40 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 21:55:40 -0000 Subject: [MacPorts] #52827: yarn @0.16.1 In-Reply-To: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> References: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> Message-ID: <061.ac3bdf057782fd832e256225935131f8@macports.org> #52827: yarn @0.16.1 -------------------------+-------------------------------- Reporter: isomarcte | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: yarn | -------------------------+-------------------------------- Changes (by isomarcte): * Attachment "patch-symbolic-link-fix.diff" added. Patch to allow for using the yarn bash wrapper from a symbolic link (credit goes to jambonrose) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 00:13:22 2016 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2016 23:13:22 -0000 Subject: [MacPorts] #52490: [Port Abandoned] Ports maintained by hum In-Reply-To: <041.9d8ed880a58e228011e8b4ff5729ba02@macports.org> References: <041.9d8ed880a58e228011e8b4ff5729ba02@macports.org> Message-ID: <056.c41ea6a84cf9b072baf91839f4898788@macports.org> #52490: [Port Abandoned] Ports maintained by hum -------------------------------------------------+------------------------- Reporter: mf2k | Owner: humem Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: apache-solr3 apache-solr4 arowpp | bact bayon brown-cluster cabocha caffe cedar | chasen chasen-base chasen-ipadic chasen- | ipadic-sjis chasen-ipadic-utf8 chasen-naist- | jdic chasen-naist-jdic-sjis chasen-naist- | jdic-utf8 cicada classias cpi00 crfpp crfpp- | devel crfsuite cutter darts darts-clone | dualist eda emacs-app emacs-mac-app expgram | extractopinion gibbslda giza-pp google-glog | groonga hadoop hts_engine_API irstlm jdepp | jubatus jubatus-mpio jubatus-msgpack-rpc | jubatus_core julius juman juman6 kakarot KNBC | knp knp3 kytea lader lda-c lda-d liblbfgs | liblinear libsvm libzookeeper lmdb lucene- | gosen2 lucene-gosen4 mahout mallet marisa- | trie mecab mecab-base mecab-ipadic mecab- | ipadic-neologd mecab-ipadic-sjis mecab- | ipadic-utf8 mecab-java mecab-jumandic mecab- | jumandic-sjis mecab-jumandic-utf8 mecab- | naist-jdic mecab-naist-jdic-sjis mecab-naist- | jdic-utf8 mecab-sjis mecab-utf8 mgizapp | MMDAgent mosesdecoder msgpack msgpack1 | normalizeNumexp oll oniguruma5 opal-ml | open_jtalk openfst p5-mecab p5-termextract p5 | -text-csv_xs palmkit pecco pficommon pialign | plda portaudio py-breadability py-chainer py- | docopt py-gensim py-jubatus-client py-langid | py-leveldb py-mecab py-mmh3 py-nltk py-nltk3 | py-pymc py-pymc3 py-sparqlwrapper py-sumy py- | word2vec rb-mecab rb19-mecab re2 rnnlm | seekanser sgd simstring sinsy slearp sofia-ml | sparsehash sptk ssrc stanford-ner stanford- | parser stanford-postagger syncha tinycdb | TinySVM unidic-mecab ux-trie vowpal_wabbit | wapiti word2vec yakmo yamcha zunda | -------------------------------------------------+------------------------- Comment (by kurthindenburg): In [changeset:"9994f6046281d1a14659d4fc7f6b3d02d4ffe49e/macports-ports" 9994f604/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="9994f6046281d1a14659d4fc7f6b3d02d4ffe49e" multiple ports - remove hum maintainer remove outdated $Id when found see https://trac.macports.org/ticket/52490 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 01:46:42 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 00:46:42 -0000 Subject: [MacPorts] #52866: libedit: unable to enter non-ASCII characters In-Reply-To: <043.1070da57209272df90653023fa509525@macports.org> References: <043.1070da57209272df90653023fa509525@macports.org> Message-ID: <058.7654483fd048b6d28ce57685e28fde63@macports.org> #52866: libedit: unable to enter non-ASCII characters ------------------------------+--------------------------------- Reporter: raimue | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: libedit sqlite3 | ------------------------------+--------------------------------- Changes (by MarcusCalhoun-Lopez): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"760795dd90b00862e47b4bf40a88da99e36688bd/macports-ports" 760795dd/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="760795dd90b00862e47b4bf40a88da99e36688bd" libedit: allow typing non-ASCII characters fixes https://trac.macports.org/ticket/52866 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 03:04:29 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 02:04:29 -0000 Subject: [MacPorts] #52490: [Port Abandoned] Ports maintained by hum In-Reply-To: <041.9d8ed880a58e228011e8b4ff5729ba02@macports.org> References: <041.9d8ed880a58e228011e8b4ff5729ba02@macports.org> Message-ID: <056.00ba1772ea98d83d71385eedbc4eb868@macports.org> #52490: [Port Abandoned] Ports maintained by hum -------------------------------------------------+------------------------- Reporter: mf2k | Owner: humem Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: apache-solr3 apache-solr4 arowpp | bact bayon brown-cluster cabocha caffe cedar | chasen chasen-base chasen-ipadic chasen- | ipadic-sjis chasen-ipadic-utf8 chasen-naist- | jdic chasen-naist-jdic-sjis chasen-naist- | jdic-utf8 cicada classias cpi00 crfpp crfpp- | devel crfsuite cutter darts darts-clone | dualist eda emacs-app emacs-mac-app expgram | extractopinion gibbslda giza-pp google-glog | groonga hadoop hts_engine_API irstlm jdepp | jubatus jubatus-mpio jubatus-msgpack-rpc | jubatus_core julius juman juman6 kakarot KNBC | knp knp3 kytea lader lda-c lda-d liblbfgs | liblinear libsvm libzookeeper lmdb lucene- | gosen2 lucene-gosen4 mahout mallet marisa- | trie mecab mecab-base mecab-ipadic mecab- | ipadic-neologd mecab-ipadic-sjis mecab- | ipadic-utf8 mecab-java mecab-jumandic mecab- | jumandic-sjis mecab-jumandic-utf8 mecab- | naist-jdic mecab-naist-jdic-sjis mecab-naist- | jdic-utf8 mecab-sjis mecab-utf8 mgizapp | MMDAgent mosesdecoder msgpack msgpack1 | normalizeNumexp oll oniguruma5 opal-ml | open_jtalk openfst p5-mecab p5-termextract p5 | -text-csv_xs palmkit pecco pficommon pialign | plda portaudio py-breadability py-chainer py- | docopt py-gensim py-jubatus-client py-langid | py-leveldb py-mecab py-mmh3 py-nltk py-nltk3 | py-pymc py-pymc3 py-sparqlwrapper py-sumy py- | word2vec rb-mecab rb19-mecab re2 rnnlm | seekanser sgd simstring sinsy slearp sofia-ml | sparsehash sptk ssrc stanford-ner stanford- | parser stanford-postagger syncha tinycdb | TinySVM unidic-mecab ux-trie vowpal_wabbit | wapiti word2vec yakmo yamcha zunda | -------------------------------------------------+------------------------- Comment (by kurthindenburg): In [changeset:"8be77b2cabebbff08e95713b90c0bcbdcc99cf6b/macports-ports" 8be77b2c/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="8be77b2cabebbff08e95713b90c0bcbdcc99cf6b" multiple ports - remove hum maintainer remove outdated $Id when found see https://trac.macports.org/ticket/52490 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 03:45:28 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 02:45:28 -0000 Subject: [MacPorts] #52490: [Port Abandoned] Ports maintained by hum In-Reply-To: <041.9d8ed880a58e228011e8b4ff5729ba02@macports.org> References: <041.9d8ed880a58e228011e8b4ff5729ba02@macports.org> Message-ID: <056.fc4c7a738d0f5b752724b74fc4e9063f@macports.org> #52490: [Port Abandoned] Ports maintained by hum -------------------------------------------------+------------------------- Reporter: mf2k | Owner: humem Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: apache-solr3 apache-solr4 arowpp | bact bayon brown-cluster cabocha caffe cedar | chasen chasen-base chasen-ipadic chasen- | ipadic-sjis chasen-ipadic-utf8 chasen-naist- | jdic chasen-naist-jdic-sjis chasen-naist- | jdic-utf8 cicada classias cpi00 crfpp crfpp- | devel crfsuite cutter darts darts-clone | dualist eda emacs-app emacs-mac-app expgram | extractopinion gibbslda giza-pp google-glog | groonga hadoop hts_engine_API irstlm jdepp | jubatus jubatus-mpio jubatus-msgpack-rpc | jubatus_core julius juman juman6 kakarot KNBC | knp knp3 kytea lader lda-c lda-d liblbfgs | liblinear libsvm libzookeeper lmdb lucene- | gosen2 lucene-gosen4 mahout mallet marisa- | trie mecab mecab-base mecab-ipadic mecab- | ipadic-neologd mecab-ipadic-sjis mecab- | ipadic-utf8 mecab-java mecab-jumandic mecab- | jumandic-sjis mecab-jumandic-utf8 mecab- | naist-jdic mecab-naist-jdic-sjis mecab-naist- | jdic-utf8 mecab-sjis mecab-utf8 mgizapp | MMDAgent mosesdecoder msgpack msgpack1 | normalizeNumexp oll oniguruma5 opal-ml | open_jtalk openfst p5-mecab p5-termextract p5 | -text-csv_xs palmkit pecco pficommon pialign | plda portaudio py-breadability py-chainer py- | docopt py-gensim py-jubatus-client py-langid | py-leveldb py-mecab py-mmh3 py-nltk py-nltk3 | py-pymc py-pymc3 py-sparqlwrapper py-sumy py- | word2vec rb-mecab rb19-mecab re2 rnnlm | seekanser sgd simstring sinsy slearp sofia-ml | sparsehash sptk ssrc stanford-ner stanford- | parser stanford-postagger syncha tinycdb | TinySVM unidic-mecab ux-trie vowpal_wabbit | wapiti word2vec yakmo yamcha zunda | -------------------------------------------------+------------------------- Comment (by kurthindenburg): In [changeset:"9994f6046281d1a14659d4fc7f6b3d02d4ffe49e/macports-ports" 9994f604/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="9994f6046281d1a14659d4fc7f6b3d02d4ffe49e" multiple ports - remove hum maintainer remove outdated $Id when found see https://trac.macports.org/ticket/52490 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 03:46:14 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 02:46:14 -0000 Subject: [MacPorts] #52866: libedit: unable to enter non-ASCII characters In-Reply-To: <043.1070da57209272df90653023fa509525@macports.org> References: <043.1070da57209272df90653023fa509525@macports.org> Message-ID: <058.993de0466799d1b6af9c906fcf691ce2@macports.org> #52866: libedit: unable to enter non-ASCII characters ------------------------------+--------------------------------- Reporter: raimue | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: libedit sqlite3 | ------------------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): In [changeset:"760795dd90b00862e47b4bf40a88da99e36688bd/macports-ports" 760795dd/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="760795dd90b00862e47b4bf40a88da99e36688bd" libedit: allow typing non-ASCII characters fixes https://trac.macports.org/ticket/52866 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 04:24:07 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 03:24:07 -0000 Subject: [MacPorts] #52866: libedit: unable to enter non-ASCII characters In-Reply-To: <043.1070da57209272df90653023fa509525@macports.org> References: <043.1070da57209272df90653023fa509525@macports.org> Message-ID: <058.655e3f6ce0f8bbf70b1fbf790e8acbaa@macports.org> #52866: libedit: unable to enter non-ASCII characters ------------------------------+--------------------------------- Reporter: raimue | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: libedit sqlite3 | ------------------------------+--------------------------------- Comment (by Schamschula): In [changeset:"b510ccebf141f1f4e0e9275a2cab0baa28f94628/macports-ports" b510cce/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="b510ccebf141f1f4e0e9275a2cab0baa28f94628" sqlite3: revert to editline See: https://trac.macports.org/ticket/52866 See: https://github.com/macports/macports- ports/commit/760795dd90b00862e47b4bf40a88da99e36688bd }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 04:45:49 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 03:45:49 -0000 Subject: [MacPorts] #52866: libedit: unable to enter non-ASCII characters In-Reply-To: <043.1070da57209272df90653023fa509525@macports.org> References: <043.1070da57209272df90653023fa509525@macports.org> Message-ID: <058.f8088b448fff8df54b1c5b262b6f57af@macports.org> #52866: libedit: unable to enter non-ASCII characters ------------------------------+--------------------------------- Reporter: raimue | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: libedit sqlite3 | ------------------------------+--------------------------------- Comment (by larryv): In [changeset:"ae7c13cb2d71a9e9ef2fbd331a1194c89dc94dbf/macports-ports" ae7c13cb/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="ae7c13cb2d71a9e9ef2fbd331a1194c89dc94dbf" sqlite3: Remove readline dependency Completes b510ccebf141f1f4e0e9275a2cab0baa28f94628. See https://trac.macports.org/ticket/52866. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 05:37:40 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 04:37:40 -0000 Subject: [MacPorts] #53001: cyrus-imapd @2.4.18_2: update to 2.5.10 and fix livecheck Message-ID: <041.71ad0abcac3041ffe23f1009cce5ae96@macports.org> #53001: cyrus-imapd @2.4.18_2: update to 2.5.10 and fix livecheck --------------------+------------------------- Reporter: l2dy | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: cyrus-imapd --------------------+------------------------- {{{ $ port livecheck cyrus-imapd Error: cannot check if cyrus-imapd was updated (regex didn't match) }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 05:49:01 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 04:49:01 -0000 Subject: [MacPorts] #53001: cyrus-imapd @2.4.18_2: update to 2.5.10 and fix livecheck In-Reply-To: <041.71ad0abcac3041ffe23f1009cce5ae96@macports.org> References: <041.71ad0abcac3041ffe23f1009cce5ae96@macports.org> Message-ID: <056.64ba722e1e15df81dff826035f10fee7@macports.org> #53001: cyrus-imapd @2.4.18_2: update to 2.5.10 and fix livecheck --------------------------+----------------- Reporter: l2dy | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cyrus-imapd | --------------------------+----------------- Comment (by larryv): In [changeset:"37fbbb230f52370f4f2ae7faf9472a649bdd8efb/macports-ports" 37fbbb23/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="37fbbb230f52370f4f2ae7faf9472a649bdd8efb" cyrus-imapd: Fix livecheck See: https://trac.macports.org/ticket/53001 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 05:58:19 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 04:58:19 -0000 Subject: [MacPorts] #53002: xorg-libsm @1.2.1: update to 1.2.2 Message-ID: <041.3ff81018c414f4fa934b0e672337d0a0@macports.org> #53002: xorg-libsm @1.2.1: update to 1.2.2 --------------------+------------------------ Reporter: l2dy | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: xorg-libsm --------------------+------------------------ -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 09:03:15 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 08:03:15 -0000 Subject: [MacPorts] #53003: speex @1.2rc1: update to 1.2rc2 Message-ID: <041.e65bf1ae5d8340cb71e757ed3780a42a@macports.org> #53003: speex @1.2rc1: update to 1.2rc2 --------------------+------------------- Reporter: l2dy | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: speex --------------------+------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 09:19:32 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 08:19:32 -0000 Subject: [MacPorts] #53004: go @1.7.3: update to 1.7.4 Message-ID: <041.c53263009725c99ff11ca3dfc2af6049@macports.org> #53004: go @1.7.3: update to 1.7.4 --------------------+----------------- Reporter: l2dy | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: go --------------------+----------------- go1.7.4 (released 2016/12/01) includes two security fixes. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 13:46:06 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 13:46:06 -0000 Subject: [MacPorts] #53003: speex @1.2rc1: update to 1.2rc2 In-Reply-To: <041.e65bf1ae5d8340cb71e757ed3780a42a@macports.org> References: <041.e65bf1ae5d8340cb71e757ed3780a42a@macports.org> Message-ID: <056.59ae8cf44111e3c933b9ca806966eab5@macports.org> #53003: speex @1.2rc1: update to 1.2rc2 ---------------------+----------------- Reporter: l2dy | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: speex | ---------------------+----------------- Comment (by l2dy): Fixed in fabb0ea/macports-ports. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 14:36:06 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 14:36:06 -0000 Subject: [MacPorts] #53005: coreutils @8.25: update to 8.26 Message-ID: <041.7260f4c736b0e373376e8f50949d41aa@macports.org> #53005: coreutils @8.25: update to 8.26 --------------------+----------------------- Reporter: l2dy | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: coreutils --------------------+----------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 14:36:17 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 14:36:17 -0000 Subject: [MacPorts] #52730: Upgrade of apache geode port In-Reply-To: <045.a1662548220541bfc88cef6eeb20d073@macports.org> References: <045.a1662548220541bfc88cef6eeb20d073@macports.org> Message-ID: <060.9c4cdbc4ac38af8014bb7429169b137f@macports.org> #52730: Upgrade of apache geode port --------------------------+--------------------------------- Reporter: kjduling | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: geode-devel | --------------------------+--------------------------------- Comment (by raimue): Reproducing my comment I made on [https://github.com/macports/macports- ports/pull/77 the related pull request]: I personally have no confidence in reviewing any Java related port. For example, I don't know if it is wise to use compiled Java class files and whether these will work on all available Java runtimes on the various versions of OS X. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 15:09:49 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 15:09:49 -0000 Subject: [MacPorts] #52613: Guile-2.0.13 fails to build on Sierra In-Reply-To: <047.ac972e8ff213b95746deb5f6352988fa@macports.org> References: <047.ac972e8ff213b95746deb5f6352988fa@macports.org> Message-ID: <062.0576e0fd34265943611f03f81f6b5e5e@macports.org> #52613: Guile-2.0.13 fails to build on Sierra -------------------------+-------------------------------- Reporter: mouse07410 | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: sierra Port: guile | -------------------------+-------------------------------- Comment (by favadi): I confirm that the problem still happens with macports 2.3.5 on macOS Sierra. Should we merged @mwette's patches? Or those patches should be recreated as a Github PR? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 15:36:48 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 15:36:48 -0000 Subject: [MacPorts] #53006: buildbot @0.8.12_7: update to 0.9.1 Message-ID: <041.a108655036a8d4af9f1e443709ba483d@macports.org> #53006: buildbot @0.8.12_7: update to 0.9.1 --------------------+---------------------- Reporter: l2dy | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: buildbot --------------------+---------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 15:40:38 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 15:40:38 -0000 Subject: [MacPorts] #53006: buildbot @0.8.12_7: update to 0.9.1 In-Reply-To: <041.a108655036a8d4af9f1e443709ba483d@macports.org> References: <041.a108655036a8d4af9f1e443709ba483d@macports.org> Message-ID: <056.a95842fa351ce2babc8b21818629e49c@macports.org> #53006: buildbot @0.8.12_7: update to 0.9.1 -----------------------+----------------- Reporter: l2dy | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: buildbot | -----------------------+----------------- Comment (by ctreleaven): Note that buildbot 0.9 is very different from 0.8. Probably want to retain a buildbot8 port. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 15:41:15 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 15:41:15 -0000 Subject: [MacPorts] #53006: buildbot @0.8.12_7: update to 0.9.1 In-Reply-To: <041.a108655036a8d4af9f1e443709ba483d@macports.org> References: <041.a108655036a8d4af9f1e443709ba483d@macports.org> Message-ID: <056.f103e7d0f1068dd5aa5f85e3809dd442@macports.org> #53006: buildbot @0.8.12_7: update to 0.9.1 -----------------------+------------------------ Reporter: l2dy | Owner: ryandesign Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: buildbot | -----------------------+------------------------ Changes (by raimue): * cc: ryandesign (removed) * owner: => ryandesign * status: new => assigned Comment: As our own infrastructure will continue to run on buildbot 0.8.x for the time being, it might make sense to update buildbot to 0.9.x and add a new ''buildbot08'' for 0.8.x (or ''buildbot-eight'' following their [http://trac.buildbot.net/wiki/Eight internal branch naming]). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 15:47:27 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 15:47:27 -0000 Subject: [MacPorts] #53007: neomutt @20161014 add slang variant Message-ID: <047.2da557977b5327e096a5410984aa70f9@macports.org> #53007: neomutt @20161014 add slang variant -------------------------+--------------------- Reporter: slaptijack | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: haspatch | Port: neomutt -------------------------+--------------------- At one time, ncurses broke certain color support (solarized, for example). Add slang variant to replace ncurses with slang. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 15:47:48 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 15:47:48 -0000 Subject: [MacPorts] #53007: neomutt @20161014 add slang variant In-Reply-To: <047.2da557977b5327e096a5410984aa70f9@macports.org> References: <047.2da557977b5327e096a5410984aa70f9@macports.org> Message-ID: <062.1fa9724f66d102ab5d7d76d8121fbf68@macports.org> #53007: neomutt @20161014 add slang variant --------------------------+---------------------- Reporter: slaptijack | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: haspatch Port: neomutt | --------------------------+---------------------- Changes (by slaptijack): * Attachment "Portfile-neomutt.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 15:54:10 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 15:54:10 -0000 Subject: [MacPorts] #53006: buildbot @0.8.12_7: update to 0.9.1 In-Reply-To: <041.a108655036a8d4af9f1e443709ba483d@macports.org> References: <041.a108655036a8d4af9f1e443709ba483d@macports.org> Message-ID: <056.54d1e6f11d92133b846016ed3cb49867@macports.org> #53006: buildbot @0.8.12_7: update to 0.9.1 -----------------------+------------------------ Reporter: l2dy | Owner: ryandesign Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: buildbot | -----------------------+------------------------ Comment (by ryandesign): Absolutely, because MacPorts infrastructure is using the buildbot 0.8 ports and has no desire to upgrade to 0.9, we need to keep buildbot 0.8 ports in MacPorts. We can also have ports for buildbot 0.9. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 16:09:37 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 16:09:37 -0000 Subject: [MacPorts] #53008: FileZilla @3.14.1_1: update to 3.22.2.2 Message-ID: <041.1bb04e6c1fb79a1e2ee3a682132ffb4f@macports.org> #53008: FileZilla @3.14.1_1: update to 3.22.2.2 --------------------+----------------------- Reporter: l2dy | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: FileZilla --------------------+----------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 16:24:41 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 16:24:41 -0000 Subject: [MacPorts] #53005: coreutils @8.25: update to 8.26 In-Reply-To: <041.7260f4c736b0e373376e8f50949d41aa@macports.org> References: <041.7260f4c736b0e373376e8f50949d41aa@macports.org> Message-ID: <056.57e1a062f03b96dbe104b4f66392f4b9@macports.org> #53005: coreutils @8.25: update to 8.26 ------------------------+---------------------- Reporter: l2dy | Owner: larryv Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: coreutils | ------------------------+---------------------- Changes (by larryv): * owner: => larryv * status: new => accepted -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 16:25:47 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 16:25:47 -0000 Subject: [MacPorts] #53008: FileZilla @3.14.1_1: update to 3.22.2.2 In-Reply-To: <041.1bb04e6c1fb79a1e2ee3a682132ffb4f@macports.org> References: <041.1bb04e6c1fb79a1e2ee3a682132ffb4f@macports.org> Message-ID: <056.f58fe877c9efcfd477eb2f2a5cfad430@macports.org> #53008: FileZilla @3.14.1_1: update to 3.22.2.2 ------------------------+----------------------- Reporter: l2dy | Owner: rudloff@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: FileZilla | ------------------------+----------------------- Changes (by larryv): * cc: rudloff@… (removed) * status: new => assigned * owner: => rudloff@… -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 16:27:48 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 16:27:48 -0000 Subject: [MacPorts] #53009: autogen @5.18.4_1: update to 5.18.12 and update homepage Message-ID: <041.c901c6950e686cb5809ca85b9ed7b7a8@macports.org> #53009: autogen @5.18.4_1: update to 5.18.12 and update homepage --------------------+--------------------- Reporter: l2dy | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: autogen --------------------+--------------------- https://www.gnu.org/software/autogen/ has prettier docs and newest download link. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 16:57:03 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 16:57:03 -0000 Subject: [MacPorts] #53003: speex @1.2rc1: update to 1.2rc2 In-Reply-To: <041.e65bf1ae5d8340cb71e757ed3780a42a@macports.org> References: <041.e65bf1ae5d8340cb71e757ed3780a42a@macports.org> Message-ID: <056.223d51edd06efec4bc387486dc0b5c7b@macports.org> #53003: speex @1.2rc1: update to 1.2rc2 ---------------------+-------------------- Reporter: l2dy | Owner: Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: speex | ---------------------+-------------------- Changes (by larryv): * status: new => closed * resolution: => fixed Comment: https://github.com/macports/macports-ports/pull/84 https://github.com/macports/macports- ports/commit/fabb0eaedf110bdcd03d936d417b91a4dfe38fe7 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 17:55:02 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 17:55:02 -0000 Subject: [MacPorts] #52730: Upgrade of apache geode port In-Reply-To: <045.a1662548220541bfc88cef6eeb20d073@macports.org> References: <045.a1662548220541bfc88cef6eeb20d073@macports.org> Message-ID: <060.3e558175d1a9612a6afb6eae1c822edc@macports.org> #52730: Upgrade of apache geode port --------------------------+--------------------------------- Reporter: kjduling | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: geode-devel | --------------------------+--------------------------------- Comment (by kjduling): I recognize the concern and had the same reaction when I did the original port for Apache Geode M2. So, I looked at what other maintainers had done. Some Java ports install binaries while others install source and build locally. Maven and gradle are two examples of Apache apps in Java that are under MacPorts as binary installs. As the Homebrew maintainer for Geode chose to do a binary install, I went that route to maintain consistency. Geode definitely has some requirements, as do the other Java binary ports. Geode needs Java 1.8. The version of OSX is (should be) irrelevant. If you would rather see the port download sources and compile, the Portfile can be rewritten to do this instead. But due to the inconsistency of ports in the database, I feel that MacPorts should come up with a policy defining when a binary port is acceptable, and when it is not. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 18:17:40 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 18:17:40 -0000 Subject: [MacPorts] #53009: autogen @5.18.4_1: update to 5.18.12 and update homepage In-Reply-To: <041.c901c6950e686cb5809ca85b9ed7b7a8@macports.org> References: <041.c901c6950e686cb5809ca85b9ed7b7a8@macports.org> Message-ID: <056.2dce07b8a6e2ba7d8095d640e0fae1ad@macports.org> #53009: autogen @5.18.4_1: update to 5.18.12 and update homepage ----------------------+------------------------ Reporter: l2dy | Owner: ryandesign Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: autogen | ----------------------+------------------------ Changes (by ryandesign): * owner: => ryandesign * status: new => accepted * type: defect => update -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 18:28:25 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 18:28:25 -0000 Subject: [MacPorts] #53009: autogen @5.18.4_1: update to 5.18.12 and update homepage In-Reply-To: <041.c901c6950e686cb5809ca85b9ed7b7a8@macports.org> References: <041.c901c6950e686cb5809ca85b9ed7b7a8@macports.org> Message-ID: <056.2abc611c479c8f96922f812ca392d669@macports.org> #53009: autogen @5.18.4_1: update to 5.18.12 and update homepage ----------------------+------------------------ Reporter: l2dy | Owner: ryandesign Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: autogen | ----------------------+------------------------ Changes (by ryandesign): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"35b77a1a48cf33a7e811fcc10c9540dec7d6a1c0/macports-ports" 35b77a1a/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="35b77a1a48cf33a7e811fcc10c9540dec7d6a1c0" autogen: Update to 5.18.12 Also update homepage and disable universal variant. Closes: https://trac.macports.org/ticket/53009 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 18:29:27 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 18:29:27 -0000 Subject: [MacPorts] #53004: go @1.7.3: update to 1.7.4 In-Reply-To: <041.c53263009725c99ff11ca3dfc2af6049@macports.org> References: <041.c53263009725c99ff11ca3dfc2af6049@macports.org> Message-ID: <056.320af4b3210a738fc7f2093f08e7ecac@macports.org> #53004: go @1.7.3: update to 1.7.4 ---------------------+---------------------- Reporter: l2dy | Owner: ci42 Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: go | ---------------------+---------------------- Changes (by ryandesign): * owner: => ci42 * cc: ci42 (removed) * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 18:30:05 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 18:30:05 -0000 Subject: [MacPorts] #53002: xorg-libsm @1.2.1: update to 1.2.2 In-Reply-To: <041.3ff81018c414f4fa934b0e672337d0a0@macports.org> References: <041.3ff81018c414f4fa934b0e672337d0a0@macports.org> Message-ID: <056.752649d890968fb3537a18b91f2f28f0@macports.org> #53002: xorg-libsm @1.2.1: update to 1.2.2 -------------------------+----------------------- Reporter: l2dy | Owner: mvfranz@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: xorg-libsm | -------------------------+----------------------- Changes (by ryandesign): * cc: mvfranz@… (removed) * owner: => mvfranz@… * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 19:55:33 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 19:55:33 -0000 Subject: [MacPorts] #52827: yarn @0.16.1 In-Reply-To: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> References: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> Message-ID: <061.03d3fab922367c6440080fd805dd0685@macports.org> #52827: yarn @0.16.1 -------------------------+-------------------------------- Reporter: isomarcte | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: yarn | -------------------------+-------------------------------- Changes (by isomarcte): * Attachment "Portfile.2" added. Update to 0.18.0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 19:55:55 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 19:55:55 -0000 Subject: [MacPorts] #52827: yarn @0.16.1 In-Reply-To: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> References: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> Message-ID: <061.f51e9ed1d48624437fc97f403254851c@macports.org> #52827: yarn @0.16.1 -------------------------+-------------------------------- Reporter: isomarcte | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: yarn | -------------------------+-------------------------------- Changes (by isomarcte): * Attachment "Portfile" removed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 19:55:55 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 19:55:55 -0000 Subject: [MacPorts] #52827: yarn @0.16.1 In-Reply-To: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> References: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> Message-ID: <061.aff692fb304deb0d5a011f8b11e57cc4@macports.org> #52827: yarn @0.16.1 -------------------------+-------------------------------- Reporter: isomarcte | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: yarn | -------------------------+-------------------------------- Changes (by isomarcte): * Attachment "Portfile" added. Update to 0.18.0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 21:38:24 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 21:38:24 -0000 Subject: [MacPorts] #53007: neomutt @20161014 add slang variant In-Reply-To: <047.2da557977b5327e096a5410984aa70f9@macports.org> References: <047.2da557977b5327e096a5410984aa70f9@macports.org> Message-ID: <062.e52f1e410c3f8da772716dfb5f78cbd7@macports.org> #53007: neomutt @20161014 add slang variant --------------------------+---------------------- Reporter: slaptijack | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: haspatch Port: neomutt | --------------------------+---------------------- Comment (by lbschenkel): Thanks for the patch. I have incorporated it into the following GitHub PR: https://github.com/macports/macports-ports/pull/86 I took the opportunity and updated the port as well. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 22:21:29 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 22:21:29 -0000 Subject: [MacPorts] #52255: cannot install octave-optiminterp In-Reply-To: <053.15cb4bb18fd14ed94a4d07d7354244dd@macports.org> References: <053.15cb4bb18fd14ed94a4d07d7354244dd@macports.org> Message-ID: <068.0fa53e6a429a68e748023f3fe337753b@macports.org> #52255: cannot install octave-optiminterp ---------------------------------+-------------------------------- Reporter: MacPorts@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: octave-optiminterp | ---------------------------------+-------------------------------- Comment (by MarcusCalhoun-Lopez): {{{ optiminterp_wrapper.F90:20:5: use optimal_interpolation 1 Fatal Error: Can't open module file 'optimal_interpolation.mod' for reading at (1): No such file or directory }}} seems to be caused by by Octave attempting to build the package in parallel.[[BR]] {{{optimal_interpolation.mod}}} is required before it is generated. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 22:26:08 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 22:26:08 -0000 Subject: [MacPorts] #51306: octave-control: configure failure In-Reply-To: <054.5d725e0a4e7fae8580915bcca9fd9c46@macports.org> References: <054.5d725e0a4e7fae8580915bcca9fd9c46@macports.org> Message-ID: <069.9c986f661d5be6d3739f024248159cab@macports.org> #51306: octave-control: configure failure -----------------------------+------------------------- Reporter: gps@… | Owner: Schamschula Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: invalid | Keywords: Port: octave-control | -----------------------------+------------------------- Changes (by MarcusCalhoun-Lopez): * status: new => closed * resolution: => invalid Comment: Close at the request of original reporter. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 22:28:51 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 22:28:51 -0000 Subject: [MacPorts] #51670: octave-odepkg build fails with release of Octave 4 on macports In-Reply-To: <064.0e5037ccff40b5d56841ba50e3641908@macports.org> References: <064.0e5037ccff40b5d56841ba50e3641908@macports.org> Message-ID: <079.5d1e85934a8296474dc276db7125da91@macports.org> #51670: octave-odepkg build fails with release of Octave 4 on macports ----------------------------------+-------------------------------- Reporter: hartman.jonathan2@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: octave-odepkg | ----------------------------------+-------------------------------- Comment (by MarcusCalhoun-Lopez): Using the development version octave-odepkg worked for me. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 22:38:46 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 22:38:46 -0000 Subject: [MacPorts] #51670: octave-odepkg build fails with release of Octave 4 on macports In-Reply-To: <064.0e5037ccff40b5d56841ba50e3641908@macports.org> References: <064.0e5037ccff40b5d56841ba50e3641908@macports.org> Message-ID: <079.77592457f23fabc50c9bd92c450dbec3@macports.org> #51670: octave-odepkg build fails with release of Octave 4 on macports ----------------------------------+-------------------------------- Reporter: hartman.jonathan2@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: octave-odepkg | ----------------------------------+-------------------------------- Changes (by MarcusCalhoun-Lopez): * status: new => closed * resolution: => fixed Comment: In [changeset:"5c63c9706d260f6a6557b110bb7608f0d92287bf/macports-ports" 5c63c970/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="5c63c9706d260f6a6557b110bb7608f0d92287bf" octave and packages: update version 4.0.3 -> 4.2.0 upgrading octave necessitated rebuilding every octave package, so take this opportunity to fix some longstanding issues. Fixes https://trac.macports.org/ticket/52917 Fixes https://trac.macports.org/ticket/50261 Fixes https://trac.macports.org/ticket/50262 Fixes https://trac.macports.org/ticket/52255 Fixes https://trac.macports.org/ticket/51670 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 22:38:46 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 22:38:46 -0000 Subject: [MacPorts] #52255: cannot install octave-optiminterp In-Reply-To: <053.15cb4bb18fd14ed94a4d07d7354244dd@macports.org> References: <053.15cb4bb18fd14ed94a4d07d7354244dd@macports.org> Message-ID: <068.9d799ebba5dc36e9a673321a8941206a@macports.org> #52255: cannot install octave-optiminterp ---------------------------------+-------------------------------- Reporter: MacPorts@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: octave-optiminterp | ---------------------------------+-------------------------------- Changes (by MarcusCalhoun-Lopez): * status: new => closed * resolution: => fixed Comment: In [changeset:"5c63c9706d260f6a6557b110bb7608f0d92287bf/macports-ports" 5c63c970/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="5c63c9706d260f6a6557b110bb7608f0d92287bf" octave and packages: update version 4.0.3 -> 4.2.0 upgrading octave necessitated rebuilding every octave package, so take this opportunity to fix some longstanding issues. Fixes https://trac.macports.org/ticket/52917 Fixes https://trac.macports.org/ticket/50261 Fixes https://trac.macports.org/ticket/50262 Fixes https://trac.macports.org/ticket/52255 Fixes https://trac.macports.org/ticket/51670 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 22:38:46 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 22:38:46 -0000 Subject: [MacPorts] #52917: octave @4.0.3_1: Please update to new stable release 4.2.0 In-Reply-To: <043.a62a7c3cd9fa1227f8793fb588b46599@macports.org> References: <043.a62a7c3cd9fa1227f8793fb588b46599@macports.org> Message-ID: <058.a868c114c14f82bd8cfee00bad19a0c3@macports.org> #52917: octave @4.0.3_1: Please update to new stable release 4.2.0 ---------------------+--------------------------------- Reporter: maehne | Owner: MarcusCalhoun-Lopez Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: octave | ---------------------+--------------------------------- Changes (by MarcusCalhoun-Lopez): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"5c63c9706d260f6a6557b110bb7608f0d92287bf/macports-ports" 5c63c970/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="5c63c9706d260f6a6557b110bb7608f0d92287bf" octave and packages: update version 4.0.3 -> 4.2.0 upgrading octave necessitated rebuilding every octave package, so take this opportunity to fix some longstanding issues. Fixes https://trac.macports.org/ticket/52917 Fixes https://trac.macports.org/ticket/50261 Fixes https://trac.macports.org/ticket/50262 Fixes https://trac.macports.org/ticket/52255 Fixes https://trac.macports.org/ticket/51670 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 22:38:46 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 22:38:46 -0000 Subject: [MacPorts] #50262: octave port group: Remove orphaned paths In-Reply-To: <048.fa420dc60880f842fc9e8e0754991fb4@macports.org> References: <048.fa420dc60880f842fc9e8e0754991fb4@macports.org> Message-ID: <063.b07901931d5d5ee44ce652e0329ebc2a@macports.org> #50262: octave port group: Remove orphaned paths --------------------------+--------------------------------- Reporter: Schamschula | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: octave | --------------------------+--------------------------------- Changes (by MarcusCalhoun-Lopez): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"5c63c9706d260f6a6557b110bb7608f0d92287bf/macports-ports" 5c63c970/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="5c63c9706d260f6a6557b110bb7608f0d92287bf" octave and packages: update version 4.0.3 -> 4.2.0 upgrading octave necessitated rebuilding every octave package, so take this opportunity to fix some longstanding issues. Fixes https://trac.macports.org/ticket/52917 Fixes https://trac.macports.org/ticket/50261 Fixes https://trac.macports.org/ticket/50262 Fixes https://trac.macports.org/ticket/52255 Fixes https://trac.macports.org/ticket/51670 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 22:38:46 2016 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2016 22:38:46 -0000 Subject: [MacPorts] #50261: octave port group: Use cli for installs In-Reply-To: <048.cbf24badc8557ce80e514955687ed64e@macports.org> References: <048.cbf24badc8557ce80e514955687ed64e@macports.org> Message-ID: <063.486e0a61dcae8048f5f31591d855a834@macports.org> #50261: octave port group: Use cli for installs --------------------------+--------------------------------- Reporter: Schamschula | Owner: MarcusCalhoun-Lopez Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: octave | --------------------------+--------------------------------- Changes (by MarcusCalhoun-Lopez): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"5c63c9706d260f6a6557b110bb7608f0d92287bf/macports-ports" 5c63c970/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="5c63c9706d260f6a6557b110bb7608f0d92287bf" octave and packages: update version 4.0.3 -> 4.2.0 upgrading octave necessitated rebuilding every octave package, so take this opportunity to fix some longstanding issues. Fixes https://trac.macports.org/ticket/52917 Fixes https://trac.macports.org/ticket/50261 Fixes https://trac.macports.org/ticket/50262 Fixes https://trac.macports.org/ticket/52255 Fixes https://trac.macports.org/ticket/51670 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 00:56:57 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 00:56:57 -0000 Subject: [MacPorts] #53010: octave @4.2.0: build failure under Sierra Message-ID: <048.a62bc116d546e781b6e9fbe7b57e30fc@macports.org> #53010: octave @4.2.0: build failure under Sierra -------------------------+--------------------------------- Reporter: Schamschula | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: octave-control -------------------------+--------------------------------- As I maintain a number of octave packages, I wanted to update my installed version to the new update (4.2.0). Unfortunately, I get a link failure for LAPACK symbols: {{{ :info:build CXXLD libinterp/liboctinterp.la :info:build clang: warning: argument unused during compilation: '-pthread' :info:build clang: warning: argument unused during compilation: '-pthread' :info:build Undefined symbols for architecture x86_64: :info:build "_ctrsen_", referenced from: :info:build Fordschur(octave_value_list const&, int) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-ordschur.o) :info:build "_dggbak_", referenced from: :info:build Fqz(octave_value_list const&, int) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-qz.o) :info:build "_dggbal_", referenced from: :info:build Fqz(octave_value_list const&, int) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-qz.o) :info:build "_dgghrd_", referenced from: :info:build Fqz(octave_value_list const&, int) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-qz.o) :info:build "_dhgeqz_", referenced from: :info:build Fqz(octave_value_list const&, int) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-qz.o) :info:build "_dlag2_", referenced from: :info:build Fqz(octave_value_list const&, int) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-qz.o) :info:build "_dtgevc_", referenced from: :info:build Fqz(octave_value_list const&, int) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-qz.o) :info:build "_dtrsen_", referenced from: :info:build Fordschur(octave_value_list const&, int) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-ordschur.o) :info:build "_strsen_", referenced from: :info:build Fordschur(octave_value_list const&, int) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-ordschur.o) :info:build "_zggbak_", referenced from: :info:build Fqz(octave_value_list const&, int) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-qz.o) :info:build "_zggbal_", referenced from: :info:build Fqz(octave_value_list const&, int) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-qz.o) :info:build "_zgghrd_", referenced from: :info:build Fqz(octave_value_list const&, int) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-qz.o) :info:build "_zhgeqz_", referenced from: :info:build Fqz(octave_value_list const&, int) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-qz.o) :info:build "_ztgevc_", referenced from: :info:build Fqz(octave_value_list const&, int) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-qz.o) :info:build "_ztrsen_", referenced from: :info:build Fordschur(octave_value_list const&, int) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-ordschur.o) :info:build ld: symbol(s) not found for architecture x86_64 }}} Tis occurred both while upgrading my current configuration: i.e. octave +app+atlas+docs+fltk+gfortran+graphicsmagick+java+qt4gui+sound and the default i.e. octave +accelerate+app+docs+fltk+gfortran+graphicsmagick+java+qt4gui+sound I've attached the log file from the second build. The errors are identical in both cases. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 00:57:18 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 00:57:18 -0000 Subject: [MacPorts] #53010: octave @4.2.0: build failure under Sierra In-Reply-To: <048.a62bc116d546e781b6e9fbe7b57e30fc@macports.org> References: <048.a62bc116d546e781b6e9fbe7b57e30fc@macports.org> Message-ID: <063.3ffb13e7b231b8727b09bbde81b5d8e9@macports.org> #53010: octave @4.2.0: build failure under Sierra -----------------------------+--------------------------------- Reporter: Schamschula | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: octave-control | -----------------------------+--------------------------------- Changes (by Schamschula): * Attachment "octave-4.2.0-main.log.gz" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 00:58:13 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 00:58:13 -0000 Subject: [MacPorts] #53010: octave @4.2.0: build failure under Sierra In-Reply-To: <048.a62bc116d546e781b6e9fbe7b57e30fc@macports.org> References: <048.a62bc116d546e781b6e9fbe7b57e30fc@macports.org> Message-ID: <063.05d556381836e04e1ae9c002bb88fc37@macports.org> #53010: octave @4.2.0: build failure under Sierra --------------------------+--------------------------------- Reporter: Schamschula | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: octave | --------------------------+--------------------------------- Changes (by Schamschula): * port: octave-control => octave -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 01:18:57 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 01:18:57 -0000 Subject: [MacPorts] #52421: smjnj is not building In-Reply-To: <045.745758901d673ca778fb8e33b5851ea6@macports.org> References: <045.745758901d673ca778fb8e33b5851ea6@macports.org> Message-ID: <060.b46a22d7bd8ef20d087bbab44dff38a6@macports.org> #52421: smjnj is not building -----------------------+------------------------ Reporter: pmetzger | Owner: bfulgham@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: smlnj | -----------------------+------------------------ Comment (by nevil): Relates to: https://trac.macports.org/ticket/52972 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 01:54:57 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 01:54:57 -0000 Subject: [MacPorts] #53010: octave @4.2.0: build failure under Sierra In-Reply-To: <048.a62bc116d546e781b6e9fbe7b57e30fc@macports.org> References: <048.a62bc116d546e781b6e9fbe7b57e30fc@macports.org> Message-ID: <063.04ba36e402c87562d28a99f2bdfee065@macports.org> #53010: octave @4.2.0: build failure under Sierra --------------------------+--------------------------------- Reporter: Schamschula | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: octave | --------------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): As a leftover from octave-devel, patch-qscintilla2.diff accidentally patches m4/acinclude.m4 instead of configure.[[BR]] This causes {{{/bin/sh ./config.status --recheck}}} to rerun configure in the build phase. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 01:55:40 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 01:55:40 -0000 Subject: [MacPorts] #53010: octave @4.2.0: build failure under Sierra In-Reply-To: <048.a62bc116d546e781b6e9fbe7b57e30fc@macports.org> References: <048.a62bc116d546e781b6e9fbe7b57e30fc@macports.org> Message-ID: <063.f487cfd844ef7506af0f2b6999013f0b@macports.org> #53010: octave @4.2.0: build failure under Sierra --------------------------+--------------------------------- Reporter: Schamschula | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: octave | --------------------------+--------------------------------- Changes (by MarcusCalhoun-Lopez): * status: new => closed * resolution: => fixed Comment: In [changeset:"a43dddb7fe3ddba0d96c2341fedadd87b4ddd45a/macports-ports" a43dddb7/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="a43dddb7fe3ddba0d96c2341fedadd87b4ddd45a" octave: replace patch from octave-devel with correct patch A revbump is required since an incorrect build might be possible with a certain combinations of variants. Fixes https://trac.macports.org/ticket/53010 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 02:04:10 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 02:04:10 -0000 Subject: [MacPorts] #52972: smlnj @110.80 +universal: New Sierra compatible version of smlnj In-Reply-To: <042.c52af5c13fe8090445a889e6c66bb5d5@macports.org> References: <042.c52af5c13fe8090445a889e6c66bb5d5@macports.org> Message-ID: <057.5f5e84c2aa3a5ff6a63564a25639a17b@macports.org> #52972: smlnj @110.80 +universal: New Sierra compatible version of smlnj ---------------------+------------------------ Reporter: nevil | Owner: bfulgham@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: smlnj | ---------------------+------------------------ Comment (by pmetzger): This should probably get applied, no? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 02:06:46 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 02:06:46 -0000 Subject: [MacPorts] #52972: smlnj @110.80 +universal: New Sierra compatible version of smlnj In-Reply-To: <042.c52af5c13fe8090445a889e6c66bb5d5@macports.org> References: <042.c52af5c13fe8090445a889e6c66bb5d5@macports.org> Message-ID: <057.62781439a83e7a9779e462c3390dcc1d@macports.org> #52972: smlnj @110.80 +universal: New Sierra compatible version of smlnj ---------------------+------------------------ Reporter: nevil | Owner: bfulgham@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: smlnj | ---------------------+------------------------ Comment (by nevil): Fixes: https://trac.macports.org/ticket/52421 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 03:35:44 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 03:35:44 -0000 Subject: [MacPorts] #52582: ghc @7.8.3_4: RTS incompatibility with Sierra In-Reply-To: <047.31ef8be7dd7559a12bcd7c2b768f2d94@macports.org> References: <047.31ef8be7dd7559a12bcd7c2b768f2d94@macports.org> Message-ID: <062.60c9e65f329fff8167277f3597fe4c13@macports.org> #52582: ghc @7.8.3_4: RTS incompatibility with Sierra -------------------------+----------------------------- Reporter: shanemikel | Owner: neverpanic Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: sierra haspatch Port: ghc | -------------------------+----------------------------- Changes (by stevecheckoway): * Attachment "Portfile.diff" added. Trivial Portfile modification to use the patch. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 03:38:41 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 03:38:41 -0000 Subject: [MacPorts] #52582: ghc @7.8.3_4: RTS incompatibility with Sierra In-Reply-To: <047.31ef8be7dd7559a12bcd7c2b768f2d94@macports.org> References: <047.31ef8be7dd7559a12bcd7c2b768f2d94@macports.org> Message-ID: <062.204f5bf16bb33aff352b3132bbc204ed@macports.org> #52582: ghc @7.8.3_4: RTS incompatibility with Sierra -------------------------+----------------------------- Reporter: shanemikel | Owner: neverpanic Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: sierra haspatch Port: ghc | -------------------------+----------------------------- Comment (by stevecheckoway): After applying the GetTime.c patch, I can build and install ghc on macOS 10.12.1 (see the attached Portfile.diff for the trivial modifications that are all that were required). I'm not sure what the linking issues are since it linked just fine for me. It would be great if the patch could be committed. My recommendation is to apply this patch and close the bug. Additional issues can be tracked with a separate bug if need be. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 04:29:35 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 04:29:35 -0000 Subject: [MacPorts] #53011: x86_64-elf-binutils @ 2.23.1: Doesn't build on macOS Sierra Message-ID: <051.083eac2d4dd8db523e48e59d170257df@macports.org> #53011: x86_64-elf-binutils @ 2.23.1: Doesn't build on macOS Sierra ----------------------------+--------------------------------- Reporter: stevecheckoway | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: x86_64-elf-binutils ----------------------------+--------------------------------- On macOS 10.12.1, the port fails to build in the step where it runs make info in build/gas/doc. I don't see obvious errors and --disable-werror is being passed to gas's configure script. {{{ Making info in doc restore=: && backupdir=".am$$" && \ rm -rf $backupdir && mkdir $backupdir && \ if (makeinfo --split-size=5000000 --split-size=5000000 --version) >/dev/null 2>&1; then \ for f in x86_64-elf-binutils.info x86_64-elf-binutils.info-[0-9] x86_64-elf-binutils.info-[0-9][0-9] x86_64-elf-binutils.i[0-9] x86_64-elf- binutils.i[0-9][0-9]; do \ if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \ done; \ else :; fi && \ if makeinfo --split-size=5000000 --split-size=5000000 -I "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf-binutils/work/binutils-2.23.1/binutils/doc" -I "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf- binutils/work/binutils-2.23.1/binutils/../libiberty" -I "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf- binutils/work/binutils-2.23.1/binutils/../bfd/doc" -I ../../bfd/doc -I /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf-binutils/work/binutils-2.23.1/binutils/doc \ -o x86_64-elf-binutils.info `test -f 'x86_64-elf-binutils.texi' || echo '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf- binutils/work/binutils-2.23.1/binutils/doc/'`x86_64-elf-binutils.texi; \ then \ rc=0; \ else \ rc=$?; \ $restore $backupdir/* `echo "./x86_64-elf-binutils.info" | sed 's|[^/]*$||'`; \ fi; \ rm -rf $backupdir; exit $rc /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf-binutils/work/binutils-2.23.1/binutils/doc/x86_64 -elf-binutils.texi:4378: warning: @itemx should not begin @table /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf-binutils/work/binutils-2.23.1/binutils/doc/x86_64 -elf-binutils.texi:4386: @itemx must follow @item /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf-binutils/work/binutils-2.23.1/binutils/doc/x86_64 -elf-binutils.texi:4390: @itemx must follow @item /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf-binutils/work/binutils-2.23.1/binutils/doc/x86_64 -elf-binutils.texi:4396: @itemx must follow @item /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf-binutils/work/binutils-2.23.1/binutils/doc/x86_64 -elf-binutils.texi:4400: @itemx must follow @item /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf-binutils/work/binutils-2.23.1/binutils/doc/x86_64 -elf-binutils.texi:4410: @itemx must follow @item /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf-binutils/work/binutils-2.23.1/binutils/doc/x86_64 -elf-binutils.texi:2385: warning: node next `ranlib' in menu `readelf' and in sectioning `size' differ /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf-binutils/work/binutils-2.23.1/binutils/doc/x86_64 -elf-binutils.texi:2463: warning: node prev `size' in menu `readelf' and in sectioning `ranlib' differ /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf-binutils/work/binutils-2.23.1/binutils/doc/x86_64 -elf-binutils.texi:2687: warning: node next `strip' in menu `elfedit' and in sectioning `c++filt' differ /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf-binutils/work/binutils-2.23.1/binutils/doc/x86_64 -elf-binutils.texi:3221: warning: node next `nlmconv' in menu `windres' and in sectioning `windmc' differ /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf-binutils/work/binutils-2.23.1/binutils/doc/x86_64 -elf-binutils.texi:3326: warning: node next `windmc' in menu `dlltool' and in sectioning `windres' differ /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf-binutils/work/binutils-2.23.1/binutils/doc/x86_64 -elf-binutils.texi:3326: warning: node prev `windmc' in menu `windres' and in sectioning `nlmconv' differ /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf-binutils/work/binutils-2.23.1/binutils/doc/x86_64 -elf-binutils.texi:3487: warning: node next `windres' in menu `windmc' and in sectioning `dlltool' differ /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf-binutils/work/binutils-2.23.1/binutils/doc/x86_64 -elf-binutils.texi:3487: warning: node prev `windres' in menu `nlmconv' and in sectioning `windmc' differ /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf-binutils/work/binutils-2.23.1/binutils/doc/x86_64 -elf-binutils.texi:3681: warning: node next `dlltool' in menu `Common Options' and in sectioning `readelf' differ /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf-binutils/work/binutils-2.23.1/binutils/doc/x86_64 -elf-binutils.texi:3681: warning: node prev `dlltool' in menu `windmc' and in sectioning `windres' differ /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf-binutils/work/binutils-2.23.1/binutils/doc/x86_64 -elf-binutils.texi:4084: warning: node next `readelf' in menu `size' and in sectioning `elfedit' differ /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf-binutils/work/binutils-2.23.1/binutils/doc/x86_64 -elf-binutils.texi:4084: warning: node prev `readelf' in menu `ranlib' and in sectioning `dlltool' differ /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf-binutils/work/binutils-2.23.1/binutils/doc/x86_64 -elf-binutils.texi:4338: warning: node next `elfedit' in menu `c++filt' and in sectioning `Common Options' differ /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf-binutils/work/binutils-2.23.1/binutils/doc/x86_64 -elf-binutils.texi:4338: warning: node prev `elfedit' in menu `strip' and in sectioning `readelf' differ /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_x86_64 -elf-binutils/x86_64-elf-binutils/work/binutils-2.23.1/binutils/doc/x86_64 -elf-binutils.texi:4432: warning: node prev `Common Options' in menu `dlltool' and in sectioning `elfedit' differ make[3]: *** [x86_64-elf-binutils.info] Error 1 }}} It was easy to update the port to 2.27 but apparently make install is installing outside the directory. {{{ ---> Staging x86_64-elf-binutils into destroot Warning: x86_64-elf-binutils installs files outside the common directory structure. }}} I didn't investigate that, but I imagine that would need to be fixed to consider updating. Nevertheless, I've attached a (totally trivial) diff to the Portfile to update to 2.27. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 04:29:51 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 04:29:51 -0000 Subject: [MacPorts] #53011: x86_64-elf-binutils @ 2.23.1: Doesn't build on macOS Sierra In-Reply-To: <051.083eac2d4dd8db523e48e59d170257df@macports.org> References: <051.083eac2d4dd8db523e48e59d170257df@macports.org> Message-ID: <066.4fa9671e670c7b0d005c6c5e9ec6ac7f@macports.org> #53011: x86_64-elf-binutils @ 2.23.1: Doesn't build on macOS Sierra ----------------------------------+------------------- Reporter: stevecheckoway | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: x86_64-elf-binutils | ----------------------------------+------------------- Changes (by stevecheckoway): * Attachment "Portfile.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 04:46:02 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 04:46:02 -0000 Subject: [MacPorts] #52490: [Port Abandoned] Ports maintained by hum In-Reply-To: <041.9d8ed880a58e228011e8b4ff5729ba02@macports.org> References: <041.9d8ed880a58e228011e8b4ff5729ba02@macports.org> Message-ID: <056.62687584bf86fb7ef1385f7e1157a32a@macports.org> #52490: [Port Abandoned] Ports maintained by hum -------------------------------------------------+------------------------- Reporter: mf2k | Owner: humem Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: apache-solr3 apache-solr4 arowpp | bact bayon brown-cluster cabocha caffe cedar | chasen chasen-base chasen-ipadic chasen- | ipadic-sjis chasen-ipadic-utf8 chasen-naist- | jdic chasen-naist-jdic-sjis chasen-naist- | jdic-utf8 cicada classias cpi00 crfpp crfpp- | devel crfsuite cutter darts darts-clone | dualist eda emacs-app emacs-mac-app expgram | extractopinion gibbslda giza-pp google-glog | groonga hadoop hts_engine_API irstlm jdepp | jubatus jubatus-mpio jubatus-msgpack-rpc | jubatus_core julius juman juman6 kakarot KNBC | knp knp3 kytea lader lda-c lda-d liblbfgs | liblinear libsvm libzookeeper lmdb lucene- | gosen2 lucene-gosen4 mahout mallet marisa- | trie mecab mecab-base mecab-ipadic mecab- | ipadic-neologd mecab-ipadic-sjis mecab- | ipadic-utf8 mecab-java mecab-jumandic mecab- | jumandic-sjis mecab-jumandic-utf8 mecab- | naist-jdic mecab-naist-jdic-sjis mecab-naist- | jdic-utf8 mecab-sjis mecab-utf8 mgizapp | MMDAgent mosesdecoder msgpack msgpack1 | normalizeNumexp oll oniguruma5 opal-ml | open_jtalk openfst p5-mecab p5-termextract p5 | -text-csv_xs palmkit pecco pficommon pialign | plda portaudio py-breadability py-chainer py- | docopt py-gensim py-jubatus-client py-langid | py-leveldb py-mecab py-mmh3 py-nltk py-nltk3 | py-pymc py-pymc3 py-sparqlwrapper py-sumy py- | word2vec rb-mecab rb19-mecab re2 rnnlm | seekanser sgd simstring sinsy slearp sofia-ml | sparsehash sptk ssrc stanford-ner stanford- | parser stanford-postagger syncha tinycdb | TinySVM unidic-mecab ux-trie vowpal_wabbit | wapiti word2vec yakmo yamcha zunda | -------------------------------------------------+------------------------- Changes (by kurthindenburg): * status: new => closed * resolution: => fixed Comment: In [changeset:"e7f7da97481097d583782c6e1fda50114055ea93/macports-ports" e7f7da97/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="e7f7da97481097d583782c6e1fda50114055ea93" multiple ports - remove hum maintainer remove outdated $Id when found closes https://trac.macports.org/ticket/52490 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 04:49:31 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 04:49:31 -0000 Subject: [MacPorts] #40393: hadoop install fails when setting up ssh In-Reply-To: <053.1e8a0184950145f45a0d4e33a6456bff@macports.org> References: <053.1e8a0184950145f45a0d4e33a6456bff@macports.org> Message-ID: <068.ed40709d649c4f526f8dd8102e95a56a@macports.org> #40393: hadoop install fails when setting up ssh -------------------------+-------------------------------- Reporter: kirc0076@… | Owner: macports-tickets@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: hadoop | -------------------------+-------------------------------- Changes (by kurthindenburg): * status: new => assigned * owner: humem => macports-tickets@… -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 04:50:04 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 04:50:04 -0000 Subject: [MacPorts] Batch modify: #40393, #42506, #43427, #46667, #47338, ... Message-ID: <138.c2aad20fa261e603756ec3a15b1ab793@macports.org> Batch modification to #40393, #42506, #43427, #46667, #47338, #47524, #47840, #48578, #48691, #49069, #49113, #49152, #49997, #50231, #50592, #50644 by kurthindenburg: Action: reassign -- Tickets URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 04:54:06 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 04:54:06 -0000 Subject: [MacPorts] #52490: [Port Abandoned] Ports maintained by hum In-Reply-To: <041.9d8ed880a58e228011e8b4ff5729ba02@macports.org> References: <041.9d8ed880a58e228011e8b4ff5729ba02@macports.org> Message-ID: <056.90eb25934732ac0cd35b378be18c23b3@macports.org> #52490: [Port Abandoned] Ports maintained by hum -------------------------------------------------+------------------------- Reporter: mf2k | Owner: humem Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: apache-solr3 apache-solr4 arowpp | bact bayon brown-cluster cabocha caffe cedar | chasen chasen-base chasen-ipadic chasen- | ipadic-sjis chasen-ipadic-utf8 chasen-naist- | jdic chasen-naist-jdic-sjis chasen-naist- | jdic-utf8 cicada classias cpi00 crfpp crfpp- | devel crfsuite cutter darts darts-clone | dualist eda emacs-app emacs-mac-app expgram | extractopinion gibbslda giza-pp google-glog | groonga hadoop hts_engine_API irstlm jdepp | jubatus jubatus-mpio jubatus-msgpack-rpc | jubatus_core julius juman juman6 kakarot KNBC | knp knp3 kytea lader lda-c lda-d liblbfgs | liblinear libsvm libzookeeper lmdb lucene- | gosen2 lucene-gosen4 mahout mallet marisa- | trie mecab mecab-base mecab-ipadic mecab- | ipadic-neologd mecab-ipadic-sjis mecab- | ipadic-utf8 mecab-java mecab-jumandic mecab- | jumandic-sjis mecab-jumandic-utf8 mecab- | naist-jdic mecab-naist-jdic-sjis mecab-naist- | jdic-utf8 mecab-sjis mecab-utf8 mgizapp | MMDAgent mosesdecoder msgpack msgpack1 | normalizeNumexp oll oniguruma5 opal-ml | open_jtalk openfst p5-mecab p5-termextract p5 | -text-csv_xs palmkit pecco pficommon pialign | plda portaudio py-breadability py-chainer py- | docopt py-gensim py-jubatus-client py-langid | py-leveldb py-mecab py-mmh3 py-nltk py-nltk3 | py-pymc py-pymc3 py-sparqlwrapper py-sumy py- | word2vec rb-mecab rb19-mecab re2 rnnlm | seekanser sgd simstring sinsy slearp sofia-ml | sparsehash sptk ssrc stanford-ner stanford- | parser stanford-postagger syncha tinycdb | TinySVM unidic-mecab ux-trie vowpal_wabbit | wapiti word2vec yakmo yamcha zunda | -------------------------------------------------+------------------------- Comment (by kurthindenburg): In [changeset:"08e198a83738714a118997c698dce2accb482410/macports-ports" 08e198a8/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="08e198a83738714a118997c698dce2accb482410" multiple ports - remove hum maintainer see https://trac.macports.org/ticket/52490 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 05:07:52 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 05:07:52 -0000 Subject: [MacPorts] #53012: [Port Abandoned] Ports maintained by mww Message-ID: <051.c9f8f6ec577f4dc24f5a4ded58088841@macports.org> #53012: [Port Abandoned] Ports maintained by mww ----------------------------+------------------- Reporter: kurthindenburg | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: ----------------------------+------------------- mww (Markus W. Weißmann) has not been seen for [search:mww at macports.org over a year] and has a large number [query:status=!closed&owner=mww at macports.org open tickets]. Markus, are you interested in maintaining any of these? port echo maintainer:mww lists 243 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 05:10:33 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 05:10:33 -0000 Subject: [MacPorts] #52863: [Port Abandoned] man In-Reply-To: <043.7ccba63e5b3bae0bcc538ba97561b84e@macports.org> References: <043.7ccba63e5b3bae0bcc538ba97561b84e@macports.org> Message-ID: <058.3adec9e6dcf8763b5e2965b6e38a0ca3@macports.org> #52863: [Port Abandoned] man ---------------------+-------------------- Reporter: raimue | Owner: mww@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: man | ---------------------+-------------------- Changes (by kurthindenburg): * status: new => closed * resolution: => fixed Comment: In [changeset:"572a1dbbb6fd5f67a70b50f56bd811581b165990/macports-ports" 572a1dbb/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="572a1dbbb6fd5f67a70b50f56bd811581b165990" man: set nomaintainer remove outdated $Id$ and add modeline closes https://trac.macports.org/ticket/52863 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 05:20:18 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 05:20:18 -0000 Subject: [MacPorts] #45612: Failed to Install SoXt on Yosemite In-Reply-To: <060.7bc0a648dbdb7a9084279f94b875f613@macports.org> References: <060.7bc0a648dbdb7a9084279f94b875f613@macports.org> Message-ID: <075.dbef6f40a2611d9a9d1ea1318e51d7ef@macports.org> #45612: Failed to Install SoXt on Yosemite ------------------------------+-------------------------------- Reporter: matthewl.lund@… | Owner: macports-tickets@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.2 Resolution: | Keywords: Port: SoXt | ------------------------------+-------------------------------- Changes (by kurthindenburg): * owner: css@… => macports-tickets@… -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 05:21:22 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 05:21:22 -0000 Subject: [MacPorts] #41394: vtk44 @4.4.2 Configure error - build failure In-Reply-To: <058.28755f0e2ee4a015adf355ef0762b04e@macports.org> References: <058.28755f0e2ee4a015adf355ef0762b04e@macports.org> Message-ID: <073.69405f6a0209b29f4fbd56f17776d8db@macports.org> #41394: vtk44 @4.4.2 Configure error - build failure ----------------------------+-------------------- Reporter: ppstonerock@… | Owner: css@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: invalid | Keywords: Port: vtk44 | ----------------------------+-------------------- Changes (by kurthindenburg): * status: new => closed * resolution: => invalid Comment: port replaced by vtk -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 05:23:08 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 05:23:08 -0000 Subject: [MacPorts] #33989: VTK: error: 'strcmp' was not declared in this scope In-Reply-To: <058.d8d4abdcc5df87411ee9cc58eb4764bb@macports.org> References: <058.d8d4abdcc5df87411ee9cc58eb4764bb@macports.org> Message-ID: <073.526548e076998d79aecd0f086090a8b7@macports.org> #33989: VTK: error: 'strcmp' was not declared in this scope ----------------------------+-------------------- Reporter: beany_kelly@… | Owner: css@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Resolution: invalid | Keywords: Port: vtk44 | ----------------------------+-------------------- Changes (by kurthindenburg): * status: new => closed * resolution: => invalid Comment: port replaced by vtk -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 05:23:28 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 05:23:28 -0000 Subject: =?utf-8?q?Re=3A_=5BMacPorts=5D_=2334305=3A_VTK=3A_error=3A_?= =?utf-8?q?=E2=80=98FSSpec=E2=80=99_has_no_member_named_=E2=80=98?= =?utf-8?q?name=E2=80=99?= In-Reply-To: <054.49f107ed69c3e581fe661d31dcdbfc53@macports.org> References: <054.49f107ed69c3e581fe661d31dcdbfc53@macports.org> Message-ID: <069.3f73b9afd6bae1bf6a52500b0eba5054@macports.org> #34305: VTK: error: ‘FSSpec’ has no member named ‘name’ ------------------------+-------------------- Reporter: orgicus@… | Owner: css@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Resolution: invalid | Keywords: Port: vtk44 | ------------------------+-------------------- Changes (by kurthindenburg): * status: new => closed * resolution: => invalid Comment: port replaced by vtk -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 05:34:38 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 05:34:38 -0000 Subject: [MacPorts] #52874: [Port Abandoned] Ports maintained by mac.com:giorgio_v In-Reply-To: <041.e2fb9e68cfaf643bb20a752caf36a8e6@macports.org> References: <041.e2fb9e68cfaf643bb20a752caf36a8e6@macports.org> Message-ID: <056.05e7b88de0947c7b2478b277a19c518a@macports.org> #52874: [Port Abandoned] Ports maintained by mac.com:giorgio_v -------------------------------------------------+------------------------- Reporter: mf2k | Owner: giorgio_v@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: pgbouncer pgintcl pgpool-II pgtcl | tclxml xmlgen | -------------------------------------------------+------------------------- Changes (by kurthindenburg): * status: new => closed * resolution: => fixed Comment: In [changeset:"4eb7f6d0bf927b19c6110133c30875e3a75925ca/macports-ports" 4eb7f6d0/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="4eb7f6d0bf927b19c6110133c30875e3a75925ca" multiple ports: remove giorgio_v maintainer Remove $Id and add modeline closes https://trac.macports.org/ticket/52874 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 05:34:55 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 05:34:55 -0000 Subject: [MacPorts] #36761: pgbouncer 1.5.3 version update and support postgresql up to 92 In-Reply-To: <057.433d6384072b3562ae98dd63925175a3@macports.org> References: <057.433d6384072b3562ae98dd63925175a3@macports.org> Message-ID: <072.8d698f49932c85231c6ac266aeffeae6@macports.org> #36761: pgbouncer 1.5.3 version update and support postgresql up to 92 ---------------------------+-------------------------------- Reporter: gunnlaugur@… | Owner: macports-tickets@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: haspatch Port: pgbouncer | ---------------------------+-------------------------------- Changes (by kurthindenburg): * owner: giorgio_v@… => macports-tickets@… * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 05:35:08 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 05:35:08 -0000 Subject: [MacPorts] #52764: pltcl fails to build In-Reply-To: <044.6599c857d0c0149062b6127f3ab859af@macports.org> References: <044.6599c857d0c0149062b6127f3ab859af@macports.org> Message-ID: <059.d4821df680bbbab4dc873f6208b0bf6c@macports.org> #52764: pltcl fails to build ----------------------+-------------------------------- Reporter: decibel | Owner: macports-tickets@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: pgtcl | ----------------------+-------------------------------- Changes (by kurthindenburg): * owner: giorgio_v@… => macports-tickets@… -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 12:31:32 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 12:31:32 -0000 Subject: [MacPorts] #47569: avahi: Could not find Python module gtk In-Reply-To: <056.36684c1b324258fc0b098f365d748731@macports.org> References: <056.36684c1b324258fc0b098f365d748731@macports.org> Message-ID: <071.0a5605e7eb02c9f41ff1526a506941af@macports.org> #47569: avahi: Could not find Python module gtk ------------------------+-------------------------------- Reporter: rudloff@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: avahi | ------------------------+-------------------------------- Comment (by hubsif): I just ran into the same issue and found this: https://trac.macports.org/ticket/12966#comment:19 {{{sudo port install cairo +x11}}} fixed it for the moment. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 13:32:07 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 13:32:07 -0000 Subject: [MacPorts] #52509: py27-spatialite 3.0.1_1: Build failure In-Reply-To: <060.421a76205539dd6cc67c810cb5ae3128@macports.org> References: <060.421a76205539dd6cc67c810cb5ae3128@macports.org> Message-ID: <075.76ca03914d200ea2393429e7a814dbe3@macports.org> #52509: py27-spatialite 3.0.1_1: Build failure ------------------------------+-------------------------------- Reporter: frank.ortmann@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: py-spatialite | ------------------------------+-------------------------------- Comment (by FrankOrtmann): Looks like the problem was resolved. I am now able to install py_spatialite and QGIS. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 14:28:28 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 14:28:28 -0000 Subject: [MacPorts] #53011: x86_64-elf-binutils @ 2.23.1: Doesn't build on macOS Sierra In-Reply-To: <051.083eac2d4dd8db523e48e59d170257df@macports.org> References: <051.083eac2d4dd8db523e48e59d170257df@macports.org> Message-ID: <066.1bce16705b627dc359ff0b00f80b5e16@macports.org> #53011: x86_64-elf-binutils @ 2.23.1: Doesn't build on macOS Sierra ----------------------------------+---------------------------- Reporter: stevecheckoway | Owner: nategriswold@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: x86_64-elf-binutils | ----------------------------------+---------------------------- Changes (by mf2k): * cc: nategriswold@… (removed) * owner: => nategriswold@… * status: new => assigned Comment: Thanks. Comments on your patch: - Please keep the rmd160 checksum. We like to have at least 2 to verify integrity. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 14:39:34 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 14:39:34 -0000 Subject: [MacPorts] #52764: pltcl fails to build In-Reply-To: <044.6599c857d0c0149062b6127f3ab859af@macports.org> References: <044.6599c857d0c0149062b6127f3ab859af@macports.org> Message-ID: <059.80f0752f4f5512942133a387a10c724b@macports.org> #52764: pltcl fails to build ----------------------+-------------------------------- Reporter: decibel | Owner: macports-tickets@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: pgtcl | ----------------------+-------------------------------- Comment (by mf2k): In the future, please use WikiFormatting. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 14:40:14 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 14:40:14 -0000 Subject: [MacPorts] #52764: pgtcl fails to build (was: pltcl fails to build) In-Reply-To: <044.6599c857d0c0149062b6127f3ab859af@macports.org> References: <044.6599c857d0c0149062b6127f3ab859af@macports.org> Message-ID: <059.77a2adb579814b0504731dea99387a48@macports.org> #52764: pgtcl fails to build ----------------------+-------------------------------- Reporter: decibel | Owner: macports-tickets@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: pgtcl | ----------------------+-------------------------------- Description changed by mf2k: Old description: > :info:build ./generic/pgtclCmds.c:2438:15: error: no member named > 'errorLine' in 'struct Tcl_Interp' > :info:build > interp->errorLine); > :info:build ~~~~~~ ^ New description: {{{ :info:build ./generic/pgtclCmds.c:2438:15: error: no member named 'errorLine' in 'struct Tcl_Interp' :info:build interp->errorLine); :info:build ~~~~~~ ^ }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 14:43:07 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 14:43:07 -0000 Subject: [MacPorts] #47569: avahi: Could not find Python module gtk In-Reply-To: <056.36684c1b324258fc0b098f365d748731@macports.org> References: <056.36684c1b324258fc0b098f365d748731@macports.org> Message-ID: <071.385871a6cea39fdb033ee3a109b9224b@macports.org> #47569: avahi: Could not find Python module gtk ------------------------+-------------------------------- Reporter: rudloff@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: duplicate | Keywords: Port: avahi | ------------------------+-------------------------------- Changes (by mf2k): * status: new => closed * resolution: => duplicate Comment: Yes this is a duplicate of #12966. cairo has long had +x11 as a default variant. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 14:44:57 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 14:44:57 -0000 Subject: [MacPorts] #52509: py27-spatialite 3.0.1_1: Build failure In-Reply-To: <049.b23383e6c027c007d5eb528d1d02e898@macports.org> References: <049.b23383e6c027c007d5eb528d1d02e898@macports.org> Message-ID: <064.551c466166b91e0fe45e0cc88606ceab@macports.org> #52509: py27-spatialite 3.0.1_1: Build failure ----------------------------+-------------------------------- Reporter: FrankOrtmann | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: py-spatialite | ----------------------------+-------------------------------- Changes (by mf2k): * status: new => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 15:37:22 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 15:37:22 -0000 Subject: [MacPorts] #53011: x86_64-elf-binutils @ 2.23.1: Doesn't build on macOS Sierra In-Reply-To: <051.083eac2d4dd8db523e48e59d170257df@macports.org> References: <051.083eac2d4dd8db523e48e59d170257df@macports.org> Message-ID: <066.15e0255e6ecab86ea8c90d898f93d3ee@macports.org> #53011: x86_64-elf-binutils @ 2.23.1: Doesn't build on macOS Sierra ----------------------------------+---------------------------- Reporter: stevecheckoway | Owner: nategriswold@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: x86_64-elf-binutils | ----------------------------------+---------------------------- Comment (by stevecheckoway): I'm happy to keep the rmd160 hash, but note that, cryptographically speaking, this doesn't actually give much additional security. See Joux's [http://link.springer.com/chapter/10.1007%2F978-3-540-28628-8_19 Multicollisions in Iterated Hash Functions. Application to Cascaded Constructions]. A natural construction to build large hash values is to concatenate several smaller hashes. For example, given two hash functions F and G, it seems reasonable given a message M to form the large hash value (F(M)G(M)). In this construction, F and G can either be two completely different hash functions or two slightly different instances of the same hash function. If F and G are good iterated hash functions with no attack better than the generic birthday paradox attack, we claim that the hash function FG obtained by concatenating F and G is not really more secure that F or G by itself. Moreover, this result applies both to collision resistance, preimage resistance and second preimage resistance. We'd be better off just using SHA-512. But really, SHA-256 is sufficient. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 15:48:53 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 15:48:53 -0000 Subject: [MacPorts] #52632: Inkscape-app quits immediately after install In-Reply-To: <056.34df243aa80de466541391e09f3b22b1@macports.org> References: <056.34df243aa80de466541391e09f3b22b1@macports.org> Message-ID: <071.43b5a7c0cfe07eb758f6474b5729a6a3@macports.org> #52632: Inkscape-app quits immediately after install ---------------------------+-------------------------------- Reporter: iansidor@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: inkscape-app | ---------------------------+-------------------------------- Comment (by atuyosi): I also got to have a similar problem with Inkscape-devel package. - $ LANG=ja_JP.UTF-8 inkscape -> NG display a message such like "Internal error occurred" in Japanese, and exit. - $ LANG=ja_JP inkscape -> OK - $ LANG=C inkscape -> OK I hope this information is useful for something. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 15:49:15 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 15:49:15 -0000 Subject: [MacPorts] #53013: iTerm2 @3.0.5: update to 3.0.12 Message-ID: <041.b0a955ad9400c638b50ad70b61073a25@macports.org> #53013: iTerm2 @3.0.5: update to 3.0.12 --------------------+-------------------- Reporter: l2dy | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: iTerm2 --------------------+-------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 15:51:41 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 15:51:41 -0000 Subject: [MacPorts] #53014: kdevelop @4.7.3: update to 5.0.3 Message-ID: <041.415ac91263c87097e3134109438f89e2@macports.org> #53014: kdevelop @4.7.3: update to 5.0.3 --------------------+---------------------- Reporter: l2dy | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: kdevelop --------------------+---------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 16:03:58 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 16:03:58 -0000 Subject: [MacPorts] #53013: iTerm2 @3.0.5: update to 3.0.12 In-Reply-To: <041.b0a955ad9400c638b50ad70b61073a25@macports.org> References: <041.b0a955ad9400c638b50ad70b61073a25@macports.org> Message-ID: <056.39c56cee91f6a71c528901c2420ffba5@macports.org> #53013: iTerm2 @3.0.5: update to 3.0.12 ---------------------+---------------------- Reporter: l2dy | Owner: markemer Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: iTerm2 | ---------------------+---------------------- Changes (by mf2k): * owner: => markemer * cc: markemer (removed) * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 16:05:26 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 16:05:26 -0000 Subject: [MacPorts] #50332: [Port Abandoned] Ports maintained by css In-Reply-To: <041.40b8b3c8786c9798f030f023a758af18@macports.org> References: <041.40b8b3c8786c9798f030f023a758af18@macports.org> Message-ID: <056.f0452ecb384d0ff8b6a76831152a154e@macports.org> #50332: [Port Abandoned] Ports maintained by css -------------------------------------------------+------------------------- Reporter: mf2k | Owner: css@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: apg doxygen glw hnb hrsh2csv | inventor rsync-lart streamripper tivodecode | vtk44 | -------------------------------------------------+------------------------- Changes (by kurthindenburg): * status: new => closed * resolution: => fixed Comment: Here's the list as-is - also the only tickets open are for these - reopen this if you want removed from any of these apg doxygen glw hnb hrsh2csv inventor rsync-lart streamripper tivodecode -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 16:12:55 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 16:12:55 -0000 Subject: [MacPorts] #52879: [Port Abandoned] chicken In-Reply-To: <041.3a4877fba0c0836662bd95aa794b166f@macports.org> References: <041.3a4877fba0c0836662bd95aa794b166f@macports.org> Message-ID: <056.cb5c06d8b120ac2dc86df1c40c13c996@macports.org> #52879: [Port Abandoned] chicken ----------------------+--------------------- Reporter: mf2k | Owner: iraikov Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: chicken | ----------------------+--------------------- Changes (by kurthindenburg): * status: new => closed * resolution: => fixed Comment: In [changeset:"041a139750cc5006d188d8e377998a7b4bba80c8/macports-ports" 041a1397/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="041a139750cc5006d188d8e377998a7b4bba80c8" chicken: set nomaintainer remove unused $Id$ closes https://trac.macports.org/ticket/52879 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 16:13:22 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 16:13:22 -0000 Subject: [MacPorts] #52719: Chicken outdated In-Reply-To: <042.eba3057947fd32d66837c3d3fc3bbb86@macports.org> References: <042.eba3057947fd32d66837c3d3fc3bbb86@macports.org> Message-ID: <057.c508abd2f12b9e4cccf1767ab2b4c51a@macports.org> #52719: Chicken outdated ----------------------+-------------------------------- Reporter: zilti | Owner: macports-tickets@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: chicken | ----------------------+-------------------------------- Changes (by kurthindenburg): * owner: iraikov => macports-tickets@… -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 16:46:02 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 16:46:02 -0000 Subject: [MacPorts] #52719: Chicken outdated In-Reply-To: <042.eba3057947fd32d66837c3d3fc3bbb86@macports.org> References: <042.eba3057947fd32d66837c3d3fc3bbb86@macports.org> Message-ID: <057.5b1840baa1735d6bf751ea6022e7d487@macports.org> #52719: Chicken outdated ----------------------+-------------------------------- Reporter: zilti | Owner: macports-tickets@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: chicken | ----------------------+-------------------------------- Changes (by kurthindenburg): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"30b226b2571fe9f0faa7169cbfa9055b690ac54b/macports-ports" 30b226b2/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="30b226b2571fe9f0faa7169cbfa9055b690ac54b" chicken: update to 4.11.0 enable tests closes https://trac.macports.org/ticket/52719#comment:3 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 17:46:49 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 17:46:49 -0000 Subject: [MacPorts] #52632: Inkscape-app quits immediately after install In-Reply-To: <056.34df243aa80de466541391e09f3b22b1@macports.org> References: <056.34df243aa80de466541391e09f3b22b1@macports.org> Message-ID: <071.96fe0743c70c034806e9f44c038d7082@macports.org> #52632: Inkscape-app quits immediately after install ---------------------------+-------------------------------- Reporter: iansidor@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: inkscape-app | ---------------------------+-------------------------------- Changes (by raimue): * Attachment "0001-inkscape-Fix-crash-on-font-name-style-being-NULL.patch" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 17:50:35 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 17:50:35 -0000 Subject: [MacPorts] #52632: Inkscape-app quits immediately after install In-Reply-To: <056.34df243aa80de466541391e09f3b22b1@macports.org> References: <056.34df243aa80de466541391e09f3b22b1@macports.org> Message-ID: <071.1cd01809cd3fd87cd728bff12c6ca378@macports.org> #52632: Inkscape-app quits immediately after install ---------------------------+-------------------------------- Reporter: iansidor@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: inkscape-app | ---------------------------+-------------------------------- Comment (by raimue): Here is a patch that solves the problem for me. It is partly based on a backport from upstream trunk, but still required an additional null-check. Increasing revision as this fixes a runtime problem. I did not look too closely, therefore I did not identify which font(s) are actually causing this problem. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 18:48:55 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 18:48:55 -0000 Subject: [MacPorts] #52935: transmission-x11 2.92_0 darwin 16 build fail In-Reply-To: <045.bd2758e52c09829d3aa98a58c8cf0cfc@macports.org> References: <045.bd2758e52c09829d3aa98a58c8cf0cfc@macports.org> Message-ID: <060.fb224569c1ad9edac5a531510787fbd8@macports.org> #52935: transmission-x11 2.92_0 darwin 16 build fail -------------------------------+-------------------------------- Reporter: datajerk | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: transmission-x11 | -------------------------------+-------------------------------- Changes (by kurthindenburg): * status: new => closed * resolution: => fixed Comment: In [changeset:"48dc7d989a29b96c574d6241f9ee034dc7b2de46/macports-ports" 48dc7d98/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="48dc7d989a29b96c574d6241f9ee034dc7b2de46" transmission-x11: fix m4 build error Use Gentoo's patch to fix m4 error closes https://trac.macports.org/ticket/52935 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 18:51:16 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 18:51:16 -0000 Subject: [MacPorts] #52079: gcc-4.0: -E, -S, -save-temps and -M options are not allowed with multiple -arch flags In-Reply-To: <047.c76c53eadc54051bdb788f8e42bf9fa0@macports.org> References: <047.c76c53eadc54051bdb788f8e42bf9fa0@macports.org> Message-ID: <062.579d4d72f4bf62f46dd81bc258bd4d77@macports.org> #52079: gcc-4.0: -E, -S, -save-temps and -M options are not allowed with multiple -arch flags -------------------------+-------------------------------- Reporter: ryandesign | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: fixed | Keywords: leopard tiger Port: | -------------------------+-------------------------------- Changes (by ryandesign): * cc: jmroot (added) * status: new => closed * resolution: => fixed Comment: Resolved by changeset:701e7b2597f2da954a390b1b63aa90d6f7aaba20/macports- base -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 19:05:24 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 19:05:24 -0000 Subject: [MacPorts] #45861: Linphone-devel port is extremely outdated and should be removed In-Reply-To: <055.203ce1b700a10c67fbf9903e85a3ad9c@macports.org> References: <055.203ce1b700a10c67fbf9903e85a3ad9c@macports.org> Message-ID: <070.735f63c8a12f1048350190b282509986@macports.org> #45861: Linphone-devel port is extremely outdated and should be removed -----------------------------+---------------------------- Reporter: william@… | Owner: simon.morlat@… Type: defect | Status: closed Priority: Low | Milestone: Component: ports | Version: 2.3.2 Resolution: fixed | Keywords: Port: linphone-devel | -----------------------------+---------------------------- Changes (by kurthindenburg): * status: new => closed * resolution: => fixed Comment: In [changeset:"03f19706097de24dea5fe49a560969451633fded/macports-ports" 03f19706/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="03f19706097de24dea5fe49a560969451633fded" linphone-devel: replaced by linphone very old port that hasn't been updated and is behind linphone version maintainer timeout closes https://trac.macports.org/ticket/45861 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 20:34:03 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 20:34:03 -0000 Subject: [MacPorts] #39100: aria2 @1.17.0 build error related to AppleTLSContext.cc; build failure In-Reply-To: <056.4e194796af1a0cc9176cf44c329f9197@macports.org> References: <056.4e194796af1a0cc9176cf44c329f9197@macports.org> Message-ID: <071.433d3db7f0f25d2b840f1aa684e6e5cd@macports.org> #39100: aria2 @1.17.0 build error related to AppleTLSContext.cc; build failure ------------------------+-------------------------------- Reporter: bitmail@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: aria2 | ------------------------+-------------------------------- Comment (by ken-cunningham-webuse): This one can be closed. I fixed this in . -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 20:37:55 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 20:37:55 -0000 Subject: [MacPorts] #52090: tk @8.6.6_0 fails building on 10.6.8 In-Reply-To: <047.b40f13fc34b092b9798f366d0e483dce@macports.org> References: <047.b40f13fc34b092b9798f366d0e483dce@macports.org> Message-ID: <062.1732bfd432eedbd977a5ebeabfebb434@macports.org> #52090: tk @8.6.6_0 fails building on 10.6.8 -------------------------+------------------------- Reporter: udbraumann | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: tk | -------------------------+------------------------- Comment (by ken-cunningham-webuse): Please see also: and -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 20:47:33 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 20:47:33 -0000 Subject: [MacPorts] #39100: aria2 @1.17.0 build error related to AppleTLSContext.cc; build failure In-Reply-To: <056.4e194796af1a0cc9176cf44c329f9197@macports.org> References: <056.4e194796af1a0cc9176cf44c329f9197@macports.org> Message-ID: <071.48e759df9579791215cbf91fa14dba8d@macports.org> #39100: aria2 @1.17.0 build error related to AppleTLSContext.cc; build failure ------------------------+-------------------------------- Reporter: bitmail@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: fixed | Keywords: Port: aria2 | ------------------------+-------------------------------- Changes (by dbevans): * status: new => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 21:37:59 2016 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2016 21:37:59 -0000 Subject: [MacPorts] #53015: octave-octclip, octave-octproj: missing patch file Message-ID: <048.be8fb1f67e3eed30df7100ac0090b392@macports.org> #53015: octave-octclip, octave-octproj: missing patch file -------------------------+------------------------------------------- Reporter: Schamschula | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: octave-octclip octave-octproj -------------------------+------------------------------------------- octave-octclip and octave-octproj ask for patch-flags.diff, however this file was not uploaded along with the octave 4.2.0 update: See https://github.com/macports/macports- ports/commit/5c63c9706d260f6a6557b110bb7608f0d92287bf -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 01:42:25 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 01:42:25 -0000 Subject: [MacPorts] #29083: gcc44 build fail - Bootstrap comparison failure In-Reply-To: <061.0a4e251181c87fb3bba07496e719b0f3@macports.org> References: <061.0a4e251181c87fb3bba07496e719b0f3@macports.org> Message-ID: <076.7b74720e0518bc9dc9cfde4b17c33716@macports.org> #29083: gcc44 build fail - Bootstrap comparison failure -------------------------------+-------------------- Reporter: cinjon.resnick@… | Owner: mww@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Resolution: worksforme | Keywords: Port: gcc44 | -------------------------------+-------------------- Changes (by jmroot): * status: new => closed * resolution: => worksforme -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 01:45:24 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 01:45:24 -0000 Subject: [MacPorts] #53015: octave-octclip, octave-octproj: missing patch file In-Reply-To: <048.be8fb1f67e3eed30df7100ac0090b392@macports.org> References: <048.be8fb1f67e3eed30df7100ac0090b392@macports.org> Message-ID: <063.293f0de8c0e7bfe54fc711a224b9b935@macports.org> #53015: octave-octclip, octave-octproj: missing patch file --------------------------------------------+------------------------------ Reporter: Schamschula | Owner: MarcusCalhoun- | Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: octave-octclip octave-octproj | --------------------------------------------+------------------------------ Changes (by MarcusCalhoun-Lopez): * status: new => closed * resolution: => fixed Comment: In [changeset:"9ea1455793a659449403aaa5f1d4f987c1d930f7/macports-ports" 9ea1455/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="9ea1455793a659449403aaa5f1d4f987c1d930f7" octave-*: add forgotten patchfiles 5c63c9706d260f6a6557b110bb7608f0d92287bf should have included the patchfiles. Fixes https://trac.macports.org/ticket/53015 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 01:46:04 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 01:46:04 -0000 Subject: [MacPorts] #53015: octave-octclip, octave-octproj: missing patch file In-Reply-To: <048.be8fb1f67e3eed30df7100ac0090b392@macports.org> References: <048.be8fb1f67e3eed30df7100ac0090b392@macports.org> Message-ID: <063.286b5bdca33266c888c5c4ae30c7f3c0@macports.org> #53015: octave-octclip, octave-octproj: missing patch file --------------------------------------------+------------------------------ Reporter: Schamschula | Owner: MarcusCalhoun- | Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: octave-octclip octave-octproj | --------------------------------------------+------------------------------ Comment (by MarcusCalhoun-Lopez): Sorry for the error. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 01:55:52 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 01:55:52 -0000 Subject: [MacPorts] #28096: stale interpreter reference used after error in interactive mode In-Reply-To: <056.a4b90d873d22c559e7694fdbb81d59b0@macports.org> References: <056.a4b90d873d22c559e7694fdbb81d59b0@macports.org> Message-ID: <071.3313e1c2ec39ba63409ef86e959acafa@macports.org> #28096: stale interpreter reference used after error in interactive mode --------------------------+-------------------------------- Reporter: nickhol18@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Low | Milestone: Component: base | Version: 1.9.2 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by jmroot): This may have been fixed by changeset:77217baff41e05f4fe900cbfa9fa9de87c0117d5/macports-base. Can anyone still repro? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 02:02:49 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 02:02:49 -0000 Subject: [MacPorts] #30168: adduser results in macports users appearing as interactive users In-Reply-To: <059.fa3eb3c2f47d410413f1c8b6092bf8c3@macports.org> References: <059.fa3eb3c2f47d410413f1c8b6092bf8c3@macports.org> Message-ID: <074.d1c3b693ef6ed05c0ca551ce9db00e0a@macports.org> #30168: adduser results in macports users appearing as interactive users -----------------------------+-------------------------------- Reporter: michal.vanco@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: MacPorts 2.0.1 Component: base | Version: 1.9.99 Resolution: fixed | Keywords: adduser lion Port: | -----------------------------+-------------------------------- Changes (by jmroot): * status: reopened => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 02:05:47 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 02:05:47 -0000 Subject: [MacPorts] #30365: Additional option to selfupdate required if major changes take place In-Reply-To: <055.783192f55cd29bb3733bd6d66ebe2521@macports.org> References: <055.783192f55cd29bb3733bd6d66ebe2521@macports.org> Message-ID: <070.edfe1c47f39148de2cc6f30e897cc334@macports.org> #30365: Additional option to selfupdate required if major changes take place --------------------------+-------------------------------- Reporter: bgschaid@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.0.0 Resolution: wontfix | Keywords: Port: | --------------------------+-------------------------------- Changes (by jmroot): * status: new => closed * resolution: => wontfix Comment: It doesn't appear that there is anything we can do here. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 02:07:41 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 02:07:41 -0000 Subject: [MacPorts] #31250: Failing to install package due to sqlite insert error In-Reply-To: <058.ae5546e95f8a464e84b10486408ac5ed@macports.org> References: <058.ae5546e95f8a464e84b10486408ac5ed@macports.org> Message-ID: <073.0c4510623640a7831c3dde74f635117b@macports.org> #31250: Failing to install package due to sqlite insert error ----------------------------+-------------------------------- Reporter: anastasiosm@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.0.3 Resolution: worksforme | Keywords: Port: | ----------------------------+-------------------------------- Changes (by jmroot): * status: new => closed * resolution: => worksforme Comment: We can't reproduce the problem and so we can't so anything without more information. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 02:40:06 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 02:40:06 -0000 Subject: [MacPorts] #35093: mpkg / mdmg requires cleaning and reinstalling every time In-Reply-To: <054.116d49136aa78d7b44356a1c73cbce66@macports.org> References: <054.116d49136aa78d7b44356a1c73cbce66@macports.org> Message-ID: <069.ee467c4638e0d5491a78029af9febbf5@macports.org> #35093: mpkg / mdmg requires cleaning and reinstalling every time ------------------------+-------------------------------- Reporter: virgilg@… | Owner: macports-tickets@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: base | Version: 2.1.1 Resolution: | Keywords: Port: | ------------------------+-------------------------------- Comment (by jmroot): Could be a dupe of #34177? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 02:42:42 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 02:42:42 -0000 Subject: [MacPorts] #37867: Weird library install_names for MacPorts dylibs In-Reply-To: <047.51ee45502cd2e19b02ba2280c454ceb5@macports.org> References: <047.51ee45502cd2e19b02ba2280c454ceb5@macports.org> Message-ID: <062.598578c05402af4ce71d3fef7c55ea91@macports.org> #37867: Weird library install_names for MacPorts dylibs -------------------------+-------------------------------- Reporter: ryandesign | Owner: macports-tickets@… Type: defect | Status: closed Priority: Low | Milestone: Component: base | Version: 2.1.2 Resolution: invalid | Keywords: Port: | -------------------------+-------------------------------- Changes (by jmroot): * status: new => closed * resolution: => invalid Comment: The observation is correct, but it's not a problem, hence closing as "invalid". -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 02:56:16 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 02:56:16 -0000 Subject: [MacPorts] #39136: make test fails when run as root and creates junk file In-Reply-To: <061.14023125429fda8071227946225b36ed@macports.org> References: <061.14023125429fda8071227946225b36ed@macports.org> Message-ID: <076.72d21e844ed04922548a83ff076fe0b9@macports.org> #39136: make test fails when run as root and creates junk file ------------------------------+-------------------------------- Reporter: Peter_Dyballa@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.1.99 Resolution: fixed | Keywords: Port: | ------------------------------+-------------------------------- Changes (by jmroot): * status: new => closed * resolution: => fixed Comment: [e47109d733683df29cfefedc721b2cd052a60247/macports-base] -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 03:01:53 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 03:01:53 -0000 Subject: [MacPorts] #43238: when updating hash, port should offer recent hash set In-Reply-To: <053.04466d59f804d326ead1b6d97e73a95a@macports.org> References: <053.04466d59f804d326ead1b6d97e73a95a@macports.org> Message-ID: <068.4446818ba0d01e16d8df49b295f3d135@macports.org> #43238: when updating hash, port should offer recent hash set --------------------------+-------------------------------- Reporter: jul_bsd@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: base | Version: Resolution: fixed | Keywords: Port: | --------------------------+-------------------------------- Changes (by jmroot): * status: new => closed * resolution: => fixed Comment: [10a884930215d61938ee38fbedfaba866d20825a/macports-base] [e392f308f5c998eca053a59138cffd05ee4a7eab/macports-base] [751267a390d3076fe52067049094cb5078a4d065/macports-base] -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 03:02:08 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 03:02:08 -0000 Subject: [MacPorts] #43238: when updating hash, port should offer recent hash set In-Reply-To: <053.04466d59f804d326ead1b6d97e73a95a@macports.org> References: <053.04466d59f804d326ead1b6d97e73a95a@macports.org> Message-ID: <068.8b5b77c0a82d656ceea22dba6721b27c@macports.org> #43238: when updating hash, port should offer recent hash set --------------------------+-------------------------------- Reporter: jul_bsd@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: MacPorts 2.4.0 Component: base | Version: Resolution: fixed | Keywords: Port: | --------------------------+-------------------------------- Changes (by jmroot): * milestone: => MacPorts 2.4.0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 03:38:10 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 03:38:10 -0000 Subject: [MacPorts] #43517: deactivate phase swallows sigint In-Reply-To: <045.3ba1cbde06fb8cc0a29b071a3d32b6ea@macports.org> References: <045.3ba1cbde06fb8cc0a29b071a3d32b6ea@macports.org> Message-ID: <060.97d19de0f150005cc91f85f4370eedee@macports.org> #43517: deactivate phase swallows sigint -----------------------+------------------------ Reporter: nerdling | Owner: neverpanic Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.2.99 Resolution: | Keywords: Port: | -----------------------+------------------------ Comment (by jmroot): Likely fixed by [0ecff30a328993179b757a13830a1a5249839dd8/macports-base], please test. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 03:48:59 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 03:48:59 -0000 Subject: [MacPorts] #44749: reclaim test suite fails if not run with superuser privileges In-Reply-To: <043.e83101c238a5c3dda562a84f0d6a053d@macports.org> References: <043.e83101c238a5c3dda562a84f0d6a053d@macports.org> Message-ID: <058.1004cb8331074f0c288ddf5f7865ab97@macports.org> #44749: reclaim test suite fails if not run with superuser privileges ---------------------+---------------------------- Reporter: larryv | Owner: ksammons@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: fixed | Keywords: gsoc14-cleanup Port: | ---------------------+---------------------------- Changes (by jmroot): * status: new => closed * resolution: => fixed Comment: [b1e6fc864113ccd6a7eb2a075e9f3778dd96cef9/macports-base] -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 04:32:31 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 04:32:31 -0000 Subject: [MacPorts] #50857: Warning if launched as non root In-Reply-To: <055.7bc5435f657486591357f2454a92c4fe@macports.org> References: <055.7bc5435f657486591357f2454a92c4fe@macports.org> Message-ID: <070.9c504bbeccf0611878618e391399289c@macports.org> #50857: Warning if launched as non root --------------------------+-------------------------------- Reporter: fabrizio@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.3.4 Resolution: duplicate | Keywords: Port: | --------------------------+-------------------------------- Changes (by jmroot): * status: new => closed * resolution: => duplicate Comment: #48439 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 04:47:50 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 04:47:50 -0000 Subject: [MacPorts] #50885: `port -b` or `buildfromsource never` do not prevent local compilation if Portfile clears archive_sites In-Reply-To: <047.8bfbf2190985a1df65a88505ca6961ce@macports.org> References: <047.8bfbf2190985a1df65a88505ca6961ce@macports.org> Message-ID: <062.c806ddfae8f4d87c37f5af45971556db@macports.org> #50885: `port -b` or `buildfromsource never` do not prevent local compilation if Portfile clears archive_sites -------------------------+-------------------------------- Reporter: burner1024 | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: MacPorts 2.4.0 Component: base | Version: 2.3.4 Resolution: fixed | Keywords: Port: | -------------------------+-------------------------------- Changes (by jmroot): * status: new => closed * resolution: => fixed * milestone: => MacPorts 2.4.0 Comment: [7c20563759f967533132a3744148926efd8dd4d4/macports-base] -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 05:01:17 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 05:01:17 -0000 Subject: [MacPorts] #52217: make test fails on Snow Leopard: Total:hasGit In-Reply-To: <047.b0fcd4b2f9a9bf36091afb6ac2188b2f@macports.org> References: <047.b0fcd4b2f9a9bf36091afb6ac2188b2f@macports.org> Message-ID: <062.659c8ec0f0eba8a538c2e94083291306@macports.org> #52217: make test fails on Snow Leopard: Total:hasGit -------------------------+-------------------------------- Reporter: ryandesign | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts 2.4.0 Component: base | Version: 2.3.99 Resolution: | Keywords: snowleopard Port: | -------------------------+-------------------------------- Changes (by jmroot): * milestone: => MacPorts 2.4.0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 05:04:28 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 05:04:28 -0000 Subject: [MacPorts] #52219: make test: error: failed to test trace: command execution failed In-Reply-To: <047.6c42d0ea1b9c6f860a585c1101c6e263@macports.org> References: <047.6c42d0ea1b9c6f860a585c1101c6e263@macports.org> Message-ID: <062.e4770a497a8c9cff9cec72838daa8463@macports.org> #52219: make test: error: failed to test trace: command execution failed -------------------------+-------------------------------- Reporter: ryandesign | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: fixed | Keywords: elcapitan sierra Port: | -------------------------+-------------------------------- Changes (by jmroot): * status: new => closed * cc: raimue (added) * resolution: => fixed Comment: [eb973fb6b7d387e539dcc614046ac619346c397d/macports-base] -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 05:13:14 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 05:13:14 -0000 Subject: [MacPorts] #53007: neomutt @20161014 add slang variant In-Reply-To: <047.2da557977b5327e096a5410984aa70f9@macports.org> References: <047.2da557977b5327e096a5410984aa70f9@macports.org> Message-ID: <062.6001e19f0acd9914cac730651988e857@macports.org> #53007: neomutt @20161014 add slang variant --------------------------+------------------------------------------------ Reporter: slaptijack | Owner: Leonardo Brondani Schenkel Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: haspatch Port: neomutt | --------------------------+------------------------------------------------ Changes (by Leonardo Brondani Schenkel ): * owner: => Leonardo Brondani Schenkel * status: new => closed * resolution: => fixed Comment: In [changeset:"291dc017758259cefa4e34af759a533ff557a6bf/macports-ports" 291dc017/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="291dc017758259cefa4e34af759a533ff557a6bf" neomutt: add +slang variant Closes: https://trac.macports.org/ticket/53007 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 05:23:03 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 05:23:03 -0000 Subject: [MacPorts] #10226: BUG: port command can't be interrupted cleanly - creates database inconsistency In-Reply-To: <055.519794da574eb229c316da95bb475fea@macports.org> References: <055.519794da574eb229c316da95bb475fea@macports.org> Message-ID: <070.340c50f5eb532a645c9b0d8a2e6addfc@macports.org> #10226: BUG: port command can't be interrupted cleanly - creates database inconsistency ------------------------+-------------------------------- Reporter: stephen@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: High | Milestone: MacPorts 2.4.0 Component: base | Version: Resolution: fixed | Keywords: Port: | ------------------------+-------------------------------- Changes (by jmroot): * milestone: MacPorts Future => MacPorts 2.4.0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 05:28:27 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 05:28:27 -0000 Subject: [MacPorts] #12429: port cannot handle spaces in various variables In-Reply-To: <053.ee92c7aee471683fa1f5426687802118@macports.org> References: <053.ee92c7aee471683fa1f5426687802118@macports.org> Message-ID: <068.0bb0ac23d9dde2f642a33b4e4e4cbea5@macports.org> #12429: port cannot handle spaces in various variables ---------------------+---------------------------- Reporter: nox@… | Owner: larryv Type: defect | Status: closed Priority: High | Milestone: MacPorts 2.3.0 Component: base | Version: 1.7.0 Resolution: fixed | Keywords: Port: | ---------------------+---------------------------- Changes (by jmroot): * milestone: MacPorts Future => MacPorts 2.3.0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 05:30:24 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 05:30:24 -0000 Subject: [MacPorts] #34562: CC, CXX, OBJC, LDFLAGS, CFLAGS, CXXFLAGS, OBJCFLAGS should be set during destroot In-Reply-To: <044.b67f1c1b033667953156e268b80256dd@macports.org> References: <044.b67f1c1b033667953156e268b80256dd@macports.org> Message-ID: <059.9b35cb265ecbccf575781ffc5c73fb38@macports.org> #34562: CC, CXX, OBJC, LDFLAGS, CFLAGS, CXXFLAGS, OBJCFLAGS should be set during destroot ----------------------+-------------------------------- Reporter: watsodw | Owner: macports-tickets@… Type: defect | Status: closed Priority: High | Milestone: Component: ports | Version: 2.1.1 Resolution: fixed | Keywords: Port: | ----------------------+-------------------------------- Changes (by jmroot): * component: base => ports * milestone: MacPorts Future => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 05:48:24 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 05:48:24 -0000 Subject: [MacPorts] #12306: BUG: "variant foo bar { ... }" constructs fail at package archival time In-Reply-To: <054.52660baf218b4d70f97a494cefdc7b92@macports.org> References: <054.52660baf218b4d70f97a494cefdc7b92@macports.org> Message-ID: <069.d8b6369639c736f33221d99bff7e4a94@macports.org> #12306: BUG: "variant foo bar { ... }" constructs fail at package archival time ---------------------+-------------------------------- Reporter: jmpp@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: MacPorts 2.4.0 Component: base | Version: 1.5.0 Resolution: fixed | Keywords: Port: | ---------------------+-------------------------------- Changes (by jmroot): * milestone: MacPorts Future => MacPorts 2.4.0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 05:49:43 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 05:49:43 -0000 Subject: [MacPorts] #13707: MacPorts installer should warn if /opt is not a directory In-Reply-To: <063.2ef044c392c0daca7eb8ae1cfe4c01fb@macports.org> References: <063.2ef044c392c0daca7eb8ae1cfe4c01fb@macports.org> Message-ID: <078.311b6c17623ff06df009d3e0c4d5fee0@macports.org> #13707: MacPorts installer should warn if /opt is not a directory ---------------------------------+-------------------------------- Reporter: martin.streicher@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 1.6.0 Resolution: worksforme | Keywords: installer Port: | ---------------------------------+-------------------------------- Changes (by jmroot): * milestone: MacPorts Future => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 05:50:24 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 05:50:24 -0000 Subject: [MacPorts] #14139: xinstall needs to support recursion In-Reply-To: <056.de0f204ed7427a55e33e0db59eae7f2a@macports.org> References: <056.de0f204ed7427a55e33e0db59eae7f2a@macports.org> Message-ID: <071.7597109c3214dce703b805a0ce904a65@macports.org> #14139: xinstall needs to support recursion --------------------------+-------------------------------- Reporter: rhwood@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: base | Version: 1.7.0 Resolution: wontfix | Keywords: Port: | --------------------------+-------------------------------- Changes (by jmroot): * milestone: MacPorts Future => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 05:51:01 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 05:51:01 -0000 Subject: [MacPorts] #14223: port upgrade overwrites the user's launchd plists In-Reply-To: <056.aeb767472343144b3076c3d6b41bf572@macports.org> References: <056.aeb767472343144b3076c3d6b41bf572@macports.org> Message-ID: <071.dfabb0cb080b52317bd5dee7c2cd6a94@macports.org> #14223: port upgrade overwrites the user's launchd plists ------------------------+-------------------------------- Reporter: vinc17@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 1.6.0 Resolution: duplicate | Keywords: Port: | ------------------------+-------------------------------- Changes (by jmroot): * milestone: MacPorts Future => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 05:51:52 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 05:51:52 -0000 Subject: [MacPorts] #14774: launchctl load instructions incomplete In-Reply-To: <044.7d685d40033e2df9a0e36d3e69cab9d0@macports.org> References: <044.7d685d40033e2df9a0e36d3e69cab9d0@macports.org> Message-ID: <059.8c268d49e593913e54b0338e17f43189@macports.org> #14774: launchctl load instructions incomplete ------------------------+----------------------------------- Reporter: dershow | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 1.6.0 Resolution: duplicate | Keywords: dbus update launchctl Port: | ------------------------+----------------------------------- Changes (by jmroot): * milestone: MacPorts Future => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 05:53:42 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 05:53:42 -0000 Subject: [MacPorts] #15467: RFE: More helpful strings for 'port help' In-Reply-To: <043.c6c2e0befeb0037ef450db86f58ab15e@macports.org> References: <043.c6c2e0befeb0037ef450db86f58ab15e@macports.org> Message-ID: <058.168f716bb832fb2d7dcc24d7296134db@macports.org> #15467: RFE: More helpful strings for 'port help' --------------------------+----------------------------- Reporter: raimue | Owner: neverpanic Type: enhancement | Status: closed Priority: Normal | Milestone: MacPorts 2.4.0 Component: base | Version: 1.7.0 Resolution: fixed | Keywords: bite-sized help Port: | --------------------------+----------------------------- Changes (by jmroot): * milestone: MacPorts Future => MacPorts 2.4.0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 05:54:20 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 05:54:20 -0000 Subject: [MacPorts] #15772: ccache support sets incompatible compiler In-Reply-To: <057.5a5263f7bd61c17c1a52947600c272af@macports.org> References: <057.5a5263f7bd61c17c1a52947600c272af@macports.org> Message-ID: <072.87fa47a25c22a0a9e4dfbcb6d0476d2c@macports.org> #15772: ccache support sets incompatible compiler ------------------------+-------------------------------- Reporter: landonf@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 1.6.0 Resolution: wontfix | Keywords: Port: | ------------------------+-------------------------------- Changes (by jmroot): * milestone: MacPorts Future => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 05:57:23 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 05:57:23 -0000 Subject: [MacPorts] #17041: meaning of livecheck results should be made clearer In-Reply-To: <044.d0b175874865a95ebeada55384b0d1e0@macports.org> References: <044.d0b175874865a95ebeada55384b0d1e0@macports.org> Message-ID: <059.60b54b98d44a5568688a54e431f8e03f@macports.org> #17041: meaning of livecheck results should be made clearer --------------------------+-------------------------------- Reporter: dbevans | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: MacPorts 2.3.5 Component: base | Version: 1.7.0 Resolution: fixed | Keywords: Port: | --------------------------+-------------------------------- Changes (by jmroot): * milestone: MacPorts Future => MacPorts 2.3.5 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 06:01:38 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 06:01:38 -0000 Subject: [MacPorts] #18133: /opt/local/bin/port documentation problems In-Reply-To: <060.18d48dedef0ed4c890e4569a9c789b85@macports.org> References: <060.18d48dedef0ed4c890e4569a9c789b85@macports.org> Message-ID: <075.106fca46c224c6f9b71c038eaef12d95@macports.org> #18133: /opt/local/bin/port documentation problems -------------------------------+-------------------------------- Reporter: macosforge.org@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: MacPorts 2.4.0 Component: base | Version: 1.7.0 Resolution: fixed | Keywords: help man Port: | -------------------------------+-------------------------------- Changes (by jmroot): * milestone: MacPorts Future => MacPorts 2.4.0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 06:02:23 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 06:02:23 -0000 Subject: [MacPorts] #19590: selfupdate fails with "unknown group 501" In-Reply-To: <059.5882d5fa8734c690f25fedac085baf6b@macports.org> References: <059.5882d5fa8734c690f25fedac085baf6b@macports.org> Message-ID: <074.fb28df1a8795563c26d3a0f695f365a5@macports.org> #19590: selfupdate fails with "unknown group 501" ---------------------------+-------------------------------- Reporter: ali_kaylan@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 1.7.0 Resolution: worksforme | Keywords: Port: | ---------------------------+-------------------------------- Changes (by jmroot): * milestone: MacPorts Future => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 06:02:54 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 06:02:54 -0000 Subject: [MacPorts] #23280: base should auto-create share/doc/${name} and share/examples/${name} in destroot In-Reply-To: <047.fe596c683d785a5f0e9f7619e28eb086@macports.org> References: <047.fe596c683d785a5f0e9f7619e28eb086@macports.org> Message-ID: <062.1ee8625868887dd25b113a0aac6b3f6e@macports.org> #23280: base should auto-create share/doc/${name} and share/examples/${name} in destroot --------------------------+-------------------------------- Reporter: ryandesign | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: base | Version: 1.8.2 Resolution: wontfix | Keywords: Port: | --------------------------+-------------------------------- Changes (by jmroot): * milestone: MacPorts Future => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 06:03:30 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 06:03:30 -0000 Subject: [MacPorts] #24507: display all relevant notes after install action completes In-Reply-To: <046.82af7f468f5890731df1d4be4f17cd2a@macports.org> References: <046.82af7f468f5890731df1d4be4f17cd2a@macports.org> Message-ID: <061.2cea1a978d264cca4b30e86412c056e3@macports.org> #24507: display all relevant notes after install action completes --------------------------+---------------------------- Reporter: keybounce | Owner: neverpanic Type: enhancement | Status: closed Priority: Normal | Milestone: MacPorts 2.4.0 Component: base | Version: 1.8.2 Resolution: fixed | Keywords: Port: | --------------------------+---------------------------- Changes (by jmroot): * milestone: MacPorts Future => MacPorts 2.4.0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 06:05:51 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 06:05:51 -0000 Subject: [MacPorts] #53016: octave @4.2.0_1 build failure Message-ID: <047.6f5926dce6c29e418e3b19edf4dea9f0@macports.org> #53016: octave @4.2.0_1 build failure ------------------------+--------------------------------- Reporter: ryandesign | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.99 Keywords: | Port: octave ------------------------+--------------------------------- {{{ Undefined symbols for architecture x86_64: "___addtf3", referenced from: __gfortran_random_r16 in libgfortran.a(random.o) __gfortran_arandom_r16 in libgfortran.a(random.o) "___divtf3", referenced from: _calculate_exp_16 in libgfortran.a(write.o) _write_float in libgfortran.a(write.o) "___eqtf2", referenced from: _write_float in libgfortran.a(write.o) "___floatunditf", referenced from: __gfortran_random_r16 in libgfortran.a(random.o) __gfortran_arandom_r16 in libgfortran.a(random.o) "___getf2", referenced from: _write_float in libgfortran.a(write.o) "___gttf2", referenced from: _write_float in libgfortran.a(write.o) "___lttf2", referenced from: _write_float in libgfortran.a(write.o) "___multf3", referenced from: _calculate_exp_16 in libgfortran.a(write.o) _write_float in libgfortran.a(write.o) __gfortran_random_r16 in libgfortran.a(random.o) __gfortran_arandom_r16 in libgfortran.a(random.o) "___subtf3", referenced from: _write_float in libgfortran.a(write.o) "___unordtf2", referenced from: _write_float in libgfortran.a(write.o) ld: symbol(s) not found for architecture x86_64 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 06:06:00 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 06:06:00 -0000 Subject: [MacPorts] #53016: octave @4.2.0_1 build failure In-Reply-To: <047.6f5926dce6c29e418e3b19edf4dea9f0@macports.org> References: <047.6f5926dce6c29e418e3b19edf4dea9f0@macports.org> Message-ID: <062.7f7c22403ebf8f6b277ca05085b299ab@macports.org> #53016: octave @4.2.0_1 build failure -------------------------+--------------------------------- Reporter: ryandesign | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.99 Resolution: | Keywords: Port: octave | -------------------------+--------------------------------- Changes (by ryandesign): * Attachment "main.log.bz2" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 06:07:01 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 06:07:01 -0000 Subject: [MacPorts] #36054: Feature request: reload action In-Reply-To: <057.d304e43ec7cf0e46e68e908776590f37@macports.org> References: <057.d304e43ec7cf0e46e68e908776590f37@macports.org> Message-ID: <072.c436b4f9d10278928bb7b9b9d99ecf7d@macports.org> #36054: Feature request: reload action ---------------------------+-------------------------------- Reporter: mailtoarlo@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: MacPorts 2.4.0 Component: base | Version: Resolution: fixed | Keywords: Port: | ---------------------------+-------------------------------- Changes (by jmroot): * milestone: MacPorts Future => MacPorts 2.4.0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 06:07:33 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 06:07:33 -0000 Subject: [MacPorts] #37949: rev-upgrade report does not explain missing slices In-Reply-To: <045.77bb9202c11357cf87b9ab39dabdb79a@macports.org> References: <045.77bb9202c11357cf87b9ab39dabdb79a@macports.org> Message-ID: <060.d197262f5341238277bce411883d88c9@macports.org> #37949: rev-upgrade report does not explain missing slices -----------------------+-------------------------------- Reporter: jeremyhu | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.1.99 Resolution: wontfix | Keywords: rev-upgrade Port: | -----------------------+-------------------------------- Changes (by jmroot): * milestone: MacPorts Future => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 06:08:03 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 06:08:03 -0000 Subject: [MacPorts] #43388: Can't interrupt while waiting for registry lock In-Reply-To: <047.e9a85480a179a097cadc7f16e73ddc36@macports.org> References: <047.e9a85480a179a097cadc7f16e73ddc36@macports.org> Message-ID: <062.38a76ff29c51ba1b817983bfbb5faf21@macports.org> #43388: Can't interrupt while waiting for registry lock -------------------------+------------------------ Reporter: ryandesign | Owner: neverpanic Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.2.99 Resolution: fixed | Keywords: Port: | -------------------------+------------------------ Changes (by jmroot): * milestone: MacPorts Future => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 06:32:37 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 06:32:37 -0000 Subject: [MacPorts] #53017: kerberos5 fails to build on Yosemite with libressl Message-ID: <045.2e6d5c80e4930d3d8f0c88d93b24a25b@macports.org> #53017: kerberos5 fails to build on Yosemite with libressl ----------------------+----------------------- Reporter: bK4gYuRo | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: kerberos5 ----------------------+----------------------- kerberos5 @1.15_0 fails to build on Yosemite (10.10.5) with libressl @2.4.3_0. :info:build Undefined symbols for architecture x86_64: :info:build "_HMAC_CTX_new", referenced from: :info:build _krb5int_hmac_keyblock in hmac.so :info:build "_EVP_MD_CTX_new", referenced from: :info:build _hash_evp in hash_evp.so :info:build _k5_sha256 in sha256.so :info:build "_HMAC_CTX_free", referenced from: :info:build _krb5int_hmac_keyblock in hmac.so :info:build "_EVP_MD_CTX_free", referenced from: :info:build _hash_evp in hash_evp.so :info:build _k5_sha256 in sha256.so :info:build ld: symbol(s) not found for architecture x86_64 I am attaching the full build log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 06:34:55 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 06:34:55 -0000 Subject: [MacPorts] #53017: kerberos5 fails to build on Yosemite with libressl In-Reply-To: <045.2e6d5c80e4930d3d8f0c88d93b24a25b@macports.org> References: <045.2e6d5c80e4930d3d8f0c88d93b24a25b@macports.org> Message-ID: <060.1992318054b1064b5d4c2fa45cb36607@macports.org> #53017: kerberos5 fails to build on Yosemite with libressl ------------------------+------------------- Reporter: bK4gYuRo | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: kerberos5 | ------------------------+------------------- Changes (by bK4gYuRo): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 09:13:39 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 09:13:39 -0000 Subject: [MacPorts] #44240: tracelib: resource forks not handled correctly In-Reply-To: <042.13b12bb6f0b9f89896f14df1f447bbfd@macports.org> References: <042.13b12bb6f0b9f89896f14df1f447bbfd@macports.org> Message-ID: <057.0268d602bd1d31f2a11ee5534e97375b@macports.org> #44240: tracelib: resource forks not handled correctly ---------------------+-------------------------------- Reporter: Ionic | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: MacPorts 2.4.0 Component: base | Version: 2.3.99 Resolution: fixed | Keywords: tracemode Port: | ---------------------+-------------------------------- Changes (by jmroot): * milestone: MacPorts Future => MacPorts 2.4.0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 09:21:45 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 09:21:45 -0000 Subject: [MacPorts] #44504: rev-upgrade: print a different message if a library exists, but has a bad install name In-Reply-To: <057.74ec52066242bfd8df7b07e75e48b9eb@macports.org> References: <057.74ec52066242bfd8df7b07e75e48b9eb@macports.org> Message-ID: <072.df0981a4aca51d0eb50f080be581af13@macports.org> #44504: rev-upgrade: print a different message if a library exists, but has a bad install name --------------------------+---------------------------- Reporter: egall@… | Owner: neverpanic Type: enhancement | Status: closed Priority: Normal | Milestone: MacPorts 2.4.0 Component: base | Version: 2.3.1 Resolution: fixed | Keywords: rev-upgrade Port: | --------------------------+---------------------------- Changes (by jmroot): * milestone: MacPorts Future => MacPorts 2.4.0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 09:22:24 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 09:22:24 -0000 Subject: [MacPorts] #44530: help for most actions has disappeared In-Reply-To: <043.5629b176a13923f3b021f99d133789dc@macports.org> References: <043.5629b176a13923f3b021f99d133789dc@macports.org> Message-ID: <058.2b8cb28d68110368ed0c46f267285e34@macports.org> #44530: help for most actions has disappeared ---------------------+------------------------ Reporter: jmroot | Owner: neverpanic Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: fixed | Keywords: Port: | ---------------------+------------------------ Changes (by jmroot): * milestone: MacPorts Future => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 09:22:49 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 09:22:49 -0000 Subject: [MacPorts] #44629: notes printed in random order In-Reply-To: <047.af04771dffc66fb546d76294300171a8@macports.org> References: <047.af04771dffc66fb546d76294300171a8@macports.org> Message-ID: <062.d9a891348c52b4cfd2bde1f3a5d1e3c6@macports.org> #44629: notes printed in random order -------------------------+-------------------------------- Reporter: ryandesign | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: fixed | Keywords: Port: | -------------------------+-------------------------------- Changes (by jmroot): * milestone: MacPorts Future => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 09:33:31 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 09:33:31 -0000 Subject: [MacPorts] #44814: portindex does not respond to Control-C In-Reply-To: <043.d4e93d914a85b06570021872fc52f7a0@macports.org> References: <043.d4e93d914a85b06570021872fc52f7a0@macports.org> Message-ID: <058.d558d6c515510fa501c9b69846fe86a2@macports.org> #44814: portindex does not respond to Control-C ---------------------+-------------------------------- Reporter: larryv | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: fixed | Keywords: Port: | ---------------------+-------------------------------- Changes (by jmroot): * milestone: MacPorts Future => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 09:46:19 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 09:46:19 -0000 Subject: [MacPorts] #45434: base should create var/log, var/run and other common directories In-Reply-To: <054.a835272c128ef07c60a5497276bbf390@macports.org> References: <054.a835272c128ef07c60a5497276bbf390@macports.org> Message-ID: <069.44d39b54de12eb61b3ac6b27aed51081@macports.org> #45434: base should create var/log, var/run and other common directories --------------------------+-------------------------------- Reporter: p.perroud@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: MacPorts 2.3.5 Component: base | Version: Resolution: fixed | Keywords: haspatch Port: | --------------------------+-------------------------------- Changes (by jmroot): * milestone: MacPorts Future => MacPorts 2.3.5 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 09:47:54 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 09:47:54 -0000 Subject: [MacPorts] #46733: Multiple definitons of flock TCL command cause problems, e.g., with restore_ports.tcl In-Reply-To: <050.4973af662853965c193d5cae5288036e@macports.org> References: <050.4973af662853965c193d5cae5288036e@macports.org> Message-ID: <065.c0208f3c12df46d6131dcf960c4e7edd@macports.org> #46733: Multiple definitons of flock TCL command cause problems, e.g., with restore_ports.tcl ---------------------+-------------------------------- Reporter: mta@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: fixed | Keywords: Port: | ---------------------+-------------------------------- Changes (by jmroot): * milestone: MacPorts Future => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 09:52:39 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 09:52:39 -0000 Subject: [MacPorts] #47688: Automatically create ${prefix}/share/doc (should be part of prefix.mtree.in) In-Reply-To: <047.130915a8e1c258c2cbb342eb0367391c@macports.org> References: <047.130915a8e1c258c2cbb342eb0367391c@macports.org> Message-ID: <062.2aad928e6e015ddbede88c3a5a90a94e@macports.org> #47688: Automatically create ${prefix}/share/doc (should be part of prefix.mtree.in) -------------------------+---------------------------- Reporter: ryandesign | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: MacPorts 2.3.5 Component: base | Version: 2.3.3 Resolution: fixed | Keywords: Port: | -------------------------+---------------------------- Changes (by jmroot): * milestone: MacPorts Future => MacPorts 2.3.5 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 10:01:19 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 10:01:19 -0000 Subject: [MacPorts] #48406: Error spew when cancelling uninstallation that is blocked by another task In-Reply-To: <047.bf41e282d944d7879e170538ca91ebd2@macports.org> References: <047.bf41e282d944d7879e170538ca91ebd2@macports.org> Message-ID: <062.65a37053d3df374022b5efdcca303ad0@macports.org> #48406: Error spew when cancelling uninstallation that is blocked by another task -------------------------+-------------------------------- Reporter: ryandesign | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: fixed | Keywords: Port: | -------------------------+-------------------------------- Changes (by jmroot): * milestone: MacPorts Future => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 10:06:45 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 10:06:45 -0000 Subject: [MacPorts] #53018: error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but "10.11" during configure Message-ID: <042.20cc68d2a5b85e3ef4bb92ae1dd59d73@macports.org> #53018: error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but "10.11" during configure --------------------+----------------------- Reporter: yabba | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: mercurial --------------------+----------------------- port update mercurial and install mercurial are not working. I have MacOSX 10.11.6. I'll attach the log. {{{ sudo port -v install mercurial ---> Computing dependencies for mercurial. ---> Fetching distfiles for mercurial ---> 4.0.1.tar.gz does not exist in /opt/local/var/macports/distfiles/mercurial ---> Attempting to fetch 4.0.1.tar.gz from https://bitbucket.org/seanfarley/mercurial/get % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 4457k 100 4457k 0 0 395k 0 0:00:11 0:00:11 --:--:-- 845k ---> Verifying checksums for mercurial ---> Checksumming 4.0.1.tar.gz ---> Extracting mercurial ---> Extracting 4.0.1.tar.gz ---> Applying patches to mercurial ---> Applying patch-setup.py.diff patching file setup.py Hunk #1 succeeded at 657 with fuzz 2 (offset 187 lines). ---> Configuring mercurial ---> Building mercurial make: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_mercurial/mercurial/work/4.0.1' /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 setup.py build /Applications/Xcode.app/Contents/Developer/usr/bin/make -C doc make[1]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_mercurial/mercurial/work/4.0.1/doc' /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 gendoc.py hg-ssh.8 > hg-ssh.8.txt.tmp mv hg-ssh.8.txt.tmp hg-ssh.8.txt /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 gendoc.py hg-ssh.8.gendoc > hg-ssh.8.gendoc.txt.tmp mv hg-ssh.8.gendoc.txt.tmp hg-ssh.8.gendoc.txt /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 gendoc.py common > common.txt.tmp mv common.txt.tmp common.txt running build running build_mo creating mercurial/locale creating mercurial/locale/da creating mercurial/locale/da/LC_MESSAGES generating mercurial/locale/da/LC_MESSAGES/hg.mo from i18n/da.po msgfmt -v -o mercurial/locale/da/LC_MESSAGES/hg.mo i18n/da.po -c error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but "10.11" during configure /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 gendoc.py hg.1 > hg.1.txt.tmp make: *** [build] Error 1 make: *** Waiting for unfinished jobs.... /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 gendoc.py hg.1.gendoc > hg.1.gendoc.txt.tmp mv hg.1.txt.tmp hg.1.txt /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 gendoc.py hgignore.5 > hgignore.5.txt.tmp mv hgignore.5.txt.tmp hgignore.5.txt /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 gendoc.py hgignore.5.gendoc > hgignore.5.gendoc.txt.tmp mv hgignore.5.gendoc.txt.tmp hgignore.5.gendoc.txt /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 gendoc.py hgrc.5 > hgrc.5.txt.tmp mv hgrc.5.txt.tmp hgrc.5.txt /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 gendoc.py hgrc.5.gendoc > hgrc.5.gendoc.txt.tmp mv hgrc.5.gendoc.txt.tmp hgrc.5.gendoc.txt /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 runrst html --halt warning \ --link-stylesheet --stylesheet-path style.css hg-ssh.8.txt hg- ssh.8.html mv hg.1.gendoc.txt.tmp hg.1.gendoc.txt /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 runrst html --halt warning \ --link-stylesheet --stylesheet-path style.css hgignore.5.txt hgignore.5.html /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 runrst html --halt warning \ --link-stylesheet --stylesheet-path style.css hgrc.5.txt hgrc.5.html /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 runrst hgmanpage --halt warning \ --strip-elements-with-class htmlonly hg-ssh.8.txt hg-ssh.8 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 runrst hgmanpage --halt warning \ --strip-elements-with-class htmlonly hg.1.txt hg.1 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 runrst hgmanpage --halt warning \ --strip-elements-with-class htmlonly hgignore.5.txt hgignore.5 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 runrst hgmanpage --halt warning \ --strip-elements-with-class htmlonly hgrc.5.txt hgrc.5 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 runrst html --halt warning \ --link-stylesheet --stylesheet-path style.css hg.1.txt hg.1.html make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_mercurial/mercurial/work/4.0.1/doc' make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_mercurial/mercurial/work/4.0.1' Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_mercurial/mercurial/work/4.0.1" && make -j2 -w all PYTHON=/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 Exit code: 2 Error: org.macports.build for port mercurial returned: command execution failed Warning: targets not executed for mercurial: org.macports.activate org.macports.build org.macports.destroot org.macports.install Please see the log file for port mercurial for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_mercurial/mercurial/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port mercurial failed }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 10:07:25 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 10:07:25 -0000 Subject: [MacPorts] #53018: error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but "10.11" during configure In-Reply-To: <042.20cc68d2a5b85e3ef4bb92ae1dd59d73@macports.org> References: <042.20cc68d2a5b85e3ef4bb92ae1dd59d73@macports.org> Message-ID: <057.d5ab04b2fe6bb471171827bc79341c0c@macports.org> #53018: error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but "10.11" during configure ------------------------+------------------- Reporter: yabba | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: mercurial | ------------------------+------------------- Changes (by yabba): * Attachment "main.log" added. /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_mercurial/mercurial/main.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 11:09:23 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 11:09:23 -0000 Subject: [MacPorts] #53018: error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but "10.11" during configure In-Reply-To: <042.20cc68d2a5b85e3ef4bb92ae1dd59d73@macports.org> References: <042.20cc68d2a5b85e3ef4bb92ae1dd59d73@macports.org> Message-ID: <057.77717de0dab6aa06aa5ed5b38a33a191@macports.org> #53018: error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but "10.11" during configure ------------------------+------------------------ Reporter: yabba | Owner: seanfarley Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: mercurial | ------------------------+------------------------ Changes (by raimue): * owner: => seanfarley * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 11:14:03 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 11:14:03 -0000 Subject: [MacPorts] #52928: `port info --line` produces multi-line output In-Reply-To: <043.010eaabc70ccc94b26fc3a4b56ff3544@macports.org> References: <043.010eaabc70ccc94b26fc3a4b56ff3544@macports.org> Message-ID: <058.f70b98e581191f1d726885152f9fd958@macports.org> #52928: `port info --line` produces multi-line output ---------------------+-------------------------------- Reporter: raimue | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: MacPorts 2.3.6 Component: base | Version: 2.3.5 Resolution: fixed | Keywords: Port: | ---------------------+-------------------------------- Changes (by raimue): * status: new => closed * resolution: => fixed Comment: In [changeset:"ba2002cbb24a451ce9bbd50256102bc73bf27bc3/macports-base" ba2002c/macports-base]: {{{ #!ConfigurableCommitTicketReference repository="macports-base" revision="ba2002cbb24a451ce9bbd50256102bc73bf27bc3" port info: Re-implement broken subfield separators The subfield_sep variable was not used anymore after 30c27d5, replace it with specific separators for the different output modes. Closes: https://trac.macports.org/ticket/52928 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 11:14:03 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 11:14:03 -0000 Subject: [MacPorts] #52928: `port info --line` produces multi-line output In-Reply-To: <043.010eaabc70ccc94b26fc3a4b56ff3544@macports.org> References: <043.010eaabc70ccc94b26fc3a4b56ff3544@macports.org> Message-ID: <058.172d3820ee84bb58f1ee3b60e10094c5@macports.org> #52928: `port info --line` produces multi-line output ---------------------+-------------------------------- Reporter: raimue | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: MacPorts 2.3.6 Component: base | Version: 2.3.5 Resolution: fixed | Keywords: Port: | ---------------------+-------------------------------- Comment (by raimue): In [changeset:"3f372a57b4066ad32b75b6fe4a0995c89e07ebcd/macports-base" 3f372a5/macports-base]: {{{ #!ConfigurableCommitTicketReference repository="macports-base" revision="3f372a57b4066ad32b75b6fe4a0995c89e07ebcd" port info: Print subfield labels only for --pretty See: https://trac.macports.org/ticket/52928 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 11:14:03 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 11:14:03 -0000 Subject: [MacPorts] #52928: `port info --line` produces multi-line output In-Reply-To: <043.010eaabc70ccc94b26fc3a4b56ff3544@macports.org> References: <043.010eaabc70ccc94b26fc3a4b56ff3544@macports.org> Message-ID: <058.417b2fff5f9bd00fceb90d30e0d82d94@macports.org> #52928: `port info --line` produces multi-line output ---------------------+-------------------------------- Reporter: raimue | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: MacPorts 2.3.6 Component: base | Version: 2.3.5 Resolution: fixed | Keywords: Port: | ---------------------+-------------------------------- Comment (by raimue): In [changeset:"b75ba554feeedd6247fdf89adb02f82afbf78685/macports-base" b75ba55/macports-base]: {{{ #!ConfigurableCommitTicketReference repository="macports-base" revision="b75ba554feeedd6247fdf89adb02f82afbf78685" port info: Flatten long_description See: https://trac.macports.org/ticket/52928#comment:3 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 12:08:48 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 12:08:48 -0000 Subject: [MacPorts] #50444: base: "port log" does not show full line of new checksums In-Reply-To: <045.c1b8e6a496302f868554115646e1d84f@macports.org> References: <045.c1b8e6a496302f868554115646e1d84f@macports.org> Message-ID: <060.6226e79fa2b7104f8719e0c06d4ebcda@macports.org> #50444: base: "port log" does not show full line of new checksums -----------------------+-------------------------------- Reporter: dstrubbe | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: MacPorts 2.4.0 Component: base | Version: 2.3.4 Resolution: fixed | Keywords: Port: | -----------------------+-------------------------------- Changes (by jmroot): * milestone: MacPorts Future => MacPorts 2.4.0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 12:12:16 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 12:12:16 -0000 Subject: [MacPorts] #43552: "Error rebuilding $portname" terminates without grace In-Reply-To: <051.6d880631ef8551d5ab40cc6e3bec1ff2@macports.org> References: <051.6d880631ef8551d5ab40cc6e3bec1ff2@macports.org> Message-ID: <066.d3213fb5a2a11129e724980679eb18f9@macports.org> #43552: "Error rebuilding $portname" terminates without grace ---------------------+---------------------------- Reporter: mp@… | Owner: neverpanic Type: defect | Status: closed Priority: Low | Milestone: MacPorts 2.4.0 Component: base | Version: 2.2.1 Resolution: fixed | Keywords: rev-upgrade Port: | ---------------------+---------------------------- Changes (by jmroot): * milestone: MacPorts Future => MacPorts 2.4.0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 12:18:16 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 12:18:16 -0000 Subject: [MacPorts] #48799: Backporting to NEXTSTEP 3.3 In-Reply-To: <051.4fbc5d77617279895f317c8d40f69498@macports.org> References: <051.4fbc5d77617279895f317c8d40f69498@macports.org> Message-ID: <066.a7bdb2cb659fe34ba9674a6629226dbe@macports.org> #48799: Backporting to NEXTSTEP 3.3 --------------------------+-------------------------------- Reporter: eike@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Low | Milestone: Component: base | Version: 2.3.3 Resolution: wontfix | Keywords: Port: | --------------------------+-------------------------------- Changes (by jmroot): * milestone: MacPorts Future => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 12:20:43 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 12:20:43 -0000 Subject: [MacPorts] #47442: port: new action_environment and/or environment mode In-Reply-To: <044.626b6379b73279325e8f45b2a081bbaf@macports.org> References: <044.626b6379b73279325e8f45b2a081bbaf@macports.org> Message-ID: <059.71ad5e1611d7af5e2bbf5becd5fa7ee7@macports.org> #47442: port: new action_environment and/or environment mode --------------------------+-------------------------------- Reporter: pixilla | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.3 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by jmroot): Dupe of #33629? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 12:58:51 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 12:58:51 -0000 Subject: [MacPorts] #47442: port: new action_environment and/or environment mode In-Reply-To: <044.626b6379b73279325e8f45b2a081bbaf@macports.org> References: <044.626b6379b73279325e8f45b2a081bbaf@macports.org> Message-ID: <059.7de4f5677090897db036e6e6c4d225b7@macports.org> #47442: port: new action_environment and/or environment mode --------------------------+-------------------------------- Reporter: pixilla | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.3 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by RJVB): Replying to [comment:4 jmroot]: > Dupe of #33629? In spirit; judging from the patchfiles Bradley's proposal is a less elaborate implementation. It's not impossible though that he provided me with the patch attached here. {{{ > port -e ---> /opt/local/etc/macports/macports.conf: sandbox_enable: no ---> /opt/local/etc/macports/macports.conf: place_worksymlink: no ---> /opt/local/etc/macports/macports.conf: prefix: /opt/local ---> /opt/local/etc/macports/macports.conf: macportsuser: bertin ---> /opt/local/etc/macports/macports.conf: portdbpath: /opt/local/var/macports ---> /opt/local/etc/macports/macports.conf: binpath: /opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin ---> /opt/local/etc/macports/macports.conf: applications_dir: /Applications/MacPorts ---> /opt/local/etc/macports/macports.conf: frameworks_dir: /opt/local/Library/Frameworks ---> /opt/local/etc/macports/macports.conf: sources_conf: /opt/local/etc/macports/sources.conf ---> /opt/local/etc/macports/macports.conf: variants_conf: /opt/local/etc/macports/variants.conf ---> /opt/local/etc/macports/macports.conf: portarchivetype: txz ---> /opt/local/etc/macports/macports.conf: universal_archs: i386 x86_64 ---> /opt/local/etc/macports/macports.conf: configurepipe: no ---> /opt/local/etc/macports/macports.conf: buildmakejobs: 4 ---> /opt/local/etc/macports/macports.conf: portautoclean: yes ---> /opt/local/etc/macports/macports.conf: keeplogs: no ---> /opt/local/etc/macports/macports.conf: extra_env: MACPORTS_COMPRESS_WORKDIR ---> /opt/local/etc/macports/macports.conf: revupgrade_mode: report ---> /opt/local/etc/macports/macports.conf: packagemaker_path: /Developer/Applications/Utilities/PackageMaker.app ---> /opt/local/etc/macports/sources.conf: file:///Users/bertin/cworks/MacOSX/MacPorts/ports nosync ---> /opt/local/etc/macports/sources.conf: file:///opt/local/site-ports nosync ---> /opt/local/etc/macports/sources.conf: file:///opt/local/site- ports/Soup nosync ---> /opt/local/etc/macports/sources.conf: rsync://rsync.macports.org/release/ports/ default ---> /opt/local/etc/macports/sources.conf: file:///opt/local/var/macports/sources/svn.macports.org/trunk/dports ---> /opt/local/etc/macports/sources.conf: file:///opt/local/var/macports/sources/git.macports.org/dports/ MacPorts 2.3.99 }}} {{{ > port environment ---> port_cmd_version: 2.3.99 ---> bootstrap_options: applications_dir: /Applications/MacPorts ---> bootstrap_options: binpath: /opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin ---> bootstrap_options: build_arch: x86_64 ---> bootstrap_options: buildmakejobs: 4 ---> bootstrap_options: buildnicevalue: 0 ---> bootstrap_options: ccache_dir: /opt/local/var/macports/build/.ccache ---> bootstrap_options: ccache_size: 2G ---> bootstrap_options: configureccache: no ---> bootstrap_options: configuredistcc: no ---> bootstrap_options: configurepipe: no ---> bootstrap_options: cxx_stdlib: libc++ ---> bootstrap_options: delete_la_files: yes ---> bootstrap_options: destroot_umask: 022 ---> bootstrap_options: developer_dir: /Applications/Xcode.app/Contents/Developer ---> bootstrap_options: extra_env: MACPORTS_COMPRESS_WORKDIR ---> bootstrap_options: frameworks_dir: /opt/local/Library/Frameworks ---> bootstrap_options: keeplogs: no ---> bootstrap_options: macosx_deployment_target: 10.9 ---> bootstrap_options: macosx_sdk_version: 10.9 ---> bootstrap_options: macportsuser: bertin ---> bootstrap_options: packagemaker_path: /Developer/Applications/UtilitiesPackageMaker.app ---> bootstrap_options: place_worksymlink: no ---> bootstrap_options: portarchivetype: txz ---> bootstrap_options: portautoclean: yes ---> bootstrap_options: portdbpath: /opt/local/var/macports ---> bootstrap_options: porttrace: no ---> bootstrap_options: portverbose: no ---> bootstrap_options: prefix: /opt/local ---> bootstrap_options: revupgrade_autorun: yes ---> bootstrap_options: revupgrade_mode: report ---> bootstrap_options: rsync_dir: macports/release/tarballs/base.tar ---> bootstrap_options: rsync_options: -rtzv --delete-after ---> bootstrap_options: rsync_server: rsync.macports.org ---> bootstrap_options: sandbox_enable: no ---> bootstrap_options: sources_conf: /opt/local/etc/macports/sources.conf ---> bootstrap_options: startupitem_install: yes ---> bootstrap_options: startupitem_type: default ---> bootstrap_options: universal_archs: i386 x86_64 ---> bootstrap_options: variants_conf: /opt/local/etc/macports/variants.conf ---> bootstrap_options: xcodebuildcmd: /usr/bin/xcodebuild ---> bootstrap_options: xcodeversion: 6.2 ---> port_tree_sources: file:///Users/bertin/cworks/MacOSX/MacPorts/ports nosync ---> port_tree_sources: file:///opt/local/site-ports nosync ---> port_tree_sources: file:///opt/local/site-ports/Soup nosync ---> port_tree_sources: rsync://rsync.macports.org/release/ports/ default ---> port_tree_sources: file:///opt/local/var/macports/sources/svn.macports.org/trunk/dports ---> port_tree_sources: file:///opt/local/var/macports/sources/git.macports.org/dports/ ---> global_variations: +langselect ---> shell environment: TMPDIR=/var/folders/j1/1439ppj08xj8h6006s6drbq00000gs/T/ HOME=/opt/local/var/macports/home USER=bertin PATH=/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin GROUP=bertin MACPORTS_COMPRESS_WORKDIR=1 LINES=48 COLUMNS=132 LANG=en_US.UTF-8 http_proxy=127.0.0.1:8001 HTTPS_PROXY=127.0.0.1:8001 NO_PROXY=localhost,192.1.1.1,*facebook.com,*.icloud.com CCACHE_DIR=/opt/local/var/macports/build/.ccache }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 14:13:22 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 14:13:22 -0000 Subject: [MacPorts] #53019: mogenerator: update to v1.31 Message-ID: <050.8a174741fb7e44432b228be9a4819fd2@macports.org> #53019: mogenerator: update to v1.31 ---------------------------+------------------------- Reporter: steventondeur | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: haspatch | Port: mogenerator ---------------------------+------------------------- mogenerator port file refers to an outdated version. Attached patch updates port file to v1.31 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 14:13:54 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 14:13:54 -0000 Subject: [MacPorts] #53019: mogenerator: update to v1.31 In-Reply-To: <050.8a174741fb7e44432b228be9a4819fd2@macports.org> References: <050.8a174741fb7e44432b228be9a4819fd2@macports.org> Message-ID: <065.9083b38bc97845131a7b4684fd77795d@macports.org> #53019: mogenerator: update to v1.31 ----------------------------+---------------------- Reporter: steventondeur | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: haspatch Port: mogenerator | ----------------------------+---------------------- Changes (by steventondeur): * Attachment "Portfile-mogenerator.diff" added. portfile patch -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 14:39:05 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 14:39:05 -0000 Subject: [MacPorts] #53020: apache24-devel @2.4.23: fix CVE-2016-8740 Message-ID: <041.61e31453795fb280b7ea256cd229e7c0@macports.org> #53020: apache24-devel @2.4.23: fix CVE-2016-8740 --------------------+---------------------------- Reporter: l2dy | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: apache24-devel --------------------+---------------------------- See http://mail-archives.apache.org/mod_mbox/httpd- announce/201612.mbox/%3C1A097A43-7CCB-4BA1-861F- E0C7EEE83A4B%40apache.org%3E -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 14:53:06 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 14:53:06 -0000 Subject: [MacPorts] #53017: kerberos5 fails to build on Yosemite with libressl In-Reply-To: <045.2e6d5c80e4930d3d8f0c88d93b24a25b@macports.org> References: <045.2e6d5c80e4930d3d8f0c88d93b24a25b@macports.org> Message-ID: <060.32f8a4a682d524b1f729e89cc52b138d@macports.org> #53017: kerberos5 fails to build on Yosemite with libressl ------------------------+------------------------ Reporter: bK4gYuRo | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: kerberos5 | ------------------------+------------------------ Changes (by mf2k): * owner: => ryandesign * status: new => assigned Comment: In the future, please use WikiFormatting and Cc the port maintainers ({{{port info --maintainers kerberos5}}}), if any. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 14:53:17 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 14:53:17 -0000 Subject: [MacPorts] #53017: kerberos5 fails to build on Yosemite with libressl In-Reply-To: <045.2e6d5c80e4930d3d8f0c88d93b24a25b@macports.org> References: <045.2e6d5c80e4930d3d8f0c88d93b24a25b@macports.org> Message-ID: <060.674abfd497b2d80de1308ba86be61650@macports.org> #53017: kerberos5 fails to build on Yosemite with libressl ------------------------+------------------------ Reporter: bK4gYuRo | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: kerberos5 | ------------------------+------------------------ Description changed by mf2k: Old description: > kerberos5 @1.15_0 fails to build on Yosemite (10.10.5) with libressl > @2.4.3_0. > > :info:build Undefined symbols for architecture x86_64: > :info:build "_HMAC_CTX_new", referenced from: > :info:build _krb5int_hmac_keyblock in hmac.so > :info:build "_EVP_MD_CTX_new", referenced from: > :info:build _hash_evp in hash_evp.so > :info:build _k5_sha256 in sha256.so > :info:build "_HMAC_CTX_free", referenced from: > :info:build _krb5int_hmac_keyblock in hmac.so > :info:build "_EVP_MD_CTX_free", referenced from: > :info:build _hash_evp in hash_evp.so > :info:build _k5_sha256 in sha256.so > :info:build ld: symbol(s) not found for architecture x86_64 > > I am attaching the full build log New description: kerberos5 @1.15_0 fails to build on Yosemite (10.10.5) with libressl @2.4.3_0. {{{ :info:build Undefined symbols for architecture x86_64: :info:build "_HMAC_CTX_new", referenced from: :info:build _krb5int_hmac_keyblock in hmac.so :info:build "_EVP_MD_CTX_new", referenced from: :info:build _hash_evp in hash_evp.so :info:build _k5_sha256 in sha256.so :info:build "_HMAC_CTX_free", referenced from: :info:build _krb5int_hmac_keyblock in hmac.so :info:build "_EVP_MD_CTX_free", referenced from: :info:build _hash_evp in hash_evp.so :info:build _k5_sha256 in sha256.so :info:build ld: symbol(s) not found for architecture x86_64 }}} I am attaching the full build log -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 15:14:52 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 15:14:52 -0000 Subject: [MacPorts] #53021: octave @4.2.0_1: Another build failure Message-ID: <041.a9100f410b771f7245060d742521900f@macports.org> #53021: octave @4.2.0_1: Another build failure --------------------+--------------------------------- Reporter: mf2k | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: octave --------------------+--------------------------------- I am seeing a different build error than #53016 for octave on El Capitan. {{{ :info:build In file included from /System/Library/Frameworks/CoreGraphics.framework/Headers/CGContext.h:18:0, :info:build from /System/Library/Frameworks/CoreGraphics.framework/Headers/CGBitmapContext.h:9, :info:build from /System/Library/Frameworks/CoreGraphics.framework/Headers/CoreGraphics.h:11, :info:build from /System/Library/Frameworks/ApplicationServices.framework/Headers/ApplicationServices.h:35, :info:build from /System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:24, :info:build from libinterp/corefcn/cdisplay.c:32: :info:build /System/Library/Frameworks/CoreGraphics.framework/Headers/CGFont.h:53:40: error: initializer element is not constant :info:build static const CGFontIndex kCGGlyphMax = kCGFontIndexMax; :info:build ^~~~~~~~~~~~~~~ :info:build libinterp/corefcn/cdisplay.c: In function 'octave_get_display_info': :info:build libinterp/corefcn/cdisplay.c:96:7: warning: 'CGDisplayModeCopyPixelEncoding' is deprecated [-Wdeprecated-declarations] :info:build CFStringRef pixelEncoding = CGDisplayModeCopyPixelEncoding (mode); :info:build ^~~~~~~~~~~ :info:build In file included from /System/Library/Frameworks/CoreGraphics.framework/Headers/CoreGraphics.h:39:0, :info:build from /System/Library/Frameworks/ApplicationServices.framework/Headers/ApplicationServices.h:35, :info:build from /System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:24, :info:build from libinterp/corefcn/cdisplay.c:32: :info:build /System/Library/Frameworks/CoreGraphics.framework/Headers/CGDirectDisplay.h:174:34: note: declared here :info:build CG_EXTERN CFStringRef __nullable CGDisplayModeCopyPixelEncoding( :info:build ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ :info:build make[2]: *** [libinterp/corefcn /libinterp_corefcn_libcorefcn_la-cdisplay.lo] Error 1 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 15:15:05 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 15:15:05 -0000 Subject: [MacPorts] #53021: octave @4.2.0_1: Another build failure In-Reply-To: <041.a9100f410b771f7245060d742521900f@macports.org> References: <041.a9100f410b771f7245060d742521900f@macports.org> Message-ID: <056.a1aa6a3a50263fdbd0be3919c1ded63c@macports.org> #53021: octave @4.2.0_1: Another build failure ---------------------+--------------------------------- Reporter: mf2k | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: octave | ---------------------+--------------------------------- Changes (by mf2k): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 15:23:54 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 15:23:54 -0000 Subject: [MacPorts] #53022: opencv @3.1.0_6+python34: Portfile broken for variant +python34 Message-ID: <044.4cfc0421df7d7ecacd2795ceaf0f1af4@macports.org> #53022: opencv @3.1.0_6+python34: Portfile broken for variant +python34 ---------------------+-------------------- Reporter: detlevd | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: opencv ---------------------+-------------------- On macOS 10.11 I installed opencv +python34, but the portfile causes python35 and friends to be installed (alltough for py34 everything is there): {{{ me at mymac> sudo port install opencv +python34 ---> Computing dependencies for opencv ---> Dependencies to be installed: py35-numpy py35-cython python35 py35-nose py35-setuptools ... }}} Furthermore, the stuff is then installed in .../3.5/lib/python3.5/site- packages where my python 3.4 scripts don't find them. Compared to earlier versions of the Portfile (opencv @3.1.0_4+python34), instead of explicit variant descriptions, the current one (opencv @3.1.0_6+python34) contains some loop over python versions {{{ set pythonversions {3.4 3.5} foreach pdv ${pythonversions} { set pv [join [lrange [split ${pdv} .] 0 1] ""] set conflist "" foreach v ${pythonversions} { ... }}} which apparently does not work as expected. Workaround: delete '3.5' from the 'pythonversions' list to get a working "+python34" variant. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 15:27:30 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 15:27:30 -0000 Subject: [MacPorts] #53019: mogenerator: update to v1.31 In-Reply-To: <050.8a174741fb7e44432b228be9a4819fd2@macports.org> References: <050.8a174741fb7e44432b228be9a4819fd2@macports.org> Message-ID: <065.663db1766fd9b3eb0af644063f37663a@macports.org> #53019: mogenerator: update to v1.31 ----------------------------+------------------------------- Reporter: steventondeur | Owner: public+macports@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: mogenerator | ----------------------------+------------------------------- Changes (by mf2k): * status: new => assigned * cc: public+macports@… (removed) * version: 2.3.5 => * owner: => public+macports@… -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 15:29:45 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 15:29:45 -0000 Subject: [MacPorts] #53020: apache24-devel @2.4.23: fix CVE-2016-8740 In-Reply-To: <041.61e31453795fb280b7ea256cd229e7c0@macports.org> References: <041.61e31453795fb280b7ea256cd229e7c0@macports.org> Message-ID: <056.6e9ab41bfd549ae2b323d3d5d743a37a@macports.org> #53020: apache24-devel @2.4.23: fix CVE-2016-8740 -----------------------------+------------------------ Reporter: l2dy | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: apache24-devel | -----------------------------+------------------------ Changes (by mf2k): * cc: ryandesign (removed) * owner: => ryandesign * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 15:48:25 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 15:48:25 -0000 Subject: [MacPorts] #53022: opencv @3.1.0_6+python34: Portfile broken for variant +python34 In-Reply-To: <044.4cfc0421df7d7ecacd2795ceaf0f1af4@macports.org> References: <044.4cfc0421df7d7ecacd2795ceaf0f1af4@macports.org> Message-ID: <059.d731074258adca325bfc1a40e693f002@macports.org> #53022: opencv @3.1.0_6+python34: Portfile broken for variant +python34 ----------------------+---------------------- Reporter: detlevd | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: opencv | ----------------------+---------------------- Changes (by mf2k): * status: new => assigned * owner: => stromnov Comment: In the future, please Cc the port maintainers ({{{port info --maintainers opencv}}}), if any. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 17:23:17 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 17:23:17 -0000 Subject: [MacPorts] #52905: gr-specest: default_variants causes error. In-Reply-To: <041.c1f2121cc9d03dcb3b3258eaf262077f@macports.org> References: <041.c1f2121cc9d03dcb3b3258eaf262077f@macports.org> Message-ID: <056.a6131bacd4b2c3655c67173bbba683eb@macports.org> #52905: gr-specest: default_variants causes error. -------------------------+----------------------- Reporter: mf2k | Owner: michaelld Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gr-specest | -------------------------+----------------------- Comment (by michaelld): In [changeset:"00c84992d43229b486aca95dbdb2b9034cc95724/macports-ports" 00c84992/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="00c84992d43229b486aca95dbdb2b9034cc95724" gr-specest: update to 748aa13b (20151205); fix default variant selection, per ticket https://trac.macports.org/ticket/52905 . }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 17:24:07 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 17:24:07 -0000 Subject: [MacPorts] #52905: gr-specest: default_variants causes error. In-Reply-To: <041.c1f2121cc9d03dcb3b3258eaf262077f@macports.org> References: <041.c1f2121cc9d03dcb3b3258eaf262077f@macports.org> Message-ID: <056.448cfb568b42c2e61d1231c5620d518a@macports.org> #52905: gr-specest: default_variants causes error. -------------------------+----------------------- Reporter: mf2k | Owner: michaelld Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: gr-specest | -------------------------+----------------------- Changes (by michaelld): * status: new => closed * resolution: => fixed Comment: Good catch! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 17:36:37 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 17:36:37 -0000 Subject: [MacPorts] #52902: uhd: Add python 3.5 In-Reply-To: <041.731bd138773a8181e00d6561842cac36@macports.org> References: <041.731bd138773a8181e00d6561842cac36@macports.org> Message-ID: <056.f8ff333481e994dc8822d1571a071c1d@macports.org> #52902: uhd: Add python 3.5 --------------------------+----------------------- Reporter: mf2k | Owner: michaelld Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: uhd | --------------------------+----------------------- Comment (by michaelld): Looks like UHD isn't quite ready for Python 3.5 yet. Here's the error I get when I add a +python35 variant and select it: {{{ :info:build [ 6%] Generating /Development/local/10_12/var/macports/build/_Development_sources_MacPorts_ports_github_macports_science_uhd /uhd-devel/work/build/docs/nocscript_functions.dox :info:build cd /Development/local/10_12/var/macports/build/_Development_sources_MacPorts_ports_github_macports_science_uhd /uhd-devel/work/build/lib && /opt/local/bin/python3.5 -B /Development/local/10_12/var/macports/build/_Development_sources_MacPorts_ports_github_macports_science_uhd /uhd-devel/work/uhd- 77cbd56a5d09b29720aa309a9c95765c01ec9c65/host/lib/rfnoc/nocscript/gen_basic_funcs.py /Development/local/10_12/var/macports/build/_Development_sources_MacPorts_ports_github_macports_science_uhd /uhd-devel/work/build/docs/nocscript_functions.dox :info:build /Development/local/10_12/var/macports/build/_Development_sources_MacPorts_ports_github_macports_science_uhd /uhd-devel/work/uhd- 77cbd56a5d09b29720aa309a9c95765c01ec9c65/host/lib/rfnoc/nocscript/gen_basic_funcs.py:391: FutureWarning: split() requires a non-empty pattern match. :info:build func_list_split = func_splitter_re.split(func_list_wo_comments) :info:build Traceback (most recent call last): :info:build File "/Development/local/10_12/var/macports/build/_Development_sources_MacPorts_ports_github_macports_science_uhd /uhd-devel/work/uhd- 77cbd56a5d09b29720aa309a9c95765c01ec9c65/host/lib/rfnoc/nocscript/gen_basic_funcs.py", line 474, in :info:build main() :info:build File "/Development/local/10_12/var/macports/build/_Development_sources_MacPorts_ports_github_macports_science_uhd /uhd-devel/work/uhd- 77cbd56a5d09b29720aa309a9c95765c01ec9c65/host/lib/rfnoc/nocscript/gen_basic_funcs.py", line 469, in main :info:build write_manual_file(outfile) :info:build File "/Development/local/10_12/var/macports/build/_Development_sources_MacPorts_ports_github_macports_science_uhd /uhd-devel/work/uhd- 77cbd56a5d09b29720aa309a9c95765c01ec9c65/host/lib/rfnoc/nocscript/gen_basic_funcs.py", line 455, in write_manual_file :info:build if not func_list_tree.has_key(func['category']): :info:build AttributeError: 'dict' object has no attribute 'has_key' :info:build make[2]: *** [docs/nocscript_functions.dox] Error 1 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 18:30:37 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 18:30:37 -0000 Subject: [MacPorts] #53018: mercurial @4.0.1: error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but "10.11" during configure (was: error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but "10.11" during configure) In-Reply-To: <042.20cc68d2a5b85e3ef4bb92ae1dd59d73@macports.org> References: <042.20cc68d2a5b85e3ef4bb92ae1dd59d73@macports.org> Message-ID: <057.a07982ba3d4732beea3c05a54c2159f9@macports.org> #53018: mercurial @4.0.1: error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but "10.11" during configure ------------------------+------------------------ Reporter: yabba | Owner: seanfarley Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: mercurial | ------------------------+------------------------ Comment (by ryandesign): Is there anything unusual about your setup? Any thing that might explain why this happens for you but not for others? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 18:34:49 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 18:34:49 -0000 Subject: [MacPorts] #53021: octave @4.2.0_1: Another build failure In-Reply-To: <041.a9100f410b771f7245060d742521900f@macports.org> References: <041.a9100f410b771f7245060d742521900f@macports.org> Message-ID: <056.0ad3265ec019b8980746ef9c4d96bd70@macports.org> #53021: octave @4.2.0_1: Another build failure ---------------------+--------------------------------- Reporter: mf2k | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: octave | ---------------------+--------------------------------- Comment (by ryandesign): That looks like you are running a version of Xcode and/or the command line tools that is too old for El Capitan. I see clang 800 mentioned in the log, so I guess you have Xcode 8. On El Capitan, there is no command line tools for Xcode 8, so ensure you have installed the command line tools for Xcode 7.3. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 19:03:50 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 19:03:50 -0000 Subject: [MacPorts] #53023: Molden checksum error yet again Message-ID: <047.c67b0ce3c0e80d007e004329a70c8f30@macports.org> #53023: Molden checksum error yet again ------------------------------+-------------------- Reporter: mersault32 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: molden; checksum | Port: molden ------------------------------+-------------------- Macports 2.3.4 on Mac OS Sierra 10.12.1 ---> Computing dependencies for molden ---> Verifying checksums for molden Error: Checksum (rmd160) mismatch for molden5.7.tar.gz Error: Checksum (sha256) mismatch for molden5.7.tar.gz Error: org.macports.checksum for port molden returned: Unable to verify file checksums Please see the log file for port molden for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_molden/molden/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port molden failed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 19:10:39 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 19:10:39 -0000 Subject: [MacPorts] #53023: Molden checksum error yet again In-Reply-To: <047.c67b0ce3c0e80d007e004329a70c8f30@macports.org> References: <047.c67b0ce3c0e80d007e004329a70c8f30@macports.org> Message-ID: <062.871159668334aaaa6d7b2b9f38316175@macports.org> #53023: Molden checksum error yet again -------------------------+------------------------ Reporter: mersault32 | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: molden | -------------------------+------------------------ Changes (by raimue): * owner: => ryandesign * status: new => assigned * keywords: molden; checksum => Old description: > Macports 2.3.4 on Mac OS Sierra 10.12.1 > > ---> Computing dependencies for molden > ---> Verifying checksums for molden > Error: Checksum (rmd160) mismatch for molden5.7.tar.gz > Error: Checksum (sha256) mismatch for molden5.7.tar.gz > Error: org.macports.checksum for port molden returned: Unable to verify > file checksums > Please see the log file for port molden for details: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_molden/molden/main.log > To report a bug, follow the instructions in the guide: > http://guide.macports.org/#project.tickets > Error: Processing of port molden failed New description: Macports 2.3.4 on Mac OS Sierra 10.12.1 {{{ ---> Computing dependencies for molden ---> Verifying checksums for molden Error: Checksum (rmd160) mismatch for molden5.7.tar.gz Error: Checksum (sha256) mismatch for molden5.7.tar.gz Error: org.macports.checksum for port molden returned: Unable to verify file checksums Please see the log file for port molden for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_molden/molden/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port molden failed }}} -- Comment: Please use WikiFormatting. Assigning to maintainer (`port info --maintainer`). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 21:55:24 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 21:55:24 -0000 Subject: [MacPorts] #53004: go @1.7.3: update to 1.7.4 In-Reply-To: <041.c53263009725c99ff11ca3dfc2af6049@macports.org> References: <041.c53263009725c99ff11ca3dfc2af6049@macports.org> Message-ID: <056.b37fa641086be7921781a5f32f55c15c@macports.org> #53004: go @1.7.3: update to 1.7.4 ---------------------+-------------------- Reporter: l2dy | Owner: ci42 Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: go | ---------------------+-------------------- Changes (by ci42): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"dc7a3c9232ccc2f65600c9eb3b4bad7c2425a153/macports-ports" dc7a3c92/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="dc7a3c9232ccc2f65600c9eb3b4bad7c2425a153" go: update to version 1.7.4 Closes: https://trac.macports.org/ticket/53004 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 22:17:10 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 22:17:10 -0000 Subject: [MacPorts] #53024: byebug Debugger for Ruby 2 Message-ID: <050.6c0422a08b4f2e5bf4cb080973445ce9@macports.org> #53024: byebug Debugger for Ruby 2 ---------------------------+------------------------- Reporter: luc-j-bourhis | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: rb23-byebug ---------------------------+------------------------- Ruby 2 introduced changes requiring new debugger frameworks: byebug is one of them. My motivation comes from the fact that it is a required install for the popular Komodo IDE to enable its graphical debugger for Ruby 2. This is the first time I write a Portfile for a ruby component, so forgive the quirks if any! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 22:18:47 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 22:18:47 -0000 Subject: [MacPorts] #53024: byebug Debugger for Ruby 2 In-Reply-To: <050.6c0422a08b4f2e5bf4cb080973445ce9@macports.org> References: <050.6c0422a08b4f2e5bf4cb080973445ce9@macports.org> Message-ID: <065.fc49c9b74074440f5fc8c4a89c4d363f@macports.org> #53024: byebug Debugger for Ruby 2 ----------------------------+----------------- Reporter: luc-j-bourhis | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rb23-byebug | ----------------------------+----------------- Changes (by luc-j-bourhis): * Attachment "Portfile" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 22:25:17 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 22:25:17 -0000 Subject: [MacPorts] #53023: Molden checksum error yet again In-Reply-To: <047.c67b0ce3c0e80d007e004329a70c8f30@macports.org> References: <047.c67b0ce3c0e80d007e004329a70c8f30@macports.org> Message-ID: <062.92f134048d4a0f20630388b39009b8dd@macports.org> #53023: Molden checksum error yet again -------------------------+------------------------ Reporter: mersault32 | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: molden | -------------------------+------------------------ Comment (by ryandesign): You didn't attach a log or show what the actual or expected checksums were. I updated molden to the latest stealth update a couple days ago in [ce9f14dfbdc11579114f33f6eb12bab7ba0354e7/macports-ports]. Please make sure you have this change by running `sudo port selfupdate` and trying again. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 22:25:50 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 22:25:50 -0000 Subject: [MacPorts] #53023: Molden checksum error yet again In-Reply-To: <047.c67b0ce3c0e80d007e004329a70c8f30@macports.org> References: <047.c67b0ce3c0e80d007e004329a70c8f30@macports.org> Message-ID: <062.7542038b4bea5ba57b4532b6eed390b3@macports.org> #53023: Molden checksum error yet again -------------------------+------------------------ Reporter: mersault32 | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: molden | -------------------------+------------------------ Changes (by ryandesign): * version: 2.3.5 => 2.3.4 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 22:46:43 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 22:46:43 -0000 Subject: [MacPorts] #53023: Molden checksum error yet again In-Reply-To: <047.c67b0ce3c0e80d007e004329a70c8f30@macports.org> References: <047.c67b0ce3c0e80d007e004329a70c8f30@macports.org> Message-ID: <062.7e22710883f71cd93576506285a523ea@macports.org> #53023: Molden checksum error yet again -------------------------+------------------------ Reporter: mersault32 | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: molden | -------------------------+------------------------ Changes (by mersault32): * Attachment "molden.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 22:47:27 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 22:47:27 -0000 Subject: [MacPorts] #53023: Molden checksum error yet again In-Reply-To: <047.c67b0ce3c0e80d007e004329a70c8f30@macports.org> References: <047.c67b0ce3c0e80d007e004329a70c8f30@macports.org> Message-ID: <062.2d8736063249a10845e15358307ca6db@macports.org> #53023: Molden checksum error yet again -------------------------+------------------------ Reporter: mersault32 | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: molden | -------------------------+------------------------ Comment (by mersault32): It is fixed now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 23:31:41 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 23:31:41 -0000 Subject: [MacPorts] #53024: byebug Debugger for Ruby 2 In-Reply-To: <050.6c0422a08b4f2e5bf4cb080973445ce9@macports.org> References: <050.6c0422a08b4f2e5bf4cb080973445ce9@macports.org> Message-ID: <065.69c8f032ab090a3f851cdc339b31ed6d@macports.org> #53024: byebug Debugger for Ruby 2 ----------------------------+----------------- Reporter: luc-j-bourhis | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rb23-byebug | ----------------------------+----------------- Comment (by ryandesign): Thanks. The license line should just read "BSD". There should be two different checksums; typically we use rmd160 and sha256. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 23:33:30 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 23:33:30 -0000 Subject: [MacPorts] #53023: Molden checksum error yet again In-Reply-To: <047.c67b0ce3c0e80d007e004329a70c8f30@macports.org> References: <047.c67b0ce3c0e80d007e004329a70c8f30@macports.org> Message-ID: <062.bbcf0f33c5b7bfefcab75abfbf5b533a@macports.org> #53023: Molden checksum error yet again -------------------------+------------------------ Reporter: mersault32 | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: invalid | Keywords: Port: molden | -------------------------+------------------------ Changes (by ryandesign): * status: assigned => closed * resolution: => invalid Comment: Thanks, that log confirms you were not up to date at the time. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 23:48:52 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 23:48:52 -0000 Subject: [MacPorts] #53024: byebug Debugger for Ruby 2 In-Reply-To: <050.6c0422a08b4f2e5bf4cb080973445ce9@macports.org> References: <050.6c0422a08b4f2e5bf4cb080973445ce9@macports.org> Message-ID: <065.fc49c9b74074440f5fc8c4a89c4d363f@macports.org> #53024: byebug Debugger for Ruby 2 ----------------------------+----------------- Reporter: luc-j-bourhis | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rb23-byebug | ----------------------------+----------------- Changes (by luc-j-bourhis): * Attachment "Portfile" removed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 23:48:52 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 23:48:52 -0000 Subject: [MacPorts] #53024: byebug Debugger for Ruby 2 In-Reply-To: <050.6c0422a08b4f2e5bf4cb080973445ce9@macports.org> References: <050.6c0422a08b4f2e5bf4cb080973445ce9@macports.org> Message-ID: <065.237e70f41d1fd3667dae95a865f9ff85@macports.org> #53024: byebug Debugger for Ruby 2 ----------------------------+----------------- Reporter: luc-j-bourhis | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rb23-byebug | ----------------------------+----------------- Changes (by luc-j-bourhis): * Attachment "Portfile" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 23:50:41 2016 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2016 23:50:41 -0000 Subject: [MacPorts] #53024: byebug Debugger for Ruby 2 In-Reply-To: <050.6c0422a08b4f2e5bf4cb080973445ce9@macports.org> References: <050.6c0422a08b4f2e5bf4cb080973445ce9@macports.org> Message-ID: <065.c051e4a9e0e0a1aab9cc08795e98123d@macports.org> #53024: byebug Debugger for Ruby 2 ----------------------------+----------------- Reporter: luc-j-bourhis | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rb23-byebug | ----------------------------+----------------- Comment (by luc-j-bourhis): I have uploaded a fixed Portfile addressing your two points. Thanks. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 01:34:26 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 01:34:26 -0000 Subject: [MacPorts] #53015: octave-octclip, octave-octproj: missing patch file In-Reply-To: <048.be8fb1f67e3eed30df7100ac0090b392@macports.org> References: <048.be8fb1f67e3eed30df7100ac0090b392@macports.org> Message-ID: <063.2355f89e655f57fa78872558038b00cb@macports.org> #53015: octave-octclip, octave-octproj: missing patch file --------------------------------------------+------------------------------ Reporter: Schamschula | Owner: MarcusCalhoun- | Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: octave-octclip octave-octproj | --------------------------------------------+------------------------------ Comment (by Schamschula): Unfortunately, the patch file results in a broken build. Both octave- octclip and octave-octproj fail to build with an error like {{{ In file included from /opt/local/include/octave-4.2.0/octave/Array.h:37: /opt/local/include/octave-4.2.0/octave/dim-vector.h:205:21: warning: variadic templates are a C++11 extension [-Wc++11-extensions] template ^ /opt/local/include/octave-4.2.0/octave/dim-vector.h:209:10: error: no member named 'initializer_list' in namespace 'std' std::initializer_list all_lengths = {r, c, lengths...}; ~~~~~^ /opt/local/include/octave-4.2.0/octave/dim-vector.h:209:27: error: unexpected type name 'octave_idx_type': expected expression std::initializer_list all_lengths = {r, c, lengths...}; ^ /opt/local/include/octave-4.2.0/octave/dim-vector.h:209:44: error: use of undeclared identifier 'all_lengths' std::initializer_list all_lengths = {r, c, lengths...}; ^ /opt/local/include/octave-4.2.0/octave/dim-vector.h:209:58: error: expected expression std::initializer_list all_lengths = {r, c, lengths...}; ^ /opt/local/include/octave-4.2.0/octave/dim-vector.h:210:33: warning: range-based for loop is a C++11 extension [-Wc++11-extensions] for (const octave_idx_type l: all_lengths) ^ /opt/local/include/octave-4.2.0/octave/dim-vector.h:210:35: error: use of undeclared identifier 'all_lengths' for (const octave_idx_type l: all_lengths) ^ /opt/local/include/octave-4.2.0/octave/dim-vector.h:212:12: error: use of undeclared identifier 'all_lengths' rep -= all_lengths.size (); ^ }}} For some reason {{{configure.cxxflags-append -std=c++11}}} in octave-1.0.tcl seems to be ignored. I modified {{{patch-flags.diff}}} to add {{{CXXFLAGS+=-std=c++11}}}, resulting in a clean build. However, I now got a MacPorts destroot error: {{{Error: org.macports.destroot for port octave-octproj returned: xinstall: Cannot stat: /opt/local/var/macports/build /_Users_marius_Development_MacPorts_ports_math_octave-octproj/octave- octproj/work/octproj/octproj-1.1.5.tar.gz, No such file or directory}}} On further investigation, I got {{{octproj-1.1.5-x86_64-apple- darwin16.x.x-api-v51.tar.gz}}} instead. I manually renamed this file to {{{octproj-1.1.5.tar.gz}}} and got it to install. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 02:31:22 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 02:31:22 -0000 Subject: [MacPorts] #53015: octave-octclip, octave-octproj: missing patch file In-Reply-To: <048.be8fb1f67e3eed30df7100ac0090b392@macports.org> References: <048.be8fb1f67e3eed30df7100ac0090b392@macports.org> Message-ID: <063.fc89cd9081784afb13e66c124a1f6a1d@macports.org> #53015: octave-octclip, octave-octproj: missing patch file --------------------------------------------+------------------------------ Reporter: Schamschula | Owner: MarcusCalhoun- | Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: octave-octclip octave-octproj | --------------------------------------------+------------------------------ Comment (by MarcusCalhoun-Lopez): This is very strange.[[BR]] I have not encountered either of these errors.[[BR]] Would it be too much to ask to post the main.log files for the two failed builds? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 09:35:38 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 09:35:38 -0000 Subject: [MacPorts] #53022: opencv @3.1.0_6+python34: Portfile broken for variant +python34 In-Reply-To: <044.4cfc0421df7d7ecacd2795ceaf0f1af4@macports.org> References: <044.4cfc0421df7d7ecacd2795ceaf0f1af4@macports.org> Message-ID: <059.83e985f1c899cf1737fc621b2cea6f2b@macports.org> #53022: opencv @3.1.0_6+python34: Portfile broken for variant +python34 ----------------------+---------------------- Reporter: detlevd | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: opencv | ----------------------+---------------------- Comment (by RJVB): My bad, defining variants (or subports) in a loop that set dependencies or configure arguments that contain loop variables can lead to unexpected results, and I've already been bitten by it before. If it's that the fix is easy enough and I'll upload a patch shortly. detlevd, you seem handy enough to tinker around in Portfiles, could you apply and test the patch when you see it please? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 09:57:21 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 09:57:21 -0000 Subject: [MacPorts] #53022: opencv @3.1.0_6+python34: Portfile broken for variant +python34 In-Reply-To: <044.4cfc0421df7d7ecacd2795ceaf0f1af4@macports.org> References: <044.4cfc0421df7d7ecacd2795ceaf0f1af4@macports.org> Message-ID: <059.530b3e955bc89c2c76570cb8d1a8d8ee@macports.org> #53022: opencv @3.1.0_6+python34: Portfile broken for variant +python34 ----------------------+---------------------- Reporter: detlevd | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: opencv | ----------------------+---------------------- Changes (by RJVB): * Attachment "opencv-python-fix.diff" added. fix the +python34 build issue (and removes an inexistant CMake option). A revbump is not required. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 10:33:53 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 10:33:53 -0000 Subject: [MacPorts] #53025: netcat @1.10_2 doesn't listen, exits with "Abort trap: 6" Message-ID: <047.949572ce9a6a463c7582161f5ea7bf86@macports.org> #53025: netcat @1.10_2 doesn't listen, exits with "Abort trap: 6" ------------------------+-------------------- Reporter: user454322 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: netcat ------------------------+-------------------- Can't use netcat to listen for incoming connections. Trying to do so results on netcat exiting with status ''134'' and message ''Abort trap: 6''. Attached is the output of ''sudo dtruss -fn nc''. {{{ $ uname -a Darwin camotes 15.5.0 Darwin Kernel Version 15.5.0: Tue Apr 19 18:36:36 PDT 2016; root:xnu-3248.50.21~8/RELEASE_X86_64 x86_64 $ port installed | grep netcat netcat @1.10_2 (active) $ nc -l 4040 Abort trap: 6 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 10:34:29 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 10:34:29 -0000 Subject: [MacPorts] #53025: netcat @1.10_2 doesn't listen, exits with "Abort trap: 6" In-Reply-To: <047.949572ce9a6a463c7582161f5ea7bf86@macports.org> References: <047.949572ce9a6a463c7582161f5ea7bf86@macports.org> Message-ID: <062.45e3023b287ca5fb4d8218ae3ec50cb7@macports.org> #53025: netcat @1.10_2 doesn't listen, exits with "Abort trap: 6" -------------------------+------------------- Reporter: user454322 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: netcat | -------------------------+------------------- Changes (by user454322): * Attachment "nc-dtruss.txt" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 11:45:53 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 11:45:53 -0000 Subject: [MacPorts] #53026: nodejs6 and npm4 needs update Message-ID: <050.c534650540f9311476383ef1b7981727@macports.org> #53026: nodejs6 and npm4 needs update ---------------------------+-------------------- Reporter: luc-j-bourhis | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: nodejs ---------------------------+-------------------- {{{ % port livecheck npm4 npm4 seems to have been updated (port version: 4.0.2, new version: 4.0.5) % port livecheck nodejs6 nodejs6 seems to have been updated (port version: 6.9.1, new version: 6.9.2) }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 12:12:29 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 12:12:29 -0000 Subject: [MacPorts] #53018: mercurial @4.0.1: error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but "10.11" during configure In-Reply-To: <042.20cc68d2a5b85e3ef4bb92ae1dd59d73@macports.org> References: <042.20cc68d2a5b85e3ef4bb92ae1dd59d73@macports.org> Message-ID: <057.f6463fa209d975bd58cb1f8753bbc3dd@macports.org> #53018: mercurial @4.0.1: error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but "10.11" during configure ------------------------+------------------------ Reporter: yabba | Owner: seanfarley Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: mercurial | ------------------------+------------------------ Comment (by yabba): Replying to [comment:2 ryandesign]: > Is there anything unusual about your setup? Any thing that might explain why this happens for you but not for others? Ryan, don't get me wrong, but isn't that a bit silly question. ;) Give me the answer for: What _is_ the _usual_ setup? ;) Specify what you expect, please. :) I expected that the update continues to work like the years before. It stopped working that day, that's the reason I filed the bug. My question is: Why all other ports work, only mercurial is bugging me? I added all log and command line trace I have. (maybe the changes from Mercurial 3 to 4?) I cleaned up my temp paths of macports and I got the following trace for the install: {{{ sudo port -v install mercurial Password: ---> Computing dependencies for mercurial. ---> Fetching distfiles for mercurial ---> 4.0.1.tar.gz does not exist in /opt/local/var/macports/distfiles/mercurial ---> Attempting to fetch 4.0.1.tar.gz from https://distfiles.macports.org/mercurial % 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 4.0.1.tar.gz from http://nue.de.distfiles.macports.org/mercurial % 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 4.0.1.tar.gz from http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/mercurial % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 264 100 264 0 0 460 0 --:--:-- --:--:-- --:--:-- 459 ---> Attempting to fetch 4.0.1.tar.gz from http://lil.fr.distfiles.macports.org/mercurial % 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 4.0.1.tar.gz from http://osl.no.distfiles.macports.org/mercurial % 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 4.0.1.tar.gz from http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/mercurial % 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 4.0.1.tar.gz from https://bitbucket.org/seanfarley/mercurial/get % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 4457k 100 4457k 0 0 1463k 0 0:00:03 0:00:03 --:--:-- 1463k ---> Verifying checksums for mercurial ---> Checksumming 4.0.1.tar.gz ---> Extracting mercurial ---> Extracting 4.0.1.tar.gz ---> Applying patches to mercurial ---> Applying patch-setup.py.diff patching file setup.py Hunk #1 succeeded at 657 with fuzz 2 (offset 187 lines). ---> Configuring mercurial ---> Building mercurial make: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_mercurial/mercurial/work/4.0.1' /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 setup.py build /Applications/Xcode.app/Contents/Developer/usr/bin/make -C doc make[1]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_mercurial/mercurial/work/4.0.1/doc' /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 gendoc.py hg-ssh.8 > hg-ssh.8.txt.tmp running build running build_mo creating mercurial/locale creating mercurial/locale/da creating mercurial/locale/da/LC_MESSAGES generating mercurial/locale/da/LC_MESSAGES/hg.mo from i18n/da.po msgfmt -v -o mercurial/locale/da/LC_MESSAGES/hg.mo i18n/da.po -c error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but "10.11" during configure make: *** [build] Error 1 make: *** Waiting for unfinished jobs.... /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 gendoc.py hg-ssh.8.gendoc > hg-ssh.8.gendoc.txt.tmp mv hg-ssh.8.gendoc.txt.tmp hg-ssh.8.gendoc.txt /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 gendoc.py common > common.txt.tmp mv hg-ssh.8.txt.tmp hg-ssh.8.txt /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 gendoc.py hg.1 > hg.1.txt.tmp mv common.txt.tmp common.txt mv hg.1.txt.tmp hg.1.txt /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 gendoc.py hg.1.gendoc > hg.1.gendoc.txt.tmp /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 gendoc.py hgignore.5 > hgignore.5.txt.tmp mv hgignore.5.txt.tmp hgignore.5.txt /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 gendoc.py hgignore.5.gendoc > hgignore.5.gendoc.txt.tmp mv hgignore.5.gendoc.txt.tmp hgignore.5.gendoc.txt /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 gendoc.py hgrc.5 > hgrc.5.txt.tmp mv hgrc.5.txt.tmp hgrc.5.txt /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 gendoc.py hgrc.5.gendoc > hgrc.5.gendoc.txt.tmp mv hgrc.5.gendoc.txt.tmp hgrc.5.gendoc.txt /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 runrst html --halt warning \ --link-stylesheet --stylesheet-path style.css hg-ssh.8.txt hg- ssh.8.html mv hg.1.gendoc.txt.tmp hg.1.gendoc.txt /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 runrst html --halt warning \ --link-stylesheet --stylesheet-path style.css hgignore.5.txt hgignore.5.html /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 runrst html --halt warning \ --link-stylesheet --stylesheet-path style.css hgrc.5.txt hgrc.5.html /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 runrst hgmanpage --halt warning \ --strip-elements-with-class htmlonly hg-ssh.8.txt hg-ssh.8 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 runrst hgmanpage --halt warning \ --strip-elements-with-class htmlonly hg.1.txt hg.1 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 runrst hgmanpage --halt warning \ --strip-elements-with-class htmlonly hgignore.5.txt hgignore.5 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 runrst hgmanpage --halt warning \ --strip-elements-with-class htmlonly hgrc.5.txt hgrc.5 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 runrst html --halt warning \ --link-stylesheet --stylesheet-path style.css hg.1.txt hg.1.html make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_mercurial/mercurial/work/4.0.1/doc' make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_mercurial/mercurial/work/4.0.1' Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_mercurial/mercurial/work/4.0.1" && make -j2 -w all PYTHON=/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 Exit code: 2 Error: org.macports.build for port mercurial returned: command execution failed Warning: targets not executed for mercurial: org.macports.activate org.macports.build org.macports.destroot org.macports.install Please see the log file for port mercurial for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_mercurial/mercurial/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port mercurial failed }}} Here the list of all installed ports (just updated): {{{ sudo port -v installed The following ports are currently installed: apache2 @2.2.31_2+preforkmpm (active) platform='darwin 15' archs='x86_64' apr @1.5.2_1 (active) platform='darwin 15' archs='x86_64' apr-util @1.5.4_0 (active) platform='darwin 15' archs='x86_64' aspell @0.60.6.1_1-nls (active) platform='darwin 15' archs='x86_64' aspell-dict-en @7.1_0 (active) platform='darwin 15' archs='noarch' at-spi2-atk @2.22.0_0 (active) platform='darwin 15' archs='x86_64' at-spi2-core @2.22.0_0 (active) platform='darwin 15' archs='x86_64' atk @2.22.0_0 (active) platform='darwin 15' archs='x86_64' autoconf @2.69_5 (active) platform='darwin 15' archs='noarch' autoconf-archive @2016.03.20_0 (active) platform='darwin 15' archs='noarch' automake @1.15_1 (active) platform='darwin 15' archs='noarch' bison @3.0.4_1 (active) platform='darwin 15' archs='x86_64' bison-runtime @3.0.4_0 (active) platform='darwin 15' archs='noarch' boost @1.59.0_2+no_single+no_static+python27 (active) platform='darwin 15' archs='x86_64' bzip2 @1.0.6_0 (active) platform='darwin 15' archs='x86_64' cairo @1.14.6_0+quartz+x11 (active) platform='darwin 15' archs='x86_64' cclient @2007f_1 (active) platform='darwin 15' archs='x86_64' clamav @0.99.2_1 (active) platform='darwin 15' archs='x86_64' cmake @3.7.1_0 (active) platform='darwin 15' archs='x86_64' coreutils @8.25_0 (active) platform='darwin 15' archs='x86_64' ctags @5.8_2 (active) platform='darwin 15' archs='x86_64' curl @7.51.0_1+ssl (active) platform='darwin 15' archs='x86_64' curl-ca-bundle @7.51.0_0 (active) platform='darwin 15' archs='noarch' cyrus-sasl2 @2.1.26_6+kerberos (active) platform='darwin 15' archs='x86_64' daq @2.0.6_0 (active) platform='darwin 15' archs='x86_64' db46 @4.6.21_10 (active) platform='darwin 15' archs='x86_64' db48 @4.8.30_4 (active) platform='darwin 15' archs='x86_64' db_select @0.1_3 (active) platform='darwin 15' archs='noarch' dbus @1.10.12_0 (active) platform='darwin 15' archs='x86_64' desktop-file-utils @0.23_0 (active) platform='darwin 15' archs='x86_64' djvulibre @3.5.27_0 (active) platform='darwin 15' archs='x86_64' docbook-xml @5.0_3 (active) platform='darwin 15' archs='noarch' docbook-xml-4.1.2 @5.0_1 (active) platform='darwin 15' archs='noarch' docbook-xml-4.2 @5.0_1 (active) platform='darwin 15' archs='noarch' docbook-xml-4.3 @5.0_1 (active) platform='darwin 15' archs='noarch' docbook-xml-4.4 @5.0_1 (active) platform='darwin 15' archs='noarch' docbook-xml-4.5 @5.0_1 (active) platform='darwin 15' archs='noarch' docbook-xml-5.0 @5.0_1 (active) platform='darwin 15' archs='noarch' docbook-xsl @1.79.1_0 (active) platform='darwin 15' archs='noarch' docker @1.12.1_0 (active) platform='darwin 15' archs='x86_64' docker-machine @0.8.1_0 (active) platform='darwin 15' archs='x86_64' e2fsprogs @1.43.3_0 (active) platform='darwin 15' archs='x86_64' ekhtml @0.3.2_0 (active) platform='darwin 15' archs='x86_64' enca @1.15_0 (active) platform='darwin 15' archs='x86_64' enchant @1.6.0_4+applespell (active) platform='darwin 15' archs='x86_64' erlang @19.1_0+hipe+ssl (active) platform='darwin 15' archs='x86_64' expat @2.2.0_0 (active) platform='darwin 15' archs='x86_64' ext2fuse @0.8.1_2 (active) platform='darwin 15' archs='x86_64' ffmpeg @3.2.2_0+gpl2+x11 (active) platform='darwin 15' archs='x86_64' fftw-3 @3.3.5_0 (active) platform='darwin 15' archs='x86_64' findutils @4.6.0_0 (active) platform='darwin 15' archs='x86_64' flac @1.3.1_2 (active) platform='darwin 15' archs='x86_64' flex @2.6.0_0 (active) platform='darwin 15' archs='x86_64' fontconfig @2.12.1_1 (active) platform='darwin 15' archs='x86_64' fop @1.1_0 (active) platform='darwin 15' archs='noarch' freeimage @3.17.0_0 (active) platform='darwin 15' archs='x86_64' freetds @1.00.21_0 (active) platform='darwin 15' archs='x86_64' freetype @2.7_0 (active) platform='darwin 15' archs='x86_64' fribidi @0.19.7_0 (active) platform='darwin 15' archs='x86_64' gawk @4.1.4_0 (active) platform='darwin 15' archs='x86_64' gd2 @2.2.3_0+x11 (active) platform='darwin 15' archs='x86_64' gdbm @1.12_0 (active) platform='darwin 15' archs='x86_64' gearmand @1.1.12_1+sqlite (active) platform='darwin 15' archs='x86_64' getopt @1.1.6_0 (active) platform='darwin 15' archs='x86_64' gettext @0.19.8.1_0 (active) platform='darwin 15' archs='x86_64' ghostscript @9.19_0+x11 (active) platform='darwin 15' archs='x86_64' giflib @4.2.3_0+x11 (active) platform='darwin 15' archs='x86_64' gindent @2.2.11_0 (active) platform='darwin 15' archs='x86_64' git @2.10.2_0+credential_osxkeychain+doc+pcre+perl5_24 (active) platform='darwin 15' archs='x86_64' glib2 @2.50.2_0 (active) platform='darwin 15' archs='x86_64' gmake @4.1_0 (active) platform='darwin 15' archs='x86_64' gmp @6.1.1_0 (active) platform='darwin 15' archs='x86_64' gnome-common @3.18.0_0 (active) platform='darwin 15' archs='noarch' gnupg @1.4.21_0 (active) platform='darwin 15' archs='x86_64' gnupg2 @2.0.30_0 (active) platform='darwin 15' archs='x86_64' gnutls @3.4.16_1 (active) platform='darwin 15' archs='x86_64' go @1.7.4_0 (active) platform='darwin 15' archs='x86_64' go-1.4 @1.4.3_0 (active) platform='darwin 15' archs='x86_64' gobject-introspection @1.50.0_0 (active) platform='darwin 15' archs='x86_64' gperf @3.0.4_2 (active) platform='darwin 15' archs='x86_64' gpg-agent @2.0.30_0+pinentry (active) platform='darwin 15' archs='x86_64' GraphicsMagick @1.3.25_1+q8 (active) platform='darwin 15' archs='x86_64' graphite2 @1.3.9_0 (active) platform='darwin 15' archs='x86_64' gsed @4.2.2_0 (active) platform='darwin 15' archs='x86_64' gtk-doc @1.25_1 (active) platform='darwin 15' archs='noarch' harfbuzz @1.3.4_0 (active) platform='darwin 15' archs='x86_64' help2man @1.47.4_1 (active) platform='darwin 15' archs='x86_64' hicolor-icon-theme @0.15_0 (active) platform='darwin 15' archs='noarch' hunspell @1.3.3_1 (active) platform='darwin 15' archs='x86_64' icu @55.1_0 (active) platform='darwin 15' archs='x86_64' ilmbase @2.2.0_0 (active) platform='darwin 15' archs='x86_64' ImageMagick @6.9.6-6_0+x11 (active) platform='darwin 15' archs='x86_64' imlib2 @1.4.9_0 (active) platform='darwin 15' archs='x86_64' intltool @0.51.0_2 (active) platform='darwin 15' archs='noarch' itstool @2.0.2_2 (active) platform='darwin 15' archs='noarch' jasper @1.900.29_0 (active) platform='darwin 15' archs='x86_64' jbig2dec @0.11_2 (active) platform='darwin 15' archs='x86_64' jbigkit @2.1_0 (active) platform='darwin 15' archs='x86_64' jpeg @9b_0 (active) platform='darwin 15' archs='x86_64' judy @1.0.5_1 (active) platform='darwin 15' archs='x86_64' kerberos5 @1.15_0 (active) platform='darwin 15' archs='x86_64' lame @3.99.5_1 (active) platform='darwin 15' archs='x86_64' lcms2 @2.8_0 (active) platform='darwin 15' archs='x86_64' libarchive @3.2.2_0 (active) platform='darwin 15' archs='x86_64' libass @0.13.4_0 (active) platform='darwin 15' archs='x86_64' libassuan @2.4.3_0 (active) platform='darwin 15' archs='x86_64' libbluray @0.9.2_0 (active) platform='darwin 15' archs='x86_64' libcomerr @1.43.3_0 (active) platform='darwin 15' archs='x86_64' libcroco @0.6.11_0 (active) platform='darwin 15' archs='x86_64' libdnet @1.12_2 (active) platform='darwin 15' archs='x86_64' libedit @20160903-3.1_1 (active) platform='darwin 15' archs='x86_64' libepoxy @1.3.1_3+python34 (active) platform='darwin 15' archs='x86_64' libesmtp @1.0.6_1 (active) platform='darwin 15' archs='x86_64' libev @4.23_0 (active) platform='darwin 15' archs='x86_64' libevent @2.0.22_3 (active) platform='darwin 15' archs='x86_64' libffi @3.2.1_0 (active) platform='darwin 15' archs='x86_64' libgcrypt @1.7.3_0 (active) platform='darwin 15' archs='x86_64' libgeoip @1.6.9_0 (active) platform='darwin 15' archs='x86_64' libgpg-error @1.25_0 (active) platform='darwin 15' archs='x86_64' libiconv @1.14_0 (active) platform='darwin 15' archs='x86_64' libid3tag @0.15.1b_2 (active) platform='darwin 15' archs='x86_64' libidn @1.33_0 (active) platform='darwin 15' archs='x86_64' libksba @1.3.5_0 (active) platform='darwin 15' archs='x86_64' libmagic @5.29_0 (active) platform='darwin 15' archs='x86_64' libmcrypt @2.5.8_1 (active) platform='darwin 15' archs='x86_64' libmemcached @1.0.10_0 (active) platform='darwin 15' archs='x86_64' libmodplug @0.8.8.5_0 (active) platform='darwin 15' archs='x86_64' libogg @1.3.2_1 (active) platform='darwin 15' archs='x86_64' libopus @1.1.3_0 (active) platform='darwin 15' archs='x86_64' libpaper @1.1.24.4_0 (active) platform='darwin 15' archs='x86_64' libpcap @1.8.1_0 (active) platform='darwin 15' archs='x86_64' libpixman @0.34.0_0 (active) platform='darwin 15' archs='x86_64' libpng @1.6.26_0 (active) platform='darwin 15' archs='x86_64' libsdl @1.2.15_3+x11 (active) platform='darwin 15' archs='x86_64' libsdl2 @2.0.5_1+x11 (active) platform='darwin 15' archs='x86_64' libsphinxclient @2.2.11_1 (active) platform='darwin 15' archs='x86_64' libssh2 @1.7.0_0 (active) platform='darwin 15' archs='x86_64' libsvm @3.20_2+java+python27+tools (active) platform='darwin 15' archs='x86_64' libtasn1 @4.9_0 (active) platform='darwin 15' archs='x86_64' libtheora @1.1.1_2 (active) platform='darwin 15' archs='x86_64' libtool @2.4.6_2 (active) platform='darwin 15' archs='x86_64' libusb @1.0.21_0 (active) platform='darwin 15' archs='x86_64' libusb-compat @0.1.5_0 (active) platform='darwin 15' archs='x86_64' libuv @1.10.1_0 (active) platform='darwin 15' archs='x86_64' libvorbis @1.3.5_0 (active) platform='darwin 15' archs='x86_64' libvpx @1.6.0_0 (active) platform='darwin 15' archs='x86_64' libxl @3.7.2.0_0 (active) platform='darwin 15' archs='x86_64' libxml2 @2.9.4_0 (active) platform='darwin 15' archs='x86_64' libxslt @1.1.29_1 (active) platform='darwin 15' archs='x86_64' libyaml @0.1.7_0 (active) platform='darwin 15' archs='x86_64' lighttpd @1.4.43_0+ssl (active) platform='darwin 15' archs='x86_64' lzo2 @2.09_0 (active) platform='darwin 15' archs='x86_64' m4 @1.4.17_0 (active) platform='darwin 15' archs='x86_64' memcached @1.4.22_0 (active) platform='darwin 15' archs='x86_64' mesa @12.0.1_2+osmesa+python27 (active) platform='darwin 15' archs='x86_64' mgzip @1.2c_1 (active) platform='darwin 15' archs='x86_64' mhash @0.9.9.9_0 (active) platform='darwin 15' archs='x86_64' ming @0.4.5_1 (active) platform='darwin 15' archs='x86_64' mysql_select @0.1.2_3 (active) platform='darwin 15' archs='noarch' ncurses @6.0_0 (active) platform='darwin 15' archs='x86_64' net-snmp @5.7.3_6+ssl (active) platform='darwin 15' archs='x86_64' nettle @3.1.1_0 (active) platform='darwin 15' archs='x86_64' nodejs4 @4.6.1_0 (active) platform='darwin 15' archs='x86_64' npm3 @3.10.9_0 (active) platform='darwin 15' archs='noarch' openexr @2.2.0_1 (active) platform='darwin 15' archs='x86_64' openjade @1.3.2_10 (active) platform='darwin 15' archs='x86_64' openjpeg @2.1.0_0 (active) platform='darwin 15' archs='x86_64' openjpeg15 @1.5.2_0 (active) platform='darwin 15' archs='x86_64' openldap @2.4.44_0 (active) platform='darwin 15' archs='x86_64' opensp @1.5.2_2 (active) platform='darwin 15' archs='x86_64' openssl @1.0.2j_0 (active) platform='darwin 15' archs='x86_64' orc @0.4.26_0 (active) platform='darwin 15' archs='x86_64' ossp-uuid @1.6.2_8+perl5_24 (active) platform='darwin 15' archs='x86_64' osxfuse @3.5.3_0 (active) platform='darwin 15' archs='x86_64' p5.16-module-corelist @5.201.512.130_0 (active) platform='darwin 15' archs='noarch' p5.24-algorithm-diff @1.190.300_0 (active) platform='darwin 15' archs='noarch' p5.24-authen-sasl @2.160.0_0 (active) platform='darwin 15' archs='noarch' p5.24-cgi @4.350.0_0 (active) platform='darwin 15' archs='noarch' p5.24-cpan-meta @2.150.10_0 (active) platform='darwin 15' archs='noarch' p5.24-cpan-meta-requirements @2.140.0_0 (active) platform='darwin 15' archs='noarch' p5.24-cpan-meta-yaml @0.18.0_0 (active) platform='darwin 15' archs='noarch' p5.24-digest-hmac @1.30.0_0 (active) platform='darwin 15' archs='noarch' p5.24-digest-sha1 @2.130.0_4 (active) platform='darwin 15' archs='x86_64' p5.24-encode @2.880.0_0 (active) platform='darwin 15' archs='x86_64' p5.24-encode-locale @1.50.0_0 (active) platform='darwin 15' archs='noarch' p5.24-error @0.170.240_0 (active) platform='darwin 15' archs='noarch' p5.24-extutils-cbuilder @0.280.224_0 (active) platform='darwin 15' archs='noarch' p5.24-file-listing @6.40.0_1 (active) platform='darwin 15' archs='noarch' p5.24-file-slurp-tiny @0.4.0_0 (active) platform='darwin 15' archs='noarch' p5.24-getopt-long @2.49.1_0 (active) platform='darwin 15' archs='noarch' p5.24-gssapi @0.280.0_3 (active) platform='darwin 15' archs='x86_64' p5.24-html-form @6.30.0_1 (active) platform='darwin 15' archs='noarch' p5.24-html-parser @3.720.0_0 (active) platform='darwin 15' archs='x86_64' p5.24-html-tagset @3.200.0_4 (active) platform='darwin 15' archs='noarch' p5.24-http-cookies @6.10.0_1 (active) platform='darwin 15' archs='noarch' p5.24-http-daemon @6.10.0_1 (active) platform='darwin 15' archs='noarch' p5.24-http-date @6.20.0_1 (active) platform='darwin 15' archs='noarch' p5.24-http-message @6.110.0_0 (active) platform='darwin 15' archs='noarch' p5.24-http-negotiate @6.10.0_1 (active) platform='darwin 15' archs='noarch' p5.24-inc-latest @0.500.0_0 (active) platform='darwin 15' archs='noarch' p5.24-io @1.250.0_4 (active) platform='darwin 15' archs='x86_64' p5.24-io-html @1.1.0_0 (active) platform='darwin 15' archs='noarch' p5.24-io-socket-inet6 @2.720.0_0 (active) platform='darwin 15' archs='noarch' p5.24-io-socket-ip @0.380.0_0 (active) platform='darwin 15' archs='noarch' p5.24-io-socket-ssl @2.39.0_0 (active) platform='darwin 15' archs='noarch' p5.24-ipc-cmd @0.960.0_0 (active) platform='darwin 15' archs='noarch' p5.24-libwww-perl @6.150.0_0+ssl (active) platform='darwin 15' archs='noarch' p5.24-locale-gettext @1.70.0_0 (active) platform='darwin 15' archs='x86_64' p5.24-locale-maketext-simple @0.210.0_3 (active) platform='darwin 15' archs='noarch' p5.24-lwp-mediatypes @6.20.0_1 (active) platform='darwin 15' archs='noarch' p5.24-lwp-protocol-https @6.60.0_1 (active) platform='darwin 15' archs='noarch' p5.24-mime-base64 @3.150.0_0 (active) platform='darwin 15' archs='x86_64' p5.24-module-build @0.422.0_1 (active) platform='darwin 15' archs='noarch' p5.24-module-load @0.320.0_1 (active) platform='darwin 15' archs='noarch' p5.24-module-load-conditional @0.680.0_0 (active) platform='darwin 15' archs='noarch' p5.24-module-metadata @1.0.33_0 (active) platform='darwin 15' archs='noarch' p5.24-mozilla-ca @20160104_0 (active) platform='darwin 15' archs='noarch' p5.24-net-http @6.90.0_0 (active) platform='darwin 15' archs='noarch' p5.24-net-libidn @0.120.0_4 (active) platform='darwin 15' archs='x86_64' p5.24-net-smtp-ssl @1.40.0_0 (active) platform='darwin 15' archs='noarch' p5.24-net-ssleay @1.780.0_0 (active) platform='darwin 15' archs='x86_64' p5.24-params-check @0.380.0_1 (active) platform='darwin 15' archs='noarch' p5.24-pathtools @3.620.0_0 (active) platform='darwin 15' archs='x86_64' p5.24-perl-ostype @1.10.0_0 (active) platform='darwin 15' archs='noarch' p5.24-pod-escapes @1.70.0_0 (active) platform='darwin 15' archs='noarch' p5.24-pod-simple @3.350.0_0 (active) platform='darwin 15' archs='noarch' p5.24-podlators @4.90.0_0 (active) platform='darwin 15' archs='noarch' p5.24-scalar-list-utils @1.460.0_0 (active) platform='darwin 15' archs='x86_64' p5.24-socket @2.24.0_0 (active) platform='darwin 15' archs='x86_64' p5.24-socket6 @0.280.0_0 (active) platform='darwin 15' archs='x86_64' p5.24-spiffy @0.460.0_0 (active) platform='darwin 15' archs='x86_64' p5.24-sub-uplevel @0.260.0_0 (active) platform='darwin 15' archs='noarch' p5.24-term-readkey @2.370.0_0 (active) platform='darwin 15' archs='x86_64' p5.24-test-base @0.880.0_0 (active) platform='darwin 15' archs='x86_64' p5.24-test-deep @1.124.0_0 (active) platform='darwin 15' archs='noarch' p5.24-test-exception @0.430.0_0 (active) platform='darwin 15' archs='noarch' p5.24-test-nowarnings @1.40.0_1 (active) platform='darwin 15' archs='noarch' p5.24-test-pod @1.510.0_0 (active) platform='darwin 15' archs='noarch' p5.24-test-simple @1.302.67_0 (active) platform='darwin 15' archs='noarch' p5.24-test-warn @0.300.0_1 (active) platform='darwin 15' archs='noarch' p5.24-test-yaml @1.60.0_0 (active) platform='darwin 15' archs='noarch' p5.24-text-diff @1.440.0_0 (active) platform='darwin 15' archs='noarch' p5.24-text-parsewords @3.300.0_0 (active) platform='darwin 15' archs='noarch' p5.24-tree-dag_node @1.290.0_0 (active) platform='darwin 15' archs='noarch' p5.24-uri @1.710.0_0 (active) platform='darwin 15' archs='noarch' p5.24-version @0.991.700_0 (active) platform='darwin 15' archs='x86_64' p5.24-www-robotrules @6.20.0_1 (active) platform='darwin 15' archs='noarch' p5.24-xml-parser @2.440.0_0 (active) platform='darwin 15' archs='x86_64' p5.24-yaml @1.200.0_0 (active) platform='darwin 15' archs='noarch' p7zip @16.02_1 (active) platform='darwin 15' archs='x86_64' p11-kit @0.23.2_1 (active) platform='darwin 15' archs='x86_64' pango @1.40.3_1+quartz+x11 (active) platform='darwin 15' archs='x86_64' pcre @8.39_0 (active) platform='darwin 15' archs='x86_64' pcre2 @10.22_0 (active) platform='darwin 15' archs='x86_64' pdflib @7.0.5_2 (active) platform='darwin 15' archs='x86_64' perl5 @5.24.0_0+perl5_24 (active) platform='darwin 15' archs='noarch' perl5.16 @5.16.3_3 (active) platform='darwin 15' archs='x86_64' perl5.22 @5.22.2_1 (active) platform='darwin 15' archs='x86_64' perl5.24 @5.24.0_0 (active) platform='darwin 15' archs='x86_64' php56 @5.6.28_0+libedit (active) platform='darwin 15' archs='x86_64' php56-apache2handler @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-APCu @4.0.11_0 (active) platform='darwin 15' archs='x86_64' php56-big_int @1.0.7_1 (active) platform='darwin 15' archs='x86_64' php56-curl @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-dba @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-dbase @5.1.1_0 (active) platform='darwin 15' archs='x86_64' php56-excel @1.0.1_1 (active) platform='darwin 15' archs='x86_64' php56-exif @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-fpm @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-FreeImage @0.1_1 (active) platform='darwin 15' archs='x86_64' php56-ftp @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-gd @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-gdchart @0.2.0_0 (active) platform='darwin 15' archs='x86_64' php56-geoip @1.0.8_1 (active) platform='darwin 15' archs='x86_64' php56-gettext @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-gmagick @1.1.7RC3_0 (active) platform='darwin 15' archs='x86_64' php56-html_parse @1.0.0_1 (active) platform='darwin 15' archs='x86_64' php56-htscanner @1.0.1_1 (active) platform='darwin 15' archs='x86_64' php56-http2 @2.5.6_0 (active) platform='darwin 15' archs='x86_64' php56-iconv @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-igbinary @1.2.1_0 (active) platform='darwin 15' archs='x86_64' php56-imagick @3.4.3RC1_0 (active) platform='darwin 15' archs='x86_64' php56-imap @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-imlib2 @0.1.00_1 (active) platform='darwin 15' archs='x86_64' php56-intl @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-ipc @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-jsmin @2.0.1_0 (active) platform='darwin 15' archs='x86_64' php56-ldap @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-libev @20131219_0 (active) platform='darwin 15' archs='x86_64' php56-libevent @0.1.0_0 (active) platform='darwin 15' archs='x86_64' php56-lzf @1.6.5_0 (active) platform='darwin 15' archs='x86_64' php56-magickwand @1.0.9-2_1 (active) platform='darwin 15' archs='x86_64' php56-mailparse @2.1.6_1 (active) platform='darwin 15' archs='x86_64' php56-mbstring @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-mcrypt @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-memcached @2.1.0_1 (active) platform='darwin 15' archs='x86_64' php56-ming @0.4.5_0 (active) platform='darwin 15' archs='x86_64' php56-mysql @5.6.28_0+mysqlnd (active) platform='darwin 15' archs='x86_64' php56-oauth @1.2.3_0 (active) platform='darwin 15' archs='x86_64' php56-odbc @5.6.28_0+unixodbc (active) platform='darwin 15' archs='x86_64' php56-opcache @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-openssl @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-pcntl @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-pdflib @3.0.4_0 (active) platform='darwin 15' archs='x86_64' php56-pear @20161027_0 (active) platform='darwin 15' archs='x86_64' php56-pop3 @1.0.2_1 (active) platform='darwin 15' archs='x86_64' php56-posix @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-postgresql @5.6.28_0+postgresql94 (active) platform='darwin 15' archs='x86_64' php56-propro @1.0.2_0 (active) platform='darwin 15' archs='x86_64' php56-pspell @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-raphf @1.1.2_0 (active) platform='darwin 15' archs='x86_64' php56-rar @3.0.2_0 (active) platform='darwin 15' archs='x86_64' php56-scrypt @1.4.2_0 (active) platform='darwin 15' archs='x86_64' php56-snmp @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-soap @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-sockets @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-solr @2.4.0_0 (active) platform='darwin 15' archs='x86_64' php56-sqlite @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-ssh2 @0.13_0 (active) platform='darwin 15' archs='x86_64' php56-suhosin @0.9.38_0 (active) platform='darwin 15' archs='x86_64' php56-tidy @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php56-uploadprogress @1.0.3.1_1 (active) platform='darwin 15' archs='x86_64' php56-uuid @1.0.4_0 (active) platform='darwin 15' archs='x86_64' php56-xdebug @2.5.0_0 (active) platform='darwin 15' archs='x86_64' php56-yaml @1.3.0_0 (active) platform='darwin 15' archs='x86_64' php56-yaz @1.2.1_0 (active) platform='darwin 15' archs='x86_64' php56-zip @5.6.28_0 (active) platform='darwin 15' archs='x86_64' php70 @7.0.13_0+libedit (active) platform='darwin 15' archs='x86_64' php70-apache2handler @7.0.13_0 (active) platform='darwin 15' archs='x86_64' php70-mysql @7.0.13_0+mysqlnd (active) platform='darwin 15' archs='x86_64' php70-sqlite @7.0.13_0 (active) platform='darwin 15' archs='x86_64' php70-xdebug @2.5.0_0 (active) platform='darwin 15' archs='x86_64' php71 @7.1.0_0+libedit (active) platform='darwin 15' archs='x86_64' php71-apache2handler @7.1.0_0 (active) platform='darwin 15' archs='x86_64' php71-calendar @7.1.0_0 (active) platform='darwin 15' archs='x86_64' php71-cgi @7.1.0_0 (active) platform='darwin 15' archs='x86_64' php71-curl @7.1.0_0 (active) platform='darwin 15' archs='x86_64' php71-dba @7.1.0_0 (active) platform='darwin 15' archs='x86_64' php71-enchant @7.1.0_0 (active) platform='darwin 15' archs='x86_64' php71-exif @7.1.0_0 (active) platform='darwin 15' archs='x86_64' php71-fpm @7.1.0_0 (active) platform='darwin 15' archs='x86_64' php71-ftp @7.1.0_0 (active) platform='darwin 15' archs='x86_64' php71-gd @7.1.0_0 (active) platform='darwin 15' archs='x86_64' php71-gettext @7.1.0_0 (active) platform='darwin 15' archs='x86_64' php71-gmp @7.1.0_0 (active) platform='darwin 15' archs='x86_64' php71-iconv @7.1.0_0 (active) platform='darwin 15' archs='x86_64' php71-imap @7.1.0_0 (active) platform='darwin 15' archs='x86_64' php71-intl @7.1.0_0 (active) platform='darwin 15' archs='x86_64' php71-ipc @7.1.0_0 (active) platform='darwin 15' archs='x86_64' php71-ldap @7.1.0_0 (active) platform='darwin 15' archs='x86_64' php71-mbstring @7.1.0_0 (active) platform='darwin 15' archs='x86_64' php71-mcrypt @7.1.0_0 (active) platform='darwin 15' archs='x86_64' php71-mysql @7.1.0_0+mysqlnd (active) platform='darwin 15' archs='x86_64' php71-odbc @7.1.0_0+unixodbc (active) platform='darwin 15' archs='x86_64' php71-opcache @7.1.0_0 (active) platform='darwin 15' archs='x86_64' php71-openssl @7.1.0_0 (active) platform='darwin 15' archs='x86_64' php_select @1.0_0 (active) platform='darwin 15' archs='noarch' pinentry @0.9.7_0 (active) platform='darwin 15' archs='x86_64' pkgconfig @0.29.1_0 (active) platform='darwin 15' archs='x86_64' popt @1.16_0 (active) platform='darwin 15' archs='x86_64' port_cutleaves @0.1.4_0 (active) platform='darwin 15' archs='noarch' postgresql94 @9.4.10_0 (active) platform='darwin 15' archs='x86_64' postgresql_select @0.2_0 (active) platform='darwin 15' archs='noarch' pth @2.0.7_1 (active) platform='darwin 15' archs='x86_64' py27-beaker @1.7.0_0 (active) platform='darwin 15' archs='noarch' py27-docutils @0.12_0 (active) platform='darwin 15' archs='noarch' py27-libxml2 @2.9.4_0 (active) platform='darwin 15' archs='x86_64' py27-mako @1.0.6_0 (active) platform='darwin 15' archs='noarch' py27-markupsafe @0.23_0 (active) platform='darwin 15' archs='x86_64' py27-roman @2.0.0_0 (active) platform='darwin 15' archs='noarch' py27-setuptools @30.2.0_0 (active) platform='darwin 15' archs='noarch' python2_select @0.0_2 (active) platform='darwin 15' archs='noarch' python3_select @0.0_1 (active) platform='darwin 15' archs='noarch' python27 @2.7.12_2 (active) platform='darwin 15' archs='x86_64' python34 @3.4.5_1 (active) platform='darwin 15' archs='x86_64' python_select @0.3_7 (active) platform='darwin 15' archs='noarch' rabbitmq-c @0.8.0_0 (active) platform='darwin 15' archs='x86_64' re2c @0.14.3_0 (active) platform='darwin 15' archs='x86_64' readline @6.3.003_1 (active) platform='darwin 15' archs='x86_64' repo @1.22_0 (active) platform='darwin 15' archs='noarch' rrdtool @1.5.5_1 (active) platform='darwin 15' archs='x86_64' rsync @3.1.2_0 (active) platform='darwin 15' archs='x86_64' schroedinger @1.0.11_0 (active) platform='darwin 15' archs='x86_64' scons @2.5.1_0 (active) platform='darwin 15' archs='noarch' serf1 @1.3.8_0 (active) platform='darwin 15' archs='x86_64' shared-mime-info @1.7_2 (active) platform='darwin 15' archs='x86_64' source-highlight @3.1.8_0 (active) platform='darwin 15' archs='x86_64' soxr @0.1.2_0 (active) platform='darwin 15' archs='x86_64' spawn-fcgi @1.6.4_0 (active) platform='darwin 15' archs='x86_64' speex @1.2rc2_0 (active) platform='darwin 15' archs='x86_64' sqlite3 @3.15.2_2 (active) platform='darwin 15' archs='x86_64' subversion @1.9.5_0 (active) platform='darwin 15' archs='x86_64' tcl @8.6.6_0+corefoundation+threads (active) platform='darwin 15' archs='x86_64' tcp_wrappers @20_2 (active) platform='darwin 15' archs='x86_64' texi2html @5.0_1 (active) platform='darwin 15' archs='noarch' texinfo @6.3_0 (active) platform='darwin 15' archs='x86_64' tidy @5.2.0_0 (active) platform='darwin 15' archs='x86_64' tiff @4.0.7_0 (active) platform='darwin 15' archs='x86_64' unixODBC @2.3.2_0 (active) platform='darwin 15' archs='x86_64' urw-fonts @1.0.7pre44_0 (active) platform='darwin 15' archs='noarch' vala @0.34.4_0 (active) platform='darwin 15' archs='x86_64' webp @0.5.1_2 (active) platform='darwin 15' archs='x86_64' wget @1.18_1+ssl (active) platform='darwin 15' archs='x86_64' x264 @20161201_0 (active) platform='darwin 15' archs='x86_64' x265 @2.1_0 (active) platform='darwin 15' archs='x86_64' Xft2 @2.3.2_0 (active) platform='darwin 15' archs='x86_64' xmlcatmgr @2.2_1 (active) platform='darwin 15' archs='x86_64' xmlto @0.0.28_0 (active) platform='darwin 15' archs='x86_64' xorg-bigreqsproto @1.1.2_0 (active) platform='darwin 15' archs='noarch' xorg-compositeproto @0.4.2_0 (active) platform='darwin 15' archs='noarch' xorg-damageproto @1.2.1_0 (active) platform='darwin 15' archs='noarch' xorg-dri2proto @2.8_0 (active) platform='darwin 15' archs='noarch' xorg-fixesproto @5.0_0 (active) platform='darwin 15' archs='noarch' xorg-glproto @1.4.17_0 (active) platform='darwin 15' archs='noarch' xorg-inputproto @2.3.2_0 (active) platform='darwin 15' archs='noarch' xorg-kbproto @1.0.7_0 (active) platform='darwin 15' archs='noarch' xorg-libice @1.0.9_0 (active) platform='darwin 15' archs='x86_64' xorg-libpthread-stubs @0.3_0 (active) platform='darwin 15' archs='noarch' xorg-libsm @1.2.1_0 (active) platform='darwin 15' archs='x86_64' xorg-libX11 @1.6.4_0 (active) platform='darwin 15' archs='x86_64' xorg-libXau @1.0.8_0 (active) platform='darwin 15' archs='x86_64' xorg-libxcb @1.12_2+python27 (active) platform='darwin 15' archs='x86_64' xorg-libXcomposite @0.4.4_0 (active) platform='darwin 15' archs='x86_64' xorg-libXcursor @1.1.14_0 (active) platform='darwin 15' archs='x86_64' xorg-libXdamage @1.1.4_0 (active) platform='darwin 15' archs='x86_64' xorg-libXdmcp @1.1.2_0 (active) platform='darwin 15' archs='x86_64' xorg-libXext @1.3.3_0 (active) platform='darwin 15' archs='x86_64' xorg-libXfixes @5.0.3_0 (active) platform='darwin 15' archs='x86_64' xorg-libXi @1.7.8_0 (active) platform='darwin 15' archs='x86_64' xorg-libXinerama @1.1.3_0 (active) platform='darwin 15' archs='x86_64' xorg-libXmu @1.1.2_0 (active) platform='darwin 15' archs='x86_64' xorg-libXrandr @1.5.1_0 (active) platform='darwin 15' archs='x86_64' xorg-libXScrnSaver @1.2.2_0 (active) platform='darwin 15' archs='x86_64' xorg-libXt @1.1.5_1 (active) platform='darwin 15' archs='x86_64' xorg-libXtst @1.2.3_0 (active) platform='darwin 15' archs='x86_64' xorg-libXxf86vm @1.1.4_0 (active) platform='darwin 15' archs='x86_64' xorg-randrproto @1.5.0_0 (active) platform='darwin 15' archs='noarch' xorg-recordproto @1.14.2_0 (active) platform='darwin 15' archs='noarch' xorg-renderproto @0.11.1_0 (active) platform='darwin 15' archs='noarch' xorg-scrnsaverproto @1.2.2_0 (active) platform='darwin 15' archs='noarch' xorg-util-macros @1.19.0_0 (active) platform='darwin 15' archs='noarch' xorg-xcb-proto @1.12_1+python27 (active) platform='darwin 15' archs='noarch' xorg-xcb-util @0.4.0_0 (active) platform='darwin 15' archs='x86_64' xorg-xcmiscproto @1.2.2_0 (active) platform='darwin 15' archs='noarch' xorg-xextproto @7.3.0_0 (active) platform='darwin 15' archs='noarch' xorg-xf86bigfontproto @1.2.0_0 (active) platform='darwin 15' archs='noarch' xorg-xf86vidmodeproto @2.3.1_0 (active) platform='darwin 15' archs='noarch' xorg-xineramaproto @1.2.1_0 (active) platform='darwin 15' archs='noarch' xorg-xproto @7.0.31_0 (active) platform='darwin 15' archs='noarch' xorg-xtrans @1.3.5_0 (active) platform='darwin 15' archs='noarch' xpm @3.5.11_0 (active) platform='darwin 15' archs='x86_64' xrender @0.9.10_0 (active) platform='darwin 15' archs='x86_64' XviD @1.3.4_0 (active) platform='darwin 15' archs='x86_64' xz @5.2.2_0 (active) platform='darwin 15' archs='x86_64' yasm @1.3.0_0 (active) platform='darwin 15' archs='x86_64' yaz @5.16.0_0 (active) platform='darwin 15' archs='x86_64' zlib @1.2.8_0 (active) platform='darwin 15' archs='x86_64' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 12:18:59 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 12:18:59 -0000 Subject: [MacPorts] #52791: port reclaim: keeps asking for permission to remove dependencies of inactive ports In-Reply-To: <042.a815cac96259f4faf06d6efcb254fa70@macports.org> References: <042.a815cac96259f4faf06d6efcb254fa70@macports.org> Message-ID: <057.a305e5b626c772ad2e7a71e18bceac8c@macports.org> #52791: port reclaim: keeps asking for permission to remove dependencies of inactive ports ---------------------+-------------------------------- Reporter: mojca | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: | Keywords: Port: | ---------------------+-------------------------------- Comment (by jmroot): This message doesn't come from reclaim but from registry::check_dependents. Reclaim should probably pre-sort the inactive ports into dependency order like 'port uninstall' does. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 12:33:17 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 12:33:17 -0000 Subject: [MacPorts] #53015: octave-octclip, octave-octproj: missing patch file In-Reply-To: <048.be8fb1f67e3eed30df7100ac0090b392@macports.org> References: <048.be8fb1f67e3eed30df7100ac0090b392@macports.org> Message-ID: <063.82696e420eabe446d99b669fc05dfdb2@macports.org> #53015: octave-octclip, octave-octproj: missing patch file --------------------------------------------+------------------------------ Reporter: Schamschula | Owner: MarcusCalhoun- | Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: octave-octclip octave-octproj | --------------------------------------------+------------------------------ Changes (by Schamschula): * Attachment "octave-octclip-main.log.gz" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 12:33:27 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 12:33:27 -0000 Subject: [MacPorts] #53015: octave-octclip, octave-octproj: missing patch file In-Reply-To: <048.be8fb1f67e3eed30df7100ac0090b392@macports.org> References: <048.be8fb1f67e3eed30df7100ac0090b392@macports.org> Message-ID: <063.5c07d002141386c66516498675b96d34@macports.org> #53015: octave-octclip, octave-octproj: missing patch file --------------------------------------------+------------------------------ Reporter: Schamschula | Owner: MarcusCalhoun- | Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: octave-octclip octave-octproj | --------------------------------------------+------------------------------ Changes (by Schamschula): * Attachment "octave-octproj-main.log.gz" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 12:34:15 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 12:34:15 -0000 Subject: [MacPorts] #53015: octave-octclip, octave-octproj: missing patch file In-Reply-To: <048.be8fb1f67e3eed30df7100ac0090b392@macports.org> References: <048.be8fb1f67e3eed30df7100ac0090b392@macports.org> Message-ID: <063.81c269cc7f8f11affa3704f082aa94d1@macports.org> #53015: octave-octclip, octave-octproj: missing patch file --------------------------------------------+------------------------------ Reporter: Schamschula | Owner: MarcusCalhoun- | Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: octave-octclip octave-octproj | --------------------------------------------+------------------------------ Comment (by Schamschula): Here are the Sierra logs for octave-octclip and octave-octproj. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 14:11:40 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 14:11:40 -0000 Subject: [MacPorts] #52791: port reclaim: keeps asking for permission to remove dependencies of inactive ports In-Reply-To: <042.a815cac96259f4faf06d6efcb254fa70@macports.org> References: <042.a815cac96259f4faf06d6efcb254fa70@macports.org> Message-ID: <057.24516912dc9341d6ac4ab02981c115b6@macports.org> #52791: port reclaim: keeps asking for permission to remove dependencies of inactive ports ---------------------+-------------------------------- Reporter: mojca | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: fixed | Keywords: Port: | ---------------------+-------------------------------- Changes (by jmroot): * status: new => closed * resolution: => fixed Comment: In [changeset:"ea850b224bf886c7d3e29dc05bc84b4336b08767/macports-base" ea850b2/macports-base]: {{{ #!ConfigurableCommitTicketReference repository="macports-base" revision="ea850b224bf886c7d3e29dc05bc84b4336b08767" Uninstall in correct order in reclaim Sort inactive ports into dependency order before uninstalling, since some of them may depend on others. Also display version information as well as port names, as there may be more than one inactive version of any given port. Fixes: https://trac.macports.org/ticket/52791 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 14:20:00 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 14:20:00 -0000 Subject: [MacPorts] #53018: mercurial @4.0.1: error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but "10.11" during configure In-Reply-To: <042.20cc68d2a5b85e3ef4bb92ae1dd59d73@macports.org> References: <042.20cc68d2a5b85e3ef4bb92ae1dd59d73@macports.org> Message-ID: <057.d8daedfbb0fbfa64d09b3e8600db9428@macports.org> #53018: mercurial @4.0.1: error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but "10.11" during configure ------------------------+------------------------ Reporter: yabba | Owner: seanfarley Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: mercurial | ------------------------+------------------------ Comment (by raimue): Replying to [comment:3 yabba]: > Give me the answer for: What _is_ the _usual_ setup? ;) > Specify what you expect, please. :) > > I expected that the update continues to work like the years before. It stopped working that day, that's the reason I filed the bug. If we cannot reproduce the problem, we need your input what would be different on your system that is causing the problem. For example, did you ever make any changes to your macports.conf? Setting `macosx_deployment_target` in macports.conf would be something that could cause this. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 14:21:14 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 14:21:14 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports Message-ID: <042.21ff840f0fef05e892d836e1deca028c@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------+------------------------------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux-gnueabi- | binutils arm-rtems-binutils avr-binutils i386 | -elf-binutils i386-mingw32-binutils i386-rtems- | binutils i960-rtems-binutils lm32-rtems- | binutils m68k-elf-binutils m68k-rtems-binutils | mips-elf-binutils mips-rtems-binutils mipsel- | linux-binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils -------------------------+------------------------------------------------- I just noticed that when using the crossbinutils PortGroup, one ends up with: {{{ /opt/local/${target}/host/lib/libiberty.a /opt/local/include/libiberty/*.h }}} The first one is not problematic, but files under `$prefix/include` are because any given binutils port would install that. I found a related commit: * https://github.com/macports/macports- ports/commit/bcdf26e5b403a4291f3c241f19e33eb86d7ca538 Judging from the fact that bfd installs {{{ /opt/local/${host}/bin/ld.bfd /opt/local/${host}/host/include/*.h /opt/local/${host}/host/lib/libbfd.a /opt/local/${host}/host/lib/libbfd.la }}} I guess that some recent update of binutils broke the `reinplace` patch. This requires: * a patch in the portgroup to fix the problem * a revbump (or ideally upgrade) of all affected `*-binutils` ports * probably a bit more testing with a couple of different binutils versions Maybe the older versions are not even affected and a fix would break older ports, I'm not sure. Existing binutils ports: || arm-aout-binutils || @2.22 || || arm-elf-binutils || @2.25 || || arm-none-eabi-binutils || @2.23.1 || || arm-none-linux-gnueabi-binutils || @2005q3-2 || || arm-rtems-binutils || @2.18 || || avr-binutils || @2.27 || || i386-elf-binutils || @2.23.1 || || i386-mingw32-binutils || @2.21-3 || || i386-rtems-binutils || @2.18 || || i960-rtems-binutils || @2.16.1 || || lm32-rtems-binutils || @2.21.1 || || m68k-elf-binutils || @2.17 || || m68k-rtems-binutils || @2.18 || || mips-elf-binutils || @2.17 || || mips-rtems-binutils || @2.18 || || mipsel-linux-binutils || @2.16.1 || || msp430-binutils || @2.21.1a-20120406 || || powerpc-rtems-binutils || @2.18 || || ppc-linux-binutils || @2.25 || || sh-rtems-binutils || @2.18 || || sparc-rtems-binutils || @2.18 || || spu-binutils || @2.20.51.0.5 || || x86_64-elf-binutils || @2.23.1 || See also #51935. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 15:11:48 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 15:11:48 -0000 Subject: [MacPorts] #53021: octave @4.2.0_1: Another build failure In-Reply-To: <041.a9100f410b771f7245060d742521900f@macports.org> References: <041.a9100f410b771f7245060d742521900f@macports.org> Message-ID: <056.88a750a296a2bfb863f49de7762fc6f1@macports.org> #53021: octave @4.2.0_1: Another build failure ---------------------+--------------------------------- Reporter: mf2k | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: octave | ---------------------+--------------------------------- Comment (by mf2k): I have the latest CLT installed for El Capitan. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 15:36:36 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 15:36:36 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.16c224c79780d66f376c7d09148faab8@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Changes (by mojca): * Attachment "crossbinutils-1.0.tcl.diff" added. An attempt of a patch for libiberty in crossbinutils -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 15:39:41 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 15:39:41 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.1588cc9b98e8cc2e517f1abca7a47d55@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Comment (by mojca): I attached a patch that seems to fix the issue with headers. The second section (adding `/`) is optional. Aljaž, are you willing to test? One problem with the existing `reinplace` is that one ends up with {{{ "libdir="/opt/local/i686-w64-mingw32/host/lib"" }}} even though I didn't spot any real problem with that. This can be fixed later if needed. I was hoping that {{{ reinplace "s|@libdir@|\"${prefix}/${crossbinutils.target}/host/lib\"|g" \ ${worksrcpath}/libiberty/Makefile.in }}} would work in a cleaner way, but it doesn't seem to. I need to learn more about `Makefile` syntax. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 16:20:27 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 16:20:27 -0000 Subject: [MacPorts] #53018: mercurial @4.0.1: error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but "10.11" during configure In-Reply-To: <042.20cc68d2a5b85e3ef4bb92ae1dd59d73@macports.org> References: <042.20cc68d2a5b85e3ef4bb92ae1dd59d73@macports.org> Message-ID: <057.6717a4da04351aab8b3cec2af74ff9b3@macports.org> #53018: mercurial @4.0.1: error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but "10.11" during configure ------------------------+------------------------ Reporter: yabba | Owner: seanfarley Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: mercurial | ------------------------+------------------------ Comment (by yabba): Replying to [comment:4 raimue]: > Replying to [comment:3 yabba]: > > Give me the answer for: What _is_ the _usual_ setup? ;) > > Specify what you expect, please. :) > > > > I expected that the update continues to work like the years before. It stopped working that day, that's the reason I filed the bug. > > If we cannot reproduce the problem, we need your input what would be different on your system that is causing the problem. For example, did you ever make any changes to your macports.conf? Setting `macosx_deployment_target` in macports.conf would be something that could cause this. OK, I tried to compile darktable. They say, one need to change some options ("https://redmine.darktable.org/projects/darktable/wiki/Darktable_on_OS_X"): Add to /opt/local/etc/macports/variants.conf {{{ +no_gnome +no_x11 +quartz -x11 +llvm34 +gtk3 }}} Add to /opt/local/etc/macports/macports.conf {{{ buildfromsource always cxx_stdlib libc++ macosx_deployment_target 10.9 }}} Thanks to your hint with `macosx_deployment_target`, I commented that line and it passes. :) I'm not in that macports building processes, but should the darktable build process use the cleaner way to set those options by the/a makefile? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 16:31:45 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 16:31:45 -0000 Subject: [MacPorts] #53014: kdevelop @4.7.3: update to 5.0.3 In-Reply-To: <041.415ac91263c87097e3134109438f89e2@macports.org> References: <041.415ac91263c87097e3134109438f89e2@macports.org> Message-ID: <056.860902e509647fbef879439ad7645d64@macports.org> #53014: kdevelop @4.7.3: update to 5.0.3 -----------------------+-------------------- Reporter: l2dy | Owner: Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: wontfix | Keywords: Port: kdevelop | -----------------------+-------------------- Changes (by NicosPavlov): * status: new => closed * resolution: => wontfix Comment: KDevelop version 5 is based based on KF5, which is not (yet) available on macports. This is the reason why kdevelop is left at version 4.7.3, which is the last one based on KDE4. Surely if KF5 is added to Macports, an additional port for kdevelop 5 could be added. Setting as wontfix for now as the required dependencies are not available. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 16:48:42 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 16:48:42 -0000 Subject: [MacPorts] #52217: make test fails on Snow Leopard: Total:hasGit In-Reply-To: <047.b0fcd4b2f9a9bf36091afb6ac2188b2f@macports.org> References: <047.b0fcd4b2f9a9bf36091afb6ac2188b2f@macports.org> Message-ID: <062.1532488a48050cabe4e1e1f6b7154428@macports.org> #52217: make test fails on Snow Leopard: Total:hasGit -------------------------+-------------------------------- Reporter: ryandesign | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: MacPorts 2.4.0 Component: base | Version: 2.3.99 Resolution: fixed | Keywords: snowleopard Port: | -------------------------+-------------------------------- Changes (by jmroot): * status: new => closed * resolution: => fixed Comment: In [changeset:"e07abc87b9c75e19de3611e1750304f5eb192e7b/macports-base" e07abc8/macports-base]: {{{ #!ConfigurableCommitTicketReference repository="macports-base" revision="e07abc87b9c75e19de3611e1750304f5eb192e7b" Fix test.tcl parsing of test output This could not handle tests with more than one constraint at all. Fixes: https://trac.macports.org/ticket/52217 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 16:49:56 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 16:49:56 -0000 Subject: [MacPorts] #52217: make test fails on Snow Leopard: Total:hasGit In-Reply-To: <047.b0fcd4b2f9a9bf36091afb6ac2188b2f@macports.org> References: <047.b0fcd4b2f9a9bf36091afb6ac2188b2f@macports.org> Message-ID: <062.d791b93d5929dd7f5cc0e752af0b0260@macports.org> #52217: make test fails on Snow Leopard: Total:hasGit -------------------------+-------------------------------- Reporter: ryandesign | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: fixed | Keywords: snowleopard Port: | -------------------------+-------------------------------- Changes (by jmroot): * milestone: MacPorts 2.4.0 => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 17:33:56 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 17:33:56 -0000 Subject: [MacPorts] #52973: add setting to allow main.log truncation In-Reply-To: <041.7fb10d8cd0fb0e25d106db000eff129a@macports.org> References: <041.7fb10d8cd0fb0e25d106db000eff129a@macports.org> Message-ID: <056.f2b986062ad71e6ab95feea415abdfa1@macports.org> #52973: add setting to allow main.log truncation --------------------------+----------------- Reporter: RJVB | Owner: Type: enhancement | Status: new Priority: Low | Milestone: Component: base | Version: Resolution: | Keywords: Port: | --------------------------+----------------- Changes (by kurthindenburg): * cc: kurthindenburg (added) Comment: I find this change to be annoying as well - it just causes you to have to remember to do a 'port clean' to avoid previous errors in the log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 17:52:47 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 17:52:47 -0000 Subject: [MacPorts] #53028: py-pyqt5 variant typos Message-ID: <046.502886aeb4b0452ffeaf206e61da1045@macports.org> #53028: py-pyqt5 variant typos --------------------------------------+---------------------- Reporter: jjstickel | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch py-spyder-devel | Port: py-pyqt5 --------------------------------------+---------------------- The py-pyqt5 portfile has a couple typos related to the webengine variant. These are fixed by the attached patch. I discovered these when installing py35-spyder-devel for the first time. Spyder will not start without the webengine variant. Perhaps the py- spyder-devel Portfile should check for it and warn the user if it was not set? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 17:53:22 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 17:53:22 -0000 Subject: [MacPorts] #53028: py-pyqt5 variant typos In-Reply-To: <046.502886aeb4b0452ffeaf206e61da1045@macports.org> References: <046.502886aeb4b0452ffeaf206e61da1045@macports.org> Message-ID: <061.b5383ab36be76c714166a42ba5829147@macports.org> #53028: py-pyqt5 variant typos ------------------------+-------------------------------------- Reporter: jjstickel | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch py-spyder-devel Port: py-pyqt5 | ------------------------+-------------------------------------- Changes (by jjstickel): * Attachment "py-pyqt5_Portfile.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 18:07:15 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 18:07:15 -0000 Subject: [MacPorts] #53016: octave @4.2.0_1 build failure In-Reply-To: <047.6f5926dce6c29e418e3b19edf4dea9f0@macports.org> References: <047.6f5926dce6c29e418e3b19edf4dea9f0@macports.org> Message-ID: <062.26d9be02b9bbac0290a8795f75d7b1ba@macports.org> #53016: octave @4.2.0_1 build failure -------------------------+--------------------------------- Reporter: ryandesign | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.99 Resolution: | Keywords: Port: octave | -------------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): The first error that occurs is the configure script's inability to find a working arrack: {{{:info:configure checking whether the arpack library works... no}}}.[[BR]] This might be a symptom of the same problem that eventually prevents octave from building.[[BR]] Does the config.log offer any clues as to why arparck can't be found? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 18:58:04 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 18:58:04 -0000 Subject: [MacPorts] #53028: py-pyqt5 variant typos In-Reply-To: <046.502886aeb4b0452ffeaf206e61da1045@macports.org> References: <046.502886aeb4b0452ffeaf206e61da1045@macports.org> Message-ID: <061.c6ba6efd7a4e2a15688d69f94c6f915c@macports.org> #53028: py-pyqt5 variant typos ------------------------+---------------------- Reporter: jjstickel | Owner: mamoll Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: py-pyqt5 | ------------------------+---------------------- Changes (by ryandesign): * status: new => assigned * owner: => mamoll * keywords: haspatch py-spyder-devel => haspatch * cc: mmoll@… (removed) Comment: > The py-pyqt5 portfile has a couple typos related to the webengine variant. These are fixed by the attached patch. These changes look correct to me. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 18:58:19 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 18:58:19 -0000 Subject: [MacPorts] #53026: nodejs6 and npm4 needs update In-Reply-To: <050.c534650540f9311476383ef1b7981727@macports.org> References: <050.c534650540f9311476383ef1b7981727@macports.org> Message-ID: <065.224cc35b33cbd81ec6c07f2f412b0ede@macports.org> #53026: nodejs6 and npm4 needs update ----------------------------+---------------------- Reporter: luc-j-bourhis | Owner: ci42 Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: nodejs | ----------------------------+---------------------- Changes (by ryandesign): * cc: ci42 (removed) * status: new => assigned * owner: => ci42 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 19:06:48 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 19:06:48 -0000 Subject: [MacPorts] #51452: nco @4.5.2_2 +accelerate build failure In-Reply-To: <058.bd17aacc709b51d1ddf7411ac72bef14@macports.org> References: <058.bd17aacc709b51d1ddf7411ac72bef14@macports.org> Message-ID: <073.84226b07270c9871ad65f1e6da5bff70@macports.org> #51452: nco @4.5.2_2 +accelerate build failure -----------------------------+---------------------- Reporter: gryphon.csd8@… | Owner: tenomoto Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: nco | -----------------------------+---------------------- Comment (by jonathanlilly): I had this problem and found an easier solution. After first using MacPorts to manually install the dependencies as described here http://nco.sourceforge.net/#bld_macports, then the MacPorts nco install worked fine. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 19:49:12 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 19:49:12 -0000 Subject: [MacPorts] #53016: octave @4.2.0_1 build failure In-Reply-To: <047.6f5926dce6c29e418e3b19edf4dea9f0@macports.org> References: <047.6f5926dce6c29e418e3b19edf4dea9f0@macports.org> Message-ID: <062.fe2c981041a59f972a6608f0f706e820@macports.org> #53016: octave @4.2.0_1 build failure -------------------------+--------------------------------- Reporter: ryandesign | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.99 Resolution: | Keywords: Port: octave | -------------------------+--------------------------------- Comment (by ryandesign): Thanks for the pointer. Indeed the config.log says: {{{ dyld: Library not loaded: /opt/local/lib/libgcc/libgfortran.3.dylib Referenced from: /opt/local/lib/libarpack.2.dylib Reason: image not found ./configure: line 3803: 95270 Trace/BPT trap: 5 ./conftest$ac_exeext }}} I am using libgcc-devel @7-20161204, and it provides libgfortran.4.dylib instead of libgfortran.3.dylib. So I guess once gcc7 becomes stable and libgcc is updated to that version, we'll have to revbump anything linking with libgfortran.3.dylib. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 19:49:39 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 19:49:39 -0000 Subject: [MacPorts] #53016: octave @4.2.0_1 build failure In-Reply-To: <047.6f5926dce6c29e418e3b19edf4dea9f0@macports.org> References: <047.6f5926dce6c29e418e3b19edf4dea9f0@macports.org> Message-ID: <062.ec1f3ddbc5098e56a6e325f47cb50f83@macports.org> #53016: octave @4.2.0_1 build failure -------------------------+--------------------------------- Reporter: ryandesign | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.99 Resolution: | Keywords: Port: octave | -------------------------+--------------------------------- Changes (by ryandesign): * Attachment "config.log.bz2" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 19:56:42 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 19:56:42 -0000 Subject: [MacPorts] #52902: uhd: Add python 3.5 In-Reply-To: <041.731bd138773a8181e00d6561842cac36@macports.org> References: <041.731bd138773a8181e00d6561842cac36@macports.org> Message-ID: <056.1a37f26b8ea89c3ef023202de75eb1e5@macports.org> #52902: uhd: Add python 3.5 --------------------------+----------------------- Reporter: mf2k | Owner: michaelld Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: uhd | --------------------------+----------------------- Comment (by michaelld): In [changeset:"a53525e95893fa14ae994c1cfb74e6757312c42e/macports-ports" a53525e9/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="a53525e95893fa14ae994c1cfb74e6757312c42e" uhd*: add experimental +python35 variant; addresses ticket https://trac.macports.org/ticket/52902 . }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 19:58:00 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 19:58:00 -0000 Subject: [MacPorts] #52902: uhd: Add python 3.5 In-Reply-To: <041.731bd138773a8181e00d6561842cac36@macports.org> References: <041.731bd138773a8181e00d6561842cac36@macports.org> Message-ID: <056.73f9894cf5453a5ac73f310091e66366@macports.org> #52902: uhd: Add python 3.5 --------------------------+----------------------- Reporter: mf2k | Owner: michaelld Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: uhd | --------------------------+----------------------- Changes (by michaelld): * status: new => closed * resolution: => fixed Comment: I went ahead and committed this change as "experimental"; it might work for someone else. Worst case is another ticket is opened with this variant failing (as I found it does) & I'll push it upstream to get fixed (and/or have me try to fix it). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 20:00:23 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 20:00:23 -0000 Subject: [MacPorts] #53018: mercurial @4.0.1: error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but "10.11" during configure In-Reply-To: <042.20cc68d2a5b85e3ef4bb92ae1dd59d73@macports.org> References: <042.20cc68d2a5b85e3ef4bb92ae1dd59d73@macports.org> Message-ID: <057.a51a8911fce562095c287bd57317e416@macports.org> #53018: mercurial @4.0.1: error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but "10.11" during configure ------------------------+------------------------ Reporter: yabba | Owner: seanfarley Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: mercurial | ------------------------+------------------------ Comment (by mf2k): Note that no ports have {{{+no_gnome}}} or {{{+no_x11}}} variants, so you should remove them from your local variants.conf file. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 21:13:01 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 21:13:01 -0000 Subject: [MacPorts] #53022: opencv @3.1.0_6+python34: Portfile broken for variant +python34 In-Reply-To: <044.4cfc0421df7d7ecacd2795ceaf0f1af4@macports.org> References: <044.4cfc0421df7d7ecacd2795ceaf0f1af4@macports.org> Message-ID: <059.f3d3caa937f78386b9ffddeae9327af2@macports.org> #53022: opencv @3.1.0_6+python34: Portfile broken for variant +python34 ----------------------+---------------------- Reporter: detlevd | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: opencv | ----------------------+---------------------- Comment (by detlevd): René - thanks for the patch! I applied it to the opencv Portfile and performed an upgrade --force on opencv. Everything works as expected now. No more dependecies on python35 in variant +python34. Scripts using 'import cv2' now work as before. I did not check it for +python35 though. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 21:26:55 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 21:26:55 -0000 Subject: [MacPorts] #53018: mercurial @4.0.1: error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but "10.11" during configure In-Reply-To: <042.20cc68d2a5b85e3ef4bb92ae1dd59d73@macports.org> References: <042.20cc68d2a5b85e3ef4bb92ae1dd59d73@macports.org> Message-ID: <057.ec720ad78dea5bdcce81d84ae7d4247a@macports.org> #53018: mercurial @4.0.1: error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but "10.11" during configure ------------------------+------------------------ Reporter: yabba | Owner: seanfarley Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: invalid | Keywords: Port: mercurial | ------------------------+------------------------ Changes (by seanfarley): * status: assigned => closed * resolution: => invalid -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 22:04:18 2016 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2016 22:04:18 -0000 Subject: [MacPorts] #53029: Upgrade libetpan to 1.7.2 Message-ID: <045.7a8696baef87017cc5cae91e4519b0eb@macports.org> #53029: Upgrade libetpan to 1.7.2 ----------------------+---------------------- Reporter: pmetzger | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: libetpan ----------------------+---------------------- libetpan on github is at 1.7.2 -- it should probably be updated as Macports is at 1.6 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 00:19:36 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 00:19:36 -0000 Subject: [MacPorts] #53029: libetpan: Upgrade to 1.7.2 (was: Upgrade libetpan to 1.7.2) In-Reply-To: <045.7a8696baef87017cc5cae91e4519b0eb@macports.org> References: <045.7a8696baef87017cc5cae91e4519b0eb@macports.org> Message-ID: <060.7fa270ccf2d2296f6d7ad8930f57d97b@macports.org> #53029: libetpan: Upgrade to 1.7.2 -----------------------+---------------------- Reporter: pmetzger | Owner: mww@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libetpan | -----------------------+---------------------- Changes (by ryandesign): * status: new => assigned * owner: => mww@… * type: defect => update -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 02:38:52 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 02:38:52 -0000 Subject: [MacPorts] #53016: octave @4.2.0_1 build failure with libgcc-devel (was: octave @4.2.0_1 build failure) In-Reply-To: <047.6f5926dce6c29e418e3b19edf4dea9f0@macports.org> References: <047.6f5926dce6c29e418e3b19edf4dea9f0@macports.org> Message-ID: <062.0db33eec6ca84f56bdca01e59a22c543@macports.org> #53016: octave @4.2.0_1 build failure with libgcc-devel -------------------------+--------------------------------- Reporter: ryandesign | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.99 Resolution: | Keywords: Port: octave | -------------------------+--------------------------------- Comment (by ryandesign): Building octave with libgcc @6.2.0 instead of libgcc-devel @7-20161204 does work. After discussing with Jeremy Sequoia, I think this is rather a bug in the gcc ports that will need to be solved there. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 05:40:39 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 05:40:39 -0000 Subject: [MacPorts] #52999: php-uuid: add php71-uuid subport In-Reply-To: <047.1baaedcebc20348ef1eda3ffb1c02491@macports.org> References: <047.1baaedcebc20348ef1eda3ffb1c02491@macports.org> Message-ID: <062.33703cd8fa4368383c721b5e16e46637@macports.org> #52999: php-uuid: add php71-uuid subport --------------------------+---------------------- Reporter: ryandesign | Owner: pixilla Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: haspatch Port: php-uuid | --------------------------+---------------------- Changes (by ryandesign): * status: new => closed * resolution: => fixed Comment: In [changeset:"55abe2a74a9cc30d1eb7d297d29505a9ca647c5a/macports-ports" 55abe2a7/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="55abe2a74a9cc30d1eb7d297d29505a9ca647c5a" php-uuid: Add php71-uuid subport Closes: https://trac.macports.org/ticket/52999 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 06:36:48 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 06:36:48 -0000 Subject: [MacPorts] #52936: rust 1.11.0_0 darwin_16 build hang In-Reply-To: <045.fb36edf770f1439f197ad217207f881c@macports.org> References: <045.fb36edf770f1439f197ad217207f881c@macports.org> Message-ID: <060.5f55b7cb32e9493d1e36a391e33420a2@macports.org> #52936: rust 1.11.0_0 darwin_16 build hang ------------------------+-------------------- Reporter: datajerk | Owner: g5pw Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: duplicate | Keywords: Port: rust | ------------------------+-------------------- Changes (by jmroot): * status: assigned => closed * resolution: => duplicate Comment: #52247 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 06:41:34 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 06:41:34 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.66ea9100b9a0cf2f3e747aacb3e530b8@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"82608d82dbbc7a45e67eb5eaa0bb981c9350a438/macports-ports" 82608d82/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="82608d82dbbc7a45e67eb5eaa0bb981c9350a438" binutils: update to 2.27 See: https://trac.macports.org/ticket/51935 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 06:44:00 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 06:44:00 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.aea8f54ecac9441f89bcea89f5fe534e@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Description changed by mojca: Old description: > It would be nice to upgrade the binutils ports. > > ||= name =||= old version =||= maint. > =||= commit =|| > || arm-aout-binutils || 2.22 || > || r || > || arm-elf-binutils || 2.25 || > stuartwesterman-gm || r || > || arm-none-eabi-binutils || 2.23.1 || > stuartwesterman-gm || r || > || arm-none-linux-gnueabi-binutils || 2005q3-2 || > stuartwesterman-gm || r || > || arm-rtems-binutils || 2.18 || > || r || > || ~~avr-binutils~~ || ~~2.25~~ || > ~~g5pw~~ || r151540 || > || binutils || 2.26.1 || > || r150799 || > || i386-elf-binutils || 2.23.1 || jinksys-gm > || r || > || i386-mingw32-binutils || 2.21-3 || > || r || > || i386-mingw32-binutils || 2.21-3 || > || r || > || i386-rtems-binutils || 2.18 || > || r || > || i960-rtems-binutils || 2.16.1 || > || r || > || lm32-rtems-binutils || 2.21.1 || yann > .sionneau-gm || r || > || m68k-elf-binutils || 2.17 || > || r || > || m68k-rtems-binutils || 2.18 || > || r || > || mips-elf-binutils || 2.17 || > || r || > || mips-rtems-binutils || 2.18 || > || r || > || mipsel-linux-binutils || 2.16.1 || > || r || > || msp430-binutils || 2.21.1a-20120406 || g5pw > || r || > || msp430-binutils-devel || 2.22-20120911 || g5pw > || r || > || powerpc-rtems-binutils || 2.18 || > || r || > || ppc-linux-binutils || 2.25 || > || r || > || sh-rtems-binutils || 2.18 || > || r || > || sparc-rtems-binutils || 2.18 || > || r || > || spu-binutils || 2.20.51.0.5 || > || r || > || x86_64-elf-binutils || 2.23.1 || > || r || New description: It would be nice to upgrade the binutils ports. ||= name =||= old version =||= maint. =||= commit =|| || arm-aout-binutils || 2.22 || || r || || arm-elf-binutils || 2.25 || stuartwesterman-gm || r || || arm-none-eabi-binutils || 2.23.1 || stuartwesterman-gm || r || || arm-none-linux-gnueabi-binutils || 2005q3-2 || stuartwesterman-gm || r || || arm-rtems-binutils || 2.18 || || r || || ~~avr-binutils~~ || ~~2.25~~ || ~~g5pw~~ || r151540 || || ~~binutils~~ || ~~2.26.1~~ || || r150799, [changeset:"82608d82dbbc7a45e67eb5eaa0bb981c9350a438/macports- ports" 82608d82] || || i386-elf-binutils || 2.23.1 || jinksys-gm || r || || i386-mingw32-binutils || 2.21-3 || || r || || i386-mingw32-binutils || 2.21-3 || || r || || i386-rtems-binutils || 2.18 || || r || || i960-rtems-binutils || 2.16.1 || || r || || lm32-rtems-binutils || 2.21.1 || yann.sionneau- gm || r || || m68k-elf-binutils || 2.17 || || r || || m68k-rtems-binutils || 2.18 || || r || || mips-elf-binutils || 2.17 || || r || || mips-rtems-binutils || 2.18 || || r || || mipsel-linux-binutils || 2.16.1 || || r || || msp430-binutils || 2.21.1a-20120406 || g5pw || r || || msp430-binutils-devel || 2.22-20120911 || g5pw || r || || powerpc-rtems-binutils || 2.18 || || r || || ppc-linux-binutils || 2.25 || || r || || sh-rtems-binutils || 2.18 || || r || || sparc-rtems-binutils || 2.18 || || r || || spu-binutils || 2.20.51.0.5 || || r || || x86_64-elf-binutils || 2.23.1 || || r || -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 11:15:58 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 11:15:58 -0000 Subject: [MacPorts] #53015: octave-octclip, octave-octproj: missing patch file In-Reply-To: <048.be8fb1f67e3eed30df7100ac0090b392@macports.org> References: <048.be8fb1f67e3eed30df7100ac0090b392@macports.org> Message-ID: <063.2d9e3632776b8a2237e6351904c1fa4f@macports.org> #53015: octave-octclip, octave-octproj: missing patch file --------------------------------------------+------------------------------ Reporter: Schamschula | Owner: MarcusCalhoun- | Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: octave-octclip octave-octproj | --------------------------------------------+------------------------------ Comment (by MarcusCalhoun-Lopez): Based on the output, I believe you may be using an older version of octave.tcl[[BR]] (perhaps in /Users/marius/Development/MacPorts/ports/_resources/port1.0/group/octave-1.0.tcl). In your log files, {{{LC_CTYPE='C'}}}, but this was removed in [changeset:"9ea1455793a659449403aaa5f1d4f987c1d930f7/macports-ports" 9ea1455/macports-ports].[[BR]] Similarly, {{{LAPACK_LIBS}}} is no longer set explicitly. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 12:08:52 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 12:08:52 -0000 Subject: [MacPorts] #53015: octave-octclip, octave-octproj: missing patch file In-Reply-To: <048.be8fb1f67e3eed30df7100ac0090b392@macports.org> References: <048.be8fb1f67e3eed30df7100ac0090b392@macports.org> Message-ID: <063.2e581be29d249f35f3fb14bf72fffec5@macports.org> #53015: octave-octclip, octave-octproj: missing patch file --------------------------------------------+------------------------------ Reporter: Schamschula | Owner: MarcusCalhoun- | Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: octave-octclip octave-octproj | --------------------------------------------+------------------------------ Comment (by Schamschula): Good catch! I had this in my local tree on one machine (unfortunately the one I use to do most test builds). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 15:31:54 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 15:31:54 -0000 Subject: [MacPorts] #53021: octave @4.2.0_1: Another build failure In-Reply-To: <041.a9100f410b771f7245060d742521900f@macports.org> References: <041.a9100f410b771f7245060d742521900f@macports.org> Message-ID: <056.866cf54bc8c73531c33a4293b51c1e4d@macports.org> #53021: octave @4.2.0_1: Another build failure ---------------------+--------------------------------- Reporter: mf2k | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: octave | ---------------------+--------------------------------- Comment (by mf2k): {{{ $ xcode-select --install xcode-select: error: command line tools are already installed, use "Software Update" to install updates $ softwareupdate -l Software Update Tool Copyright 2002-2015 Apple Inc. Finding available software No new software available. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 18:32:55 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 18:32:55 -0000 Subject: [MacPorts] #53030: ncftp @3.2.6 Checksum mismatch Message-ID: <046.b696169b01e43efd21e5d8e71dae82ee@macports.org> #53030: ncftp @3.2.6 Checksum mismatch -----------------------+------------------- Reporter: crapshoot | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: ncftp -----------------------+------------------- The rmd160 and sha256 checksums for ncftp-3.2.6-src.tar.xz listed in the Portfile do not match those of the downloaded file. I downloaded from two sites just to confirm. The CHANGELOG.txt in the ncftp sources says 3.2.6 was released on 2016-12-04. It looks like there was a "stealth update" after the initial release on 2016-11-27. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 18:33:34 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 18:33:34 -0000 Subject: [MacPorts] #53030: ncftp @3.2.6 Checksum mismatch In-Reply-To: <046.b696169b01e43efd21e5d8e71dae82ee@macports.org> References: <046.b696169b01e43efd21e5d8e71dae82ee@macports.org> Message-ID: <061.b2af69f12a65e2a272751c907e58b60c@macports.org> #53030: ncftp @3.2.6 Checksum mismatch ------------------------+---------------------- Reporter: crapshoot | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: ncftp | ------------------------+---------------------- Changes (by crapshoot): * Attachment "main.log" added. Log file of checksum failure -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 18:34:17 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 18:34:17 -0000 Subject: [MacPorts] #53030: ncftp @3.2.6 Checksum mismatch In-Reply-To: <046.b696169b01e43efd21e5d8e71dae82ee@macports.org> References: <046.b696169b01e43efd21e5d8e71dae82ee@macports.org> Message-ID: <061.8c49f6d8c99b286f98d3fc72071aed0d@macports.org> #53030: ncftp @3.2.6 Checksum mismatch ------------------------+---------------------- Reporter: crapshoot | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: ncftp | ------------------------+---------------------- Changes (by crapshoot): * Attachment "Portfile.patch" added. Portfile patch for new checksums -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 19:34:25 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 19:34:25 -0000 Subject: [MacPorts] #53031: macports ncl fails, mac install of ncarg works Message-ID: <043.2f66a17331fd430dc6114c13ca7272cd@macports.org> #53031: macports ncl fails, mac install of ncarg works --------------------+------------------- Reporter: basmac | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: ncl | Port: ncarg --------------------+------------------- Running the same script the macports /opt/local crashes with an error, whereas a separate default install of ncarg/ncl works from /usr/local. Attached is the log, running /opt/local ncl first then /usr/local ncl second using ( ncarg @6.3.0_8+gcc6 (active)) macports fails on ElCap or new install on Sierra. The attached log is Sierra, but has the same error, on ElCap (ncarg @6.3.0_9+gcc5 (active)) The library script ESMF_regridding.ncl are the same size in /usr/local/ncl/ as under /opt/local. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 19:35:53 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 19:35:53 -0000 Subject: [MacPorts] #53031: macports ncl fails, mac install of ncarg works In-Reply-To: <043.2f66a17331fd430dc6114c13ca7272cd@macports.org> References: <043.2f66a17331fd430dc6114c13ca7272cd@macports.org> Message-ID: <058.3c4dac5fe1093eb3ad88f03435a5e044@macports.org> #53031: macports ncl fails, mac install of ncarg works ---------------------+------------------- Reporter: basmac | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: ncl Port: ncarg | ---------------------+------------------- Changes (by basmac): * Attachment "ncl.mac27.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 19:43:04 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 19:43:04 -0000 Subject: [MacPorts] #53032: dumpasn1 port broken - sources cannot be found Message-ID: <050.0ccd2d20c3fbe8910c09cef6b72869b3@macports.org> #53032: dumpasn1 port broken - sources cannot be found ---------------------------+------------------- Reporter: snappy-pickle | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: ---------------------------+------------------- Running on macOS 10.12.1, trying to install dumpasn1, the source files could not be found: {{{ neuromancer: bootstrapping-encoding-experiments [643]$ sw_vers ProductName: Mac OS X ProductVersion: 10.12.1 BuildVersion: 16B2555 neuromancer: bootstrapping-encoding-experiments [644]$ uname -a Darwin Neuromancer.local 16.1.0 Darwin Kernel Version 16.1.0: Thu Oct 13 21:26:57 PDT 2016; root:xnu-3789.21.3~60/RELEASE_X86_64 x86_64 neuromancer: bootstrapping-encoding-experiments [645]$ sudo port -v install dumpasn1 ---> Fetching distfiles for dumpasn1 ---> dumpasn1.cfg does not exist in /opt/local/var/macports/distfiles/dumpasn1/20110202 ---> Attempting to fetch dumpasn1.cfg from http://www.cs.auckland.ac.nz/~pgut001/ % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 215k 0 215k 0 0 60742 0 --:--:-- 0:00:03 --:--:-- 73280 ---> Attempting to fetch dumpasn1.cfg from https://distfiles.macports.org/dumpasn1/20110202 % 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 dumpasn1.cfg from http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/dumpasn1/20110202 % 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 dumpasn1.cfg from http://cjj.kr.distfiles.macports.org/dumpasn1/20110202 % 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 dumpasn1.cfg from http://fco.it.distfiles.macports.org/mirrors/macports- distfiles/dumpasn1/20110202 % 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 dumpasn1.cfg from http://her.gr.distfiles.macports.org/dumpasn1/20110202 % 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 dumpasn1.cfg from http://jnb.za.distfiles.macports.org/distfiles/dumpasn1/20110202 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0 ---> Attempting to fetch dumpasn1.cfg from http://jog.id.distfiles.macports.org/macports/distfiles/dumpasn1/20110202 % 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 dumpasn1.cfg from http://lil.fr.distfiles.macports.org/dumpasn1/20110202 % 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 dumpasn1.cfg from http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/dumpasn1/20110202 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 272 100 272 0 0 447 0 --:--:-- --:--:-- --:--:-- 448 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 ---> Attempting to fetch dumpasn1.cfg from http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/dumpasn1/20110202 % 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 dumpasn1.cfg from http://nue.de.distfiles.macports.org/dumpasn1/20110202 % 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 dumpasn1.cfg from http://osl.no.distfiles.macports.org/dumpasn1/20110202 % 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 dumpasn1.cfg from https://pek.cn.distfiles.macports.org/macports/distfiles/dumpasn1/20110202 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- 0:00:02 --:--:-- 0 ---> Attempting to fetch dumpasn1.cfg from http://sea.us.distfiles.macports.org/macports/distfiles/dumpasn1/20110202 % 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 dumpasn1.cfg from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/dumpasn1/20110202 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 Error: org.macports.fetch for port dumpasn1 returned: fetch failed Warning: targets not executed for dumpasn1: org.macports.activate org.macports.fetch org.macports.checksum org.macports.extract org.macports.patch org.macports.configure org.macports.build org.macports.destroot org.macports.install Please see the log file for port dumpasn1 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_dumpasn1/dumpasn1/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port dumpasn1 failed neuromancer: bootstrapping-encoding-experiments [646]$ }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 20:06:36 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 20:06:36 -0000 Subject: [MacPorts] #53033: saga doesn't open LAS files Message-ID: <044.0b3d9a9da39d2653ab487fab175435ea@macports.org> #53033: saga doesn't open LAS files -------------------------+------------------ Reporter: dershow | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: saga -------------------------+------------------ The main reason that I wanted to install saga was to open and work with las LiDAR files. But, for some reason there is no I/O tool in the MacPorts version of saga that imports LAS. This tool is present on the Windows version, and it would be great if it becomes available on the macports version as well. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 20:48:31 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 20:48:31 -0000 Subject: [MacPorts] #53028: py-pyqt5 variant typos In-Reply-To: <046.502886aeb4b0452ffeaf206e61da1045@macports.org> References: <046.502886aeb4b0452ffeaf206e61da1045@macports.org> Message-ID: <061.104c8969c40de7be9cc36652b2ffd867@macports.org> #53028: py-pyqt5 variant typos ------------------------+---------------------- Reporter: jjstickel | Owner: mamoll Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: py-pyqt5 | ------------------------+---------------------- Changes (by Eric A. Borisch ): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"7b13b914049db082b5ebb462435b0681e155c8f7/macports-ports" 7b13b914/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="7b13b914049db082b5ebb462435b0681e155c8f7" py-pyqt5: Fix typos in webengine variant. Closes: https://trac.macports.org/ticket/53028 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 21:06:34 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 21:06:34 -0000 Subject: [MacPorts] #53030: ncftp @3.2.6 Checksum mismatch In-Reply-To: <046.b696169b01e43efd21e5d8e71dae82ee@macports.org> References: <046.b696169b01e43efd21e5d8e71dae82ee@macports.org> Message-ID: <061.a728321af91e984fafeba28498f8088c@macports.org> #53030: ncftp @3.2.6 Checksum mismatch ------------------------+---------------------- Reporter: crapshoot | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: ncftp | ------------------------+---------------------- Comment (by tobypeterson): WTF -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 21:18:44 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 21:18:44 -0000 Subject: [MacPorts] #53021: octave @4.2.0_1: Another build failure In-Reply-To: <041.a9100f410b771f7245060d742521900f@macports.org> References: <041.a9100f410b771f7245060d742521900f@macports.org> Message-ID: <056.4642c4397fad3288eed5fe79b0436c4a@macports.org> #53021: octave @4.2.0_1: Another build failure ---------------------+--------------------------------- Reporter: mf2k | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: octave | ---------------------+--------------------------------- Comment (by tehcog): I have the same problem. {{{ Software OS X 10.9.5 (13F1911) ---- NerdCenter { ~ }-> port version Version: 2.3.5 NerdCenter { ~ }-> xcodebuild -version Xcode 6.2 Build version 6C131e }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 21:22:46 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 21:22:46 -0000 Subject: [MacPorts] #53031: macports ncl fails, mac install of ncarg works In-Reply-To: <043.2f66a17331fd430dc6114c13ca7272cd@macports.org> References: <043.2f66a17331fd430dc6114c13ca7272cd@macports.org> Message-ID: <058.951707e224baf5f21a585e58d8d592e5@macports.org> #53031: macports ncl fails, mac install of ncarg works ---------------------+---------------------- Reporter: basmac | Owner: tenomoto Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: ncarg | ---------------------+---------------------- Changes (by mf2k): * cc: takeshi@… (removed) * status: new => assigned * owner: => tenomoto * keywords: ncl => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 21:24:14 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 21:24:14 -0000 Subject: [MacPorts] #53030: ncftp @3.2.6 Checksum mismatch In-Reply-To: <046.b696169b01e43efd21e5d8e71dae82ee@macports.org> References: <046.b696169b01e43efd21e5d8e71dae82ee@macports.org> Message-ID: <061.a145600496d320c13fe3ea5aec595a9d@macports.org> #53030: ncftp @3.2.6 Checksum mismatch ------------------------+---------------------- Reporter: crapshoot | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: ncftp | ------------------------+---------------------- Comment (by tobypeterson): Not the first time. See commit 89fba1b1628ad3e98532879fac9497b78ce5ceb0 for example. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 21:26:37 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 21:26:37 -0000 Subject: [MacPorts] #53030: ncftp @3.2.6 Checksum mismatch In-Reply-To: <046.b696169b01e43efd21e5d8e71dae82ee@macports.org> References: <046.b696169b01e43efd21e5d8e71dae82ee@macports.org> Message-ID: <061.61f82f9a4377e3a39bf77484db2763eb@macports.org> #53030: ncftp @3.2.6 Checksum mismatch ------------------------+---------------------- Reporter: crapshoot | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: ncftp | ------------------------+---------------------- Changes (by tobypeterson): * status: new => closed * resolution: => fixed Comment: Applied patch with a dist_subdir to prevent failures for people who've already fetched the old tarball. Pushed 2196fe1c8f545af48f16838a3f9d07aba18b3d51 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 21:37:13 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 21:37:13 -0000 Subject: [MacPorts] #53032: dumpasn1 port broken - sources cannot be found In-Reply-To: <050.0ccd2d20c3fbe8910c09cef6b72869b3@macports.org> References: <050.0ccd2d20c3fbe8910c09cef6b72869b3@macports.org> Message-ID: <065.f002438ea0aa5585d1a8769203b6fd3f@macports.org> #53032: dumpasn1 port broken - sources cannot be found ----------------------------+---------------------- Reporter: snappy-pickle | Owner: cjr@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: dumpasn1 | ----------------------------+---------------------- Changes (by mf2k): * owner: => cjr@… * status: new => assigned * port: => dumpasn1 Comment: In the future, please fill in the Port field and Cc the port maintainers ({{{port info --maintainers dumpasn1}}}), if any. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 21:41:14 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 21:41:14 -0000 Subject: [MacPorts] #53034: libuv issue in upgrade outdated Message-ID: <044.ed968e16ccb34a9aa629648c8b54070d@macports.org> #53034: libuv issue in upgrade outdated ---------------------+----------------- Reporter: ajpowel | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: ---------------------+----------------- Hello -- When I do, "sudo -E port upgrade outdated" I get the error below. What should one do to deal w/ the issue? ---> Attempting to fetch libuv-1.10.1.tar.gz from https://distfiles.macports.org/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://cjj.kr.distfiles.macports.org/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://her.gr.distfiles.macports.org/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://jnb.za.distfiles.macports.org/distfiles/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://jog.id.distfiles.macports.org/macports/distfiles/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://lil.fr.distfiles.macports.org/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://nue.de.distfiles.macports.org/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://osl.no.distfiles.macports.org/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from https://pek.cn.distfiles.macports.org/macports/distfiles/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://sea.us.distfiles.macports.org/macports/distfiles/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/libuv Error: org.macports.fetch for port libuv returned: fetch failed Please see the log file for port libuv for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libuv/libuv/main.log Error: Problem while installing libuv To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 21:41:25 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 21:41:25 -0000 Subject: [MacPorts] #53035: [Port Abandoned] dumpasn1 Message-ID: <041.3890334eaaece8314f08b12b6580c830@macports.org> #53035: [Port Abandoned] dumpasn1 --------------------+---------------------- Reporter: mf2k | Owner: cjr@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: dumpasn1 --------------------+---------------------- The [wiki:MacPortsDevelopers Macports developer] cjr has not been seen in [search:cjr at macports.org 10 years] and has a few [query:status=!closed&owner=cjr at macports.org open tickets]. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 21:43:46 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 21:43:46 -0000 Subject: [MacPorts] #53034: libuv issue in upgrade outdated In-Reply-To: <044.ed968e16ccb34a9aa629648c8b54070d@macports.org> References: <044.ed968e16ccb34a9aa629648c8b54070d@macports.org> Message-ID: <059.cc4c4a765dadbff306b13d4167148b7d@macports.org> #53034: libuv issue in upgrade outdated ----------------------+---------------------- Reporter: ajpowel | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libuv | ----------------------+---------------------- Changes (by mf2k): * owner: => raimue * cc: michaelld (added) * status: new => assigned * port: => libuv Comment: In the future, please use WikiFormatting, fill in the Port field and Cc the port maintainers ({{{port info --maintainers libuv}}}), if any. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 21:44:06 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 21:44:06 -0000 Subject: [MacPorts] #53034: libuv issue in upgrade outdated In-Reply-To: <044.ed968e16ccb34a9aa629648c8b54070d@macports.org> References: <044.ed968e16ccb34a9aa629648c8b54070d@macports.org> Message-ID: <059.dfce4b9c0008ba498215b8a239c4f641@macports.org> #53034: libuv issue in upgrade outdated ----------------------+---------------------- Reporter: ajpowel | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libuv | ----------------------+---------------------- Description changed by mf2k: Old description: > Hello -- > > When I do, "sudo -E port upgrade outdated" I get the error below. > > What should one do to deal w/ the issue? > > > ---> Attempting to fetch libuv-1.10.1.tar.gz from > https://distfiles.macports.org/libuv > ---> Attempting to fetch libuv-1.10.1.tar.gz from > http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/libuv > ---> Attempting to fetch libuv-1.10.1.tar.gz from > http://cjj.kr.distfiles.macports.org/libuv > ---> Attempting to fetch libuv-1.10.1.tar.gz from > http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/libuv > ---> Attempting to fetch libuv-1.10.1.tar.gz from > http://her.gr.distfiles.macports.org/libuv > ---> Attempting to fetch libuv-1.10.1.tar.gz from > http://jnb.za.distfiles.macports.org/distfiles/libuv > ---> Attempting to fetch libuv-1.10.1.tar.gz from > http://jog.id.distfiles.macports.org/macports/distfiles/libuv > ---> Attempting to fetch libuv-1.10.1.tar.gz from > http://lil.fr.distfiles.macports.org/libuv > ---> Attempting to fetch libuv-1.10.1.tar.gz from > http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/libuv > ---> Attempting to fetch libuv-1.10.1.tar.gz from > http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/libuv > ---> Attempting to fetch libuv-1.10.1.tar.gz from > http://nue.de.distfiles.macports.org/libuv > ---> Attempting to fetch libuv-1.10.1.tar.gz from > http://osl.no.distfiles.macports.org/libuv > ---> Attempting to fetch libuv-1.10.1.tar.gz from > https://pek.cn.distfiles.macports.org/macports/distfiles/libuv > ---> Attempting to fetch libuv-1.10.1.tar.gz from > http://sea.us.distfiles.macports.org/macports/distfiles/libuv > ---> Attempting to fetch libuv-1.10.1.tar.gz from > http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/libuv > Error: org.macports.fetch for port libuv returned: fetch failed > Please see the log file for port libuv for details: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libuv/libuv/main.log > Error: Problem while installing libuv > To report a bug, follow the instructions in the guide: > http://guide.macports.org/#project.tickets New description: Hello -- When I do, "sudo -E port upgrade outdated" I get the error below. What should one do to deal w/ the issue? {{{ ---> Attempting to fetch libuv-1.10.1.tar.gz from https://distfiles.macports.org/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://cjj.kr.distfiles.macports.org/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://her.gr.distfiles.macports.org/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://jnb.za.distfiles.macports.org/distfiles/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://jog.id.distfiles.macports.org/macports/distfiles/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://lil.fr.distfiles.macports.org/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://nue.de.distfiles.macports.org/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://osl.no.distfiles.macports.org/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from https://pek.cn.distfiles.macports.org/macports/distfiles/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://sea.us.distfiles.macports.org/macports/distfiles/libuv ---> Attempting to fetch libuv-1.10.1.tar.gz from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/libuv Error: org.macports.fetch for port libuv returned: fetch failed Please see the log file for port libuv for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libuv/libuv/main.log Error: Problem while installing libuv To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 21:48:37 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 21:48:37 -0000 Subject: [MacPorts] #53033: saga doesn't open LAS files In-Reply-To: <044.0b3d9a9da39d2653ab487fab175435ea@macports.org> References: <044.0b3d9a9da39d2653ab487fab175435ea@macports.org> Message-ID: <059.c5c44b0ff8a5a1f4dab98e62f3760cb8@macports.org> #53033: saga doesn't open LAS files --------------------------+---------------------- Reporter: dershow | Owner: Veence Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: saga | --------------------------+---------------------- Changes (by mf2k): * status: new => assigned * cc: vince@… (removed) * owner: => Veence -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 22:05:25 2016 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2016 22:05:25 -0000 Subject: [MacPorts] #53030: ncftp @3.2.6 Checksum mismatch In-Reply-To: <046.b696169b01e43efd21e5d8e71dae82ee@macports.org> References: <046.b696169b01e43efd21e5d8e71dae82ee@macports.org> Message-ID: <061.efeaa11f9148ebe1d8c37660bc3141da@macports.org> #53030: ncftp @3.2.6 Checksum mismatch ------------------------+---------------------- Reporter: crapshoot | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: ncftp | ------------------------+---------------------- Comment (by crapshoot): Thanks for the quick fix! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 02:29:19 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 02:29:19 -0000 Subject: [MacPorts] #52516: sundials @2.6.2_1: update to 2.7.0, add +fcmix In-Reply-To: <046.5029d3318db8e0e993f5d643efb20855@macports.org> References: <046.5029d3318db8e0e993f5d643efb20855@macports.org> Message-ID: <061.040a2fb1146b9a3f08d69cb1b1b6632b@macports.org> #52516: sundials @2.6.2_1: update to 2.7.0, add +fcmix ------------------------+------------------------ Reporter: jjstickel | Owner: seanfarley Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: sundials | ------------------------+------------------------ Changes (by kurthindenburg): * cc: kurthindenburg (added) Comment: As far as I can tell, this update works fine - let me know if you want me to commit it. If you commit, might as well fix the eval issue displayed in port lint --nitpick -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 02:35:39 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 02:35:39 -0000 Subject: [MacPorts] #53036: [Port New] libchewing Message-ID: <042.8b452ee8a9de3a161a300385f4be9866@macports.org> #53036: [Port New] libchewing ------------------------+------------------------ Reporter: cwlin | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: libchewing ------------------------+------------------------ Hi MacPorts, I've created a new port for libchewing. libchewing is a library which is used for developing chinese input method on various platforms. Please kindly help to review and add it if possible. Thanks! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 03:07:19 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 03:07:19 -0000 Subject: [MacPorts] #53036: [Port New] libchewing In-Reply-To: <042.8b452ee8a9de3a161a300385f4be9866@macports.org> References: <042.8b452ee8a9de3a161a300385f4be9866@macports.org> Message-ID: <057.71c2684227880d33bd1c08a3231d304f@macports.org> #53036: [Port New] libchewing -------------------------+----------------- Reporter: cwlin | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libchewing | -------------------------+----------------- Changes (by cwlin): * Attachment "Portfile" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 04:36:10 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 04:36:10 -0000 Subject: [MacPorts] #53036: [Port New] libchewing In-Reply-To: <042.8b452ee8a9de3a161a300385f4be9866@macports.org> References: <042.8b452ee8a9de3a161a300385f4be9866@macports.org> Message-ID: <057.616b8d2bf8aa11cf6238cf8fe6f2a1fc@macports.org> #53036: [Port New] libchewing -------------------------+----------------- Reporter: cwlin | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libchewing | -------------------------+----------------- Comment (by ryandesign): Thanks. For software hosted on github, you should make use of the github 1.0 portgroup. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 10:12:45 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 10:12:45 -0000 Subject: [MacPorts] #53034: libuv issue in upgrade outdated In-Reply-To: <044.ed968e16ccb34a9aa629648c8b54070d@macports.org> References: <044.ed968e16ccb34a9aa629648c8b54070d@macports.org> Message-ID: <059.d10cc5931608531ce4fa2c8ce142b092@macports.org> #53034: libuv issue in upgrade outdated ----------------------+---------------------- Reporter: ajpowel | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libuv | ----------------------+---------------------- Comment (by raimue): I cannot reproduce the problem. Please provide the full main.log. On which version of macOS are you? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 10:15:13 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 10:15:13 -0000 Subject: [MacPorts] #53034: libuv @1.10.1: fetch failure (was: libuv issue in upgrade outdated) In-Reply-To: <044.ed968e16ccb34a9aa629648c8b54070d@macports.org> References: <044.ed968e16ccb34a9aa629648c8b54070d@macports.org> Message-ID: <059.17cd3edb22643c0beef635b04cba1659@macports.org> #53034: libuv @1.10.1: fetch failure ----------------------+---------------------- Reporter: ajpowel | Owner: raimue Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libuv | ----------------------+---------------------- Changes (by raimue): * status: assigned => accepted -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 11:02:42 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 11:02:42 -0000 Subject: [MacPorts] #51344: seqan @2.1.1_0 Fixes installation of missing files In-Reply-To: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> References: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> Message-ID: <057.65d8e2e5e4fa382f62a24091062bd05e@macports.org> #51344: seqan @2.1.1_0 Fixes installation of missing files ---------------------+--------------------------------- Reporter: rrahn | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch maintainer Port: seqan | ---------------------+--------------------------------- Changes (by rrahn): * Attachment "Portfile-seqan.diff" removed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 11:02:42 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 11:02:42 -0000 Subject: [MacPorts] #51344: seqan @2.1.1_0 Fixes installation of missing files In-Reply-To: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> References: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> Message-ID: <057.398cfc66f7bb9b17982c7942c4c3f922@macports.org> #51344: seqan @2.1.1_0 Fixes installation of missing files ---------------------+--------------------------------- Reporter: rrahn | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch maintainer Port: seqan | ---------------------+--------------------------------- Changes (by rrahn): * Attachment "Portfile-seqan.diff" added. Updated patch file for seqan portfile -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 11:05:01 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 11:05:01 -0000 Subject: [MacPorts] #51344: seqan @2.1.1_0 Fixes installation of missing files In-Reply-To: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> References: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> Message-ID: <057.f24a6c4beca27d4e5d41fa5093783a58@macports.org> #51344: seqan @2.1.1_0 Fixes installation of missing files ---------------------+--------------------------------- Reporter: rrahn | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch maintainer Port: seqan | ---------------------+--------------------------------- Comment (by rrahn): Hey, I updated the portfile. The patch will now install all files to a fixed location. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 11:36:17 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 11:36:17 -0000 Subject: [MacPorts] #51344: seqan @2.1.1_0 Fixes installation of missing files In-Reply-To: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> References: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> Message-ID: <057.961e306ed18c5169e390c313754e41b5@macports.org> #51344: seqan @2.1.1_0 Fixes installation of missing files ---------------------+--------------------------------- Reporter: rrahn | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch maintainer Port: seqan | ---------------------+--------------------------------- Comment (by raimue): The patch file is somewhat garbled, as it contains a unified diff followed by two diffs in normal format. These diffs apply different changes and I cannot deduce what your intention was. When changing files that will be installed, you will also need to increase the `revision`: {{{ #!diff --- a/science/seqan/Portfile +++ b/science/seqan/Portfile @@ -5,6 +5,7 @@ PortSystem 1.0 name seqan version 2.1.1 +revision 1 categories science platforms darwin supported_archs noarch }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 12:08:12 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 12:08:12 -0000 Subject: [MacPorts] #51344: seqan @2.1.1_0 Fixes installation of missing files In-Reply-To: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> References: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> Message-ID: <057.9ba439a22dd60978c57040330796f804@macports.org> #51344: seqan @2.1.1_0 Fixes installation of missing files ---------------------+--------------------------------- Reporter: rrahn | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch maintainer Port: seqan | ---------------------+--------------------------------- Comment (by rrahn): Oh, sorry. I'll fix that and also increase the revision number. Thx for pointing this out. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 12:13:27 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 12:13:27 -0000 Subject: [MacPorts] #51344: seqan @2.1.1_0 Fixes installation of missing files In-Reply-To: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> References: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> Message-ID: <057.398cfc66f7bb9b17982c7942c4c3f922@macports.org> #51344: seqan @2.1.1_0 Fixes installation of missing files ---------------------+--------------------------------- Reporter: rrahn | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch maintainer Port: seqan | ---------------------+--------------------------------- Changes (by rrahn): * Attachment "Portfile-seqan.diff" removed. Updated patch file for seqan portfile -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 12:13:27 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 12:13:27 -0000 Subject: [MacPorts] #51344: seqan @2.1.1_0 Fixes installation of missing files In-Reply-To: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> References: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> Message-ID: <057.51bc1a9714716a68b54f76606503a19f@macports.org> #51344: seqan @2.1.1_0 Fixes installation of missing files ---------------------+--------------------------------- Reporter: rrahn | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch maintainer Port: seqan | ---------------------+--------------------------------- Changes (by rrahn): * Attachment "Portfile-seqan.diff" added. Cleaned up patch file -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 12:14:09 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 12:14:09 -0000 Subject: [MacPorts] #51344: seqan @2.1.1_0 Fixes installation of missing files In-Reply-To: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> References: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> Message-ID: <057.42ffd4af45316579984ab090fe21c9a1@macports.org> #51344: seqan @2.1.1_0 Fixes installation of missing files ---------------------+--------------------------------- Reporter: rrahn | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch maintainer Port: seqan | ---------------------+--------------------------------- Comment (by rrahn): Ok, I hope the file os now ok. Thanks again. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 13:26:00 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 13:26:00 -0000 Subject: [MacPorts] #51344: seqan @2.1.1_0 Fixes installation of missing files In-Reply-To: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> References: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> Message-ID: <057.6e7d1faab79f68678c060c9dead83e8e@macports.org> #51344: seqan @2.1.1_0 Fixes installation of missing files ---------------------+--------------------------------- Reporter: rrahn | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch maintainer Port: seqan | ---------------------+--------------------------------- Comment (by raimue): The preferred format for diffs would be unified, which is usually created by running `diff -u Portfile.orig Portfile` as described in [https://guide.macports.org/#development.patches.portfile the guide]. Are you sure these are the right changes? The directory structure you are creating does not make sense. * The previous copy statement for `include` looked fine. What is the addition of a trailing slash supposed to solve? * This now creates `${prefix}/share/doc/doc/seqan/` (duplicate `doc/`) * The `.pc` file needs to go to `${prefix}/lib/pkgconfig/`. Similarly for the `.cmake` file, which would be expected in `${prefix}/lib/cmake/${name}/`. What is the point in not putting them into the default search paths? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 13:33:37 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 13:33:37 -0000 Subject: [MacPorts] #53030: ncftp @3.2.6 Checksum mismatch In-Reply-To: <046.b696169b01e43efd21e5d8e71dae82ee@macports.org> References: <046.b696169b01e43efd21e5d8e71dae82ee@macports.org> Message-ID: <061.021b6aea13f1c40d9fd4289432bfdbb9@macports.org> #53030: ncftp @3.2.6 Checksum mismatch ------------------------+---------------------- Reporter: crapshoot | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: ncftp | ------------------------+---------------------- Comment (by raimue): For future reference, the solution with `dist_subdir` is described in PortfileRecipes#stealth-updates. By the way, as we have multiple repositories configured on Trac, you need to specify the repository you want to link to with TracLinks: * [89fba1b1628ad3e98532879fac9497b78ce5ceb0/macports-ports] * [2196fe1c8f545af48f16838a3f9d07aba18b3d51/macports-ports] -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 13:44:21 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 13:44:21 -0000 Subject: [MacPorts] #51344: seqan @2.1.1_0 Fixes installation of missing files In-Reply-To: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> References: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> Message-ID: <057.d4377b64ee85e54eb59f1f00748c79aa@macports.org> #51344: seqan @2.1.1_0 Fixes installation of missing files ---------------------+--------------------------------- Reporter: rrahn | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch maintainer Port: seqan | ---------------------+--------------------------------- Comment (by rrahn): Right, these first two path changes were not intentionally. For the pkgconfig, I wasn't actually sure but thanks for pointing that out. It seems that `${prefix}/share/pkgconfig` is also a valid path. For cmake the given path is in the standard search path according to the `find_package` documentation. But if you prefer to install it into `lib` I can do that. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 13:55:08 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 13:55:08 -0000 Subject: [MacPorts] #53037: tuxtype @1.8.3 +Configure error: missing dependencies Message-ID: <044.893854147059eea5fd0f08f2c1cab3f8@macports.org> #53037: tuxtype @1.8.3 +Configure error: missing dependencies -------------------------------------------------+------------------------- Reporter: sonicth | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: tuxtype, "Tux Typing", t4k_common, | Port: tuxtype libsdl_net | -------------------------------------------------+------------------------- Port needs to be updated: 1) {{{libsdl_net}}} needs to be added as a dependency 2) {{{t4k_common}}} needs to be pulled from GitHub and built specifically for this port (NOTE t4k_common is broken, since sources moved to GitHub, please also see this: https://trac.macports.org/ticket/51582) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 13:55:54 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 13:55:54 -0000 Subject: [MacPorts] #53037: tuxtype @1.8.3 +Configure error: missing dependencies In-Reply-To: <044.893854147059eea5fd0f08f2c1cab3f8@macports.org> References: <044.893854147059eea5fd0f08f2c1cab3f8@macports.org> Message-ID: <059.20bd86fb11e9e8ec6b9b0b9442b97ffe@macports.org> #53037: tuxtype @1.8.3 +Configure error: missing dependencies -------------------------+------------------------------------------------- Reporter: sonicth | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: tuxtype, "Tux Typing", t4k_common, Port: tuxtype | libsdl_net -------------------------+------------------------------------------------- Changes (by sonicth): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 14:37:09 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 14:37:09 -0000 Subject: [MacPorts] #53037: tuxtype @1.8.3 +Configure error: missing dependencies In-Reply-To: <044.893854147059eea5fd0f08f2c1cab3f8@macports.org> References: <044.893854147059eea5fd0f08f2c1cab3f8@macports.org> Message-ID: <059.0577664f2a7832ce5cba56f692610fd7@macports.org> #53037: tuxtype @1.8.3 +Configure error: missing dependencies ----------------------+------------------- Reporter: sonicth | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: tuxtype | ----------------------+------------------- Changes (by mf2k): * keywords: tuxtype, "Tux Typing", t4k_common, libsdl_net => Comment: In the future, please use WikiFormatting. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 14:37:39 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 14:37:39 -0000 Subject: [MacPorts] #53037: tuxtype @1.8.3 +Configure error: missing dependencies In-Reply-To: <044.893854147059eea5fd0f08f2c1cab3f8@macports.org> References: <044.893854147059eea5fd0f08f2c1cab3f8@macports.org> Message-ID: <059.09b6cf55e1700c8e316695255c88292d@macports.org> #53037: tuxtype @1.8.3 +Configure error: missing dependencies ----------------------+------------------- Reporter: sonicth | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: tuxtype | ----------------------+------------------- Description changed by mf2k: Old description: > Port needs to be updated: > 1) {{{libsdl_net}}} needs to be added as a dependency > 2) {{{t4k_common}}} needs to be pulled from GitHub and built specifically > for this port > (NOTE t4k_common is broken, since sources moved to GitHub, please also > see this: https://trac.macports.org/ticket/51582) New description: Port needs to be updated: 1. {{{libsdl_net}}} needs to be added as a dependency 2. {{{t4k_common}}} needs to be pulled from GitHub and built specifically for this port (NOTE t4k_common is broken, since sources moved to GitHub, please also see this: ticket:51582 -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 14:42:05 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 14:42:05 -0000 Subject: [MacPorts] #52978: qt5 applications not finding platforms plugins In-Reply-To: <045.9c09814a332002fea84a56d085e2da6d@macports.org> References: <045.9c09814a332002fea84a56d085e2da6d@macports.org> Message-ID: <060.83e448694e66075e2c06d5ea0ed718dc@macports.org> #52978: qt5 applications not finding platforms plugins -----------------------+--------------------------------- Reporter: dmarteau | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: qt5 | -----------------------+--------------------------------- Changes (by mf2k): * status: new => assigned * owner: => MarcusCalhoun-Lopez * type: enhancement => defect Comment: In the future, please use WikiFormatting and Cc the port maintainers ({{{port info --maintainers qt5}}}), if any. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 14:42:22 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 14:42:22 -0000 Subject: [MacPorts] #52978: qt5 applications not finding platforms plugins In-Reply-To: <045.9c09814a332002fea84a56d085e2da6d@macports.org> References: <045.9c09814a332002fea84a56d085e2da6d@macports.org> Message-ID: <060.67c8df2ae88d42499ea583b23f1a7c75@macports.org> #52978: qt5 applications not finding platforms plugins -----------------------+--------------------------------- Reporter: dmarteau | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: qt5 | -----------------------+--------------------------------- Description changed by mf2k: Old description: > Actually when compiling and running a qt5 application I need to set up > explicitly the environnement variable QT_QPA_PLATFORM_PLUGIN_PATH or the > application would not start with the error: > > ``` > Fatal: This application failed to start because it could not find or load > the Qt platform plugin "cocoa" > in "". > ``` > > It is not clear if this is a qt5 installation problem or if this should > be handled by the application. > > Thanks New description: Actually when compiling and running a qt5 application I need to set up explicitly the environnement variable QT_QPA_PLATFORM_PLUGIN_PATH or the application would not start with the error: {{{ Fatal: This application failed to start because it could not find or load the Qt platform plugin "cocoa" in "". }}} It is not clear if this is a qt5 installation problem or if this should be handled by the application. Thanks -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 14:48:06 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 14:48:06 -0000 Subject: [MacPorts] #52978: qt5 applications not finding platforms plugins In-Reply-To: <045.9c09814a332002fea84a56d085e2da6d@macports.org> References: <045.9c09814a332002fea84a56d085e2da6d@macports.org> Message-ID: <060.09f99b9ae0252130c3dc140c9abdda7a@macports.org> #52978: qt5 applications not finding platforms plugins -----------------------+--------------------------------- Reporter: dmarteau | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: qt5 | -----------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): It would help if I could reproduce this error.[[BR]] What application is failing?[[BR]] Is it a MacPorts application? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 14:48:21 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 14:48:21 -0000 Subject: [MacPorts] #52978: qt5 applications not finding platforms plugins In-Reply-To: <045.9c09814a332002fea84a56d085e2da6d@macports.org> References: <045.9c09814a332002fea84a56d085e2da6d@macports.org> Message-ID: <060.b992673244649de2f9445c7536479970@macports.org> #52978: qt5 applications not finding platforms plugins -----------------------+--------------------------------- Reporter: dmarteau | Owner: MarcusCalhoun-Lopez Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: qt5 | -----------------------+--------------------------------- Changes (by MarcusCalhoun-Lopez): * status: assigned => accepted -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 14:53:04 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 14:53:04 -0000 Subject: [MacPorts] #52827: yarn @0.16.1 In-Reply-To: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> References: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> Message-ID: <061.0aa47886865a9e76bf81eec3a6f6bd84@macports.org> #52827: yarn @0.16.1 -------------------------+-------------------------------- Reporter: isomarcte | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: yarn | -------------------------+-------------------------------- Comment (by mf2k): Some comments: - Since you are using the Github portgroup, you should be able to remove the {{{distname}}} and {{{worksrcdir}}} lines because they should be set correctly already by the portgroup. - Can openmaintainer be added? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 14:56:43 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 14:56:43 -0000 Subject: [MacPorts] #52978: qt5 applications not finding platforms plugins In-Reply-To: <045.9c09814a332002fea84a56d085e2da6d@macports.org> References: <045.9c09814a332002fea84a56d085e2da6d@macports.org> Message-ID: <060.c30a11cc529f569f87a7113b4024f6fd@macports.org> #52978: qt5 applications not finding platforms plugins -----------------------+--------------------------------- Reporter: dmarteau | Owner: MarcusCalhoun-Lopez Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: qt5 | -----------------------+--------------------------------- Comment (by dmarteau): No this is not a MacPorts application, this in QGIS (from branch master) which now depends on QT5 that I am compiling. All compiling tools (cmake) and qt5 libraries are from Macports installation. This is why I said that it is not clear for me if this is a qt5 installation problem or if this should be handled by the application at compile time. Afaik this problem does not occurs on linux platform. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 14:57:14 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 14:57:14 -0000 Subject: [MacPorts] #51344: seqan @2.1.1_0 Fixes installation of missing files In-Reply-To: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> References: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> Message-ID: <057.51bc1a9714716a68b54f76606503a19f@macports.org> #51344: seqan @2.1.1_0 Fixes installation of missing files ---------------------+--------------------------------- Reporter: rrahn | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch maintainer Port: seqan | ---------------------+--------------------------------- Changes (by rrahn): * Attachment "Portfile-seqan.diff" removed. Cleaned up patch file -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 14:57:14 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 14:57:14 -0000 Subject: [MacPorts] #51344: seqan @2.1.1_0 Fixes installation of missing files In-Reply-To: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> References: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> Message-ID: <057.edf0a8574b6e736df1b61e3a197757ac@macports.org> #51344: seqan @2.1.1_0 Fixes installation of missing files ---------------------+--------------------------------- Reporter: rrahn | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch maintainer Port: seqan | ---------------------+--------------------------------- Changes (by rrahn): * Attachment "Portfile-seqan.diff" added. Cleaned up patch file -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 15:20:09 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 15:20:09 -0000 Subject: [MacPorts] #53038: nvm @0.32.1: New port submission Message-ID: <045.dc7197e3aae2807b83a493ebec9dddfe@macports.org> #53038: nvm @0.32.1: New port submission ------------------------+----------------- Reporter: coditect | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: nvm ------------------------+----------------- I have created a Portfile for NVM, a version manager for Node. It differs from a normal install of NVM in the following ways: * NVM and NVM-managed version of Node are stored in `$prefix/lib/nvm` instead of `~/.nvm` * NVM does not need to be initialized in `~/.profile`. Instead, a script stored at `$prefix/bin/nvm` intercepts calls to `nvm`, and runs `nvm.sh` before passing control to the `nvm()` shell function. This process is less efficient, but greatly simplifies the use of NVM with `sudo` and multiple user accounts. Suggestions and criticisms are greatly appreciated! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 15:20:26 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 15:20:26 -0000 Subject: [MacPorts] #53038: nvm @0.32.1: New port submission In-Reply-To: <045.dc7197e3aae2807b83a493ebec9dddfe@macports.org> References: <045.dc7197e3aae2807b83a493ebec9dddfe@macports.org> Message-ID: <060.5109ef9079c5d05dda4c8d3b0e68f730@macports.org> #53038: nvm @0.32.1: New port submission -------------------------+----------------- Reporter: coditect | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: nvm | -------------------------+----------------- Changes (by coditect): * Attachment "Portfile" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 16:39:21 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 16:39:21 -0000 Subject: [MacPorts] #51344: seqan @2.1.1_0 Fixes installation of missing files In-Reply-To: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> References: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> Message-ID: <057.c447112888cf6e8f99f4c8516e21d4eb@macports.org> #51344: seqan @2.1.1_0 Fixes installation of missing files ---------------------+--------------------------------- Reporter: rrahn | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch maintainer Port: seqan | ---------------------+--------------------------------- Comment (by raimue): Yes, both `${prefix}/lib/pkgconfig` and `${prefix}/share/pkgconfig` would be valid. I don't think there is any strong preference, but the former appears to be more popular among ports. I am no cmake expert and I don't know if there is any preference or difference in the `Find*.cmake` or `*-config.cmake` files. I am just wondering why upstream decides to use the former and then it is changed here to the latter. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 16:46:41 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 16:46:41 -0000 Subject: [MacPorts] #53039: luarocks 2.3.0: Unable to verify checksums Message-ID: <045.c62e9ba7df24f78fcf04241455501a97@macports.org> #53039: luarocks 2.3.0: Unable to verify checksums ----------------------+---------------------- Reporter: mathomp4 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: luarocks ----------------------+---------------------- I was trying to install luarocks today and I got a checksum failure (see below). I ran these commands based on other checksum tickets I saw, but I can run some more if requested. {{{ (12) $ port selfupdate ---> Updating MacPorts base sources using rsync MacPorts base version 2.3.5 installed, MacPorts base version 2.3.5 downloaded. ---> Updating the ports tree ---> MacPorts base is already the latest version The ports tree has been updated. To upgrade your installed ports, you should run port upgrade outdated (13) $ port clean --all luarocks ---> Cleaning luarocks (14) $ port -v checksum luarocks ---> Fetching distfiles for luarocks ---> luarocks-2.3.0.tar.gz does not exist in /Users/mathomp4/macports/var/macports/distfiles/luarocks ---> Attempting to fetch luarocks-2.3.0.tar.gz from https://github.com/keplerproject/luarocks/tarball/v2.3.0 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 139 0 139 0 0 215 0 --:--:-- --:--:-- --:--:-- 215 100 132 0 132 0 0 197 0 --:--:-- --:--:-- --:--:-- 197 100 3918k 100 3918k 0 0 3861k 0 0:00:01 0:00:01 --:--:-- 3861k ---> Verifying checksums for luarocks ---> Checksumming luarocks-2.3.0.tar.gz Error: Checksum (rmd160) mismatch for luarocks-2.3.0.tar.gz Portfile checksum: luarocks-2.3.0.tar.gz rmd160 7b435a44d738aac1a37436cb8fab6b14ae5deb10 Distfile checksum: luarocks-2.3.0.tar.gz rmd160 377103c0ac5ec62576a798da2b3e721162a9f241 Error: Checksum (sha256) mismatch for luarocks-2.3.0.tar.gz Portfile checksum: luarocks-2.3.0.tar.gz sha256 0e44e4246ee602dcc623b4a2c329a2c57627a598018d3474e30c28a91fe5276d Distfile checksum: luarocks-2.3.0.tar.gz sha256 b544a630f2a936e487745781dee342d2d90da1df91d35ded532a3a995affe719 The correct checksum line may be: checksums rmd160 377103c0ac5ec62576a798da2b3e721162a9f241 \ sha256 b544a630f2a936e487745781dee342d2d90da1df91d35ded532a3a995affe719 Error: org.macports.checksum for port luarocks returned: Unable to verify file checksums Warning: targets not executed for luarocks: org.macports.checksum Please see the log file for port luarocks for details: /Users/mathomp4/macports/var/macports/logs/_Users_mathomp4_macports_var_macports_sources_distfiles.macports.org_ports_devel_luarocks/luarocks/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port luarocks failed }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 17:15:55 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 17:15:55 -0000 Subject: [MacPorts] #53040: py27-wxpython-3.0 @3.0.2.0 fatal error: 'type_traits' file not found on systems upgraded to libc++ Message-ID: <042.60b960fe5a4bb70586997df006b20806@macports.org> #53040: py27-wxpython-3.0 @3.0.2.0 fatal error: 'type_traits' file not found on systems upgraded to libc++ --------------------+------------------------------- Reporter: kencu | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: py27-wxpython-3.0 --------------------+------------------------------- wxpython build stalls on 10.6 with libc++ (and I will presume other systems upgraded to libc++ < 10.9) due to {{{ fatal error: 'type_traits' file not found }}} the configuration phase gives a clue trouble is coming {{{ checking how to run the C++ preprocessor... /opt/local/bin/clang++-mp-3.7 -E checking type_traits usability... yes checking type_traits presence... no configure: WARNING: type_traits: accepted by the compiler, rejected by the preprocessor! configure: WARNING: type_traits: proceeding with the compiler's result checking for type_traits... yes checking for __sync_fetch_and_add and __sync_sub_and_fetch builtins... yes }}} which then fails during compilation: {{{ creating build/temp.macosx-10.6-x86_64-2.7/src/osx_cocoa /opt/local/bin/clang-mp-3.7 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict- prototypes -arch x86_64 -DSWIG_TYPE_TABLE=_wxPython_table -DSWIG_PYTHON_OUTPUT_TUPLE -DSWIG_PYTHON_SILENT_MEMLEAK -DWXP_USE_THREAD=1 -UNDEBUG -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXMAC__ -D__WXOSX__ -D__WXOSX_COCOA__ -Iinclude -Isrc -I/opt/local/Library/Frameworks/wxWidgets.framework/Versions/wxPython/3.0/lib/wx/include /osx_cocoa-unicode-3.0 -I/opt/local/Library/Frameworks/wxWidgets.framework/Versions/wxPython/3.0/include/wx-3.0 -I/opt/local/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c src/helpers.cpp -o build/temp.macosx-10.6-x86_64-2.7/src/helpers.o -O3 In file included from src/helpers.cpp:17: In file included from include/wx/wxPython/wxPython_int.h:35: In file included from /opt/local/Library/Frameworks/wxWidgets.framework/Versions/wxPython/3.0/include/wx-3.0/wx/wx.h:15: In file included from /opt/local/Library/Frameworks/wxWidgets.framework/Versions/wxPython/3.0/include/wx-3.0/wx/object.h:19: In file included from /opt/local/Library/Frameworks/wxWidgets.framework/Versions/wxPython/3.0/include/wx-3.0/wx/memory.h:15: In file included from /opt/local/Library/Frameworks/wxWidgets.framework/Versions/wxPython/3.0/include/wx-3.0/wx/string.h:46: /opt/local/Library/Frameworks/wxWidgets.framework/Versions/wxPython/3.0/include/wx-3.0/wx/strvararg.h:25:14: fatal error: 'type_traits' file not found #include }}} the solution seems to be to get -stdlib=libc++ onto that build command line. I tried various things, but in the end, adding the following bit to `wxPython-src-3.0.2.0/wxPython/config.py` in the darwin section worked. {{{ if sys.platform[:6] == "darwin": WXPLAT = '__WXMAC__' if WXPORT == 'osx_carbon': # Flags and such for a Darwin (Max OS X) build of Python GENDIR = 'osx_carbon' WXPLAT2 = '__WXOSX_CARBON__' else: GENDIR = 'osx_cocoa' WXPLAT2 = '__WXOSX_COCOA__' + cflags.append('-stdlib=libc++') + lflags.append('-stdlib=libc++') }}} I think only one of the the flag is actually used, but at this moment I'm not sure which one it is. in the end, success: {{{ $ port -v installed | grep py27-wxpython-3.0 py27-wxpython-3.0 @3.0.2.0_0 (active) platform='darwin 10' archs='x86_64' }}} not completely sure how to fully test the functionality at present, however. No doubt there are better ways to fix it, like rewriting the issue with the configure script to correctly decide whether to use `type_traits`. Is this useful enough to you to have me build a patch for it? Or shall we just leave it as an available workaround for people? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 17:25:08 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 17:25:08 -0000 Subject: [MacPorts] #53040: py27-wxpython-3.0 @3.0.2.0 fatal error: 'type_traits' file not found on systems upgraded to libc++ In-Reply-To: <042.60b960fe5a4bb70586997df006b20806@macports.org> References: <042.60b960fe5a4bb70586997df006b20806@macports.org> Message-ID: <057.a542163699edc3ac6441c039066a9769@macports.org> #53040: py27-wxpython-3.0 @3.0.2.0 fatal error: 'type_traits' file not found on systems upgraded to libc++ ------------------------------+---------------------------- Reporter: kencu | Owner: jyrkiwahlstedt Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-wxpython-3.0 | ------------------------------+---------------------------- Changes (by mf2k): * cc: jyrkiwahlstedt (removed) * status: new => assigned * port: py27-wxpython-3.0 => py-wxpython-3.0 * owner: => jyrkiwahlstedt -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 17:27:24 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 17:27:24 -0000 Subject: [MacPorts] #53040: py27-wxpython-3.0 @3.0.2.0 fatal error: 'type_traits' file not found on systems upgraded to libc++ In-Reply-To: <042.60b960fe5a4bb70586997df006b20806@macports.org> References: <042.60b960fe5a4bb70586997df006b20806@macports.org> Message-ID: <057.729e72290b769a52c3c28e02c482927b@macports.org> #53040: py27-wxpython-3.0 @3.0.2.0 fatal error: 'type_traits' file not found on systems upgraded to libc++ ------------------------------+---------------------------- Reporter: kencu | Owner: jyrkiwahlstedt Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-wxpython-3.0 | ------------------------------+---------------------------- Comment (by mojca): No, we should fix this properly rather than let users patch files manually. I can imagine that this is a problem since I already had problems building wxWidgets-3.0 and had to add the following: {{{ #!tcl if {[string match *clang* ${configure.cxx}]} { configure.ldflags-append \ -stdlib=${configure.cxx_stdlib} } }}} The main question is how to fix this properly and whether there is any way to submit this upstream / ask upstream to fix it. I reported the initial problem to wxWidgets developers, but they argued that whatever MacPorts is already setting is not sufficient. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 17:55:37 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 17:55:37 -0000 Subject: [MacPorts] #47338: mecab, p5-mecab: new repository, update homepage, master_sites, livecheck In-Reply-To: <044.e1b80c917d36576ceb92f502529f3ce4@macports.org> References: <044.e1b80c917d36576ceb92f502529f3ce4@macports.org> Message-ID: <059.f65bfd439505ed5b9b23a54d21d684c3@macports.org> #47338: mecab, p5-mecab: new repository, update homepage, master_sites, livecheck ------------------------------+-------------------------------- Reporter: dbevans | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: mecab, p5-mecab | ------------------------------+-------------------------------- Changes (by dbevans): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"365f845cb2d053655a6123fd2829ab0dfae93c2f/macports-ports" 365f845c/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="365f845cb2d053655a6123fd2829ab0dfae93c2f" mecab*, p5-mecab: new repository, update homepage, master_sites, livecheck * homepage to http://taku910.github.io/mecab/ * master_sites to macports_distfiles:mecab * disable livecheck Closes: https://trac.macports.org/ticket/47338 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 18:52:11 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 18:52:11 -0000 Subject: [MacPorts] #51344: seqan @2.1.1_0 Fixes installation of missing files In-Reply-To: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> References: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> Message-ID: <057.810b9fcdb0b740e93bed4460898e9421@macports.org> #51344: seqan @2.1.1_0 Fixes installation of missing files ---------------------+--------------------------------- Reporter: rrahn | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch maintainer Port: seqan | ---------------------+--------------------------------- Comment (by rrahn): Actually, FindSeqAn will be renamed to seqan-config in the upcoming release, as it is the proper way of distributing the package info for cmake. For 2.1.1 and 2.2.0 we have to manually rename it during installation process. I updated the port file to install now into `${prefix}/lib/pkgconfig` and ${prefix}/lib/cmake/seqan`. I hope I got it right this time. Many thanks for the support. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 19:16:42 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 19:16:42 -0000 Subject: [MacPorts] #53041: p5-xml-twig: update to version 3.52 Message-ID: <044.4f82598ac31c02610396d014082d8f12@macports.org> #53041: p5-xml-twig: update to version 3.52 ----------------------+------------------------------- Reporter: dbevans | Owner: frank.mcpherson@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: p5-xml-twig ----------------------+------------------------------- Proposed patch attached for this update including adding openmaintainer to facilitate future updates when maintainer is not available. Minor cleanups to remove outdated Id tag line and comment are also included. Please let me know if you approve these changes. Thanks. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 19:18:06 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 19:18:06 -0000 Subject: [MacPorts] #53041: p5-xml-twig: update to version 3.52 In-Reply-To: <044.4f82598ac31c02610396d014082d8f12@macports.org> References: <044.4f82598ac31c02610396d014082d8f12@macports.org> Message-ID: <059.3f6794fb0cfb8a1a5bce114a3e00e02f@macports.org> #53041: p5-xml-twig: update to version 3.52 --------------------------+------------------------------- Reporter: dbevans | Owner: frank.mcpherson@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: p5-xml-twig | --------------------------+------------------------------- Changes (by dbevans): * Attachment "p5-xml-twig-3.52.patch" added. Proposed patch to update p5-xml-twig -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 19:27:55 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 19:27:55 -0000 Subject: [MacPorts] #53038: nvm @0.32.1: New port submission In-Reply-To: <045.dc7197e3aae2807b83a493ebec9dddfe@macports.org> References: <045.dc7197e3aae2807b83a493ebec9dddfe@macports.org> Message-ID: <060.b2f89702e34411fa577f64fdf4add2d6@macports.org> #53038: nvm @0.32.1: New port submission -------------------------+----------------- Reporter: coditect | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: nvm | -------------------------+----------------- Changes (by ryandesign): * cc: ci42 (added) Comment: "openmaintainer" is not valid as the only maintainer. If nobody maintains the port, the correct value is "nomaintainer". Is there a specific reason why you wrote code to write a file? Usually, we put such files in the files directory and just copy them. It would be easier to follow if you put the code relating to the bash_completion variant into the bash_completion variant. I'll leave it to Christoph to decide whether it is a good idea to provide a port for nvm. (The way its use will cause unregistered files to be installed in $prefix/lib/nvm is for example undesirable, but I realize npm already does something similar.) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 19:33:01 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 19:33:01 -0000 Subject: [MacPorts] #53038: nvm @0.32.1: New port submission In-Reply-To: <045.dc7197e3aae2807b83a493ebec9dddfe@macports.org> References: <045.dc7197e3aae2807b83a493ebec9dddfe@macports.org> Message-ID: <060.505f1a52ff202795c33dfa0b38ca09f1@macports.org> #53038: nvm @0.32.1: New port submission -------------------------+----------------- Reporter: coditect | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: nvm | -------------------------+----------------- Comment (by ryandesign): Replying to [comment:1 ryandesign]: > Is there a specific reason why you wrote code to write a file? Usually, we put such files in the files directory and just copy them. I see you use some variables in the script. Typically, we handle that by putting a `@PLACEHOLDER@` in the file in the files directory, and then after you copy it to the right place, you can use `reinplace` to replace the placeholder with the real value. I also see the script runs nvm using `nvm $@`. That won't work for arguments containing spaces. You need `nvm "$@"`. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 19:35:37 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 19:35:37 -0000 Subject: [MacPorts] #53039: luarocks 2.3.0: Unable to verify checksums In-Reply-To: <045.c62e9ba7df24f78fcf04241455501a97@macports.org> References: <045.c62e9ba7df24f78fcf04241455501a97@macports.org> Message-ID: <060.e057dbec1da6921b72e98294655e65a3@macports.org> #53039: luarocks 2.3.0: Unable to verify checksums -----------------------+------------------- Reporter: mathomp4 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: luarocks | -----------------------+------------------- Comment (by ryandesign): This probably occurred because the "luarocks" project moved from the "keplerproject" GitHub organization to the "luarocks" GitHub organization, and the GitHub organization name is contained within the data that gets checksummed, so this caused the checksum to change. Meanwhile newer versions of luarocks have been released; perhaps we could update the port to 2.4.0, 2.4.1 or 2.4.2 while fixing this problem. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 19:39:20 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 19:39:20 -0000 Subject: [MacPorts] #53037: tuxtype @1.8.3 +Configure error: missing dependencies In-Reply-To: <044.893854147059eea5fd0f08f2c1cab3f8@macports.org> References: <044.893854147059eea5fd0f08f2c1cab3f8@macports.org> Message-ID: <059.c14761d4cdedf1e3fa47128f83b731d1@macports.org> #53037: tuxtype @1.8.3 +Configure error: missing dependencies ----------------------+------------------- Reporter: sonicth | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: tuxtype | ----------------------+------------------- Comment (by ryandesign): Why do you say: > t4k_common needs to be ... built specifically for this port Why would fixing the t4k_common port to fetch and build properly per #51582 not be sufficient? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 19:57:11 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 19:57:11 -0000 Subject: [MacPorts] #53037: tuxtype @1.8.3 +Configure error: missing dependencies In-Reply-To: <044.893854147059eea5fd0f08f2c1cab3f8@macports.org> References: <044.893854147059eea5fd0f08f2c1cab3f8@macports.org> Message-ID: <059.5512685077ffe84ef091978d030e8cc3@macports.org> #53037: tuxtype @1.8.3 +Configure error: missing dependencies ----------------------+------------------- Reporter: sonicth | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: tuxtype | ----------------------+------------------- Comment (by sonicth): Replying to [comment:3 ryandesign]: > > t4k_common needs to be ... built specifically for this port > > Why would fixing the t4k_common port to fetch and build properly per #51582 not be sufficient? That would be the best solution, probably. However, on the other hand, only two ports use it (those are '''TuxMath''' and '''Tux Typing''', or anything else...?). Would it not be simpler for each of these ports to just fetch the dependency individually? Maybe not? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 20:20:08 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 20:20:08 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.a9482f10e437eb671abfcdb1558998f8@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Comment (by mojca): See also r72086 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 20:20:27 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 20:20:27 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.3feb4961d3b15ce658f1b5004a7b8f98@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): `i960-rtems-binutils` says: > i960-rtems-gcc does not build on darwin 9+ (Mac OS X 10.5+) and it has been abandonned upstream. and I can confirm that it doesn't build for me. I suggest removing both ports (binutils and gcc). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 20:33:51 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 20:33:51 -0000 Subject: [MacPorts] #53038: nvm @0.32.1: New port submission In-Reply-To: <045.dc7197e3aae2807b83a493ebec9dddfe@macports.org> References: <045.dc7197e3aae2807b83a493ebec9dddfe@macports.org> Message-ID: <060.5109ef9079c5d05dda4c8d3b0e68f730@macports.org> #53038: nvm @0.32.1: New port submission -------------------------+----------------- Reporter: coditect | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: nvm | -------------------------+----------------- Changes (by coditect): * Attachment "Portfile" removed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 20:33:51 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 20:33:51 -0000 Subject: [MacPorts] #53038: nvm @0.32.1: New port submission In-Reply-To: <045.dc7197e3aae2807b83a493ebec9dddfe@macports.org> References: <045.dc7197e3aae2807b83a493ebec9dddfe@macports.org> Message-ID: <060.7d3907c159003f97032dc92d5302d7cf@macports.org> #53038: nvm @0.32.1: New port submission -------------------------+----------------- Reporter: coditect | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: nvm | -------------------------+----------------- Changes (by coditect): * Attachment "Portfile" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 20:34:06 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 20:34:06 -0000 Subject: [MacPorts] #53038: nvm @0.32.1: New port submission In-Reply-To: <045.dc7197e3aae2807b83a493ebec9dddfe@macports.org> References: <045.dc7197e3aae2807b83a493ebec9dddfe@macports.org> Message-ID: <060.924af92bbb41e2ee88213730582f03e2@macports.org> #53038: nvm @0.32.1: New port submission -------------------------+----------------- Reporter: coditect | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: nvm | -------------------------+----------------- Changes (by coditect): * Attachment "nvm_bin.sh" added. files/nvm_bin.sh -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 20:46:38 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 20:46:38 -0000 Subject: [MacPorts] #53038: nvm @0.32.1: New port submission In-Reply-To: <045.dc7197e3aae2807b83a493ebec9dddfe@macports.org> References: <045.dc7197e3aae2807b83a493ebec9dddfe@macports.org> Message-ID: <060.01718a74ea5e47b638e12548043a87df@macports.org> #53038: nvm @0.32.1: New port submission -------------------------+----------------- Reporter: coditect | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: nvm | -------------------------+----------------- Comment (by coditect): Replying to [comment:2 ryandesign]: Thanks for the feedback, Ryan. I uploaded a new version of the Portfile that incorporates your suggestions. I agree that leaving behind the contents of `$prefix/lib/nvm/alias`, `$prefix/lib/nvm/.cache`, and `$prefix/lib/nvm/versions` after uninstalling the port is undesirable. Is there any way to instruct MacPorts that those folders should be expunged during a `port uninstall`? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 20:55:16 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 20:55:16 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.90c74214e063b65b4bc0233f340c5615@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Old description: > I just noticed that when using the crossbinutils PortGroup, one ends up > with: > {{{ > /opt/local/${target}/host/lib/libiberty.a > /opt/local/include/libiberty/*.h > }}} > The first one is not problematic, but files under `$prefix/include` are > because any given binutils port would install that. > > I found a related commit: > * https://github.com/macports/macports- > ports/commit/bcdf26e5b403a4291f3c241f19e33eb86d7ca538 > > Judging from the fact that bfd installs > {{{ > /opt/local/${host}/bin/ld.bfd > /opt/local/${host}/host/include/*.h > /opt/local/${host}/host/lib/libbfd.a > /opt/local/${host}/host/lib/libbfd.la > }}} > I guess that some recent update of binutils broke the `reinplace` patch. > > This requires: > * a patch in the portgroup to fix the problem > * a revbump (or ideally upgrade) of all affected `*-binutils` ports > * probably a bit more testing with a couple of different binutils > versions > > Maybe the older versions are not even affected and a fix would break > older ports, I'm not sure. > > Existing binutils ports: > || arm-aout-binutils || @2.22 || > || arm-elf-binutils || @2.25 || > || arm-none-eabi-binutils || @2.23.1 || > || arm-none-linux-gnueabi-binutils || @2005q3-2 || > || arm-rtems-binutils || @2.18 || > || avr-binutils || @2.27 || > || i386-elf-binutils || @2.23.1 || > || i386-mingw32-binutils || @2.21-3 || > || i386-rtems-binutils || @2.18 || > || i960-rtems-binutils || @2.16.1 || > || lm32-rtems-binutils || @2.21.1 || > || m68k-elf-binutils || @2.17 || > || m68k-rtems-binutils || @2.18 || > || mips-elf-binutils || @2.17 || > || mips-rtems-binutils || @2.18 || > || mipsel-linux-binutils || @2.16.1 || > || msp430-binutils || @2.21.1a-20120406 || > || powerpc-rtems-binutils || @2.18 || > || ppc-linux-binutils || @2.25 || > || sh-rtems-binutils || @2.18 || > || sparc-rtems-binutils || @2.18 || > || spu-binutils || @2.20.51.0.5 || > || x86_64-elf-binutils || @2.23.1 || > > See also #51935. New description: I just noticed that when using the crossbinutils PortGroup, one ends up with: {{{ /opt/local/${target}/host/lib/libiberty.a /opt/local/include/libiberty/*.h }}} The first one is not problematic, but files under `$prefix/include` are because any given binutils port would install that. I found a related commit: * https://github.com/macports/macports- ports/commit/bcdf26e5b403a4291f3c241f19e33eb86d7ca538 Judging from the fact that bfd installs {{{ /opt/local/${host}/bin/ld.bfd /opt/local/${host}/host/include/*.h /opt/local/${host}/host/lib/libbfd.a /opt/local/${host}/host/lib/libbfd.la }}} I guess that some recent update of binutils broke the `reinplace` patch. This requires: * a patch in the portgroup to fix the problem * a revbump (or ideally upgrade) of all affected `*-binutils` ports * probably a bit more testing with a couple of different binutils versions Maybe the older versions are not even affected and a fix would break older ports, I'm not sure. Existing binutils ports: Using the portgroup: || avr-binutils || @2.27 || g5pw || || msp430-binutils || @2.21.1a-20120406 || g5pw || || msp430-binutils-devel || 2.22 || g5pw || || arm-elf-binutils || @2.25 || gmail:stuartwesterman || || arm-none-eabi-binutils || @2.23.1 || gmail:stuartwesterman || || i386-elf-binutils || @2.23.1 || gmail:jinksys || || x86_64-elf-binutils || @2.23.1 || gmail:nategriswold || || ppc-linux-binutils || @2.25 || || arm-aout-binutils || @2.22 || || spu-binutils || @2.20.51.0.5 || || mipsel-linux-binutils || @2.16.1 || Others: || arm-none-linux-gnueabi-binutils || @2005q3-2 || || arm-rtems-binutils || @2.18 || || i386-mingw32-binutils || @2.21-3 || || i386-rtems-binutils || @2.18 || || i960-rtems-binutils || @2.16.1 || || lm32-rtems-binutils || @2.21.1 || || m68k-elf-binutils || @2.17 || || m68k-rtems-binutils || @2.18 || || mips-elf-binutils || @2.17 || || mips-rtems-binutils || @2.18 || || powerpc-rtems-binutils || @2.18 || || sh-rtems-binutils || @2.18 || || sparc-rtems-binutils || @2.18 || See also #51935. -- Comment (by mojca): I sorted the ports a bit according to: * whether they use the portgroup * maintainer * version It could be that only the newer versions are affected. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 21:01:16 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 21:01:16 -0000 Subject: [MacPorts] #53038: nvm @0.32.1: New port submission In-Reply-To: <045.dc7197e3aae2807b83a493ebec9dddfe@macports.org> References: <045.dc7197e3aae2807b83a493ebec9dddfe@macports.org> Message-ID: <060.2ea26b9078d412a8267e206b536d8e6f@macports.org> #53038: nvm @0.32.1: New port submission -------------------------+----------------- Reporter: coditect | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: nvm | -------------------------+----------------- Comment (by coditect): Replying to [comment:1 ryandesign]: Regarding the appropriateness of providing a port for nvm: I think a cleaner solution would be to allow multiple `nodejs*` ports to be installed side-by-side (they currently conflict) and choosing the active version of node through `port select`. I think the biggest difficulty with this approach would be switching between different versions of of npm and the `node_modules` folder in tandem with node itself. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 21:04:27 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 21:04:27 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.11e5dc5fd7c6834586c80b3ce223f0b1@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Description changed by mojca: Old description: > I just noticed that when using the crossbinutils PortGroup, one ends up > with: > {{{ > /opt/local/${target}/host/lib/libiberty.a > /opt/local/include/libiberty/*.h > }}} > The first one is not problematic, but files under `$prefix/include` are > because any given binutils port would install that. > > I found a related commit: > * https://github.com/macports/macports- > ports/commit/bcdf26e5b403a4291f3c241f19e33eb86d7ca538 > > Judging from the fact that bfd installs > {{{ > /opt/local/${host}/bin/ld.bfd > /opt/local/${host}/host/include/*.h > /opt/local/${host}/host/lib/libbfd.a > /opt/local/${host}/host/lib/libbfd.la > }}} > I guess that some recent update of binutils broke the `reinplace` patch. > > This requires: > * a patch in the portgroup to fix the problem > * a revbump (or ideally upgrade) of all affected `*-binutils` ports > * probably a bit more testing with a couple of different binutils > versions > > Maybe the older versions are not even affected and a fix would break > older ports, I'm not sure. > > Existing binutils ports: > > Using the portgroup: > || avr-binutils || @2.27 || g5pw || > || msp430-binutils || @2.21.1a-20120406 || g5pw || > || msp430-binutils-devel || 2.22 || g5pw || > || arm-elf-binutils || @2.25 || > gmail:stuartwesterman || > || arm-none-eabi-binutils || @2.23.1 || > gmail:stuartwesterman || > || i386-elf-binutils || @2.23.1 || gmail:jinksys > || > || x86_64-elf-binutils || @2.23.1 || > gmail:nategriswold || > || ppc-linux-binutils || @2.25 || > || arm-aout-binutils || @2.22 || > || spu-binutils || @2.20.51.0.5 || > || mipsel-linux-binutils || @2.16.1 || > > Others: > || arm-none-linux-gnueabi-binutils || @2005q3-2 || > || arm-rtems-binutils || @2.18 || > || i386-mingw32-binutils || @2.21-3 || > || i386-rtems-binutils || @2.18 || > || i960-rtems-binutils || @2.16.1 || > || lm32-rtems-binutils || @2.21.1 || > || m68k-elf-binutils || @2.17 || > || m68k-rtems-binutils || @2.18 || > || mips-elf-binutils || @2.17 || > || mips-rtems-binutils || @2.18 || > || powerpc-rtems-binutils || @2.18 || > || sh-rtems-binutils || @2.18 || > || sparc-rtems-binutils || @2.18 || > > See also #51935. New description: I just noticed that when using the crossbinutils PortGroup, one ends up with: {{{ /opt/local/${target}/host/lib/libiberty.a /opt/local/include/libiberty/*.h }}} The first one is not problematic, but files under `$prefix/include` are because any given binutils port would install that. I found a related commit: * https://github.com/macports/macports- ports/commit/bcdf26e5b403a4291f3c241f19e33eb86d7ca538 Judging from the fact that bfd installs {{{ /opt/local/${host}/bin/ld.bfd /opt/local/${host}/host/include/*.h /opt/local/${host}/host/lib/libbfd.a /opt/local/${host}/host/lib/libbfd.la }}} I guess that some recent update of binutils broke the `reinplace` patch. This requires: * a patch in the portgroup to fix the problem * a revbump (or ideally upgrade) of all affected `*-binutils` ports * probably a bit more testing with a couple of different binutils versions Maybe the older versions are not even affected and a fix would break older ports, I'm not sure. Existing binutils ports: Using the portgroup: || avr-binutils || @2.27 || g5pw || || msp430-binutils || @2.21.1a-20120406 || g5pw || || msp430-binutils-devel || 2.22 || g5pw || || arm-elf-binutils || @2.25 || gmail:stuartwesterman || || arm-none-eabi-binutils || @2.23.1 || gmail:stuartwesterman || || i386-elf-binutils || @2.23.1 || gmail:jinksys || || x86_64-elf-binutils || @2.23.1 || gmail:nategriswold || || ppc-linux-binutils || @2.25 || || arm-aout-binutils || @2.22 || || spu-binutils || @2.20.51.0.5 || Others: || arm-none-linux-gnueabi-binutils || @2005q3-2 || || arm-rtems-binutils || @2.18 || || i386-mingw32-binutils || @2.21-3 || || i386-rtems-binutils || @2.18 || || i960-rtems-binutils || @2.16.1 || || lm32-rtems-binutils || @2.21.1 || || m68k-elf-binutils || @2.17 || || m68k-rtems-binutils || @2.18 || || mips-elf-binutils || @2.17 || || mips-rtems-binutils || @2.18 || || mipsel-linux-binutils || @2.16.1 || || powerpc-rtems-binutils || @2.18 || || sh-rtems-binutils || @2.18 || || sparc-rtems-binutils || @2.18 || See also #51935. -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 21:10:08 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 21:10:08 -0000 Subject: [MacPorts] #53042: gnuradio @3.7.10.1_1 install fails on Snow Leopard due to undeclared long long math prototypes - and fix Message-ID: <042.83f707075941558260948d2d3f3e7ca4@macports.org> #53042: gnuradio @3.7.10.1_1 install fails on Snow Leopard due to undeclared long long math prototypes - and fix -------------------------+---------------------- Reporter: kencu | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: snowleopard | Port: gnuradio -------------------------+---------------------- building gnuradio on 10.6.8 hits a pause when certain long long math prototypes are not found, like this: {{{ error: use of undeclared identifier 'llrintf' }}} the problem appears to be due to several missing long long math prototypes previously identified and fixed by Jeremy in other ports (like clang-3.8). See [ticket:52130] and . Indeed, adding in that same block of missing prototypes from Jeremy's libcxx github commit fixes the current gnuradio and the build proceeds successfully and gnuradio appears to run. The block should have gone into this file: {{{ gnuradio-3.7.10.1/gnuradio-runtime/include/gnuradio/math.h }}} but for some reason that didn't work immediately for me. Might have been something stupid on my end, like pasting it in but not writing to disk before I compiled again. Anyway, I stuck it here {{{ gnuradio-3.7.10.1/gr-blocks/lib/float_array_to_int.cc }}} and it worked fine. Haven't hooked it up to a radio yet, but the windows open and the waterfall and other displays come up. Thanks for gnuradio. My ham license should be more fun with some of those new USB radios to play with. I might be the only person on earth who cares to run gnuradio on 10.6.8. Do you want a patch and some further fiddling to to see if the math.h fix can be made to work correctly, or should we just leave this on trac for interested persons to find? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 21:25:24 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 21:25:24 -0000 Subject: [MacPorts] #53042: gnuradio @3.7.10.1_1 install fails on Snow Leopard due to undeclared long long math prototypes - and fix In-Reply-To: <042.83f707075941558260948d2d3f3e7ca4@macports.org> References: <042.83f707075941558260948d2d3f3e7ca4@macports.org> Message-ID: <057.8896c2a93472374b26bc1cf1784b1d19@macports.org> #53042: gnuradio @3.7.10.1_1 install fails on Snow Leopard due to undeclared long long math prototypes - and fix -----------------------+------------------------- Reporter: kencu | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: gnuradio | -----------------------+------------------------- Comment (by michaelld): I would welcome a patch, yes! More compatibility is better. Let's take this off-MP ... email me directly at michael.dickens at ettus.com . Thx! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 21:27:16 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 21:27:16 -0000 Subject: [MacPorts] #53042: gnuradio @3.7.10.1_1 install fails on Snow Leopard due to undeclared long long math prototypes - and fix In-Reply-To: <042.83f707075941558260948d2d3f3e7ca4@macports.org> References: <042.83f707075941558260948d2d3f3e7ca4@macports.org> Message-ID: <057.fb4d0fa46468c963fb4d1db43f8304af@macports.org> #53042: gnuradio @3.7.10.1_1 install fails on Snow Leopard due to undeclared long long math prototypes - and fix -----------------------+------------------------- Reporter: kencu | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: gnuradio | -----------------------+------------------------- Changes (by ryandesign): * owner: => michaelld * status: new => assigned * cc: michaelld (removed) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 21:28:19 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 21:28:19 -0000 Subject: [MacPorts] #47318: gnuradio: gnuradio-companion: command not found In-Reply-To: <050.7306b1d76aca2cf2a123253e91ec91e4@macports.org> References: <050.7306b1d76aca2cf2a123253e91ec91e4@macports.org> Message-ID: <065.c6dd7843a482d29ae711eb9b298e2354@macports.org> #47318: gnuradio: gnuradio-companion: command not found -------------------------+----------------------- Reporter: luuc@… | Owner: michaelld Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: worksforme | Keywords: Port: gnuradio | -------------------------+----------------------- Changes (by ryandesign): * status: new => closed * resolution: => worksforme Comment: Since there's been no response from the reporter in well over a year, I'll close this ticket. If it's still a problem, please reopen it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 22:28:01 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 22:28:01 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.3c44410f82bbd80e83adbebd70591355@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Comment (by mojca): I opened a [https://github.com/macports/macports-ports/pull/90/ pull request] for the ports that include the PortGroup. Others are probably not affected anyway. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 22:29:41 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 22:29:41 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.ad33aa1bf2b2e6ef89d06b6b0e869509@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): I opened a [https://github.com/macports/macports-ports/pull/90/ pull request] that updates some of the ports that use the PortGroup. I tried converting some others, but that often requires a lot more work and modifications. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 22:38:18 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 22:38:18 -0000 Subject: [MacPorts] #41787: wxmsw @2.8.4: +universal variant fails because i386-mingw32-w32api is not universal In-Reply-To: <057.72a121d1607b662d2d30ac7ae4a943d4@macports.org> References: <057.72a121d1607b662d2d30ac7ae4a943d4@macports.org> Message-ID: <072.597b587cde10fa1e7b3be1c85b66c403@macports.org> #41787: wxmsw @2.8.4: +universal variant fails because i386-mingw32-w32api is not universal ----------------------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: wontfix | Keywords: Port: wxmsw i386-mingw32-w32api | ----------------------------------------+-------------------------------- Changes (by mojca): * status: new => closed * resolution: => wontfix Comment: I don't see a reason for keeping this ticket open (or for trying to address the issue). I would actually prefer to remove both wxmsw and the old mingw once the new mingw-w64 is added. If you have a good reason why this should be fixed, please speak up. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 22:40:47 2016 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2016 22:40:47 -0000 Subject: [MacPorts] #31578: Update i386-mingw32-gcc to latest version In-Reply-To: <042.69c7bf42c3aceaea3de77468f68babec@macports.org> References: <042.69c7bf42c3aceaea3de77468f68babec@macports.org> Message-ID: <057.1ea18a86f5a447b6622e5e758aadb3af@macports.org> #31578: Update i386-mingw32-gcc to latest version -------------------------------+----------------------- Reporter: mojca | Owner: landonf@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: wontfix | Keywords: Port: i386-mingw32-gcc | -------------------------------+----------------------- Changes (by mojca): * status: new => closed * resolution: => wontfix Comment: After five years I'm closing my own ticket as I don't think it's worth spending any time at all fixing issues with the old MinGW cross-compiler. It makes more sense to switch to MinGW-w64 completely. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 00:01:48 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 00:01:48 -0000 Subject: [MacPorts] #52516: sundials @2.6.2_1: update to 2.7.0, add +fcmix In-Reply-To: <046.5029d3318db8e0e993f5d643efb20855@macports.org> References: <046.5029d3318db8e0e993f5d643efb20855@macports.org> Message-ID: <061.a06f71d9ac5352bf270eab47215c4242@macports.org> #52516: sundials @2.6.2_1: update to 2.7.0, add +fcmix ------------------------+------------------------ Reporter: jjstickel | Owner: seanfarley Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: sundials | ------------------------+------------------------ Comment (by seanfarley): Just need to test it with PETSc. I usually use this example to verify it worked: {{{ $ cd petsc/src/ts/examples/tutorials $ make ex3 $ ./ex3 -ts_type sundials }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 02:34:47 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 02:34:47 -0000 Subject: [MacPorts] #50845: libunwind: fails to find 'bits/c++config.h' on 10.5/PPC In-Reply-To: <042.dc439143bad4305d12829f44ffd3509f@macports.org> References: <042.dc439143bad4305d12829f44ffd3509f@macports.org> Message-ID: <057.1bec0c1cda12b8471c2d28e0c70fd060@macports.org> #50845: libunwind: fails to find 'bits/c++config.h' on 10.5/PPC ------------------------+---------------------- Reporter: mojca | Owner: jeremyhu Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: leopard Port: libunwind | ------------------------+---------------------- Comment (by mascondante): Per https://trac.macports.org/wiki/LibcxxOnOlderSystems#Leopardppc I stall here. My specific log (should it help) can be found here: https://ghostbin.com/paste/gpxuz My configuration: https://ghostbin.com/paste/nd557 Hoping to get up to C++ 11. The older systems file (unrelated I realize) seems to show it's doable. Hoping some love for the last of the PPC generation continues to be shown as you folks have been so fabulously spearheading so far. Thank you. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 03:26:43 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 03:26:43 -0000 Subject: [MacPorts] #53043: py-sphinx dependents: remove py26 and py33 Message-ID: <043.c9ddeb2c0ac22f69cf03bf226e020391@macports.org> #53043: py-sphinx dependents: remove py26 and py33 -------------------------+------------------------------------------------- Reporter: jmroot | Owner: seanfarley Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: py26-hieroglyph py33-hieroglyph | py26-pydicom -------------------------+------------------------------------------------- Sphinx 1.5 has dropped support for Python 2.6 and 3.3. The dependents of py26-sphinx and py33-sphinx will thus need to be removed before I update. (If you really need it, I could instead keep those sphinx subports at 1.4.9, but that's a little more work.) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 03:58:03 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 03:58:03 -0000 Subject: [MacPorts] #51599: main.log is never deleted with "keeplogs yes" In-Reply-To: <047.9755d7bd7d52ac696cbb8591edc781ed@macports.org> References: <047.9755d7bd7d52ac696cbb8591edc781ed@macports.org> Message-ID: <062.634bb972e763dbcab543e27a75e9959f@macports.org> #51599: main.log is never deleted with "keeplogs yes" -------------------------+-------------------------------- Reporter: ryandesign | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: | Keywords: Port: | -------------------------+-------------------------------- Comment (by jmroot): Isn't the entire point of that setting to prevent logs from being deleted by clean? I don't see the bug here. If your concern is that there is no way to delete logs, `port clean --logs` does that. For reference, the responsible code in portclean.tcl is {{{ if {(([info exists ports_clean_logs] && $ports_clean_logs eq "yes") || ($keeplogs eq "no")) && !$usealtworkpath} { clean_logs } }}} and the basic logic there has not changed since 2009 with [58be192b342eebd6f73719371ad53011d053c3b9/macports-base]. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 04:34:53 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 04:34:53 -0000 Subject: [MacPorts] #53031: macports ncl fails, mac install of ncarg works In-Reply-To: <043.2f66a17331fd430dc6114c13ca7272cd@macports.org> References: <043.2f66a17331fd430dc6114c13ca7272cd@macports.org> Message-ID: <058.03bccac2bb3475e8e6e696fd87da3a84@macports.org> #53031: macports ncl fails, mac install of ncarg works ---------------------+---------------------- Reporter: basmac | Owner: tenomoto Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: ncarg | ---------------------+---------------------- Comment (by tenomoto): Thanks for reporting. I was able to reproduce the problem, but I don't have a solution at the moment. It appears that {{{setfileoption}}} break the symbol table and {{{Opt}}} becomes undefined, I attach the simple script to cause the error. BTW, I'd like to draw your attention the warning message on line 47. {{{ warning:["Palette.c":1850]:NhlLoadColormapFiles: Invalid colormap directory: /opt/local/ncl/lib/ncarg/colormaps }}} The default {{{NCARG_COLORMAPS}}} should be {{{/opt/local/lib/ncarg/colormaps}}}. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 04:35:45 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 04:35:45 -0000 Subject: [MacPorts] #53031: macports ncl fails, mac install of ncarg works In-Reply-To: <043.2f66a17331fd430dc6114c13ca7272cd@macports.org> References: <043.2f66a17331fd430dc6114c13ca7272cd@macports.org> Message-ID: <058.9661cd5468f00fe2d17faa855606ce56@macports.org> #53031: macports ncl fails, mac install of ncarg works ---------------------+---------------------- Reporter: basmac | Owner: tenomoto Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: ncarg | ---------------------+---------------------- Changes (by tenomoto): * Attachment "bar.ncl" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 05:46:28 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 05:46:28 -0000 Subject: [MacPorts] #50986: Dependencies fail to install because hostnames cannot be resolved because we've run out of file descriptors In-Reply-To: <065.e9b6bca89adc00c5c4582978bef7bae7@macports.org> References: <065.e9b6bca89adc00c5c4582978bef7bae7@macports.org> Message-ID: <080.787eb1b5db8fa411e047e3e5b1ab5336@macports.org> #50986: Dependencies fail to install because hostnames cannot be resolved because we've run out of file descriptors -----------------------------------+-------------------------------- Reporter: benedikt.hielscher@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: base | Version: 2.3.4 Resolution: | Keywords: elcapitan sierra Port: | -----------------------------------+-------------------------------- Comment (by jmroot): In [changeset:"b856b49512cc7c50bc064f056e97fad7ca5b3f5e/macports-base" b856b495/macports-base]: {{{ #!ConfigurableCommitTicketReference repository="macports-base" revision="b856b49512cc7c50bc064f056e97fad7ca5b3f5e" Always maximise RLIMIT_NOFILE This should at least work around problems with running out of fds. Code calling setrlimit has been moved from one place in tracelib.c and put in its own command, which is called from mportinit. See: https://trac.macports.org/ticket/50986 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 05:47:47 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 05:47:47 -0000 Subject: [MacPorts] #50986: Dependencies fail to install because hostnames cannot be resolved because we've run out of file descriptors In-Reply-To: <065.e9b6bca89adc00c5c4582978bef7bae7@macports.org> References: <065.e9b6bca89adc00c5c4582978bef7bae7@macports.org> Message-ID: <080.16070560a0fc0ebea43a9c614452148c@macports.org> #50986: Dependencies fail to install because hostnames cannot be resolved because we've run out of file descriptors -----------------------------------+-------------------------------- Reporter: benedikt.hielscher@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: base | Version: 2.3.4 Resolution: | Keywords: elcapitan sierra Port: | -----------------------------------+-------------------------------- Comment (by jmroot): As per the above, there's now a workaround in master that should hopefully do the trick. I'd still very much like to know what's using up all our fds. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 06:25:02 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 06:25:02 -0000 Subject: [MacPorts] #53032: dumpasn1 port broken - sources cannot be found In-Reply-To: <050.0ccd2d20c3fbe8910c09cef6b72869b3@macports.org> References: <050.0ccd2d20c3fbe8910c09cef6b72869b3@macports.org> Message-ID: <065.5ace953d82495cf56d4a96db6ecf3c53@macports.org> #53032: dumpasn1 port broken - sources cannot be found ----------------------------+---------------------- Reporter: snappy-pickle | Owner: cjr@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: dumpasn1 | ----------------------------+---------------------- Comment (by snappy-pickle): Replying to [comment:1 mf2k]: > In the future, please fill in the Port field and Cc the port maintainers ({{{port info --maintainers dumpasn1}}}), if any. Eeek! Apologies! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 06:48:32 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 06:48:32 -0000 Subject: [MacPorts] #43210: Missing error messages In-Reply-To: <047.09dd9c62990eaecdfff758ebece63b12@macports.org> References: <047.09dd9c62990eaecdfff758ebece63b12@macports.org> Message-ID: <062.c85662d30ab13a145c14b3b14dfc1a39@macports.org> #43210: Missing error messages -------------------------+------------------------ Reporter: ryandesign | Owner: neverpanic Type: defect | Status: assigned Priority: Normal | Milestone: Component: base | Version: 2.2.99 Resolution: | Keywords: Port: | -------------------------+------------------------ Comment (by jmroot): I set up the same situation with 3 dummy ports and got this result: {{{ % sudo port upgrade testport1 ---> Computing dependencies for testport1 ---> Dependencies to be installed: testport2 ---> Activating testport2 @1.1_0 Error: Failed to activate testport2: Image error: /opt/local/share/doc/testport2/foo is being used by the active testport3 port. Please deactivate this port first, or use 'port -f activate testport2' to force the activation. Error: See /opt/local/var/macports/logs/_Users_josh_Coding_dports- dev_local_test_testport2/testport2/main.log for details. Error: Follow https://guide.macports.org/#project.tickets to report a bug. }}} Maybe this is only an issue in conjunction with whatever made the portfile in the registry fail? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 06:57:26 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 06:57:26 -0000 Subject: [MacPorts] #47592: rev-upgrade should use prefix_unwritable check (was: rev-upgrade should always require root privileges) In-Reply-To: <051.6b88e216d1f8cbd19533ee9e2cfed884@macports.org> References: <051.6b88e216d1f8cbd19533ee9e2cfed884@macports.org> Message-ID: <066.678d7fd829ac378046f339225bf0a671@macports.org> #47592: rev-upgrade should use prefix_unwritable check ----------------------+------------------------ Reporter: mp@… | Owner: neverpanic Type: defect | Status: assigned Priority: Not set | Milestone: Component: base | Version: 2.3.99 Resolution: | Keywords: Port: | ----------------------+------------------------ Comment (by jmroot): Changing summary since MacPorts can be installed in a non-root-owned prefix, and in that case it can be run without root privileges and rev- upgrade should still work. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 07:33:34 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 07:33:34 -0000 Subject: [MacPorts] #47592: rev-upgrade should use prefix_unwritable check In-Reply-To: <051.6b88e216d1f8cbd19533ee9e2cfed884@macports.org> References: <051.6b88e216d1f8cbd19533ee9e2cfed884@macports.org> Message-ID: <066.d2638c515b39521f14566b7def7eb57b@macports.org> #47592: rev-upgrade should use prefix_unwritable check ----------------------+------------------------ Reporter: mp@… | Owner: neverpanic Type: defect | Status: closed Priority: Not set | Milestone: Component: base | Version: 2.3.99 Resolution: fixed | Keywords: Port: | ----------------------+------------------------ Changes (by jmroot): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"d4f49041852b9cf42e47d373cce7a3239d76a7fa/macports-base" d4f4904/macports-base]: {{{ #!ConfigurableCommitTicketReference repository="macports-base" revision="d4f49041852b9cf42e47d373cce7a3239d76a7fa" Avoid rev-upgrade permissions errors Check that the prefix is writable when running rev-upgrade in rebuild mode, and fail early with a good message if not. Fixes: https://trac.macports.org/ticket/47592 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 07:33:45 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 07:33:45 -0000 Subject: [MacPorts] #47592: rev-upgrade should use prefix_unwritable check In-Reply-To: <051.6b88e216d1f8cbd19533ee9e2cfed884@macports.org> References: <051.6b88e216d1f8cbd19533ee9e2cfed884@macports.org> Message-ID: <066.64604f6de883c332d47a1c1d7f120e3e@macports.org> #47592: rev-upgrade should use prefix_unwritable check ----------------------+---------------------------- Reporter: mp@… | Owner: neverpanic Type: defect | Status: closed Priority: Not set | Milestone: MacPorts 2.4.0 Component: base | Version: 2.3.99 Resolution: fixed | Keywords: Port: | ----------------------+---------------------------- Changes (by jmroot): * milestone: => MacPorts 2.4.0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 07:50:33 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 07:50:33 -0000 Subject: [MacPorts] #43210: Missing error messages In-Reply-To: <047.09dd9c62990eaecdfff758ebece63b12@macports.org> References: <047.09dd9c62990eaecdfff758ebece63b12@macports.org> Message-ID: <062.f38f1e5b09bbbfe8b84f4477a129bbb4@macports.org> #43210: Missing error messages -------------------------+------------------------ Reporter: ryandesign | Owner: neverpanic Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.2.99 Resolution: duplicate | Keywords: Port: | -------------------------+------------------------ Changes (by jmroot): * status: assigned => closed * resolution: => duplicate Comment: Actually, the situation was slightly different in that unixODBC declares a conflict with virtuoso-7. So, dupe of #49334. Output from current master with conflicts declared, for the record: {{{ % sudo port upgrade testport1 Password: ---> Computing dependencies for testport1 Error: Can't install testport2 because conflicting ports are active: testport3 Error: Follow https://guide.macports.org/#project.tickets to report a bug. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 07:59:26 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 07:59:26 -0000 Subject: [MacPorts] #41722: livecheck and distfiles overwrite main.log In-Reply-To: <047.03b932db7bb458c31f6d7307cfff3ac9@macports.org> References: <047.03b932db7bb458c31f6d7307cfff3ac9@macports.org> Message-ID: <062.8a57ee9cd27472c9cde21ab4eb1be27b@macports.org> #41722: livecheck and distfiles overwrite main.log -------------------------+-------------------------------- Reporter: ryandesign | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts Future Component: base | Version: 2.2.99 Resolution: | Keywords: Port: | -------------------------+-------------------------------- Comment (by jmroot): This should no longer be the case in current master since logs are appended to now, right? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 08:17:49 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 08:17:49 -0000 Subject: [MacPorts] #50845: libunwind: fails to find 'bits/c++config.h' on 10.5/PPC In-Reply-To: <042.dc439143bad4305d12829f44ffd3509f@macports.org> References: <042.dc439143bad4305d12829f44ffd3509f@macports.org> Message-ID: <057.cb027edb69b0154bac500bac5f087613@macports.org> #50845: libunwind: fails to find 'bits/c++config.h' on 10.5/PPC ------------------------+---------------------- Reporter: mojca | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: leopard Port: libunwind | ------------------------+---------------------- Changes (by jeremyhu): * status: new => closed * resolution: => fixed Comment: The reported problem with incorrect include paths on Leopard was fixed in dca2c7ae4a4e4ad1164b389ae82ae9f8c3dc6e90, and I provided a fix upstream in actually https://llvm.org/bugs/show_bug.cgi?id=30858 I've got libunwind built on Leopard, so I believe this is resolved. @mascondante, Leopard/ppc support is *very* experimental, and no support is offered for that configuration. Please open another ticket to track your issue. What architecture is /opt/local/bin/clang-mp-3.4? I suspect there might be a bug in the compiler as I remember seeing something like that in the past. Are you able to execute it x86_64 or just i386? Can you try using macports-clang-3.3 to build libunwind? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 08:18:54 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 08:18:54 -0000 Subject: [MacPorts] #50845: libunwind: fails to find 'bits/c++config.h' on 10.5/PPC In-Reply-To: <042.dc439143bad4305d12829f44ffd3509f@macports.org> References: <042.dc439143bad4305d12829f44ffd3509f@macports.org> Message-ID: <057.6336e6784279632424f8fee0cfc7a2b6@macports.org> #50845: libunwind: fails to find 'bits/c++config.h' on 10.5/PPC ------------------------+---------------------- Reporter: mojca | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: leopard Port: libunwind | ------------------------+---------------------- Comment (by jeremyhu): Also, why are you trying to build libunwind for ppc with 3.4? You should really be using a much newer toolchain for the ppc support. Use the older intel toolchain to bootstrap the newer toolchains, and use that to build your ppc executables. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 11:44:08 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 11:44:08 -0000 Subject: [MacPorts] #42725: Use modern tools for 'port pkg' on newer OS versions In-Reply-To: <054.6c91ba3a7aa7d0bc744e3171e70fd385@macports.org> References: <054.6c91ba3a7aa7d0bc744e3171e70fd385@macports.org> Message-ID: <069.fc539bdf1930b73deb785480ecf20c1a@macports.org> #42725: Use modern tools for 'port pkg' on newer OS versions --------------------------+-------------------------------- Reporter: rob@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.2.1 Resolution: fixed | Keywords: Port: | --------------------------+-------------------------------- Changes (by jmroot): * status: new => closed * resolution: => fixed Comment: In [changeset:"dd89bb80ff262bab1403da89d2d09e4a9ef32839/macports-base" dd89bb8/macports-base]: {{{ #!ConfigurableCommitTicketReference repository="macports-base" revision="dd89bb80ff262bab1403da89d2d09e4a9ef32839" Use pkgbuild when possible PackageMaker.app has been removed from Xcode tools for some time, so use pkgbuild instead when it's available and we're building flat packages. Fixes: https://trac.macports.org/ticket/42725 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 11:45:29 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 11:45:29 -0000 Subject: [MacPorts] #42725: Use modern tools for 'port pkg' on newer OS versions In-Reply-To: <054.6c91ba3a7aa7d0bc744e3171e70fd385@macports.org> References: <054.6c91ba3a7aa7d0bc744e3171e70fd385@macports.org> Message-ID: <069.b2a18bfdd711534388f7d3f7f9e67ec0@macports.org> #42725: Use modern tools for 'port pkg' on newer OS versions --------------------------+-------------------------------- Reporter: rob@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: MacPorts 2.4.0 Component: base | Version: 2.2.1 Resolution: fixed | Keywords: Port: | --------------------------+-------------------------------- Changes (by jmroot): * milestone: => MacPorts 2.4.0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 11:47:07 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 11:47:07 -0000 Subject: [MacPorts] #47592: rev-upgrade should use prefix_unwritable check In-Reply-To: <051.6b88e216d1f8cbd19533ee9e2cfed884@macports.org> References: <051.6b88e216d1f8cbd19533ee9e2cfed884@macports.org> Message-ID: <066.f6ad0919ef5fe5093eb026bf5162acf7@macports.org> #47592: rev-upgrade should use prefix_unwritable check ---------------------+---------------------------- Reporter: mp@… | Owner: neverpanic Type: defect | Status: closed Priority: Normal | Milestone: MacPorts 2.4.0 Component: base | Version: 2.3.99 Resolution: fixed | Keywords: Port: | ---------------------+---------------------------- Changes (by jmroot): * priority: Not set => Normal -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 12:26:29 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 12:26:29 -0000 Subject: [MacPorts] #48439: port selfupdate - privileges error message In-Reply-To: <056.ccf9498c5ca7618342e261e557693093@macports.org> References: <056.ccf9498c5ca7618342e261e557693093@macports.org> Message-ID: <071.4517d32443b1ba09db5641dea2f8fd20@macports.org> #48439: port selfupdate - privileges error message -----------------------------+-------------------------------- Reporter: grunermonzon@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Low | Milestone: Component: base | Version: 2.3.3 Resolution: fixed | Keywords: Port: | -----------------------------+-------------------------------- Changes (by jmroot): * status: new => closed * resolution: => fixed Comment: In [changeset:"68016b825bdd8d7f422e6216a397c4c57cecde01/macports-base" 68016b8/macports-base]: {{{ #!ConfigurableCommitTicketReference repository="macports-base" revision="68016b825bdd8d7f422e6216a397c4c57cecde01" Add prefix_unwritable check for selfupdate Fail early with a good message if the user forgot to use sudo or otherwise can't write to the prefix. Fixes: https://trac.macports.org/ticket/48439 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 12:28:11 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 12:28:11 -0000 Subject: [MacPorts] #48439: port selfupdate - privileges error message In-Reply-To: <056.ccf9498c5ca7618342e261e557693093@macports.org> References: <056.ccf9498c5ca7618342e261e557693093@macports.org> Message-ID: <071.63b1fa8f792d2d7dcb71a5a8d712b9ac@macports.org> #48439: port selfupdate - privileges error message -----------------------------+-------------------------------- Reporter: grunermonzon@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Low | Milestone: MacPorts 2.4.0 Component: base | Version: 2.3.3 Resolution: fixed | Keywords: Port: | -----------------------------+-------------------------------- Changes (by jmroot): * milestone: => MacPorts 2.4.0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 12:38:04 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 12:38:04 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ Message-ID: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ ------------------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: snowleopard lion | Port: octave ------------------------------+--------------------------------- Octave fails to build on pre-10.9 platforms with libstdc++: {{{ :info:build In file included from libinterp/corefcn/Cell.cc:25: :info:build In file included from ./config.h:3485: :info:build ./oct-conf-post.h:186:12: fatal error: 'cstdint' file not found :info:build # include :info:build ^ :info:build preserving existing HG-ID file :info:build make[3]: Entering directory `/path/to/octave/work/octave-4.2.0' :info:build make[3]: Leaving directory `/path/to/octave/work/octave-4.2.0' :info:build CXX libinterp/corefcn/libinterp_corefcn_libcorefcn_la- __contourc__.lo :info:build In file included from libinterp/corefcn/__contourc__.cc:36: :info:build In file included from ./config.h:3485: :info:build ./oct-conf-post.h:186:12: fatal error: 'cstdint' file not found :info:build # include :info:build ^ :info:build 1 error generated. }}} Some buildbot links: * [https://build.macports.org/builders/ports-10.6_x86_64_legacy- builder/builds/12318 10.6] [https://build.macports.org/builders/ports-10.6_i386_legacy- builder/builds/11882 10.6 i386] * [https://build.macports.org/builders/ports-10.7_x86_64_legacy- builder/builds/17554 10.7] * [https://build.macports.org/builders/ports-10.8_x86_64_legacy- builder/builds/12252 10.8] I didn't even check the PPC builds and 10.9 fails in a different way: * [https://build.macports.org/builders/ports-10.9_x86_64-builder/builds/12309 10.9] See: * http://stackoverflow.com/questions/10116724/clang-os-x-lion-cannot-find- cstdint -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 13:05:34 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 13:05:34 -0000 Subject: [MacPorts] #52845: mpv 0.21 update In-Reply-To: <043.e673edb81f111939a6207eb0205e5927@macports.org> References: <043.e673edb81f111939a6207eb0205e5927@macports.org> Message-ID: <058.5c89bb563c546ae676daea457d7c2869@macports.org> #52845: mpv 0.21 update ---------------------+---------------------- Reporter: iMiKED | Owner: Ionic Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: mpv | ---------------------+---------------------- Comment (by jf): I don't know how far along this update is, but if it's not too much trouble, is it ok to update to 0.22.0 instead (see https://github.com/mpv- player/mpv/releases/tag/v0.22.0)? Thank you! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 13:22:46 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 13:22:46 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.ce355112e2ce4e7063fa255a0d5fbb48@macports.org> #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Comment (by mojca): Just for completeness, 4.0.3 installed without any problems. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 14:58:52 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 14:58:52 -0000 Subject: [MacPorts] #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') Message-ID: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') --------------------+-------------------- Reporter: RJVB | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: ruby23 --------------------+-------------------- Trying to build port:ruby23 from source I get the following error: {{{ > sudo port -sv install ruby23 ... :info:build CC = /usr/bin/clang :info:build LD = ld :info:build LDSHARED = /usr/bin/clang -dynamiclib :info:build CFLAGS = -Os -fno-common -pipe -arch x86_64 :info:build XCFLAGS = -D_FORTIFY_SOURCE=2 -fstack-protector -fno- strict-overflow -fvisibility=hidden -DRUBY_EXPORT :info:build CPPFLAGS = -I/opt/local/include -I/opt/local/include -D_XOPEN_SOURCE -D_DARWIN_C_SOURCE -D_DARWIN_UNLIMITED_SELECT -D_REENTRANT -I. -I.ext/include/x86_64-darwin13 -I./include -I. :info:build DLDFLAGS = -Wl,-undefined,dynamic_lookup -Wl,-multiply_defined,suppress -L/opt/local/lib -install_name /opt/local/lib/libruby.2.3.0.dylib -current_version 2.3.0 -compatibility_version 2.3.3 -fstack-protector -Wl,-u,_objc_msgSend -framework CoreFoundation -fstack-protector -Wl,-u,_objc_msgSend -framework CoreFoundation -arch x86_64 :info:build SOLIBS = -lpthread -ldl -lobjc :info:build Apple LLVM version 6.0 (clang-600.0.57) (based on LLVM 3.5svn) :info:build Target: x86_64-apple-darwin13.4.0 :info:build Thread model: posix :info:build translating probes probes.d :info:build error: unable to open output file '/dev/fd/8': '' :info:build 1 error generated. :info:build dtrace: failed to compile script probes.d: Preprocessor failed to process input program :info:build make: *** [probes.h] Error 1 ... }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 15:01:23 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 15:01:23 -0000 Subject: [MacPorts] #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') In-Reply-To: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> References: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> Message-ID: <056.ab40727d0e93cb6c95e0a4f58807b0f9@macports.org> #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') ---------------------+----------------- Reporter: RJVB | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ruby23 | ---------------------+----------------- Changes (by RJVB): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 15:05:36 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 15:05:36 -0000 Subject: [MacPorts] #53046: editors/neovim: please update to 0.1.7 (released Nov 27) Message-ID: <039.10a4f815af396149e4935bf28477d027@macports.org> #53046: editors/neovim: please update to 0.1.7 (released Nov 27) --------------------+----------------- Reporter: jf | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: --------------------+----------------- Latest is 0.1.7 (https://github.com/neovim/neovim/releases/latest), released November 27 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 15:36:43 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 15:36:43 -0000 Subject: [MacPorts] #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') In-Reply-To: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> References: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> Message-ID: <056.ab4875e41ae0c42a6fa750ed4cc65936@macports.org> #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') ---------------------+---------------------- Reporter: RJVB | Owner: kimuraw Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ruby23 | ---------------------+---------------------- Changes (by mf2k): * cc: kimuraw@… (removed) * owner: => kimuraw * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 16:08:09 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 16:08:09 -0000 Subject: [MacPorts] #53047: [Port Abandoned] p5-xml-twig Message-ID: <041.e3ab8292d5fe7018a4326c1a33adbfc2@macports.org> #53047: [Port Abandoned] p5-xml-twig --------------------+------------------------------- Reporter: mf2k | Owner: frank.mcpherson@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: p5-xml-twig --------------------+------------------------------- maintainer has not been seen [search:frank.mcpherson at janusresearch.com since 2007] and has an [query:status=!closed&owner=frank.mcpherson at janusresearch.com open ticket]. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 16:14:30 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 16:14:30 -0000 Subject: [MacPorts] #41722: livecheck and distfiles overwrite main.log In-Reply-To: <047.03b932db7bb458c31f6d7307cfff3ac9@macports.org> References: <047.03b932db7bb458c31f6d7307cfff3ac9@macports.org> Message-ID: <062.356e7ae15dd22f79d274fcb0489fd8a5@macports.org> #41722: livecheck and distfiles overwrite main.log -------------------------+-------------------------------- Reporter: ryandesign | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts Future Component: base | Version: 2.2.99 Resolution: | Keywords: Port: | -------------------------+-------------------------------- Comment (by raimue): Even then the livecheck log messages will probably be somewhere between the build log messages. Writing logs is not possible if run without sudo, while the command itself works just fine this way, so logs will already only be written in some cases. Is there a reason to ever write logs for these port targets? I think logging should honor `target_state ${org.macports.livecheck} no`, which is also used on other targets and for example also prevents creating a work directory. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 16:15:11 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 16:15:11 -0000 Subject: [MacPorts] #53046: editors/neovim: please update to 0.1.7 (released Nov 27) In-Reply-To: <039.10a4f815af396149e4935bf28477d027@macports.org> References: <039.10a4f815af396149e4935bf28477d027@macports.org> Message-ID: <054.93cb6f07e93d600c08c11ce4477b278e@macports.org> #53046: editors/neovim: please update to 0.1.7 (released Nov 27) ---------------------+---------------------- Reporter: jf | Owner: raimue Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | ---------------------+---------------------- Changes (by raimue): * owner: => raimue * status: new => accepted -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 16:15:46 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 16:15:46 -0000 Subject: [MacPorts] #53046: editors/neovim: please update to 0.1.7 (released Nov 27) In-Reply-To: <039.10a4f815af396149e4935bf28477d027@macports.org> References: <039.10a4f815af396149e4935bf28477d027@macports.org> Message-ID: <054.e804ec85286546166c7daa9a51519d82@macports.org> #53046: editors/neovim: please update to 0.1.7 (released Nov 27) ---------------------+---------------------- Reporter: jf | Owner: raimue Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: neovim | ---------------------+---------------------- Changes (by raimue): * port: => neovim Comment: Please remember to fill the port field and CC maintainers (`port info --maintainers neovim`). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 16:20:55 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 16:20:55 -0000 Subject: [MacPorts] #53048: libbiosig @1.8.0: update to 1.8.4 Message-ID: <047.ecd7a0974fd0e76c0c2936b16a849065@macports.org> #53048: libbiosig @1.8.0: update to 1.8.4 ---------------------------------+----------------------- Reporter: neurodroid | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch maintainer | Port: libbiosig ---------------------------------+----------------------- Several bug fixes & compatibility improvements Maintainer (christsc at gmx.de) posts from github account -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 16:21:39 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 16:21:39 -0000 Subject: [MacPorts] #53048: libbiosig @1.8.0: update to 1.8.4 In-Reply-To: <047.ecd7a0974fd0e76c0c2936b16a849065@macports.org> References: <047.ecd7a0974fd0e76c0c2936b16a849065@macports.org> Message-ID: <062.0dc4a74a2a89de2e47d35914f874c019@macports.org> #53048: libbiosig @1.8.0: update to 1.8.4 -------------------------+--------------------------------- Reporter: neurodroid | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: libbiosig | -------------------------+--------------------------------- Changes (by neurodroid): * Attachment "Portfile-libbiosig.diff" added. libbiosig Portfile patch -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 16:24:40 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 16:24:40 -0000 Subject: [MacPorts] #53049: gqrx dependency missing Message-ID: <047.a52d7adc49f837cb619e48c8ee89512f@macports.org> #53049: gqrx dependency missing ------------------------+---------------------------- Reporter: umtauscher | Owner: Type: defect | Status: new Priority: Normal | Milestone: MacPorts 2.3.6 Component: ports | Version: Keywords: qt5, gqrx | Port: gqrx ------------------------+---------------------------- It seems the port ist missing the dependency for the qt5 package -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 16:27:25 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 16:27:25 -0000 Subject: [MacPorts] #53046: editors/neovim: please update to 0.1.7 (released Nov 27) In-Reply-To: <039.10a4f815af396149e4935bf28477d027@macports.org> References: <039.10a4f815af396149e4935bf28477d027@macports.org> Message-ID: <054.4663aaed3efeece15900f1eb22dfba5f@macports.org> #53046: editors/neovim: please update to 0.1.7 (released Nov 27) ---------------------+---------------------- Reporter: jf | Owner: raimue Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: neovim | ---------------------+---------------------- Comment (by jf): gotcha. Sorry about that! About the maintainers field: if it's "openmaintainer", I suppose that means there are no real maintainers (and therefore that field does not have a value)? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 17:00:37 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 17:00:37 -0000 Subject: [MacPorts] #50845: libunwind: fails to find 'bits/c++config.h' on 10.5/PPC In-Reply-To: <042.dc439143bad4305d12829f44ffd3509f@macports.org> References: <042.dc439143bad4305d12829f44ffd3509f@macports.org> Message-ID: <057.40b15067035f1d1106a02df43967ed9d@macports.org> #50845: libunwind: fails to find 'bits/c++config.h' on 10.5/PPC ------------------------+---------------------- Reporter: mojca | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: leopard Port: libunwind | ------------------------+---------------------- Comment (by kencu): Replying to [comment:7 mascondante]: > Per https://trac.macports.org/wiki/LibcxxOnOlderSystems#Leopardppc I stall at what is described in this ticket. > My specific log (should it help) can be found here: https://ghostbin.com/paste/gpxuz Comment 4 above indicates the exact same error you had. If you look at comment 5, the solution is to disable universal building of libunwind (it will build as PPC or as intel code, but for some reason not as both at the same time). Best, K -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 17:05:44 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 17:05:44 -0000 Subject: [MacPorts] #53046: editors/neovim: please update to 0.1.7 (released Nov 27) In-Reply-To: <039.10a4f815af396149e4935bf28477d027@macports.org> References: <039.10a4f815af396149e4935bf28477d027@macports.org> Message-ID: <054.0f25b693cf59b2fdc808f5301ded5cee@macports.org> #53046: editors/neovim: please update to 0.1.7 (released Nov 27) ---------------------+---------------------- Reporter: jf | Owner: raimue Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: neovim | ---------------------+---------------------- Comment (by mf2k): {{{nomaintainer}}} means that the port has no maintainer. See the [wiki:MacPortsDevelopers#special wiki page] for further explanation. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 17:07:52 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 17:07:52 -0000 Subject: [MacPorts] #53046: editors/neovim: please update to 0.1.7 (released Nov 27) In-Reply-To: <039.10a4f815af396149e4935bf28477d027@macports.org> References: <039.10a4f815af396149e4935bf28477d027@macports.org> Message-ID: <054.44d53cd81e9a5ebe503ff82465806e94@macports.org> #53046: editors/neovim: please update to 0.1.7 (released Nov 27) ---------------------+---------------------- Reporter: jf | Owner: raimue Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: neovim | ---------------------+---------------------- Comment (by jf): I see. My bad! I missed the first line and only saw the 2nd (am on a small font here). Thanks for your - double! - patience, guys! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 17:17:47 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 17:17:47 -0000 Subject: [MacPorts] #53036: [Port New] libchewing In-Reply-To: <042.8b452ee8a9de3a161a300385f4be9866@macports.org> References: <042.8b452ee8a9de3a161a300385f4be9866@macports.org> Message-ID: <057.71c2684227880d33bd1c08a3231d304f@macports.org> #53036: [Port New] libchewing -------------------------+----------------- Reporter: cwlin | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libchewing | -------------------------+----------------- Changes (by cwlin): * Attachment "Portfile" removed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 17:17:48 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 17:17:48 -0000 Subject: [MacPorts] #53036: [Port New] libchewing In-Reply-To: <042.8b452ee8a9de3a161a300385f4be9866@macports.org> References: <042.8b452ee8a9de3a161a300385f4be9866@macports.org> Message-ID: <057.fbf326348840042e11b55bcca4f8a315@macports.org> #53036: [Port New] libchewing -------------------------+----------------- Reporter: cwlin | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libchewing | -------------------------+----------------- Changes (by cwlin): * Attachment "Portfile" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 17:30:30 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 17:30:30 -0000 Subject: [MacPorts] #53036: [Port New] libchewing In-Reply-To: <042.8b452ee8a9de3a161a300385f4be9866@macports.org> References: <042.8b452ee8a9de3a161a300385f4be9866@macports.org> Message-ID: <057.fbf326348840042e11b55bcca4f8a315@macports.org> #53036: [Port New] libchewing -------------------------+----------------- Reporter: cwlin | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libchewing | -------------------------+----------------- Changes (by cwlin): * Attachment "Portfile" removed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 17:30:30 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 17:30:30 -0000 Subject: [MacPorts] #53036: [Port New] libchewing In-Reply-To: <042.8b452ee8a9de3a161a300385f4be9866@macports.org> References: <042.8b452ee8a9de3a161a300385f4be9866@macports.org> Message-ID: <057.632b94b666ed0b6050cdd785315e2232@macports.org> #53036: [Port New] libchewing -------------------------+----------------- Reporter: cwlin | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libchewing | -------------------------+----------------- Changes (by cwlin): * Attachment "Portfile" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 17:33:48 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 17:33:48 -0000 Subject: [MacPorts] #53036: [Port New] libchewing In-Reply-To: <042.8b452ee8a9de3a161a300385f4be9866@macports.org> References: <042.8b452ee8a9de3a161a300385f4be9866@macports.org> Message-ID: <057.84aef41a3e83e39b55207babbbcf2eab@macports.org> #53036: [Port New] libchewing -------------------------+----------------- Reporter: cwlin | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libchewing | -------------------------+----------------- Comment (by cwlin): Hi Ryan, I've updated the Portfile based on your comment. Thanks for your suggestion! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 17:45:21 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 17:45:21 -0000 Subject: [MacPorts] #51582: Error: org.macports.checksum for port t4k_common returned: Unable to verify file checksums In-Reply-To: <055.8d73c4f5bda5e3f8dbfaf60b2d44415c@macports.org> References: <055.8d73c4f5bda5e3f8dbfaf60b2d44415c@macports.org> Message-ID: <070.05e81aa22b133a321335c2619b38a2b2@macports.org> #51582: Error: org.macports.checksum for port t4k_common returned: Unable to verify file checksums -------------------------+-------------------------------- Reporter: accounts@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: t4k_common | -------------------------+-------------------------------- Changes (by kurthindenburg): * status: new => closed * resolution: => fixed Comment: In [changeset:"d29073724b1a08476f281f3361ad31c466089ee1/macports-ports" d2907372/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="d29073724b1a08476f281f3361ad31c466089ee1" t4k_common: move to github closes https://trac.macports.org/ticket/51582 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 18:36:03 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 18:36:03 -0000 Subject: [MacPorts] #53037: tuxtype @1.8.3 +Configure error: missing dependencies In-Reply-To: <044.893854147059eea5fd0f08f2c1cab3f8@macports.org> References: <044.893854147059eea5fd0f08f2c1cab3f8@macports.org> Message-ID: <059.49c8f3119601cb57054571176272c164@macports.org> #53037: tuxtype @1.8.3 +Configure error: missing dependencies ----------------------+------------------- Reporter: sonicth | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: tuxtype | ----------------------+------------------- Comment (by kurthindenburg): I've "Fixed" t4k_common and I'll commit a "fix" for this port - as far as I tell it works as expected - let me know of any issues. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 18:37:52 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 18:37:52 -0000 Subject: [MacPorts] #53037: tuxtype @1.8.3 +Configure error: missing dependencies In-Reply-To: <044.893854147059eea5fd0f08f2c1cab3f8@macports.org> References: <044.893854147059eea5fd0f08f2c1cab3f8@macports.org> Message-ID: <059.0011099d4b1975179079220ac7980e6c@macports.org> #53037: tuxtype @1.8.3 +Configure error: missing dependencies ----------------------+---------------------------- Reporter: sonicth | Owner: kurthindenburg Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: tuxtype | ----------------------+---------------------------- Changes (by kurthindenburg): * owner: => kurthindenburg * status: new => closed * resolution: => fixed Comment: In [changeset:"fc74d9cb41e78bda79ca7c78a0c400cf53b29496/macports-ports" fc74d9cb/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="fc74d9cb41e78bda79ca7c78a0c400cf53b29496" tuxtype: move to github and add deps add libsdl_net and t4k_common deps closes https://trac.macports.org/ticket/53037 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 19:02:59 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 19:02:59 -0000 Subject: [MacPorts] #52865: Port request: eric6 In-Reply-To: <043.b6ef4dd6c9a1e6cd98e3751186c62c97@macports.org> References: <043.b6ef4dd6c9a1e6cd98e3751186c62c97@macports.org> Message-ID: <058.878f2a815fb769be80a47913d159b882@macports.org> #52865: Port request: eric6 ----------------------+-------------------------------- Reporter: iEFdev | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: eric6 | ----------------------+-------------------------------- Changes (by kurthindenburg): * cc: kurthindenburg (added) * version: 2.3.4 => * port: eric4 => eric6 Comment: So far the only change needed is {{{ master_sites sourceforge:project/eric-ide/${name}/stable/${version} }}} the big issues are getting the deps correct for all the variants - have you worked on that anymore? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 19:59:43 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 19:59:43 -0000 Subject: [MacPorts] #50845: libunwind: fails to find 'bits/c++config.h' on 10.5/PPC In-Reply-To: <042.dc439143bad4305d12829f44ffd3509f@macports.org> References: <042.dc439143bad4305d12829f44ffd3509f@macports.org> Message-ID: <057.732118c770af6344feda574f7ec22e0e@macports.org> #50845: libunwind: fails to find 'bits/c++config.h' on 10.5/PPC ------------------------+---------------------- Reporter: mojca | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: leopard Port: libunwind | ------------------------+---------------------- Comment (by jeremyhu): Thanks, Ken. Is this something we should get added to the LibcxxOnOlderSystems guide? Can you send me a suggested edit to make things clearer? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 20:17:17 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 20:17:17 -0000 Subject: [MacPorts] #53022: opencv @3.1.0_6+python34: Portfile broken for variant +python34 In-Reply-To: <044.4cfc0421df7d7ecacd2795ceaf0f1af4@macports.org> References: <044.4cfc0421df7d7ecacd2795ceaf0f1af4@macports.org> Message-ID: <059.0ed302254b032c3e9f281a9bd82afa46@macports.org> #53022: opencv @3.1.0_6+python34: Portfile broken for variant +python34 ----------------------+---------------------- Reporter: detlevd | Owner: mkae Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: opencv | ----------------------+---------------------- Changes (by mkae): * owner: stromnov => mkae * cc: stromnov (added) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 20:17:34 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 20:17:34 -0000 Subject: [MacPorts] #53022: opencv @3.1.0_6+python34: Portfile broken for variant +python34 In-Reply-To: <044.4cfc0421df7d7ecacd2795ceaf0f1af4@macports.org> References: <044.4cfc0421df7d7ecacd2795ceaf0f1af4@macports.org> Message-ID: <059.793765b1ac8d17d7f42171c3026f06a8@macports.org> #53022: opencv @3.1.0_6+python34: Portfile broken for variant +python34 ----------------------+---------------------- Reporter: detlevd | Owner: mkae Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: opencv | ----------------------+---------------------- Changes (by mkae): * cc: mkae (removed) * version: 2.3.4 => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 20:53:43 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 20:53:43 -0000 Subject: [MacPorts] #53049: gqrx dependency missing In-Reply-To: <047.a52d7adc49f837cb619e48c8ee89512f@macports.org> References: <047.a52d7adc49f837cb619e48c8ee89512f@macports.org> Message-ID: <062.0e6d24a6b86bc153ceb779c18fdc1424@macports.org> #53049: gqrx dependency missing -------------------------+----------------------- Reporter: umtauscher | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gqrx | -------------------------+----------------------- Changes (by ryandesign): * owner: => michaelld * status: new => assigned * keywords: qt5, gqrx => * milestone: MacPorts 2.3.6 => Comment: gqrx already has a dependency on qt5-qtbase: {{{ $ port deps gqrx Full Name: gqrx @2.6_1 Build Dependencies: pkgconfig Library Dependencies: qt5-qtbase, gr-osmosdr, gnuradio }}} Is that not sufficient? What problem are you seeing? Can you show us a terminal transcript or attach a log file? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 20:55:18 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 20:55:18 -0000 Subject: [MacPorts] #31945: *-rtems-* ports are all out of date. In-Reply-To: <053.654934225253a598c0065334f00165b2@macports.org> References: <053.654934225253a598c0065334f00165b2@macports.org> Message-ID: <068.ccea47efe02c08f4e05bdc250859e94d@macports.org> #31945: *-rtems-* ports are all out of date. -------------------------------------------------+------------------------- Reporter: chrisj@… | Owner: macports- | tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Resolution: | Keywords: Port: arm-rtems-binutils arm-rtems-gcc | i386-rtems-binutils i386-rtems-gcc i960 | -rtems-binutils i960-rtems-gcc lm32-rtems- | binutils m68k-rtems-binutils m68k-rtems-gcc | mips-rtems-binutils mips-rtems-gcc powerpc- | rtems-binutils powerpc-rtems-gcc sh-rtems- | binutils sh-rtems-gcc sparc-rtems-binutils | sparc-rtems-gcc | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"c9a5124265ec67a9885a1e4a4d24b24fcee43251/macports-ports" c9a51242/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="c9a5124265ec67a9885a1e4a4d24b24fcee43251" i960-rtems-(binutils|gcc): remove obsolete ports These ports no longer build on 10.5+, abandoned upstream. See: https://trac.macports.org/ticket/31945 See: https://trac.macports.org/ticket/51935 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 20:55:18 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 20:55:18 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.14c072c4e84a0900277baa62f1bd5444@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"c9a5124265ec67a9885a1e4a4d24b24fcee43251/macports-ports" c9a51242/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="c9a5124265ec67a9885a1e4a4d24b24fcee43251" i960-rtems-(binutils|gcc): remove obsolete ports These ports no longer build on 10.5+, abandoned upstream. See: https://trac.macports.org/ticket/31945 See: https://trac.macports.org/ticket/51935 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 20:56:35 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 20:56:35 -0000 Subject: [MacPorts] #53048: libbiosig @1.8.0: update to 1.8.4 In-Reply-To: <047.ecd7a0974fd0e76c0c2936b16a849065@macports.org> References: <047.ecd7a0974fd0e76c0c2936b16a849065@macports.org> Message-ID: <062.d635a42afc7825e407ef7ffb0d559cfe@macports.org> #53048: libbiosig @1.8.0: update to 1.8.4 -------------------------+--------------------------------- Reporter: neurodroid | Owner: ryandesign Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: libbiosig | -------------------------+--------------------------------- Changes (by ryandesign): * status: new => accepted * owner: => ryandesign Comment: Thanks. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 20:58:41 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 20:58:41 -0000 Subject: [MacPorts] #31945: *-rtems-* ports are all out of date. In-Reply-To: <053.654934225253a598c0065334f00165b2@macports.org> References: <053.654934225253a598c0065334f00165b2@macports.org> Message-ID: <068.e437d1afbd8f9d73af05219411047c97@macports.org> #31945: *-rtems-* ports are all out of date. -------------------------------------------------+------------------------- Reporter: chrisj@… | Owner: macports- | tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Resolution: | Keywords: Port: arm-rtems-binutils arm-rtems-gcc | i386-rtems-binutils i386-rtems-gcc i960 | -rtems-binutils i960-rtems-gcc lm32-rtems- | binutils m68k-rtems-binutils m68k-rtems-gcc | mips-rtems-binutils mips-rtems-gcc powerpc- | rtems-binutils powerpc-rtems-gcc sh-rtems- | binutils sh-rtems-gcc sparc-rtems-binutils | sparc-rtems-gcc | -------------------------------------------------+------------------------- Comment (by mojca): I accidentally stumbled on this ticket. I'm willing to look into this if it is still relevant and if someone can provide basic guidance and testing. I have no clue how to test anything beyond checking whether the source compiles successfully. See also #51935. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 21:00:26 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 21:00:26 -0000 Subject: [MacPorts] #52827: yarn @0.16.1 In-Reply-To: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> References: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> Message-ID: <061.883e86cfd6ab65bbef14e22ec697975a@macports.org> #52827: yarn @0.16.1 -------------------------+-------------------------------- Reporter: isomarcte | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: yarn | -------------------------+-------------------------------- Comment (by jambonrose): Hi Frank, Thanks for your feedback! I've got a PR open that integrates many of David's changes: https://github.com/macports/macports-ports/pull/48 I added the `openmaintainer` line you requested. I attempted to remove `distname` and `worksrcdir`, but this resulted in errors. Removing `worksrcdir`: {{{ Error: org.macports.extract for port yarn returned: no files matched glob pattern "/opt/local/var/macports/build/_Users_magus_Ports_devel_yarn/yarn/work /yarnpkg-yarn-*" Please see the log file for port yarn for details: /opt/local/var/macports/logs/_Users_magus_Ports_devel_yarn/yarn/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port yarn failed }}} Removing `distname`: {{{ ---> Computing dependencies for yarn ---> Fetching distfiles for yarn ---> Attempting to fetch yarn-0.18.0.tar.gz from https://distfiles.macports.org/yarn ---> Attempting to fetch yarn-0.18.0.tar.gz from https://github.com/yarnpkg/yarn/releases/download/v0.18.0 ---> Attempting to fetch yarn-0.18.0.tar.gz from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/yarn ---> Attempting to fetch yarn-0.18.0.tar.gz from http://lil.fr.distfiles.macports.org/yarn ... etc ... }}} I will take another stab at the problem later, but would appreciate any guidance/feedback you might have. Thanks! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 21:16:08 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 21:16:08 -0000 Subject: [MacPorts] #52814: scala2.12 @2.12.0: new port for scala 2.12 In-Reply-To: <046.e1987f1e22fff610473ebab53cbde69e@macports.org> References: <046.e1987f1e22fff610473ebab53cbde69e@macports.org> Message-ID: <061.975b02e7d8f2f900716819e12d7b12d4@macports.org> #52814: scala2.12 @2.12.0: new port for scala 2.12 ---------------------------------------+---------------------- Reporter: isomarcte | Owner: mkae Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: scala2.12 scala2.12-docs | ---------------------------------------+---------------------- Changes (by mkae): * owner: macports-tickets@… => mkae * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 21:16:18 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 21:16:18 -0000 Subject: [MacPorts] #52814: scala2.12 @2.12.0: new port for scala 2.12 In-Reply-To: <046.e1987f1e22fff610473ebab53cbde69e@macports.org> References: <046.e1987f1e22fff610473ebab53cbde69e@macports.org> Message-ID: <061.8d8661487867525afa45501ab6fa01a7@macports.org> #52814: scala2.12 @2.12.0: new port for scala 2.12 ---------------------------------------+---------------------- Reporter: isomarcte | Owner: mkae Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: scala2.12 scala2.12-docs | ---------------------------------------+---------------------- Changes (by mkae): * version: 2.3.4 => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 21:18:13 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 21:18:13 -0000 Subject: [MacPorts] #52814: scala2.12 @2.12.0: new port for scala 2.12 In-Reply-To: <046.e1987f1e22fff610473ebab53cbde69e@macports.org> References: <046.e1987f1e22fff610473ebab53cbde69e@macports.org> Message-ID: <061.fc870aea3218860f4d143ce02f8c431a@macports.org> #52814: scala2.12 @2.12.0: new port for scala 2.12 ---------------------------------------+-------------------- Reporter: isomarcte | Owner: mkae Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: scala2.12 scala2.12-docs | ---------------------------------------+-------------------- Changes (by Marko Käning ): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"83e5ce36d4aabb857970c25c5c75820431e09da4/macports-ports" 83e5ce36/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="83e5ce36d4aabb857970c25c5c75820431e09da4" new port for scala 2.12 Closes: https://trac.macports.org/ticket/52814 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 21:32:18 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 21:32:18 -0000 Subject: [MacPorts] #52827: yarn @0.16.1 In-Reply-To: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> References: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> Message-ID: <061.f27dc0f84aa1770a62f6fe25d496aeb2@macports.org> #52827: yarn @0.16.1 -------------------------+-------------------------------- Reporter: isomarcte | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: yarn | -------------------------+-------------------------------- Comment (by isomarcte): This ticket should be closed. The PR on github should be considered the authoritative source. https://github.com/macports/macports-ports/pull/48 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 21:32:32 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 21:32:32 -0000 Subject: [MacPorts] #31945: *-rtems-* ports are all out of date. In-Reply-To: <053.654934225253a598c0065334f00165b2@macports.org> References: <053.654934225253a598c0065334f00165b2@macports.org> Message-ID: <068.c92c30ee442c8c6549bda818f22b9ea4@macports.org> #31945: *-rtems-* ports are all out of date. -------------------------------------------------+------------------------- Reporter: chrisj@… | Owner: mojca Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-rtems-binutils arm-rtems-gcc | i386-rtems-binutils i386-rtems-gcc i960 | -rtems-binutils i960-rtems-gcc lm32-rtems- | binutils m68k-rtems-binutils m68k-rtems-gcc | mips-rtems-binutils mips-rtems-gcc powerpc- | rtems-binutils powerpc-rtems-gcc sh-rtems- | binutils sh-rtems-gcc sparc-rtems-binutils | sparc-rtems-gcc | -------------------------------------------------+------------------------- Changes (by mojca): * owner: macports-tickets@… => mojca * status: new => assigned * version: 2.0.3 => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 21:34:05 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 21:34:05 -0000 Subject: [MacPorts] #53048: libbiosig @1.8.0: update to 1.8.4 In-Reply-To: <047.ecd7a0974fd0e76c0c2936b16a849065@macports.org> References: <047.ecd7a0974fd0e76c0c2936b16a849065@macports.org> Message-ID: <062.87c57bb728a063fbbb7bb30db2acade7@macports.org> #53048: libbiosig @1.8.0: update to 1.8.4 -------------------------+--------------------------------- Reporter: neurodroid | Owner: ryandesign Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch maintainer Port: libbiosig | -------------------------+--------------------------------- Changes (by ryandesign): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"58edc8770da8e3cdda886ef340dd1cda61f5dde4/macports-ports" 58edc877/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="58edc8770da8e3cdda886ef340dd1cda61f5dde4" libbiosig: Update to 1.8.4 Closes: https://trac.macports.org/ticket/53048 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 21:34:16 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 21:34:16 -0000 Subject: [MacPorts] #53013: iTerm2 @3.0.5: update to 3.0.12 In-Reply-To: <041.b0a955ad9400c638b50ad70b61073a25@macports.org> References: <041.b0a955ad9400c638b50ad70b61073a25@macports.org> Message-ID: <056.56b7bdb5599cb2d8f9fe61023adaeec3@macports.org> #53013: iTerm2 @3.0.5: update to 3.0.12 ---------------------+---------------------- Reporter: l2dy | Owner: markemer Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: iTerm2 | ---------------------+---------------------- Comment (by markemer): I have the beginnings of this, I'll issue a pull request shortly. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 21:41:44 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 21:41:44 -0000 Subject: [MacPorts] #53022: opencv @3.1.0_6+python34: Portfile broken for variant +python34 In-Reply-To: <044.4cfc0421df7d7ecacd2795ceaf0f1af4@macports.org> References: <044.4cfc0421df7d7ecacd2795ceaf0f1af4@macports.org> Message-ID: <059.5c59bcc4b4035ce64441a325273f7e64@macports.org> #53022: opencv @3.1.0_6+python34: Portfile broken for variant +python34 ----------------------+-------------------- Reporter: detlevd | Owner: mkae Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: opencv | ----------------------+-------------------- Changes (by mkae): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"26d39ec43c7d5d5c87b9384dbb8fb5c804b9cf34/macports-ports" 26d39ec4/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="26d39ec43c7d5d5c87b9384dbb8fb5c804b9cf34" opencv: fix broken variant handling revbump to force rebuild due to wrongly spelled configure option Closes: https://trac.macports.org/ticket/53022 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 22:31:19 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 22:31:19 -0000 Subject: [MacPorts] #53013: iTerm2 @3.0.5: update to 3.0.12 In-Reply-To: <041.b0a955ad9400c638b50ad70b61073a25@macports.org> References: <041.b0a955ad9400c638b50ad70b61073a25@macports.org> Message-ID: <056.05d85c1f9cd09a0f419cd42052d188bf@macports.org> #53013: iTerm2 @3.0.5: update to 3.0.12 ---------------------+---------------------- Reporter: l2dy | Owner: markemer Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: iTerm2 | ---------------------+---------------------- Comment (by markemer): Pull request is up: https://github.com/macports/macports-ports/pull/93 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 22:51:01 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 22:51:01 -0000 Subject: [MacPorts] #53013: iTerm2 @3.0.5: update to 3.0.12 In-Reply-To: <041.b0a955ad9400c638b50ad70b61073a25@macports.org> References: <041.b0a955ad9400c638b50ad70b61073a25@macports.org> Message-ID: <056.702efdf0aaac78ab4a2120fd395f5826@macports.org> #53013: iTerm2 @3.0.5: update to 3.0.12 ---------------------+---------------------- Reporter: l2dy | Owner: markemer Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: iTerm2 | ---------------------+---------------------- Changes (by markemer): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"ee6b74283d650368fbbe767aa444b5ce0b380eb9/macports-ports" ee6b7428/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="ee6b74283d650368fbbe767aa444b5ce0b380eb9" Update of iTerm2 to 3.0.13 Closes https://trac.macports.org/ticket/53013 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 22:53:20 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 22:53:20 -0000 Subject: [MacPorts] #52048: iTerm2: update to 3.0.8 In-Reply-To: <047.1fc3b667129e583b3f80418ded5bdfb4@macports.org> References: <047.1fc3b667129e583b3f80418ded5bdfb4@macports.org> Message-ID: <062.a43ba66aa541a07a8a904851ac3f25b2@macports.org> #52048: iTerm2: update to 3.0.8 -------------------------+---------------------- Reporter: ryandesign | Owner: markemer Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: iTerm2 | -------------------------+---------------------- Comment (by markemer): We can close this, https://trac.macports.org/ticket/53013 makes it irrelevant. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 23:03:34 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 23:03:34 -0000 Subject: [MacPorts] #52869: OpenSceneGraph: fails to build due to changes in jpeg port In-Reply-To: <041.605a25c238eb52e5ff80ed0a94ecc86d@macports.org> References: <041.605a25c238eb52e5ff80ed0a94ecc86d@macports.org> Message-ID: <056.49d91c0272d36331c3a4c5a2eba254d1@macports.org> #52869: OpenSceneGraph: fails to build due to changes in jpeg port -------------------------------------------------+------------------------- Reporter: mkae | Owner: macports- | tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: OpenSceneGraph OpenSceneGraph- | devel | -------------------------------------------------+------------------------- Comment (by mkae): @dbevans, so, what could be done about this for OSG(-devel) then? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 23:09:53 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 23:09:53 -0000 Subject: [MacPorts] #52078: iTerm2 @3.0.5_0: pasting with the mouse between tabs does not work (anymore) In-Reply-To: <062.7038fee47b689585c64a9af194d6eab3@macports.org> References: <062.7038fee47b689585c64a9af194d6eab3@macports.org> Message-ID: <077.c6031cc7661388e7c002b252d501ee5d@macports.org> #52078: iTerm2 @3.0.5_0: pasting with the mouse between tabs does not work (anymore) --------------------------------+---------------------- Reporter: graziosi.angelo@… | Owner: markemer Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: iTerm2 | --------------------------------+---------------------- Comment (by markemer): We updated to 3.0.13 - see if things are better. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 23:59:35 2016 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2016 23:59:35 -0000 Subject: [MacPorts] #52210: libsdl2: make it build on 10.6 (against 10.6 SDK) In-Reply-To: <067.45256ed94fc9945c64bb2209be6b3a0a@macports.org> References: <067.45256ed94fc9945c64bb2209be6b3a0a@macports.org> Message-ID: <082.adac93f8fc60671684c3aba7fb226bd7@macports.org> #52210: libsdl2: make it build on 10.6 (against 10.6 SDK) -------------------------------------+------------------------- Reporter: kenneth.f.cunningham@… | Owner: jmroot Type: defect | Status: new Priority: Low | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: libsdl2 | -------------------------------------+------------------------- Comment (by kencu): Here is something interesting along these lines, perhaps. '''patch to compile SDL2 on Mac OS X 10.5 Leopard''' this version was written against SLD2 2.0.3 it appears. also, ''this project'' has a downloadable framework version of libsdl2 (between 2.0 and 2.1, says the info) is a fat binary with x86_64, i386, and PPC code that is apparently compatible back to 10.4. patches are also included in a directory. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 00:06:18 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 00:06:18 -0000 Subject: [MacPorts] #52869: OpenSceneGraph: fails to build due to changes in jpeg port In-Reply-To: <041.605a25c238eb52e5ff80ed0a94ecc86d@macports.org> References: <041.605a25c238eb52e5ff80ed0a94ecc86d@macports.org> Message-ID: <056.23d94998341528cb3fa0688376119380@macports.org> #52869: OpenSceneGraph: fails to build due to changes in jpeg port -------------------------------------------------+------------------------- Reporter: mkae | Owner: macports- | tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: OpenSceneGraph OpenSceneGraph- | devel | -------------------------------------------------+------------------------- Comment (by dbevans): Since the jpeg developers claim this sort of problem is not theirs, I suggest reporting this upstream to the OSG developers and see if they can come up with a fix. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 00:16:54 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 00:16:54 -0000 Subject: [MacPorts] #50845: libunwind: fails to find 'bits/c++config.h' on 10.5/PPC In-Reply-To: <042.dc439143bad4305d12829f44ffd3509f@macports.org> References: <042.dc439143bad4305d12829f44ffd3509f@macports.org> Message-ID: <057.9c575c342229eb1736cbdc48867a6000@macports.org> #50845: libunwind: fails to find 'bits/c++config.h' on 10.5/PPC ------------------------+---------------------- Reporter: mojca | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: leopard Port: libunwind | ------------------------+---------------------- Comment (by kencu): It's still fairly mind-bending, isn't it? You seemed to be able to build the libraries universally with both ppc and intel code using clang-3.7. I'm just trying to see if I can recreate that process now on an Intel Leopard machine I have here. With clang-3.4 on Leopard PPC or Leopard Intel I had the 'no universal' issue above... I wonder if it might be possible to build clang-3.7 with a PPC slice, for Leopard, on Intel. If so, given how hard this is to build and how long it takes to get set up, perhaps I might make that and the four libraries available somewhere so people could bootstrap that far. That would still leave us with the exception bugs, but it would be closer to something useful...maybe... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 04:40:27 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 04:40:27 -0000 Subject: [MacPorts] #53050: mpv 0.22 update Message-ID: <043.ede0b5c165466cc5d52fb032c6a990ef@macports.org> #53050: mpv 0.22 update --------------------+------------------- Reporter: iMiKED | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: --------------------+------------------- Please, update mpv to 0.21 version -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 04:41:09 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 04:41:09 -0000 Subject: [MacPorts] #53050: mpv 0.22 update In-Reply-To: <043.ede0b5c165466cc5d52fb032c6a990ef@macports.org> References: <043.ede0b5c165466cc5d52fb032c6a990ef@macports.org> Message-ID: <058.24d572872f7d9aaca09d37b10690118e@macports.org> #53050: mpv 0.22 update ---------------------+------------------- Reporter: iMiKED | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: | ---------------------+------------------- Comment (by iMiKED): Please, update mpv to 0.22 version -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 07:33:02 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 07:33:02 -0000 Subject: [MacPorts] #52845: mpv: update to 0.22 (was: mpv 0.21 update) In-Reply-To: <043.e673edb81f111939a6207eb0205e5927@macports.org> References: <043.e673edb81f111939a6207eb0205e5927@macports.org> Message-ID: <058.5a9a7a1da0e9002d2c180ebe7a3f628b@macports.org> #52845: mpv: update to 0.22 ---------------------+---------------------- Reporter: iMiKED | Owner: Ionic Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: mpv | ---------------------+---------------------- Changes (by Ionic): * version: 2.3.4 => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 07:34:07 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 07:34:07 -0000 Subject: [MacPorts] #53050: mpv 0.22 update In-Reply-To: <043.ede0b5c165466cc5d52fb032c6a990ef@macports.org> References: <043.ede0b5c165466cc5d52fb032c6a990ef@macports.org> Message-ID: <058.85102533df5561a02914e49b369ea497@macports.org> #53050: mpv 0.22 update ------------------------+-------------------- Reporter: iMiKED | Owner: Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: duplicate | Keywords: Port: mpv | ------------------------+-------------------- Changes (by Ionic): * status: new => closed * version: 2.3.5 => * resolution: => duplicate * port: => mpv Comment: Duplicate of #52845, closing up. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 07:34:50 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 07:34:50 -0000 Subject: [MacPorts] #52845: mpv: update to 0.22 In-Reply-To: <043.e673edb81f111939a6207eb0205e5927@macports.org> References: <043.e673edb81f111939a6207eb0205e5927@macports.org> Message-ID: <058.13f55a5b39fdb6401033aac15eb31551@macports.org> #52845: mpv: update to 0.22 ---------------------+---------------------- Reporter: iMiKED | Owner: Ionic Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: mpv | ---------------------+---------------------- Comment (by Ionic): I'll start updating my main system so that I can work on it now... afterwards my 10.6 VM and then we'll see. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 08:03:36 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 08:03:36 -0000 Subject: [MacPorts] #53051: port py-virtualenv add default selection note Message-ID: <043.5d1ff70fe0b31a70b1406cced7cd9421@macports.org> #53051: port py-virtualenv add default selection note -------------------------+--------------------------- Reporter: anddam | Owner: larryv Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: py-virtualenv -------------------------+--------------------------- Add a default selection note to py-virtualenv port. If there's no strict need to avoid it, I suggest adding openmaintainer. https://github.com/macports/macports-ports/pull/94 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 09:40:26 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 09:40:26 -0000 Subject: [MacPorts] #52210: libsdl2: make it build on 10.6 (against 10.6 SDK) In-Reply-To: <067.45256ed94fc9945c64bb2209be6b3a0a@macports.org> References: <067.45256ed94fc9945c64bb2209be6b3a0a@macports.org> Message-ID: <082.39d1e927e4f54c68d502f4a385d60850@macports.org> #52210: libsdl2: make it build on 10.6 (against 10.6 SDK) -------------------------------------+------------------------- Reporter: kenneth.f.cunningham@… | Owner: jmroot Type: defect | Status: new Priority: Low | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: libsdl2 | -------------------------------------+------------------------- Comment (by mojca): I almost forgot about this ticket. I didn't check the patches for `include/SDL_config.h` yet, but the rest seems like completely reasonable patching. The patch uses {{{ #!c #if MAC_OS_X_VERSION_MIN_REQUIRED }}} while Jeremy suggested {{{ #!c #if __MAC_OS_X_VERSION_MAX_ALLOWED }}} I always mix up the difference between the two (the idea is mostly the same, just different use case) and I guess Jeremy knows better. Thanks a lot for the good news. It probably makes sense to test that patch (and perhaps look at my observations above), first on 10.6, then on 10.5, and submit it upstream. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 09:51:59 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 09:51:59 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.59625d410743710cb425554a1a45c4a2@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"2a2a8ad9b30e41ace06c7558ecce28c6fdfdf21f/macports-ports" 2a2a8ad9/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="2a2a8ad9b30e41ace06c7558ecce28c6fdfdf21f" crossbinutils-1.0: move libiberty header Fix location of ${prefix}/include/libiberty/*.h that caused conflicts in *-binutils ports. See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 09:52:00 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 09:52:00 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.7eca9a5e2b3d70595e89af4558d5ae85@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"3ad4b0960ad55da00d8cbd654538ec94706c386d/macports-ports" 3ad4b096/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="3ad4b0960ad55da00d8cbd654538ec94706c386d" arm-aout-binutils: upgrade to 2.27 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 09:52:00 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 09:52:00 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.6a392bb8690ecac79316fdf012f07154@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"3ad4b0960ad55da00d8cbd654538ec94706c386d/macports-ports" 3ad4b096/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="3ad4b0960ad55da00d8cbd654538ec94706c386d" arm-aout-binutils: upgrade to 2.27 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 09:52:00 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 09:52:00 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.4c0701027bbd73f975b8b852f0569431@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"7e0ebaf05f602af4cfb0337e3013a2537a7f5059/macports-ports" 7e0ebaf0/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="7e0ebaf05f602af4cfb0337e3013a2537a7f5059" avr-binutils: remove libiberty patch, revbump * Remove $Id$ line. * Patch for libiberty is no longer needed, but we need a revbump. See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 09:52:00 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 09:52:00 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.5aff73c1e90f0ae8a39eb2d8789fbf32@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"1edf79dcd8ac0cb4371abced98bde1e3e3f99062/macports-ports" 1edf79dc/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="1edf79dcd8ac0cb4371abced98bde1e3e3f99062" spu-binutils: upgrade to 2.27 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 09:52:01 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 09:52:01 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.1fc0f3288e671e47d664bcbb73cdd315@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"1edf79dcd8ac0cb4371abced98bde1e3e3f99062/macports-ports" 1edf79dc/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="1edf79dcd8ac0cb4371abced98bde1e3e3f99062" spu-binutils: upgrade to 2.27 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 09:52:01 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 09:52:01 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.4e110b217fdbaeb1c180955e0a4d6c6d@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"0cd1ac10a71b2f841e728cbea17442f793031e27/macports-ports" 0cd1ac1/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="0cd1ac10a71b2f841e728cbea17442f793031e27" ppc-linux-binutils: upgrade to 2.27 Patches no longer needed (included upstream). See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 09:52:01 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 09:52:01 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.e439351ed066678e3de943207b982cbc@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"0cd1ac10a71b2f841e728cbea17442f793031e27/macports-ports" 0cd1ac1/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="0cd1ac10a71b2f841e728cbea17442f793031e27" ppc-linux-binutils: upgrade to 2.27 Patches no longer needed (included upstream). See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 09:52:01 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 09:52:01 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.08eca0571382d871b3808748d5df39a2@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"0eb3986fc7a6218b1c2d05899365abc22d66af4d/macports-ports" 0eb3986/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="0eb3986fc7a6218b1c2d05899365abc22d66af4d" arm-elf-binutils: upgrade to 2.27 License is part of the PortGroup and not needed here. See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 09:52:01 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 09:52:01 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.f3b51af3787cafe1f2e42944b8222f74@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"0eb3986fc7a6218b1c2d05899365abc22d66af4d/macports-ports" 0eb3986/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="0eb3986fc7a6218b1c2d05899365abc22d66af4d" arm-elf-binutils: upgrade to 2.27 License is part of the PortGroup and not needed here. See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 09:52:02 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 09:52:02 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.ef5ca1e31ca28f5c0c3eb42b93e2faff@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"ccc83b50b7d929f9e039525cbcf5a74064983c46/macports-ports" ccc83b5/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="ccc83b50b7d929f9e039525cbcf5a74064983c46" arm-none-eabi-binutils: upgrade to 2.27 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 09:52:02 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 09:52:02 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.d786767aa044d66b970cd52c389982be@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"ccc83b50b7d929f9e039525cbcf5a74064983c46/macports-ports" ccc83b5/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="ccc83b50b7d929f9e039525cbcf5a74064983c46" arm-none-eabi-binutils: upgrade to 2.27 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 09:52:02 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 09:52:02 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.62313919000b86fe87f4c689a8a98897@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"9451379b7b431ac5f59a4b940f8c30a4ceca4e63/macports-ports" 9451379b/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="9451379b7b431ac5f59a4b940f8c30a4ceca4e63" x86_64-elf-binutils: upgrade to 2.27 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 09:52:02 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 09:52:02 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.220c6792b09f8d1c0a6c2ed41bfd301a@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"9451379b7b431ac5f59a4b940f8c30a4ceca4e63/macports-ports" 9451379b/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="9451379b7b431ac5f59a4b940f8c30a4ceca4e63" x86_64-elf-binutils: upgrade to 2.27 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 09:52:03 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 09:52:03 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.fcb525f519b6c6b9f3667a2237394453@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"9a5ee5f941c294f1da9b21f6290fbc87c1f7f4b1/macports-ports" 9a5ee5f9/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="9a5ee5f941c294f1da9b21f6290fbc87c1f7f4b1" i386-elf-binutils: upgrade to 2.27 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 09:52:03 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 09:52:03 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.ec0628bb239582a8605c68088ef6ad81@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"9a5ee5f941c294f1da9b21f6290fbc87c1f7f4b1/macports-ports" 9a5ee5f9/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="9a5ee5f941c294f1da9b21f6290fbc87c1f7f4b1" i386-elf-binutils: upgrade to 2.27 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 09:52:03 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 09:52:03 -0000 Subject: [MacPorts] #40174: MinGW-w64: add win64 cross-compiler In-Reply-To: <059.6f05edcab273d7fe0bf88ffe97aec928@macports.org> References: <059.6f05edcab273d7fe0bf88ffe97aec928@macports.org> Message-ID: <074.12e9704fff301cc56bc1be6987512a7d@macports.org> #40174: MinGW-w64: add win64 cross-compiler -------------------------------------------------+------------------------- Reporter: sam.halliday@… | Owner: mojca Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: mingw-w64 i686-w64-mingw32-gcc | x86_64-w64-mingw32-gcc | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"07d0ce548162f49ee846ac274dbcbd970fd7e639/macports-ports" 07d0ce54/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="07d0ce548162f49ee846ac274dbcbd970fd7e639" {i686|x86_64}-w64-mingw32-binutils: new ports Closes: https://trac.macports.org/ticket/13606 See: https://trac.macports.org/ticket/40174 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 09:52:03 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 09:52:03 -0000 Subject: [MacPorts] #13606: New cross/x86_64-pc-mingw32-binutils port In-Reply-To: <064.be87212c54e36dd7f12a7c084694b2c3@macports.org> References: <064.be87212c54e36dd7f12a7c084694b2c3@macports.org> Message-ID: <079.0d627b561d8628eb40716ff1db902c8e@macports.org> #13606: New cross/x86_64-pc-mingw32-binutils port -------------------------------------+------------------------------------- Reporter: jljusten macports@… | Owner: mojca Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: cross mingw x86_64 x64 Port: i386-mingw32-binutils, | binutils mingw-w64 | -------------------------------------+------------------------------------- Changes (by mojca): * status: new => closed * resolution: => fixed Comment: In [changeset:"07d0ce548162f49ee846ac274dbcbd970fd7e639/macports-ports" 07d0ce54/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="07d0ce548162f49ee846ac274dbcbd970fd7e639" {i686|x86_64}-w64-mingw32-binutils: new ports Closes: https://trac.macports.org/ticket/13606 See: https://trac.macports.org/ticket/40174 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 11:39:41 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 11:39:41 -0000 Subject: [MacPorts] #46507: QtCurve update with support for Qt5 In-Reply-To: <041.a4bd6944c8c9acbfeb8df11e1b349a18@macports.org> References: <041.a4bd6944c8c9acbfeb8df11e1b349a18@macports.org> Message-ID: <056.cac5f07bf01c1553d3ce6d452a228a8e@macports.org> #46507: QtCurve update with support for Qt5 --------------------------+--------------------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch maintainer Port: QtCurve | --------------------------+--------------------------------- Changes (by mkae): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"fcb150809ae811167b97bce5a002729a9fafc80c/macports-ports" fcb15080/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="fcb150809ae811167b97bce5a002729a9fafc80c" qtcurve: New subport qtcurve-extra + patch for KCM Upstreamed patch to prevent the killTimer warning when changing styles via the styles KCM. Fixed the GTk2 theme upstream. Ship Mac-appropriate kdeglobals file for this theme. Code cleanup & introduction of a libcxx variant for 10.6 (and earlier). qtcurve{,-qt5,-gtk2}: revive function that scans for system-wide config file. qtcurve-extra: install a system-wide config file (stylerc) that provides a Mac-like look. Deactivate config pages that don't make sense on OS X and/or don't work properly anywhere. qtcurve-qt5: Adapt to the new cmake.install_rpath syntax. qtcurve : Add a setting to use a non-native ("in-window") menubar with select applications; incorporated upstream. qtcurve(-qt5): Implements qt4 & qt5 UIs and previews for the onlyTicksInMenu feature which was incorporated upstream. Another upstreamed fix that prevents the well-known menu-rendering glitch under Qt4 (happened also with qtcurve when popup menus were rounded). D-Bus patching. The Qt5 subport is "KF5-ready" but will install as +qtonly by default until the required KF5 dependencies are available in MacPorts. Closes: https://trac.macports.org/ticket/46507 Closes: #7 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 14:04:17 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 14:04:17 -0000 Subject: [MacPorts] #53052: Homebank @5.1.2 updating a port to a newer upstream version Message-ID: <044.8ba0eb9389d23fa485124fe651dee17b@macports.org> #53052: Homebank @5.1.2 updating a port to a newer upstream version ---------------------------------+---------------------- Reporter: sibador | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch maintainer | Port: homebank ---------------------------------+---------------------- Hello I updated from version 5.1.1 to 5.1.2 Thank you -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 14:04:31 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 14:04:31 -0000 Subject: [MacPorts] #53052: Homebank @5.1.2 updating a port to a newer upstream version In-Reply-To: <044.8ba0eb9389d23fa485124fe651dee17b@macports.org> References: <044.8ba0eb9389d23fa485124fe651dee17b@macports.org> Message-ID: <059.68aed6d9c6578af2d24572d989614632@macports.org> #53052: Homebank @5.1.2 updating a port to a newer upstream version -----------------------+--------------------------------- Reporter: sibador | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: homebank | -----------------------+--------------------------------- Changes (by sibador): * Attachment "homebank.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 14:51:00 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 14:51:00 -0000 Subject: [MacPorts] #53049: gqrx dependency missing In-Reply-To: <047.a52d7adc49f837cb619e48c8ee89512f@macports.org> References: <047.a52d7adc49f837cb619e48c8ee89512f@macports.org> Message-ID: <062.30f2e317abf9102a5e800fafed57b606@macports.org> #53049: gqrx dependency missing -------------------------+----------------------- Reporter: umtauscher | Owner: michaelld Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: worksforme | Keywords: Port: gqrx | -------------------------+----------------------- Changes (by michaelld): * status: assigned => closed * resolution: => worksforme Comment: Closing ticket as "works for me", per mp-dev email https://lists.macports.org/pipermail/macports- dev/2016-December/034898.html . -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 15:34:34 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 15:34:34 -0000 Subject: [MacPorts] #53042: gnuradio @3.7.10.1_1 install fails on Snow Leopard due to undeclared long long math prototypes - and fix In-Reply-To: <042.83f707075941558260948d2d3f3e7ca4@macports.org> References: <042.83f707075941558260948d2d3f3e7ca4@macports.org> Message-ID: <057.2131abe1ddbb24f0cfca779a88b38c18@macports.org> #53042: gnuradio @3.7.10.1_1 install fails on Snow Leopard due to undeclared long long math prototypes - and fix -----------------------+------------------------- Reporter: kencu | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: gnuradio | -----------------------+------------------------- Comment (by michaelld): In [changeset:"94b9570ed7dcfd3f48a0077e4dcda3cfa7086781/macports-ports" 94b9570e/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="94b9570ed7dcfd3f48a0077e4dcda3cfa7086781" gnuradio: update devel to 0ec18440 (20161210); remove $id$ line; add patch to fix building on 10.6 Snow Leopard due to missing function prototype, which addresses ticket https://trac.macports.org/ticket/53042 . }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 15:35:54 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 15:35:54 -0000 Subject: [MacPorts] #53042: gnuradio @3.7.10.1_1 install fails on Snow Leopard due to undeclared long long math prototypes - and fix In-Reply-To: <042.83f707075941558260948d2d3f3e7ca4@macports.org> References: <042.83f707075941558260948d2d3f3e7ca4@macports.org> Message-ID: <057.b9a638920694da28b9d62f65949d3085@macports.org> #53042: gnuradio @3.7.10.1_1 install fails on Snow Leopard due to undeclared long long math prototypes - and fix -----------------------+------------------------- Reporter: kencu | Owner: michaelld Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: snowleopard Port: gnuradio | -----------------------+------------------------- Changes (by michaelld): * status: assigned => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 15:37:15 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 15:37:15 -0000 Subject: [MacPorts] #53042: gnuradio @3.7.10.1_1 install fails on Snow Leopard due to undeclared long long math prototypes - and fix In-Reply-To: <042.83f707075941558260948d2d3f3e7ca4@macports.org> References: <042.83f707075941558260948d2d3f3e7ca4@macports.org> Message-ID: <057.0a89e5e9955d6ac5c3934feca3747981@macports.org> #53042: gnuradio @3.7.10.1_1 install fails on Snow Leopard due to undeclared long long math prototypes - and fix -----------------------+------------------------- Reporter: kencu | Owner: michaelld Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: snowleopard Port: gnuradio | -----------------------+------------------------- Comment (by michaelld): Please test & verify that this fix works. It's the same as yours just renamed; hopefully I got the new patch name correct :) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 15:42:19 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 15:42:19 -0000 Subject: [MacPorts] #52048: iTerm2: update to 3.0.8 In-Reply-To: <047.1fc3b667129e583b3f80418ded5bdfb4@macports.org> References: <047.1fc3b667129e583b3f80418ded5bdfb4@macports.org> Message-ID: <062.cd35e64baa825ae71a48b05809f0e869@macports.org> #52048: iTerm2: update to 3.0.8 -------------------------+---------------------- Reporter: ryandesign | Owner: markemer Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: duplicate | Keywords: Port: iTerm2 | -------------------------+---------------------- Changes (by mf2k): * status: new => closed * resolution: => duplicate Comment: #53013 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 16:09:44 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 16:09:44 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.b32713a01d77ccbdae3e9d3e06f23300@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Changes (by mojca): * status: new => closed * resolution: => fixed Old description: > I just noticed that when using the crossbinutils PortGroup, one ends up > with: > {{{ > /opt/local/${target}/host/lib/libiberty.a > /opt/local/include/libiberty/*.h > }}} > The first one is not problematic, but files under `$prefix/include` are > because any given binutils port would install that. > > I found a related commit: > * https://github.com/macports/macports- > ports/commit/bcdf26e5b403a4291f3c241f19e33eb86d7ca538 > > Judging from the fact that bfd installs > {{{ > /opt/local/${host}/bin/ld.bfd > /opt/local/${host}/host/include/*.h > /opt/local/${host}/host/lib/libbfd.a > /opt/local/${host}/host/lib/libbfd.la > }}} > I guess that some recent update of binutils broke the `reinplace` patch. > > This requires: > * a patch in the portgroup to fix the problem > * a revbump (or ideally upgrade) of all affected `*-binutils` ports > * probably a bit more testing with a couple of different binutils > versions > > Maybe the older versions are not even affected and a fix would break > older ports, I'm not sure. > > Existing binutils ports: > > Using the portgroup: > || avr-binutils || @2.27 || g5pw || > || msp430-binutils || @2.21.1a-20120406 || g5pw || > || msp430-binutils-devel || 2.22 || g5pw || > || arm-elf-binutils || @2.25 || > gmail:stuartwesterman || > || arm-none-eabi-binutils || @2.23.1 || > gmail:stuartwesterman || > || i386-elf-binutils || @2.23.1 || gmail:jinksys > || > || x86_64-elf-binutils || @2.23.1 || > gmail:nategriswold || > || ppc-linux-binutils || @2.25 || > || arm-aout-binutils || @2.22 || > || spu-binutils || @2.20.51.0.5 || > > Others: > || arm-none-linux-gnueabi-binutils || @2005q3-2 || > || arm-rtems-binutils || @2.18 || > || i386-mingw32-binutils || @2.21-3 || > || i386-rtems-binutils || @2.18 || > || i960-rtems-binutils || @2.16.1 || > || lm32-rtems-binutils || @2.21.1 || > || m68k-elf-binutils || @2.17 || > || m68k-rtems-binutils || @2.18 || > || mips-elf-binutils || @2.17 || > || mips-rtems-binutils || @2.18 || > || mipsel-linux-binutils || @2.16.1 || > || powerpc-rtems-binutils || @2.18 || > || sh-rtems-binutils || @2.18 || > || sparc-rtems-binutils || @2.18 || > > See also #51935. New description: I just noticed that when using the crossbinutils PortGroup, one ends up with: {{{ /opt/local/${target}/host/lib/libiberty.a /opt/local/include/libiberty/*.h }}} The first one is not problematic, but files under `$prefix/include` are because any given binutils port would install that. I found a related commit: * https://github.com/macports/macports- ports/commit/bcdf26e5b403a4291f3c241f19e33eb86d7ca538 Judging from the fact that bfd installs {{{ /opt/local/${host}/bin/ld.bfd /opt/local/${host}/host/include/*.h /opt/local/${host}/host/lib/libbfd.a /opt/local/${host}/host/lib/libbfd.la }}} I guess that some recent update of binutils broke the `reinplace` patch. This requires: * a patch in the portgroup to fix the problem * a revbump (or ideally upgrade) of all affected `*-binutils` ports * probably a bit more testing with a couple of different binutils versions Maybe the older versions are not even affected and a fix would break older ports, I'm not sure. Existing binutils ports: Using the portgroup: || avr-binutils || @2.27 || g5pw || || msp430-binutils || @2.21.1a-20120406 || g5pw || || msp430-binutils-devel || @2.22 || g5pw || || arm-elf-binutils || @2.25 || gmail:stuartwesterman || || arm-none-eabi-binutils || @2.23.1 || gmail:stuartwesterman || || i386-elf-binutils || @2.23.1 || gmail:jinksys || || x86_64-elf-binutils || @2.23.1 || gmail:nategriswold || || ppc-linux-binutils || @2.25 || || arm-aout-binutils || @2.22 || || spu-binutils || @2.20.51.0.5 || Others: || arm-none-linux-gnueabi-binutils || @2005q3-2 || || arm-rtems-binutils || @2.18 || || i386-mingw32-binutils || @2.21-3 || || i386-rtems-binutils || @2.18 || || i960-rtems-binutils || @2.16.1 || || lm32-rtems-binutils || @2.21.1 || || m68k-elf-binutils || @2.17 || || m68k-rtems-binutils || @2.18 || || mips-elf-binutils || @2.17 || || mips-rtems-binutils || @2.18 || || mipsel-linux-binutils || @2.16.1 || || powerpc-rtems-binutils || @2.18 || || sh-rtems-binutils || @2.18 || || sparc-rtems-binutils || @2.18 || See also #51935. -- Comment: I upgraded all ports that use the crosstools portgroup except for `msp430-binutils[-devel]` and those two apparently use an old enough version of binutils, so that the archives on http://packages.macports.org/ were not affected. Closing this ticket, still tracking updates on #51935. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 16:23:16 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 16:23:16 -0000 Subject: [MacPorts] #53052: Homebank @5.1.2 updating a port to a newer upstream version In-Reply-To: <044.8ba0eb9389d23fa485124fe651dee17b@macports.org> References: <044.8ba0eb9389d23fa485124fe651dee17b@macports.org> Message-ID: <059.4fb6d9b45cdcd6a5a2e387b4a0e2a641@macports.org> #53052: Homebank @5.1.2 updating a port to a newer upstream version -----------------------+--------------------------------- Reporter: sibador | Owner: ryandesign Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: homebank | -----------------------+--------------------------------- Changes (by ryandesign): * status: new => accepted * owner: => ryandesign Comment: Thanks. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 16:36:02 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 16:36:02 -0000 Subject: [MacPorts] #53052: Homebank @5.1.2 updating a port to a newer upstream version In-Reply-To: <044.8ba0eb9389d23fa485124fe651dee17b@macports.org> References: <044.8ba0eb9389d23fa485124fe651dee17b@macports.org> Message-ID: <059.987e6f01435aead1d4a0debc3b13c187@macports.org> #53052: Homebank @5.1.2 updating a port to a newer upstream version -----------------------+--------------------------------- Reporter: sibador | Owner: ryandesign Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch maintainer Port: homebank | -----------------------+--------------------------------- Changes (by ryandesign): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"529d656f5ac5be1fe964d2a8c2e3947c61d54232/macports-ports" 529d656/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="529d656f5ac5be1fe964d2a8c2e3947c61d54232" homebank: Update to 5.1.2 Closes: https://trac.macports.org/ticket/53052 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 16:51:45 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 16:51:45 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.67eb55c058c1440dea1d06d5752a63dc@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Description changed by mojca: Old description: > It would be nice to upgrade the binutils ports. > > ||= name =||= old version =||= maint. > =||= commit =|| > || arm-aout-binutils || 2.22 || > || r || > || arm-elf-binutils || 2.25 || > stuartwesterman-gm || r || > || arm-none-eabi-binutils || 2.23.1 || > stuartwesterman-gm || r || > || arm-none-linux-gnueabi-binutils || 2005q3-2 || > stuartwesterman-gm || r || > || arm-rtems-binutils || 2.18 || > || r || > || ~~avr-binutils~~ || ~~2.25~~ || > ~~g5pw~~ || r151540 || > || ~~binutils~~ || ~~2.26.1~~ || > || r150799, [changeset:"82608d82dbbc7a45e67eb5eaa0bb981c9350a438 > /macports-ports" 82608d82] || > || i386-elf-binutils || 2.23.1 || jinksys-gm > || r || > || i386-mingw32-binutils || 2.21-3 || > || r || > || i386-mingw32-binutils || 2.21-3 || > || r || > || i386-rtems-binutils || 2.18 || > || r || > || i960-rtems-binutils || 2.16.1 || > || r || > || lm32-rtems-binutils || 2.21.1 || yann > .sionneau-gm || r || > || m68k-elf-binutils || 2.17 || > || r || > || m68k-rtems-binutils || 2.18 || > || r || > || mips-elf-binutils || 2.17 || > || r || > || mips-rtems-binutils || 2.18 || > || r || > || mipsel-linux-binutils || 2.16.1 || > || r || > || msp430-binutils || 2.21.1a-20120406 || g5pw > || r || > || msp430-binutils-devel || 2.22-20120911 || g5pw > || r || > || powerpc-rtems-binutils || 2.18 || > || r || > || ppc-linux-binutils || 2.25 || > || r || > || sh-rtems-binutils || 2.18 || > || r || > || sparc-rtems-binutils || 2.18 || > || r || > || spu-binutils || 2.20.51.0.5 || > || r || > || x86_64-elf-binutils || 2.23.1 || > || r || New description: It would be nice to upgrade the binutils ports and to switch to the `crossbinutils` PortGroup in ports where this is not yet the case. ||= name =||= old version =||= maint. =||= commit =|| ||= (using crossbinutils) =|| || || || || ~~binutils~~ || ~~2.26.1~~ || || r150799, [changeset:"82608d82dbbc7a45e67eb5eaa0bb981c9350a438/macports- ports" 82608d82] || || ~~avr-binutils~~ || ~~2.25~~ || ~~g5pw~~ || r151540 || || msp430-binutils || 2.21.1a-20120406 || g5pw || || || msp430-binutils-devel || 2.22-20120911 || g5pw || || || ~~arm-elf-binutils~~ || ~~2.25~~ || stuartwesterman-gm || [changeset:"0eb3986fc7a6218b1c2d05899365abc22d66af4d /macports-ports" 0eb3986f] || || ~~arm-none-eabi-binutils~~ || ~~2.23.1~~ || stuartwesterman-gm || [changeset:"ccc83b50b7d929f9e039525cbcf5a74064983c46 /macports-ports" ccc83b50] || || ~~i386-elf-binutils~~ || ~~2.23.1~~ || jinksys-gm || [changeset:"9a5ee5f941c294f1da9b21f6290fbc87c1f7f4b1/macports-ports" 9a5ee5f9] || || ~~x86_64-elf-binutils~~ || ~~2.23.1~~ || nategriswold- gm || [changeset:"9451379b7b431ac5f59a4b940f8c30a4ceca4e63/macports- ports" 9451379b] || || ~~ppc-linux-binutils~~ || ~~2.25~~ || || [changeset:"0cd1ac10a71b2f841e728cbea17442f793031e27/macports-ports" 0cd1ac10] || || ~~arm-aout-binutils~~ || ~~2.22~~ || || [changeset:"3ad4b0960ad55da00d8cbd654538ec94706c386d/macports-ports" 3ad4b096] || || ~~spu-binutils~~ || ~~2.20.51.0.5~~ || || [changeset:"1edf79dcd8ac0cb4371abced98bde1e3e3f99062/macports-ports" 1edf79dc] || ||= (not using crossbinutils) =|| || || || || arm-none-linux-gnueabi-binutils || 2005q3-2 || stuartwesterman-gm || || || m68k-elf-binutils || 2.17 || || || || mips-elf-binutils || 2.17 || || || || mipsel-linux-binutils || 2.16.1 || || || ||= (rtems, see #31945) =|| || || || || arm-rtems-binutils || 2.18 || || || || i386-rtems-binutils || 2.18 || || || || lm32-rtems-binutils || 2.21.1 || yann.sionneau- gm || || || m68k-rtems-binutils || 2.18 || || || || mips-rtems-binutils || 2.18 || || || || powerpc-rtems-binutils || 2.18 || || || || sh-rtems-binutils || 2.18 || || || || sparc-rtems-binutils || 2.18 || || || ||= (obsolete?) =|| || || || || i386-mingw32-binutils || 2.21-3 || || || || i386-mingw32-binutils || 2.21-3 || || || ||= (removed) =|| || || || || ~~i960-rtems-binutils~~ || ~~2.16.1~~ || || [changeset:"c9a5124265ec67a9885a1e4a4d24b24fcee43251/macports-ports" c9a51242] || -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 17:14:32 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 17:14:32 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.2400e909900637b081d05bbec1e779ef@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"ba77cc17739a8b29f028601570fe19bc797383e7/macports-ports" ba77cc17/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="ba77cc17739a8b29f028601570fe19bc797383e7" mips-elf-binutils: upgrade to 2.27, use portgroup * Upgrade to binutils 2.27 * Add the crossbinutils portgroup * Patch is no longer needed See: https://trac.macports.org/ticket/51935 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 17:26:08 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 17:26:08 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.012dfc6067db67e97749178204eb5009@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"6348190358f3e179150444e2c3447ccc5996e05a/macports-ports" 63481903/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="6348190358f3e179150444e2c3447ccc5996e05a" m68k-elf-binutils: upgrade to 2.27, use portgroup * Upgrade to binutils 2.27 * Add the crossbinutils portgroup * Patch is no longer needed See: https://trac.macports.org/ticket/51935 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 17:45:10 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 17:45:10 -0000 Subject: [MacPorts] #53040: py27-wxpython-3.0 @3.0.2.0 fatal error: 'type_traits' file not found on systems upgraded to libc++ In-Reply-To: <042.60b960fe5a4bb70586997df006b20806@macports.org> References: <042.60b960fe5a4bb70586997df006b20806@macports.org> Message-ID: <057.2d08d4b21cfee97330b9c75981f938ce@macports.org> #53040: py27-wxpython-3.0 @3.0.2.0 fatal error: 'type_traits' file not found on systems upgraded to libc++ ------------------------------+---------------------------- Reporter: kencu | Owner: jyrkiwahlstedt Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-wxpython-3.0 | ------------------------------+---------------------------- Comment (by kencu): OK. I foresee a block like the one you have in wxWidgets making it into this port as well, ultimately. For my education, can you tell me how it is that adding "-stdlib=libc++" to the build command allows the compiler to find the "type_traits" file? I know it works, but I don't understand why it works, exactly. -- K -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 17:58:53 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 17:58:53 -0000 Subject: [MacPorts] #53042: gnuradio @3.7.10.1_1 install fails on Snow Leopard due to undeclared long long math prototypes - and fix In-Reply-To: <042.83f707075941558260948d2d3f3e7ca4@macports.org> References: <042.83f707075941558260948d2d3f3e7ca4@macports.org> Message-ID: <057.be891ed5f45b5c5e8ded3e601ceb546f@macports.org> #53042: gnuradio @3.7.10.1_1 install fails on Snow Leopard due to undeclared long long math prototypes - and fix -----------------------+------------------------- Reporter: kencu | Owner: michaelld Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: snowleopard Port: gnuradio | -----------------------+------------------------- Comment (by kencu): looks good {{{ gnuradio-devel @20161210_0+docs+grc+jack+portaudio+qtgui+sdl+swig+uhd+wavelet+wxgui (active) platform='darwin 10' archs='x86_64' }}} and this {{{ /opt/local/share/gnuradio/examples/qt-gui/display_qt }}} brings up a nice window with real-looking data displayed. To get it to build, py27-wxpython-3.0 also has to build (with the default options, at least). With libc++ enabled on 10.6, that currently requires a fix such as [ticket:53040] which looks like it is going to be fixed in the main repo shortly. Thanks. K. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 18:37:11 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 18:37:11 -0000 Subject: [MacPorts] #53042: gnuradio @3.7.10.1_1 install fails on Snow Leopard due to undeclared long long math prototypes - and fix In-Reply-To: <042.83f707075941558260948d2d3f3e7ca4@macports.org> References: <042.83f707075941558260948d2d3f3e7ca4@macports.org> Message-ID: <057.cc1d2974eb9928beb20b33e1c53bb823@macports.org> #53042: gnuradio @3.7.10.1_1 install fails on Snow Leopard due to undeclared long long math prototypes - and fix -----------------------+------------------------- Reporter: kencu | Owner: michaelld Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: snowleopard Port: gnuradio | -----------------------+------------------------- Comment (by michaelld): Great! Thx for reporting back. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 18:38:44 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 18:38:44 -0000 Subject: [MacPorts] #50492: vte @0.43.2_0: build failure due to libstdc++ compatibility issue on 10.8 and earlier In-Reply-To: <044.12f5c0cae806f5ae17dd64326668b762@macports.org> References: <044.12f5c0cae806f5ae17dd64326668b762@macports.org> Message-ID: <059.ca1d48baaeb649e0d63159ff4a9ba4ab@macports.org> #50492: vte @0.43.2_0: build failure due to libstdc++ compatibility issue on 10.8 and earlier ----------------------+--------------------- Reporter: dbevans | Owner: dbevans Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: vte | ----------------------+--------------------- Changes (by dbevans): * status: assigned => closed * resolution: => fixed Comment: Considering this fixed for now. Future versions will probably use the cxx11 portgroup, -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 18:47:45 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 18:47:45 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.76e25f5d078ea40dc295b9160ceb69b8@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"7288f4317f196cd0a8326a7a1b9fe1f42bf4b870/macports-ports" 7288f431/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="7288f4317f196cd0a8326a7a1b9fe1f42bf4b870" arm-none-linux-gnueabi-binutils: upgrade to 2.27 * Upgrade to binutils 2.27 * Add the crossbinutils portgroup * Patch is no longer needed * Maintainer timeout See: https://trac.macports.org/ticket/51935 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 23:00:41 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 23:00:41 -0000 Subject: [MacPorts] #50845: libunwind: fails to find 'bits/c++config.h' on 10.5/PPC In-Reply-To: <042.dc439143bad4305d12829f44ffd3509f@macports.org> References: <042.dc439143bad4305d12829f44ffd3509f@macports.org> Message-ID: <057.621d4b6df18f0ed7d4cfa9b661a94888@macports.org> #50845: libunwind: fails to find 'bits/c++config.h' on 10.5/PPC ------------------------+---------------------- Reporter: mojca | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: leopard Port: libunwind | ------------------------+---------------------- Comment (by kencu): Jeremy, all works as you've outlined, through to the end of that LibcxxOnOlderSystems document. Only thing I would add that might not be clear is that the Leopard instructions for Leopard(ppc) only work on Leopard Intel at present. clang-3.7 will install on Leopard intel and generate ppc code that runs, but on Leopard PPC clang-3.4 is as far as you go and doesn't work on PPC as it does on Intel to complete the compiles of the libraries (or clang-3.7). Leopard PPC with clang-3.4 did build libunwind for me, but not universally -- only for PPC. It did build libmacho universally. It would not build libcxxabi just now on PPC, however. {{{ libunwind @3.9.0_0 platform='darwin 9' archs='ppc' libunwind @3.9.0_3 (active) platform='darwin 9' archs='ppc' libunwind-headers @3.9.0_0 (active) platform='darwin 9' archs='noarch' libmacho @886_0+universal (active) platform='darwin 9' archs='i386 ppc' libmacho-headers @886_0 (active) platform='darwin 9' archs='noarch' }}} attempt to build libcxxabi: {{{ sudo port -v install libcxxabi ---> Computing dependencies for libcxxabi. ---> Building libcxxabi + for FILE in '../src/*.cpp' + /opt/local/bin/clang++-mp-3.4 -I/opt/local/include -c -g -O3 -arch ppc -std=c++11 -stdlib=libc++ -fstrict-aliasing -Wstrict-aliasing=2 -Wsign- conversion -Wshadow -Wconversion -Wunused-variable -Wmissing-field- initializers -Wchar-subscripts -Wmismatched-tags -Wmissing-braces -Wshorten-64-to-32 -Wsign-compare -Wstrict-aliasing=2 -Wstrict-overflow=4 -Wunused-parameter -Wnewline-eof -I../include ../src/abort_message.cpp /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libcxxabi/libcxxabi/work/.tmp /abort_message-a08a1d.s:22:Missing string /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libcxxabi/libcxxabi/work/.tmp /abort_message-a08a1d.s:22:Rest of line ignored. 1st junk character valued 49 (1). /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libcxxabi/libcxxabi/work/.tmp /abort_message-a08a1d.s:30:Unknown pseudo-op: .loc /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libcxxabi/libcxxabi/work/.tmp /abort_message-a08a1d.s:30:Rest of line ignored. 1st junk character valued 49 (1). /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libcxxabi/libcxxabi/work/.tmp /abort_message-a08a1d.s:43:Unknown pseudo-op: .loc /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libcxxabi/libcxxabi/work/.tmp /abort_message-a08a1d.s:43:Rest of line ignored. 1st junk character valued 49 (1). /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libcxxabi/libcxxabi/work/.tmp /abort_message-a08a1d.s:60:Unknown pseudo-op: .loc /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libcxxabi/libcxxabi/work/.tmp /abort_message-a08a1d.s:60:Rest of line ignored. 1st junk character valued 49 (1). /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libcxxabi/libcxxabi/work/.tmp /abort_message-a08a1d.s:65:Unknown pseudo-op: .loc /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libcxxabi/libcxxabi/work/.tmp /abort_message-a08a1d.s:65:Rest of line ignored. 1st junk character valued 49 (1). /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libcxxabi/libcxxabi/work/.tmp /abort_message-a08a1d.s:67:Unknown pseudo-op: .loc /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libcxxabi/libcxxabi/work/.tmp /abort_message-a08a1d.s:67:Rest of line ignored. 1st junk character valued 49 (1). /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libcxxabi/libcxxabi/work/.tmp /abort_message-a08a1d.s:69:Unknown pseudo-op: .loc /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libcxxabi/libcxxabi/work/.tmp /abort_message-a08a1d.s:69:Rest of line ignored. 1st junk character valued 49 (1). /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libcxxabi/libcxxabi/work/.tmp /abort_message-a08a1d.s:75:Unknown pseudo-op: .loc /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libcxxabi/libcxxabi/work/.tmp /abort_message-a08a1d.s:75:Rest of line ignored. 1st junk character valued 49 (1). clang: error: assembler (via gcc) command failed with exit code 1 (use -v to see invocation) Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libcxxabi/libcxxabi/work/libcxxabi-3.9.0.src/lib" && ./buildit all Exit code: 1 Error: org.macports.build for port libcxxabi returned: command execution failed }}} Next immediate step for bootstrapping a clang-libcxx plan for leopard PPC would appear to be to 1. get the runtimes (libcxx, libcxxabi, libmacho, libunwind) onto Leopard PPC by building them with clang-3.7 on Leopard Intel (done) and getting them over as binaries. That's reasonably easy. 2. build a few simple cxx11 ports on Leopard Intel with PPC slices, and get them onto the Leopard PPC machine as binary installs and see what happens. I tried building a simple cxx11 port, aria2, on Leopard Intel with a ppc slice and it died early with various errors - libtool being the first -- so this might take some thinking. {{{ sudo port -v install aria2 +universal universal_archs="x86_64 i386 ppc" configure.compiler=macports-clang-3.7 Password: Error: Cannot install aria2 for the arch(s) 'i386 ppc x86_64' because Error: its dependency libtool is only installed for the arch 'i386' Error: and the configured universal_archs 'i386 ppc' are not sufficient. Error: Unable to execute port: architecture mismatch }}} {{{ sudo port -v -n upgrade --force libtool +universal universal_archs="x86_64 i386 ppc" configure.compiler=macports-clang-3.7 fails with libtool: compile: /opt/local/bin/clang-mp-3.7 -DHAVE_CONFIG_H -I. -DLTDLOPEN=libltdl "-DLT_CONFIG_H=" -DLTDL -I. -I. -Ilibltdl -I./libltdl -Ilibltdl/libltdl -I./libltdl/libltdl -I/opt/local/include -pipe -Os -arch x86_64 -arch i386 -arch ppc -c libltdl/ltdl.c -o libltdl /libltdl_libltdl_la-ltdl.o >/dev/null 2>&1 /bin/sh ./libtool --tag=CC --mode=link /opt/local/bin/clang-mp-3.7 -pipe -Os -arch x86_64 -arch i386 -arch ppc -no-undefined -version-info 10:1:3 -dlpreopen libltdl/dlopen.la -L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 -arch i386 -arch ppc -o libltdl/libltdl.la -rpath /opt/local/lib libltdl/loaders /libltdl_libltdl_la-preopen.lo libltdl/libltdl_libltdl_la-lt__alloc.lo libltdl/libltdl_libltdl_la-lt_dlloader.lo libltdl/libltdl_libltdl_la- lt_error.lo libltdl/libltdl_libltdl_la-ltdl.lo libltdl/libltdl_libltdl_la- slist.lo libltdl/lt__argz.lo libtool: error: not configured to extract global symbols from dlpreopened files libtool: link: (cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libtool/libtool/work/libtool-2.4.6/libltdl/.libs/libltdl.lax/dlopen.a/unfat-13206/dlopen.a-x86_64 && ar x "dlopen.a") libtool: link: (cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libtool/libtool/work/libtool-2.4.6/libltdl/.libs/libltdl.lax/dlopen.a/unfat-13206/dlopen.a-i386 && ar x "dlopen.a") libtool: link: (cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libtool/libtool/work/libtool-2.4.6/libltdl/.libs/libltdl.lax/dlopen.a/unfat-13206/dlopen.a-ppc && ar x "dlopen.a") libtool: link: /opt/local/bin/clang-mp-3.7 -dynamiclib -o libltdl/.libs/libltdl.7.dylib libltdl/loaders/.libs/libltdl_libltdl_la- preopen.o libltdl/.libs/libltdl_libltdl_la-lt__alloc.o libltdl/.libs /libltdl_libltdl_la-lt_dlloader.o libltdl/.libs/libltdl_libltdl_la- lt_error.o libltdl/.libs/libltdl_libltdl_la-ltdl.o libltdl/.libs /libltdl_libltdl_la-slist.o libltdl/.libs/lt__argz.o libltdl/.libs/libltdl.lax/dlopen.a/dlopen.o -L/opt/local/lib -Os -arch x86_64 -arch i386 -arch ppc -Wl,-headerpad_max_install_names -arch x86_64 -arch i386 -arch ppc -install_name /opt/local/lib/libltdl.7.dylib -compatibility_version 11 -current_version 11.1 -Wl,-single_module Undefined symbols for architecture x86_64: "_lt_libltdl_LTX_preloaded_symbols", referenced from: _lt_dlinit in libltdl_libltdl_la-ltdl.o ld: symbol(s) not found for architecture x86_64 }}} Perhaps I'll invent a simple 'hello world' port and see if I can get the process at least started with this. But this sounds like a new ticket, rather than adding it here where it doesn't belong... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 23:35:47 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 23:35:47 -0000 Subject: [MacPorts] #52770: Git: pre-commit-hook could run "port lint" if a Portfile is about to be committed by the user... In-Reply-To: <041.f53e08b7fca86571a656be0a1eca329d@macports.org> References: <041.f53e08b7fca86571a656be0a1eca329d@macports.org> Message-ID: <056.aa93a94c99ee24c62c92202095788163@macports.org> #52770: Git: pre-commit-hook could run "port lint" if a Portfile is about to be committed by the user... -----------------------------+--------------------- Reporter: mkae | Owner: admin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: 2.3.4 Resolution: | Keywords: Port: | -----------------------------+--------------------- Comment (by mkae): A nice example where such a hook would have been helpful is e.g. [https://build.macports.org/builders/ports-10.12_x86_64-watcher/builds/2384/steps/subports/logs/property%20changes this failed build] which could have been prevented if {{{port lint}}} would have spotted the issue with an incomplete argument for {{{depends_lib-append}}}, see this diff: {{{ - depends_lib-append qt5-qtsvg + depends_lib-append port:qt5-qtsvg }}} The latter had to be fixed in the [https://build.macports.org/builders/ports-10.12_x86_64-watcher/builds/2385/steps/subports/logs/stdio subsequent commit]. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 23:47:32 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 23:47:32 -0000 Subject: [MacPorts] #50845: libunwind: fails to find 'bits/c++config.h' on 10.5/PPC In-Reply-To: <042.dc439143bad4305d12829f44ffd3509f@macports.org> References: <042.dc439143bad4305d12829f44ffd3509f@macports.org> Message-ID: <057.a50faf6604b92f221beb4d4f9f3d32b9@macports.org> #50845: libunwind: fails to find 'bits/c++config.h' on 10.5/PPC ------------------------+---------------------- Reporter: mojca | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: leopard Port: libunwind | ------------------------+---------------------- Comment (by kencu): So - finally - yes, that all works. I copied over libunwind, libmacho, libcxxabi, and libcxx from the Leopard Intel machine to the Leopard PPC machine, and they all appear to work well there. (you scp the fat binaries from the Leopard Intel machine into `/opt/local/var/macports/incoming/verified/ ` on the Leopard PPC machine, and then install them with `sudo port install -v -b`. I can build a c++ hello world app on Leopard PPC against libc++ with clang-3.4, and it works. A c++ hello world app built against libc++ on Leopard Intel with clang-3.7 also works when copied over to Leopard PPC. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 23:48:43 2016 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2016 23:48:43 -0000 Subject: [MacPorts] #52770: Git: pre-commit-hook could run "port lint" if a Portfile is about to be committed by the user... In-Reply-To: <041.f53e08b7fca86571a656be0a1eca329d@macports.org> References: <041.f53e08b7fca86571a656be0a1eca329d@macports.org> Message-ID: <056.55fddf539254a445f5970bfb67d3b152@macports.org> #52770: Git: pre-commit-hook could run "port lint" if a Portfile is about to be committed by the user... -----------------------------+--------------------- Reporter: mkae | Owner: admin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: 2.3.4 Resolution: | Keywords: Port: | -----------------------------+--------------------- Comment (by mkae): A test showed, that {{{port lint}}} would have spotted this: {{{ $ port lint qtcurve-qt5 Error: Unable to open port: can't set "depends_lib": invalid depspec: qt5-qtsvg }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 02:09:03 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 02:09:03 -0000 Subject: [MacPorts] #52770: Git: pre-commit-hook could run "port lint" if a Portfile is about to be committed by the user... In-Reply-To: <041.f53e08b7fca86571a656be0a1eca329d@macports.org> References: <041.f53e08b7fca86571a656be0a1eca329d@macports.org> Message-ID: <056.7f8ccc6462edb1bffdd42e694cd54f43@macports.org> #52770: Git: pre-commit-hook could run "port lint" if a Portfile is about to be committed by the user... -----------------------------+--------------------- Reporter: mkae | Owner: admin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: 2.3.4 Resolution: | Keywords: Port: | -----------------------------+--------------------- Comment (by larryv): Replying to [comment:1 mkae]: > This hook functionality could probably be implemented as a plugin > directly on GitHub I’m fairly sure that GitHub does not provide this functionality. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 03:40:25 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 03:40:25 -0000 Subject: [MacPorts] #53051: port py-virtualenv add default selection note In-Reply-To: <043.5d1ff70fe0b31a70b1406cced7cd9421@macports.org> References: <043.5d1ff70fe0b31a70b1406cced7cd9421@macports.org> Message-ID: <058.d44434500334128daab6eab0d49cae17@macports.org> #53051: port py-virtualenv add default selection note ----------------------------+---------------------- Reporter: anddam | Owner: larryv Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: py-virtualenv | ----------------------------+---------------------- Comment (by larryv): I don’t really like other people touching the ports I maintain. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 03:54:55 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 03:54:55 -0000 Subject: [MacPorts] #53051: port py-virtualenv add default selection note In-Reply-To: <043.5d1ff70fe0b31a70b1406cced7cd9421@macports.org> References: <043.5d1ff70fe0b31a70b1406cced7cd9421@macports.org> Message-ID: <058.8c3bf07c4905bc22ddfb2c2e463e4660@macports.org> #53051: port py-virtualenv add default selection note ----------------------------+---------------------- Reporter: anddam | Owner: larryv Type: enhancement | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: py-virtualenv | ----------------------------+---------------------- Changes (by larryv): * status: new => accepted -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 03:55:05 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 03:55:05 -0000 Subject: [MacPorts] #53051: port py-virtualenv add default selection note In-Reply-To: <043.5d1ff70fe0b31a70b1406cced7cd9421@macports.org> References: <043.5d1ff70fe0b31a70b1406cced7cd9421@macports.org> Message-ID: <058.83a06eae13f1c4d2a7ecbfbe2cafd19f@macports.org> #53051: port py-virtualenv add default selection note ----------------------------+---------------------- Reporter: anddam | Owner: larryv Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: py-virtualenv | ----------------------------+---------------------- Changes (by larryv): * status: accepted => closed * resolution: => fixed Comment: Closed by [51aa859becd584538bd86dc503ef2b7938010e08/macports-ports]. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 07:45:42 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 07:45:42 -0000 Subject: [MacPorts] #53040: py27-wxpython-3.0 @3.0.2.0 fatal error: 'type_traits' file not found on systems upgraded to libc++ In-Reply-To: <042.60b960fe5a4bb70586997df006b20806@macports.org> References: <042.60b960fe5a4bb70586997df006b20806@macports.org> Message-ID: <057.d66caf52a2a4f424fa6c11a32ac2640d@macports.org> #53040: py27-wxpython-3.0 @3.0.2.0 fatal error: 'type_traits' file not found on systems upgraded to libc++ ------------------------------+---------------------------- Reporter: kencu | Owner: jyrkiwahlstedt Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-wxpython-3.0 | ------------------------------+---------------------------- Comment (by mojca): [http://en.cppreference.com/w/cpp/header/type_traits type_traits] is part of C++11 standard. The libstdc++ as shipped on OS X (I think it's version 2 or something) doesn't support C++11. If you want C++11, you need to switch to libc++ (or to gcc 4.7+ which then using its own libstdc++ version 3). In theory you would also need to add something like `-std=c++11` to compiler flags, but on OS X you would automatically get (some?) C++11 features just by switching to libc++. The problem you are experiencing is because wxWidgets' configure checks whether particular features are available and when you build it on a "libc++" installation, it would find the C++11 features and use them, but then during the linking the flag is apparently missing and it won't be able to find the features it found earlier. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 07:48:50 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 07:48:50 -0000 Subject: [MacPorts] #53040: py27-wxpython-3.0 @3.0.2.0 fatal error: 'type_traits' file not found on systems upgraded to libc++ In-Reply-To: <042.60b960fe5a4bb70586997df006b20806@macports.org> References: <042.60b960fe5a4bb70586997df006b20806@macports.org> Message-ID: <057.3016d2bcad98e9c327a7d94c67380bc3@macports.org> #53040: py27-wxpython-3.0 @3.0.2.0 fatal error: 'type_traits' file not found on systems upgraded to libc++ ------------------------------+---------------------------- Reporter: kencu | Owner: jyrkiwahlstedt Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-wxpython-3.0 | ------------------------------+---------------------------- Comment (by mojca): It's also possible that in case of wxPython the installation doesn't get any flags at all (and it should). But it uses an existing wxWidgets installation that was compiled with those flags and the installed wxWidgets headers claim the support for `type_traits` was there. I should test this on 10.6 with libc++. It is not useful if I just keep guessing. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 08:13:48 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 08:13:48 -0000 Subject: [MacPorts] #53040: py27-wxpython-3.0 @3.0.2.0 fatal error: 'type_traits' file not found on systems upgraded to libc++ In-Reply-To: <042.60b960fe5a4bb70586997df006b20806@macports.org> References: <042.60b960fe5a4bb70586997df006b20806@macports.org> Message-ID: <057.681f11068427c160d66d57ddd9af3177@macports.org> #53040: py27-wxpython-3.0 @3.0.2.0 fatal error: 'type_traits' file not found on systems upgraded to libc++ ------------------------------+---------------------- Reporter: kencu | Owner: mojca Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-wxpython-3.0 | ------------------------------+---------------------- Changes (by mojca): * owner: jyrkiwahlstedt => mojca * cc: mojca (removed) * cc: jyrkiwahlstedt (added) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 08:14:46 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 08:14:46 -0000 Subject: [MacPorts] #53040: py27-wxpython-3.0 @3.0.2.0 fatal error: 'type_traits' file not found on systems upgraded to libc++ In-Reply-To: <042.60b960fe5a4bb70586997df006b20806@macports.org> References: <042.60b960fe5a4bb70586997df006b20806@macports.org> Message-ID: <057.d222d86bdf9da0aeefe0900366f4af56@macports.org> #53040: py27-wxpython-3.0 @3.0.2.0 fatal error: 'type_traits' file not found on systems upgraded to libc++ ------------------------------+---------------------- Reporter: kencu | Owner: mojca Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-wxpython-3.0 | ------------------------------+---------------------- Comment (by mojca): I reassigned the ticket to myself, but if Jyrki wants to work on it ... go ahead. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 09:12:30 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 09:12:30 -0000 Subject: [MacPorts] #53053: atlas build fail -- Xcode can't create dynamic library? Message-ID: <045.1ab6c050d554c8c359441aa8e4c1f425@macports.org> #53053: atlas build fail -- Xcode can't create dynamic library? -------------------------------------------+------------------- Reporter: Zippyzip | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: xcode dynamic library fortran | Port: atlas -------------------------------------------+------------------- I can't manage to build standalone atlas (+gcc5). ( It seems +nofortran avoids the error but then I get problems for atlas dependent ports such as Octave) MacOS X: El Capitan 10.11.6 XCode: 8.1 Macports: 2.3.5. Snippet of presumably relevant part of the log file: {{{ :info:build make[4]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_atlas/atlas/work/ATLAS/build/lib' :info:build /Applications/Xcode.app/Contents/Developer/usr/bin/make dylib :info:build make[5]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_atlas/atlas/work/ATLAS/build/lib' :info:build rm -rf RCW_tMp ; mkdir RCW_tMp :info:build cd RCW_tMp ; ar x ../liblapack.a :info:build cd RCW_tMp ; ar x ../libf77blas.a :info:build cd RCW_tMp ; ar x ../libcblas.a :info:build cd RCW_tMp ; ar x ../libatlas.a :info:build cd RCW_tMp ; /usr/bin/libtool -dynamiclib -o ../libsatlas.dylib \ :info:build -install_name /opt/local/lib/libsatlas.dylib -current_version 3.10.2 \ :info:build -compatibility_version 3.10.2 *.o -lpthread -lm /opt/local/lib/gcc5/libgfortran.dylib :info:build error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: unknown option character `d' in: -dynamiclib :info:build Usage: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool -static [-] file [...] [-filelist listfile[,dirname]] [-arch_only arch] [-sacLT] [-no_warning_for_no_symbols] :info:build Usage: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool -dynamic [-] file [...] [-filelist listfile[,dirname]] [-arch_only arch] [-o output] [-install_name name] [-compatibility_version #] [-current_version #] [-seg1addr 0x#] [-segs_read_only_addr 0x#] [-segs_read_write_addr 0x#] [-seg_addr_table ] [-seg_addr_table_filename ] [-all_load] [-noall_load] :info:build make[5]: *** [dylib] Error 1 :info:build make[5]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_atlas/atlas/work/ATLAS/build/lib' :info:build make[4]: *** [shared_all] Error 2 :info:build make[4]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_atlas/atlas/work/ATLAS/build/lib' :info:build make[3]: *** [dylibs] Error 2 :info:build make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_atlas/atlas/work/ATLAS/build' :info:build make[2]: *** [IBuildDyLibs] Error 2 :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_atlas/atlas/work/ATLAS/build/bin' :info:build ARED LIBRARY UPDATE at 10:05 :info:build make -f Makefile IBuildDyLibs 2>&1 | ./xatlas_tee INSTALL_LOG/LIBDYBUILD.LOG :info:build DONE STAGE 5-2-0 at 10:05 }}} ... {{{ :info:build /Applications/Xcode.app/Contents/Developer/usr/bin/make dylib :info:build rm -rf RCW_tMp ; mkdir RCW_tMp :info:build cd RCW_tMp ; ar x ../liblapack.a :info:build cd RCW_tMp ; ar x ../libf77blas.a :info:build cd RCW_tMp ; ar x ../libcblas.a :info:build cd RCW_tMp ; ar x ../libatlas.a :info:build cd RCW_tMp ; /opt/local/bin/gcc-mp-5 -fomit-frame-pointer -mfpmath=sse -O3 -fno-schedule-insns2 -fPIC -msse4.2 -m64 -fPIC -dynamiclib -o ../libsatlas.dylib \ :info:build -install_name /opt/local/lib/libsatlas.dylib -current_version 3.10.2 \ :info:build -compatibility_version 3.10.2 *.o -lpthread -lm /opt/local/lib/gcc5/libgfortran.dylib :info:build gcc-mp-5: error: /opt/local/lib/gcc5/libgfortran.dylib: No such file or directory :info:build make[1]: *** [dylib] Error 1 :info:build make: *** [shared_all] Error 2 :info:build Command failed: /usr/bin/make shared_all :info:build Exit code: 2 :error:build org.macports.build for port atlas returned: command execution failed }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 09:54:21 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 09:54:21 -0000 Subject: [MacPorts] #53054: vcsn: 2.4 is out Message-ID: <042.8c0aba0378d281d075c02dee4fd8e96e@macports.org> #53054: vcsn: 2.4 is out --------------------+------------------ Reporter: akimd | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: vcsn --------------------+------------------ Hi! Vcsn 2.4 is out, and the current version in MacPorts is 2.4. I attached the diff, and the corresponding PortFile. Cheers! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 09:54:39 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 09:54:39 -0000 Subject: [MacPorts] #53054: vcsn: 2.4 is out In-Reply-To: <042.8c0aba0378d281d075c02dee4fd8e96e@macports.org> References: <042.8c0aba0378d281d075c02dee4fd8e96e@macports.org> Message-ID: <057.5465c1f71815c798db371eb247ea6754@macports.org> #53054: vcsn: 2.4 is out ---------------------+----------------- Reporter: akimd | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: vcsn | ---------------------+----------------- Changes (by akimd): * Attachment "macports.diff" added. Diff -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 09:54:57 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 09:54:57 -0000 Subject: [MacPorts] #53054: vcsn: 2.4 is out In-Reply-To: <042.8c0aba0378d281d075c02dee4fd8e96e@macports.org> References: <042.8c0aba0378d281d075c02dee4fd8e96e@macports.org> Message-ID: <057.055bb5379b01462f72def239d79f250b@macports.org> #53054: vcsn: 2.4 is out ---------------------+----------------- Reporter: akimd | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: vcsn | ---------------------+----------------- Changes (by akimd): * Attachment "vcsn.macports" added. vcsn 2.4 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 09:55:47 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 09:55:47 -0000 Subject: [MacPorts] #53054: vcsn: 2.4 is out In-Reply-To: <042.8c0aba0378d281d075c02dee4fd8e96e@macports.org> References: <042.8c0aba0378d281d075c02dee4fd8e96e@macports.org> Message-ID: <057.754d46b486e6ab673fb3c83fd5960c1f@macports.org> #53054: vcsn: 2.4 is out ---------------------+----------------- Reporter: akimd | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: vcsn | ---------------------+----------------- Comment (by akimd): Sorry, I meant that the current version in MacPorts is 2.2. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 10:18:28 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 10:18:28 -0000 Subject: [MacPorts] #53046: editors/neovim: please update to 0.1.7 (released Nov 27) In-Reply-To: <039.10a4f815af396149e4935bf28477d027@macports.org> References: <039.10a4f815af396149e4935bf28477d027@macports.org> Message-ID: <054.831f2cf2a0f7562b26278e54a98b139a@macports.org> #53046: editors/neovim: please update to 0.1.7 (released Nov 27) ---------------------+-------------------- Reporter: jf | Owner: raimue Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: neovim | ---------------------+-------------------- Changes (by raimue): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"b8348e4bf7cce46e4cd680e00af796991ff71f12/macports-ports" b8348e4b/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="b8348e4bf7cce46e4cd680e00af796991ff71f12" neovim: Update to version 0.1.7 Closes: https://trac.macports.org/ticket/53046 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 10:57:42 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 10:57:42 -0000 Subject: [MacPorts] #52951: wxWidgets-3.2 does not build In-Reply-To: <045.5ccbbc3b9cc1ea7e021e5dbb885d68cb@macports.org> References: <045.5ccbbc3b9cc1ea7e021e5dbb885d68cb@macports.org> Message-ID: <060.3b180c25ade551f035b6e43fbc849e5a@macports.org> #52951: wxWidgets-3.2 does not build ----------------------------+---------------------- Reporter: rkitover | Owner: mojca Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: sierra Port: wxWidgets-3.2 | ----------------------------+---------------------- Comment (by mojca): Are you willing to check whether https://github.com/mojca/macports- ports/tree/wx/graphics/wxWidgets-3.2 works for you? (I currently don't have access to 10.12.) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 10:59:10 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 10:59:10 -0000 Subject: [MacPorts] #52951: wxWidgets-3.2 does not build In-Reply-To: <045.5ccbbc3b9cc1ea7e021e5dbb885d68cb@macports.org> References: <045.5ccbbc3b9cc1ea7e021e5dbb885d68cb@macports.org> Message-ID: <060.f4c740d4c8ef049bafe3b8986e50377d@macports.org> #52951: wxWidgets-3.2 does not build ----------------------------+---------------------- Reporter: rkitover | Owner: mojca Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: sierra Port: wxWidgets-3.2 | ----------------------------+---------------------- Changes (by mojca): * Attachment "wxWidgets-3.2.Portfile" added. A Portfile for wxWidgets 3.1.0 from the latest git master, should hopefully work on 10.12 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 10:59:28 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 10:59:28 -0000 Subject: [MacPorts] #53055: Undefined symbols from libavcodec "_xvid_plugin_2pass2" "_xvid_plugin_single" Message-ID: <048.1858e3aec017963dbaa47013a433d4c6@macports.org> #53055: Undefined symbols from libavcodec "_xvid_plugin_2pass2" "_xvid_plugin_single" -------------------------+-------------------- Reporter: platipodium | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: ffmpeg -------------------------+-------------------- ffmpeg fails to build on sierra with undefined symbols in libavcodec: {{{ :info:build Undefined symbols for architecture x86_64: :info:build "_xvid_plugin_2pass2", referenced from: :info:build _xvid_encode_init in libxvid.o :info:build _ff_xvid_rate_control_init in libxvid_rc.o :info:build _ff_xvid_rate_estimate_qscale in libxvid_rc.o :info:build ld: symbol(s) not found for architecture x86_64 :info:build library.mak:102: recipe for target 'libavcodec/libavcodec.57.dylib' failed :info:build gmake: *** [libavcodec/libavcodec.57.dylib] Error 1 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 10:59:59 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 10:59:59 -0000 Subject: [MacPorts] #53055: Undefined symbols from libavcodec "_xvid_plugin_2pass2" "_xvid_plugin_single" In-Reply-To: <048.1858e3aec017963dbaa47013a433d4c6@macports.org> References: <048.1858e3aec017963dbaa47013a433d4c6@macports.org> Message-ID: <063.11e04745aec3d3305a8d7e3d4820cfd5@macports.org> #53055: Undefined symbols from libavcodec "_xvid_plugin_2pass2" "_xvid_plugin_single" --------------------------+----------------- Reporter: platipodium | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ffmpeg | --------------------------+----------------- Changes (by platipodium): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 11:24:39 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 11:24:39 -0000 Subject: [MacPorts] #52582: ghc @7.8.3_4: RTS incompatibility with Sierra In-Reply-To: <047.31ef8be7dd7559a12bcd7c2b768f2d94@macports.org> References: <047.31ef8be7dd7559a12bcd7c2b768f2d94@macports.org> Message-ID: <062.ce67b6ae60dd67285eee2f44abf9616c@macports.org> #52582: ghc @7.8.3_4: RTS incompatibility with Sierra -------------------------+----------------------------- Reporter: shanemikel | Owner: neverpanic Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: sierra haspatch Port: ghc | -------------------------+----------------------------- Comment (by jmalcaide): I can confirm that after applying the Portfile patch and adding the GetTime.c patch file, the ghc port builds, installs and works just fine on macOS Sierra. So I also suggest to apply the fixes and close the bug. Please notice that this bug also affects the ports dependent on ghc. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 12:02:15 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 12:02:15 -0000 Subject: [MacPorts] #53056: buildbot: multiple failed dependencies reported as multiple broken builds in email report Message-ID: <042.b427e2aae5c2ea9c0d3d5e7b01b9a607@macports.org> #53056: buildbot: multiple failed dependencies reported as multiple broken builds in email report ----------------------------+--------------------- Reporter: mojca | Owner: admin@… Type: defect | Status: new Priority: Low | Milestone: Component: server/hosting | Version: Keywords: buildbot | Port: ----------------------------+--------------------- See [https://lists.macports.org/pipermail/macports- builds/2016-December/001964.html this report]: {{{ Log from failed builds: Building 'root6' ... [ERROR] (failed to install dependency 'cmake') > maintainers: jonesc at hep.phy.cam.ac.uk,michaelld at macports.org,mojca at macports.org. Building 'root6' ... [ERROR] (failed to install dependency 'py27-setuptools') > maintainers: jmr at macports.org,jonesc at hep.phy.cam.ac.uk,mojca at macports.org. Building 'root6' ... [ERROR] (failed to install dependency 'harfbuzz') > maintainers: jonesc at hep.phy.cam.ac.uk,mojca at macports.org,ryandesign at macports.org. Building 'root6' ... [ERROR] (failed to install dependency 'libunwind') > maintainers: jeremyhu at macports.org,jonesc at hep.phy.cam.ac.uk,mojca at macports.org. Building 'root6' ... [ERROR] (failed to install dependency 'ocaml') > maintainers: jonesc at hep.phy.cam.ac.uk,mojca at macports.org,mww at macports.org. }}} that is generated by `mpbb/mpbb-install-dependencies` {{{ #!bash # $depvariants isn't quoted on purpose # shellcheck disable=SC2086 if ! failcache_test "$depname" $depvariants; then text="Dependency '${depname}' with variants '${depvariants}' has previously failed and is required." echo "$text" >&2 echo "$text" >> "$log_status_dependencies" echo "Building '$port' ... [ERROR] (failed to install dependency '${depname}') maintainers: $(get-maintainers "$port" "${depname}")." >> "$log_subports_progress" failcachecounter=$((failcachecounter + 1)) fi }}} to result in [https://build.macports.org/builders/ports-10.5_ppc_legacy- watcher/builds/2593/steps/summary/logs/stdio/text this]: {{{ Building 'root6' ... [ERROR] (failed to install dependency 'cmake') maintainers: jonesc;hep.phy.cam.ac.uk,michaelld;macports.org,mojca;macports.org. Building 'root6' ... [ERROR] (failed to install dependency 'py27-setuptools') maintainers: jmr;macports.org,jonesc;hep.phy.cam.ac.uk,mojca;macports.org. Building 'root6' ... [ERROR] (failed to install dependency 'harfbuzz') maintainers: jonesc;hep.phy.cam.ac.uk,mojca;macports.org,ryandesign;macports.org. Building 'root6' ... [ERROR] (failed to install dependency 'libunwind') maintainers: jeremyhu;macports.org,jonesc;hep.phy.cam.ac.uk,mojca;macports.org. Building 'root6' ... [ERROR] (failed to install dependency 'ocaml') maintainers: jonesc;hep.phy.cam.ac.uk,mojca;macports.org,mww;macports.org. }}} and then converted to the email list inside `master.cfg` It's harmless in principle and the list of recipients is correct, but the output should be improved. Suggestions welcome. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 12:30:20 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 12:30:20 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.63809ad723133c450e2326f44ebc12f8@macports.org> #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): In [changeset:"410bebe15d26eb99a11917357bd7fa44e56988a7/macports-ports" 410bebe/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="410bebe15d26eb99a11917357bd7fa44e56988a7" octave: use compiler that works for OS and cxx_stdlib values For a full build, octave requires a C++11 compatible compiler with the same standard library (libc++ or libstdc++) as its dependencies. See https://trac.macports.org/ticket/53044 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 12:31:10 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 12:31:10 -0000 Subject: [MacPorts] #52845: mpv: update to 0.22 In-Reply-To: <043.e673edb81f111939a6207eb0205e5927@macports.org> References: <043.e673edb81f111939a6207eb0205e5927@macports.org> Message-ID: <058.1ab08521e1ef598bf3cc31f670fe5af4@macports.org> #52845: mpv: update to 0.22 ---------------------+---------------------- Reporter: iMiKED | Owner: Ionic Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: mpv | ---------------------+---------------------- Comment (by jf): thank you, Ionic! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 12:32:51 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 12:32:51 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.65d4e590c1a2caa62483ea14935a929c@macports.org> #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Comment (by mojca): Didn't you accidentally delete the `#` character? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 12:38:57 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 12:38:57 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.045011e8ee7ec34537f0369eb3f8a8c5@macports.org> #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Comment (by mojca): I didn't test the new commit yet, but in my case GraphicsMagick has been compiled with the standard/default clang compiler against `libstdc++` rather than with gcc (against gcc's own & incompatible `libstdc++`). If the dependency indeed has to be compiled with the same compiler, you are calling for bigger troubles by switching to `macports-gcc-6`. What role does GraphicsMagick play for Octave? Could it be disabled on older platforms if that is the likely source of troubles? Or is it absolutely necessary to do any plotting? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 12:51:06 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 12:51:06 -0000 Subject: [MacPorts] #53053: atlas build fail -- Xcode can't create dynamic library? In-Reply-To: <045.1ab6c050d554c8c359441aa8e4c1f425@macports.org> References: <045.1ab6c050d554c8c359441aa8e4c1f425@macports.org> Message-ID: <060.d71319eb3f4edb4ca3f4667685fc8ab7@macports.org> #53053: atlas build fail -- Xcode can't create dynamic library? -----------------------+------------------------------------------- Reporter: Zippyzip | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: xcode dynamic library fortran Port: atlas | -----------------------+------------------------------------------- Comment (by Zippyzip): My apologies, it seems the problem is not related to Xcode but to gcc/gfortran. I still don't understand why libgfortran is a dead symlink on my installation, looking into it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 12:51:59 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 12:51:59 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.014fd71c87c3cfe990487f223eded018@macports.org> #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): Replying to [comment:3 mojca]: > Didn't you accidentally delete the `#` character? Not only did I accidentally delete the `#` character, it took [https://github.com/macports/macports- ports/commit/ca4b37c4064873939cacb96a1ab9859dc9d45107 two] [https://github.com/macports/macports- ports/commit/891e50e243e7b9edf197c34a7d3bd07ec952abff tries] to fix it.[[BR]] This is one of the times that I wish git didn't keep a full history of commits. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 12:56:05 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 12:56:05 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.e33f823cbcb569983fb490a0f4e6e22c@macports.org> #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): Replying to [comment:4 mojca]: > I didn't test the new commit yet, but in my case GraphicsMagick has been compiled with the standard/default clang compiler against `libstdc++` rather than with gcc (against gcc's own & incompatible `libstdc++`). > > If the dependency indeed has to be compiled with the same compiler, you are calling for bigger troubles by switching to `macports-gcc-6`. Octave only silently defaults to macports-gcc-6 if {{{${configure.cxx_stdlib} eq "libstdc++"}}}.[[BR]] On 10.12, 10.11, and 10.10, the system clang is used.[[BR]] On 10.9, macports-clang is used because the buildbot failure seems to indicate the system clang doesn't work.[[BR]] On 10.8, macports-gcc is used since C++11 is required.[[BR]] This assumes, of course, that the user hasn't intentionally set {{{configure.cxx_stdlib}}} to something else. If the user specifically requests a {{{gcc*}}} variant, then the {{{graphicsmagick}}} variant is not the default and is marked in conflict. Won't this keep the C++ standard library consistent?[[BR]] I am a little bit new to {{{compiler.blacklist}}} and {{{compiler.whitelist}}}.[[BR]] Please feel free to correct my assessment. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 14:13:07 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 14:13:07 -0000 Subject: [MacPorts] #53038: nvm @0.32.1: New port submission In-Reply-To: <045.dc7197e3aae2807b83a493ebec9dddfe@macports.org> References: <045.dc7197e3aae2807b83a493ebec9dddfe@macports.org> Message-ID: <060.12ecded04a4b72e92c3408e707c8eed0@macports.org> #53038: nvm @0.32.1: New port submission -------------------------+----------------- Reporter: coditect | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: nvm | -------------------------+----------------- Comment (by coditect): I have discovered several issues with the way that I set up this nvm port. Perhaps most problematic is the inconsistencies between `$prefix/lib/nvm` and a user's `$PATH` caused by running nvm with sudo. I am abandoning work on this project for now and would like to retract my Portfile submission. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 14:21:02 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 14:21:02 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.ebd9d2b8c8eaa5ee9337418bbafc9cf0@macports.org> #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Comment (by mojca): As predicted the build is [https://build.macports.org/builders/ports-10 .7_x86_64_legacy-builder/builds/18138 still broken]: {{{ Undefined symbols for architecture x86_64: "Magick::Image::ping(std::__cxx11::basic_string, std::allocator > const&)", referenced from: F__magick_ping__(octave_value_list const&, int) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-__magick_read__.o) "Magick::Image::attribute(std::__cxx11::basic_string, std::allocator >)", referenced from: is_indexed(Magick::Image const&) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-__magick_read__.o) fill_exif(octave_scalar_map&, Magick::Image&, std::__cxx11::basic_string, std::allocator > const&) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-__magick_read__.o) fill_exif_ints(octave_scalar_map&, Magick::Image&, std::__cxx11::basic_string, std::allocator > const&) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-__magick_read__.o) fill_exif_floats(octave_scalar_map&, Magick::Image&, std::__cxx11::basic_string, std::allocator > const&) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-__magick_read__.o) F__magick_finfo__(octave_value_list const&, int) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-__magick_read__.o) octave_value_list read_images(std::vector >&, Array const&, int const&, octave_scalar_map const&) in libcorefcn.a(libinterp_corefcn_libcorefcn_la- __magick_read__.o) octave_value_list read_images > >(std::vector >&, Array const&, int const&, octave_scalar_map const&) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-__magick_read__.o) ... "Magick::CoderInfo::CoderInfo(std::__cxx11::basic_string, std::allocator > const&)", referenced from: F__magick_formats__(octave_value_list const&, int) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-__magick_read__.o) "Magick::Image::magick[abi:cxx11]() const", referenced from: is_indexed(Magick::Image const&) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-__magick_read__.o) F__magick_ping__(octave_value_list const&, int) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-__magick_read__.o) F__magick_finfo__(octave_value_list const&, int) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-__magick_read__.o) octave_value_list read_images(std::vector >&, Array const&, int const&, octave_scalar_map const&) in libcorefcn.a(libinterp_corefcn_libcorefcn_la- __magick_read__.o) octave_value_list read_images > >(std::vector >&, Array const&, int const&, octave_scalar_map const&) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-__magick_read__.o) octave_value_list read_images > >(std::vector >&, Array const&, int const&, octave_scalar_map const&) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-__magick_read__.o) octave_value_list read_images(std::vector >&, Array const&, int const&, octave_scalar_map const&) in libcorefcn.a(libinterp_corefcn_libcorefcn_la- __magick_read__.o) ... "Magick::Image::comment[abi:cxx11]() const", referenced from: F__magick_finfo__(octave_value_list const&, int) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-__magick_read__.o) "Magick::CoderInfo::description[abi:cxx11]() const", referenced from: F__magick_formats__(octave_value_list const&, int) in libcorefcn.a (libinterp_corefcn_libcorefcn_la-__magick_read__.o) ld: symbol(s) not found for architecture x86_64 }}} You cannot simply fall back to macports-gcc-6 just because it would be nice to have C++11. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 14:23:35 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 14:23:35 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.01ee2cb22ff08c8f7533327e940d86b8@macports.org> #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Comment (by mojca): Replying to [comment:5 MarcusCalhoun-Lopez]: > Replying to [comment:3 mojca]: > > Didn't you accidentally delete the `#` character? > Not only did I accidentally delete the `#` character, it took [https://github.com/macports/macports- ports/commit/ca4b37c4064873939cacb96a1ab9859dc9d45107 two] [https://github.com/macports/macports- ports/commit/891e50e243e7b9edf197c34a7d3bd07ec952abff tries] to fix it.[[BR]] > This is one of the times that I wish git didn't keep a full history of commits. As long as you don't push the changes to the main server, you can edit the commits however you want. But once you push to the server, you cannot do it any longer (you can do it on your own fork of course, it has only been disabled on the main server on purpose). Of course you have to test your changes before pushing :) SVN is actually worse in that respect. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 14:36:15 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 14:36:15 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.e994cb368812fbb2b6ae2d16c236e987@macports.org> #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): Replying to [comment:7 mojca]: > As predicted the build is [https://build.macports.org/builders/ports-10 .7_x86_64_legacy-builder/builds/18138 still broken]:[[BR]] > You cannot simply fall back to macports-gcc-6 just because it would be nice to have C++11. As of version 4.2, C++11 is a requirement of Octave, so we must find a way of using a C++11 compliant compiler.[[BR]] I apparently do not understand libc++ vs libstdc++ as well as I though I did.[[BR]] Another wrinkle is that I have very limited ability to test my code on older systems.[[BR]] I will keep trying to find a solution, but any suggestions are welcome.[[BR]] Thank you for helping to keep an eye on this. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 14:37:40 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 14:37:40 -0000 Subject: [MacPorts] #53031: macports ncl fails, mac install of ncarg works In-Reply-To: <043.2f66a17331fd430dc6114c13ca7272cd@macports.org> References: <043.2f66a17331fd430dc6114c13ca7272cd@macports.org> Message-ID: <058.3a42df3e9c1a8da21bf444353fb21b5e@macports.org> #53031: macports ncl fails, mac install of ncarg works ---------------------+---------------------- Reporter: basmac | Owner: tenomoto Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: ncarg | ---------------------+---------------------- Comment (by basmac): Hi, thanks for finding the issue, when I run your bar.ncl I get the following. Is this what we are supposed to get ? [mac27:~] bmcinnes% ncl bar.ncl Copyright (C) 1995-2015 - All Rights Reserved University Corporation for Atmospheric Research NCAR Command Language Version 6.3.0 The use of this software is governed by a License Agreement. See http://www.ncl.ucar.edu/ for more details. Variable: nc_file_type Type: string Total Size: 8 bytes 1 values Number of Dimensions: 1 Dimensions and sizes: [1] Coordinates: (0) netcdf3 fatal:Variable (nc_file_type) is undefined fatal:["Execute.c":8575]:Execute: Error occurred at or near line 10 in file bar.ncl fatal:["Execute.c":8575]:Execute: Error occurred at or near line 16 in file bar.ncl [mac27:~] bmcinnes% I am not sure if this is related, but the user also has this issue, for your information I made a script that tests both the regridding and the ability to plot .png files. Here is the output when I try to run it using the /usr/local NCL version: [mac72:~/NCL/NCLtalk/NCLmacports] mgehne% setenv NCARG_ROOT /usr/local [mac72:~/NCL/NCLtalk/NCLmacports] mgehne% setenv PATH /usr/local/$PATH [mac72:~/NCL/NCLtalk/NCLmacports] mgehne% source ~/.tcshrc [mac72:~/NCL/NCLtalk/NCLmacports] mgehne% ncl test_regrid_plot.ncl Copyright (C) 1995-2015 - All Rights Reserved University Corporation for Atmospheric Research NCAR Command Language Version 6.3.0 The use of this software is governed by a License Agreement. See http://www.ncl.ucar.edu/ for more details. (0) Regrid option is on. (0) Plot option is on. (0) defining data array Variable: data Type: float Total Size: 259200 bytes 64800 values Number of Dimensions: 2 Dimensions and sizes: [lat | 180] x [lon | 360] Coordinates: lat: [-89.5..89.5] lon: [ 0..359] (0) Regridding! (0) defining new lat and lon arrays (0) defining options for regridding (0) Regridding using method = neareststod dyld: Library not loaded: /usr/local/lib/libgfortran.3.dylib Referenced from: /usr/local/ncl/bin/ESMF_RegridWeightGen Reason: image not found fatal:The result of the conditional expression yields a missing value. NCL can not determine branch, see ismissing function fatal:["Execute.c":8575]:Execute: Error occurred at or near line 2938 in file $NCARG_ROOT/lib/ncarg/nclscripts/esmf/ESMF_regridding.ncl fatal:["Execute.c":8575]:Execute: Error occurred at or near line 4027 in file $NCARG_ROOT/lib/ncarg/nclscripts/esmf/ESMF_regridding.ncl fatal:["Execute.c":8575]:Execute: Error occurred at or near line 69 in file test_regrid_plot.ncl [mac72:~/NCL/NCLtalk/NCLmacports] mgehne% which ncl /usr/local/bin/ncl [mac72:~/NCL/NCLtalk/NCLmacports] mgehne% env | grep NCARG NCARG_ROOT=/usr/local NCARG_COLORMAPS=/Users/mgehne/NCL/Colormaps:/usr/local/lib/ncarg/colormaps This is a slightly different error message than I have been getting previously. I also attached the test script if you feel like running that on your machine. Setting the options at the beginning to False turns off the regridding or plotting. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 14:39:02 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 14:39:02 -0000 Subject: [MacPorts] #53054: vcsn: 2.4 is out In-Reply-To: <042.8c0aba0378d281d075c02dee4fd8e96e@macports.org> References: <042.8c0aba0378d281d075c02dee4fd8e96e@macports.org> Message-ID: <057.75f97bb252a60e791298ffa565f08dbd@macports.org> #53054: vcsn: 2.4 is out ---------------------+--------------------------------- Reporter: akimd | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: vcsn | ---------------------+--------------------------------- Changes (by mf2k): * keywords: => haspatch maintainer -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 14:39:37 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 14:39:37 -0000 Subject: [MacPorts] #53054: vcsn: 2.4 is out In-Reply-To: <042.8c0aba0378d281d075c02dee4fd8e96e@macports.org> References: <042.8c0aba0378d281d075c02dee4fd8e96e@macports.org> Message-ID: <057.9534533a54a4ba943b8898cb015a5a9f@macports.org> #53054: vcsn: 2.4 is out ---------------------+--------------------------------- Reporter: akimd | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: vcsn | ---------------------+--------------------------------- Comment (by mf2k): Thank you! We only need the diff, not the complete Portfile attached. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 14:41:41 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 14:41:41 -0000 Subject: [MacPorts] #53055: ffmpeg: Undefined symbols from libavcodec "_xvid_plugin_2pass2" "_xvid_plugin_single" (was: Undefined symbols from libavcodec "_xvid_plugin_2pass2" "_xvid_plugin_single") In-Reply-To: <048.1858e3aec017963dbaa47013a433d4c6@macports.org> References: <048.1858e3aec017963dbaa47013a433d4c6@macports.org> Message-ID: <063.7b6890ae29626f3ba99d065d1c5d47d3@macports.org> #53055: ffmpeg: Undefined symbols from libavcodec "_xvid_plugin_2pass2" "_xvid_plugin_single" --------------------------+---------------------- Reporter: platipodium | Owner: dbevans Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ffmpeg | --------------------------+---------------------- Changes (by mf2k): * owner: => dbevans * status: new => assigned * cc: jeremyhu (added) Comment: In the future, please Cc the port maintainers ({{{port info --maintainers ffmpeg}}}), if any. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 14:46:59 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 14:46:59 -0000 Subject: [MacPorts] #53053: atlas build fail -- Xcode can't create dynamic library? In-Reply-To: <045.1ab6c050d554c8c359441aa8e4c1f425@macports.org> References: <045.1ab6c050d554c8c359441aa8e4c1f425@macports.org> Message-ID: <060.7f3ad0bf00fdd9c740153fdcea34d0cd@macports.org> #53053: atlas build fail -- Xcode can't create dynamic library? -----------------------+---------------------- Reporter: Zippyzip | Owner: Veence Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: atlas | -----------------------+---------------------- Changes (by mf2k): * cc: vince@… (removed) * owner: => Veence * status: new => assigned * keywords: xcode dynamic library fortran => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 14:48:07 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 14:48:07 -0000 Subject: [MacPorts] #53038: nvm @0.32.1: New port submission In-Reply-To: <045.dc7197e3aae2807b83a493ebec9dddfe@macports.org> References: <045.dc7197e3aae2807b83a493ebec9dddfe@macports.org> Message-ID: <060.8b38e4fbe3bad5b00be7ba51d55d45f1@macports.org> #53038: nvm @0.32.1: New port submission -------------------------+-------------------- Reporter: coditect | Owner: Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: wontfix | Keywords: Port: nvm | -------------------------+-------------------- Changes (by mf2k): * status: new => closed * resolution: => wontfix -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 14:48:53 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 14:48:53 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.a36ddd27fad72b9dbeb1579c4b9d8489@macports.org> #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Comment (by mojca): Replying to [comment:6 MarcusCalhoun-Lopez]: > Octave only silently defaults to macports-gcc-6 if {{{${configure.cxx_stdlib} eq "libstdc++"}}}. OK, but how exactly doe that help? > On 10.12, 10.11, and 10.10, the system clang is used.[[BR]] > On 10.9, macports-clang is used because the buildbot failure seems to indicate the system clang doesn't work. That's both fine. > On 10.8, macports-gcc is used since C++11 is required. That's generally bad. Unless you make sure that all dependencies were built with macports-gcc as well, but even then it's better to switch to `libc++` for all. > If the user specifically requests a {{{gcc*}}} variant, then the {{{graphicsmagick}}} variant is not the default and is marked in conflict. This doesn't seem to be the case with your current code: {{{ #!tcl if { [variant_isset graphicsmagick] && ${configure.cxx_stdlib} eq "libstdc++"} { compiler.blacklist-append {macports-clang-*} compiler.whitelist-append \ macports-gcc-6 \ macports-gcc-5 \ macports-gcc-4.9 \ macports-gcc-4.8 \ macports-gcc-4.7 } }}} You don't set any variant anywhere and you actually switch to macports-gcc when you specifically '''know''' that graphicsmagic is being used. If you set a whitelist, you don't need a blacklist. I also noticed that you blacklist clang at various places in a redundant way: {{{ #!tcl compiler.blacklist-append {*gcc-3*} {*gcc-4.[0-6]} {clang < 700} cc compiler.blacklist-append { clang <= 318.0.61 } }}} > Won't this keep the C++ standard library consistent? No. The macports-gcc compiler is specifically not compatible with the default compiler. And in a very bad way. Replying to [comment:9 MarcusCalhoun-Lopez]: > As of version 4.2, C++11 is a requirement of Octave, so we must find a way of using a C++11 compliant compiler. My suggestion would be to switch to `libc++` and disable `graphicsmagic` unless `libc++` is default already (in that case `graphicsmagic` can stay). The only other alternative is to provide an alternative build of graphicsmagic against `libc++` (I do that with a subport `wxWidgets-3.0-libcxx` for example, but it might not always be always possible or practical or reasonable to do so.) What exactly does graphicsmagic bring? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 14:51:30 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 14:51:30 -0000 Subject: [MacPorts] #53031: macports ncl fails, mac install of ncarg works In-Reply-To: <043.2f66a17331fd430dc6114c13ca7272cd@macports.org> References: <043.2f66a17331fd430dc6114c13ca7272cd@macports.org> Message-ID: <058.82b397939bddda49a97f9aeaec401b8f@macports.org> #53031: macports ncl fails, mac install of ncarg works ---------------------+---------------------- Reporter: basmac | Owner: tenomoto Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: ncarg | ---------------------+---------------------- Changes (by basmac): * Attachment "test_regrid_plot.ncl" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 16:50:38 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 16:50:38 -0000 Subject: [MacPorts] #53057: czmq will not build: upgrade to v4 or patch header file in 3.0.2 Message-ID: <050.2c440ca4a5d1d2ec8897d4ba69b60eda@macports.org> #53057: czmq will not build: upgrade to v4 or patch header file in 3.0.2 -------------------------------+------------------ Reporter: brianboonstra | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: zmq header pragma | Port: czmq -------------------------------+------------------ Since zmq in MacPorts is now version 4.2, the czmq package (at czmq v3.0.2) no longer builds. This is due to czmq_prelude.h attempting to #import the deprecated zmq_utils. As a result of this import we end up with a clang compiler error arising from line zmq_utils:40 #pragma GCC diagnostic ignored "-Wcpp" Version 4 of czmq corrected the import in https://github.com/zeromq/czmq/commit/9c782c08c29770c400fdad756f9d2c54a367358a Version 3.0.2 never got the correction backported. MacPorts should either backport the czmq patch or switch to version 4. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 17:34:29 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 17:34:29 -0000 Subject: [MacPorts] #52770: Git: pre-commit-hook could run "port lint" if a Portfile is about to be committed by the user... In-Reply-To: <041.f53e08b7fca86571a656be0a1eca329d@macports.org> References: <041.f53e08b7fca86571a656be0a1eca329d@macports.org> Message-ID: <056.9b30114a639548d26a3e1d09fa53fd9c@macports.org> #52770: Git: pre-commit-hook could run "port lint" if a Portfile is about to be committed by the user... -----------------------------+--------------------- Reporter: mkae | Owner: admin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: 2.3.4 Resolution: | Keywords: Port: | -----------------------------+--------------------- Comment (by mkae): Replying to [comment:4 larryv]: > I’m fairly sure that GitHub does not provide this functionality. Surely not directly on GitHub, Larry, but triggered from there on the buildbots or a dedicated lintbot perhaps. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 18:05:33 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 18:05:33 -0000 Subject: [MacPorts] #52770: Git: pre-commit-hook could run "port lint" if a Portfile is about to be committed by the user... In-Reply-To: <041.f53e08b7fca86571a656be0a1eca329d@macports.org> References: <041.f53e08b7fca86571a656be0a1eca329d@macports.org> Message-ID: <056.c3215ef10b205ccd994a3f73e385ae0f@macports.org> #52770: Git: pre-commit-hook could run "port lint" if a Portfile is about to be committed by the user... -----------------------------+--------------------- Reporter: mkae | Owner: admin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: 2.3.4 Resolution: | Keywords: Port: | -----------------------------+--------------------- Comment (by raimue): When you start with WebHooks this sounds like a different use case and you are not talking about a pre-commit hook anymore. Yes, `port lint` for pull requests would be nice to have. I previously suggested this on macports-dev to explore using [https://travis-ci.org/ Travis CI] for this, as they offer the required isolated environment, which is not provided by our buildbots. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 18:13:38 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 18:13:38 -0000 Subject: [MacPorts] #52770: Git: pre-commit-hook could run "port lint" if a Portfile is about to be committed by the user... In-Reply-To: <041.f53e08b7fca86571a656be0a1eca329d@macports.org> References: <041.f53e08b7fca86571a656be0a1eca329d@macports.org> Message-ID: <056.3e19db3ebed76a00253722bc287bb01b@macports.org> #52770: Git: pre-commit-hook could run "port lint" if a Portfile is about to be committed by the user... -----------------------------+--------------------- Reporter: mkae | Owner: admin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: 2.3.4 Resolution: | Keywords: Port: | -----------------------------+--------------------- Comment (by mkae): You are right, indeed I drifted off-topic... Sorry for that. Best to stick to the pre-commit hook which would have to lint all to-be- committed Portfiles. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 20:06:32 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 20:06:32 -0000 Subject: [MacPorts] #48800: gtest: please remove In-Reply-To: <047.9000c372c4b2abc640d29ce0ec79dc97@macports.org> References: <047.9000c372c4b2abc640d29ce0ec79dc97@macports.org> Message-ID: <062.fbf307c67c82ed103f63d5f9013c54a2@macports.org> #48800: gtest: please remove -------------------------+------------------- Reporter: ryandesign | Owner: blair Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gtest | -------------------------+------------------- Comment (by little-big-h): By now, the port is broken because the svn-URL isn't valid anymore (the project was moved to github). This must be the worst possible solution: a port that is not really maintained, broken and discouraged by the upstream developers. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 20:08:31 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 20:08:31 -0000 Subject: [MacPorts] #53055: ffmpeg: Undefined symbols from libavcodec "_xvid_plugin_2pass2" "_xvid_plugin_single" In-Reply-To: <048.1858e3aec017963dbaa47013a433d4c6@macports.org> References: <048.1858e3aec017963dbaa47013a433d4c6@macports.org> Message-ID: <063.f01d33227884d43e8195da3e6858ac57@macports.org> #53055: ffmpeg: Undefined symbols from libavcodec "_xvid_plugin_2pass2" "_xvid_plugin_single" --------------------------+---------------------- Reporter: platipodium | Owner: dbevans Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ffmpeg | --------------------------+---------------------- Changes (by dbevans): * status: assigned => accepted Comment: I'm unable to reproduce this issue on Sierra and the log file attached is not that of a clean build. Please make sure your port tree is up-to-date and try again after cleaning ffmpeg. If the failure appears again you should then submit the full log produced. The log should show not only the build failure itself but all steps leading up to it, Also indicate if you are using any non-default variants. {{{ sudo port sync sudo port clean ffmpeg sudo port install ffmpeg }}} Thanks for your help -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 20:38:31 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 20:38:31 -0000 Subject: [MacPorts] #53055: ffmpeg: Undefined symbols from libavcodec "_xvid_plugin_2pass2" "_xvid_plugin_single" In-Reply-To: <048.1858e3aec017963dbaa47013a433d4c6@macports.org> References: <048.1858e3aec017963dbaa47013a433d4c6@macports.org> Message-ID: <063.f21752b139b922324499641e0f5f1fa7@macports.org> #53055: ffmpeg: Undefined symbols from libavcodec "_xvid_plugin_2pass2" "_xvid_plugin_single" --------------------------+---------------------- Reporter: platipodium | Owner: dbevans Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ffmpeg | --------------------------+---------------------- Comment (by platipodium): OK, this was helpful. {{{ Error: org.macports.archivefetch for port ffmpeg returned: libsdl2 must be installed without +x11. }}} So I reinstalled libsdl -x11 and thereafter ffmpeg was fine. Thanks! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 20:39:34 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 20:39:34 -0000 Subject: [MacPorts] #53031: macports ncl fails, mac install of ncarg works In-Reply-To: <043.2f66a17331fd430dc6114c13ca7272cd@macports.org> References: <043.2f66a17331fd430dc6114c13ca7272cd@macports.org> Message-ID: <058.965eb87133f4ed68d82d312ce59358e9@macports.org> #53031: macports ncl fails, mac install of ncarg works ---------------------+---------------------- Reporter: basmac | Owner: tenomoto Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: ncarg | ---------------------+---------------------- Comment (by basmac): On clean mac Sierra and ncl 6.3.0 in /usr/local/, your test fails for /opt/local version of ncl and works on /usr/local version which is 10.10. [mac27:~] bmcinnes% cd [mac27:~] bmcinnes% setenv NCARG_ROOT /opt/local [mac27:~] bmcinnes% ncl bar.ncl Copyright (C) 1995-2015 - All Rights Reserved University Corporation for Atmospheric Research NCAR Command Language Version 6.3.0 The use of this software is governed by a License Agreement. See http://www.ncl.ucar.edu/ for more details. Variable: nc_file_type Type: string Total Size: 8 bytes 1 values Number of Dimensions: 1 Dimensions and sizes: [1] Coordinates: (0) netcdf3 fatal:Variable (nc_file_type) is undefined fatal:["Execute.c":8575]:Execute: Error occurred at or near line 10 in file bar.ncl fatal:["Execute.c":8575]:Execute: Error occurred at or near line 16 in file bar.ncl [mac27:~] bmcinnes% /usr/local/bin/ncl bar.ncl Copyright (C) 1995-2015 - All Rights Reserved University Corporation for Atmospheric Research NCAR Command Language Version 6.3.0 The use of this software is governed by a License Agreement. See http://www.ncl.ucar.edu/ for more details. Variable: nc_file_type Type: string Total Size: 8 bytes 1 values Number of Dimensions: 1 Dimensions and sizes: [1] Coordinates: (0) netcdf3 Variable: nc_file_type Type: string Total Size: 8 bytes 1 values Number of Dimensions: 1 Dimensions and sizes: [1] Coordinates: (0) netcdf4 Variable: nc_file_type Type: string Total Size: 8 bytes 1 values Number of Dimensions: 1 Dimensions and sizes: [1] Coordinates: (0) netcdf3 [mac27:~] bmcinnes% -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 20:44:29 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 20:44:29 -0000 Subject: [MacPorts] #52951: wxWidgets-3.2 does not build In-Reply-To: <045.5ccbbc3b9cc1ea7e021e5dbb885d68cb@macports.org> References: <045.5ccbbc3b9cc1ea7e021e5dbb885d68cb@macports.org> Message-ID: <060.438b9662ffaa011ca8a4c16670b939ee@macports.org> #52951: wxWidgets-3.2 does not build ----------------------------+---------------------- Reporter: rkitover | Owner: mojca Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: sierra Port: wxWidgets-3.2 | ----------------------------+---------------------- Comment (by rkitover): Just built your Portfile, builds fine, tried linking our app with it, works fine as well. Thank you! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 20:49:23 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 20:49:23 -0000 Subject: [MacPorts] #52951: wxWidgets-3.2 does not build In-Reply-To: <045.5ccbbc3b9cc1ea7e021e5dbb885d68cb@macports.org> References: <045.5ccbbc3b9cc1ea7e021e5dbb885d68cb@macports.org> Message-ID: <060.8170967c05240357dd2d54473a25a9ae@macports.org> #52951: wxWidgets-3.2 does not build ----------------------------+---------------------- Reporter: rkitover | Owner: mojca Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: sierra Port: wxWidgets-3.2 | ----------------------------+---------------------- Comment (by mojca): Thanks for confirmation. I'll wait for [https://github.com/wxWidgets/wxWidgets/pull/370 another patch] to be merged in the official repository that will allow wxWidgets 3.2 to be built also on 10.7 & 10.8 (that was broken in the meantime) and then commit a slightly later version. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 20:51:43 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 20:51:43 -0000 Subject: [MacPorts] #53058: nsis: build fails on 10.6 due to a missing zlib Message-ID: <042.90088184fe2b9c0226a378ef5f8f62d8@macports.org> #53058: nsis: build fails on 10.6 due to a missing zlib -------------------------+------------------ Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: snowleopard | Port: nsis -------------------------+------------------ See the [https://build.macports.org/builders/ports-10.6_x86_64_legacy- builder/builds/12923 build log]: {{{ /usr/bin/c++ --version i686-apple-darwin10-g++-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3) Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Checking for C library gdi32... no Checking for C library user32... no Checking for C library pthread... no Checking for C library iconv... no Checking for C library shlwapi... no Checking for C library z... no zlib (darwin) is missing! Command failed: cd "/path/to/nsis/work/nsis-3.01-src" && scons PREFIX="/opt/local" CC="/usr/bin/cc" CXX="/usr/bin/c++" APPEND_CCFLAGS="-stdlib=libstdc++" APPEND_LINKFLAGS="-stdlib=libstdc++" STRIP=0 SKIPSTUBS=all SKIPPLUGINS=all SKIPUTILS=all SKIPMISC=all }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 21:03:54 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 21:03:54 -0000 Subject: [MacPorts] #53057: czmq will not build: upgrade to v4 or patch header file in 3.0.2 In-Reply-To: <050.2c440ca4a5d1d2ec8897d4ba69b60eda@macports.org> References: <050.2c440ca4a5d1d2ec8897d4ba69b60eda@macports.org> Message-ID: <065.8119d296a9aeb693b19b5c502cd97856@macports.org> #53057: czmq will not build: upgrade to v4 or patch header file in 3.0.2 ----------------------------+---------------------- Reporter: brianboonstra | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: czmq | ----------------------------+---------------------- Changes (by mf2k): * keywords: zmq header pragma => * status: new => assigned * owner: => stromnov Comment: In the future, please use WikiFormatting and Cc the port maintainers ({{{port info --maintainers czmq}}}), if any. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 21:04:06 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 21:04:06 -0000 Subject: [MacPorts] #53057: czmq will not build: upgrade to v4 or patch header file in 3.0.2 In-Reply-To: <050.2c440ca4a5d1d2ec8897d4ba69b60eda@macports.org> References: <050.2c440ca4a5d1d2ec8897d4ba69b60eda@macports.org> Message-ID: <065.342c7bf340d2672cf74f7e6d847f9b6b@macports.org> #53057: czmq will not build: upgrade to v4 or patch header file in 3.0.2 ----------------------------+---------------------- Reporter: brianboonstra | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: czmq | ----------------------------+---------------------- Description changed by mf2k: Old description: > Since zmq in MacPorts is now version 4.2, the czmq package (at czmq > v3.0.2) no longer builds. This is due to czmq_prelude.h attempting to > #import the deprecated zmq_utils. As a result of this import we end up > with a clang compiler error arising from line zmq_utils:40 > > #pragma GCC diagnostic ignored "-Wcpp" > > > Version 4 of czmq corrected the import in > > https://github.com/zeromq/czmq/commit/9c782c08c29770c400fdad756f9d2c54a367358a > > Version 3.0.2 never got the correction backported. > > MacPorts should either backport the czmq patch or switch to version 4. New description: Since zmq in MacPorts is now version 4.2, the czmq package (at czmq v3.0.2) no longer builds. This is due to czmq_prelude.h attempting to #import the deprecated zmq_utils. As a result of this import we end up with a clang compiler error arising from line zmq_utils:40 {{{ #pragma GCC diagnostic ignored "-Wcpp" }}} Version 4 of czmq corrected the import in https://github.com/zeromq/czmq/commit/9c782c08c29770c400fdad756f9d2c54a367358a Version 3.0.2 never got the correction backported. MacPorts should either backport the czmq patch or switch to version 4. -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 21:45:01 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 21:45:01 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.1b663a8b4c7fb611fadba5849cf86694@macports.org> #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Comment (by mojca): So two questions in fact: * What exactly is the role of graphicsmagic, what do users loose if it's missing * Why would users want to use `macports-gcc-6`? For the reasons of performance perhaps? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 23:39:38 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 23:39:38 -0000 Subject: [MacPorts] #53054: vcsn @2.2: update to 2.4 (was: vcsn: 2.4 is out) In-Reply-To: <042.8c0aba0378d281d075c02dee4fd8e96e@macports.org> References: <042.8c0aba0378d281d075c02dee4fd8e96e@macports.org> Message-ID: <057.05c28bde658bc5fdec3c6a7df95042ce@macports.org> #53054: vcsn @2.2: update to 2.4 ---------------------+--------------------------------- Reporter: akimd | Owner: larryv Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: vcsn | ---------------------+--------------------------------- Changes (by larryv): * status: new => accepted * owner: => larryv Comment: Thank you! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 23:40:44 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 23:40:44 -0000 Subject: [MacPorts] #50500: simpler up-to-date qca Port allowing concurrent Qt4 and Qt5 installations In-Reply-To: <041.5a8cf720b2316dc3a82d28ba5f1c267c@macports.org> References: <041.5a8cf720b2316dc3a82d28ba5f1c267c@macports.org> Message-ID: <056.3075bfff1f57da1db7391a2e90e88d3f@macports.org> #50500: simpler up-to-date qca Port allowing concurrent Qt4 and Qt5 installations ---------------------+-------------------------------- Reporter: RJVB | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: qca | ---------------------+-------------------------------- Changes (by RJVB): * status: new => closed * resolution: => fixed Comment: In [changeset:"c802cab46968d77548eafffcce6dddc015c93d9f/macports-ports" c802cab4/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="c802cab46968d77548eafffcce6dddc015c93d9f" port:qca* : proposed adoption and introduction of Qt5 subports The QCA ports have been without maintainer for a bit now, and lack the possibility to install for Qt4 and Qt5 concurrently. That possibility is essential for the future KF5 ports, so I propose that Marko and I adopt this port and introduce the required changes. The ports as defined by the current Portfile have seen thorough testing by both of us as well as by a few "beta testers" of my KF5 ports. I don't think there is any point in maintaining the Qt4 and Qt5 variants. The current version also introduces a few changes that are unrelated to Qt5/KF5 but aim to simplify dependencies by reducing the number of subports. This is open for discussion w.r.t. the Qt4 versions. I don't think there is much justification (for use with MacPorts) to build QCA as a framework, but this could be reintroduced as a variant. Closes: #59 Closes: https://trac.macports.org/ticket/50500 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 23:49:58 2016 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2016 23:49:58 -0000 Subject: [MacPorts] #53054: vcsn @2.2: update to 2.4 In-Reply-To: <042.8c0aba0378d281d075c02dee4fd8e96e@macports.org> References: <042.8c0aba0378d281d075c02dee4fd8e96e@macports.org> Message-ID: <057.f2d1a4b2134d82453a9aeb59c4521791@macports.org> #53054: vcsn @2.2: update to 2.4 ---------------------+--------------------------------- Reporter: akimd | Owner: larryv Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch maintainer Port: vcsn | ---------------------+--------------------------------- Changes (by akimd): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"d8ee4be238b29d2927f17275707e86abc5c9828d/macports-ports" d8ee4be2/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="d8ee4be238b29d2927f17275707e86abc5c9828d" vcsn: Update to 2.4, switch to Python 3.5 Closes: https://trac.macports.org/ticket/53054 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 00:03:34 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 00:03:34 -0000 Subject: [MacPorts] #53055: ffmpeg: Undefined symbols from libavcodec "_xvid_plugin_2pass2" "_xvid_plugin_single" In-Reply-To: <048.1858e3aec017963dbaa47013a433d4c6@macports.org> References: <048.1858e3aec017963dbaa47013a433d4c6@macports.org> Message-ID: <063.645ea7225611ccbf41121ea761fe0f0a@macports.org> #53055: ffmpeg: Undefined symbols from libavcodec "_xvid_plugin_2pass2" "_xvid_plugin_single" --------------------------+---------------------- Reporter: platipodium | Owner: dbevans Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ffmpeg | --------------------------+---------------------- Comment (by dbevans): Great! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 00:04:07 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 00:04:07 -0000 Subject: [MacPorts] #53055: ffmpeg: Undefined symbols from libavcodec "_xvid_plugin_2pass2" "_xvid_plugin_single" In-Reply-To: <048.1858e3aec017963dbaa47013a433d4c6@macports.org> References: <048.1858e3aec017963dbaa47013a433d4c6@macports.org> Message-ID: <063.be0920eb88dfd8171cb62d4ccf93720c@macports.org> #53055: ffmpeg: Undefined symbols from libavcodec "_xvid_plugin_2pass2" "_xvid_plugin_single" --------------------------+--------------------- Reporter: platipodium | Owner: dbevans Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: worksforme | Keywords: Port: ffmpeg | --------------------------+--------------------- Changes (by dbevans): * status: accepted => closed * resolution: => worksforme -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 00:05:56 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 00:05:56 -0000 Subject: [MacPorts] #53059: Octave audio upgrade problems Message-ID: <050.a1ae3ff9782c98acde09c42ac011f456@macports.org> #53059: Octave audio upgrade problems ----------------------------------+----------------- Reporter: gjolleyrogers | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: octave audio upgrade | Port: ----------------------------------+----------------- Hi, I'm having problems with upgrading octave-audio. I've tried cleaning and uninstalling but the problems still persist. sudo port install octave-audio ---> Computing dependencies for octave-audio ---> Verifying checksums for octave-audio Error: No checksum set for patch-objcflags.diff Error: No checksum set for audio-1.1.4.tar.gz Error: org.macports.checksum for port octave-audio returned: Unable to verify file checksums Please see the log file for port octave-audio for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_math_octave-audio/octave-audio/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port octave-audio failed Here's the relevant extract from the logs OS X 10.11.6 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 00:13:52 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 00:13:52 -0000 Subject: [MacPorts] #51413: submission: phonon-backend-vlc with qt5 subport In-Reply-To: <041.002960c4ae3a6932302f53c42fdff330@macports.org> References: <041.002960c4ae3a6932302f53c42fdff330@macports.org> Message-ID: <056.55bed69ed262db8a90423cc20b9140b7@macports.org> #51413: submission: phonon-backend-vlc with qt5 subport -------------------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: phonon-backend-vlc-qt5 | -------------------------------------+---------------------- Changes (by mkae): * owner: macports-tickets@… => mkae * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 00:14:39 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 00:14:39 -0000 Subject: [MacPorts] #51413: submission: phonon-backend-vlc with qt5 subport In-Reply-To: <041.002960c4ae3a6932302f53c42fdff330@macports.org> References: <041.002960c4ae3a6932302f53c42fdff330@macports.org> Message-ID: <056.40edf3de8c0ddadba7e8a057c79236c1@macports.org> #51413: submission: phonon-backend-vlc with qt5 subport -------------------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: phonon-backend-vlc-qt5 | -------------------------------------+---------------------- Changes (by mkae): * cc: mkae (removed) * version: 2.3.4 => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 01:05:41 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 01:05:41 -0000 Subject: [MacPorts] #50709: port:opencv+qt4 uses Qt5 if both Qt4 and Qt5 are installed In-Reply-To: <041.0390807f10d7b4b56073a3a7b88f24df@macports.org> References: <041.0390807f10d7b4b56073a3a7b88f24df@macports.org> Message-ID: <056.4370d7aa5ded059bf49a29fbcbbc21d8@macports.org> #50709: port:opencv+qt4 uses Qt5 if both Qt4 and Qt5 are installed ---------------------+---------------------- Reporter: RJVB | Owner: stromnov Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: opencv | ---------------------+---------------------- Changes (by mkae): * status: new => closed * version: 2.3.4 => * resolution: => fixed Comment: This should be closed, as {{{opencv}}} has progressed in the meantime. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 01:06:50 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 01:06:50 -0000 Subject: [MacPorts] #50747: Kdenlive In-Reply-To: <064.0c3705a8377cc14787e8f769f9a3d3de@macports.org> References: <064.0c3705a8377cc14787e8f769f9a3d3de@macports.org> Message-ID: <079.2519e0b36daf1a057c0b0cb45e22eed5@macports.org> #50747: Kdenlive -------------------------+------------------------ Reporter: andy@… | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: worksforme | Keywords: Port: expat | -------------------------+------------------------ Changes (by mkae): * status: new => closed * resolution: => worksforme Comment: Guess this can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 01:06:56 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 01:06:56 -0000 Subject: [MacPorts] #50747: Kdenlive In-Reply-To: <064.0c3705a8377cc14787e8f769f9a3d3de@macports.org> References: <064.0c3705a8377cc14787e8f769f9a3d3de@macports.org> Message-ID: <079.5d485f8361d4cab3b390a18171dec6f9@macports.org> #50747: Kdenlive -------------------------+------------------------ Reporter: andy@… | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: worksforme | Keywords: Port: expat | -------------------------+------------------------ Changes (by mkae): * version: 2.3.4 => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 01:09:00 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 01:09:00 -0000 Subject: [MacPorts] #52703: git: git-gui crashing In-Reply-To: <041.41563308f2c85adc3d982e5601a537ca@macports.org> References: <041.41563308f2c85adc3d982e5601a537ca@macports.org> Message-ID: <056.84e8ed14dab571ed5044a9b300cda1f1@macports.org> #52703: git: git-gui crashing ---------------------+-------------------- Reporter: mkae | Owner: ci42 Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: sierra Port: git | ---------------------+-------------------- Comment (by mkae): This seems a bit hackish... @ci42, is that the way to go for MacPorts? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 01:25:22 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 01:25:22 -0000 Subject: [MacPorts] #52716: trac: link under MacPorts logo should lead to www.macports.org In-Reply-To: <041.d9cc5f4299d75d667f2e8e52d5fafd93@macports.org> References: <041.d9cc5f4299d75d667f2e8e52d5fafd93@macports.org> Message-ID: <056.daaad4646b7de0235c7b7356a9002d35@macports.org> #52716: trac: link under MacPorts logo should lead to www.macports.org -----------------------------+--------------------- Reporter: mkae | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+--------------------- Comment (by mkae): Replying to [comment:3 ryandesign]: > It won't be confusing when there is a unified header/footer on all MacPorts sites that behaves the same on every site. +1 In my mind I do connect the MacPorts logo with MacPorts' main page... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 01:27:34 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 01:27:34 -0000 Subject: [MacPorts] #45625: QtCurve 1.8.18_0 fails to build on Snow Leopard In-Reply-To: <041.3e3132822d94e64ae60d8c66c17d2123@macports.org> References: <041.3e3132822d94e64ae60d8c66c17d2123@macports.org> Message-ID: <056.6a48e6acfe74f9d99cb5a105e5d7883c@macports.org> #45625: QtCurve 1.8.18_0 fails to build on Snow Leopard -------------------------+-------------------- Reporter: mkae | Owner: RJVB Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: worksforme | Keywords: Port: qtcurve | -------------------------+-------------------- Changes (by mkae): * status: new => closed * resolution: => worksforme -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 01:42:57 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 01:42:57 -0000 Subject: [MacPorts] #46558: phonon-backend-gstreamer update to 4.8.2 and qt5 support In-Reply-To: <041.71a41150aa5e01a45a493a76643c7c35@macports.org> References: <041.71a41150aa5e01a45a493a76643c7c35@macports.org> Message-ID: <056.3782e2a6966eba751b8408cc2bf22115@macports.org> #46558: phonon-backend-gstreamer update to 4.8.2 and qt5 support ---------------------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: phonon-backend-gstreamer | ---------------------------------------+---------------------- Changes (by mkae): * cc: michaelld (added) * owner: michaelld => mkae * status: new => assigned Comment: I guess I can take over. Assigning it to myself now, please revert, @michaelld, if you feel like it, otherwise I'll take of this in the near future. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 01:46:54 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 01:46:54 -0000 Subject: [MacPorts] #46558: phonon-backend-gstreamer update to 4.8.2 and qt5 support In-Reply-To: <041.71a41150aa5e01a45a493a76643c7c35@macports.org> References: <041.71a41150aa5e01a45a493a76643c7c35@macports.org> Message-ID: <056.94d910c401f3f3b87906b4f009e6ac23@macports.org> #46558: phonon-backend-gstreamer update to 4.8.2 and qt5 support ---------------------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: phonon-backend-gstreamer | ---------------------------------------+---------------------- Comment (by michaelld): You're on a roll .. don't let me stop you! I have way too many other things requiring my attention right now; I'm just barely able to keep up with my "usual" MacPorts work ... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 02:36:38 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 02:36:38 -0000 Subject: [MacPorts] #53017: kerberos5 fails to build on Yosemite with libressl In-Reply-To: <045.2e6d5c80e4930d3d8f0c88d93b24a25b@macports.org> References: <045.2e6d5c80e4930d3d8f0c88d93b24a25b@macports.org> Message-ID: <060.8b76b96c3fc6cb01f749d06265378e89@macports.org> #53017: kerberos5 fails to build on Yosemite with libressl ------------------------+------------------------ Reporter: bK4gYuRo | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: kerberos5 | ------------------------+------------------------ Comment (by jerryyhom): Kerberos5 1.15 updated their support for OpenSSL 1.1, which renamed some API's. Hence, building with LibreSSL will fail. The same problem results in a partial build error for ntp 4.2.8p9. Does LibreSSL have plans to be API compatible with OpenSSL 1.1? Otherwise, the SSL ports are problematic for port dependencies. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 03:55:50 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 03:55:50 -0000 Subject: [MacPorts] #46558: phonon-backend-gstreamer update to 4.8.2 and qt5 support In-Reply-To: <041.71a41150aa5e01a45a493a76643c7c35@macports.org> References: <041.71a41150aa5e01a45a493a76643c7c35@macports.org> Message-ID: <056.9e69e5c1359a3148520464ca873bd4b7@macports.org> #46558: phonon-backend-gstreamer update to 4.8.2 and qt5 support ---------------------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: phonon-backend-gstreamer | ---------------------------------------+---------------------- Changes (by mkae): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"47c0c4f682b22803ae250258187544187d50f898/macports-ports" 47c0c4f/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="47c0c4f682b22803ae250258187544187d50f898" phonon-backend-gstreamer(-qt5): update to 4.9.0 and introduce new subport Squash commit: commit 5084c0bb0f4edef8ad380910182fad25a5c203f8 Author: Marko Käning Date: Tue Dec 13 04:51:38 2016 +0100 phonon-backend-gstreamer-qt5: michaelld drops maintainership commit 848cd25de1d3fa80eab96d6b5aa4d7deb9cb513f Author: Marko Käning Date: Tue Dec 13 04:47:21 2016 +0100 phonon-backend-gstreamer(-qt5): master_sites's folder changed for 4.9.0 commit 909946083acb91e66b8d88a489773ba066e6954e Author: Marko Käning Date: Tue Dec 13 04:31:20 2016 +0100 phonon-backend-gstreamer: update to 4.9.0 - avoiding building the X11 renderer has changed => new patch - remove unused patches commit ccaa0e34a4aa2fafc8276a6fb8d86fa8af7398a2 Author: Marko Käning Date: Tue Dec 13 03:09:55 2016 +0100 phonon-backend-gstreamer: introduce qt5 support - add co-maintainership for RJVB Closes: https://trac.macports.org/ticket/46558 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 04:33:21 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 04:33:21 -0000 Subject: [MacPorts] #53059: octave-audio @1.1.4: patchfile patch-objcflags.diff is missing (was: Octave audio upgrade problems) In-Reply-To: <050.a1ae3ff9782c98acde09c42ac011f456@macports.org> References: <050.a1ae3ff9782c98acde09c42ac011f456@macports.org> Message-ID: <065.4bdab84c980cf88d94d7d7b89337cb91@macports.org> #53059: octave-audio @1.1.4: patchfile patch-objcflags.diff is missing ----------------------------+--------------------------------- Reporter: gjolleyrogers | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: octave-audio | ----------------------------+--------------------------------- Changes (by ryandesign): * status: new => assigned * keywords: octave audio upgrade => * owner: => MarcusCalhoun-Lopez * port: => octave-audio Old description: > Hi, > I'm having problems with upgrading octave-audio. I've tried cleaning and > uninstalling but the problems still persist. > > sudo port install octave-audio > ---> Computing dependencies for octave-audio > ---> Verifying checksums for octave-audio > Error: No checksum set for patch-objcflags.diff > Error: No checksum set for audio-1.1.4.tar.gz > Error: org.macports.checksum for port octave-audio returned: Unable to > verify file checksums > Please see the log file for port octave-audio for details: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports > .org_release_tarballs_ports_math_octave-audio/octave-audio/main.log > To report a bug, follow the instructions in the guide: > http://guide.macports.org/#project.tickets > Error: Processing of port octave-audio failed > > Here's the relevant extract from the logs > > OS X 10.11.6 New description: Hi, I'm having problems with upgrading octave-audio. I've tried cleaning and uninstalling but the problems still persist. {{{ sudo port install octave-audio ---> Computing dependencies for octave-audio ---> Verifying checksums for octave-audio Error: No checksum set for patch-objcflags.diff Error: No checksum set for audio-1.1.4.tar.gz Error: org.macports.checksum for port octave-audio returned: Unable to verify file checksums Please see the log file for port octave-audio for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_math_octave-audio/octave-audio/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port octave-audio failed }}} Here's the relevant extract from the logs OS X 10.11.6 -- Comment: The real problem is that the patch-objcflags.diff patchfile was not committed when a reference to it was added to the portfile in changeset:5c63c9706d260f6a6557b110bb7608f0d92287bf/macports-ports. I'm not sure why this problem was bypassed on your system to arrive at a different problem. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 05:11:16 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 05:11:16 -0000 Subject: [MacPorts] #53058: nsis @3.0.1: build fails on 10.6 due to a missing zlib (was: nsis: build fails on 10.6 due to a missing zlib) In-Reply-To: <042.90088184fe2b9c0226a378ef5f8f62d8@macports.org> References: <042.90088184fe2b9c0226a378ef5f8f62d8@macports.org> Message-ID: <057.470406b53f00cdc9f816ab58eeaf4232@macports.org> #53058: nsis @3.0.1: build fails on 10.6 due to a missing zlib ---------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: nsis | ---------------------+------------------------- Comment (by ryandesign): I've reported it to the developers: https://sourceforge.net/p/nsis/bugs/1169/ -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 06:40:06 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 06:40:06 -0000 Subject: [MacPorts] #51411: mlt: qt5 subport In-Reply-To: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> References: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> Message-ID: <056.63ce6164c6f140e5be99cd31b9514978@macports.org> #51411: mlt: qt5 subport --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: mlt | --------------------------+---------------------- Changes (by mkae): * cc: dan@… (added) * owner: dan@… => mkae * status: new => accepted Comment: I am picking this up, since I hope to be forced to have to use this with Qt5. If you're not happy with this, simply revert this! I'll file a PR if needed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 06:41:55 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 06:41:55 -0000 Subject: [MacPorts] #51411: mlt: qt5 subport In-Reply-To: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> References: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> Message-ID: <056.373fe0d5c4bc6de7a4e5bff541eb310b@macports.org> #51411: mlt: qt5 subport --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: mlt | --------------------------+---------------------- Comment (by mkae): Dan, would you be fine with co-maintainership and also allowing openmaintainer for this port? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 06:44:41 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 06:44:41 -0000 Subject: [MacPorts] #52951: wxWidgets-3.2 does not build In-Reply-To: <045.5ccbbc3b9cc1ea7e021e5dbb885d68cb@macports.org> References: <045.5ccbbc3b9cc1ea7e021e5dbb885d68cb@macports.org> Message-ID: <060.eb7f9b4030e1e24c73690f165d731661@macports.org> #52951: wxWidgets-3.2 does not build ----------------------------+-------------------- Reporter: rkitover | Owner: mojca Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: sierra Port: wxWidgets-3.2 | ----------------------------+-------------------- Changes (by mojca): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"40745aba497c4c5c4dedf1d3a8ea9d5012a9d4f0/macports-ports" 40745aba/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="40745aba497c4c5c4dedf1d3a8ea9d5012a9d4f0" wxWidgets-3.2: upgrade to commit 159186d from git * Use commit 159186d (2016-12-12) from master to add support for newer platforms without extensive patching. * Remove two patches from upstream. Closes: https://trac.macports.org/ticket/52951 See: https://github.com/wxWidgets/wxWidgets/pull/370 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 06:46:39 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 06:46:39 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.21a4a41a511c75135a5f198242bd367e@macports.org> #51619: qt5.depends_component procedure ---------------------------+-------------------------------- Reporter: RJVB | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+-------------------------------- Comment (by mkae): What's the status of this? René, did you discuss this already on the dev- ML? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 06:47:06 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 06:47:06 -0000 Subject: [MacPorts] #50968: playground : qt5-kde-devel @ Qt 5.6.1 In-Reply-To: <041.d5a5ffc300e2fa6caaaf0d7b722c86f6@macports.org> References: <041.d5a5ffc300e2fa6caaaf0d7b722c86f6@macports.org> Message-ID: <056.988fa5e17e0f41567e6aaddf52134cf2@macports.org> #50968: playground : qt5-kde-devel @ Qt 5.6.1 ----------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5-kde-devel | ----------------------------+---------------------- Changes (by mkae): * owner: macports-tickets@… => mkae * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 06:47:18 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 06:47:18 -0000 Subject: [MacPorts] #50966: Qt5 PortGroup files; preparing for port:qt5-kde and the KF5 port family In-Reply-To: <041.1cf77e697e16112454e887b8e62c5844@macports.org> References: <041.1cf77e697e16112454e887b8e62c5844@macports.org> Message-ID: <056.bf1cf314b1d4a311a68d6162cd58d10c@macports.org> #50966: Qt5 PortGroup files; preparing for port:qt5-kde and the KF5 port family ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Changes (by mkae): * owner: macports-tickets@… => mkae * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 06:47:58 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 06:47:58 -0000 Subject: [MacPorts] #50183: QtCurve ports: updates for Qt5 and KF5 In-Reply-To: <041.1d3879e4368a36421063153a3f91099b@macports.org> References: <041.1d3879e4368a36421063153a3f91099b@macports.org> Message-ID: <056.da171f9a7653207c491049a00564a7aa@macports.org> #50183: QtCurve ports: updates for Qt5 and KF5 ----------------------+---------------------- Reporter: RJVB | Owner: mkae Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch Port: QtCurve | ----------------------+---------------------- Changes (by mkae): * status: new => accepted * owner: macports-tickets@… => mkae -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 06:48:28 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 06:48:28 -0000 Subject: [MacPorts] #50183: QtCurve ports: updates for Qt5 and KF5 In-Reply-To: <041.1d3879e4368a36421063153a3f91099b@macports.org> References: <041.1d3879e4368a36421063153a3f91099b@macports.org> Message-ID: <056.63cc369833e39c10a137b13751d0cbd5@macports.org> #50183: QtCurve ports: updates for Qt5 and KF5 ----------------------+---------------------- Reporter: RJVB | Owner: mkae Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: qtcurve | ----------------------+---------------------- Changes (by mkae): * status: accepted => closed * version: 2.3.4 => * resolution: => fixed * port: QtCurve => qtcurve Comment: This should be all fine by now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 06:48:53 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 06:48:53 -0000 Subject: [MacPorts] #51411: mlt: qt5 subport In-Reply-To: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> References: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> Message-ID: <056.34f1e49731f63c9c235c53a67a0ea4aa@macports.org> #51411: mlt: qt5 subport --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: mlt | --------------------------+---------------------- Comment (by ddennedy): Yes, I agree with this. I appreciate the help. Especially, I doubt I could have come up with the changes in mlt.4.diff - much appreciated! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 06:49:24 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 06:49:24 -0000 Subject: [MacPorts] #49780: provide an interface for ports to depend on Qt5 components In-Reply-To: <041.04d62d1e22ef2830cb4b76433d93e873@macports.org> References: <041.04d62d1e22ef2830cb4b76433d93e873@macports.org> Message-ID: <056.0336664d92ca5c4defb69af80f7d600d@macports.org> #49780: provide an interface for ports to depend on Qt5 components --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5 qt5-kde | --------------------------+---------------------- Changes (by mkae): * owner: macports-tickets@… => mkae * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 06:50:09 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 06:50:09 -0000 Subject: [MacPorts] #49780: provide an interface for ports to depend on Qt5 components In-Reply-To: <041.04d62d1e22ef2830cb4b76433d93e873@macports.org> References: <041.04d62d1e22ef2830cb4b76433d93e873@macports.org> Message-ID: <056.5e898f828b67c831e8ea9bf9d555103a@macports.org> #49780: provide an interface for ports to depend on Qt5 components --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5 qt5-kde | --------------------------+---------------------- Comment (by mkae): What exactly is the status of this? I guess it's all part of {{{qt5-kde(-devel)}}} these days, no!? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 06:50:49 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 06:50:49 -0000 Subject: [MacPorts] #49721: qt5: some programs' tests try to delete /Applications In-Reply-To: <041.67e56b91ca1d608ba21eda1fca8b3ee4@macports.org> References: <041.67e56b91ca1d608ba21eda1fca8b3ee4@macports.org> Message-ID: <056.b073166bb87843fd23157e71ca631b11@macports.org> #49721: qt5: some programs' tests try to delete /Applications ---------------------+--------------------------------- Reporter: RJVB | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5 | ---------------------+--------------------------------- Comment (by mkae): How to proceed with this, guys? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 06:51:10 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 06:51:10 -0000 Subject: [MacPorts] #49109: port modifications required by making qt4-mac co-installable with Qt5 In-Reply-To: <041.ed916633811460a610cbd879f97870ef@macports.org> References: <041.ed916633811460a610cbd879f97870ef@macports.org> Message-ID: <056.c9f7da7519a55ca315700c2a0f5be838@macports.org> #49109: port modifications required by making qt4-mac co-installable with Qt5 --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: | --------------------------+---------------------- Changes (by mkae): * owner: macports-tickets@… => mkae * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 06:53:07 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 06:53:07 -0000 Subject: [MacPorts] #49109: port modifications required by making qt4-mac co-installable with Qt5 In-Reply-To: <041.ed916633811460a610cbd879f97870ef@macports.org> References: <041.ed916633811460a610cbd879f97870ef@macports.org> Message-ID: <056.d06b66e0ebabbc257043da3fda603d03@macports.org> #49109: port modifications required by making qt4-mac co-installable with Qt5 --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: | --------------------------+---------------------- Comment (by mkae): Parts of this, René, should now be committed. Can you cross-check what we're still missing in MacPorts' central repo? (Surely the python modules. Not sure about the attica patch... No time to check now.) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 06:53:37 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 06:53:37 -0000 Subject: [MacPorts] #48296: qt5-mac @5.4.2_1 staging into ${prefix}/libexec/qt5-mac In-Reply-To: <058.6eb383c8eff0c062b8e5f0834cea5b5e@macports.org> References: <058.6eb383c8eff0c062b8e5f0834cea5b5e@macports.org> Message-ID: <073.1482b291ce3bd626a96fb0df5f4a8d66@macports.org> #48296: qt5-mac @5.4.2_1 staging into ${prefix}/libexec/qt5-mac ----------------------------+--------------------------------- Reporter: l.digaspero@… | Owner: MarcusCalhoun-Lopez Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: qt5-mac | ----------------------------+--------------------------------- Comment (by mkae): What's the status of this, actually? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 06:55:41 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 06:55:41 -0000 Subject: [MacPorts] #51411: mlt: qt5 subport In-Reply-To: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> References: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> Message-ID: <056.4e026691878e86112971543e16df678b@macports.org> #51411: mlt: qt5 subport --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: mlt | --------------------------+---------------------- Changes (by mkae): * status: accepted => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 06:57:43 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 06:57:43 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.d0e210efc4a3a096f4a87e7b3e9412f5@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Changes (by mkae): * owner: macports-tickets@… => mkae * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 06:58:18 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 06:58:18 -0000 Subject: [MacPorts] #51411: mlt: qt5 subport In-Reply-To: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> References: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> Message-ID: <056.dbfd17d2c13431f4a8e9fb1576059395@macports.org> #51411: mlt: qt5 subport --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: mlt | --------------------------+---------------------- Changes (by mkae): * cc: mkae (removed) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 06:59:53 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 06:59:53 -0000 Subject: [MacPorts] #51454: py35-spyder-devel @3.0.0b2 +qt5 won't load after update to Qt5.6 In-Reply-To: <060.dd5b3e8df72a7af79c6c968974e8fa2e@macports.org> References: <060.dd5b3e8df72a7af79c6c968974e8fa2e@macports.org> Message-ID: <075.4ec794cc2c845894d98dd91f30ee22e6@macports.org> #51454: py35-spyder-devel @3.0.0b2 +qt5 won't load after update to Qt5.6 ------------------------------+------------------------ Reporter: r.williams.06@… | Owner: eborisch@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: py-spyder-devel | ------------------------------+------------------------ Comment (by mkae): Hi @eborisch, I saw that upstream has fixed this. Can you integrate it on MacPorts? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 07:01:43 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 07:01:43 -0000 Subject: [MacPorts] #50968: playground : qt5-kde-devel @ Qt 5.6.1 In-Reply-To: <041.d5a5ffc300e2fa6caaaf0d7b722c86f6@macports.org> References: <041.d5a5ffc300e2fa6caaaf0d7b722c86f6@macports.org> Message-ID: <056.a7ab2d1d9cb131be7d6218213b4d478d@macports.org> #50968: playground : qt5-kde-devel @ Qt 5.6.1 ----------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5-kde-devel | ----------------------------+---------------------- Changes (by mkae): * cc: mkae (removed) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 07:01:59 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 07:01:59 -0000 Subject: [MacPorts] #50966: Qt5 PortGroup files; preparing for port:qt5-kde and the KF5 port family In-Reply-To: <041.1cf77e697e16112454e887b8e62c5844@macports.org> References: <041.1cf77e697e16112454e887b8e62c5844@macports.org> Message-ID: <056.8001c7bf6d21e2048f29ae100d185cde@macports.org> #50966: Qt5 PortGroup files; preparing for port:qt5-kde and the KF5 port family ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Changes (by mkae): * cc: mkae (removed) * version: 2.3.4 => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 07:02:31 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 07:02:31 -0000 Subject: [MacPorts] #49780: provide an interface for ports to depend on Qt5 components In-Reply-To: <041.04d62d1e22ef2830cb4b76433d93e873@macports.org> References: <041.04d62d1e22ef2830cb4b76433d93e873@macports.org> Message-ID: <056.11ba83a4373745c67c5202f93eea8f3a@macports.org> #49780: provide an interface for ports to depend on Qt5 components --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5 qt5-kde | --------------------------+---------------------- Changes (by mkae): * cc: mkae (removed) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 07:04:06 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 07:04:06 -0000 Subject: [MacPorts] #48088: proposed improvements to port:qt5-mac In-Reply-To: <041.e0858a4b637f82763860a44ea17b9fe4@macports.org> References: <041.e0858a4b637f82763860a44ea17b9fe4@macports.org> Message-ID: <056.43e222f949b31434be6caf0b3211ef93@macports.org> #48088: proposed improvements to port:qt5-mac --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5-mac | --------------------------+---------------------- Changes (by mkae): * cc: mkae (removed) * owner: macports-tickets@… => mkae * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 07:04:31 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 07:04:31 -0000 Subject: [MacPorts] #47047: new (meta)port submission: qt5-mac-mysql-plugins In-Reply-To: <041.b229f7eb575b63488a96fbbc73638db2@macports.org> References: <041.b229f7eb575b63488a96fbbc73638db2@macports.org> Message-ID: <056.0d3fb5b136b72f706a10e03c4e17ca04@macports.org> #47047: new (meta)port submission: qt5-mac-mysql-plugins ------------------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: qt5-mac-mysql-plugins | ------------------------------------+---------------------- Changes (by mkae): * cc: mkae (removed) * owner: macports-tickets@… => mkae * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 07:04:59 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 07:04:59 -0000 Subject: [MacPorts] #46536: qt5-mac-devel submission: provides Qt 5.4.x In-Reply-To: <041.0494a95d3cc841884ff13f5714458f8e@macports.org> References: <041.0494a95d3cc841884ff13f5714458f8e@macports.org> Message-ID: <056.e825b8d439413b8b0aef8d6ef4b8ec66@macports.org> #46536: qt5-mac-devel submission: provides Qt 5.4.x ----------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5-mac-devel | ----------------------------+---------------------- Changes (by mkae): * owner: macports-tickets@… => mkae * status: new => assigned * cc: mkae (removed) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 07:05:21 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 07:05:21 -0000 Subject: [MacPorts] #46496: co-installable qt4-mac and qt5-mac step2 : qt5-mac In-Reply-To: <041.873ee2a825d3590ea03ad935ff67433c@macports.org> References: <041.873ee2a825d3590ea03ad935ff67433c@macports.org> Message-ID: <056.1d91cf9bb3502e715d04c8d44b091c27@macports.org> #46496: co-installable qt4-mac and qt5-mac step2 : qt5-mac --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: qt5-mac | --------------------------+---------------------- Changes (by mkae): * status: new => assigned * cc: mkae (removed) * version: 2.3.3 => * owner: macports-tickets@… => mkae -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 07:07:10 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 07:07:10 -0000 Subject: [MacPorts] #48024: charm-qt5 @1.8.0_20150312: cannot evaluate portfile In-Reply-To: <043.45a44fa2fadee95e9a87c1212e7e56bf@macports.org> References: <043.45a44fa2fadee95e9a87c1212e7e56bf@macports.org> Message-ID: <058.d7da3ea77e6673e2657684fd3ade4fa5@macports.org> #48024: charm-qt5 @1.8.0_20150312: cannot evaluate portfile ------------------------+---------------------- Reporter: larryv | Owner: mkae Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: charm-qt5 | ------------------------+---------------------- Changes (by mkae): * cc: mkae (removed) * cc: RJVB (added) * owner: RJVB => mkae * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 07:08:28 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 07:08:28 -0000 Subject: [MacPorts] #51620: py-pyqt5: fix DBus module build and pyversion conflicts, support multiple Qt5 ports In-Reply-To: <041.878bbad1021a18186c191e6780e8baed@macports.org> References: <041.878bbad1021a18186c191e6780e8baed@macports.org> Message-ID: <056.0ddacd5412789194457cb774861de0f4@macports.org> #51620: py-pyqt5: fix DBus module build and pyversion conflicts, support multiple Qt5 ports --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-pyqt5 | --------------------------+---------------------- Changes (by mkae): * owner: macports-tickets@… => mkae * status: new => assigned * cc: mkae (removed) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 07:08:43 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 07:08:43 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.aa91f7a39fa7dfe222f707a0ac6f37ac@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Changes (by mkae): * cc: mkae (removed) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 07:09:47 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 07:09:47 -0000 Subject: [MacPorts] #49577: polkit-qt version update and qt5 subport In-Reply-To: <041.10c457beacec7a8439cb3cbbfa864b31@macports.org> References: <041.10c457beacec7a8439cb3cbbfa864b31@macports.org> Message-ID: <056.7dfb1935469ccf17cbc95a10dafcd3b1@macports.org> #49577: polkit-qt version update and qt5 subport ------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: polkit-qt | ------------------------+---------------------- Changes (by mkae): * cc: mkae (removed) * owner: macports-tickets@… => mkae * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 07:10:07 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 07:10:07 -0000 Subject: [MacPorts] #49109: port modifications required by making qt4-mac co-installable with Qt5 In-Reply-To: <041.ed916633811460a610cbd879f97870ef@macports.org> References: <041.ed916633811460a610cbd879f97870ef@macports.org> Message-ID: <056.e25fcff6d9d07f353ce1f4c11fe981ec@macports.org> #49109: port modifications required by making qt4-mac co-installable with Qt5 --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: | --------------------------+---------------------- Changes (by mkae): * cc: mkae (removed) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 07:13:41 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 07:13:41 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.3c5e359b1d59eaa3fc39599cae3e048e@macports.org> #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++ ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Changes (by mojca): * cc: cjones051073 (added) Comment: I'm adding Chris to this ticket. Chris, given your broad experience with the nasty ROOT6 dependencies, would you be willing to give a helping hand also to octave? The following patch works for me (that is: octave compiles, but the patch is far from being ready to commit): {{{ #!diff @@ -13,6 +13,7 @@ PortGroup linear_algebra 1.0 # See https://trac.macports.org/ticket/53044 for restricting clang versions further PortGroup compiler_blacklist_versions 1.0 compiler.blacklist-append {*gcc-3*} {*gcc-4.[0-6]} {clang < 700} cc +configure.cxx_stdlib libc++ name octave version 4.2.0 @@ -515,6 +516,9 @@ default_variants-append +docs # "Magick::Image::ping(std::__cxx11::basic_string, std::allocator > const&)" set magickConflict {} set magickDefault yes +if {${cxx_stdlib} ne "libc++"} { + set magickDefault no +} if {${configure.cxx_stdlib} ne "libstdc++"} { foreach gccVar ${compilers.gcc_variants} { if {[variant_exists ${gccVar}] } { @@ -534,16 +538,6 @@ if {${magickDefault}} { default_variants-append +graphicsmagick } -if { [variant_isset graphicsmagick] && ${configure.cxx_stdlib} eq "libstdc++"} { - compiler.blacklist-append {macports-clang-*} - compiler.whitelist-append \ - macports-gcc-6 \ - macports-gcc-5 \ - macports-gcc-4.9 \ - macports-gcc-4.8 \ - macports-gcc-4.7 -} - post-destroot { # put any startup commands in ${destroot}${prefix}/share/octave/${version}/m/startup/octaverc # see https://www.gnu.org/software/octave/doc/interpreter/Startup- Files.html }}} Note that `configure.cxx_stdlib libc++` should only be added when building with clang, maybe something like {{{ if {[string match *clang* ${configure.cxx}]} { configure.cxx_stdlib libc++ } }}} even though I'm not absolutely sure how this interacts with the rest of the variants and I'm not sure about the order of execution. I'm not 100% sure about the following, but I hope that {{{ #!tcl if {${cxx_stdlib} ne "libc++"} }}} checks for global setting of `cxx_stdlib`. If it is set to `libc++`, then it should be safe to build with graphicsmagick as graphicsmagic should be built against `libc++` as well and should be safe to use. If default is `libstdc++`, then the user could build either with gcc or with clang, but not against graphicsmagic in any case. I would probably do it in an even more drastic way: {{{ #!tcl if {${cxx_stdlib} eq "libc++"} { eval "variant graphicsmagick description {use GraphicsMagick for image I/O} conflicts ${magickConflict} { depends_lib-append port:GraphicsMagick configure.args-replace --without-magick --with- magick=GraphicsMagick }" } }}} That is: don't even add the variant if there is no way for the user to build it. Note that the following part of code will be slightly problematic: {{{ #!tcl if {${configure.cxx_stdlib} ne "libstdc++"} { }}} because the port will always set `libc++` for clang. Another problem is that whenever a compiler is picked up automatically (in my case that would be `macports-clang-3.8`), you don't activate a variant for it. Oh, wait ... I just tried to run `octave` now to test it and I get a GUI instead of the command line? Is this something new from version 4.2 or is that because I disabled graphicmagic? I like the GUI of course, but what's the trick to force it to stay in the Terminal? And the GUI is stalled at exit. I have to force quit it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 07:18:51 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 07:18:51 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 (was: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++) In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.ce752e86fd9c46d70e8187fc90a2d029@macports.org> #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 07:39:22 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 07:39:22 -0000 Subject: [MacPorts] #53058: nsis @3.0.1: build fails on 10.6 due to a missing zlib In-Reply-To: <042.90088184fe2b9c0226a378ef5f8f62d8@macports.org> References: <042.90088184fe2b9c0226a378ef5f8f62d8@macports.org> Message-ID: <057.78f029aac062e63ec0062ebda8cce16c@macports.org> #53058: nsis @3.0.1: build fails on 10.6 due to a missing zlib ---------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: nsis | ---------------------+------------------------- Changes (by mojca): * cc: ryandesign (added) Comment: Ryan, this might just as well be due to the wrong compiler or wrong flags (I guess we should not add `-stdlib=...` when not using clang for example). I tested it now and if I switch to macports-clang-3.4, then it works correctly. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 07:41:50 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 07:41:50 -0000 Subject: [MacPorts] #48800: gtest: please remove In-Reply-To: <047.9000c372c4b2abc640d29ce0ec79dc97@macports.org> References: <047.9000c372c4b2abc640d29ce0ec79dc97@macports.org> Message-ID: <062.853fe6138911a8de75ef66461542ec62@macports.org> #48800: gtest: please remove -------------------------+------------------- Reporter: ryandesign | Owner: blair Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gtest | -------------------------+------------------- Comment (by ryandesign): Blair, please remove the port as per my previous remarks. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 07:41:58 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 07:41:58 -0000 Subject: [MacPorts] #53058: nsis @3.0.1: build fails on 10.6 due to a missing zlib In-Reply-To: <042.90088184fe2b9c0226a378ef5f8f62d8@macports.org> References: <042.90088184fe2b9c0226a378ef5f8f62d8@macports.org> Message-ID: <057.48f7c5526ba3978286e9a868afc6455d@macports.org> #53058: nsis @3.0.1: build fails on 10.6 due to a missing zlib ---------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: nsis | ---------------------+------------------------- Comment (by mojca): And in fact when I remove the `-stdlib=...`, the port builds even with the default compiler. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 09:22:52 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 09:22:52 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.56b95b9ac4ea1e3f921c4ac14610c526@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by RJVB): Status? No idea TBH. The procedure itself probably evolved a bit since I created this ticket, which I haven't kept up to date for lack of activity on it. I did bring up the idea of using a wrapper around `depends_lib` to have a standard and above all clean way of declaring dependencies on Qt5 components that will work with both port:qt5 and port:qt5-kde (and port:qt5-kde-devel, for us if we never commit it) by hiding details like the appropriate path- style dependencies. I don't think there has been negative feedback. It would make sense to introduce this (and incite port maintainers to use it) even before we start the introduction process for port:qt5-kde . -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 09:31:35 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 09:31:35 -0000 Subject: [MacPorts] #51411: mlt: qt5 subport In-Reply-To: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> References: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> Message-ID: <056.b5b524cc6a13900dc6c67bf6a2021b02@macports.org> #51411: mlt: qt5 subport --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: mlt | --------------------------+---------------------- Comment (by RJVB): Replying to [comment:8 ddennedy]: > Yes, I agree with this. I appreciate the help. Especially, I doubt I could have come up with the changes in mlt.4.diff - much appreciated! You're very welcome and I appreciate the quick reaction! It would help us if you could test the new version on your end (even if you don't have Qt5 installed), and push it if it works for you. I don't think there's much point in waiting for the introduction of kf5-kdenlive, esp. not for a complex port like that one. Rather, we should allow users to start weaning off Qt4. I see I put myself first in the maintainer list which isn't very nice in retrospect and probably just a bit of force of habit. You can evidently keep principle maintainership... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 09:33:41 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 09:33:41 -0000 Subject: [MacPorts] #49780: provide an interface for ports to depend on Qt5 components In-Reply-To: <041.04d62d1e22ef2830cb4b76433d93e873@macports.org> References: <041.04d62d1e22ef2830cb4b76433d93e873@macports.org> Message-ID: <056.9e9aaa5388c8680482980be24f1cc5b6@macports.org> #49780: provide an interface for ports to depend on Qt5 components --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5 qt5-kde | --------------------------+---------------------- Comment (by RJVB): Yes, and see #51619 . -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 09:38:03 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 09:38:03 -0000 Subject: [MacPorts] #49721: qt5: some programs' tests try to delete /Applications In-Reply-To: <041.67e56b91ca1d608ba21eda1fca8b3ee4@macports.org> References: <041.67e56b91ca1d608ba21eda1fca8b3ee4@macports.org> Message-ID: <056.8ccc88e3d1a400c573cf342e341de220@macports.org> #49721: qt5: some programs' tests try to delete /Applications ---------------------+--------------------------------- Reporter: RJVB | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5 | ---------------------+--------------------------------- Comment (by RJVB): port:qt5-kde will fix this along with the other required modifications to QStandardPaths, and I made upstream aware of it via a bug report. There probably is little risk for regular Qt5 ports (how many include auto/unit tests anyway?) and I deactivate the test feature in the KF5 ports if they are built against port:qt5 instead of port:qt5-kde . -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 09:41:01 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 09:41:01 -0000 Subject: [MacPorts] #48296: qt5-mac @5.4.2_1 staging into ${prefix}/libexec/qt5-mac In-Reply-To: <058.6eb383c8eff0c062b8e5f0834cea5b5e@macports.org> References: <058.6eb383c8eff0c062b8e5f0834cea5b5e@macports.org> Message-ID: <073.19f544554ae40f8b9d1842b2a3a6f623@macports.org> #48296: qt5-mac @5.4.2_1 staging into ${prefix}/libexec/qt5-mac ----------------------------+--------------------------------- Reporter: l.digaspero@… | Owner: MarcusCalhoun-Lopez Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: qt5-mac | ----------------------------+--------------------------------- Comment (by RJVB): Status=obsolete. port:qt5 now installs to libexec/qt5, which made it a lot easier to make port:qt5-kde a drop-in replacement. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 10:23:55 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 10:23:55 -0000 Subject: [MacPorts] #51736: python35 @3.5.2_0 fails to build with macosx_deployment_target 10.7 In-Reply-To: <062.8c08a469789372292496c76e330ca0cd@macports.org> References: <062.8c08a469789372292496c76e330ca0cd@macports.org> Message-ID: <077.0543614b5231c058335fce01a81d9c9f@macports.org> #51736: python35 @3.5.2_0 fails to build with macosx_deployment_target 10.7 -----------------------------------------+---------------------------- Reporter: help@… | Owner: jyrkiwahlstedt Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: python34 python35 python36 | -----------------------------------------+---------------------------- Changes (by parafin): * Attachment "stack_size.patch" added. workaround -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 10:27:54 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 10:27:54 -0000 Subject: [MacPorts] #51736: python35 @3.5.2_0 fails to build with macosx_deployment_target 10.7 In-Reply-To: <062.8c08a469789372292496c76e330ca0cd@macports.org> References: <062.8c08a469789372292496c76e330ca0cd@macports.org> Message-ID: <077.752e38c5f1f3ad24bf3f4fae2205fc84@macports.org> #51736: python35 @3.5.2_0 fails to build with macosx_deployment_target 10.7 -----------------------------------------+---------------------------- Reporter: help@… | Owner: jyrkiwahlstedt Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: python34 python35 python36 | -----------------------------------------+---------------------------- Comment (by parafin): Looks like usage of -stack_size option when MACOSX_DEPLOYMENT_TARGET is set to 10.7 triggers a bug in linker. Just removing it helps, but I'm not sure of consequences (see comments above changed line in patch file). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 11:40:50 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 11:40:50 -0000 Subject: [MacPorts] #53059: octave-audio @1.1.4: patchfile patch-objcflags.diff is missing In-Reply-To: <050.a1ae3ff9782c98acde09c42ac011f456@macports.org> References: <050.a1ae3ff9782c98acde09c42ac011f456@macports.org> Message-ID: <065.81c0ce14acf1ea71549ef9bd40b786c9@macports.org> #53059: octave-audio @1.1.4: patchfile patch-objcflags.diff is missing ----------------------------+--------------------------------- Reporter: gjolleyrogers | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: octave-audio | ----------------------------+--------------------------------- Changes (by MarcusCalhoun-Lopez): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"299116b6810746d994aab836e54e4740a78e671d/macports-ports" 299116b6/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="299116b6810746d994aab836e54e4740a78e671d" octave-audio: add missing patchfile Fixes https://trac.macports.org/ticket/53059 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 12:05:59 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 12:05:59 -0000 Subject: [MacPorts] #53060: p5-perlmagick fetch failed, files missing from server Message-ID: <048.ba240fc1d79cfe36bf3172475e943def@macports.org> #53060: p5-perlmagick fetch failed, files missing from server -------------------------------------+------------------------------ Reporter: PBainbridge | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: perlmagick, imagemagick | Port: p5.24-perlmagick -------------------------------------+------------------------------ The file ImageMagick-6.9.6-6.tar.xz appears to be missing from the various mirrors and therefore fails to complete: ---> Computing dependencies for p5-perlmagick ---> Dependencies to be installed: p5.24-perlmagick ---> Fetching archive for p5.24-perlmagick ---> Attempting to fetch p5.24-perlmagick-6.9.6-6_0.darwin_10.x86_64.tbz2 from https://packages.macports.org/p5.24-perlmagick ---> Attempting to fetch p5.24-perlmagick-6.9.6-6_0.darwin_10.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/p5.24-perlmagick ---> Attempting to fetch p5.24-perlmagick-6.9.6-6_0.darwin_10.x86_64.tbz2 from http://lil.fr.packages.macports.org/p5.24-perlmagick ---> Fetching distfiles for p5.24-perlmagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from https://distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://lil.fr.distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://mirror.checkdomain.de/imagemagick/ ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://osl.no.distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://nue.de.distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from ftp://ftp.sunet.se/pub/multimedia/graphics/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from ftp://sunsite.icm.edu.pl/packages/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://fco.it.distfiles.macports.org/mirrors/macports- distfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://www.imagemagick.org/download/ ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://sea.us.distfiles.macports.org/macports/distfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://jnb.za.distfiles.macports.org/distfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://jog.id.distfiles.macports.org/macports/distfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://cjj.kr.distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from https://pek.cn.distfiles.macports.org/macports/distfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from ftp://ftp.u-aizu.ac.jp/pub/graphics/image/ImageMagick/imagemagick.org/ ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://her.gr.distfiles.macports.org/ImageMagick Error: org.macports.fetch for port p5.24-perlmagick returned: fetch failed Error: Failed to install p5.24-perlmagick Please see the log file for port p5.24-perlmagick for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5-perlmagick/p5.24-perlmagick/main.log Error: The following dependencies were not installed: p5.24-perlmagick To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port p5-perlmagick failed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 13:47:56 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 13:47:56 -0000 Subject: [MacPorts] #53041: p5-xml-twig: update to version 3.52 In-Reply-To: <044.4f82598ac31c02610396d014082d8f12@macports.org> References: <044.4f82598ac31c02610396d014082d8f12@macports.org> Message-ID: <059.fe93a95474d4ed91fc7fb629b28128d1@macports.org> #53041: p5-xml-twig: update to version 3.52 --------------------------+------------------------------- Reporter: dbevans | Owner: frank.mcpherson@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: p5-xml-twig | --------------------------+------------------------------- Changes (by dbevans): * status: new => closed * resolution: => fixed Comment: In [changeset:"4d1cd9fad3b1b513195251eb3fb50a9e69448485/macports-ports" 4d1cd9fa/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="4d1cd9fad3b1b513195251eb3fb50a9e69448485" p5-xml-twig: update to version 3.52 Remove outdated Id tag line and comment. Maintainer timeout. Closes: https://trac.macports.org/ticket/53041 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 14:17:39 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 14:17:39 -0000 Subject: [MacPorts] #53060: p5-perlmagick fetch failed, files missing from server In-Reply-To: <048.ba240fc1d79cfe36bf3172475e943def@macports.org> References: <048.ba240fc1d79cfe36bf3172475e943def@macports.org> Message-ID: <063.11248019325d62f28a6fa4a30e63d432@macports.org> #53060: p5-perlmagick fetch failed, files missing from server ----------------------------+------------------------- Reporter: PBainbridge | Owner: astricker@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: p5-perlmagick | ----------------------------+------------------------- Changes (by mf2k): * keywords: perlmagick, imagemagick => * cc: ryandesign (added) * status: new => assigned * port: p5.24-perlmagick => p5-perlmagick * owner: => astricker@… Comment: In the future, please use WikiFormatting and Cc the port maintainers ({{{port info --maintainers p5-perlmagick}}}), if any. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 14:18:02 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 14:18:02 -0000 Subject: [MacPorts] #53060: p5-perlmagick fetch failed, files missing from server In-Reply-To: <048.ba240fc1d79cfe36bf3172475e943def@macports.org> References: <048.ba240fc1d79cfe36bf3172475e943def@macports.org> Message-ID: <063.a6d84a11f7212077d39d030d722ba530@macports.org> #53060: p5-perlmagick fetch failed, files missing from server ----------------------------+------------------------- Reporter: PBainbridge | Owner: astricker@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: p5-perlmagick | ----------------------------+------------------------- Description changed by mf2k: Old description: > The file ImageMagick-6.9.6-6.tar.xz appears to be missing from the > various mirrors and therefore fails to complete: > > ---> Computing dependencies for p5-perlmagick > ---> Dependencies to be installed: p5.24-perlmagick > ---> Fetching archive for p5.24-perlmagick > ---> Attempting to fetch > p5.24-perlmagick-6.9.6-6_0.darwin_10.x86_64.tbz2 from > https://packages.macports.org/p5.24-perlmagick > ---> Attempting to fetch > p5.24-perlmagick-6.9.6-6_0.darwin_10.x86_64.tbz2 from > http://mse.uk.packages.macports.org/sites/packages.macports.org/p5.24-perlmagick > ---> Attempting to fetch > p5.24-perlmagick-6.9.6-6_0.darwin_10.x86_64.tbz2 from > http://lil.fr.packages.macports.org/p5.24-perlmagick > ---> Fetching distfiles for p5.24-perlmagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > https://distfiles.macports.org/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://lil.fr.distfiles.macports.org/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://mirror.checkdomain.de/imagemagick/ > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://osl.no.distfiles.macports.org/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://nue.de.distfiles.macports.org/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > ftp://ftp.sunet.se/pub/multimedia/graphics/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > ftp://sunsite.icm.edu.pl/packages/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://fco.it.distfiles.macports.org/mirrors/macports- > distfiles/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://www.imagemagick.org/download/ > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://sea.us.distfiles.macports.org/macports/distfiles/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://jnb.za.distfiles.macports.org/distfiles/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://jog.id.distfiles.macports.org/macports/distfiles/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://cjj.kr.distfiles.macports.org/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > https://pek.cn.distfiles.macports.org/macports/distfiles/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > ftp://ftp.u-aizu.ac.jp/pub/graphics/image/ImageMagick/imagemagick.org/ > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://her.gr.distfiles.macports.org/ImageMagick > Error: org.macports.fetch for port p5.24-perlmagick returned: fetch > failed > Error: Failed to install p5.24-perlmagick > Please see the log file for port p5.24-perlmagick for details: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5-perlmagick/p5.24-perlmagick/main.log > Error: The following dependencies were not installed: p5.24-perlmagick > To report a bug, follow the instructions in the guide: > http://guide.macports.org/#project.tickets > Error: Processing of port p5-perlmagick failed New description: The file ImageMagick-6.9.6-6.tar.xz appears to be missing from the various mirrors and therefore fails to complete: {{{ ---> Computing dependencies for p5-perlmagick ---> Dependencies to be installed: p5.24-perlmagick ---> Fetching archive for p5.24-perlmagick ---> Attempting to fetch p5.24-perlmagick-6.9.6-6_0.darwin_10.x86_64.tbz2 from https://packages.macports.org/p5.24-perlmagick ---> Attempting to fetch p5.24-perlmagick-6.9.6-6_0.darwin_10.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/p5.24-perlmagick ---> Attempting to fetch p5.24-perlmagick-6.9.6-6_0.darwin_10.x86_64.tbz2 from http://lil.fr.packages.macports.org/p5.24-perlmagick ---> Fetching distfiles for p5.24-perlmagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from https://distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://lil.fr.distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://mirror.checkdomain.de/imagemagick/ ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://osl.no.distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://nue.de.distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from ftp://ftp.sunet.se/pub/multimedia/graphics/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from ftp://sunsite.icm.edu.pl/packages/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://fco.it.distfiles.macports.org/mirrors/macports- distfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://www.imagemagick.org/download/ ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://sea.us.distfiles.macports.org/macports/distfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://jnb.za.distfiles.macports.org/distfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://jog.id.distfiles.macports.org/macports/distfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://cjj.kr.distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from https://pek.cn.distfiles.macports.org/macports/distfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from ftp://ftp.u-aizu.ac.jp/pub/graphics/image/ImageMagick/imagemagick.org/ ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://her.gr.distfiles.macports.org/ImageMagick Error: org.macports.fetch for port p5.24-perlmagick returned: fetch failed Error: Failed to install p5.24-perlmagick Please see the log file for port p5.24-perlmagick for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5-perlmagick/p5.24-perlmagick/main.log Error: The following dependencies were not installed: p5.24-perlmagick To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port p5-perlmagick failed }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 14:18:36 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 14:18:36 -0000 Subject: [MacPorts] #53060: p5.24-perlmagick: fetch failed, files missing from server (was: p5-perlmagick fetch failed, files missing from server) In-Reply-To: <048.ba240fc1d79cfe36bf3172475e943def@macports.org> References: <048.ba240fc1d79cfe36bf3172475e943def@macports.org> Message-ID: <063.17d4d5409c889b2bd73336b4e634027e@macports.org> #53060: p5.24-perlmagick: fetch failed, files missing from server ----------------------------+------------------------- Reporter: PBainbridge | Owner: astricker@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: p5-perlmagick | ----------------------------+------------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 14:47:38 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 14:47:38 -0000 Subject: [MacPorts] #51454: py35-spyder-devel @3.0.0b2 +qt5 won't load after update to Qt5.6 In-Reply-To: <060.dd5b3e8df72a7af79c6c968974e8fa2e@macports.org> References: <060.dd5b3e8df72a7af79c6c968974e8fa2e@macports.org> Message-ID: <075.7e441470b22361c344675cffa0f99f84@macports.org> #51454: py35-spyder-devel @3.0.0b2 +qt5 won't load after update to Qt5.6 ------------------------------+------------------------ Reporter: r.williams.06@… | Owner: eborisch@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: py-spyder-devel | ------------------------------+------------------------ Comment (by eborisch): py-spyder-devel has been updated to 3.0.2; are you still having issues? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 14:53:27 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 14:53:27 -0000 Subject: [MacPorts] #53021: octave @4.2.0_1 +gcc6 +openblas: build failure (was: octave @4.2.0_1: Another build failure) In-Reply-To: <041.a9100f410b771f7245060d742521900f@macports.org> References: <041.a9100f410b771f7245060d742521900f@macports.org> Message-ID: <056.9cded1aa65609581ca176066bb04564c@macports.org> #53021: octave @4.2.0_1 +gcc6 +openblas: build failure ---------------------+--------------------------------- Reporter: mf2k | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: octave | ---------------------+--------------------------------- Comment (by mf2k): I am using the non-default variants {{{+gcc6 +openblas}}} in my variants.conf file to build it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 15:11:03 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 15:11:03 -0000 Subject: [MacPorts] #40174: MinGW-w64: add win64 cross-compiler In-Reply-To: <059.6f05edcab273d7fe0bf88ffe97aec928@macports.org> References: <059.6f05edcab273d7fe0bf88ffe97aec928@macports.org> Message-ID: <074.9888701b5816b598d58270f9607fe76a@macports.org> #40174: MinGW-w64: add win64 cross-compiler -------------------------------------------------+------------------------- Reporter: sam.halliday@… | Owner: mojca Type: request | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: mingw-w64 i686-w64-mingw32-gcc | x86_64-w64-mingw32-gcc | -------------------------------------------------+------------------------- Changes (by mojca): * status: new => closed * resolution: => fixed Comment: In [changeset:"0caa2d2b0c78f879897c25f4b4cd9992d0c223ec/macports-ports" 0caa2d2/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="0caa2d2b0c78f879897c25f4b4cd9992d0c223ec" mingw-w64: new cross-compiler for Windows Following: * ${arch}-w64-mingw32-binutils this completes the cross-compiler for Windows with the following subports: * ${arch}-w64-mingw32-headers * ${arch}-w64-mingw32-crt * ${arch}-w64-mingw32-gcc-bootstrap * ${arch}-w64-mingw32-gcc with `arch=i686|x86_64`. The first two ports come from the MinGW-w64 project, while GCC is compiled from original GCC sources. The `*-gcc-bootstrap` port is needed to compile `*-crt` and `*-gcc` itself. Not (yet?) implemented: * support for Ada * support for pthreads-win32 & OpenMP * support for parallel installation of multiple GCC compilers Closes: https://trac.macports.org/ticket/40174 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 15:17:04 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 15:17:04 -0000 Subject: [MacPorts] #53061: i386-mingw32: remove ports, replaced by i686-w64-mingw32 Message-ID: <042.2f80d4e0beb184bcb48851c3a692428b@macports.org> #53061: i386-mingw32: remove ports, replaced by i686-w64-mingw32 -------------------------+------------------------------------------------- Reporter: mojca | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: i386-mingw32-binutils | i386-mingw32-gcc i386-mingw32-libunicows | i386-mingw32-runtime i386-mingw32-w32api -------------------------+------------------------------------------------- I would like to suggest removal of the following ports: * i386-mingw32-binutils * i386-mingw32-gcc * i386-mingw32-libunicows * i386-mingw32-runtime * i386-mingw32-w32api since the functionality is now provided by the new MinGW-w64 ports (see #40174): * i686-w64-mingw32-binutils * i686-w64-mingw32-headers * i686-w64-mingw32-crt * i686-w64-mingw32-gcc-bootstrap * i686-w64-mingw32-gcc * x86_64-w64-mingw32-binutils * x86_64-w64-mingw32-headers * x86_64-w64-mingw32-crt * x86_64-w64-mingw32-gcc-bootstrap * x86_64-w64-mingw32-gcc Some build instructions are here: * http://www.mingw.org/wiki/HostedCrossCompilerHOWTO * http://www.mingw.org/wiki/linuxcrossmingw but note the citation: > As of this writing, the MinGW Project does not support any official build of GCC, more recent than GCC-3.4.5, for use as a cross hosted MinGW development tool, on any platform. This is unlikely to change, until after an officially supported stable GCC-4.x version has been released, for native use on the MS-Windows platform. > > If you wish to experiment with more recent versions, then please feel free to do so, /.../ > However, please understand that we are currently unable to offer you support for such experimental builds in production use. While they don't say it's impossible to use a newer compiler, using GCC 3.4.5 is literally useless today, and using a newer compiler is both unsupported and much more tricky to get working that by simply fetching MinGW-w64 that supports using basically any given GCC compiler without any patches/modifications at all. See also #31578. We have no dependent ports other than wxmsw that most likely nobody uses. The most we could hypothetically do is provide symlinks from `i386-mingw32-gcc` to `i686-w64-mingw32-gcc` etc. I'm not sure if that is too helpful though. I'm not sure if the ports should be deleted or `replaced_by`. Given that the new ports provide different binary names, it might be better to delete them. If anyone objects, please speak now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 15:18:09 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 15:18:09 -0000 Subject: [MacPorts] #40174: MinGW-w64: add win64 cross-compiler In-Reply-To: <059.6f05edcab273d7fe0bf88ffe97aec928@macports.org> References: <059.6f05edcab273d7fe0bf88ffe97aec928@macports.org> Message-ID: <074.e60866994e4aea6e0c5c5bd2c936a204@macports.org> #40174: MinGW-w64: add win64 cross-compiler -------------------------------------------------+------------------------- Reporter: sam.halliday@… | Owner: mojca Type: request | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: mingw-w64 i686-w64-mingw32-gcc | x86_64-w64-mingw32-gcc | -------------------------------------------------+------------------------- Comment (by mojca): See also #53061 with suggestion to remove i386-mingw. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 15:33:23 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 15:33:23 -0000 Subject: [MacPorts] #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') In-Reply-To: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> References: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> Message-ID: <056.bfc990083a2ff096fe0a5805ccc67174@macports.org> #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') ---------------------+---------------------- Reporter: RJVB | Owner: kimuraw Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ruby23 | ---------------------+---------------------- Comment (by kimuraw): I cannot reproduce the build error on my Mac (OS X 10.9.5 / VMWare fusion). But I found a similar problem for ruby-2.1.3. - https://github.com/Homebrew/legacy-homebrew/issues/32910 The article says wrong permission of `/usr/sbin/dtrace` leads build errors of ruby. Maybe, the following operation solves your problem. {{{ $ sudo chmod -s /usr/sbin/dtrace $ sudo port clean ruby23 $ sudo port -sv install ruby23 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 16:22:17 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 16:22:17 -0000 Subject: [MacPorts] #51344: seqan @2.1.1_0 Fixes installation of missing files In-Reply-To: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> References: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> Message-ID: <057.68f8bc2237d18c289addecae579d2e9d@macports.org> #51344: seqan @2.1.1_0 Fixes installation of missing files ---------------------+--------------------------------- Reporter: rrahn | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: haspatch maintainer Port: seqan | ---------------------+--------------------------------- Changes (by raimue): * status: new => closed * resolution: => fixed Comment: In [changeset:"8289af56ad400ec37110bcd9d5e294f8147bd24d/macports-ports" 8289af5/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="8289af56ad400ec37110bcd9d5e294f8147bd24d" seqan: fix installation of missing files Closes: https://trac.macports.org/ticket/51344 (maintainer) }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 17:03:32 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 17:03:32 -0000 Subject: [MacPorts] #53043: py-sphinx dependents: remove py26 and py33 In-Reply-To: <043.c9ddeb2c0ac22f69cf03bf226e020391@macports.org> References: <043.c9ddeb2c0ac22f69cf03bf226e020391@macports.org> Message-ID: <058.6cb6c9da1984805a2e0529da3177804d@macports.org> #53043: py-sphinx dependents: remove py26 and py33 -------------------------------------------------+------------------------- Reporter: jmroot | Owner: seanfarley Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: py26-hieroglyph py33-hieroglyph | py26-pydicom | -------------------------------------------------+------------------------- Changes (by jmroot): * status: new => closed * resolution: => fixed Comment: In [changeset:"6182bf57059f418d624775633ab88e7c5087f242/macports-ports" 6182bf57/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="6182bf57059f418d624775633ab88e7c5087f242" py-sphinx dependents: remove 26 and 33 subports Sphinx 1.5 has dropped support for Python 2.6 and 3.3. Maintainer timeout. Closes: https://trac.macports.org/ticket/53043 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 17:07:40 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 17:07:40 -0000 Subject: [MacPorts] #53024: byebug Debugger for Ruby 2 In-Reply-To: <050.6c0422a08b4f2e5bf4cb080973445ce9@macports.org> References: <050.6c0422a08b4f2e5bf4cb080973445ce9@macports.org> Message-ID: <065.237e70f41d1fd3667dae95a865f9ff85@macports.org> #53024: byebug Debugger for Ruby 2 ----------------------------+----------------- Reporter: luc-j-bourhis | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rb23-byebug | ----------------------------+----------------- Changes (by luc-j-bourhis): * Attachment "Portfile" removed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 17:07:40 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 17:07:40 -0000 Subject: [MacPorts] #53024: byebug Debugger for Ruby 2 In-Reply-To: <050.6c0422a08b4f2e5bf4cb080973445ce9@macports.org> References: <050.6c0422a08b4f2e5bf4cb080973445ce9@macports.org> Message-ID: <065.a52a6abc2f4c09160c8d5ce6e7443bca@macports.org> #53024: byebug Debugger for Ruby 2 ----------------------------+----------------- Reporter: luc-j-bourhis | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rb23-byebug | ----------------------------+----------------- Changes (by luc-j-bourhis): * Attachment "Portfile" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 17:25:21 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 17:25:21 -0000 Subject: [MacPorts] #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') In-Reply-To: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> References: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> Message-ID: <056.1d846fea17456d35b702bc1263815687@macports.org> #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') ---------------------+---------------------- Reporter: RJVB | Owner: kimuraw Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ruby23 | ---------------------+---------------------- Comment (by RJVB): Yes, this looks like a permissions problem calling dtrace. Rather than making dtrace SUID root it would probably be cleaner to figure out how to make MacPorts build it as root. The big question here is why ruby needs to do this, and to what extent the file generated with the command is host-specific. If it's not, the cleanest thing would be to distribute if in `${filespath}` and copy it to the appropriate location in the `post-configure`. This is what you get running sudo make in ${worksrcpath}: {{{ ... dtrace -o probes.h.tmp -h -C -I. -I.ext/include/x86_64-darwin13 -I./include -I. -s probes.d . ./vm_opts.h sed -e 's/RUBY_/RUBY_DTRACE_/g' -e 's/PROBES_H_TMP/RUBY_PROBES_H/' -e 's/(char \*/(const char */g' -e 's/, char \*/, const char */g' probes.h.tmp > probes.h rm -f probes.h.tmp ... }}} I'll see what probes.h contains and attach it if it seems redistributable. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 17:30:01 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 17:30:01 -0000 Subject: [MacPorts] #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') In-Reply-To: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> References: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> Message-ID: <056.f7f7a14a31f23554981f7d0acfc76100@macports.org> #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') ---------------------+---------------------- Reporter: RJVB | Owner: kimuraw Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ruby23 | ---------------------+---------------------- Changes (by RJVB): * Attachment "probes.h" added. generated probes.h file. It seems to be reproducible on my end. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 17:44:27 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 17:44:27 -0000 Subject: [MacPorts] #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') In-Reply-To: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> References: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> Message-ID: <056.1b1d588a8519111fca0683c0d4842099@macports.org> #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') ---------------------+---------------------- Reporter: RJVB | Owner: kimuraw Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ruby23 | ---------------------+---------------------- Comment (by geekosaur): `dtrace` isn't normally suid. If kimuraw's instruction worked, it turned suid *off* (`chmod -s`); presumably you caused the problem by making `dtrace` suid yourself. (Yes, that is sometimes convenient; it's also quite the security hole, and also breaks non-tracing use cases like this one where you're just compiling a D script: since it doesn't know it is suid, the file is written owned by root instead of the user running it.) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 18:43:17 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 18:43:17 -0000 Subject: [MacPorts] #48296: qt5-mac @5.4.2_1 staging into ${prefix}/libexec/qt5-mac In-Reply-To: <058.6eb383c8eff0c062b8e5f0834cea5b5e@macports.org> References: <058.6eb383c8eff0c062b8e5f0834cea5b5e@macports.org> Message-ID: <073.160b905081f88da07c0caf4bb2ae6213@macports.org> #48296: qt5-mac @5.4.2_1 staging into ${prefix}/libexec/qt5-mac ----------------------------+--------------------------------- Reporter: l.digaspero@… | Owner: MarcusCalhoun-Lopez Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: fixed | Keywords: Port: qt5-mac | ----------------------------+--------------------------------- Changes (by mkae): * status: new => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 18:45:23 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 18:45:23 -0000 Subject: [MacPorts] #53011: x86_64-elf-binutils @ 2.23.1: Doesn't build on macOS Sierra In-Reply-To: <051.083eac2d4dd8db523e48e59d170257df@macports.org> References: <051.083eac2d4dd8db523e48e59d170257df@macports.org> Message-ID: <066.649f49c81badeae98d41f3be3ec68e4a@macports.org> #53011: x86_64-elf-binutils @ 2.23.1: Doesn't build on macOS Sierra ----------------------------------+---------------------------- Reporter: stevecheckoway | Owner: nategriswold@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: x86_64-elf-binutils | ----------------------------------+---------------------------- Changes (by mojca): * cc: mojca (added) * status: assigned => closed * version: 2.3.5 => * resolution: => fixed Comment: See #51935. The port was upgraded to the latest version in [changeset:"9451379b7b431ac5f59a4b940f8c30a4ceca4e63/macports-ports" 9451379b]. I didn't notice this ticket back then, but the package built successfully on all our buildbots from 10.6 up to 10.12. I assume the problem was fixed. If I'm wrong, please reopen the ticket. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 18:49:40 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 18:49:40 -0000 Subject: [MacPorts] #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') In-Reply-To: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> References: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> Message-ID: <056.7d70260680c38526a57db29f5fcef5b0@macports.org> #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') ---------------------+---------------------- Reporter: RJVB | Owner: kimuraw Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ruby23 | ---------------------+---------------------- Comment (by RJVB): Replying to [comment:4 geekosaur]: > (Yes, that is sometimes convenient; it's also quite the security hole, I know, but isn't it a bit more than just a convenience if you want to use dtrace or something built on top of it? > and also breaks non-tracing use cases like this one where you're just compiling a D > script: since it doesn't know it is suid, the file is written owned by root instead of the > user running it.) That shouldn't be a problem here as long as it's world-readable, but the error cited above is not about permissions on the probes.h file. It's hard to know though who complains about opening /dev/fd/8 (an inter-process pipe?) for output, though. It turns out you were right, but I fail to see why. I think it would still be interesting to know if a pre-generated probes.h can be used. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 18:50:11 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 18:50:11 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.5ae5a48167d10184e32bd1eecf8b8da1@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by mkae): Okay, I guess a PR should be created, so that further discussion can start on GitHub, right? Especially needed with @mcalhoun being the maintainer of {{{qt5}}}! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 19:00:11 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 19:00:11 -0000 Subject: [MacPorts] #53062: poppler fails to install Message-ID: <046.c8fa858c3409aff55975ac5519c0f676@macports.org> #53062: poppler fails to install -----------------------+--------------------- Reporter: william76 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: poppler -----------------------+--------------------- I had a look at the download locations, they only have up to 0.48.0 of the package... $ sudo port install poppler ---> Computing dependencies for poppler ---> Fetching distfiles for poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from https://poppler.freedesktop.org/ ---> Attempting to fetch poppler-0.49.0.tar.xz from https://distfiles.macports.org/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://cjj.kr.distfiles.macports.org/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://her.gr.distfiles.macports.org/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://jnb.za.distfiles.macports.org/distfiles/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://jog.id.distfiles.macports.org/macports/distfiles/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://lil.fr.distfiles.macports.org/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://nue.de.distfiles.macports.org/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://osl.no.distfiles.macports.org/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from https://pek.cn.distfiles.macports.org/macports/distfiles/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://sea.us.distfiles.macports.org/macports/distfiles/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/poppler Error: org.macports.fetch for port poppler returned: fetch failed Please see the log file for port poppler for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_poppler/poppler/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port poppler failed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 19:18:51 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 19:18:51 -0000 Subject: [MacPorts] #53008: FileZilla @3.14.1_1: update to 3.22.2.2 In-Reply-To: <041.1bb04e6c1fb79a1e2ee3a682132ffb4f@macports.org> References: <041.1bb04e6c1fb79a1e2ee3a682132ffb4f@macports.org> Message-ID: <056.8aa6c00705ca0cacc2fcf555ebfe6c33@macports.org> #53008: FileZilla @3.14.1_1: update to 3.22.2.2 ------------------------+----------------------- Reporter: l2dy | Owner: rudloff@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: FileZilla | ------------------------+----------------------- Comment (by mojca): rudloff is not too active at the moment, it might help to also provide a patch. I tried upgrading once, but then gave up due to some problems. See also #50514. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 19:33:42 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 19:33:42 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.5cc1199457252ccbb0575f67ec400077@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by RJVB): Possibly. What annoys me a bit here is that we'd be putting stuff in mcalhoun's PG which will later be moved to the common/header PG file. The only way I see around that would be to introduce that common/header PG as `qt5-1.1.tcl`, which for now would simply include `qt5-1.0.tcl` plus define some relevant things from my own common/header PG file. For us it will be easy enough to convert all Portfiles to include the v1.1 Qt5 PG, but how acceptable would it be to make that change to all existing ports using Qt5? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 19:39:18 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 19:39:18 -0000 Subject: [MacPorts] #51729: i386-elf-binutils @2.23.1_1 update to 2.26 In-Reply-To: <062.a04fad3429664b0d14b38b55d52ca4b9@macports.org> References: <062.a04fad3429664b0d14b38b55d52ca4b9@macports.org> Message-ID: <077.dd47951b41bf9c0553832c42da79df97@macports.org> #51729: i386-elf-binutils @2.23.1_1 update to 2.26 --------------------------------+----------------------- Reporter: help@… | Owner: jinksys@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: i386-elf-binutils | --------------------------------+----------------------- Changes (by mojca): * cc: mojca (added) * status: new => closed * resolution: => fixed Comment: See #51935. The problem with libiberty was fixed in [changeset:"2a2a8ad9b30e41ace06c7558ecce28c6fdfdf21f/macports-ports" 2a2a8ad9] and the port was upgraded in [changeset:"9a5ee5f941c294f1da9b21f6290fbc87c1f7f4b1/macports-ports" 9a5ee5f9]. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 19:43:00 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 19:43:00 -0000 Subject: [MacPorts] #51728: x86_64-elf-binutils @2.23.1_1 update to 2.26 In-Reply-To: <062.69f10e9ea0f316393355e778c1c0c507@macports.org> References: <062.69f10e9ea0f316393355e778c1c0c507@macports.org> Message-ID: <077.ae7eebfa3e366d855d47d0e5d9193f2b@macports.org> #51728: x86_64-elf-binutils @2.23.1_1 update to 2.26 ----------------------------------+---------------------------- Reporter: help@… | Owner: nategriswold@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: x86_64-elf-binutils | ----------------------------------+---------------------------- Changes (by mojca): * status: new => closed * cc: mojca (added) * resolution: => fixed Comment: See also #53011 and #51935. The port was upgraded to the latest version in [changeset:"9451379b7b431ac5f59a4b940f8c30a4ceca4e63/macports-ports" 9451379b]. I didn't notice this ticket back then, but the package built successfully on all our buildbots from 10.6 up to 10.12. I assume the problem was fixed. If I'm wrong, please reopen the ticket. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 19:55:34 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 19:55:34 -0000 Subject: [MacPorts] #49386: Binutils @2.24_0 fails to install In-Reply-To: <055.174613476a8c506114d1617aca5dd8c6@macports.org> References: <055.174613476a8c506114d1617aca5dd8c6@macports.org> Message-ID: <070.9c8938ea274d851d5ecb65b5f0760e8c@macports.org> #49386: Binutils @2.24_0 fails to install ----------------------------+-------------------------------- Reporter: ben.haefele@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: binutils | ----------------------------+-------------------------------- Comment (by mojca): * Meanwhile binutils has been upgraded to 2.27, see #51935. Can you please try again? * I don't see `/opt/local/binutils.h` in gdb, but there is `ansidecl.h`. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 19:58:05 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 19:58:05 -0000 Subject: [MacPorts] #43988: mipsel-linux-binutils @2.16.1_3: @itemx must follow @item In-Reply-To: <059.766f626b7bbdc4ad58409ce3517fe004@macports.org> References: <059.766f626b7bbdc4ad58409ce3517fe004@macports.org> Message-ID: <074.c4f4fc7256966f83511027bec3707840@macports.org> #43988: mipsel-linux-binutils @2.16.1_3: @itemx must follow @item ------------------------------------+-------------------------------- Reporter: maverick.woo@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: mipsel-linux-binutils | ------------------------------------+-------------------------------- Changes (by mojca): * cc: mojca (added) * status: new => closed * version: 2.3.0 => * resolution: => fixed Comment: See also #51935. I had problems upgrading this particular port. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 19:59:18 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 19:59:18 -0000 Subject: [MacPorts] #43988: mipsel-linux-binutils @2.16.1_3: @itemx must follow @item In-Reply-To: <059.766f626b7bbdc4ad58409ce3517fe004@macports.org> References: <059.766f626b7bbdc4ad58409ce3517fe004@macports.org> Message-ID: <074.3b79bac369480efe91cb61a8259a2c0f@macports.org> #43988: mipsel-linux-binutils @2.16.1_3: @itemx must follow @item ------------------------------------+-------------------------------- Reporter: maverick.woo@… | Owner: macports-tickets@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: mipsel-linux-binutils | ------------------------------------+-------------------------------- Changes (by mojca): * status: closed => reopened * resolution: fixed => Comment: Sorry, I accidentally closed this ticket. Reopening it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 20:17:42 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 20:17:42 -0000 Subject: [MacPorts] #43646: i386-mingw32-binutils build error In-Reply-To: <059.0428a90efd2d1611cfb13e3c23bf52e6@macports.org> References: <059.0428a90efd2d1611cfb13e3c23bf52e6@macports.org> Message-ID: <074.fb60af11019860aa311bb71c4f047c06@macports.org> #43646: i386-mingw32-binutils build error ------------------------------------+----------------------- Reporter: jozef.mojzis@… | Owner: landonf@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: i386-mingw32-binutils | ------------------------------------+----------------------- Changes (by mojca): * version: 2.2.1 => Comment: The ports seems to [https://build.macports.org/builders/ports-10.9_x86_64-builder/builds/12984 build fine] on the buildbot at the moment. See also: [[TicketQuery(id=40174|51935|53061)]] I would be grateful for further feedback & whether or not this is still a problem for you. Then again I would be in favour of removing this port, you can install `i686-w64-mingw32-binutils` now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 20:23:26 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 20:23:26 -0000 Subject: [MacPorts] #38304: i386-mingw32-binutils @2.21-3_0: windres converts resource string to UTF-16 with wrong endianness, PATCH In-Reply-To: <058.027445a8a8af53248a4e89672cacf876@macports.org> References: <058.027445a8a8af53248a4e89672cacf876@macports.org> Message-ID: <073.fbc2cb079a871eaa94413fb01ae6d344@macports.org> #38304: i386-mingw32-binutils @2.21-3_0: windres converts resource string to UTF-16 with wrong endianness, PATCH ------------------------------------+----------------------- Reporter: phil.krylov@… | Owner: landonf@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: i386-mingw32-binutils | ------------------------------------+----------------------- Changes (by mojca): * version: 2.1.3 => Comment: The ports seems to [https://build.macports.org/builders/ports-10.9_x86_64-builder/builds/12984 build fine] on the buildbot at the moment. See also: [[TicketQuery(id=40174|51935|53061)]] I would be grateful for further feedback & whether or not this is still a problem. Then again I would be in favour of removing this port, you can install `i686-w64-mingw32-binutils` now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 21:03:09 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 21:03:09 -0000 Subject: [MacPorts] #38304: i386-mingw32-binutils @2.21-3_0: windres converts resource string to UTF-16 with wrong endianness, PATCH In-Reply-To: <046.c7f4ac96bb5cf0ccbd7a5c9dbc380086@macports.org> References: <046.c7f4ac96bb5cf0ccbd7a5c9dbc380086@macports.org> Message-ID: <061.f3642d44142d6ae3b85861593fa2534b@macports.org> #38304: i386-mingw32-binutils @2.21-3_0: windres converts resource string to UTF-16 with wrong endianness, PATCH ------------------------------------+----------------------- Reporter: tuffnatty | Owner: landonf@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: i386-mingw32-binutils | ------------------------------------+----------------------- Comment (by tuffnatty): 1) This port did always build fine. The bug reported reveals itself on runtime of a program built using this binutils/windres version. 2) If mingw-w64-* work well finally, there is probably no need for mingw32. I am using a self-built port of mingw-w64 recently. 3) On the other hand, I see no reason to not accept the patch until all mingw32 users switch to mingw-w64, because it is in upstream, tested for ages already, and adding the patch to macports does not seem difficult. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 21:04:03 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 21:04:03 -0000 Subject: [MacPorts] #53062: poppler fails to install In-Reply-To: <046.c8fa858c3409aff55975ac5519c0f676@macports.org> References: <046.c8fa858c3409aff55975ac5519c0f676@macports.org> Message-ID: <061.55a9a3905acf0c7e9b0c9d9fc2a63d77@macports.org> #53062: poppler fails to install ------------------------+---------------------- Reporter: william76 | Owner: dbevans Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: poppler | ------------------------+---------------------- Changes (by mf2k): * owner: => dbevans * status: new => assigned Comment: In the future, please use WikiFormatting and Cc the port maintainers ({{{port info --maintainers poppler}}}), if any. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 21:04:15 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 21:04:15 -0000 Subject: [MacPorts] #53062: poppler fails to install In-Reply-To: <046.c8fa858c3409aff55975ac5519c0f676@macports.org> References: <046.c8fa858c3409aff55975ac5519c0f676@macports.org> Message-ID: <061.c14e197de9103973608563933d7f0415@macports.org> #53062: poppler fails to install ------------------------+---------------------- Reporter: william76 | Owner: dbevans Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: poppler | ------------------------+---------------------- Description changed by mf2k: Old description: > I had a look at the download locations, they only have up to 0.48.0 of > the package... > > $ sudo port install poppler > ---> Computing dependencies for poppler > ---> Fetching distfiles for poppler > ---> Attempting to fetch poppler-0.49.0.tar.xz from > https://poppler.freedesktop.org/ > ---> Attempting to fetch poppler-0.49.0.tar.xz from > https://distfiles.macports.org/poppler > ---> Attempting to fetch poppler-0.49.0.tar.xz from > http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/poppler > ---> Attempting to fetch poppler-0.49.0.tar.xz from > http://cjj.kr.distfiles.macports.org/poppler > ---> Attempting to fetch poppler-0.49.0.tar.xz from > http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/poppler > ---> Attempting to fetch poppler-0.49.0.tar.xz from > http://her.gr.distfiles.macports.org/poppler > ---> Attempting to fetch poppler-0.49.0.tar.xz from > http://jnb.za.distfiles.macports.org/distfiles/poppler > ---> Attempting to fetch poppler-0.49.0.tar.xz from > http://jog.id.distfiles.macports.org/macports/distfiles/poppler > ---> Attempting to fetch poppler-0.49.0.tar.xz from > http://lil.fr.distfiles.macports.org/poppler > ---> Attempting to fetch poppler-0.49.0.tar.xz from > http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/poppler > ---> Attempting to fetch poppler-0.49.0.tar.xz from > http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/poppler > ---> Attempting to fetch poppler-0.49.0.tar.xz from > http://nue.de.distfiles.macports.org/poppler > ---> Attempting to fetch poppler-0.49.0.tar.xz from > http://osl.no.distfiles.macports.org/poppler > ---> Attempting to fetch poppler-0.49.0.tar.xz from > https://pek.cn.distfiles.macports.org/macports/distfiles/poppler > ---> Attempting to fetch poppler-0.49.0.tar.xz from > http://sea.us.distfiles.macports.org/macports/distfiles/poppler > ---> Attempting to fetch poppler-0.49.0.tar.xz from > http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/poppler > Error: org.macports.fetch for port poppler returned: fetch failed > Please see the log file for port poppler for details: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_poppler/poppler/main.log > To report a bug, follow the instructions in the guide: > http://guide.macports.org/#project.tickets > Error: Processing of port poppler failed New description: I had a look at the download locations, they only have up to 0.48.0 of the package... {{{ $ sudo port install poppler ---> Computing dependencies for poppler ---> Fetching distfiles for poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from https://poppler.freedesktop.org/ ---> Attempting to fetch poppler-0.49.0.tar.xz from https://distfiles.macports.org/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://cjj.kr.distfiles.macports.org/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://her.gr.distfiles.macports.org/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://jnb.za.distfiles.macports.org/distfiles/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://jog.id.distfiles.macports.org/macports/distfiles/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://lil.fr.distfiles.macports.org/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://nue.de.distfiles.macports.org/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://osl.no.distfiles.macports.org/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from https://pek.cn.distfiles.macports.org/macports/distfiles/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://sea.us.distfiles.macports.org/macports/distfiles/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/poppler Error: org.macports.fetch for port poppler returned: fetch failed Please see the log file for port poppler for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_poppler/poppler/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port poppler failed }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 21:07:40 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 21:07:40 -0000 Subject: [MacPorts] #53062: poppler fails to install In-Reply-To: <046.c8fa858c3409aff55975ac5519c0f676@macports.org> References: <046.c8fa858c3409aff55975ac5519c0f676@macports.org> Message-ID: <061.920de98085dd6513db2ccea3ad81fe5f@macports.org> #53062: poppler fails to install ------------------------+---------------------- Reporter: william76 | Owner: dbevans Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: poppler | ------------------------+---------------------- Comment (by kencu): worked for me just now: {{{ $ ls -la /opt/local/var/macports/distfiles/poppler/poppler-0.49.0.tar.xz -rw-r--r-- 1 macports admin 1685860 15 Nov 12:51 /opt/local/var/macports/distfiles/poppler/poppler-0.49.0.tar.xz }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 21:41:29 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 21:41:29 -0000 Subject: [MacPorts] #52869: OpenSceneGraph: fails to build due to changes in jpeg port In-Reply-To: <041.605a25c238eb52e5ff80ed0a94ecc86d@macports.org> References: <041.605a25c238eb52e5ff80ed0a94ecc86d@macports.org> Message-ID: <056.dcafae797333f628420f900d2497efcc@macports.org> #52869: OpenSceneGraph: fails to build due to changes in jpeg port -------------------------------------------------+------------------------- Reporter: mkae | Owner: macports- | tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: OpenSceneGraph OpenSceneGraph- | devel | -------------------------------------------------+------------------------- Comment (by dershow): It looks like it has been discussed some at OSG: [https://github.com/openscenegraph/OpenSceneGraph/issues/58] -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 21:46:03 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 21:46:03 -0000 Subject: [MacPorts] #38304: i386-mingw32-binutils @2.21-3_0: windres converts resource string to UTF-16 with wrong endianness, PATCH In-Reply-To: <046.c7f4ac96bb5cf0ccbd7a5c9dbc380086@macports.org> References: <046.c7f4ac96bb5cf0ccbd7a5c9dbc380086@macports.org> Message-ID: <061.07d69954656e19a26e91e8922926c605@macports.org> #38304: i386-mingw32-binutils @2.21-3_0: windres converts resource string to UTF-16 with wrong endianness, PATCH ------------------------------------+----------------------- Reporter: tuffnatty | Owner: landonf@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: i386-mingw32-binutils | ------------------------------------+----------------------- Changes (by mojca): * status: new => closed * resolution: => fixed Comment: In [changeset:"ed25e98e074f868285325b3c1f6b5681afd6737e/macports-ports" ed25e98e/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="ed25e98e074f868285325b3c1f6b5681afd6737e" i386-mingw32-binutils: upgrade to 2.25.1-1 * Upgrade to version 2.25.1-1 * Add license GPL-3+ * Remove `$Id$` line Closes: https://trac.macports.org/ticket/38304 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53061 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 21:46:04 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 21:46:04 -0000 Subject: [MacPorts] #53061: i386-mingw32: remove ports, replaced by i686-w64-mingw32 In-Reply-To: <042.2f80d4e0beb184bcb48851c3a692428b@macports.org> References: <042.2f80d4e0beb184bcb48851c3a692428b@macports.org> Message-ID: <057.df453aad564c29f6df9bbb9dd15761b4@macports.org> #53061: i386-mingw32: remove ports, replaced by i686-w64-mingw32 -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: i386-mingw32-binutils | i386-mingw32-gcc i386-mingw32-libunicows | i386-mingw32-runtime i386-mingw32-w32api | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"ed25e98e074f868285325b3c1f6b5681afd6737e/macports-ports" ed25e98e/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="ed25e98e074f868285325b3c1f6b5681afd6737e" i386-mingw32-binutils: upgrade to 2.25.1-1 * Upgrade to version 2.25.1-1 * Add license GPL-3+ * Remove `$Id$` line Closes: https://trac.macports.org/ticket/38304 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53061 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 21:46:04 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 21:46:04 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.923cc38806cb332a005cbb7448082ab7@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"ed25e98e074f868285325b3c1f6b5681afd6737e/macports-ports" ed25e98e/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="ed25e98e074f868285325b3c1f6b5681afd6737e" i386-mingw32-binutils: upgrade to 2.25.1-1 * Upgrade to version 2.25.1-1 * Add license GPL-3+ * Remove `$Id$` line Closes: https://trac.macports.org/ticket/38304 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53061 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 21:49:13 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 21:49:13 -0000 Subject: [MacPorts] #38304: i386-mingw32-binutils @2.21-3_0: windres converts resource string to UTF-16 with wrong endianness, PATCH In-Reply-To: <046.c7f4ac96bb5cf0ccbd7a5c9dbc380086@macports.org> References: <046.c7f4ac96bb5cf0ccbd7a5c9dbc380086@macports.org> Message-ID: <061.e348c5d098528e430790e2b6e1bd6756@macports.org> #38304: i386-mingw32-binutils @2.21-3_0: windres converts resource string to UTF-16 with wrong endianness, PATCH ------------------------------------+----------------------- Reporter: tuffnatty | Owner: landonf@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: i386-mingw32-binutils | ------------------------------------+----------------------- Comment (by mojca): I checked and the patch is already applied in the version of binutils used by `i686-w64-mingw32-binutils` as well as in the version of binutils as shipped by the MinGW project (2.25.1). I updated the port even (if it's going to be removed afterwards). I didn't bother modernizing it in any other way. I guess I could install it from `binutils` directly, but ... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 21:50:52 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 21:50:52 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.bca8c7d58b62d7625bc77749a54b5945@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Description changed by mojca: Old description: > It would be nice to upgrade the binutils ports and to switch to the > `crossbinutils` PortGroup in ports where this is not yet the case. > > ||= name =||= old version =||= maint. > =||= commit =|| > ||= (using crossbinutils) =|| || > || || > || ~~binutils~~ || ~~2.26.1~~ || > || r150799, [changeset:"82608d82dbbc7a45e67eb5eaa0bb981c9350a438 > /macports-ports" 82608d82] || > || ~~avr-binutils~~ || ~~2.25~~ || ~~g5pw~~ > || r151540 || > || msp430-binutils || 2.21.1a-20120406 || g5pw > || || > || msp430-binutils-devel || 2.22-20120911 || g5pw > || || > || ~~arm-elf-binutils~~ || ~~2.25~~ || > stuartwesterman-gm || > [changeset:"0eb3986fc7a6218b1c2d05899365abc22d66af4d/macports-ports" > 0eb3986f] || > || ~~arm-none-eabi-binutils~~ || ~~2.23.1~~ || > stuartwesterman-gm || > [changeset:"ccc83b50b7d929f9e039525cbcf5a74064983c46/macports-ports" > ccc83b50] || > || ~~i386-elf-binutils~~ || ~~2.23.1~~ || jinksys-gm > || [changeset:"9a5ee5f941c294f1da9b21f6290fbc87c1f7f4b1/macports-ports" > 9a5ee5f9] || > || ~~x86_64-elf-binutils~~ || ~~2.23.1~~ || nategriswold- > gm || [changeset:"9451379b7b431ac5f59a4b940f8c30a4ceca4e63/macports- > ports" 9451379b] || > || ~~ppc-linux-binutils~~ || ~~2.25~~ || > || [changeset:"0cd1ac10a71b2f841e728cbea17442f793031e27/macports-ports" > 0cd1ac10] || > || ~~arm-aout-binutils~~ || ~~2.22~~ || > || [changeset:"3ad4b0960ad55da00d8cbd654538ec94706c386d/macports-ports" > 3ad4b096] || > || ~~spu-binutils~~ || ~~2.20.51.0.5~~ || > || [changeset:"1edf79dcd8ac0cb4371abced98bde1e3e3f99062/macports-ports" > 1edf79dc] || > ||= (not using crossbinutils) =|| || > || || > || arm-none-linux-gnueabi-binutils || 2005q3-2 || > stuartwesterman-gm || || > || m68k-elf-binutils || 2.17 || > || || > || mips-elf-binutils || 2.17 || > || || > || mipsel-linux-binutils || 2.16.1 || > || || > ||= (rtems, see #31945) =|| || > || || > || arm-rtems-binutils || 2.18 || > || || > || i386-rtems-binutils || 2.18 || > || || > || lm32-rtems-binutils || 2.21.1 || yann > .sionneau-gm || || > || m68k-rtems-binutils || 2.18 || > || || > || mips-rtems-binutils || 2.18 || > || || > || powerpc-rtems-binutils || 2.18 || > || || > || sh-rtems-binutils || 2.18 || > || || > || sparc-rtems-binutils || 2.18 || > || || > ||= (obsolete?) =|| || > || || > || i386-mingw32-binutils || 2.21-3 || > || || > || i386-mingw32-binutils || 2.21-3 || > || || > ||= (removed) =|| || > || || > || ~~i960-rtems-binutils~~ || ~~2.16.1~~ || > || [changeset:"c9a5124265ec67a9885a1e4a4d24b24fcee43251/macports-ports" > c9a51242] || New description: It would be nice to upgrade the binutils ports and to switch to the `crossbinutils` PortGroup in ports where this is not yet the case. ||= name =||= old version =||= maint. =||= commit =|| ||= (using crossbinutils) =|| || || || || ~~binutils~~ || ~~2.26.1~~ || || r150799, [changeset:"82608d82dbbc7a45e67eb5eaa0bb981c9350a438/macports- ports" 82608d82] || || ~~avr-binutils~~ || ~~2.25~~ || ~~g5pw~~ || r151540 || || msp430-binutils || 2.21.1a-20120406 || g5pw || || || msp430-binutils-devel || 2.22-20120911 || g5pw || || || ~~arm-elf-binutils~~ || ~~2.25~~ || stuartwesterman-gm || [changeset:"0eb3986fc7a6218b1c2d05899365abc22d66af4d /macports-ports" 0eb3986f] || || ~~arm-none-eabi-binutils~~ || ~~2.23.1~~ || stuartwesterman-gm || [changeset:"ccc83b50b7d929f9e039525cbcf5a74064983c46 /macports-ports" ccc83b50] || || ~~i386-elf-binutils~~ || ~~2.23.1~~ || jinksys-gm || [changeset:"9a5ee5f941c294f1da9b21f6290fbc87c1f7f4b1/macports-ports" 9a5ee5f9], see #51729 || || ~~x86_64-elf-binutils~~ || ~~2.23.1~~ || nategriswold- gm || [changeset:"9451379b7b431ac5f59a4b940f8c30a4ceca4e63/macports- ports" 9451379b], see #53011, #51728 || || ~~ppc-linux-binutils~~ || ~~2.25~~ || || [changeset:"0cd1ac10a71b2f841e728cbea17442f793031e27/macports-ports" 0cd1ac10] || || ~~arm-aout-binutils~~ || ~~2.22~~ || || [changeset:"3ad4b0960ad55da00d8cbd654538ec94706c386d/macports-ports" 3ad4b096] || || ~~spu-binutils~~ || ~~2.20.51.0.5~~ || || [changeset:"1edf79dcd8ac0cb4371abced98bde1e3e3f99062/macports-ports" 1edf79dc] || ||= (not using crossbinutils) =|| || || || || ~~arm-none-linux-gnueabi-binutils~~ || ~~2005q3-2~~ || stuartwesterman-gm || [changeset:"7288f4317f196cd0a8326a7a1b9fe1f42bf4b870 /macports-ports" 7288f431] || || ~~m68k-elf-binutils~~ || ~~2.17~~ || || [changeset:"6348190358f3e179150444e2c3447ccc5996e05a/macports-ports" 63481903] || || ~~mips-elf-binutils~~ || ~~2.17~~ || || [changeset:"ba77cc17739a8b29f028601570fe19bc797383e7/macports-ports" ba77cc17] || || mipsel-linux-binutils || 2.16.1 || || see #38135, #43988 || ||= (rtems, see #31945) =|| || || || || arm-rtems-binutils || 2.18 || || || || i386-rtems-binutils || 2.18 || || || || lm32-rtems-binutils || 2.21.1 || yann.sionneau- gm || || || m68k-rtems-binutils || 2.18 || || || || mips-rtems-binutils || 2.18 || || || || powerpc-rtems-binutils || 2.18 || || || || sh-rtems-binutils || 2.18 || || || || sparc-rtems-binutils || 2.18 || || || ||= (obsolete?) =|| || || || || i386-mingw32-binutils || 2.21-3 || || [changeset:"ed25e98e074f868285325b3c1f6b5681afd6737e/macports-ports" ed25e98e], see #38304, #43646 || ||= (removed) =|| || || || || ~~i960-rtems-binutils~~ || ~~2.16.1~~ || || [changeset:"c9a5124265ec67a9885a1e4a4d24b24fcee43251/macports-ports" c9a51242] || -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 21:52:15 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 21:52:15 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.cd2fa1bf994821a763dbd5379a4f708a@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Description changed by mojca: Old description: > It would be nice to upgrade the binutils ports and to switch to the > `crossbinutils` PortGroup in ports where this is not yet the case. > > ||= name =||= old version =||= maint. > =||= commit =|| > ||= (using crossbinutils) =|| || > || || > || ~~binutils~~ || ~~2.26.1~~ || > || r150799, [changeset:"82608d82dbbc7a45e67eb5eaa0bb981c9350a438 > /macports-ports" 82608d82] || > || ~~avr-binutils~~ || ~~2.25~~ || ~~g5pw~~ > || r151540 || > || msp430-binutils || 2.21.1a-20120406 || g5pw > || || > || msp430-binutils-devel || 2.22-20120911 || g5pw > || || > || ~~arm-elf-binutils~~ || ~~2.25~~ || > stuartwesterman-gm || > [changeset:"0eb3986fc7a6218b1c2d05899365abc22d66af4d/macports-ports" > 0eb3986f] || > || ~~arm-none-eabi-binutils~~ || ~~2.23.1~~ || > stuartwesterman-gm || > [changeset:"ccc83b50b7d929f9e039525cbcf5a74064983c46/macports-ports" > ccc83b50] || > || ~~i386-elf-binutils~~ || ~~2.23.1~~ || jinksys-gm > || [changeset:"9a5ee5f941c294f1da9b21f6290fbc87c1f7f4b1/macports-ports" > 9a5ee5f9], see #51729 || > || ~~x86_64-elf-binutils~~ || ~~2.23.1~~ || nategriswold- > gm || [changeset:"9451379b7b431ac5f59a4b940f8c30a4ceca4e63/macports- > ports" 9451379b], see #53011, #51728 || > || ~~ppc-linux-binutils~~ || ~~2.25~~ || > || [changeset:"0cd1ac10a71b2f841e728cbea17442f793031e27/macports-ports" > 0cd1ac10] || > || ~~arm-aout-binutils~~ || ~~2.22~~ || > || [changeset:"3ad4b0960ad55da00d8cbd654538ec94706c386d/macports-ports" > 3ad4b096] || > || ~~spu-binutils~~ || ~~2.20.51.0.5~~ || > || [changeset:"1edf79dcd8ac0cb4371abced98bde1e3e3f99062/macports-ports" > 1edf79dc] || > ||= (not using crossbinutils) =|| || > || || > || ~~arm-none-linux-gnueabi-binutils~~ || ~~2005q3-2~~ || > stuartwesterman-gm || > [changeset:"7288f4317f196cd0a8326a7a1b9fe1f42bf4b870/macports-ports" > 7288f431] || > || ~~m68k-elf-binutils~~ || ~~2.17~~ || > || [changeset:"6348190358f3e179150444e2c3447ccc5996e05a/macports-ports" > 63481903] || > || ~~mips-elf-binutils~~ || ~~2.17~~ || > || [changeset:"ba77cc17739a8b29f028601570fe19bc797383e7/macports-ports" > ba77cc17] || > || mipsel-linux-binutils || 2.16.1 || > || see #38135, #43988 || > ||= (rtems, see #31945) =|| || > || || > || arm-rtems-binutils || 2.18 || > || || > || i386-rtems-binutils || 2.18 || > || || > || lm32-rtems-binutils || 2.21.1 || yann > .sionneau-gm || || > || m68k-rtems-binutils || 2.18 || > || || > || mips-rtems-binutils || 2.18 || > || || > || powerpc-rtems-binutils || 2.18 || > || || > || sh-rtems-binutils || 2.18 || > || || > || sparc-rtems-binutils || 2.18 || > || || > ||= (obsolete?) =|| || > || || > || i386-mingw32-binutils || 2.21-3 || > || [changeset:"ed25e98e074f868285325b3c1f6b5681afd6737e/macports-ports" > ed25e98e], see #38304, #43646 || > ||= (removed) =|| || > || || > || ~~i960-rtems-binutils~~ || ~~2.16.1~~ || > || [changeset:"c9a5124265ec67a9885a1e4a4d24b24fcee43251/macports-ports" > c9a51242] || New description: It would be nice to upgrade the binutils ports and to switch to the `crossbinutils` PortGroup in ports where this is not yet the case. ||= name =||= old version =||= maint. =||= commit =|| ||= (using crossbinutils) =|| || || || || ~~binutils~~ || ~~2.26.1~~ || || r150799, [changeset:"82608d82dbbc7a45e67eb5eaa0bb981c9350a438/macports- ports" 82608d82] || || ~~avr-binutils~~ || ~~2.25~~ || ~~g5pw~~ || r151540 || || msp430-binutils || 2.21.1a-20120406 || g5pw || || || msp430-binutils-devel || 2.22-20120911 || g5pw || || || ~~arm-elf-binutils~~ || ~~2.25~~ || stuartwesterman-gm || [changeset:"0eb3986fc7a6218b1c2d05899365abc22d66af4d /macports-ports" 0eb3986f] || || ~~arm-none-eabi-binutils~~ || ~~2.23.1~~ || stuartwesterman-gm || [changeset:"ccc83b50b7d929f9e039525cbcf5a74064983c46 /macports-ports" ccc83b50] || || ~~i386-elf-binutils~~ || ~~2.23.1~~ || jinksys-gm || [changeset:"9a5ee5f941c294f1da9b21f6290fbc87c1f7f4b1/macports-ports" 9a5ee5f9], see #51729 || || ~~x86_64-elf-binutils~~ || ~~2.23.1~~ || nategriswold- gm || [changeset:"9451379b7b431ac5f59a4b940f8c30a4ceca4e63/macports- ports" 9451379b], see #53011, #51728 || || ~~ppc-linux-binutils~~ || ~~2.25~~ || || [changeset:"0cd1ac10a71b2f841e728cbea17442f793031e27/macports-ports" 0cd1ac10] || || ~~arm-aout-binutils~~ || ~~2.22~~ || || [changeset:"3ad4b0960ad55da00d8cbd654538ec94706c386d/macports-ports" 3ad4b096] || || ~~spu-binutils~~ || ~~2.20.51.0.5~~ || || [changeset:"1edf79dcd8ac0cb4371abced98bde1e3e3f99062/macports-ports" 1edf79dc] || ||= (not using crossbinutils) =|| || || || || ~~arm-none-linux-gnueabi-binutils~~ || ~~2005q3-2~~ || stuartwesterman-gm || [changeset:"7288f4317f196cd0a8326a7a1b9fe1f42bf4b870 /macports-ports" 7288f431] || || ~~m68k-elf-binutils~~ || ~~2.17~~ || || [changeset:"6348190358f3e179150444e2c3447ccc5996e05a/macports-ports" 63481903] || || ~~mips-elf-binutils~~ || ~~2.17~~ || || [changeset:"ba77cc17739a8b29f028601570fe19bc797383e7/macports-ports" ba77cc17] || || mipsel-linux-binutils || 2.16.1 || || see #38135, #43988 || ||= (rtems, see #31945) =|| || || || || arm-rtems-binutils || 2.18 || || || || i386-rtems-binutils || 2.18 || || || || lm32-rtems-binutils || 2.21.1 || yann.sionneau- gm || || || m68k-rtems-binutils || 2.18 || || || || mips-rtems-binutils || 2.18 || || || || powerpc-rtems-binutils || 2.18 || || || || sh-rtems-binutils || 2.18 || || || || sparc-rtems-binutils || 2.18 || || || ||= (obsolete?, see #53061) =|| || || || || i386-mingw32-binutils || 2.21-3 || || [changeset:"ed25e98e074f868285325b3c1f6b5681afd6737e/macports-ports" ed25e98e], see #38304, #43646 || ||= (removed) =|| || || || || ~~i960-rtems-binutils~~ || ~~2.16.1~~ || || [changeset:"c9a5124265ec67a9885a1e4a4d24b24fcee43251/macports-ports" c9a51242] || -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 22:30:08 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 22:30:08 -0000 Subject: [MacPorts] #38304: i386-mingw32-binutils @2.21-3_0: windres converts resource string to UTF-16 with wrong endianness, PATCH In-Reply-To: <046.c7f4ac96bb5cf0ccbd7a5c9dbc380086@macports.org> References: <046.c7f4ac96bb5cf0ccbd7a5c9dbc380086@macports.org> Message-ID: <061.4b0752624d8607b9ec72c40ffbf5b965@macports.org> #38304: i386-mingw32-binutils @2.21-3_0: windres converts resource string to UTF-16 with wrong endianness, PATCH ------------------------------------+----------------------- Reporter: tuffnatty | Owner: landonf@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: i386-mingw32-binutils | ------------------------------------+----------------------- Comment (by mojca): It fails to build on 10.6: {{{ Undefined symbols: "_wcsncasecmp", referenced from: _rsrc_sort_entries in libbfd.a(peigen.o) }}} but I'm not going to worry why as the port from MinGW-w64 builds just fine. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 22:43:32 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 22:43:32 -0000 Subject: [MacPorts] #43646: i386-mingw32-binutils build error In-Reply-To: <059.0428a90efd2d1611cfb13e3c23bf52e6@macports.org> References: <059.0428a90efd2d1611cfb13e3c23bf52e6@macports.org> Message-ID: <074.12cd642efdfc3c4c259fe2d7a19f7525@macports.org> #43646: i386-mingw32-binutils build error ------------------------------------+----------------------- Reporter: jozef.mojzis@… | Owner: landonf@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: i386-mingw32-binutils | ------------------------------------+----------------------- Changes (by mojca): * status: new => closed * resolution: => fixed Comment: Latest commit with an update to 2.25.1 in [changeset:"ed25e98e074f868285325b3c1f6b5681afd6737e/macports-ports" ed25e98e]. Please reopen if this is still causing problems. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 22:49:33 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 22:49:33 -0000 Subject: [MacPorts] #47836: i386-mingw32-gcc @3.4.5-20060117-2 Fails to build In-Reply-To: <058.3a43d81506ce15ab65b6db6ffc941f4b@macports.org> References: <058.3a43d81506ce15ab65b6db6ffc941f4b@macports.org> Message-ID: <073.3f42030cd3615d9b7c37c2a47b86fdab@macports.org> #47836: i386-mingw32-gcc @3.4.5-20060117-2 Fails to build -------------------------------+----------------------- Reporter: rpspringuel@… | Owner: landonf@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: i386-mingw32-gcc | -------------------------------+----------------------- Changes (by mojca): * cc: mojca (added) * version: 2.3.3 => Comment: The error was: {{{ error: unrecognized command line option "-stdlib=libc++" }}} I would suggest you to install `i686-w64-mingw32-gcc` instead. See: [[TicketQuery(id=40174|53061)]] I don't think that spending any time fixing the ancient beast is worth any effort. I needed a cross-compiler, but this one wasn't able to compile any slightly more modern C++ code. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 22:58:24 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 22:58:24 -0000 Subject: [MacPorts] #13553: gcc43: does not provide gcj on Mac OS X Leopard (PPC) In-Reply-To: <058.48e33d4e739bdfeaddda9e131136bc5b@macports.org> References: <058.48e33d4e739bdfeaddda9e131136bc5b@macports.org> Message-ID: <073.cddb4c524c768de76f06bf6b16a01d5e@macports.org> #13553: gcc43: does not provide gcj on Mac OS X Leopard (PPC) ------------------------+---------------------- Reporter: shirose@… | Owner: mww@… Type: defect | Status: assigned Priority: Low | Milestone: Component: ports | Version: 1.5.2 Resolution: | Keywords: Port: gcc43 | ------------------------+---------------------- Comment (by mojca): See #49227. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 22:58:54 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 22:58:54 -0000 Subject: [MacPorts] #49227: gcc5 @5.2.0: fix gcj In-Reply-To: <066.dce6d1a29528cb82470a6d1404c37036@macports.org> References: <066.dce6d1a29528cb82470a6d1404c37036@macports.org> Message-ID: <081.59ab2aae7a58fe8bcdb0fdbd955d846c@macports.org> #49227: gcc5 @5.2.0: fix gcj ------------------------------------+---------------------- Reporter: howarth.at.macports@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch Port: gcc5 | ------------------------------------+---------------------- Comment (by mojca): See also #13553. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 23:04:29 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 23:04:29 -0000 Subject: [MacPorts] #51982: gcc5 fails to build on snowleopard In-Reply-To: <057.dd264799d28e70ca0f6ffa55f5ac2e24@macports.org> References: <057.dd264799d28e70ca0f6ffa55f5ac2e24@macports.org> Message-ID: <072.34a6734cf0ddd133986cbfa37c2fefd5@macports.org> #51982: gcc5 fails to build on snowleopard ----------------------------+------------------------- Reporter: chrisgorman@… | Owner: mww@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: worksforme | Keywords: snowleopard Port: gcc5 | ----------------------------+------------------------- Changes (by mojca): * status: new => closed * resolution: => worksforme Comment: Failing to get any additional information from the submitter for months and not being able to reproduce the problem, I'm closing this ticket as `worksforme`. If there are still problems, please submit a new ticket after updating macports & port definitions and after a clean attempt. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 23:12:21 2016 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2016 23:12:21 -0000 Subject: [MacPorts] #53062: poppler fails to install In-Reply-To: <046.c8fa858c3409aff55975ac5519c0f676@macports.org> References: <046.c8fa858c3409aff55975ac5519c0f676@macports.org> Message-ID: <061.fd6371b97b937214554b1d7fbd95cbb8@macports.org> #53062: poppler fails to install -------------------------+--------------------- Reporter: william76 | Owner: dbevans Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: worksforme | Keywords: Port: poppler | -------------------------+--------------------- Changes (by dbevans): * cc: ryandesign (added) * status: assigned => closed * resolution: => worksforme Comment: There have been some problems with the MacPorts distfile mirrors recently and according to {{{ port -d distcheck }}} poppler 0.49 is one of the casualties. Poppler is not available on any of the standard MacPorts mirrors. However, I can download it just fine from it's master_sites location https://poppler.freedesktop.org/ either using {{{ sudo port -d fetch poppler ---> Fetching distfiles for poppler DEBUG: Can't run fetch on this port without elevated privileges. Escalating privileges back to root. DEBUG: euid changed to: 0. egid changed to: 0. DEBUG: changing euid/egid - current euid: 0 - current egid: 0 DEBUG: egid changed to: 501 DEBUG: euid changed to: 502 DEBUG: Executing org.macports.fetch (poppler) ---> poppler-0.49.0.tar.xz does not exist in /opt/local/var/macports/distfiles/poppler ---> Attempting to fetch poppler-0.49.0.tar.xz from https://distfiles.macports.org/poppler % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 DEBUG: Fetching distfile failed: The requested URL returned error: 404 Not Found ---> Attempting to fetch poppler-0.49.0.tar.xz from https://poppler.freedesktop.org/ % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 1646k 100 1646k 0 0 678k 0 0:00:02 0:00:02 --:--:-- 678k }}} or directly using a web browser so I suspect that your problem is due to a transient network problem with the upstream poppler server or perhaps a local network problem on your end. At any rate, please give it a try again later. Copying @ryandesign for a possible update on the distfile mirroring situation. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 04:31:48 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 04:31:48 -0000 Subject: [MacPorts] #51736: python35 @3.5.2_0 fails to build with macosx_deployment_target 10.7 In-Reply-To: <062.8c08a469789372292496c76e330ca0cd@macports.org> References: <062.8c08a469789372292496c76e330ca0cd@macports.org> Message-ID: <077.556c978e2ec01820faadf227ae59a9fb@macports.org> #51736: python35 @3.5.2_0 fails to build with macosx_deployment_target 10.7 -----------------------------------------+---------------------------- Reporter: help@… | Owner: jyrkiwahlstedt Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: python34 python35 python36 | -----------------------------------------+---------------------------- Changes (by larryv): * cc: larryv, ned-deily (added) Comment: We don’t support changing the deployment target globally, so I recommend that we not apply any workarounds. This should be reported upstream if it has not already been. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 04:58:55 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 04:58:55 -0000 Subject: [MacPorts] #51736: python35 @3.5.2_0 fails to build with macosx_deployment_target 10.7 In-Reply-To: <062.8c08a469789372292496c76e330ca0cd@macports.org> References: <062.8c08a469789372292496c76e330ca0cd@macports.org> Message-ID: <077.f2a13d11f35a6f39c7800bd03d64e164@macports.org> #51736: python35 @3.5.2_0 fails to build with macosx_deployment_target 10.7 -----------------------------------------+---------------------------- Reporter: help@… | Owner: jyrkiwahlstedt Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: python34 python35 python36 | -----------------------------------------+---------------------------- Comment (by ned-deily): Appears to be a duplicate of http://bugs.python.org/issue21381 which has languished. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 05:24:48 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 05:24:48 -0000 Subject: [MacPorts] #53063: wordpress @3.5: update to 4.6.1 Message-ID: <041.77d2e284d1ff70a3b0febac109a17c8e@macports.org> #53063: wordpress @3.5: update to 4.6.1 --------------------+----------------------- Reporter: l2dy | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: wordpress --------------------+----------------------- WordPress 4.6.1 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 06:36:22 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 06:36:22 -0000 Subject: [MacPorts] #53058: nsis @3.0.1: build fails on 10.6 due to a missing zlib In-Reply-To: <042.90088184fe2b9c0226a378ef5f8f62d8@macports.org> References: <042.90088184fe2b9c0226a378ef5f8f62d8@macports.org> Message-ID: <057.11e85e426dc5a157f2e3a69a7e833a68@macports.org> #53058: nsis @3.0.1: build fails on 10.6 due to a missing zlib ---------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: nsis | ---------------------+------------------------- Comment (by ryandesign): Yes that all sounds right. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 06:52:29 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 06:52:29 -0000 Subject: [MacPorts] #51411: mlt: qt5 subport In-Reply-To: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> References: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> Message-ID: <056.85289307212fdfe4dd97a2dd04d67179@macports.org> #51411: mlt: qt5 subport --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: mlt | --------------------------+---------------------- Comment (by ddennedy): I am trying to test this, but when I run portindex with multimedia/mlt/Portfile patched with mlt.4.diff, I get `Failed to parse file multimedia/mlt/Portfile with subport 'mlt-qt5': can't read "os.major": no such variable` I see os.major documented in the Guide, but I do not know why it is failing. I did run `port selfupdate` prior to starting this, and it succeeded. I am running 10.11 El Capitan {{{ Macbooks-MacBook-Pro:ports ddennedy$ port version Version: 2.3.5 }}} Any thoughts? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 07:05:42 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 07:05:42 -0000 Subject: [MacPorts] #51411: mlt: qt5 subport In-Reply-To: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> References: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> Message-ID: <056.43f2020e4e544941c48edfde6849ff24@macports.org> #51411: mlt: qt5 subport --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: mlt | --------------------------+---------------------- Comment (by ddennedy): Despite the above issue, the patched local mlt port (not mlt-qt5) upgraded fine, `melt --version` shows the new version `6.4.1` and some basic tests work. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 07:50:41 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 07:50:41 -0000 Subject: [MacPorts] #53064: qrupdate: parallel universal build fails Message-ID: <047.1ed4877b18293e3962be07af23210783@macports.org> #53064: qrupdate: parallel universal build fails ------------------------+---------------------- Reporter: ryandesign | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.99 Keywords: | Port: qrupdate ------------------------+---------------------- {{{ ---> Building qrupdate DEBUG: Executing org.macports.build (qrupdate) ---> Building qrupdate for architecture x86_64 DEBUG: setting option build.dir to /opt/local/var/macports/build /_Users_rschmidt_macports_macports- ports_math_qrupdate/qrupdate/work/qrupdate-1.1.2-x86_64 DEBUG: Environment: DEBUG: CC_PRINT_OPTIONS='YES' DEBUG: CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build /_Users_rschmidt_macports_macports- ports_math_qrupdate/qrupdate/work/.CC_PRINT_OPTIONS' DEBUG: CPATH='/opt/local/include' DEBUG: LIBRARY_PATH='/opt/local/lib' DEBUG: MACOSX_DEPLOYMENT_TARGET='10.12' Executing: cd "/opt/local/var/macports/build /_Users_rschmidt_macports_macports- ports_math_qrupdate/qrupdate/work/qrupdate-1.1.2-x86_64" && /usr/bin/make -j8 -w lib solib PREFIX=/opt/local LAPACK="" BLAS="-lvecLibFort" DEBUG: system: cd "/opt/local/var/macports/build /_Users_rschmidt_macports_macports- ports_math_qrupdate/qrupdate/work/qrupdate-1.1.2-x86_64" && /usr/bin/make -j8 -w lib solib PREFIX=/opt/local LAPACK="" BLAS="-lvecLibFort" make: Entering directory `/opt/local/var/macports/build /_Users_rschmidt_macports_macports- ports_math_qrupdate/qrupdate/work/qrupdate-1.1.2-x86_64' make -C src/ lib make -C src/ solib make[1]: Entering directory `/opt/local/var/macports/build /_Users_rschmidt_macports_macports- ports_math_qrupdate/qrupdate/work/qrupdate-1.1.2-x86_64/src' make[1]: Entering directory `/opt/local/var/macports/build /_Users_rschmidt_macports_macports- ports_math_qrupdate/qrupdate/work/qrupdate-1.1.2-x86_64/src' /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c caxcpy.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c caxcpy.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cch1dn.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cch1dn.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cch1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cch1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cchdex.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cchdex.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cchinx.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cchinx.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cchshx.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cchshx.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cgqvec.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cgqvec.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cqhqr.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cqhqr.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cqr1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cqr1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cqrdec.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cqrdec.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cqrder.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cqrder.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cqrinc.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cqrinc.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cqrinr.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cqrinr.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cqrot.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cqrot.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cqrqh.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cqrqh.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cqrshc.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cqrshc.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cqrtv1.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dch1dn.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c cqrtv1.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dch1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dch1dn.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dchdex.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dch1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dchinx.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dchdex.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dchshx.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dchinx.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dgqvec.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dchshx.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dqhqr.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dgqvec.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dqr1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dqhqr.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dqrdec.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dqrder.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dqr1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dqrinc.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dqrdec.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dqrinr.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dqrder.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dqrot.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dqrinc.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dqrqh.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dqrinr.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dqrshc.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dqrot.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dqrtv1.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c sch1dn.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dqrqh.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c sch1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dqrshc.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c schdex.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dqrtv1.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c schinx.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c schshx.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c sch1dn.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c sgqvec.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c schdex.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c sqhqr.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c sqr1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c schinx.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c sqrdec.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c schshx.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c sqrder.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c sqr1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c sqrinc.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c sqrdec.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c sqrder.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c sqrinr.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c sqrot.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c sqrinc.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c sqrqh.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c sqrinr.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c sqrshc.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c sqrot.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c sqrtv1.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zaxcpy.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c sqrqh.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zch1dn.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c sqrshc.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zch1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zaxcpy.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zchdex.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zch1dn.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zchinx.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zch1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zchshx.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zgqvec.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zchdex.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zqhqr.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zchinx.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zqr1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zchshx.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zqrdec.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zqhqr.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zqrder.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zqr1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zqrdec.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zqrinc.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zqrder.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zqrinr.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zqrinc.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zqrot.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zqrinr.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zqrqh.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zqrot.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zqrshc.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zqrqh.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zqrtv1.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c clu1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zqrshc.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dlu1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zqrtv1.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c slu1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zlu1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c clu1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c clup1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dlu1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c slu1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dlup1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c slup1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zlu1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zlup1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c clup1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c dlup1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c slup1up.f /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -fPIC -c zlup1up.f libtool -o ../libqrupdate.a caxcpy.o cch1dn.o cch1up.o cchdex.o cchinx.o cchshx.o cgqvec.o cqhqr.o cqr1up.o cqrdec.o cqrder.o cqrinc.o cqrinr.o cqrot.o cqrqh.o cqrshc.o cqrtv1.o dch1dn.o dch1up.o dchdex.o dchinx.o dchshx.o dgqvec.o dqhqr.o dqr1up.o dqrdec.o dqrder.o dqrinc.o dqrinr.o dqrot.o dqrqh.o dqrshc.o dqrtv1.o sch1dn.o sch1up.o schdex.o schinx.o schshx.o sgqvec.o sqhqr.o sqr1up.o sqrdec.o sqrder.o sqrinc.o sqrinr.o sqrot.o sqrqh.o sqrshc.o sqrtv1.o zaxcpy.o zch1dn.o zch1up.o zchdex.o zchinx.o zchshx.o zgqvec.o zqhqr.o zqr1up.o zqrdec.o zqrder.o zqrinc.o zqrinr.o zqrot.o zqrqh.o zqrshc.o zqrtv1.o clu1up.o dlu1up.o slu1up.o zlu1up.o clup1up.o dlup1up.o slup1up.o zlup1up.o error: libtool: can't open file: slup1up.o (No such file or directory) make[1]: *** [../libqrupdate.a] Error 1 make[1]: Leaving directory `/opt/local/var/macports/build /_Users_rschmidt_macports_macports- ports_math_qrupdate/qrupdate/work/qrupdate-1.1.2-x86_64/src' make: *** [lib] Error 2 make: *** Waiting for unfinished jobs.... /opt/local/bin/gfortran-mp-6 -m64 -fimplicit-none -O3 -funroll-loops -dynamiclib -o ../libqrupdate.dylib -install_name /opt/local/lib/libqrupdate.1.dylib caxcpy.o cch1dn.o cch1up.o cchdex.o cchinx.o cchshx.o cgqvec.o cqhqr.o cqr1up.o cqrdec.o cqrder.o cqrinc.o cqrinr.o cqrot.o cqrqh.o cqrshc.o cqrtv1.o dch1dn.o dch1up.o dchdex.o dchinx.o dchshx.o dgqvec.o dqhqr.o dqr1up.o dqrdec.o dqrder.o dqrinc.o dqrinr.o dqrot.o dqrqh.o dqrshc.o dqrtv1.o sch1dn.o sch1up.o schdex.o schinx.o schshx.o sgqvec.o sqhqr.o sqr1up.o sqrdec.o sqrder.o sqrinc.o sqrinr.o sqrot.o sqrqh.o sqrshc.o sqrtv1.o zaxcpy.o zch1dn.o zch1up.o zchdex.o zchinx.o zchshx.o zgqvec.o zqhqr.o zqr1up.o zqrdec.o zqrder.o zqrinc.o zqrinr.o zqrot.o zqrqh.o zqrshc.o zqrtv1.o clu1up.o dlu1up.o slu1up.o zlu1up.o clup1up.o dlup1up.o slup1up.o zlup1up.o \ -lvecLibFort make[1]: Leaving directory `/opt/local/var/macports/build /_Users_rschmidt_macports_macports- ports_math_qrupdate/qrupdate/work/qrupdate-1.1.2-x86_64/src' make: Leaving directory `/opt/local/var/macports/build /_Users_rschmidt_macports_macports- ports_math_qrupdate/qrupdate/work/qrupdate-1.1.2-x86_64' Command failed: cd "/opt/local/var/macports/build /_Users_rschmidt_macports_macports- ports_math_qrupdate/qrupdate/work/qrupdate-1.1.2-x86_64" && /usr/bin/make -j8 -w lib solib PREFIX=/opt/local LAPACK="" BLAS="-lvecLibFort" Exit code: 2 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 07:54:00 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 07:54:00 -0000 Subject: [MacPorts] #53065: qgis @2.18.0 build failure Message-ID: <047.acd0aebce4f8fa360df821a9edae7ed0@macports.org> #53065: qgis @2.18.0 build failure ------------------------+------------------- Reporter: BuddyVolly | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: qgis ------------------------+------------------- Hello, I am using a MacBook Pro early 2011 with El Capitano 10.11.6 I just upgraded from MacPorts 2.3.4 to 2.3.5. After that I upgraded the outdated port which included the upgrade from qgis 2.16.3 to 2.18. This fails with the following messages: {{{ ---> Computing dependencies for QGIS ---> Fetching archive for QGIS 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: ---> Attempting to fetch QGIS- 2_18_0_1+postgresql95+qt4.darwin_15.x86_64.tbz2 from http://fco.it.packages.macports.org/mirrors/macports-packages/QGIS/QGIS ---> Attempting to fetch QGIS- 2_18_0_1+postgresql95+qt4.darwin_15.x86_64.tbz2 from https://packages.macports.org/QGIS ---> Attempting to fetch QGIS- 2_18_0_1+postgresql95+qt4.darwin_15.x86_64.tbz2 from http://lil.fr.packages.macports.org/QGIS ---> Fetching distfiles for QGIS ---> Verifying checksums for QGIS ---> Extracting QGIS ---> Applying patches to QGIS ---> Configuring QGIS Error: org.macports.configure for port QGIS returned: configure failure: command execution failed Please see the log file for port QGIS for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gis_qgis/QGIS/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port qgis failed }}} Find the complete log file attached. Line 2229-2230 indicate that there might be a problem with QScintilla. [[BR]] Any help is much appreciated, many thanks,[[BR]] Andreas -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 07:54:28 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 07:54:28 -0000 Subject: [MacPorts] #53065: qgis @2.18.0 build failure In-Reply-To: <047.acd0aebce4f8fa360df821a9edae7ed0@macports.org> References: <047.acd0aebce4f8fa360df821a9edae7ed0@macports.org> Message-ID: <062.0242182805c38c62ca1a4def28fa5846@macports.org> #53065: qgis @2.18.0 build failure -------------------------+------------------- Reporter: BuddyVolly | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: qgis | -------------------------+------------------- Changes (by BuddyVolly): * Attachment "main.log" added. main logfile -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 08:43:26 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 08:43:26 -0000 Subject: [MacPorts] #53065: QGIS @2.18.0 build failure (was: qgis @2.18.0 build failure) In-Reply-To: <047.acd0aebce4f8fa360df821a9edae7ed0@macports.org> References: <047.acd0aebce4f8fa360df821a9edae7ed0@macports.org> Message-ID: <062.d2c74a83b171ec46e7b85579c4e318f5@macports.org> #53065: QGIS @2.18.0 build failure -------------------------+---------------------- Reporter: BuddyVolly | Owner: Veence Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: QGIS | -------------------------+---------------------- Changes (by ryandesign): * status: new => assigned * owner: => Veence * port: qgis => QGIS -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 08:57:44 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 08:57:44 -0000 Subject: [MacPorts] #51411: mlt: qt5 subport In-Reply-To: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> References: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> Message-ID: <056.e9a1db42a5af8f8028642f30fe64375c@macports.org> #51411: mlt: qt5 subport --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: mlt | --------------------------+---------------------- Comment (by RJVB): Replying to [comment:12 ddennedy]: > I am trying to test this, Thanks, I appreciate it! Good news `port:mlt` still works (not that there was any reason why it wouldn't ... :) ) > `Failed to parse file multimedia/mlt/Portfile with subport 'mlt-qt5': can't read "os.major": no such variable` ... > Any thoughts? Yes, my bad, I missed a global declaration for os.major: I'm quite certain your error will disappear when you add this declaration: {{{ proc qt5.depends_component {first args} { + global os.major }}} Let me know if this works and you want me to upload an updated patch. R. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 09:33:28 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 09:33:28 -0000 Subject: [MacPorts] #48857: gcc ports: support compiling multiple archs (universal) using the Apple GCC driver In-Reply-To: <045.883f557881a10b8bae6a8ce6ba2b74ee@macports.org> References: <045.883f557881a10b8bae6a8ce6ba2b74ee@macports.org> Message-ID: <060.6a7565c07b425f9af6613822545655ad@macports.org> #48857: gcc ports: support compiling multiple archs (universal) using the Apple GCC driver -------------------------------------------------+------------------------- Reporter: devernay | Owner: mww@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gcc43 gcc44 gcc45 gcc46 gcc47 | gcc48 gcc49 gcc5 gcc6 | -------------------------------------------------+------------------------- Comment (by mojca): Did you actually try to get an (official) answer from GCC? I would find this extension useful as well, but in any case someone needs to write a "complete patch". -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 10:10:01 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 10:10:01 -0000 Subject: [MacPorts] #53066: Version Update to SeqAn 2.2.0 Message-ID: <042.15db684f9fdbe281bd57c709cb6b7b88@macports.org> #53066: Version Update to SeqAn 2.2.0 --------------------+------------------- Reporter: rrahn | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: seqan --------------------+------------------- Updates the version of seqan port to version 2.2.0. Updates corresponding hash values and resets revision number to 0. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 10:10:32 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 10:10:32 -0000 Subject: [MacPorts] #53066: Version Update to SeqAn 2.2.0 In-Reply-To: <042.15db684f9fdbe281bd57c709cb6b7b88@macports.org> References: <042.15db684f9fdbe281bd57c709cb6b7b88@macports.org> Message-ID: <057.dc7c2626218d76c7aa9fdcfdd396a8c8@macports.org> #53066: Version Update to SeqAn 2.2.0 ---------------------+----------------- Reporter: rrahn | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: seqan | ---------------------+----------------- Changes (by rrahn): * Attachment "Portfile-seqan.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 11:00:55 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 11:00:55 -0000 Subject: [MacPorts] #53058: nsis @3.0.1: build fails on 10.6 due to a missing zlib In-Reply-To: <042.90088184fe2b9c0226a378ef5f8f62d8@macports.org> References: <042.90088184fe2b9c0226a378ef5f8f62d8@macports.org> Message-ID: <057.8ab36b341b75c5eab483edc282b662c3@macports.org> #53058: nsis @3.0.1: build fails on 10.6 due to a missing zlib ---------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: nsis | ---------------------+------------------------- Comment (by mojca): I would have done it already, but I'm not quite sure which flags belong where. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 11:05:55 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 11:05:55 -0000 Subject: [MacPorts] #53067: brightness @1.0: update to 1.2 Message-ID: <041.91c4e677bc70edf6a02fa405c3d29c74@macports.org> #53067: brightness @1.0: update to 1.2 --------------------+------------------------ Reporter: l2dy | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: brightness --------------------+------------------------ It was moved to https://github.com/nriley/brightness. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 11:39:35 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 11:39:35 -0000 Subject: [MacPorts] #47197: cmake-based ports: add cmake.out_of_source yes/no In-Reply-To: <042.143327c5ff7caac583f0e30b8a2e7ab1@macports.org> References: <042.143327c5ff7caac583f0e30b8a2e7ab1@macports.org> Message-ID: <057.c37e2dcb7ac1980e6b2bdd2a6127b830@macports.org> #47197: cmake-based ports: add cmake.out_of_source yes/no -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: Cockatrice Io LucenePlusPlus | OpenSceneGraph OpenSceneGraph-devel | PlasmaClient PlasmaShop TOra Vidalia allegro | allegro5 alps apbs apiextractor assimp2 | autopano-sift-c blosc bob box2d cgal charm | chemkit chipmunk choqok clucene clucene-devel | coinor-liblemon collada-dom dolfin ebook- | tools efte emergent ettercap exiv2 falcon | fann freealut freecad freecell-solver gccxml- | devel generatorrunner graphite2 htcondor indi | indi_maxdomeii json_spirit kealib libdynd | libftdi libhsplasma liblas libmsn | libmusicbrainz3 libpcl libplist libtuxcap | lua-luabitop metis mysql55-connector-cpp | newmat nifticlib nomacs oce ogre openal-soft | openbabel opencv openjpeg orocos-kdl orocos- | rtt osgswig-devel parmetis pgrouting physfs | piklab playerstage-player playerstage-stage | polkit-qt portmidi py-dynd qfsm qgis | qlandkartegt qlandkartegt-garmindev qlipper | qore-qt4-module rabbitmq-c rsgislib rspamd | scalapack scribus sdcv seqan-apps sfcgal | shogun-devel sigil soci streamlog synergy | synergy-devel sysdig tagainijisho toluapp | usbmuxd viennacl vigra vrpn vtk vtk5 vxl | wbxml2 widelands | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"ac51b298654028d96e94ec9479401d16d1302752/macports-ports" ac51b298/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="ac51b298654028d96e94ec9479401d16d1302752" wbxml2: upgrade to 0.11.4 * Upgrade to version 0.11.4 * Add `cmake.out_of_source yes` * Avoid installing `FindLibWbxml2.cmake` to version-dependent location `${prefix}/share/cmake-3.7/Modules/FindLibWbxml2.cmake` See: https://trac.macports.org/ticket/47197 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 12:03:45 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 12:03:45 -0000 Subject: [MacPorts] #47197: cmake-based ports: add cmake.out_of_source yes/no In-Reply-To: <042.143327c5ff7caac583f0e30b8a2e7ab1@macports.org> References: <042.143327c5ff7caac583f0e30b8a2e7ab1@macports.org> Message-ID: <057.b1ee75ec4f3fea0f19c6b76a59549427@macports.org> #47197: cmake-based ports: add cmake.out_of_source yes/no -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: Cockatrice Io LucenePlusPlus | OpenSceneGraph OpenSceneGraph-devel | PlasmaClient PlasmaShop TOra Vidalia allegro | allegro5 alps apbs apiextractor assimp2 | autopano-sift-c blosc bob box2d cgal charm | chemkit chipmunk choqok clucene clucene-devel | coinor-liblemon collada-dom dolfin ebook- | tools efte emergent ettercap exiv2 falcon | fann freealut freecad freecell-solver gccxml- | devel generatorrunner graphite2 htcondor indi | indi_maxdomeii json_spirit kealib libdynd | libftdi libhsplasma liblas libmsn | libmusicbrainz3 libpcl libplist libtuxcap | lua-luabitop metis mysql55-connector-cpp | newmat nifticlib nomacs oce ogre openal-soft | openbabel opencv openjpeg orocos-kdl orocos- | rtt osgswig-devel parmetis pgrouting physfs | piklab playerstage-player playerstage-stage | polkit-qt portmidi py-dynd qfsm qgis | qlandkartegt qlandkartegt-garmindev qlipper | qore-qt4-module rabbitmq-c rsgislib rspamd | scalapack scribus sdcv seqan-apps sfcgal | shogun-devel sigil soci streamlog synergy | synergy-devel sysdig tagainijisho toluapp | usbmuxd viennacl vigra vrpn vtk vtk5 vxl | wbxml2 widelands | -------------------------------------------------+------------------------- Description changed by mojca: Old description: > Following #33259 and r134128 it would be nice if maintainers of ports > using the cmake PortGroup would add the following line to their ports > {{{ > cmake.out_of_source yes > }}} > and test whether the ports still compile fine (no need for a revbump). > Some ports already use out-of-source builds, so those ports would need a > minor clean-up. > > If the port doesn't work that way, please add an explicit > {{{ > cmake.out_of_source no > }}} > with a short comment (and possibly file an upstream bug report). > > Once all the ports are tested, this would become the default behaviour > and the line (setting `yes`) will be removed from the ports. > > List of affected ports (not necessarily up to date): > > ==== Ports which require maintainer approval ==== > - PlasmaClient (ryandesign): > - PlasmaShop (ryandesign): > - alps (gmail.com:gamperl): > - ~~apbs~~ (gmail.com:howarth.at.macports): > - autopano-sift-c (auckland.ac.nz:p.schmiedeskamp,gmail.com:hvdwolf): > - cgal (vince): > - coinor-liblemon (fu-berlin.de:david.weese,cs.elte.hu:alpar): > - fann (gmail.com:mwilliams256): > - ~~flann~~ (mmoll): ? > - ~~gmt5~~ (eprofs.de:florian,takeshi): r134283 > - ~~gnudatalanguage~~ (takeshi): r134284 > - ~~gnuradio~~ (michaelld): r134164 > - ~~h3dut~~il (sensegraphics.com:support): r134471 > - htcondor (aronnax): > - indi (gmail.com:ferran.casarramona): > - indi_maxdomeii (gmail.com:ferran.casarramona): > - kealib (vince): > - ~~libbiosig~~ (gmx.de:christsc): r134178 > - libhsplasma (ryandesign): > - liblas (gmail.com:venabled): > - ~~libnifalcon~~ (gmail.com:richardsjohnt): r135988 > - libpcl (gmail.com:luminans,vince): > - ~~magicspp~~ (takeshi): r134297 > - metis (sean): > - ogre (gmail.com:marin.saric): > - ~~ompl~~ (mmoll): > - ~~oxygen-icons~~ (nicos): r134217 > - pgrouting (vince): > - physfs (users.sourceforge.net:luiji): > - piklab (bmstu.ru:gav): > - playerstage-player (ai.sri.com:vincent): > - playerstage-stage (ai.sri.com:vincent): > - qgis (vince): > - ~~qhull~~ (mmoll): > - qlandkartegt (puffin.lb.shuttle.de:michael.klein,mk): > - qlandkartegt-garmindev (puffin.lb.shuttle.de:michael.klein,mk): > - qore-qt4-module (scribus.info:petr): > - ~~root6~~ (hep.phy.cam.ac.uk:jonesc,mojca): r134138 > - rsgislib (vince): > - seqan-apps (fu-berlin.de:david.weese): > - sfcgal (vince): > - streamlog (gmail.com:gtolemans): > - ~~uhd~~ (michaelld): r134170 > - vigra (gmail.com:benjamin.seppke): > ==== Ports with openmaintainer ==== > - ~~Bear~~ (cal,openmaintainer): r134188 > - ~~OpenGTL~~ (gmail.com:mschamschula,openmaintainer): r134172 > - TOra (pvanek,openmaintainer): > - ~~airspy~~ (michaelld,openmaintainer): r134227 > - armadillo (gmail.com:christian.frisson,openmaintainer): > - ~~assimp~~ (openmaintainer,mmoll): ? > - ~~bladeRF~~ (michaelld,openmaintainer): r134224 > - blosc (stromnov,openmaintainer): > - box2d (stromnov,openmaintainer): > - bullet (stromnov,openmaintainer): > - ~~ceres-solver~~ (mmoll,openmaintainer): ? > - charm (gmail.com:rjvbertin,mk,openmaintainer): > - chipmunk (stromnov,openmaintainer): > - ~~chromaprint~~ (khindenburg,openmaintainer): r134479 > - ~~clhep~~ (mojca,openmaintainer): r134136 > - clucene (free.fr:dinh.viet.hoa,openmaintainer): > - ~~dcmtk~~ (eborisch,openmaintainer): r135597 > - dolfin (sean,openmaintainer): > - efte (reiffert,openmaintainer): > - ~~eigen~~ (nicos,openmaintainer): r134215 > - ~~eigen3~~ (eborisch,openmaintainer): r140077 > - exiv2 (vafer.org:tcurdt,openmaintainer): > - falcon (snc,openmaintainer): > - ~~fcl~~ (mmoll,openmaintainer): > - freealut (gmail.com:lubodiakov,openmaintainer): > - freecad (gmail.com:mark.brethen,openmaintainer): > - ~~gate~~ (mojca,openmaintainer): r134133 > - ~~geant4~~ (mojca,openmaintainer): r134132 > - ~~gerbil~~ (cal,openmaintainer): r134191 > - ~~glfw~~ (michaelld,openmaintainer): r134225 > - ~~gr-air-modes~~ (michaelld,openmaintainer): r134241 > - ~~gr-ais~~ (michaelld,openmaintainer): r134240 > - ~~gr-baz~~ (michaelld,openmaintainer): r134239 > - ~~gr-dvbs~~ (michaelld,openmaintainer): r134238 > - ~~gr-dvbs2~~ (michaelld,openmaintainer): r134237 > - ~~gr-dvbt~~ (michaelld,openmaintainer): r134236 > - ~~gr-fcdproplus~~ (michaelld,openmaintainer): r134235 > - ~~gr-fosphor~~ (michaelld,openmaintainer): r134233 > - ~~gr-iqbalance~~ (michaelld,openmaintainer): r134232 > - ~~gr-mac~~ (michaelld,openmaintainer): r134231 > - ~~gr-osmosdr~~ (michaelld,openmaintainer): r134230 > - ~~gr-rds~~ (michaelld,openmaintainer): r134229 > - graphite2 (ryandesign,openmaintainer): > - ~~hackrf~~ (michaelld,openmaintainer): r134226 > - ~~iAIDA~~ (mojca,gmail.com:apfeiffer1,openmaintainer): r134134 > - ~~kst~~ (nicos,openmaintainer): r134216 > - ~~lensfun~~ (devans,openmaintainer): r134153 > - ~~lib2geom~~ (devans,openmaintainer): r134154 > - ~~libLASi~~ (takeshi,openmaintainer): r134298 > - ~~libccd~~ (mmoll,openmaintainer): > - libdynd (stromnov,openmaintainer): > - libftdi (snc,openmaintainer): > - ~~libgit2~~ (juanrgar,devans,openmaintainer): r134155 > - ~~liblastfm~~ (michaelld,openmaintainer): r134242 > - ~~libphonenumber-cpp~~ (devans,openmaintainer): r134156 > - ~~libproxy~~ (devans,openmaintainer): r134157 > - ~~libssh~~ (cal,openmaintainer): r134187 > - libtuxcap (ryandesign,openmaintainer): > - ~~lmms~~ (ryandesign,openmaintainer): r135968 > - ~~mariadb~~ (pixilla,openmaintainer): r137069 > - ~~mariadb-10.0~~ (pixilla,openmaintainer): r137069 > - ~~mariadb-10.1~~ (pixilla,openmaintainer): r137069 > - ~~mysql55 (pixilla,openmaintainer): r137069 > - mysql55-connector-cpp (pixilla,openmaintainer): > - ~~mysql56~~ (pixilla,openmaintainer): r137069 > - nomacs (pvanek,openmaintainer): > - oce (gmail.com:mark.brethen,openmaintainer): > - openal-soft (ryandesign,openmaintainer): > - openbabel (mac.com:mlund,openmaintainer): > - opencv (stromnov,openmaintainer): > - ~~openjpeg~~ (mcalhoun,openmaintainer): r138982 > - ~~orfeotoolbox~~ (gmail.com:julien.malik,stromnov,openmaintainer): > r136969 > - parmetis (sean,openmaintainer): > - ~~pdf2htmlex~~ (iapa.in:iapain,mojca,openmaintainer): r134135 > - ~~pdfpc~~ (cal,openmaintainer): r134192 > - ~~percona~~ (mac.com:quest,openmaintainer): r137069 > - ~~phonon~~ (michaelld,openmaintainer): r134243 > - ~~phonon-backend-gstreamer~~ (michaelld,openmaintainer): r134247 > - ~~podofo~~ (devans,openmaintainer): r134159 > - ~~pqp~~ (mmoll,openmaintainer): ? > - py-dynd (stromnov,openmaintainer): > - ~~py-pyside~~ (openmaintainer,mmoll): ? > - ~~py-pyside-tools~~ (openmaintainer,mmoll): ? > - ~~py-shiboken~~ (openmaintainer,mmoll): > - qlipper (pvanek,openmaintainer): > - quassel (sicherha,openmaintainer): > - rabbitmq-c (ryandesign,openmaintainer): > - rspamd (pixilla,openmaintainer): > - ~~rtl-sdr~~ (michaelld,openmaintainer): r134246 > - scalapack (sean,openmaintainer): > - ~~scantailor~~ (raphael,openmaintainer): r148275 > - sdcv (ryandesign,openmaintainer): > - shogun-devel (stromnov,openmaintainer): > - sigil (openmaintainer,krischik): > - soci (rmh.de:g.lorenz,openmaintainer): > - ~~sysdig~~ (g5pw,openmaintainer): r147845 > - tagainijisho (strasweb.fr:rudloff,openmaintainer): > - ~~telepathy-qt~~ (nicos,openmaintainer): r135178 > - ~~tinyxml~~ (openmaintainer,mmoll): r134144 > - viennacl (stromnov,openmaintainer): > - ~~vramsteg~~ (raimue,openmaintainer): r134597 > - vtk (stromnov,openmaintainer): > - ~~weechat~~ (gmail.com:starkhalo,openmaintainer): r137362 > - ~~xrootd~~ (hep.phy.cam.ac.uk:jonesc,openmaintainer): r139539 > - ~~yajl~~ (gmail.com:benjaminlyu,openmaintainer): r139535 > - ~~yaml-cpp~~ (the-huck.com:patrick,openmaintainer): r139538 > ==== Ports with nomaintainer ==== > - Cockatrice: > - ~~FreeRDP~~: r135596 > - Io: > - LucenePlusPlus: > - OpenSceneGraph: > - OpenSceneGraph-devel: > - Vidalia: > - allegro: > - allegro5: > - apiextractor: > - assimp2: > - ~~avidemux~~: r141390 > - chemkit: > - choqok: > - clucene-devel: > - collada-dom: > - ~~cuneiform~~: r136891 > - ~~cutecom-qt4-mac~~: r148651 > - ebook-tools: > - emergent: > - ettercap: > - freecell-solver: > - ~~gccxml-devel~~: r148679 > - generatorrunner: > - ~~gl2ps~~: r135599 > - ~~gmsh~~: r134173 > - ~~hugin-app~~: r134470 > - json_spirit: > - libmsn: > - libmusicbrainz3: > - libplist: > - lua-luabitop: > - newmat: > - nifticlib: > - orocos-kdl: > - orocos-rtt: > - osgswig-devel: > - polkit-qt: > - portmidi: > - qfsm: > - ~~scribus~~: r137847 > - synergy: > - synergy-devel: > - ~~taglib~~: r139536 > - ~~task~~: r139537 > - ~~tigervnc~~: r138607 > - toluapp: > - usbmuxd: > - vrpn: > - vtk5: > - vxl: > - wbxml2: > - ~~wesnoth~~: r139534 > - widelands: > - ~~wxLua~~: r134469 > - ~~zorba~~: r139532 > > === Other === > - kde4-1.1.tcl: r134210 New description: Following #33259 and r134128 it would be nice if maintainers of ports using the cmake PortGroup would add the following line to their ports {{{ cmake.out_of_source yes }}} and test whether the ports still compile fine (no need for a revbump). Some ports already use out-of-source builds, so those ports would need a minor clean-up. If the port doesn't work that way, please add an explicit {{{ cmake.out_of_source no }}} with a short comment (and possibly file an upstream bug report). Once all the ports are tested, this would become the default behaviour and the line (setting `yes`) will be removed from the ports. List of affected ports (not necessarily up to date): ==== Ports which require maintainer approval ==== - PlasmaClient (ryandesign): - PlasmaShop (ryandesign): - alps (gmail.com:gamperl): - ~~apbs~~ (gmail.com:howarth.at.macports): - autopano-sift-c (auckland.ac.nz:p.schmiedeskamp,gmail.com:hvdwolf): - cgal (vince): - coinor-liblemon (fu-berlin.de:david.weese,cs.elte.hu:alpar): - fann (gmail.com:mwilliams256): - ~~flann~~ (mmoll): ? - ~~gmt5~~ (eprofs.de:florian,takeshi): r134283 - ~~gnudatalanguage~~ (takeshi): r134284 - ~~gnuradio~~ (michaelld): r134164 - ~~h3dut~~il (sensegraphics.com:support): r134471 - htcondor (aronnax): - indi (gmail.com:ferran.casarramona): - indi_maxdomeii (gmail.com:ferran.casarramona): - kealib (vince): - ~~libbiosig~~ (gmx.de:christsc): r134178 - libhsplasma (ryandesign): - liblas (gmail.com:venabled): - ~~libnifalcon~~ (gmail.com:richardsjohnt): r135988 - libpcl (gmail.com:luminans,vince): - ~~magicspp~~ (takeshi): r134297 - metis (sean): - ogre (gmail.com:marin.saric): - ~~ompl~~ (mmoll): - ~~oxygen-icons~~ (nicos): r134217 - pgrouting (vince): - physfs (users.sourceforge.net:luiji): - piklab (bmstu.ru:gav): - playerstage-player (ai.sri.com:vincent): - playerstage-stage (ai.sri.com:vincent): - qgis (vince): - ~~qhull~~ (mmoll): - qlandkartegt (puffin.lb.shuttle.de:michael.klein,mk): - qlandkartegt-garmindev (puffin.lb.shuttle.de:michael.klein,mk): - qore-qt4-module (scribus.info:petr): - ~~root6~~ (hep.phy.cam.ac.uk:jonesc,mojca): r134138 - rsgislib (vince): - seqan-apps (fu-berlin.de:david.weese): - sfcgal (vince): - streamlog (gmail.com:gtolemans): - ~~uhd~~ (michaelld): r134170 - vigra (gmail.com:benjamin.seppke): ==== Ports with openmaintainer ==== - ~~Bear~~ (cal,openmaintainer): r134188 - ~~OpenGTL~~ (gmail.com:mschamschula,openmaintainer): r134172 - TOra (pvanek,openmaintainer): - ~~airspy~~ (michaelld,openmaintainer): r134227 - armadillo (gmail.com:christian.frisson,openmaintainer): - ~~assimp~~ (openmaintainer,mmoll): ? - ~~bladeRF~~ (michaelld,openmaintainer): r134224 - blosc (stromnov,openmaintainer): - box2d (stromnov,openmaintainer): - bullet (stromnov,openmaintainer): - ~~ceres-solver~~ (mmoll,openmaintainer): ? - charm (gmail.com:rjvbertin,mk,openmaintainer): - chipmunk (stromnov,openmaintainer): - ~~chromaprint~~ (khindenburg,openmaintainer): r134479 - ~~clhep~~ (mojca,openmaintainer): r134136 - clucene (free.fr:dinh.viet.hoa,openmaintainer): - ~~dcmtk~~ (eborisch,openmaintainer): r135597 - dolfin (sean,openmaintainer): - efte (reiffert,openmaintainer): - ~~eigen~~ (nicos,openmaintainer): r134215 - ~~eigen3~~ (eborisch,openmaintainer): r140077 - exiv2 (vafer.org:tcurdt,openmaintainer): - falcon (snc,openmaintainer): - ~~fcl~~ (mmoll,openmaintainer): - freealut (gmail.com:lubodiakov,openmaintainer): - freecad (gmail.com:mark.brethen,openmaintainer): - ~~gate~~ (mojca,openmaintainer): r134133 - ~~geant4~~ (mojca,openmaintainer): r134132 - ~~gerbil~~ (cal,openmaintainer): r134191 - ~~glfw~~ (michaelld,openmaintainer): r134225 - ~~gr-air-modes~~ (michaelld,openmaintainer): r134241 - ~~gr-ais~~ (michaelld,openmaintainer): r134240 - ~~gr-baz~~ (michaelld,openmaintainer): r134239 - ~~gr-dvbs~~ (michaelld,openmaintainer): r134238 - ~~gr-dvbs2~~ (michaelld,openmaintainer): r134237 - ~~gr-dvbt~~ (michaelld,openmaintainer): r134236 - ~~gr-fcdproplus~~ (michaelld,openmaintainer): r134235 - ~~gr-fosphor~~ (michaelld,openmaintainer): r134233 - ~~gr-iqbalance~~ (michaelld,openmaintainer): r134232 - ~~gr-mac~~ (michaelld,openmaintainer): r134231 - ~~gr-osmosdr~~ (michaelld,openmaintainer): r134230 - ~~gr-rds~~ (michaelld,openmaintainer): r134229 - graphite2 (ryandesign,openmaintainer): - ~~hackrf~~ (michaelld,openmaintainer): r134226 - ~~iAIDA~~ (mojca,gmail.com:apfeiffer1,openmaintainer): r134134 - ~~kst~~ (nicos,openmaintainer): r134216 - ~~lensfun~~ (devans,openmaintainer): r134153 - ~~lib2geom~~ (devans,openmaintainer): r134154 - ~~libLASi~~ (takeshi,openmaintainer): r134298 - ~~libccd~~ (mmoll,openmaintainer): - libdynd (stromnov,openmaintainer): - libftdi (snc,openmaintainer): - ~~libgit2~~ (juanrgar,devans,openmaintainer): r134155 - ~~liblastfm~~ (michaelld,openmaintainer): r134242 - ~~libphonenumber-cpp~~ (devans,openmaintainer): r134156 - ~~libproxy~~ (devans,openmaintainer): r134157 - ~~libssh~~ (cal,openmaintainer): r134187 - libtuxcap (ryandesign,openmaintainer): - ~~lmms~~ (ryandesign,openmaintainer): r135968 - ~~mariadb~~ (pixilla,openmaintainer): r137069 - ~~mariadb-10.0~~ (pixilla,openmaintainer): r137069 - ~~mariadb-10.1~~ (pixilla,openmaintainer): r137069 - ~~mysql55 (pixilla,openmaintainer): r137069 - mysql55-connector-cpp (pixilla,openmaintainer): - ~~mysql56~~ (pixilla,openmaintainer): r137069 - nomacs (pvanek,openmaintainer): - oce (gmail.com:mark.brethen,openmaintainer): - openal-soft (ryandesign,openmaintainer): - openbabel (mac.com:mlund,openmaintainer): - opencv (stromnov,openmaintainer): - ~~openjpeg~~ (mcalhoun,openmaintainer): r138982 - ~~orfeotoolbox~~ (gmail.com:julien.malik,stromnov,openmaintainer): r136969 - parmetis (sean,openmaintainer): - ~~pdf2htmlex~~ (iapa.in:iapain,mojca,openmaintainer): r134135 - ~~pdfpc~~ (cal,openmaintainer): r134192 - ~~percona~~ (mac.com:quest,openmaintainer): r137069 - ~~phonon~~ (michaelld,openmaintainer): r134243 - ~~phonon-backend-gstreamer~~ (michaelld,openmaintainer): r134247 - ~~podofo~~ (devans,openmaintainer): r134159 - ~~pqp~~ (mmoll,openmaintainer): ? - py-dynd (stromnov,openmaintainer): - ~~py-pyside~~ (openmaintainer,mmoll): ? - ~~py-pyside-tools~~ (openmaintainer,mmoll): ? - ~~py-shiboken~~ (openmaintainer,mmoll): - qlipper (pvanek,openmaintainer): - quassel (sicherha,openmaintainer): - rabbitmq-c (ryandesign,openmaintainer): - rspamd (pixilla,openmaintainer): - ~~rtl-sdr~~ (michaelld,openmaintainer): r134246 - scalapack (sean,openmaintainer): - ~~scantailor~~ (raphael,openmaintainer): r148275 - sdcv (ryandesign,openmaintainer): - shogun-devel (stromnov,openmaintainer): - sigil (openmaintainer,krischik): - soci (rmh.de:g.lorenz,openmaintainer): - ~~sysdig~~ (g5pw,openmaintainer): r147845 - tagainijisho (strasweb.fr:rudloff,openmaintainer): - ~~telepathy-qt~~ (nicos,openmaintainer): r135178 - ~~tinyxml~~ (openmaintainer,mmoll): r134144 - viennacl (stromnov,openmaintainer): - ~~vramsteg~~ (raimue,openmaintainer): r134597 - vtk (stromnov,openmaintainer): - ~~weechat~~ (gmail.com:starkhalo,openmaintainer): r137362 - ~~xrootd~~ (hep.phy.cam.ac.uk:jonesc,openmaintainer): r139539 - ~~yajl~~ (gmail.com:benjaminlyu,openmaintainer): r139535 - ~~yaml-cpp~~ (the-huck.com:patrick,openmaintainer): r139538 ==== Ports with nomaintainer ==== - Cockatrice: - ~~FreeRDP~~: r135596 - Io: - ~~LucenePlusPlus~~: r141818 - ~~OpenSceneGraph~~: r146106 - ~~OpenSceneGraph-devel~~: r146109 - Vidalia: - allegro: - ~~allegro5~~: [changeset:ce43624df98dc50905f49f97ff9a21eb7f1cf117 /macports-ports ce43624d] - apiextractor: - assimp2: - ~~avidemux~~: r141390 - chemkit: - choqok: - clucene-devel: - collada-dom: - ~~cuneiform~~: r136891 - ~~cutecom-qt4-mac~~: r148651 - ebook-tools: - emergent: - ettercap: - freecell-solver: - ~~gccxml-devel~~: r148679 - generatorrunner: - ~~gl2ps~~: r135599 - ~~gmsh~~: r134173 - ~~hugin-app~~: r134470 - json_spirit: - libmsn: - libmusicbrainz3: - libplist: - ~~lua-luabitop~~: r140260 - newmat: - nifticlib: - orocos-kdl: - orocos-rtt: - osgswig-devel: - polkit-qt: - portmidi: - qfsm: - ~~scribus~~: r137847 - synergy: - synergy-devel: - ~~taglib~~: r139536 - ~~task~~: r139537 - ~~tigervnc~~: r138607 - toluapp: - usbmuxd: - ~~vrpn~~: r141020 - vtk5: - vxl: - ~~wbxml2~~: [changeset:ac51b298654028d96e94ec9479401d16d1302752 /macports-ports ac51b298] - ~~wesnoth~~: r139534 - ~~widelands~~: r153719 - ~~wxLua~~: r134469 - ~~zorba~~: r139532 === Other === - kde4-1.1.tcl: r134210 -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 12:15:04 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 12:15:04 -0000 Subject: [MacPorts] #52107: Trac: options to temporarily disable emails on tickets that affect many maintainers and commits In-Reply-To: <042.e08b9e8ca9c85977a7f2cf63065e3324@macports.org> References: <042.e08b9e8ca9c85977a7f2cf63065e3324@macports.org> Message-ID: <057.43062db6e668d518df0474f625b283cc@macports.org> #52107: Trac: options to temporarily disable emails on tickets that affect many maintainers and commits -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: assigned Priority: Low | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+---------------------- Description changed by mojca: Old description: > I opened this to discuss options/ideas to allow "quiet" changes on > tickets like #39383 or #48365/#52081. > > Some solutions that come to my mind: > > * having a separate field similar to descriptions that would not generate > email traffic > * having a checkbox saying "don't send an email when I add these changes" > * being able to a reply with a checkbox "anyone can edit text of this > reply" (people could then edit reply without generating more email > traffic) > * open 100 new tickets and only display a ticket query in the master > ticket (I don't like that idea too much though) > * open two tickets, one to notify developers, the other one without any > subscribers to actually track the progress (ideally I would like to have > the ability to include the whole description field from another ticket) > > See also https://trac-hacks.org/wiki/QuietPlugin for a potentially useful > plugin. > > [https://trac.edgewall.org/ticket/2073#comment:33 Citing]: > > > I think it could be good to take the discussion of your use case over > to the trac-users MailingList. I have ideas on how to solve your issue, > and would be happy to commit some time to implementing a plugin (if > needed), for such a big and important open source project that uses Trac > ;) > > > > If you start a thread on trac-users with your ideas on how to solve it > we can start discussing potential solutions. New description: I opened this to discuss options/ideas to allow "quiet" changes on tickets like #39383 or #48365/#52081. Some solutions that come to my mind: * having a separate field similar to descriptions that would not generate email traffic * having a checkbox saying "don't send an email when I add these changes" * being able to a reply with a checkbox "anyone can edit text of this reply" (people could then edit reply without generating more email traffic) * open 100 new tickets and only display a ticket query in the master ticket (I don't like that idea too much though) * open two tickets, one to notify developers, the other one without any subscribers to actually track the progress (ideally I would like to have the ability to include the whole description field from another ticket) See also https://trac-hacks.org/wiki/QuietPlugin for a potentially useful plugin. After we started automatically adding new commit messages at the end of the tickets, this will become an even bigger problem. Ticket #47197 is another example with 60 subscribers and over 200 required commits. On the other hand this might be an opportunity to add some more clever automatism. My wish would be to have one comment field with a well-defined template reserved for the "bot" and then the bot could potentially change that comment as new commits arrive. We could have some syntax like {{{ Closes: https://trac.macports.org/ticket/{nnnnn} for {portname} }}} and then the bot could track progress for us in that template. [https://trac.edgewall.org/ticket/2073#comment:33 Citing]: > I think it could be good to take the discussion of your use case over to the trac-users MailingList. I have ideas on how to solve your issue, and would be happy to commit some time to implementing a plugin (if needed), for such a big and important open source project that uses Trac ;) > > If you start a thread on trac-users with your ideas on how to solve it we can start discussing potential solutions. -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 12:16:49 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 12:16:49 -0000 Subject: [MacPorts] #52107: Trac: options to temporarily disable emails on tickets that affect many maintainers and commits In-Reply-To: <042.e08b9e8ca9c85977a7f2cf63065e3324@macports.org> References: <042.e08b9e8ca9c85977a7f2cf63065e3324@macports.org> Message-ID: <057.d5c8c8e7e1caaa1f5261854d92d6d2e7@macports.org> #52107: Trac: options to temporarily disable emails on tickets that affect many maintainers and commits -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: assigned Priority: Low | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+---------------------- Description changed by mojca: Old description: > I opened this to discuss options/ideas to allow "quiet" changes on > tickets like #39383 or #48365/#52081. > > Some solutions that come to my mind: > > * having a separate field similar to descriptions that would not generate > email traffic > * having a checkbox saying "don't send an email when I add these changes" > * being able to a reply with a checkbox "anyone can edit text of this > reply" (people could then edit reply without generating more email > traffic) > * open 100 new tickets and only display a ticket query in the master > ticket (I don't like that idea too much though) > * open two tickets, one to notify developers, the other one without any > subscribers to actually track the progress (ideally I would like to have > the ability to include the whole description field from another ticket) > > See also https://trac-hacks.org/wiki/QuietPlugin for a potentially useful > plugin. > > After we started automatically adding new commit messages at the end of > the tickets, this will become an even bigger problem. Ticket #47197 is > another example with 60 subscribers and over 200 required commits. On the > other hand this might be an opportunity to add some more clever > automatism. My wish would be to have one comment field with a well- > defined template reserved for the "bot" and then the bot could > potentially change that comment as new commits arrive. > > We could have some syntax like > {{{ > Closes: https://trac.macports.org/ticket/{nnnnn} for {portname} > }}} > and then the bot could track progress for us in that template. > > [https://trac.edgewall.org/ticket/2073#comment:33 Citing]: > > > I think it could be good to take the discussion of your use case over > to the trac-users MailingList. I have ideas on how to solve your issue, > and would be happy to commit some time to implementing a plugin (if > needed), for such a big and important open source project that uses Trac > ;) > > > > If you start a thread on trac-users with your ideas on how to solve it > we can start discussing potential solutions. New description: I opened this to discuss options/ideas to allow "quiet" changes on tickets like #39383 or #48365/#52081. Some solutions that come to my mind: * having a separate field similar to descriptions that would not generate email traffic * having a checkbox saying "don't send an email when I add these changes" * being able to a reply with a checkbox "anyone can edit text of this reply" (people could then edit reply without generating more email traffic) * open 100 new tickets and only display a ticket query in the master ticket (I don't like that idea too much though) * open two tickets, one to notify developers, the other one without any subscribers to actually track the progress (ideally I would like to have the ability to include the whole description field from another ticket) See also https://trac-hacks.org/wiki/QuietPlugin for a potentially useful plugin.
After we started automatically adding new commit messages at the end of the tickets, this will become an even bigger problem. Ticket #47197 is another example with 60 subscribers and over 200 required commits. On the other hand this might be an opportunity to add some more clever automatism. My wish would be to have one comment field with a well-defined template reserved for the "bot" and then the bot could potentially change that comment as new commits arrive. We could have some syntax like {{{ Closes: https://trac.macports.org/ticket/{nnnnn} for {portname} # for partial fixes See: https://trac.macports.org/ticket/{nnnnn} for {anotherportname} }}} and then the bot could track progress for us in that template without notifying all the recipients about the change. [https://trac.edgewall.org/ticket/2073#comment:33 Citing]: > I think it could be good to take the discussion of your use case over to the trac-users MailingList. I have ideas on how to solve your issue, and would be happy to commit some time to implementing a plugin (if needed), for such a big and important open source project that uses Trac ;) > > If you start a thread on trac-users with your ideas on how to solve it we can start discussing potential solutions. -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 12:17:21 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 12:17:21 -0000 Subject: [MacPorts] #52107: Trac: options to temporarily disable emails on tickets that affect many maintainers and commits In-Reply-To: <042.e08b9e8ca9c85977a7f2cf63065e3324@macports.org> References: <042.e08b9e8ca9c85977a7f2cf63065e3324@macports.org> Message-ID: <057.d76d2ce99473a0d22c744bb9cefc4290@macports.org> #52107: Trac: options to temporarily disable emails on tickets that affect many maintainers and commits -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: enhancement | Status: assigned Priority: Low | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+---------------------- Description changed by mojca: Old description: > I opened this to discuss options/ideas to allow "quiet" changes on > tickets like #39383 or #48365/#52081. > > Some solutions that come to my mind: > > * having a separate field similar to descriptions that would not generate > email traffic > * having a checkbox saying "don't send an email when I add these changes" > * being able to a reply with a checkbox "anyone can edit text of this > reply" (people could then edit reply without generating more email > traffic) > * open 100 new tickets and only display a ticket query in the master > ticket (I don't like that idea too much though) > * open two tickets, one to notify developers, the other one without any > subscribers to actually track the progress (ideally I would like to have > the ability to include the whole description field from another ticket) > > See also https://trac-hacks.org/wiki/QuietPlugin for a potentially useful > plugin. > >
> > After we started automatically adding new commit messages at the end of > the tickets, this will become an even bigger problem. Ticket #47197 is > another example with 60 subscribers and over 200 required commits. On the > other hand this might be an opportunity to add some more clever > automatism. My wish would be to have one comment field with a well- > defined template reserved for the "bot" and then the bot could > potentially change that comment as new commits arrive. > > We could have some syntax like > {{{ > Closes: https://trac.macports.org/ticket/{nnnnn} for {portname} > # for partial fixes > See: https://trac.macports.org/ticket/{nnnnn} for {anotherportname} > }}} > and then the bot could track progress for us in that template without > notifying all the recipients about the change. > > [https://trac.edgewall.org/ticket/2073#comment:33 Citing]: > > > I think it could be good to take the discussion of your use case over > to the trac-users MailingList. I have ideas on how to solve your issue, > and would be happy to commit some time to implementing a plugin (if > needed), for such a big and important open source project that uses Trac > ;) > > > > If you start a thread on trac-users with your ideas on how to solve it > we can start discussing potential solutions. New description: I opened this to discuss options/ideas to allow "quiet" changes on tickets like #39383 or #48365/#52081. Some solutions that come to my mind: * having a separate field similar to descriptions that would not generate email traffic * having a checkbox saying "don't send an email when I add these changes" * being able to a reply with a checkbox "anyone can edit text of this reply" (people could then edit reply without generating more email traffic) * open 100 new tickets and only display a ticket query in the master ticket (I don't like that idea too much though) * open two tickets, one to notify developers, the other one without any subscribers to actually track the progress (ideally I would like to have the ability to include the whole description field from another ticket) See also https://trac-hacks.org/wiki/QuietPlugin for a potentially useful plugin. ---- After we started automatically adding new commit messages at the end of the tickets, this will become an even bigger problem. Ticket #47197 is another example with 60 subscribers and over 200 required commits. On the other hand this might be an opportunity to add some more clever automatism. My wish would be to have one comment field with a well-defined template reserved for the "bot" and then the bot could potentially change that comment as new commits arrive. We could have some syntax like {{{ Closes: https://trac.macports.org/ticket/{nnnnn} for {portname} # for partial fixes See: https://trac.macports.org/ticket/{nnnnn} for {anotherportname} }}} and then the bot could track progress for us in that template without notifying all the recipients about the change. [https://trac.edgewall.org/ticket/2073#comment:33 Citing]: > I think it could be good to take the discussion of your use case over to the trac-users MailingList. I have ideas on how to solve your issue, and would be happy to commit some time to implementing a plugin (if needed), for such a big and important open source project that uses Trac ;) > > If you start a thread on trac-users with your ideas on how to solve it we can start discussing potential solutions. -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 12:29:25 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 12:29:25 -0000 Subject: [MacPorts] #53068: Building kerberos5 with LibreSSL broken Message-ID: <042.c91362ad9f23e6c506c532e237484343@macports.org> #53068: Building kerberos5 with LibreSSL broken --------------------+----------------------- Reporter: H3ik0 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: kerberos5 --------------------+----------------------- Hello, I can't build OpenSSH with LibreSSL, because kerberos5 is broken with LibreSSL. Also LibreSSL stable and dev. {{{ ---> Building kerberos5 Error: org.macports.build for port kerberos5 returned: command execution failed Please see the log file for port kerberos5 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_kerberos5/kerberos5/main.log Error: Unable to upgrade port: 1 Error rebuilding kerberos5 while executing "error "Error rebuilding $portname"" (procedure "revupgrade_scanandrebuild" line 395) invoked from within "revupgrade_scanandrebuild broken_port_counts $opts" (procedure "macports::revupgrade" line 5) invoked from within "macports::revupgrade $opts" (procedure "action_revupgrade" line 2) invoked from within "action_revupgrade $action $portlist $opts" (procedure "action_target" line 96) invoked from within "$action_proc $action $portlist [array get global_options]" (procedure "process_cmd" line 103) invoked from within "process_cmd $remaining_args" invoked from within "if { [llength $remaining_args] > 0 } { # If there are remaining arguments, process those as a command set exit_status [process_cmd $remaining..." (file "/opt/local/bin/port" line 5286) }}} main.log: {{{ Error: Port opensshBuilding not found }}} With OpenSSL all is fine. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 12:35:12 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 12:35:12 -0000 Subject: [MacPorts] #49109: port modifications required by making qt4-mac co-installable with Qt5 In-Reply-To: <041.ed916633811460a610cbd879f97870ef@macports.org> References: <041.ed916633811460a610cbd879f97870ef@macports.org> Message-ID: <056.911cf98fdfdfca35d7150e01b7945b89@macports.org> #49109: port modifications required by making qt4-mac co-installable with Qt5 --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: | --------------------------+---------------------- Comment (by RJVB): attica has had recent attention in a different ticket. I trust Nicos has done what it takes to allow it to build. The py-qt patches are relatively recent and c/should indeed be tested independently and committed. Everything qca-related ought to be covered by the qca pull request; the corresponding attachments can be deleted. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 13:13:00 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 13:13:00 -0000 Subject: [MacPorts] #53068: Building kerberos5 with LibreSSL broken In-Reply-To: <042.c91362ad9f23e6c506c532e237484343@macports.org> References: <042.c91362ad9f23e6c506c532e237484343@macports.org> Message-ID: <057.d96d27d3acce7e640f2d87bae1909c5b@macports.org> #53068: Building kerberos5 with LibreSSL broken ------------------------+------------------------ Reporter: H3ik0 | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: kerberos5 | ------------------------+------------------------ Changes (by raimue): * owner: => ryandesign * status: new => assigned Comment: Please attach the full main.log. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 13:38:04 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 13:38:04 -0000 Subject: [MacPorts] #53068: Building kerberos5 with LibreSSL broken In-Reply-To: <042.c91362ad9f23e6c506c532e237484343@macports.org> References: <042.c91362ad9f23e6c506c532e237484343@macports.org> Message-ID: <057.d0d2628d78dbd2b8e33519c8c655cd2c@macports.org> #53068: Building kerberos5 with LibreSSL broken ------------------------+------------------------ Reporter: H3ik0 | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: kerberos5 | ------------------------+------------------------ Changes (by H3ik0): * Attachment "main.log" added. main.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 14:34:55 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 14:34:55 -0000 Subject: [MacPorts] #53069: uhd +python35 build failure Message-ID: <041.2b7d697f3b931da26189c5328053513f@macports.org> #53069: uhd +python35 build failure --------------------+--------------------------- Reporter: mf2k | Owner: michaelld Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: uhd uhd-devel --------------------+--------------------------- uhd(-devel) is failing to build with python35. {{{ "/opt/local/var/macports/build/_opt_local_var_macports_sources_github .com_macports_macports-ports_science_uhd/uhd/work/uhd- 003_010_001_000/host/lib/rfnoc/nocscript/gen_basic_funcs.py", line 455, in write_manual_file :info:build if not func_list_tree.has_key(func['category']): :info:build AttributeError: 'dict' object has no attribute 'has_key' :info:build make[2]: *** [docs/nocscript_functions.dox] Error 1 :info:build make[2]: *** Waiting for unfinished jobs.... :info:build }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 14:35:08 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 14:35:08 -0000 Subject: [MacPorts] #53069: uhd +python35 build failure In-Reply-To: <041.2b7d697f3b931da26189c5328053513f@macports.org> References: <041.2b7d697f3b931da26189c5328053513f@macports.org> Message-ID: <056.30648587e17e88cca922c10efaecdb09@macports.org> #53069: uhd +python35 build failure ----------------------------+----------------------- Reporter: mf2k | Owner: michaelld Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: uhd uhd-devel | ----------------------------+----------------------- Changes (by mf2k): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 14:36:44 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 14:36:44 -0000 Subject: [MacPorts] #53069: uhd +python35 build failure In-Reply-To: <041.2b7d697f3b931da26189c5328053513f@macports.org> References: <041.2b7d697f3b931da26189c5328053513f@macports.org> Message-ID: <056.918fe5333a46a954e96b25d7ce3de9b1@macports.org> #53069: uhd +python35 build failure ----------------------------+----------------------- Reporter: mf2k | Owner: michaelld Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: uhd uhd-devel | ----------------------------+----------------------- Comment (by mf2k): See also #52902. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 14:47:40 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 14:47:40 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.4e41cbb915b9fad9301072cd1695e862@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Comment (by RJVB): I'm finally getting around to looking at this. It looks fine with me, but you haven't included the current version of the GeneralUser soundfont at all. Do you want to ship that as a separate port, or as a subport? It's true that it's linked only indirectly to fluid(synth), so we could ship it under a different name (gu-soundfont? generaluser-soundfont?) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 14:51:40 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 14:51:40 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.84810e61d43bd9ff4f17509ae17c67fa@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Comment (by RJVB): Oh, and re: ${prefix}/etc/timidity : are you patching/configuring TiMidity++ to look there for its config file? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 15:41:06 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 15:41:06 -0000 Subject: [MacPorts] #49960: opencv: add python35 variant In-Reply-To: <059.a087649471a17487e15f25754380ea12@macports.org> References: <059.a087649471a17487e15f25754380ea12@macports.org> Message-ID: <074.d913c4fc8ed1a744948ed0356d1fec81@macports.org> #49960: opencv: add python35 variant -----------------------------+---------------------- Reporter: miguel.barao@… | Owner: stromnov Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: opencv | -----------------------------+---------------------- Comment (by ksze): python35 variant is available now. Somebody should close this ticket. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 15:47:30 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 15:47:30 -0000 Subject: [MacPorts] #53070: Update Version of port sedan-apps to 2.2.0 Message-ID: <042.bb14e5fd4bccf9d3d78441222e2e613b@macports.org> #53070: Update Version of port sedan-apps to 2.2.0 --------------------+------------------------ Reporter: rrahn | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: seqan-apps --------------------+------------------------ Updates seqan-apps portfile to version 2.2.0. Updates the checksums for the corresponding sources. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 15:47:51 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 15:47:51 -0000 Subject: [MacPorts] #53070: Update Version of port sedan-apps to 2.2.0 In-Reply-To: <042.bb14e5fd4bccf9d3d78441222e2e613b@macports.org> References: <042.bb14e5fd4bccf9d3d78441222e2e613b@macports.org> Message-ID: <057.865a1f41108e0371540e9246a7e4debe@macports.org> #53070: Update Version of port sedan-apps to 2.2.0 -------------------------+----------------- Reporter: rrahn | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: seqan-apps | -------------------------+----------------- Changes (by rrahn): * Attachment "Portfile-seqan-apps.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 15:57:40 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 15:57:40 -0000 Subject: [MacPorts] #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') In-Reply-To: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> References: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> Message-ID: <056.402d041d85408543a38de761726d65e1@macports.org> #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') ---------------------+---------------------- Reporter: RJVB | Owner: kimuraw Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ruby23 | ---------------------+---------------------- Comment (by kimuraw): Thanks geekosaur. From your suggestion, I confirmed suid bit of `dtrace` in my Mac is *off*. `sudo port` commands work under user "macports" privileges by default. That is strange dtrace requires "root" suid in this problem. RJVB, can you show me permissions of the build directories and its filesystem? {{{ $ ls -lad /Volumes/VMs/MPbuild /Volumes/VMs $ mount | grep VMs }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 16:05:55 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 16:05:55 -0000 Subject: [MacPorts] #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') In-Reply-To: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> References: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> Message-ID: <056.d21cd9c93ff1b104292d1efd8c2b3e36@macports.org> #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') ---------------------+---------------------- Reporter: RJVB | Owner: kimuraw Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ruby23 | ---------------------+---------------------- Changes (by kimuraw): * Attachment "ruby23-10.9-clang-main.log" added. build success main.log without giving suid to dtrace -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 16:09:19 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 16:09:19 -0000 Subject: [MacPorts] #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') In-Reply-To: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> References: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> Message-ID: <056.4827c5f59b3ee13aa9be6368853fd123@macports.org> #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') ---------------------+---------------------- Reporter: RJVB | Owner: kimuraw Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ruby23 | ---------------------+---------------------- Changes (by kimuraw): * Attachment "ruby23-10.9-probes.h" added. build success probes.h, same as RJVB's -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 16:16:43 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 16:16:43 -0000 Subject: [MacPorts] #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') In-Reply-To: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> References: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> Message-ID: <056.61f62a1a6587e1943cc7bcb8bb4306df@macports.org> #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') ---------------------+---------------------- Reporter: RJVB | Owner: kimuraw Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ruby23 | ---------------------+---------------------- Comment (by RJVB): Replying to [comment:6 kimuraw]: > `sudo port` commands work under user "macports" privileges by default. > That is strange dtrace requires "root" suid in this problem. No, my analysis was wrong: - running `sudo make` inside `${worksrcpath}` (and with the environment set as port would set it) works fine, whether dtrace is SUID or not - running `port build ruby23` works fine when dtrace is NOT suid root. The problem has to do with write permissions on a special file which I *think* is an inter-process pipe where the "stdin part" is created by a privileged application (dtrace running SUID root) and a non privileged process. I've never seen this before, but without knowing who owns /dev/fd/8 (file descriptor 8) I cannot say more. @kimuraw: do you have a possibility to compare the generated probes.h file with mine, preferably also when using other Mac OS versions? It it's identical everywhere (= it depends only on the probes.d input file) then it isn't necessary to generate it anew each time. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 16:20:19 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 16:20:19 -0000 Subject: [MacPorts] #53065: QGIS @2.18.0 build failure In-Reply-To: <047.acd0aebce4f8fa360df821a9edae7ed0@macports.org> References: <047.acd0aebce4f8fa360df821a9edae7ed0@macports.org> Message-ID: <062.f0f7a9322174251862f385c21ddb0354@macports.org> #53065: QGIS @2.18.0 build failure -------------------------+---------------------- Reporter: BuddyVolly | Owner: Veence Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: QGIS | -------------------------+---------------------- Comment (by cmutel): The problem isn't QScintilla, but QCA (crypto stuff). Some [https://github.com/macports/macports- ports/commit/c802cab46968d77548eafffcce6dddc015c93d9f recent changes to QCA in 2.1.0_4] to improve compatibility with QT4 and QT5 somehow broke QGis finding the QCA library or headers. Downgrading to 2.1.0_3+qt4 solved the problem for me. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 16:36:05 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 16:36:05 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.91d57d10d5e9e9448a014d140e4aa3f7@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Comment (by mojca): I included just the fonts from one website. The other package (GeneralUser GS) with the dropbox font is still to be written and I would prefer to make a separate port rather than a subport. I was hoping to get your feedback, publish this font and then do the other one. (And once we have both, continue with TiMidity.) No, I didn't patch TiMidity. I forgot what I did, it's pretty long since I touched the ports, but I think I made symlinks and later realized that sourcing files is the way to go (without testing). And when including files I guess that one can use full path anyway. I only mentioned `/etc` because I saw it in Debian. We can put the files anywhere, but I would prefer to be consistent between different packages (this one, GeneralUser GS, freepats, ...). Suggestions welcome. (I basically forgot most of the stuff, but if one font needs the other, we could make a runtime dependency.) So please let me know if you are OK with the approach of two separate ports (different authors, different names, different sources, ...) and whether you have any other suggestions about this particular package. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 16:37:42 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 16:37:42 -0000 Subject: [MacPorts] #47197: cmake-based ports: add cmake.out_of_source yes/no In-Reply-To: <042.143327c5ff7caac583f0e30b8a2e7ab1@macports.org> References: <042.143327c5ff7caac583f0e30b8a2e7ab1@macports.org> Message-ID: <057.95dae143896b3a78d5933182be863079@macports.org> #47197: cmake-based ports: add cmake.out_of_source yes/no -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: Cockatrice Io LucenePlusPlus | OpenSceneGraph OpenSceneGraph-devel | PlasmaClient PlasmaShop TOra Vidalia allegro | allegro5 alps apbs apiextractor assimp2 | autopano-sift-c blosc bob box2d cgal charm | chemkit chipmunk choqok clucene clucene-devel | coinor-liblemon collada-dom dolfin ebook- | tools efte emergent ettercap exiv2 falcon | fann freealut freecad freecell-solver gccxml- | devel generatorrunner graphite2 indi | indi_maxdomeii json_spirit kealib libdynd | libftdi libhsplasma liblas libmsn | libmusicbrainz3 libpcl libplist libtuxcap | lua-luabitop metis mysql55-connector-cpp | newmat nifticlib nomacs oce ogre openal-soft | openbabel opencv openjpeg orocos-kdl orocos- | rtt osgswig-devel parmetis pgrouting physfs | piklab playerstage-player playerstage-stage | polkit-qt portmidi py-dynd qfsm qgis | qlandkartegt qlandkartegt-garmindev qlipper | qore-qt4-module rabbitmq-c rsgislib rspamd | scalapack scribus sdcv seqan-apps sfcgal | shogun-devel sigil soci streamlog synergy | synergy-devel sysdig tagainijisho toluapp | usbmuxd viennacl vigra vrpn vtk vtk5 vxl | wbxml2 widelands | -------------------------------------------------+------------------------- Changes (by lpsinger): * cc: lpsinger (removed) * port: Cockatrice Io LucenePlusPlus OpenSceneGraph OpenSceneGraph-devel PlasmaClient PlasmaShop TOra Vidalia allegro allegro5 alps apbs apiextractor assimp2 autopano-sift-c blosc bob box2d cgal charm chemkit chipmunk choqok clucene clucene-devel coinor-liblemon collada- dom dolfin ebook-tools efte emergent ettercap exiv2 falcon fann freealut freecad freecell-solver gccxml-devel generatorrunner graphite2 htcondor indi indi_maxdomeii json_spirit kealib libdynd libftdi libhsplasma liblas libmsn libmusicbrainz3 libpcl libplist libtuxcap lua-luabitop metis mysql55-connector-cpp newmat nifticlib nomacs oce ogre openal-soft openbabel opencv openjpeg orocos-kdl orocos-rtt osgswig-devel parmetis pgrouting physfs piklab playerstage- player playerstage-stage polkit-qt portmidi py-dynd qfsm qgis qlandkartegt qlandkartegt-garmindev qlipper qore-qt4-module rabbitmq-c rsgislib rspamd scalapack scribus sdcv seqan-apps sfcgal shogun-devel sigil soci streamlog synergy synergy-devel sysdig tagainijisho toluapp usbmuxd viennacl vigra vrpn vtk vtk5 vxl wbxml2 widelands => Cockatrice Io LucenePlusPlus OpenSceneGraph OpenSceneGraph-devel PlasmaClient PlasmaShop TOra Vidalia allegro allegro5 alps apbs apiextractor assimp2 autopano-sift-c blosc bob box2d cgal charm chemkit chipmunk choqok clucene clucene-devel coinor-liblemon collada- dom dolfin ebook-tools efte emergent ettercap exiv2 falcon fann freealut freecad freecell-solver gccxml-devel generatorrunner graphite2 indi indi_maxdomeii json_spirit kealib libdynd libftdi libhsplasma liblas libmsn libmusicbrainz3 libpcl libplist libtuxcap lua-luabitop metis mysql55-connector-cpp newmat nifticlib nomacs oce ogre openal-soft openbabel opencv openjpeg orocos-kdl orocos-rtt osgswig-devel parmetis pgrouting physfs piklab playerstage-player playerstage-stage polkit-qt portmidi py-dynd qfsm qgis qlandkartegt qlandkartegt-garmindev qlipper qore-qt4-module rabbitmq-c rsgislib rspamd scalapack scribus sdcv seqan-apps sfcgal shogun-devel sigil soci streamlog synergy synergy-devel sysdig tagainijisho toluapp usbmuxd viennacl vigra vrpn vtk vtk5 vxl wbxml2 widelands Old description: > Following #33259 and r134128 it would be nice if maintainers of ports > using the cmake PortGroup would add the following line to their ports > {{{ > cmake.out_of_source yes > }}} > and test whether the ports still compile fine (no need for a revbump). > Some ports already use out-of-source builds, so those ports would need a > minor clean-up. > > If the port doesn't work that way, please add an explicit > {{{ > cmake.out_of_source no > }}} > with a short comment (and possibly file an upstream bug report). > > Once all the ports are tested, this would become the default behaviour > and the line (setting `yes`) will be removed from the ports. > > List of affected ports (not necessarily up to date): > > ==== Ports which require maintainer approval ==== > - PlasmaClient (ryandesign): > - PlasmaShop (ryandesign): > - alps (gmail.com:gamperl): > - ~~apbs~~ (gmail.com:howarth.at.macports): > - autopano-sift-c (auckland.ac.nz:p.schmiedeskamp,gmail.com:hvdwolf): > - cgal (vince): > - coinor-liblemon (fu-berlin.de:david.weese,cs.elte.hu:alpar): > - fann (gmail.com:mwilliams256): > - ~~flann~~ (mmoll): ? > - ~~gmt5~~ (eprofs.de:florian,takeshi): r134283 > - ~~gnudatalanguage~~ (takeshi): r134284 > - ~~gnuradio~~ (michaelld): r134164 > - ~~h3dut~~il (sensegraphics.com:support): r134471 > - htcondor (aronnax): > - indi (gmail.com:ferran.casarramona): > - indi_maxdomeii (gmail.com:ferran.casarramona): > - kealib (vince): > - ~~libbiosig~~ (gmx.de:christsc): r134178 > - libhsplasma (ryandesign): > - liblas (gmail.com:venabled): > - ~~libnifalcon~~ (gmail.com:richardsjohnt): r135988 > - libpcl (gmail.com:luminans,vince): > - ~~magicspp~~ (takeshi): r134297 > - metis (sean): > - ogre (gmail.com:marin.saric): > - ~~ompl~~ (mmoll): > - ~~oxygen-icons~~ (nicos): r134217 > - pgrouting (vince): > - physfs (users.sourceforge.net:luiji): > - piklab (bmstu.ru:gav): > - playerstage-player (ai.sri.com:vincent): > - playerstage-stage (ai.sri.com:vincent): > - qgis (vince): > - ~~qhull~~ (mmoll): > - qlandkartegt (puffin.lb.shuttle.de:michael.klein,mk): > - qlandkartegt-garmindev (puffin.lb.shuttle.de:michael.klein,mk): > - qore-qt4-module (scribus.info:petr): > - ~~root6~~ (hep.phy.cam.ac.uk:jonesc,mojca): r134138 > - rsgislib (vince): > - seqan-apps (fu-berlin.de:david.weese): > - sfcgal (vince): > - streamlog (gmail.com:gtolemans): > - ~~uhd~~ (michaelld): r134170 > - vigra (gmail.com:benjamin.seppke): > ==== Ports with openmaintainer ==== > - ~~Bear~~ (cal,openmaintainer): r134188 > - ~~OpenGTL~~ (gmail.com:mschamschula,openmaintainer): r134172 > - TOra (pvanek,openmaintainer): > - ~~airspy~~ (michaelld,openmaintainer): r134227 > - armadillo (gmail.com:christian.frisson,openmaintainer): > - ~~assimp~~ (openmaintainer,mmoll): ? > - ~~bladeRF~~ (michaelld,openmaintainer): r134224 > - blosc (stromnov,openmaintainer): > - box2d (stromnov,openmaintainer): > - bullet (stromnov,openmaintainer): > - ~~ceres-solver~~ (mmoll,openmaintainer): ? > - charm (gmail.com:rjvbertin,mk,openmaintainer): > - chipmunk (stromnov,openmaintainer): > - ~~chromaprint~~ (khindenburg,openmaintainer): r134479 > - ~~clhep~~ (mojca,openmaintainer): r134136 > - clucene (free.fr:dinh.viet.hoa,openmaintainer): > - ~~dcmtk~~ (eborisch,openmaintainer): r135597 > - dolfin (sean,openmaintainer): > - efte (reiffert,openmaintainer): > - ~~eigen~~ (nicos,openmaintainer): r134215 > - ~~eigen3~~ (eborisch,openmaintainer): r140077 > - exiv2 (vafer.org:tcurdt,openmaintainer): > - falcon (snc,openmaintainer): > - ~~fcl~~ (mmoll,openmaintainer): > - freealut (gmail.com:lubodiakov,openmaintainer): > - freecad (gmail.com:mark.brethen,openmaintainer): > - ~~gate~~ (mojca,openmaintainer): r134133 > - ~~geant4~~ (mojca,openmaintainer): r134132 > - ~~gerbil~~ (cal,openmaintainer): r134191 > - ~~glfw~~ (michaelld,openmaintainer): r134225 > - ~~gr-air-modes~~ (michaelld,openmaintainer): r134241 > - ~~gr-ais~~ (michaelld,openmaintainer): r134240 > - ~~gr-baz~~ (michaelld,openmaintainer): r134239 > - ~~gr-dvbs~~ (michaelld,openmaintainer): r134238 > - ~~gr-dvbs2~~ (michaelld,openmaintainer): r134237 > - ~~gr-dvbt~~ (michaelld,openmaintainer): r134236 > - ~~gr-fcdproplus~~ (michaelld,openmaintainer): r134235 > - ~~gr-fosphor~~ (michaelld,openmaintainer): r134233 > - ~~gr-iqbalance~~ (michaelld,openmaintainer): r134232 > - ~~gr-mac~~ (michaelld,openmaintainer): r134231 > - ~~gr-osmosdr~~ (michaelld,openmaintainer): r134230 > - ~~gr-rds~~ (michaelld,openmaintainer): r134229 > - graphite2 (ryandesign,openmaintainer): > - ~~hackrf~~ (michaelld,openmaintainer): r134226 > - ~~iAIDA~~ (mojca,gmail.com:apfeiffer1,openmaintainer): r134134 > - ~~kst~~ (nicos,openmaintainer): r134216 > - ~~lensfun~~ (devans,openmaintainer): r134153 > - ~~lib2geom~~ (devans,openmaintainer): r134154 > - ~~libLASi~~ (takeshi,openmaintainer): r134298 > - ~~libccd~~ (mmoll,openmaintainer): > - libdynd (stromnov,openmaintainer): > - libftdi (snc,openmaintainer): > - ~~libgit2~~ (juanrgar,devans,openmaintainer): r134155 > - ~~liblastfm~~ (michaelld,openmaintainer): r134242 > - ~~libphonenumber-cpp~~ (devans,openmaintainer): r134156 > - ~~libproxy~~ (devans,openmaintainer): r134157 > - ~~libssh~~ (cal,openmaintainer): r134187 > - libtuxcap (ryandesign,openmaintainer): > - ~~lmms~~ (ryandesign,openmaintainer): r135968 > - ~~mariadb~~ (pixilla,openmaintainer): r137069 > - ~~mariadb-10.0~~ (pixilla,openmaintainer): r137069 > - ~~mariadb-10.1~~ (pixilla,openmaintainer): r137069 > - ~~mysql55 (pixilla,openmaintainer): r137069 > - mysql55-connector-cpp (pixilla,openmaintainer): > - ~~mysql56~~ (pixilla,openmaintainer): r137069 > - nomacs (pvanek,openmaintainer): > - oce (gmail.com:mark.brethen,openmaintainer): > - openal-soft (ryandesign,openmaintainer): > - openbabel (mac.com:mlund,openmaintainer): > - opencv (stromnov,openmaintainer): > - ~~openjpeg~~ (mcalhoun,openmaintainer): r138982 > - ~~orfeotoolbox~~ (gmail.com:julien.malik,stromnov,openmaintainer): > r136969 > - parmetis (sean,openmaintainer): > - ~~pdf2htmlex~~ (iapa.in:iapain,mojca,openmaintainer): r134135 > - ~~pdfpc~~ (cal,openmaintainer): r134192 > - ~~percona~~ (mac.com:quest,openmaintainer): r137069 > - ~~phonon~~ (michaelld,openmaintainer): r134243 > - ~~phonon-backend-gstreamer~~ (michaelld,openmaintainer): r134247 > - ~~podofo~~ (devans,openmaintainer): r134159 > - ~~pqp~~ (mmoll,openmaintainer): ? > - py-dynd (stromnov,openmaintainer): > - ~~py-pyside~~ (openmaintainer,mmoll): ? > - ~~py-pyside-tools~~ (openmaintainer,mmoll): ? > - ~~py-shiboken~~ (openmaintainer,mmoll): > - qlipper (pvanek,openmaintainer): > - quassel (sicherha,openmaintainer): > - rabbitmq-c (ryandesign,openmaintainer): > - rspamd (pixilla,openmaintainer): > - ~~rtl-sdr~~ (michaelld,openmaintainer): r134246 > - scalapack (sean,openmaintainer): > - ~~scantailor~~ (raphael,openmaintainer): r148275 > - sdcv (ryandesign,openmaintainer): > - shogun-devel (stromnov,openmaintainer): > - sigil (openmaintainer,krischik): > - soci (rmh.de:g.lorenz,openmaintainer): > - ~~sysdig~~ (g5pw,openmaintainer): r147845 > - tagainijisho (strasweb.fr:rudloff,openmaintainer): > - ~~telepathy-qt~~ (nicos,openmaintainer): r135178 > - ~~tinyxml~~ (openmaintainer,mmoll): r134144 > - viennacl (stromnov,openmaintainer): > - ~~vramsteg~~ (raimue,openmaintainer): r134597 > - vtk (stromnov,openmaintainer): > - ~~weechat~~ (gmail.com:starkhalo,openmaintainer): r137362 > - ~~xrootd~~ (hep.phy.cam.ac.uk:jonesc,openmaintainer): r139539 > - ~~yajl~~ (gmail.com:benjaminlyu,openmaintainer): r139535 > - ~~yaml-cpp~~ (the-huck.com:patrick,openmaintainer): r139538 > ==== Ports with nomaintainer ==== > - Cockatrice: > - ~~FreeRDP~~: r135596 > - Io: > - ~~LucenePlusPlus~~: r141818 > - ~~OpenSceneGraph~~: r146106 > - ~~OpenSceneGraph-devel~~: r146109 > - Vidalia: > - allegro: > - ~~allegro5~~: [changeset:ce43624df98dc50905f49f97ff9a21eb7f1cf117 > /macports-ports ce43624d] > - apiextractor: > - assimp2: > - ~~avidemux~~: r141390 > - chemkit: > - choqok: > - clucene-devel: > - collada-dom: > - ~~cuneiform~~: r136891 > - ~~cutecom-qt4-mac~~: r148651 > - ebook-tools: > - emergent: > - ettercap: > - freecell-solver: > - ~~gccxml-devel~~: r148679 > - generatorrunner: > - ~~gl2ps~~: r135599 > - ~~gmsh~~: r134173 > - ~~hugin-app~~: r134470 > - json_spirit: > - libmsn: > - libmusicbrainz3: > - libplist: > - ~~lua-luabitop~~: r140260 > - newmat: > - nifticlib: > - orocos-kdl: > - orocos-rtt: > - osgswig-devel: > - polkit-qt: > - portmidi: > - qfsm: > - ~~scribus~~: r137847 > - synergy: > - synergy-devel: > - ~~taglib~~: r139536 > - ~~task~~: r139537 > - ~~tigervnc~~: r138607 > - toluapp: > - usbmuxd: > - ~~vrpn~~: r141020 > - vtk5: > - vxl: > - ~~wbxml2~~: [changeset:ac51b298654028d96e94ec9479401d16d1302752 > /macports-ports ac51b298] > - ~~wesnoth~~: r139534 > - ~~widelands~~: r153719 > - ~~wxLua~~: r134469 > - ~~zorba~~: r139532 > > === Other === > - kde4-1.1.tcl: r134210 New description: Following #33259 and r134128 it would be nice if maintainers of ports using the cmake PortGroup would add the following line to their ports {{{ cmake.out_of_source yes }}} and test whether the ports still compile fine (no need for a revbump). Some ports already use out-of-source builds, so those ports would need a minor clean-up. If the port doesn't work that way, please add an explicit {{{ cmake.out_of_source no }}} with a short comment (and possibly file an upstream bug report). Once all the ports are tested, this would become the default behaviour and the line (setting `yes`) will be removed from the ports. List of affected ports (not necessarily up to date): ==== Ports which require maintainer approval ==== - PlasmaClient (ryandesign): - PlasmaShop (ryandesign): - alps (gmail.com:gamperl): - ~~apbs~~ (gmail.com:howarth.at.macports): - autopano-sift-c (auckland.ac.nz:p.schmiedeskamp,gmail.com:hvdwolf): - cgal (vince): - coinor-liblemon (fu-berlin.de:david.weese,cs.elte.hu:alpar): - fann (gmail.com:mwilliams256): - ~~flann~~ (mmoll): ? - ~~gmt5~~ (eprofs.de:florian,takeshi): r134283 - ~~gnudatalanguage~~ (takeshi): r134284 - ~~gnuradio~~ (michaelld): r134164 - ~~h3dut~~il (sensegraphics.com:support): r134471 - ~~htcondor~~ (aronnax): [changeset:a58ca400496b58e7643b1cd06c578ce6ca03c5be/macports-ports a58ca40049] - indi (gmail.com:ferran.casarramona): - indi_maxdomeii (gmail.com:ferran.casarramona): - kealib (vince): - ~~libbiosig~~ (gmx.de:christsc): r134178 - libhsplasma (ryandesign): - liblas (gmail.com:venabled): - ~~libnifalcon~~ (gmail.com:richardsjohnt): r135988 - libpcl (gmail.com:luminans,vince): - ~~magicspp~~ (takeshi): r134297 - metis (sean): - ogre (gmail.com:marin.saric): - ~~ompl~~ (mmoll): - ~~oxygen-icons~~ (nicos): r134217 - pgrouting (vince): - physfs (users.sourceforge.net:luiji): - piklab (bmstu.ru:gav): - playerstage-player (ai.sri.com:vincent): - playerstage-stage (ai.sri.com:vincent): - qgis (vince): - ~~qhull~~ (mmoll): - qlandkartegt (puffin.lb.shuttle.de:michael.klein,mk): - qlandkartegt-garmindev (puffin.lb.shuttle.de:michael.klein,mk): - qore-qt4-module (scribus.info:petr): - ~~root6~~ (hep.phy.cam.ac.uk:jonesc,mojca): r134138 - rsgislib (vince): - seqan-apps (fu-berlin.de:david.weese): - sfcgal (vince): - streamlog (gmail.com:gtolemans): - ~~uhd~~ (michaelld): r134170 - vigra (gmail.com:benjamin.seppke): ==== Ports with openmaintainer ==== - ~~Bear~~ (cal,openmaintainer): r134188 - ~~OpenGTL~~ (gmail.com:mschamschula,openmaintainer): r134172 - TOra (pvanek,openmaintainer): - ~~airspy~~ (michaelld,openmaintainer): r134227 - armadillo (gmail.com:christian.frisson,openmaintainer): - ~~assimp~~ (openmaintainer,mmoll): ? - ~~bladeRF~~ (michaelld,openmaintainer): r134224 - blosc (stromnov,openmaintainer): - box2d (stromnov,openmaintainer): - bullet (stromnov,openmaintainer): - ~~ceres-solver~~ (mmoll,openmaintainer): ? - charm (gmail.com:rjvbertin,mk,openmaintainer): - chipmunk (stromnov,openmaintainer): - ~~chromaprint~~ (khindenburg,openmaintainer): r134479 - ~~clhep~~ (mojca,openmaintainer): r134136 - clucene (free.fr:dinh.viet.hoa,openmaintainer): - ~~dcmtk~~ (eborisch,openmaintainer): r135597 - dolfin (sean,openmaintainer): - efte (reiffert,openmaintainer): - ~~eigen~~ (nicos,openmaintainer): r134215 - ~~eigen3~~ (eborisch,openmaintainer): r140077 - exiv2 (vafer.org:tcurdt,openmaintainer): - falcon (snc,openmaintainer): - ~~fcl~~ (mmoll,openmaintainer): - freealut (gmail.com:lubodiakov,openmaintainer): - freecad (gmail.com:mark.brethen,openmaintainer): - ~~gate~~ (mojca,openmaintainer): r134133 - ~~geant4~~ (mojca,openmaintainer): r134132 - ~~gerbil~~ (cal,openmaintainer): r134191 - ~~glfw~~ (michaelld,openmaintainer): r134225 - ~~gr-air-modes~~ (michaelld,openmaintainer): r134241 - ~~gr-ais~~ (michaelld,openmaintainer): r134240 - ~~gr-baz~~ (michaelld,openmaintainer): r134239 - ~~gr-dvbs~~ (michaelld,openmaintainer): r134238 - ~~gr-dvbs2~~ (michaelld,openmaintainer): r134237 - ~~gr-dvbt~~ (michaelld,openmaintainer): r134236 - ~~gr-fcdproplus~~ (michaelld,openmaintainer): r134235 - ~~gr-fosphor~~ (michaelld,openmaintainer): r134233 - ~~gr-iqbalance~~ (michaelld,openmaintainer): r134232 - ~~gr-mac~~ (michaelld,openmaintainer): r134231 - ~~gr-osmosdr~~ (michaelld,openmaintainer): r134230 - ~~gr-rds~~ (michaelld,openmaintainer): r134229 - graphite2 (ryandesign,openmaintainer): - ~~hackrf~~ (michaelld,openmaintainer): r134226 - ~~iAIDA~~ (mojca,gmail.com:apfeiffer1,openmaintainer): r134134 - ~~kst~~ (nicos,openmaintainer): r134216 - ~~lensfun~~ (devans,openmaintainer): r134153 - ~~lib2geom~~ (devans,openmaintainer): r134154 - ~~libLASi~~ (takeshi,openmaintainer): r134298 - ~~libccd~~ (mmoll,openmaintainer): - libdynd (stromnov,openmaintainer): - libftdi (snc,openmaintainer): - ~~libgit2~~ (juanrgar,devans,openmaintainer): r134155 - ~~liblastfm~~ (michaelld,openmaintainer): r134242 - ~~libphonenumber-cpp~~ (devans,openmaintainer): r134156 - ~~libproxy~~ (devans,openmaintainer): r134157 - ~~libssh~~ (cal,openmaintainer): r134187 - libtuxcap (ryandesign,openmaintainer): - ~~lmms~~ (ryandesign,openmaintainer): r135968 - ~~mariadb~~ (pixilla,openmaintainer): r137069 - ~~mariadb-10.0~~ (pixilla,openmaintainer): r137069 - ~~mariadb-10.1~~ (pixilla,openmaintainer): r137069 - ~~mysql55 (pixilla,openmaintainer): r137069 - mysql55-connector-cpp (pixilla,openmaintainer): - ~~mysql56~~ (pixilla,openmaintainer): r137069 - nomacs (pvanek,openmaintainer): - oce (gmail.com:mark.brethen,openmaintainer): - openal-soft (ryandesign,openmaintainer): - openbabel (mac.com:mlund,openmaintainer): - opencv (stromnov,openmaintainer): - ~~openjpeg~~ (mcalhoun,openmaintainer): r138982 - ~~orfeotoolbox~~ (gmail.com:julien.malik,stromnov,openmaintainer): r136969 - parmetis (sean,openmaintainer): - ~~pdf2htmlex~~ (iapa.in:iapain,mojca,openmaintainer): r134135 - ~~pdfpc~~ (cal,openmaintainer): r134192 - ~~percona~~ (mac.com:quest,openmaintainer): r137069 - ~~phonon~~ (michaelld,openmaintainer): r134243 - ~~phonon-backend-gstreamer~~ (michaelld,openmaintainer): r134247 - ~~podofo~~ (devans,openmaintainer): r134159 - ~~pqp~~ (mmoll,openmaintainer): ? - py-dynd (stromnov,openmaintainer): - ~~py-pyside~~ (openmaintainer,mmoll): ? - ~~py-pyside-tools~~ (openmaintainer,mmoll): ? - ~~py-shiboken~~ (openmaintainer,mmoll): - qlipper (pvanek,openmaintainer): - quassel (sicherha,openmaintainer): - rabbitmq-c (ryandesign,openmaintainer): - rspamd (pixilla,openmaintainer): - ~~rtl-sdr~~ (michaelld,openmaintainer): r134246 - scalapack (sean,openmaintainer): - ~~scantailor~~ (raphael,openmaintainer): r148275 - sdcv (ryandesign,openmaintainer): - shogun-devel (stromnov,openmaintainer): - sigil (openmaintainer,krischik): - soci (rmh.de:g.lorenz,openmaintainer): - ~~sysdig~~ (g5pw,openmaintainer): r147845 - tagainijisho (strasweb.fr:rudloff,openmaintainer): - ~~telepathy-qt~~ (nicos,openmaintainer): r135178 - ~~tinyxml~~ (openmaintainer,mmoll): r134144 - viennacl (stromnov,openmaintainer): - ~~vramsteg~~ (raimue,openmaintainer): r134597 - vtk (stromnov,openmaintainer): - ~~weechat~~ (gmail.com:starkhalo,openmaintainer): r137362 - ~~xrootd~~ (hep.phy.cam.ac.uk:jonesc,openmaintainer): r139539 - ~~yajl~~ (gmail.com:benjaminlyu,openmaintainer): r139535 - ~~yaml-cpp~~ (the-huck.com:patrick,openmaintainer): r139538 ==== Ports with nomaintainer ==== - Cockatrice: - ~~FreeRDP~~: r135596 - Io: - ~~LucenePlusPlus~~: r141818 - ~~OpenSceneGraph~~: r146106 - ~~OpenSceneGraph-devel~~: r146109 - Vidalia: - allegro: - ~~allegro5~~: [changeset:ce43624df98dc50905f49f97ff9a21eb7f1cf117 /macports-ports ce43624d] - apiextractor: - assimp2: - ~~avidemux~~: r141390 - chemkit: - choqok: - clucene-devel: - collada-dom: - ~~cuneiform~~: r136891 - ~~cutecom-qt4-mac~~: r148651 - ebook-tools: - emergent: - ettercap: - freecell-solver: - ~~gccxml-devel~~: r148679 - generatorrunner: - ~~gl2ps~~: r135599 - ~~gmsh~~: r134173 - ~~hugin-app~~: r134470 - json_spirit: - libmsn: - libmusicbrainz3: - libplist: - ~~lua-luabitop~~: r140260 - newmat: - nifticlib: - orocos-kdl: - orocos-rtt: - osgswig-devel: - polkit-qt: - portmidi: - qfsm: - ~~scribus~~: r137847 - synergy: - synergy-devel: - ~~taglib~~: r139536 - ~~task~~: r139537 - ~~tigervnc~~: r138607 - toluapp: - usbmuxd: - ~~vrpn~~: r141020 - vtk5: - vxl: - ~~wbxml2~~: [changeset:ac51b298654028d96e94ec9479401d16d1302752 /macports-ports ac51b298] - ~~wesnoth~~: r139534 - ~~widelands~~: r153719 - ~~wxLua~~: r134469 - ~~zorba~~: r139532 === Other === - kde4-1.1.tcl: r134210 -- Comment: htcondor done in [changeset:a58ca400496b58e7643b1cd06c578ce6ca03c5be /macports-ports a58ca40049] -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 16:47:39 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 16:47:39 -0000 Subject: [MacPorts] #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') In-Reply-To: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> References: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> Message-ID: <056.9c2ba2d887db66cd196a2db03ce4274b@macports.org> #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') ---------------------+---------------------- Reporter: RJVB | Owner: kimuraw Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ruby23 | ---------------------+---------------------- Comment (by kencu): could you just delete `-pipe` from this build? {{{ :build CFLAGS = -Os -fno-common -pipe -arch x86_64 }}} I understand it just improves performance, but it is not a required flag, I believe... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 17:03:57 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 17:03:57 -0000 Subject: [MacPorts] #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') In-Reply-To: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> References: <041.a99261ec9dd2c9db59ca29cb82b94e8d@macports.org> Message-ID: <056.91292dc43ff42f8391fcf067251f81af@macports.org> #53045: ruby23 fails to build on 10.9.5 (:info:build error: unable to open output file '/dev/fd/8': '') ---------------------+---------------------- Reporter: RJVB | Owner: kimuraw Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ruby23 | ---------------------+---------------------- Comment (by RJVB): - I *think* -pipe is moot with clang, at least that compiler doesn't seem to invoke the different compilation stages as separate processes - whether or not -pipe improves performance depends on how parallel you build, and how loaded the host already is... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 17:04:53 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 17:04:53 -0000 Subject: [MacPorts] #47197: cmake-based ports: add cmake.out_of_source yes/no In-Reply-To: <042.143327c5ff7caac583f0e30b8a2e7ab1@macports.org> References: <042.143327c5ff7caac583f0e30b8a2e7ab1@macports.org> Message-ID: <057.54364d048de3b424181f0583590f8d02@macports.org> #47197: cmake-based ports: add cmake.out_of_source yes/no -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: Cockatrice Io LucenePlusPlus | OpenSceneGraph OpenSceneGraph-devel | PlasmaClient PlasmaShop TOra Vidalia allegro | allegro5 alps apbs apiextractor assimp2 | autopano-sift-c blosc bob box2d cgal charm | chemkit chipmunk choqok clucene clucene-devel | coinor-liblemon collada-dom dolfin ebook- | tools efte emergent ettercap exiv2 falcon | fann freealut freecad freecell-solver gccxml- | devel generatorrunner graphite2 indi | indi_maxdomeii json_spirit kealib libdynd | libftdi libhsplasma liblas libmsn | libmusicbrainz3 libpcl libplist libtuxcap | lua-luabitop metis mysql55-connector-cpp | newmat nifticlib nomacs oce ogre openal-soft | openbabel opencv openjpeg orocos-kdl orocos- | rtt osgswig-devel parmetis pgrouting physfs | piklab playerstage-player playerstage-stage | polkit-qt portmidi py-dynd qfsm qgis | qlandkartegt qlandkartegt-garmindev qlipper | qore-qt4-module rabbitmq-c rsgislib rspamd | scalapack scribus sdcv seqan-apps sfcgal | shogun-devel sigil soci streamlog synergy | synergy-devel sysdig tagainijisho toluapp | usbmuxd viennacl vigra vrpn vtk vtk5 vxl | wbxml2 widelands | -------------------------------------------------+------------------------- Comment (by RJVB): ports can also start migrating to the cmake 1.1 portgroup. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 17:16:01 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 17:16:01 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.ad0a879b2f26a6a633989ca3ad1b1973@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Comment (by RJVB): I'm fine with a separate port for the complete GeneralUser soundfont. I'd publish them both at the same time though. YMMV, but I find it gives much better sound quality in general than the soundfonts Debian provides. I also forgot most of the details of what I did already :-/ but I had a look at my own TiMidity port. I cannot see any patch or configuration option to have it expect its config file under ${prefix}/share/timidity so for now I *presume* that's the default. We'll take that bridge when we get to it. > So please let me know if you are OK [...] Yes. The only suggestion I have would have (which would speak for publishing both ports at once) is to integrate with the `port select` mechanism. I see that I have a symlink `000Default.sf2` in my soundfont directory which allows applications that use alphanumeric sorting of a selection of soundfont files to pick up a specific one as the preferred soundfont. Of course we can also do that later, when the exact need for this kind of thing becomes clear. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 17:46:44 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 17:46:44 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.73b0418aad8ff2b405d7024860aee9b9@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Comment (by mojca): Replying to [comment:13 RJVB]: > I'm fine with a separate port for the complete GeneralUser soundfont. I'd publish them both at the same time though. Fine with me. > YMMV, but I find it gives much better sound quality in general than the soundfonts Debian provides. I have no clue what Debian provides, so this doesn't help me in any way :) > I also forgot most of the details of what I did already :-/ but I had a look at my own TiMidity port. I cannot see any patch or configuration option to have it expect its config file under ${prefix}/share/timidity so for now I *presume* that's the default. We'll take that bridge when we get to it. It seems to use `/opt/local/share/timidity/timidity.cfg` here. I didn't test anything else. > Yes. The only suggestion I have would have (which would speak for publishing both ports at once) is to integrate with the `port select` mechanism. What would be the options? If we use `port select`, then I don't understand what happens if none is selected. If we are talking about selecting the font for TiMidity, we could create a port `timidity-config +freepats [+]fluid` that would only install a single configuration file. > I see that I have a symlink `000Default.sf2` in my soundfont directory which allows applications that use alphanumeric sorting of a selection of soundfont files to pick up a specific one as the preferred soundfont. I don't understand what this does and how it works. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 18:33:58 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 18:33:58 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.16031eed378352ad6ddb12394e643d4f@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Comment (by RJVB): Replying to [comment:14 mojca]: > > YMMV, but I find it gives much better sound quality in general than the soundfonts Debian provides. > > I have no clue what Debian provides, so this doesn't help me in any way :) The ones from your current port, which are the soundfonts Debian provide in their fluid-soundfont package :) > It seems to use `/opt/local/share/timidity/timidity.cfg` here. I didn't test anything else. Same here. > What would be the options? If we use `port select`, then I don't understand what happens if none is selected. If we are talking about selecting the font for TiMidity, we could create a port `timidity-config +freepats [+]fluid` that would only install a single configuration file. Just like with other ports the selection mechanism would allow to select a default soundfont from among the installed soundfonts, in such a way that you can get the soundfont you want in all situations. I think qsynth was the reason I created the symlink: it take a soundfont path, and then seems to use the file in there that comes first in standard alphanumeric sorting. > I don't understand what this does and how it works. I'm not thinking very straight today, is the explanation above clearer? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 18:49:28 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 18:49:28 -0000 Subject: [MacPorts] #53071: Upgrade to ImageMagick is failing Message-ID: <047.58efd3a8040fb4edd34c241e7b693a28@macports.org> #53071: Upgrade to ImageMagick is failing ------------------------+----------------- Reporter: pcollinson | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: ------------------------+----------------- ~# port clean --dist ImageMagick ---> Cleaning ImageMagick ~# port -u upgrade outdated ---> Computing dependencies for ImageMagick ---> Fetching archive for ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6_0+x11.darwin_15.x86_64.tbz2 from https://packages.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6_0+x11.darwin_15.x86_64.tbz2 from http://nue.de.packages.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6_0+x11.darwin_15.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/ImageMagick ---> Fetching distfiles for ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from https://distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://lil.fr.distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://mirror.checkdomain.de/imagemagick/ ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://nue.de.distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://osl.no.distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from ftp://sunsite.icm.edu.pl/packages/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://fco.it.distfiles.macports.org/mirrors/macports- distfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from ftp://ftp.sunet.se/pub/multimedia/graphics/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://www.imagemagick.org/download/ ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://sea.us.distfiles.macports.org/macports/distfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://jnb.za.distfiles.macports.org/distfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://jog.id.distfiles.macports.org/macports/distfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://cjj.kr.distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from https://pek.cn.distfiles.macports.org/macports/distfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from ftp://ftp.u-aizu.ac.jp/pub/graphics/image/ImageMagick/imagemagick.org/ ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://her.gr.distfiles.macports.org/ImageMagick Error: org.macports.fetch for port ImageMagick returned: fetch failed Please see the log file for port ImageMagick for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_ImageMagick/ImageMagick/main.log Error: Unable to upgrade port: 1 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Something appears to be missing -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 19:22:50 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 19:22:50 -0000 Subject: [MacPorts] #47197: cmake-based ports: add cmake.out_of_source yes/no In-Reply-To: <042.143327c5ff7caac583f0e30b8a2e7ab1@macports.org> References: <042.143327c5ff7caac583f0e30b8a2e7ab1@macports.org> Message-ID: <057.ae3b23e644947caf6f3a825383db1425@macports.org> #47197: cmake-based ports: add cmake.out_of_source yes/no -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: Cockatrice Io LucenePlusPlus | OpenSceneGraph OpenSceneGraph-devel | PlasmaClient PlasmaShop TOra Vidalia allegro | allegro5 alps apbs apiextractor assimp2 | autopano-sift-c blosc bob box2d cgal charm | chemkit chipmunk choqok clucene clucene-devel | coinor-liblemon collada-dom dolfin ebook- | tools efte emergent ettercap exiv2 falcon | fann freealut freecad freecell-solver gccxml- | devel generatorrunner graphite2 indi | indi_maxdomeii json_spirit kealib libdynd | libftdi libhsplasma liblas libmsn | libmusicbrainz3 libpcl libplist libtuxcap | lua-luabitop metis mysql55-connector-cpp | newmat nifticlib nomacs oce ogre openal-soft | openbabel opencv openjpeg orocos-kdl orocos- | rtt osgswig-devel parmetis pgrouting physfs | piklab playerstage-player playerstage-stage | polkit-qt portmidi py-dynd qfsm qgis | qlandkartegt qlandkartegt-garmindev qlipper | qore-qt4-module rabbitmq-c rsgislib rspamd | scalapack scribus sdcv seqan-apps sfcgal | shogun-devel sigil soci streamlog synergy | synergy-devel sysdig tagainijisho toluapp | usbmuxd viennacl vigra vrpn vtk vtk5 vxl | wbxml2 widelands | -------------------------------------------------+------------------------- Comment (by larryv): I would recommend against this until we nail the new API down. Off-topic, anyway. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 19:42:00 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 19:42:00 -0000 Subject: [MacPorts] #47197: cmake-based ports: add cmake.out_of_source yes/no In-Reply-To: <042.143327c5ff7caac583f0e30b8a2e7ab1@macports.org> References: <042.143327c5ff7caac583f0e30b8a2e7ab1@macports.org> Message-ID: <057.325ed1339a3f5a97dab522b7e69b3df5@macports.org> #47197: cmake-based ports: add cmake.out_of_source yes/no -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: Cockatrice Io LucenePlusPlus | OpenSceneGraph OpenSceneGraph-devel | PlasmaClient PlasmaShop TOra Vidalia allegro | allegro5 alps apbs apiextractor assimp2 | autopano-sift-c blosc bob box2d cgal charm | chemkit chipmunk choqok clucene clucene-devel | coinor-liblemon collada-dom dolfin ebook- | tools efte emergent ettercap exiv2 falcon | fann freealut freecad freecell-solver gccxml- | devel generatorrunner graphite2 indi | indi_maxdomeii json_spirit kealib libdynd | libftdi libhsplasma liblas libmsn | libmusicbrainz3 libpcl libplist libtuxcap | lua-luabitop metis mysql55-connector-cpp | newmat nifticlib nomacs oce ogre openal-soft | openbabel opencv openjpeg orocos-kdl orocos- | rtt osgswig-devel parmetis pgrouting physfs | piklab playerstage-player playerstage-stage | polkit-qt portmidi py-dynd qfsm qgis | qlandkartegt qlandkartegt-garmindev qlipper | qore-qt4-module rabbitmq-c rsgislib rspamd | scalapack scribus sdcv seqan-apps sfcgal | shogun-devel sigil soci streamlog synergy | synergy-devel sysdig tagainijisho toluapp | usbmuxd viennacl vigra vrpn vtk vtk5 vxl | wbxml2 widelands | -------------------------------------------------+------------------------- Comment (by RJVB): Not really; new features aside the v1.1 PG sets cmake.out_of_source, and that's about all it does if you don't use the new API. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 23:59:39 2016 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2016 23:59:39 -0000 Subject: [MacPorts] #46658: pulseaudio @5.0_1: builds but doesn't work In-Reply-To: <041.d843686d1e126a9748538f8890c8a09e@macports.org> References: <041.d843686d1e126a9748538f8890c8a09e@macports.org> Message-ID: <056.f4f8ae6fcd0ea26fa508a15daf997d9e@macports.org> #46658: pulseaudio @5.0_1: builds but doesn't work -------------------------+-------------------- Reporter: RJVB | Owner: Ionic Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: fixed | Keywords: Port: pulseaudio | -------------------------+-------------------- Comment (by kencu): Hi, I bumped into an error that seems to be much like this one today while trying out a new port I'm working on that uses this. {{{ $ port -v installed pulseaudio pulseaudio @9.0_1+x11 (active) platform='darwin 10' archs='x86_64' }}} {{{ $ pulseaudio W: [] caps.c: Normally all extra capabilities would be dropped now, but that's impossible because PulseAudio was built without capabilities support. Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory W: [] pid.c: Stale PID file, overwriting. pulseaudio(51409,0x7fff71106cc0) malloc: *** error for object 0x1008404d8: pointer being freed was not allocated *** set a breakpoint in malloc_error_break to debug Abort trap }}} {{{ rocess: pulseaudio [51426] Path: /opt/local/bin/pulseaudio Identifier: pulseaudio Version: ??? (???) Code Type: X86-64 (Native) Parent Process: pulseaudio [51425] Date/Time: 2016-12-14 15:54:10.223 -0800 OS Version: Mac OS X 10.6.8 (10K549) Report Version: 6 Interval Since Last Report: 137823 sec Crashes Since Last Report: 10 Per-App Crashes Since Last Report: 9 Anonymous UUID: A3B3F8DB-9F61-4B79-884D-3BB3BE6151F5 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Application Specific Information: abort() called Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 libSystem.B.dylib 0x00007fff8988f0b6 __kill + 10 1 libSystem.B.dylib 0x00007fff8992f9f6 abort + 83 2 libSystem.B.dylib 0x00007fff89847195 free + 128 3 libpulse.0.dylib 0x00000001000e88de pa_xfree + 31 4 module-coreaudio-device.so 0x0000000100aec5f1 ca_device_create_streams + 2271 5 module-coreaudio-device.so 0x0000000100aebae9 module_coreaudio_device_LTX_pa__init + 852 6 libpulsecore-9.0.dylib 0x0000000100036632 pa_module_load + 474 7 module-coreaudio-detect.so 0x0000000100a8d11a ca_update_device_list + 654 8 module-coreaudio-detect.so 0x0000000100a8ccbb module_coreaudio_detect_LTX_pa__init + 367 9 libpulsecore-9.0.dylib 0x0000000100036632 pa_module_load + 474 10 libpulsecore-9.0.dylib 0x0000000100026200 pa_cli_command_load + 146 11 libpulsecore-9.0.dylib 0x0000000100024136 pa_cli_command_execute_line_stateful + 563 12 libpulsecore-9.0.dylib 0x0000000100024869 pa_cli_command_execute_file_stream + 165 13 pulseaudio 0x000000010000db66 main + 7794 14 pulseaudio 0x0000000100007754 start + 52 }}} I presume this is using dbus, which seems to be running {{{ $ sudo launchctl load -w /Library/LaunchDaemons/org.freedesktop.dbus- system.plist org.freedesktop.dbus-system: Already loaded }}} Not completely sure where to go with this next... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 00:00:45 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 00:00:45 -0000 Subject: [MacPorts] #53072: chromaprint @1.4.0: default build fails on 10.8 and earlier due to inclusion of C++11 header Message-ID: <044.a96bc61b1ea83cf3406c5aadf3f008e3@macports.org> #53072: chromaprint @1.4.0: default build fails on 10.8 and earlier due to inclusion of C++11 header ---------------------+---------------------------- Reporter: dbevans | Owner: kurthindenburg Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: chromaprint ---------------------+---------------------------- Build on 10.8 fails as follows (using default libstdc++) {{{ :info:build [ 50%] Building CXX object src/CMakeFiles/chromaprint_objs.dir/image_builder.cpp.o :info:build cd /opt/local/var/macports/build/_Volumes_MiniHD_opt_github .com_macports_macports-ports_audio_chromaprint/chromaprint/work/build/src && /usr/bin/clang++ -DHAVE_CONFIG_H -D_SCL_SECURE_NO_WARNINGS -D_USE_MATH_DEFINES -D__STDC_CONSTANT_MACROS -D__STDC_LIMIT_MACROS -I/opt/local/var/macports/build/_Volumes_MiniHD_opt_github .com_macports_macports-ports_audio_chromaprint/chromaprint/work/build -I/opt/local/var/macports/build/_Volumes_MiniHD_opt_github .com_macports_macports- ports_audio_chromaprint/chromaprint/work/chromaprint-1.4/src -I/opt/local/include -pipe -Os -stdlib=libstdc++ -std=c++11 -DNDEBUG -arch x86_64 -mmacosx-version-min=10.8 -fPIC -o CMakeFiles/chromaprint_objs.dir/image_builder.cpp.o -c /opt/local/var/macports/build/_Volumes_MiniHD_opt_github .com_macports_macports- ports_audio_chromaprint/chromaprint/work/chromaprint-1.4/src/image_builder.cpp :info:build In file included from /opt/local/var/macports/build/_Volumes_MiniHD_opt_github .com_macports_macports- ports_audio_chromaprint/chromaprint/work/chromaprint-1.4/src/fingerprinter.cpp:9: :info:build In file included from /opt/local/var/macports/build/_Volumes_MiniHD_opt_github .com_macports_macports- ports_audio_chromaprint/chromaprint/work/chromaprint-1.4/src/fft.h:13: :info:build /opt/local/var/macports/build/_Volumes_MiniHD_opt_github .com_macports_macports- ports_audio_chromaprint/chromaprint/work/chromaprint-1.4/src/audio/audio_slicer.h:8:10: fatal error: 'cstdint' file not found :info:build #include :info:build ^ :info:build 1 error generated. }}} Because of the inclusion of this C++11 header libc++ is required instead and, in fact, -std=c++11 is declared as a build argument. Suggest using PortGroup cxx11 to clarify this issue and to point to the solution on the earlier platforms. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 00:02:38 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 00:02:38 -0000 Subject: [MacPorts] #53073: py35-ipython @5.1.0 does not run on a PPC running OSX 10.5.8 Message-ID: <048.d3c18f2ad6bd73d631225d7e831c4a07@macports.org> #53073: py35-ipython @5.1.0 does not run on a PPC running OSX 10.5.8 ---------------------------------------+-------------------------- Reporter: josephsacco | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: ipython3, OSX 10.5.8, PPC | Port: py35-ipython ---------------------------------------+-------------------------- See output below. -Joseph -------------- $ipython3 --log-level=DEBUG [TerminalIPythonApp] IPYTHONDIR set to: /Users/jsacco/.ipython[[BR]] [TerminalIPythonApp] Created profile dir: '/Users/jsacco/.ipython/profile_default'[[BR]] [TerminalIPythonApp] Searching path ['/Users/jsacco', '/Users/jsacco/.ipython/profile_default', '/usr/local/etc/ipython', '/etc/ipython'] for config files[[BR]] [TerminalIPythonApp] Attempting to load config file: ipython_config.py[[BR]] [TerminalIPythonApp] Looking for ipython_config in /etc/ipython[[BR]] [TerminalIPythonApp] Looking for ipython_config in /usr/local/etc/ipython[[BR]] [TerminalIPythonApp] Looking for ipython_config in /Users/jsacco/.ipython/profile_default[[BR]] [TerminalIPythonApp] Looking for ipython_config in /Users/jsacco[[BR]] Python 3.5.2 (default, Oct 11 2016, 15:44:53) Type "copyright", "credits" or "license" for more information. IPython 5.1.0 -- An enhanced Interactive Python. ? -> Introduction and overview of IPython's features. %quickref -> Quick reference. help -> Python's own help system. object? -> Details about 'object', use 'object??' for extra details. [TerminalIPythonApp] Loading IPython extensions... [TerminalIPythonApp] Loading IPython extension: storemagic [TerminalIPythonApp] Starting IPython's mainloop... In [1]: Traceback (most recent call last): File "/opt/local/bin/ipython3", line 5, in start_ipython() File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 /site-packages/IPython/__init__.py", line 119, in start_ipython return launch_new_instance(argv=argv, **kwargs) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 /site-packages/traitlets/config/application.py", line 658, in launch_instance app.start() File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 /site-packages/IPython/terminal/ipapp.py", line 348, in start self.shell.mainloop() File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 /site-packages/IPython/terminal/interactiveshell.py", line 440, in mainloop self.interact() File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 /site-packages/IPython/terminal/interactiveshell.py", line 423, in interact code = self.prompt_for_code() File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 /site-packages/IPython/terminal/interactiveshell.py", line 333, in prompt_for_code pre_run=self.pre_prompt, reset_current_buffer=True) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 /site-packages/prompt_toolkit/interface.py", line 394, in run self.eventloop.run(self.input, self.create_eventloop_callbacks()) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 /site-packages/prompt_toolkit/eventloop/posix.py", line 92, in run self.add_reader(stdin, read_from_stdin) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 /site-packages/prompt_toolkit/eventloop/posix.py", line 273, in add_reader self.selector.register(fd) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 /site-packages/prompt_toolkit/eventloop/select.py", line 75, in register sel.register(fd) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 /site-packages/prompt_toolkit/eventloop/select.py", line 130, in register self._sel.register(fd, selectors.EVENT_READ, None) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/selectors.py", line 536, in register self._kqueue.control([kev], 0, 0) OSError: [Errno 45] Operation not supported -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 00:03:21 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 00:03:21 -0000 Subject: [MacPorts] #53072: chromaprint @1.4.0: default build fails on 10.8 and earlier due to inclusion of C++11 header In-Reply-To: <044.a96bc61b1ea83cf3406c5aadf3f008e3@macports.org> References: <044.a96bc61b1ea83cf3406c5aadf3f008e3@macports.org> Message-ID: <059.7d30ff053d71b7de23c409f34ec0b9fd@macports.org> #53072: chromaprint @1.4.0: default build fails on 10.8 and earlier due to inclusion of C++11 header --------------------------+---------------------------- Reporter: dbevans | Owner: kurthindenburg Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: chromaprint | --------------------------+---------------------------- Changes (by dbevans): * Attachment "main.log" added. Log showing build failure on 10.8 and earlier -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 01:13:19 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 01:13:19 -0000 Subject: [MacPorts] #53060: ImageMagick, p5.24-perlmagick: fetch failed, files missing from server (was: p5.24-perlmagick: fetch failed, files missing from server) In-Reply-To: <048.ba240fc1d79cfe36bf3172475e943def@macports.org> References: <048.ba240fc1d79cfe36bf3172475e943def@macports.org> Message-ID: <063.f6cb62a9125b2c1852ecbb105ee532c1@macports.org> #53060: ImageMagick, p5.24-perlmagick: fetch failed, files missing from server -----------------------------------------+------------------------ Reporter: PBainbridge | Owner: ryandesign Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: ImageMagick, p5-perlmagick | -----------------------------------------+------------------------ Changes (by ryandesign): * owner: astricker@… => ryandesign * cc: ryandesign (removed) * cc: pcollinson (added) * status: assigned => accepted * port: p5-perlmagick => ImageMagick, p5-perlmagick Comment: Has duplicate #53071. Looks like the developers updated ImageMagick to a new version, and removed the old version from their servers. Meanwhile, we have not yet brought distfile mirroring online on the new MacPorts servers since moving away from macOS forge, so we did not mirror the old files. I manually added the distfile to our server now. It should show up on MacPorts mirrors within an hour or two. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 01:13:35 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 01:13:35 -0000 Subject: [MacPorts] #53071: Upgrade to ImageMagick is failing In-Reply-To: <047.58efd3a8040fb4edd34c241e7b693a28@macports.org> References: <047.58efd3a8040fb4edd34c241e7b693a28@macports.org> Message-ID: <062.cf40a2ac124a0499650a608a6dcb38e7@macports.org> #53071: Upgrade to ImageMagick is failing --------------------------+------------------------ Reporter: pcollinson | Owner: ryandesign Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ImageMagick | --------------------------+------------------------ Changes (by ryandesign): * owner: => ryandesign * status: new => accepted * port: => ImageMagick Old description: > ~# port clean --dist ImageMagick > ---> Cleaning ImageMagick > ~# port -u upgrade outdated > ---> Computing dependencies for ImageMagick > ---> Fetching archive for ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6_0+x11.darwin_15.x86_64.tbz2 > from https://packages.macports.org/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6_0+x11.darwin_15.x86_64.tbz2 > from http://nue.de.packages.macports.org/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6_0+x11.darwin_15.x86_64.tbz2 > from > http://mse.uk.packages.macports.org/sites/packages.macports.org/ImageMagick > ---> Fetching distfiles for ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > https://distfiles.macports.org/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://lil.fr.distfiles.macports.org/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://mirror.checkdomain.de/imagemagick/ > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://nue.de.distfiles.macports.org/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://osl.no.distfiles.macports.org/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > ftp://sunsite.icm.edu.pl/packages/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://fco.it.distfiles.macports.org/mirrors/macports- > distfiles/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > ftp://ftp.sunet.se/pub/multimedia/graphics/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://www.imagemagick.org/download/ > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://sea.us.distfiles.macports.org/macports/distfiles/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://jnb.za.distfiles.macports.org/distfiles/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://jog.id.distfiles.macports.org/macports/distfiles/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://cjj.kr.distfiles.macports.org/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > https://pek.cn.distfiles.macports.org/macports/distfiles/ImageMagick > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > ftp://ftp.u-aizu.ac.jp/pub/graphics/image/ImageMagick/imagemagick.org/ > ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from > http://her.gr.distfiles.macports.org/ImageMagick > Error: org.macports.fetch for port ImageMagick returned: fetch failed > Please see the log file for port ImageMagick for details: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_ImageMagick/ImageMagick/main.log > Error: Unable to upgrade port: 1 > To report a bug, follow the instructions in the guide: > http://guide.macports.org/#project.tickets > > Something appears to be missing New description: {{{ ~# port clean --dist ImageMagick ---> Cleaning ImageMagick ~# port -u upgrade outdated ---> Computing dependencies for ImageMagick ---> Fetching archive for ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6_0+x11.darwin_15.x86_64.tbz2 from https://packages.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6_0+x11.darwin_15.x86_64.tbz2 from http://nue.de.packages.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6_0+x11.darwin_15.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/ImageMagick ---> Fetching distfiles for ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from https://distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://lil.fr.distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://mirror.checkdomain.de/imagemagick/ ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://nue.de.distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://osl.no.distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from ftp://sunsite.icm.edu.pl/packages/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://fco.it.distfiles.macports.org/mirrors/macports- distfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from ftp://ftp.sunet.se/pub/multimedia/graphics/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://www.imagemagick.org/download/ ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://sea.us.distfiles.macports.org/macports/distfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://jnb.za.distfiles.macports.org/distfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://jog.id.distfiles.macports.org/macports/distfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://cjj.kr.distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from https://pek.cn.distfiles.macports.org/macports/distfiles/ImageMagick ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from ftp://ftp.u-aizu.ac.jp/pub/graphics/image/ImageMagick/imagemagick.org/ ---> Attempting to fetch ImageMagick-6.9.6-6.tar.xz from http://her.gr.distfiles.macports.org/ImageMagick Error: org.macports.fetch for port ImageMagick returned: fetch failed Please see the log file for port ImageMagick for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_ImageMagick/ImageMagick/main.log Error: Unable to upgrade port: 1 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets }}} Something appears to be missing -- Comment: Duplicate of #53060. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 01:13:42 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 01:13:42 -0000 Subject: [MacPorts] #53071: Upgrade to ImageMagick is failing In-Reply-To: <047.58efd3a8040fb4edd34c241e7b693a28@macports.org> References: <047.58efd3a8040fb4edd34c241e7b693a28@macports.org> Message-ID: <062.5675d138157ba5ba6fb6b111110bca51@macports.org> #53071: Upgrade to ImageMagick is failing --------------------------+------------------------ Reporter: pcollinson | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: duplicate | Keywords: Port: ImageMagick | --------------------------+------------------------ Changes (by ryandesign): * status: accepted => closed * resolution: => duplicate -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 01:23:03 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 01:23:03 -0000 Subject: [MacPorts] #52845: mpv: update to 0.22 In-Reply-To: <043.e673edb81f111939a6207eb0205e5927@macports.org> References: <043.e673edb81f111939a6207eb0205e5927@macports.org> Message-ID: <058.9ca2b198b39be7aba6289341127c7a1c@macports.org> #52845: mpv: update to 0.22 ---------------------+---------------------- Reporter: iMiKED | Owner: Ionic Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: mpv | ---------------------+---------------------- Comment (by Ionic): ... and I'm still updating my VM. It ran into an error upgrading GCC 6, so I'll have to clean and restart this. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 03:59:31 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 03:59:31 -0000 Subject: [MacPorts] #53060: ImageMagick, p5.24-perlmagick: fetch failed, files missing from server In-Reply-To: <048.ba240fc1d79cfe36bf3172475e943def@macports.org> References: <048.ba240fc1d79cfe36bf3172475e943def@macports.org> Message-ID: <063.be2ad750b11fb9d80e6e2dc5e07a2763@macports.org> #53060: ImageMagick, p5.24-perlmagick: fetch failed, files missing from server -----------------------------------------+------------------------ Reporter: PBainbridge | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: ImageMagick, p5-perlmagick | -----------------------------------------+------------------------ Changes (by ryandesign): * status: accepted => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 06:12:46 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 06:12:46 -0000 Subject: [MacPorts] #51411: mlt: qt5 subport In-Reply-To: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> References: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> Message-ID: <056.d5b511a3aeac12c035737c77fa332757@macports.org> #51411: mlt: qt5 subport --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: mlt | --------------------------+---------------------- Changes (by ddennedy): * Attachment "mlt-Portfile-6.4.1.diff" added. update to 6.4.1 and add mlt-qt5 subport -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 06:17:24 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 06:17:24 -0000 Subject: [MacPorts] #51411: mlt: qt5 subport In-Reply-To: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> References: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> Message-ID: <056.10044e1caaae7e8355e6e4e4fa6532e1@macports.org> #51411: mlt: qt5 subport --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: mlt | --------------------------+---------------------- Comment (by ddennedy): Yes, the global declaration fixed it. I do not have push permission; so, I uploaded a new patch file that includes everything: mlt- Portfile-6.4.1.diff. I also successfully built mlt-qt5 and did some basic testing of it. I approve this change to be committed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 08:26:05 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 08:26:05 -0000 Subject: [MacPorts] #51411: mlt: qt5 subport In-Reply-To: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> References: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> Message-ID: <056.08dbb6b394a94d0960000e13fe1ecb33@macports.org> #51411: mlt: qt5 subport --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: mlt | --------------------------+---------------------- Comment (by RJVB): Perfect, thanks! David, if you're seeing this, maybe you can commit the patch like you did the 2 previous changes (if Marko doesn't beat you to it)? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 08:38:14 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 08:38:14 -0000 Subject: [MacPorts] #46658: pulseaudio @5.0_1: builds but doesn't work In-Reply-To: <041.d843686d1e126a9748538f8890c8a09e@macports.org> References: <041.d843686d1e126a9748538f8890c8a09e@macports.org> Message-ID: <056.52fd004bf2e915d7166be02c0a1ac121@macports.org> #46658: pulseaudio @5.0_1: builds but doesn't work -------------------------+---------------------- Reporter: RJVB | Owner: Ionic Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: pulseaudio | -------------------------+---------------------- Changes (by RJVB): * status: closed => reopened * resolution: fixed => Comment: I'm reopening the ticket for you, but you probably ought to be opening a new ticket for this issue. It is indeed related but apparently due to another issue: {{{ Dynamic session lookup supported but failed: Unable to find launchd socket when setuid }}} What does `ls -l /opt/local/bin/pulseaudio` tell, has it indeed been installed suid root? Checking on a Linux box (KaOS, to be sure it uses an up-to-date version) I note that that's not the case there; the audio daemon runs under my own UID, without any special permissions. Mac OS is a different beast, but I wouldn't expect it to require special privileges to play sound, much less so than on Linux (and even there it's rarely necessary). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 10:25:38 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 10:25:38 -0000 Subject: [MacPorts] #53036: [Port New] libchewing In-Reply-To: <042.8b452ee8a9de3a161a300385f4be9866@macports.org> References: <042.8b452ee8a9de3a161a300385f4be9866@macports.org> Message-ID: <057.83243e69cdb1a80b8488c811ccfe3777@macports.org> #53036: [Port New] libchewing -------------------------+-------------------- Reporter: cwlin | Owner: cwlin Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: libchewing | -------------------------+-------------------- Changes (by cwlin): * status: new => closed * owner: => cwlin * resolution: => fixed Comment: In [changeset:"d33c02597eb3487f8d0cba3a33b5a0b4470f8a7f/macports-ports" d33c0259/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="d33c02597eb3487f8d0cba3a33b5a0b4470f8a7f" libchewing: new port The intelligent phonetic input method library The Chewing is an intelligent phonetic (Zhuyin/Bopomofo) input method, one of the most popular choices for Traditional Chinese users. Chewing was inspired by other proprietary intelligent Zhuyin input methods under Microsoft Windows, namely, Wang-Xin by Eten, Microsoft New Zhuyin, and Nature Zhuyin. Closes: https://trac.macports.org/ticket/53036 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 10:27:42 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 10:27:42 -0000 Subject: [MacPorts] #53036: [Port New] libchewing In-Reply-To: <042.8b452ee8a9de3a161a300385f4be9866@macports.org> References: <042.8b452ee8a9de3a161a300385f4be9866@macports.org> Message-ID: <057.e26c0422d80ec3cb575e10dff9c1f58a@macports.org> #53036: [Port New] libchewing -------------------------+-------------------- Reporter: cwlin | Owner: cwlin Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: libchewing | -------------------------+-------------------- Comment (by mojca): I'm not sure about the best category for this port. I kept devel as suggested in the Portfile, but it would make sense to pick something more linguistic-related. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 10:32:31 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 10:32:31 -0000 Subject: [MacPorts] #52785: ldas-tools-diskcacheAPI 2.5.5 Updated to latest source version In-Reply-To: <043.5f1f1824d62352ee370943c8a93d8c18@macports.org> References: <043.5f1f1824d62352ee370943c8a93d8c18@macports.org> Message-ID: <058.347ac58c2dc17d01dccf51756093320c@macports.org> #52785: ldas-tools-diskcacheAPI 2.5.5 Updated to latest source version --------------------------------------+--------------------------------- Reporter: emaros | Owner: skymoo Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch maintainer Port: lads-tools-diskcacheAPI | --------------------------------------+--------------------------------- Changes (by mojca): * status: accepted => closed * resolution: => fixed Comment: This was committed in [changeset:444386ca2d9abec3af17fb593f60109f4844b670 /macports-ports 444386ca]. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 11:32:09 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 11:32:09 -0000 Subject: [MacPorts] #53074: clhep @2.3.4.3: fails to build on 10.6 due to unsupported thread-local storage Message-ID: <042.0205aeab538e072ac2276e831976977b@macports.org> #53074: clhep @2.3.4.3: fails to build on 10.6 due to unsupported thread-local storage -------------------------+------------------- Reporter: mojca | Owner: mojca Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: snowleopard | Port: clhep -------------------------+------------------- {{{ /path/to/clhep/work/build/CLHEP/Random/DoubConv.hh:51:10: error: thread- local storage is not supported for the current target static CLHEP_THREAD_LOCAL bool byte_order_known; ^ }}} Upstream ticket: * https://its.cern.ch/jira/projects/CLHEP/issues/CLHEP-140 Full log: * https://build.macports.org/builders/ports-10.6_x86_64_legacy- builder/builds/13075/ See also: #44062 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 11:39:53 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 11:39:53 -0000 Subject: [MacPorts] #51620: py-pyqt5: fix DBus module build and pyversion conflicts, support multiple Qt5 ports In-Reply-To: <041.878bbad1021a18186c191e6780e8baed@macports.org> References: <041.878bbad1021a18186c191e6780e8baed@macports.org> Message-ID: <056.6cf132cce1f8485db81783de544e31b9@macports.org> #51620: py-pyqt5: fix DBus module build and pyversion conflicts, support multiple Qt5 ports --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-pyqt5 | --------------------------+---------------------- Comment (by mojca): See also #52500. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 11:42:53 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 11:42:53 -0000 Subject: [MacPorts] #52500: py-pyqt5 @5.6: conflict between Python versions In-Reply-To: <044.d13f04b961b76931b075833a7608276a@macports.org> References: <044.d13f04b961b76931b075833a7608276a@macports.org> Message-ID: <059.7c0e3031e71809d4b11b4e42f7951b82@macports.org> #52500: py-pyqt5 @5.6: conflict between Python versions -----------------------+--------------------------------- Reporter: dliessi | Owner: mamoll Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: py-pyqt5 | -----------------------+--------------------------------- Changes (by mojca): * cc: mkae, RJVB (added) Comment: See also #51620. I would commit this, it's just that I'm unable to test it at the moment (being too lazy to upgrade my OS and having issues with building some of the Qt5 dependencies). Marko? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 11:55:00 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 11:55:00 -0000 Subject: [MacPorts] #51520: llvm-3.9 @3.9-r270400_0+assertions+debug build failure on snow leopard due to missing strnlen function - and fix In-Reply-To: <067.fcaa7e4195b6cce47cbccee919b1a2f0@macports.org> References: <067.fcaa7e4195b6cce47cbccee919b1a2f0@macports.org> Message-ID: <082.e6dce83a2056aa6d9b2464a3ddf2a8b7@macports.org> #51520: llvm-3.9 @3.9-r270400_0+assertions+debug build failure on snow leopard due to missing strnlen function - and fix -------------------------------------+------------------------- Reporter: kenneth.f.cunningham@… | Owner: jeremyhu Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: snowleopard Port: llvm-3.9 clang-3.9 | -------------------------------------+------------------------- Changes (by mojca): * port: llvm-3.9 => llvm-3.9 clang-3.9 Comment: I added `clang-3.9` to the list of ports. Even though this is not exact, it's affected and users (me included) might search for open tickets for clang-3.9 without success (forgetting about existence of llvm). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 11:59:15 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 11:59:15 -0000 Subject: [MacPorts] #53068: Building kerberos5 with LibreSSL broken In-Reply-To: <042.c91362ad9f23e6c506c532e237484343@macports.org> References: <042.c91362ad9f23e6c506c532e237484343@macports.org> Message-ID: <057.e925fb6cd5a4c497329c38f237e628c7@macports.org> #53068: Building kerberos5 with LibreSSL broken ------------------------+------------------------ Reporter: H3ik0 | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: duplicate | Keywords: Port: kerberos5 | ------------------------+------------------------ Changes (by ryandesign): * status: assigned => closed * resolution: => duplicate Comment: Duplicate of #53017. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 12:01:49 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 12:01:49 -0000 Subject: [MacPorts] #53017: kerberos5 @1.15: build fails with libressl (was: kerberos5 fails to build on Yosemite with libressl) In-Reply-To: <045.2e6d5c80e4930d3d8f0c88d93b24a25b@macports.org> References: <045.2e6d5c80e4930d3d8f0c88d93b24a25b@macports.org> Message-ID: <060.8c8b18880270447c1a8603a4c68184b6@macports.org> #53017: kerberos5 @1.15: build fails with libressl ------------------------+------------------------ Reporter: bK4gYuRo | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: kerberos5 | ------------------------+------------------------ Changes (by ryandesign): * cc: H3ik0, jeremyhu (added) Comment: Has duplicate #53068. > Does LibreSSL have plans to be API compatible with OpenSSL 1.1? Otherwise, the SSL ports are problematic for port dependencies. Sounds like a question to ask the developers of libressl. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 12:37:02 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 12:37:02 -0000 Subject: [MacPorts] #52500: py-pyqt5 @5.6: conflict between Python versions In-Reply-To: <044.d13f04b961b76931b075833a7608276a@macports.org> References: <044.d13f04b961b76931b075833a7608276a@macports.org> Message-ID: <059.4be4fed45ee387da9bc7c8fb9f09d062@macports.org> #52500: py-pyqt5 @5.6: conflict between Python versions -----------------------+--------------------------------- Reporter: dliessi | Owner: mamoll Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: py-pyqt5 | -----------------------+--------------------------------- Comment (by dliessi): I'm sorry I never answered to comment:2, but I haven't yet had the chance to test the change. I'll manage to be near the 10.11 machine tonight and test the patch. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 12:44:35 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 12:44:35 -0000 Subject: [MacPorts] #53073: py35-ipython @5.1.0 does not run on a PPC running OSX 10.5.8 In-Reply-To: <048.d3c18f2ad6bd73d631225d7e831c4a07@macports.org> References: <048.d3c18f2ad6bd73d631225d7e831c4a07@macports.org> Message-ID: <063.a4659e46ea98cd185befef2e1d0fae4d@macports.org> #53073: py35-ipython @5.1.0 does not run on a PPC running OSX 10.5.8 ---------------------------+------------------------------ Reporter: josephsacco | Owner: lpsinger Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: leopard, powerpc Port: py35-ipython | ---------------------------+------------------------------ Changes (by ryandesign): * cc: seanfarley, stromnov (added) * status: new => assigned * owner: => lpsinger * keywords: ipython3, OSX 10.5.8, PPC => leopard, powerpc Old description: > See output below. > > -Joseph > > -------------- > $ipython3 --log-level=DEBUG > > [TerminalIPythonApp] IPYTHONDIR set to: /Users/jsacco/.ipython[[BR]] > > [TerminalIPythonApp] Created profile dir: > '/Users/jsacco/.ipython/profile_default'[[BR]] > > [TerminalIPythonApp] Searching path ['/Users/jsacco', > '/Users/jsacco/.ipython/profile_default', '/usr/local/etc/ipython', > '/etc/ipython'] for config files[[BR]] > > [TerminalIPythonApp] Attempting to load config file: > ipython_config.py[[BR]] > > [TerminalIPythonApp] Looking for ipython_config in /etc/ipython[[BR]] > > [TerminalIPythonApp] Looking for ipython_config in > /usr/local/etc/ipython[[BR]] > > [TerminalIPythonApp] Looking for ipython_config in > /Users/jsacco/.ipython/profile_default[[BR]] > > [TerminalIPythonApp] Looking for ipython_config in /Users/jsacco[[BR]] > > Python 3.5.2 (default, Oct 11 2016, 15:44:53) > Type "copyright", "credits" or "license" for more information. > > IPython 5.1.0 -- An enhanced Interactive Python. > ? -> Introduction and overview of IPython's features. > %quickref -> Quick reference. > help -> Python's own help system. > object? -> Details about 'object', use 'object??' for extra details. > > [TerminalIPythonApp] Loading IPython extensions... > [TerminalIPythonApp] Loading IPython extension: storemagic > [TerminalIPythonApp] Starting IPython's mainloop... > > In [1]: > Traceback (most recent call last): > File "/opt/local/bin/ipython3", line 5, in > start_ipython() > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 > /site-packages/IPython/__init__.py", line 119, in start_ipython > return launch_new_instance(argv=argv, **kwargs) > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 > /site-packages/traitlets/config/application.py", line 658, in > launch_instance > app.start() > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 > /site-packages/IPython/terminal/ipapp.py", line 348, in start > self.shell.mainloop() > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 > /site-packages/IPython/terminal/interactiveshell.py", line 440, in > mainloop > self.interact() > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 > /site-packages/IPython/terminal/interactiveshell.py", line 423, in > interact > code = self.prompt_for_code() > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 > /site-packages/IPython/terminal/interactiveshell.py", line 333, in > prompt_for_code > pre_run=self.pre_prompt, reset_current_buffer=True) > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 > /site-packages/prompt_toolkit/interface.py", line 394, in run > self.eventloop.run(self.input, self.create_eventloop_callbacks()) > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 > /site-packages/prompt_toolkit/eventloop/posix.py", line 92, in run > self.add_reader(stdin, read_from_stdin) > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 > /site-packages/prompt_toolkit/eventloop/posix.py", line 273, in > add_reader > self.selector.register(fd) > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 > /site-packages/prompt_toolkit/eventloop/select.py", line 75, in register > sel.register(fd) > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 > /site-packages/prompt_toolkit/eventloop/select.py", line 130, in register > self._sel.register(fd, selectors.EVENT_READ, None) > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/selectors.py", > line 536, in register > self._kqueue.control([kev], 0, 0) > OSError: [Errno 45] Operation not supported New description: See output below. -Joseph {{{ $ipython3 --log-level=DEBUG [TerminalIPythonApp] IPYTHONDIR set to: /Users/jsacco/.ipython [TerminalIPythonApp] Created profile dir: '/Users/jsacco/.ipython/profile_default' [TerminalIPythonApp] Searching path ['/Users/jsacco', '/Users/jsacco/.ipython/profile_default', '/usr/local/etc/ipython', '/etc/ipython'] for config files [TerminalIPythonApp] Attempting to load config file: ipython_config.py [TerminalIPythonApp] Looking for ipython_config in /etc/ipython [TerminalIPythonApp] Looking for ipython_config in /usr/local/etc/ipython [TerminalIPythonApp] Looking for ipython_config in /Users/jsacco/.ipython/profile_default [TerminalIPythonApp] Looking for ipython_config in /Users/jsacco Python 3.5.2 (default, Oct 11 2016, 15:44:53) Type "copyright", "credits" or "license" for more information. IPython 5.1.0 -- An enhanced Interactive Python. ? -> Introduction and overview of IPython's features. %quickref -> Quick reference. help -> Python's own help system. object? -> Details about 'object', use 'object??' for extra details. [TerminalIPythonApp] Loading IPython extensions... [TerminalIPythonApp] Loading IPython extension: storemagic [TerminalIPythonApp] Starting IPython's mainloop... In [1]: Traceback (most recent call last): File "/opt/local/bin/ipython3", line 5, in start_ipython() File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 /site-packages/IPython/__init__.py", line 119, in start_ipython return launch_new_instance(argv=argv, **kwargs) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 /site-packages/traitlets/config/application.py", line 658, in launch_instance app.start() File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 /site-packages/IPython/terminal/ipapp.py", line 348, in start self.shell.mainloop() File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 /site-packages/IPython/terminal/interactiveshell.py", line 440, in mainloop self.interact() File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 /site-packages/IPython/terminal/interactiveshell.py", line 423, in interact code = self.prompt_for_code() File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 /site-packages/IPython/terminal/interactiveshell.py", line 333, in prompt_for_code pre_run=self.pre_prompt, reset_current_buffer=True) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 /site-packages/prompt_toolkit/interface.py", line 394, in run self.eventloop.run(self.input, self.create_eventloop_callbacks()) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 /site-packages/prompt_toolkit/eventloop/posix.py", line 92, in run self.add_reader(stdin, read_from_stdin) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 /site-packages/prompt_toolkit/eventloop/posix.py", line 273, in add_reader self.selector.register(fd) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 /site-packages/prompt_toolkit/eventloop/select.py", line 75, in register sel.register(fd) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5 /site-packages/prompt_toolkit/eventloop/select.py", line 130, in register self._sel.register(fd, selectors.EVENT_READ, None) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/selectors.py", line 536, in register self._kqueue.control([kev], 0, 0) OSError: [Errno 45] Operation not supported }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 12:50:42 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 12:50:42 -0000 Subject: [MacPorts] #52500: py-pyqt5 @5.6: conflict between Python versions In-Reply-To: <044.d13f04b961b76931b075833a7608276a@macports.org> References: <044.d13f04b961b76931b075833a7608276a@macports.org> Message-ID: <059.0264dcaa7e1b65e0eeb5059ea816c8ba@macports.org> #52500: py-pyqt5 @5.6: conflict between Python versions -----------------------+--------------------------------- Reporter: dliessi | Owner: mamoll Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: py-pyqt5 | -----------------------+--------------------------------- Comment (by RJVB): This seems to use a patch to achieve what my own proposal achieves with existing configure arguments. I think that's preferable. I've updated my patch against the current port and am now test-building py27-sip and py35-sip . There also is a 5.7 upgrade which theoretically should build against Qt 5.6 according to the docs, but appears not to. I'll update #51620 when I'm done. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 12:51:26 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 12:51:26 -0000 Subject: [MacPorts] #52613: Guile-2.0.13 fails to build on Sierra In-Reply-To: <047.ac972e8ff213b95746deb5f6352988fa@macports.org> References: <047.ac972e8ff213b95746deb5f6352988fa@macports.org> Message-ID: <062.066fe86c67622efd33444d28d94d118e@macports.org> #52613: Guile-2.0.13 fails to build on Sierra -------------------------+-------------------------------- Reporter: mouse07410 | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: sierra Port: guile | -------------------------+-------------------------------- Comment (by ryandesign): Ideally, the developers of guile would fix their software and release a new version of it, then MacPorts will update to that version. Perhaps someone could ask the developers of guile how close they are to doing that. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 14:36:32 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 14:36:32 -0000 Subject: [MacPorts] #53017: kerberos5 @1.15: build fails with libressl In-Reply-To: <045.2e6d5c80e4930d3d8f0c88d93b24a25b@macports.org> References: <045.2e6d5c80e4930d3d8f0c88d93b24a25b@macports.org> Message-ID: <060.d3950582a2b14436b4a56942b894eea7@macports.org> #53017: kerberos5 @1.15: build fails with libressl ------------------------+------------------------ Reporter: bK4gYuRo | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: kerberos5 | ------------------------+------------------------ Comment (by H3ik0): I got this answer from libressl: On 2016/12/15 13:16, Heiko wrote: > Hello Dev's, fyi: > > according to the MacPorts Ticket > > https://trac.macports.org/ticket/53017#comment:6 > > build kerberos5 1.15 fails with libressl because of missing API > compatibilty with OpenSSL 1.1 > > Regards, > Heiko > You'll need to modify OPENSSL_VERSION_NUMBER checks to exclude libressl. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 14:47:57 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 14:47:57 -0000 Subject: [MacPorts] #53070: Update Version of port sedan-apps to 2.2.0 In-Reply-To: <042.bb14e5fd4bccf9d3d78441222e2e613b@macports.org> References: <042.bb14e5fd4bccf9d3d78441222e2e613b@macports.org> Message-ID: <057.804fab9a66f5711a36de38104132bbf2@macports.org> #53070: Update Version of port sedan-apps to 2.2.0 -------------------------+--------------------------------- Reporter: rrahn | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: seqan-apps | -------------------------+--------------------------------- Changes (by mf2k): * keywords: => haspatch maintainer -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 14:49:45 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 14:49:45 -0000 Subject: [MacPorts] #53067: brightness @1.0: update to 1.2 In-Reply-To: <041.91c4e677bc70edf6a02fa405c3d29c74@macports.org> References: <041.91c4e677bc70edf6a02fa405c3d29c74@macports.org> Message-ID: <056.cfca5821d32395aad42a22c871612cdf@macports.org> #53067: brightness @1.0: update to 1.2 -------------------------+---------------------- Reporter: l2dy | Owner: mww@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: brightness | -------------------------+---------------------- Changes (by mf2k): * status: new => assigned * owner: => mww@… * cc: mww@… (removed) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 14:50:21 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 14:50:21 -0000 Subject: [MacPorts] #53066: Version Update to SeqAn 2.2.0 In-Reply-To: <042.15db684f9fdbe281bd57c709cb6b7b88@macports.org> References: <042.15db684f9fdbe281bd57c709cb6b7b88@macports.org> Message-ID: <057.fc76d84410ab7e16e9a1ccdc68cd7e40@macports.org> #53066: Version Update to SeqAn 2.2.0 ---------------------+--------------------------------- Reporter: rrahn | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: seqan | ---------------------+--------------------------------- Changes (by mf2k): * keywords: => haspatch maintainer -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 14:58:02 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 14:58:02 -0000 Subject: [MacPorts] #53021: octave @4.2.0_1 +gcc6 +openblas: build failure In-Reply-To: <041.a9100f410b771f7245060d742521900f@macports.org> References: <041.a9100f410b771f7245060d742521900f@macports.org> Message-ID: <056.a94a37c26f7b3fc4ce8e0865bac800a0@macports.org> #53021: octave @4.2.0_1 +gcc6 +openblas: build failure ---------------------+--------------------------------- Reporter: mf2k | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: octave | ---------------------+--------------------------------- Comment (by mf2k): It is still happening with the new version of Xcode 8.2. {{{ $ xcodebuild -version Xcode 8.2 Build version 8C38 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 16:37:29 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 16:37:29 -0000 Subject: [MacPorts] #53075: zmq @4.2.0 does not build on a PPC running OS X 10.5.8 Message-ID: <048.31fbe9d8211f3e3f6e11ee0ef415fb28@macports.org> #53075: zmq @4.2.0 does not build on a PPC running OS X 10.5.8 ------------------------------+----------------- Reporter: josephsacco | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: leopard, powerpc | Port: zmq ------------------------------+----------------- The latest version of zmq does not build on a PPC running leopard. The previous version, 4.1.6_0, builds without incident. The problem is CLOCK_MONOTONIC is not defined in time.h for OSX 10.5.8[see snippet of build output below]. -Joseph src/clock.cpp: In static member function 'static uint64_t zmq::clock_t::rdtsc()': src/clock.cpp:243:19: error: 'CLOCK_MONOTONIC' was not declared in this scope clock_gettime(CLOCK_MONOTONIC, &ts); ^~~~~~~~~~~~~~~ src/clock.cpp:243:39: error: 'clock_gettime' was not declared in this scope clock_gettime(CLOCK_MONOTONIC, &ts); ^ -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 17:12:53 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 17:12:53 -0000 Subject: [MacPorts] #46658: pulseaudio @5.0_1: builds but doesn't work In-Reply-To: <041.d843686d1e126a9748538f8890c8a09e@macports.org> References: <041.d843686d1e126a9748538f8890c8a09e@macports.org> Message-ID: <056.2982b277469a6208d54b4ddf71fc4ea0@macports.org> #46658: pulseaudio @5.0_1: builds but doesn't work -------------------------+---------------------- Reporter: RJVB | Owner: Ionic Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: pulseaudio | -------------------------+---------------------- Comment (by kencu): Thanks - pulseaudio seems to have the same permissions as other executables in there... {{{ -rwxr-xr-x 1 root admin 3971 7 Jun 2016 pth-config -rwxr-xr-x 1 root admin 107484 14 Dec 15:44 pulseaudio -rwxr-xr-x 1 root admin 80276 11 Oct 09:34 pwdecrypt }}} {{{ $ ls -la libpul* -rwxr-xr-x 1 root admin 39160 14 Dec 15:44 libpulse-mainloop- glib.0.dylib lrwxr-xr-x 1 root admin 30 14 Dec 15:44 libpulse-mainloop- glib.dylib -> libpulse-mainloop-glib.0.dylib -rwxr-xr-x 1 root admin 36696 14 Dec 15:44 libpulse-simple.0.dylib lrwxr-xr-x 1 root admin 23 14 Dec 15:44 libpulse-simple.dylib -> libpulse-simple.0.dylib -rwxr-xr-x 1 root admin 325344 14 Dec 15:44 libpulse.0.dylib lrwxr-xr-x 1 root admin 16 14 Dec 15:44 libpulse.dylib -> libpulse.0.dylib }}} {{{ $ file libpulse.0.dylib libpulse.0.dylib: Mach-O 64-bit dynamically linked shared library x86_64 }}} {{{ $ otool -L libpulse.0.dylib libpulse.0.dylib: /opt/local/lib/libpulse.0.dylib (compatibility version 21.0.0, current version 21.0.0) /opt/local/lib/pulseaudio/libpulsecommon-9.0.dylib (compatibility version 0.0.0, current version 0.0.0) /opt/local/lib/libX11-xcb.1.dylib (compatibility version 2.0.0, current version 2.0.0) /opt/local/lib/libX11.6.dylib (compatibility version 10.0.0, current version 10.0.0) /opt/local/lib/libxcb.1.dylib (compatibility version 3.0.0, current version 3.0.0) /opt/local/lib/libICE.6.dylib (compatibility version 10.0.0, current version 10.0.0) /opt/local/lib/libSM.6.dylib (compatibility version 7.0.0, current version 7.1.0) /opt/local/lib/libXtst.6.dylib (compatibility version 8.0.0, current version 8.0.0) /opt/local/lib/libintl.8.dylib (compatibility version 10.0.0, current version 10.5.0) /opt/local/lib/libjson-c.2.dylib (compatibility version 3.0.0, current version 3.2.0) /opt/local/lib/libiconv.2.dylib (compatibility version 8.0.0, current version 8.1.0) /opt/local/lib/libsndfile.1.dylib (compatibility version 2.0.0, current version 2.26.0) /opt/local/lib/libdbus-1.3.dylib (compatibility version 18.0.0, current version 18.8.0) /opt/local/lib/libgdbm.4.dylib (compatibility version 5.0.0, current version 5.0.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 44.0.0) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 550.44.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.11) }}} dbus seems to be loaded and running {{{ $ ps -a -u root | grep dbus 500 64 ?? 0:00.04 /opt/local/bin/dbus-daemon --system --nofork }}} I don't know much about dbus - I see it's linked against `libdbus-1.3`. Perhaps some kind of dbus version thingy? Maybe my dbus is loaded but not working correctly? here's the printout from {{{ $ pulseaudio -vvvvvvvvvvvvvvvv W: [] caps.c: Normally all extra capabilities would be dropped now, but that's impossible because PulseAudio was built without capabilities support. Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory I: [] core-util.c: Failed to acquire high-priority scheduling: Input/output error I: [] main.c: This is PulseAudio 9.0-rebootstrapped D: [] main.c: Compilation host: x86_64-apple-darwin10.8.0 D: [] main.c: Compilation CFLAGS: -pipe -Os -arch x86_64 -Wall -W -Wextra -Wno-long-long -Wno-overlength-strings -Wundef -Wformat=2 -Wsign-compare -Wformat-security -Wmissing-include-dirs -Wformat-nonliteral -Wold-style- definition -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls -Wmissing-declarations -Wmissing-noreturn -Wshadow -Wendif-labels -Wcast- align -Wstrict-aliasing -Wwrite-strings -Wno-unused-parameter -ffast-math -fno-common -fdiagnostics-show-option -fdiagnostics-color=auto -mmacosx- version-min=10.6 -isysroot / D: [] main.c: Running on host: Darwin i386 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 D: [] main.c: Found 2 CPUs. I: [] main.c: Page size is 4096 bytes D: [] main.c: Compiled with Valgrind support: no D: [] main.c: Running in valgrind mode: no D: [] main.c: Running in VM: no D: [] main.c: Optimized build: yes D: [] main.c: FASTPATH defined, only fast path asserts disabled. I: [] main.c: Machine ID is a6e343d28e0aa658e03380295806ccbb. I: [] main.c: Using runtime directory /Users/cunningh/.config/pulse /a6e343d28e0aa658e03380295806ccbb-runtime. I: [] main.c: Using state directory /Users/cunningh/.config/pulse. I: [] main.c: Using modules directory /opt/local/lib/pulse-9.0/modules. I: [] main.c: Running in system mode: no W: [] pid.c: Stale PID file, overwriting. I: [] main.c: System supports high resolution timers D: [] memblock.c: Using shared posix-shm memory pool with 1024 slots of size 64.0 KiB each, total size is 64.0 MiB, maximum usable slot size is 65472 I: [] cpu-x86.c: CPU flags: CMOV MMX SSE SSE2 SSE3 SSSE3 I: [] svolume_mmx.c: Initialising MMX optimized volume functions. I: [] remap_mmx.c: Initialising MMX optimized remappers. I: [] svolume_sse.c: Initialising SSE2 optimized volume functions. I: [] remap_sse.c: Initialising SSE2 optimized remappers. I: [] sconv_sse.c: Initialising SSE2 optimized conversions. I: [] svolume_orc.c: Initialising ORC optimized volume functions. D: [] database-gdbm.c: Opened GDBM database '/Users/cunningh/.config/pulse /a6e343d28e0aa658e03380295806ccbb-device-volumes.x86_64-apple- darwin10.8.0.gdbm' I: [] module-device-restore.c: Successfully opened database file '/Users/cunningh/.config/pulse/a6e343d28e0aa658e03380295806ccbb-device- volumes'. I: [] module.c: Loaded "module-device-restore" (index: #0; argument: ""). D: [] database-gdbm.c: Opened GDBM database '/Users/cunningh/.config/pulse /a6e343d28e0aa658e03380295806ccbb-stream-volumes.x86_64-apple- darwin10.8.0.gdbm' I: [] module-stream-restore.c: Successfully opened database file '/Users/cunningh/.config/pulse/a6e343d28e0aa658e03380295806ccbb-stream- volumes'. D: [] protocol-dbus.c: Interface org.PulseAudio.Ext.StreamRestore1 added for object /org/pulseaudio/stream_restore1 I: [] module.c: Loaded "module-stream-restore" (index: #1; argument: ""). D: [] database-gdbm.c: Opened GDBM database '/Users/cunningh/.config/pulse /a6e343d28e0aa658e03380295806ccbb-card-database.x86_64-apple- darwin10.8.0.gdbm' I: [] module-card-restore.c: Successfully opened database file '/Users/cunningh/.config/pulse/a6e343d28e0aa658e03380295806ccbb-card- database'. I: [] module.c: Loaded "module-card-restore" (index: #2; argument: ""). I: [] module.c: Loaded "module-augment-properties" (index: #3; argument: ""). I: [] module.c: Loaded "module-switch-on-port-available" (index: #4; argument: ""). D: [] module.c: Checking for existence of '/opt/local/lib/pulse-9.0/modules/module-coreaudio-detect.so': success D: [] module-coreaudio-detect.c: Loading module-coreaudio-device with arguments 'object_id=263 record=1 playback=1' I: [] module-coreaudio-device.c: Initializing module for CoreAudio device 'Built-in Microphone' (id 263) I: [] module-card-restore.c: Restoring port latency offsets for card Built-in_Microphone. I: [] card.c: Created 0 "Built-in_Microphone" D: [] module-coreaudio-device.c: Sample rate: 44100.000000 D: [] module-coreaudio-device.c: 8 bytes per packet D: [] module-coreaudio-device.c: 1 frames per packet D: [] module-coreaudio-device.c: 8 bytes per frame D: [] module-coreaudio-device.c: 2 channels per frame D: [] module-coreaudio-device.c: 32 bits per channel D: [] module-coreaudio-device.c: Stream name is >Channel 1, Channel 2< D: [] module-device-restore.c: Database contains no data for key: source:Channel_1__Channel_2 D: [] module-device-restore.c: Database contains no (or invalid) data for key: source:Channel_1__Channel_2:null I: [] source.c: Created source 0 "Channel_1__Channel_2" with sample spec float32le 2ch 44100Hz and channel map front-left,front-right I: [] source.c: device.string = "Built-in Microphone" I: [] source.c: device.product.name = "Built-in Microphone" I: [] source.c: device.description = "Built-in Microphone" I: [] source.c: device.access_mode = "mmap" I: [] source.c: device.class = "sound" I: [] source.c: device.api = "CoreAudio" I: [] source.c: device.buffering.buffer_size = "4096" I: [] source.c: device.vendor.name = "Apple Inc." I: [] source.c: device.icon_name = "audio-card" D: [] module-coreaudio-device.c: 512 frames per IOProc D: [Built-in Microphone] module-coreaudio-device.c: Thread starting up D: [Built-in Microphone] core-util.c: sysctl for hw.cpufrequency: 2330000000 I: [Built-in Microphone] core-util.c: Successfully acquired real-time thread priority. I: [] module.c: Loaded "module-coreaudio-device" (index: #6; argument: "object_id=263 record=1 playback=1"). D: [] module-coreaudio-detect.c: Loading module-coreaudio-device with arguments 'object_id=261 record=1 playback=1' I: [] module-coreaudio-device.c: Initializing module for CoreAudio device 'Built-in Input' (id 261) I: [] module-card-restore.c: Restoring port latency offsets for card Built-in_Input. I: [] card.c: Created 1 "Built-in_Input" D: [] module-coreaudio-device.c: Sample rate: 44100.000000 D: [] module-coreaudio-device.c: 8 bytes per packet D: [] module-coreaudio-device.c: 1 frames per packet D: [] module-coreaudio-device.c: 8 bytes per frame D: [] module-coreaudio-device.c: 2 channels per frame D: [] module-coreaudio-device.c: 32 bits per channel D: [] module-coreaudio-device.c: Stream name is >Channel 1, Channel 2< D: [] core-subscribe.c: Dropped redundant event due to change event. D: [] module-device-restore.c: Database contains no data for key: source:Channel_1__Channel_2.2 D: [] module-device-restore.c: Database contains no (or invalid) data for key: source:Channel_1__Channel_2.2:null I: [] source.c: Created source 1 "Channel_1__Channel_2.2" with sample spec float32le 2ch 44100Hz and channel map front-left,front-right I: [] source.c: device.string = "Built-in Input" I: [] source.c: device.product.name = "Built-in Input" I: [] source.c: device.description = "Built-in Input" I: [] source.c: device.access_mode = "mmap" I: [] source.c: device.class = "sound" I: [] source.c: device.api = "CoreAudio" I: [] source.c: device.buffering.buffer_size = "4096" I: [] source.c: device.vendor.name = "Apple Inc." I: [] source.c: device.icon_name = "audio-card" D: [] module-coreaudio-device.c: 512 frames per IOProc D: [Built-in Input] module-coreaudio-device.c: Thread starting up D: [Built-in Input] core-util.c: sysctl for hw.cpufrequency: 2330000000 I: [Built-in Input] core-util.c: Successfully acquired real-time thread priority. I: [] module.c: Loaded "module-coreaudio-device" (index: #7; argument: "object_id=261 record=1 playback=1"). D: [] module-coreaudio-detect.c: Loading module-coreaudio-device with arguments 'object_id=265 record=1 playback=1' I: [] module-coreaudio-device.c: Initializing module for CoreAudio device 'Built-in Output' (id 265) I: [] module-card-restore.c: Restoring port latency offsets for card Built-in_Output. I: [] card.c: Created 2 "Built-in_Output" D: [] module-coreaudio-device.c: Sample rate: 44100.000000 D: [] module-coreaudio-device.c: 8 bytes per packet D: [] module-coreaudio-device.c: 1 frames per packet D: [] module-coreaudio-device.c: 8 bytes per frame D: [] module-coreaudio-device.c: 2 channels per frame D: [] module-coreaudio-device.c: 32 bits per channel pulseaudio(53039,0x7fff71106cc0) malloc: *** error for object 0x100d0d8b8: pointer being freed was not allocated *** set a breakpoint in malloc_error_break to debug Abort trap }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 17:43:26 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 17:43:26 -0000 Subject: [MacPorts] #51620: py-pyqt5: fix DBus module build and pyversion conflicts, support multiple Qt5 ports In-Reply-To: <041.878bbad1021a18186c191e6780e8baed@macports.org> References: <041.878bbad1021a18186c191e6780e8baed@macports.org> Message-ID: <056.1e14d3dedb58edcfdebecb590db2042c@macports.org> #51620: py-pyqt5: fix DBus module build and pyversion conflicts, support multiple Qt5 ports --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-pyqt5 | --------------------------+---------------------- Changes (by RJVB): * Attachment "py-pyqt5.2.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 17:49:34 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 17:49:34 -0000 Subject: [MacPorts] #51620: py-pyqt5: fix DBus module build and pyversion conflicts, support multiple Qt5 ports In-Reply-To: <041.878bbad1021a18186c191e6780e8baed@macports.org> References: <041.878bbad1021a18186c191e6780e8baed@macports.org> Message-ID: <056.97acb3951197a3bf8781209bc70c3f0c@macports.org> #51620: py-pyqt5: fix DBus module build and pyversion conflicts, support multiple Qt5 ports --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-pyqt5 | --------------------------+---------------------- Comment (by RJVB): Here's the new patch announced on #52500. It looks more complex than it is because I couldn't resist cleaning up whitespace inconsistencies too. Compared to my original submission, this patch drops the qt{webkit,webengine} variants which were already implemented under a shorter name, but also reverts to NOT making the QtWebEngine variant default. That Qt component is huge as said and not yet used by many ports, so I consider it still justified to make it available on explicit demand only. I have implemented an additional variant the interest of which became apparent while using the software. It prevents aborting (= on-demand crashing) when Python errors (even benign ones) occur. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 17:49:55 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 17:49:55 -0000 Subject: [MacPorts] #52500: py-pyqt5 @5.6: conflict between Python versions In-Reply-To: <044.d13f04b961b76931b075833a7608276a@macports.org> References: <044.d13f04b961b76931b075833a7608276a@macports.org> Message-ID: <059.1eb422750830284c3570379da4706718@macports.org> #52500: py-pyqt5 @5.6: conflict between Python versions -----------------------+--------------------------------- Reporter: dliessi | Owner: mamoll Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: py-pyqt5 | -----------------------+--------------------------------- Comment (by RJVB): As promised: https://trac.macports.org/attachment/ticket/51620/py- pyqt5.2.diff -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 17:55:58 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 17:55:58 -0000 Subject: [MacPorts] #46658: pulseaudio @5.0_1: builds but doesn't work In-Reply-To: <041.d843686d1e126a9748538f8890c8a09e@macports.org> References: <041.d843686d1e126a9748538f8890c8a09e@macports.org> Message-ID: <056.1d95c00d0c4132189a3fc702a6cf1849@macports.org> #46658: pulseaudio @5.0_1: builds but doesn't work -------------------------+---------------------- Reporter: RJVB | Owner: Ionic Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: pulseaudio | -------------------------+---------------------- Comment (by RJVB): So the setuid error is not correct, that's annoying. Are you by any chance doing this as root? If you're not, then you have started the wrong DBus daemon. The system DBus daemon is rarely necessary, but the user session DBus is required for many things: {{{ > launchctl load -w /opt/local/Library/LaunchAgents/org.freedesktop.dbus- session.plist }}} Quit and restart Terminal.app, restart your XQuartz session or simply log off and back in after that command. Now pulseaudio ought to find your session DBus. If not: what does `port installed dbus` show? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 17:58:43 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 17:58:43 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.e9fcbecd40604560c8a383070bab0785@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Changes (by RJVB): * Attachment "GeneralUser.Portfile" added. my proposal for a port providing the GeneralUser GS soundfont -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 18:00:45 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 18:00:45 -0000 Subject: [MacPorts] #51620: py-pyqt5: fix DBus module build and pyversion conflicts, support multiple Qt5 ports In-Reply-To: <041.878bbad1021a18186c191e6780e8baed@macports.org> References: <041.878bbad1021a18186c191e6780e8baed@macports.org> Message-ID: <056.5d598783262727b7d08d914b92cf4306@macports.org> #51620: py-pyqt5: fix DBus module build and pyversion conflicts, support multiple Qt5 ports --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-pyqt5 | --------------------------+---------------------- Changes (by RJVB): * Attachment "patch-no-abort-on-python-errors.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 18:04:26 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 18:04:26 -0000 Subject: [MacPorts] #51045: "---> Attempting to fetch" doesn't start in a new line In-Reply-To: <042.da3c0d0fb7d2c1d9ef35864c3eeb3b17@macports.org> References: <042.da3c0d0fb7d2c1d9ef35864c3eeb3b17@macports.org> Message-ID: <057.cab0b6f6ef4894d9e259234a3bdd6d4f@macports.org> #51045: "---> Attempting to fetch" doesn't start in a new line ---------------------+-------------------------------- Reporter: mojca | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: | Keywords: Port: | ---------------------+-------------------------------- Comment (by raimue): I cannot reproduce this with current master. Was this fixed already? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 18:13:05 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 18:13:05 -0000 Subject: [MacPorts] #53075: zmq @4.2.0 does not build on a PPC running OS X 10.5.8 In-Reply-To: <048.31fbe9d8211f3e3f6e11ee0ef415fb28@macports.org> References: <048.31fbe9d8211f3e3f6e11ee0ef415fb28@macports.org> Message-ID: <063.4e2d208483cf0d6e776a56277557e24d@macports.org> #53075: zmq @4.2.0 does not build on a PPC running OS X 10.5.8 --------------------------+------------------------------ Reporter: josephsacco | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: leopard, powerpc Port: zmq | --------------------------+------------------------------ Comment (by kencu): The issue could be here this guard block {{{ #if defined ZMQ_HAVE_OSX && __MAC_OS_X_VERSION_MIN_REQUIRED < 101200 // less than macOS 10.12 + int rc = alt_clock_gettime (CLOCK_MONOTONIC, &tv); +#else int rc = clock_gettime (CLOCK_MONOTONIC, &tv); +#endif }}} might not be working correctly for Leopard, because Leopard should not be seeing that function call, it appears. Why don't you try forcing `alt_clock_gettime` to be used and see if that fixes it? for a quick one-off way to do that, port -v configure it, go into the source, and monkey with that file like so maybe: {{{ int rc = alt_clock_gettime (CLOCK_MONOTONIC, &tv); }}} then try building. If it doesn't work, look for other guards that might need fiddling with. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 18:14:13 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 18:14:13 -0000 Subject: [MacPorts] #53076: gcc47 @4.7.4_6 fails to build Message-ID: <043.7f4cb9cd057864586874ffa3345eb065@macports.org> #53076: gcc47 @4.7.4_6 fails to build --------------------+------------------- Reporter: posita | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: gcc47 --------------------+------------------- `main.log` attached. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 18:14:33 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 18:14:33 -0000 Subject: [MacPorts] #53076: gcc47 @4.7.4_6 fails to build In-Reply-To: <043.7f4cb9cd057864586874ffa3345eb065@macports.org> References: <043.7f4cb9cd057864586874ffa3345eb065@macports.org> Message-ID: <058.e93b8efc4ff21153bf7912d1a7a965c8@macports.org> #53076: gcc47 @4.7.4_6 fails to build ---------------------+----------------- Reporter: posita | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gcc47 | ---------------------+----------------- Changes (by posita): * Attachment "main.log" added. main.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 18:16:03 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 18:16:03 -0000 Subject: [MacPorts] #53076: gcc47 @4.7.4_6 fails to build In-Reply-To: <043.7f4cb9cd057864586874ffa3345eb065@macports.org> References: <043.7f4cb9cd057864586874ffa3345eb065@macports.org> Message-ID: <058.3a665297f90ace6c2a2da56775c1f0f7@macports.org> #53076: gcc47 @4.7.4_6 fails to build ---------------------+----------------- Reporter: posita | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gcc47 | ---------------------+----------------- Comment (by posita): Apologies! Forgot to CC maintainer (mww at macports.org), but I can no longer edit the ticket details. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 19:13:27 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 19:13:27 -0000 Subject: [MacPorts] #51045: "---> Attempting to fetch" doesn't start in a new line In-Reply-To: <042.da3c0d0fb7d2c1d9ef35864c3eeb3b17@macports.org> References: <042.da3c0d0fb7d2c1d9ef35864c3eeb3b17@macports.org> Message-ID: <057.32ee87e02ec4e4e6320b1c8be2d05bc3@macports.org> #51045: "---> Attempting to fetch" doesn't start in a new line ---------------------+-------------------------------- Reporter: mojca | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: | Keywords: Port: | ---------------------+-------------------------------- Comment (by mojca): I just updated to the latest version and I still experience the problem. OK, it's a slightly older OS, but I tested the released version on 10.6 and 10.12 and I don't see the problem there. I'm using bash from MacPorts as my shell, but switching to `/bin/bash` didn't help. I can try to investigate a bit further (for example by installing master to 10.6, I would be grateful for suggestions about what I could test locally) to figure out what exactly could cause the problem or why the problem wasn't fixed for me (in case it was fixed for others). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 19:34:02 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 19:34:02 -0000 Subject: [MacPorts] #51045: "---> Attempting to fetch" doesn't start in a new line In-Reply-To: <042.da3c0d0fb7d2c1d9ef35864c3eeb3b17@macports.org> References: <042.da3c0d0fb7d2c1d9ef35864c3eeb3b17@macports.org> Message-ID: <057.a85563db2c35ff9f625cc3f473d1a9ff@macports.org> #51045: "---> Attempting to fetch" doesn't start in a new line ---------------------+-------------------------------- Reporter: mojca | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: | Keywords: Port: | ---------------------+-------------------------------- Comment (by raimue): Did you experience this originally with an older version of macOS? Perhaps this only occured due to a bug in the progress output of libcurl which was missing a final newline? To clarify my findings a bit more, I tested on macOS 10.12 Sierra. I increasing the version of a port and then run `sudo port install `. I did not see the problem with either 2.3.5 or [changeset:cb1ee59765942aad6a2021efc2efabd3ec526966/macports-base current master]. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 19:52:58 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 19:52:58 -0000 Subject: [MacPorts] #53076: gcc47 @4.7.4_6 fails to build In-Reply-To: <043.7f4cb9cd057864586874ffa3345eb065@macports.org> References: <043.7f4cb9cd057864586874ffa3345eb065@macports.org> Message-ID: <058.7d30f4aa9dee8d9066806e489abbdae4@macports.org> #53076: gcc47 @4.7.4_6 fails to build ---------------------+---------------------- Reporter: posita | Owner: mww@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gcc47 | ---------------------+---------------------- Changes (by raimue): * owner: => mww@… * status: new => assigned Comment: Appears to be an issue with texinfo: {{{ :info:build /Users/matt/.site/var/macports/build/_Users_matt_.site_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc47/gcc47/work/gcc-4.7.4/gcc/doc/gcc.texi:209: no matching `@end tex' :info:build /Users/matt/.site/var/macports/build/_Users_matt_.site_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc47/gcc47/work/gcc-4.7.4/gcc/doc/gcc.texi:209: no matching `@end multitable' :info:build /Users/matt/.site/var/macports/build/_Users_matt_.site_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc47/gcc47/work/gcc-4.7.4/gcc/doc/gcc.texi:209: no matching `@end titlepage' :info:build make[3]: *** [doc/gcc.info] Error 1 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 20:15:16 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 20:15:16 -0000 Subject: [MacPorts] #53075: zmq @4.2.0 does not build on a PPC running OS X 10.5.8 In-Reply-To: <048.31fbe9d8211f3e3f6e11ee0ef415fb28@macports.org> References: <048.31fbe9d8211f3e3f6e11ee0ef415fb28@macports.org> Message-ID: <063.6fb42a7704caf8aa400f2b6180c08c57@macports.org> #53075: zmq @4.2.0 does not build on a PPC running OS X 10.5.8 --------------------------+------------------------------ Reporter: josephsacco | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: leopard, powerpc Port: zmq | --------------------------+------------------------------ Comment (by josephsacco): That was one of the first things I tried... :-) The problem is the macro CLOCK_MONOTONIC is ''' not defined''' for OS X 10.5.8. The code for version 4.1.6 does something far more trivial. The method containing the offending line, zmq::clock_t::rdsc()[[BR]] returns 0 under OS X 10.5.8.[[BR]] I am not sure what that means, or whether it is the right thing to do. If I make that change, zmq @4.2 builds. For added amusement I then ran 'make test'. Of the 77 tests that ran, only 3 passed. The remaining 74 failed [illegal instruction: exit 132] -Joseph -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 22:13:19 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 22:13:19 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.730d6162de990990fabaaf908e9cec68@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Comment (by mojca): The reason why livecheck doesn't work is because {{{ curl -A "MacPorts libcurl" http://www.schristiancollins.com/generaluser.php }}} returns 403, most likely to drive bots away (if you remove libcurl, it works). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 23:09:30 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 23:09:30 -0000 Subject: [MacPorts] #51045: "---> Attempting to fetch" doesn't start in a new line In-Reply-To: <042.da3c0d0fb7d2c1d9ef35864c3eeb3b17@macports.org> References: <042.da3c0d0fb7d2c1d9ef35864c3eeb3b17@macports.org> Message-ID: <057.5d8d90d9b37a6ef07b1c246f48aef74e@macports.org> #51045: "---> Attempting to fetch" doesn't start in a new line ---------------------+-------------------------------- Reporter: mojca | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: | Keywords: Port: | ---------------------+-------------------------------- Comment (by ryandesign): We can use the buildbot logs to see what happens on various OS versions. Picking a build at random (libgcrypt): [https://build.macports.org/builders/ports-10.6_i386_legacy- builder/builds/12362/steps/install-port/logs/stdio We don't see the problem on Snow Leopard] (curl 7.19.7): {{{ ---> Attempting to fetch libgcrypt-1.7.5_0.darwin_10.i386.tbz2 from https://packages.macports.org/libgcrypt % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 DEBUG: Fetching archive failed:: The requested URL returned error: 404 }}} [https://build.macports.org/builders/ports-10.7_x86_64_legacy- builder/builds/18310/steps/install-port/logs/stdio We don't see the problem on Lion] (curl 7.21.4): {{{ ---> Attempting to fetch libgcrypt-1.7.5_0.darwin_11.x86_64.tbz2 from https://packages.macports.org/libgcrypt % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 DEBUG: Fetching archive failed:: The requested URL returned error: 404 }}} [https://build.macports.org/builders/ports-10.8_x86_64_legacy- builder/builds/13004/steps/install-port/logs/stdio We don't see the problem on Mountain Lion] (curl 7.24.0): {{{ ---> Attempting to fetch libgcrypt-1.7.5_0.darwin_12.x86_64.tbz2 from https://packages.macports.org/libgcrypt % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 DEBUG: Fetching archive failed:: The requested URL returned error: 404 }}} [https://build.macports.org/builders/ports-10.9_x86_64-builder/builds/13056/steps /install-port/logs/stdio We don't see the problem on Mavericks] (curl 7.30.0): {{{ ---> Attempting to fetch libgcrypt-1.7.5_0.darwin_13.x86_64.tbz2 from https://packages.macports.org/libgcrypt % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 DEBUG: Fetching archive failed:: The requested URL returned error: 404 Not Found }}} [https://build.macports.org/builders/ports-10.10_x86_64-builder/builds/13039/steps /install-port/logs/stdio We see the problem on Yosemite] (curl 7.43.0): {{{ ---> Attempting to fetch libgcrypt-1.7.5_0.darwin_14.x86_64.tbz2 from https://packages.macports.org/libgcrypt % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0DEBUG: Fetching archive failed:: The requested URL returned error: 404 Not Found }}} [https://build.macports.org/builders/ports-10.11_x86_64-builder/builds/13069/steps /install-port/logs/stdio We see the problem on El Capitan] (curl 7.43.0): {{{ ---> Attempting to fetch libgcrypt-1.7.5_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/libgcrypt % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0DEBUG: Fetching archive failed:: The requested URL returned error: 404 Not Found }}} [https://build.macports.org/builders/ports-10.12_x86_64-builder/builds/14897/steps /install-port/logs/stdio We don't see the problem on Sierra] (curl 7.49.1): {{{ ---> Attempting to fetch libgcrypt-1.7.5_0.darwin_16.x86_64.tbz2 from https://packages.macports.org/libgcrypt % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 DEBUG: Fetching archive failed:: The requested URL returned error: 404 Not Found }}} This suggests it is a curl bug that was introduced after curl 7.30.0 and fixed before curl 7.49.1. But it's also possible Apple made custom modifications to the copies of curl included with macOS that could account for this. These types of bugs in the system curl are a reason why I've suggested that we should [comment:ticket:51516:23 bundle a newer copy of curl] so that we get consistent behavior across OS versions. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 23:12:02 2016 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2016 23:12:02 -0000 Subject: [MacPorts] #51516: MacPorts should use a bundled copy of a newer libcurl and SSL library rather than the OS X version In-Reply-To: <047.77071f9662e9241a7e27fcde2de41507@macports.org> References: <047.77071f9662e9241a7e27fcde2de41507@macports.org> Message-ID: <062.6a870abca0f70d4170b10dfb9a96597b@macports.org> #51516: MacPorts should use a bundled copy of a newer libcurl and SSL library rather than the OS X version --------------------------+-------------------------------- Reporter: ryandesign | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: MacPorts Future Component: base | Version: Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by ryandesign): Replying to [comment:23 ryandesign]: > the idea to use a bundled curl is much older, and is based on the idea that we should use the latest software, because it has more features and fixes bugs. #51045 is an example of such a curl bug. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 00:08:48 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 00:08:48 -0000 Subject: [MacPorts] #51045: "---> Attempting to fetch" doesn't start in a new line In-Reply-To: <042.da3c0d0fb7d2c1d9ef35864c3eeb3b17@macports.org> References: <042.da3c0d0fb7d2c1d9ef35864c3eeb3b17@macports.org> Message-ID: <057.cfefe75e076f3bbe529b1734fbcc7c38@macports.org> #51045: "---> Attempting to fetch" doesn't start in a new line ---------------------+-------------------------------- Reporter: mojca | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: | Keywords: Port: | ---------------------+-------------------------------- Comment (by mojca): For me the problem is present on Lion as well, even though I don't remember seeing it in the stable version. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 06:51:32 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 06:51:32 -0000 Subject: [MacPorts] #46658: pulseaudio @5.0_1: builds but doesn't work In-Reply-To: <041.d843686d1e126a9748538f8890c8a09e@macports.org> References: <041.d843686d1e126a9748538f8890c8a09e@macports.org> Message-ID: <056.f42a9f466a7fa30fb9a231d1d5320a49@macports.org> #46658: pulseaudio @5.0_1: builds but doesn't work -------------------------+---------------------- Reporter: RJVB | Owner: Ionic Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: pulseaudio | -------------------------+---------------------- Comment (by kencu): same error. doesn't help that I know nothing about dbus. {{{ $ port installed dbus The following ports are currently installed: dbus @1.10.12_0 (active) }}} I was working on a new port - OpenDUNE - and the audio for that uses pulseaudio - ergo this tangle. Strangely, even after the crash, I got the audio somehow... Looks like it has something to do with coreaudio, based on that crash chain... I'll try it on a different system and see what happens. Perhaps it's a 10.6 thing. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 08:24:05 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 08:24:05 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.47521f46f934c28f02bd75ebb843766e@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Comment (by RJVB): I expected something like that; something even nastier protects the dropbox location (like when there are no search permission on a directory). So do we figure out a custom livecheck connection method (and how) or do we just use the workaround I found? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 08:44:18 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 08:44:18 -0000 Subject: [MacPorts] #46658: pulseaudio @5.0_1: builds but doesn't work In-Reply-To: <041.d843686d1e126a9748538f8890c8a09e@macports.org> References: <041.d843686d1e126a9748538f8890c8a09e@macports.org> Message-ID: <056.2acc7a0faee877bc72b9a784f9355326@macports.org> #46658: pulseaudio @5.0_1: builds but doesn't work -------------------------+---------------------- Reporter: RJVB | Owner: Ionic Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: pulseaudio | -------------------------+---------------------- Comment (by RJVB): Do you still get the setuid error and failure to connect to a session DBus? That's becoming hard to debug from a distance. The only thing you need to know about dbus is that clients find it via an environment variable that's easy to check for because its name starts with DBUS. I can confirm that dbus used to work just fine on 10.6 but it's been quite a while since I checked it. If you have Qt4 or Qt5 installed there's an application called qdbusviewer (probably in /opt/local/libexec/qt[45]/bin). If that starts and shows at least a few things that are not errors you're good on the dbus side of things. The fact you still get audio suggests that pulseaudio forks a process that does the actual work which doesn't crash. You are right that this might be a bug related to CoreAudio differences on 10.6 . The exact reason for the crash here is that the CA module tries to free memory that was never allocated. You can try to debug that yourself (`lldb /opt/local/bin/pulseaudio` ...), you can wait for the port maintainer to jump in, or you can report the crash upstream. In case OpenDUNE is an X11 application: did you install pulseaudio with the +x11 variant? I take it you checked if it only supports pulseaudio? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 09:45:52 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 09:45:52 -0000 Subject: [MacPorts] #53017: kerberos5 @1.15: build fails with libressl In-Reply-To: <045.2e6d5c80e4930d3d8f0c88d93b24a25b@macports.org> References: <045.2e6d5c80e4930d3d8f0c88d93b24a25b@macports.org> Message-ID: <060.3a1d725bbd0172474e38f1cc8b4e8bf8@macports.org> #53017: kerberos5 @1.15: build fails with libressl ------------------------+------------------------ Reporter: bK4gYuRo | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: kerberos5 | ------------------------+------------------------ Comment (by jeremyhu): Yeah, IMO, we should seriously just consider dropping OpenSSL and focus on Libressl. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 12:11:01 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 12:11:01 -0000 Subject: [MacPorts] #53075: zmq @4.2.0 does not build on a PPC running OS X 10.5.8 In-Reply-To: <048.31fbe9d8211f3e3f6e11ee0ef415fb28@macports.org> References: <048.31fbe9d8211f3e3f6e11ee0ef415fb28@macports.org> Message-ID: <063.15f994434c200016fd9827482de2a522@macports.org> #53075: zmq @4.2.0 does not build on a PPC running OS X 10.5.8 --------------------------+------------------------------ Reporter: josephsacco | Owner: merijn@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: leopard, powerpc Port: zmq | --------------------------+------------------------------ Changes (by ryandesign): * status: new => assigned * cc: stromnov@… (removed) * cc: michaelld, stromnov (added) * owner: => merijn@… Old description: > The latest version of zmq does not build on a PPC running leopard. The > previous version, 4.1.6_0, builds without incident. > > The problem is CLOCK_MONOTONIC is not defined in time.h for OSX > 10.5.8[see snippet of build output below]. > > -Joseph > > src/clock.cpp: In static member function 'static uint64_t > zmq::clock_t::rdtsc()': > src/clock.cpp:243:19: error: 'CLOCK_MONOTONIC' was not declared in this > scope > clock_gettime(CLOCK_MONOTONIC, &ts); > ^~~~~~~~~~~~~~~ > src/clock.cpp:243:39: error: 'clock_gettime' was not declared in this > scope > clock_gettime(CLOCK_MONOTONIC, &ts); > ^ New description: The latest version of zmq does not build on a PPC running leopard. The previous version, 4.1.6_0, builds without incident. The problem is CLOCK_MONOTONIC is not defined in time.h for OSX 10.5.8[see snippet of build output below]. -Joseph {{{ src/clock.cpp: In static member function 'static uint64_t zmq::clock_t::rdtsc()': src/clock.cpp:243:19: error: 'CLOCK_MONOTONIC' was not declared in this scope clock_gettime(CLOCK_MONOTONIC, &ts); ^~~~~~~~~~~~~~~ src/clock.cpp:243:39: error: 'clock_gettime' was not declared in this scope clock_gettime(CLOCK_MONOTONIC, &ts); ^ }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 12:32:12 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 12:32:12 -0000 Subject: [MacPorts] #53077: port request: chmcmd Message-ID: <041.e8a8c96ed295a98eb0ccd5f103127425@macports.org> #53077: port request: chmcmd ---------------------+------------------------ Reporter: RJVB | Owner: Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: fpc chmcmd ---------------------+------------------------ FreePascal includes a nice little binary that has standalone interest, and which can be distributed on its own, technically speaking: `chmcmd`. This can take the place of MS HTML WorkShop help compiler (hhc.exe) in doxygen applications (`HHC_LOCATION`); a quick comparison between the chm files built through doxygen by hhc.exe and chmcmd revealed no obvious information or function loss. The only alternative I am currently aware of to create a single archive file containing what would otherwise be a possibly very large set of HTML files is Qt's compiled help (.qch); in my testing these can be twice as big as .chm files and recent regressions in Qt's Assistant make them a less appealing alternative. I'm working on an updated `port:kchmviewer`; having the chmcmd command available without having to install the whole FreePascal environment would definitely be a win, esp. for the API documentation generated by my KF5 ports. I don't think the command itself is required by FreePascal (to be confirmed, but it's discussed on their wiki as more of a demonstration than an actual tool). I haven't looked at specifics, but a priori it should be possible to build just this executable in the FreePascal source tree. This would lead to a (sub)port that has a build dependency on port:fpc but ships a standalone executable (to be installed in ${prefix}/bin, of course). I *presume* that the (L)GPL-2 makes it impossible for me to bundle the executable with my `port:kf5-kapidocs` ? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 13:23:45 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 13:23:45 -0000 Subject: [MacPorts] #53078: openmpi-llvm fails to configure Message-ID: <041.1424a3dbde95993469eb625774bd6185@macports.org> #53078: openmpi-llvm fails to configure --------------------+-------------------------- Reporter: ksze | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: openmpi-llvm --------------------+-------------------------- openmpi-llvm fails at the configure stage. Somehow it's looking for compilers that don't exist. Build log attached. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 13:25:16 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 13:25:16 -0000 Subject: [MacPorts] #53078: openmpi-llvm fails to configure In-Reply-To: <041.1424a3dbde95993469eb625774bd6185@macports.org> References: <041.1424a3dbde95993469eb625774bd6185@macports.org> Message-ID: <056.f03d1677ebd1ab354f289cb79c278c14@macports.org> #53078: openmpi-llvm fails to configure ---------------------------+------------------- Reporter: ksze | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: openmpi-llvm | ---------------------------+------------------- Changes (by ksze): * Attachment "main.log" added. Build log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 14:42:30 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 14:42:30 -0000 Subject: [MacPorts] #53075: zmq @4.2.0 does not build on a PPC running OS X 10.5.8 In-Reply-To: <048.31fbe9d8211f3e3f6e11ee0ef415fb28@macports.org> References: <048.31fbe9d8211f3e3f6e11ee0ef415fb28@macports.org> Message-ID: <063.4c625984a416463f6a5283453fc70fa2@macports.org> #53075: zmq @4.2.0 does not build on a PPC running OS X 10.5.8 --------------------------+----------------------------- Reporter: josephsacco | Owner: merijn@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: leopard powerpc Port: zmq | --------------------------+----------------------------- Changes (by mf2k): * keywords: leopard, powerpc => leopard powerpc -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 14:43:28 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 14:43:28 -0000 Subject: [MacPorts] #53078: openmpi-llvm fails to configure In-Reply-To: <041.1424a3dbde95993469eb625774bd6185@macports.org> References: <041.1424a3dbde95993469eb625774bd6185@macports.org> Message-ID: <056.0a570b31638b43d36dc6cd4864d05402@macports.org> #53078: openmpi-llvm fails to configure ---------------------------+------------------------ Reporter: ksze | Owner: seanfarley Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: openmpi-llvm | ---------------------------+------------------------ Changes (by mf2k): * cc: seanfarley (removed) * owner: => seanfarley * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 14:44:31 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 14:44:31 -0000 Subject: [MacPorts] #53078: openmpi-llvm fails to configure In-Reply-To: <041.1424a3dbde95993469eb625774bd6185@macports.org> References: <041.1424a3dbde95993469eb625774bd6185@macports.org> Message-ID: <056.e80d485a45a78bf6e7ff4b7cbde04c12@macports.org> #53078: openmpi-llvm fails to configure ---------------------------+------------------------ Reporter: ksze | Owner: seanfarley Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: openmpi-llvm | ---------------------------+------------------------ Comment (by mf2k): This is the error: {{{ :info:configure configure: error: C compiler cannot create executables }}} This almost always means that you do not have the Xcode command line tools installed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 14:52:30 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 14:52:30 -0000 Subject: [MacPorts] #53078: openmpi-llvm fails to configure In-Reply-To: <041.1424a3dbde95993469eb625774bd6185@macports.org> References: <041.1424a3dbde95993469eb625774bd6185@macports.org> Message-ID: <056.7059721169112fb856c86b8e6c41d39d@macports.org> #53078: openmpi-llvm fails to configure ---------------------------+------------------------ Reporter: ksze | Owner: seanfarley Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: openmpi-llvm | ---------------------------+------------------------ Comment (by ksze): But I *do* have the command line tools installed, at least according to App Store. I have "Command Line Tools (macOS Sierra version 10.12) for Xcode", which I installed as an App Store update on December 14th. Xcode was also updated to 8.2 on the same day. I have already agreed to the license with `sudo xcodebuild -license` since the new Xcode and command line tools were installed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 14:59:12 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 14:59:12 -0000 Subject: [MacPorts] #53078: openmpi-llvm fails to configure In-Reply-To: <041.1424a3dbde95993469eb625774bd6185@macports.org> References: <041.1424a3dbde95993469eb625774bd6185@macports.org> Message-ID: <056.62b0727abad94c940dccd73628e50e53@macports.org> #53078: openmpi-llvm fails to configure ---------------------------+------------------------ Reporter: ksze | Owner: seanfarley Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: openmpi-llvm | ---------------------------+------------------------ Comment (by mf2k): Sounds like you have it setup correctly. Just for completeness, what happens when you type: {{{ xcode-select --install }}} and {{{ sudo softwareupdate --list }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 15:06:47 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 15:06:47 -0000 Subject: [MacPorts] #53078: openmpi-llvm fails to configure In-Reply-To: <041.1424a3dbde95993469eb625774bd6185@macports.org> References: <041.1424a3dbde95993469eb625774bd6185@macports.org> Message-ID: <056.296b921feba70de35ed61d1a322c7455@macports.org> #53078: openmpi-llvm fails to configure ---------------------------+------------------------ Reporter: ksze | Owner: seanfarley Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: openmpi-llvm | ---------------------------+------------------------ Comment (by mf2k): Nevermind. I see the same error when I try to install it. I too have Xcode 8.2. Maybe their configure script needs to be updated for it. It appears to be looking for: {{{ /Applications/Xcode.app/Contents/Developer/usr/bin/llvm-gcc-4.2 }}} But that no longer exists. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 15:07:28 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 15:07:28 -0000 Subject: [MacPorts] #53078: openmpi-llvm fails to configure In-Reply-To: <041.1424a3dbde95993469eb625774bd6185@macports.org> References: <041.1424a3dbde95993469eb625774bd6185@macports.org> Message-ID: <056.f07293d93abfca013ba6274cf1efe659@macports.org> #53078: openmpi-llvm fails to configure ---------------------------+------------------------ Reporter: ksze | Owner: seanfarley Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: openmpi-llvm | ---------------------------+------------------------ Comment (by ksze): {{{ $ sudo xcode-select --install xcode-select: error: command line tools are already installed, use "Software Update" to install updates }}} {{{ $ sudo softwareupdate --list Software Update Tool Copyright 2002-2015 Apple Inc. Finding available software No new software available. }}} To go back to the error: the configure stage was looking for `/Applications/Xcode.app/Contents/Developer/usr/bin/llvm-gcc-4.2`. A quick search on Google suggests that `llvm-gcc-4.2` is quite outdated. So I don't know why configure was looking for it. On my system, I have these `gcc` as part of the command line tools, but no `llvm-gcc-4.2`: {{{ $ /Applications/Xcode.app/Contents/Developer/usr/bin/gcc Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 8.0.0 (clang-800.0.42.1) Target: x86_64-apple-darwin16.3.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin }}} And `g++` in the same directory is just a symlink to `gcc` -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 16:16:29 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 16:16:29 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.fd2a8f661a96f9adac4afda24d5181d5@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Comment (by mojca): I understand DropBox. I don't think it's worth implementing ugly workarounds to fix this. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 16:26:05 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 16:26:05 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.e531c875265b38b07682b9e774c68d58@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Comment (by mojca): Other than that the port looks ok to me. I'm not sure to what extent it's ok to rename font files. And someone's idea was to change the name from "generaluser-soundfont" to "soundfont-generaluser" in line with "py-*", "qt5-*", but that's a stylistic choice. It's not like we are having lots of sound files anyway. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 16:30:52 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 16:30:52 -0000 Subject: [MacPorts] #53077: port request: chmcmd In-Reply-To: <041.e8a8c96ed295a98eb0ccd5f103127425@macports.org> References: <041.e8a8c96ed295a98eb0ccd5f103127425@macports.org> Message-ID: <056.a8cb414168fce6b701b5f5a58cc46e04@macports.org> #53077: port request: chmcmd -------------------------+----------------- Reporter: RJVB | Owner: Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fpc chmcmd | -------------------------+----------------- Comment (by RJVB): Here's a sample implementation for a `port:chmcmd-fpc` subport. I went for a subport in order to reuse some of the existing Portfile code, but also to download the rather large distfiles only once. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 17:06:03 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 17:06:03 -0000 Subject: [MacPorts] #53069: uhd +python35 build failure In-Reply-To: <041.2b7d697f3b931da26189c5328053513f@macports.org> References: <041.2b7d697f3b931da26189c5328053513f@macports.org> Message-ID: <056.957ceee32d20d3d359e241d6a6c9d93c@macports.org> #53069: uhd +python35 build failure ----------------------------+----------------------- Reporter: mf2k | Owner: michaelld Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: uhd uhd-devel | ----------------------------+----------------------- Comment (by michaelld): In [changeset:"e50de14a8031b86e01b9e1b50afb646b645557b0/macports-ports" e50de14a/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="e50de14a8031b86e01b9e1b50afb646b645557b0" uhd: add temporary patch to fix building on Python 3.5; works with older Python too; addresses ticket https://trac.macports.org/ticket/53069 . }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 17:06:32 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 17:06:32 -0000 Subject: [MacPorts] #53069: uhd +python35 build failure In-Reply-To: <041.2b7d697f3b931da26189c5328053513f@macports.org> References: <041.2b7d697f3b931da26189c5328053513f@macports.org> Message-ID: <056.df37a9296d1f30e1c93d8c34e1047b0b@macports.org> #53069: uhd +python35 build failure ----------------------------+----------------------- Reporter: mf2k | Owner: michaelld Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: uhd uhd-devel | ----------------------------+----------------------- Changes (by michaelld): * status: new => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 17:13:46 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 17:13:46 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.f19d18270a2d72e0d850a6589c591856@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Comment (by RJVB): Actually, ports depending on qt5 have a -qt5 suffix. That was the consensus a while back (in part because the qtN- prefix was already used to distinguish Qt *providing* ports), and I've been adhering to that. That would be an additional argument to put the soundfont first: these are ports providing soundfonts, not ports that depend on (or provide something for) a specific soundfont. Then again the rest of the world refers to the Fluid soundfonts, or the GeneralUser soundfont, so it would only be logical that the port names reflect the natural (English)language. Why would it not be OK to rename a font file, if it's basically just wrapping it to all lower case and removing spaces? Is checking an archlinux site for new version availability an ugly workaround? Seems less ugly to me than getting everything from a comparable site (debian's) ;) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 17:16:10 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 17:16:10 -0000 Subject: [MacPorts] #53079: cctools @895 does not build on a PPC running leopard Message-ID: <048.e4ab1f1e512b4bd19f57bb41b870c232@macports.org> #53079: cctools @895 does not build on a PPC running leopard -------------------------+--------------------- Reporter: josephsacco | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: PPC leopard | Port: cctools -------------------------+--------------------- cctools @895 does not build on a PPC running OS X 10.5.8 due to a typo in libstuff/ofile.c {{{ $ cat cctools-895-ofile.patch --- libstuff/ofile.c- 2016-12-16 11:53:10.000000000 -0500 +++ libstuff/ofile.c 2016-12-16 11:53:41.000000000 -0500 @@ -3423,7 +3423,7 @@ if(size - offset > sizeof(uint32_t)){ memcpy(&magic, addr + offset, sizeof(uint32_t)); #ifdef __BIG_ENDIAN__ - if(magic == FAT_MAGIC || (magic == FAT_MAGIC_64) + if(magic == FAT_MAGIC || (magic == FAT_MAGIC_64)) #endif /* __BIG_ENDIAN__ */ #ifdef __LITTLE_ENDIAN__ if(magic == SWAP_INT(FAT_MAGIC) || }}} A patch file containing the above patch is attached. -Joseph -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 17:16:48 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 17:16:48 -0000 Subject: [MacPorts] #53080: wireshark2 @2.2.2_0: update to 2.2.3 Message-ID: <048.41a9d54c7ea93ce59da4b444e79225f6@macports.org> #53080: wireshark2 @2.2.2_0: update to 2.2.3 -------------------------+------------------------------ Reporter: Schamschula | Owner: opendarwin.org@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: wireshark2 -------------------------+------------------------------ wireshark has been updated to version 2.2.3. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 17:17:10 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 17:17:10 -0000 Subject: [MacPorts] #53080: wireshark2 @2.2.2_0: update to 2.2.3 In-Reply-To: <048.41a9d54c7ea93ce59da4b444e79225f6@macports.org> References: <048.41a9d54c7ea93ce59da4b444e79225f6@macports.org> Message-ID: <063.9903b0a9310c40732b30ccae313d3cc0@macports.org> #53080: wireshark2 @2.2.2_0: update to 2.2.3 --------------------------+------------------------------ Reporter: Schamschula | Owner: opendarwin.org@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: wireshark2 | --------------------------+------------------------------ Changes (by Schamschula): * Attachment "Portfile-wireshark2.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 17:17:23 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 17:17:23 -0000 Subject: [MacPorts] #53079: cctools @895 does not build on a PPC running leopard In-Reply-To: <048.e4ab1f1e512b4bd19f57bb41b870c232@macports.org> References: <048.e4ab1f1e512b4bd19f57bb41b870c232@macports.org> Message-ID: <063.bd374bc301077bdac7941e27b307b42e@macports.org> #53079: cctools @895 does not build on a PPC running leopard --------------------------+------------------------- Reporter: josephsacco | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: PPC leopard Port: cctools | --------------------------+------------------------- Changes (by josephsacco): * Attachment "cctools-895-ofile.patch" added. patch file for libstudd/ofile.c -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 17:41:30 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 17:41:30 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.00b6d65e4701d10f4acef5132fba1a18@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Comment (by mojca): Yes, soundfont at the end is more natural language. What I meant with an ugly workaround was literally ugly patching of macports to pass a different browser id to avoid the blocking to be able to get the livecheck directly from upstream. Livecheck from Arch is not optimal, but probably the best we can do at the moment. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 17:57:55 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 17:57:55 -0000 Subject: [MacPorts] #53081: dblatex @0.3.7 update to 0.3.9 Message-ID: <045.5f64c342b220438ad7793e4199ed4b36@macports.org> #53081: dblatex @0.3.7 update to 0.3.9 ----------------------+--------------------- Reporter: nortcele | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: dblatex ----------------------+--------------------- Could dblatex be updated to version 0.3.9? The file dblatex-0.3.7-0.3.9.diff update the Portfile. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 17:59:00 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 17:59:00 -0000 Subject: [MacPorts] #53081: dblatex @0.3.7 update to 0.3.9 In-Reply-To: <045.5f64c342b220438ad7793e4199ed4b36@macports.org> References: <045.5f64c342b220438ad7793e4199ed4b36@macports.org> Message-ID: <060.c611bcadaf2f95350c9db7a36fb7c5d1@macports.org> #53081: dblatex @0.3.7 update to 0.3.9 -----------------------+----------------- Reporter: nortcele | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: dblatex | -----------------------+----------------- Changes (by nortcele): * Attachment "dblatex-0.3.7-0.3.9.diff" added. Patch to change dblatex 0.3.7 to 0.3.9 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 18:33:08 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 18:33:08 -0000 Subject: [MacPorts] #53080: wireshark2 @2.2.2_0: update to 2.2.3 In-Reply-To: <048.41a9d54c7ea93ce59da4b444e79225f6@macports.org> References: <048.41a9d54c7ea93ce59da4b444e79225f6@macports.org> Message-ID: <063.1bf2b9786121e11a498b0450657f879d@macports.org> #53080: wireshark2 @2.2.2_0: update to 2.2.3 --------------------------+------------------------------ Reporter: Schamschula | Owner: opendarwin.org@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: wireshark2 | --------------------------+------------------------------ Changes (by ghosthound): * status: new => closed * resolution: => fixed Comment: resolved in 0ca1972483e37c525ecacfd225f014f811a2dd00 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 18:58:03 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 18:58:03 -0000 Subject: [MacPorts] #53076: gcc47 @4.7.4_6 fails to build In-Reply-To: <043.7f4cb9cd057864586874ffa3345eb065@macports.org> References: <043.7f4cb9cd057864586874ffa3345eb065@macports.org> Message-ID: <058.7dfdca090e8782adb51f7d267c0416a3@macports.org> #53076: gcc47 @4.7.4_6 fails to build ---------------------+---------------------- Reporter: posita | Owner: mww@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gcc47 | ---------------------+---------------------- Comment (by posita): For what it's worth, `gcc47` is getting pulled in as a dependency of `pdftk`. Should I try (re)building `texinfo` and then try again? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 19:09:25 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 19:09:25 -0000 Subject: [MacPorts] #53079: cctools @895 does not build on a PPC running leopard In-Reply-To: <048.e4ab1f1e512b4bd19f57bb41b870c232@macports.org> References: <048.e4ab1f1e512b4bd19f57bb41b870c232@macports.org> Message-ID: <063.2249aff6a2058309b4143f0db4c2353e@macports.org> #53079: cctools @895 does not build on a PPC running leopard --------------------------+------------------------- Reporter: josephsacco | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: PPC leopard Port: cctools | --------------------------+------------------------- Changes (by jeremyhu): * owner: => jeremyhu * status: new => closed * resolution: => fixed Comment: In [changeset:"57f6eba329bb599a383adccdc3df1ec61c8ce3ac/macports-ports" 57f6eba/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="57f6eba329bb599a383adccdc3df1ec61c8ce3ac" cctools: Address ppc build failure Fixes https://trac.macports.org/ticket/53079 Signed-off-by: Jeremy Huddleston Sequoia }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 20:09:09 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 20:09:09 -0000 Subject: [MacPorts] #53081: dblatex @0.3.7 update to 0.3.9 In-Reply-To: <045.5f64c342b220438ad7793e4199ed4b36@macports.org> References: <045.5f64c342b220438ad7793e4199ed4b36@macports.org> Message-ID: <060.602f193929aab236c9f8a7aa8a8d60c9@macports.org> #53081: dblatex @0.3.7 update to 0.3.9 -----------------------+------------------------ Reporter: nortcele | Owner: neverpanic Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: dblatex | -----------------------+------------------------ Changes (by mf2k): * keywords: => haspatch * owner: => neverpanic * status: new => assigned * cc: neverpanic (removed) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 20:34:09 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 20:34:09 -0000 Subject: [MacPorts] #53082: can pygrib be updated to 2.0.2 Message-ID: <043.577304d3ff1656f0fe045222bc374468@macports.org> #53082: can pygrib be updated to 2.0.2 --------------------+-------------------- Reporter: basmac | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: pygrib | Port: pygrib --------------------+-------------------- Current pygrb for the various python versions, needs to be updated to 2.0.2 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 21:23:55 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 21:23:55 -0000 Subject: [MacPorts] #53072: chromaprint @1.4.0: default build fails on 10.8 and earlier due to inclusion of C++11 header In-Reply-To: <044.a96bc61b1ea83cf3406c5aadf3f008e3@macports.org> References: <044.a96bc61b1ea83cf3406c5aadf3f008e3@macports.org> Message-ID: <059.4026da28b5b61f6624e5939681e24952@macports.org> #53072: chromaprint @1.4.0: default build fails on 10.8 and earlier due to inclusion of C++11 header --------------------------+---------------------------- Reporter: dbevans | Owner: kurthindenburg Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: chromaprint | --------------------------+---------------------------- Comment (by dbevans): In [changeset:"7456389e07114f340731bc45374db63e4804dab6/macports-ports" 7456389e/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="7456389e07114f340731bc45374db63e4804dab6" gstreamer1-gst-plugins-bad: disable chromaprint plugin if cxx_stdlib is libstdc++ chromaprint 1.4+ build requires libc++. See: https://trac.macports.org/ticket/53072 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 21:57:20 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 21:57:20 -0000 Subject: [MacPorts] #51411: mlt: qt5 subport In-Reply-To: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> References: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> Message-ID: <056.533d839f2d5b2898c8398423db0784f1@macports.org> #51411: mlt: qt5 subport --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: mlt | --------------------------+---------------------- Changes (by mkae): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"9248ec92130b70576a8489c1cfca3f0322d41207/macports-ports" 9248ec9/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="9248ec92130b70576a8489c1cfca3f0322d41207" mlt-qt5: new port - add RJVB as co-maintainer - drop invalid keyword Id Closes: https://trac.macports.org/ticket/51411 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 22:03:07 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 22:03:07 -0000 Subject: [MacPorts] #51413: submission: phonon-backend-vlc with qt5 subport In-Reply-To: <041.002960c4ae3a6932302f53c42fdff330@macports.org> References: <041.002960c4ae3a6932302f53c42fdff330@macports.org> Message-ID: <056.40d311f2f180a59589a999360e43c756@macports.org> #51413: submission: phonon-backend-vlc with qt5 subport -------------------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: phonon-backend-vlc-qt5 | -------------------------------------+---------------------- Comment (by mkae): BTW, I think, René, this should be using the github PG if really required. Yet, OTOH, it would be better to make use of a released version. Is that possible? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 22:06:45 2016 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2016 22:06:45 -0000 Subject: [MacPorts] #51413: submission: phonon-backend-vlc with qt5 subport In-Reply-To: <041.002960c4ae3a6932302f53c42fdff330@macports.org> References: <041.002960c4ae3a6932302f53c42fdff330@macports.org> Message-ID: <056.1fb4243295958bfc7bdf77bda7db5a37@macports.org> #51413: submission: phonon-backend-vlc with qt5 subport -------------------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: phonon-backend-vlc-qt5 | -------------------------------------+---------------------- Comment (by mkae): Could this Portfile not also make use of cmake 1.1 already? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 00:02:53 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 00:02:53 -0000 Subject: [MacPorts] #52535: Installing libVLC fails at configure stage In-Reply-To: <053.df925bcddc583457bb7040eddda657cf@macports.org> References: <053.df925bcddc583457bb7040eddda657cf@macports.org> Message-ID: <068.6b611701ebd3dc871d36f8743d35452e@macports.org> #52535: Installing libVLC fails at configure stage -----------------------+-------------------- Reporter: rakesh@… | Owner: RJVB Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: libVLC | -----------------------+-------------------- Changes (by mkae): * status: new => closed * resolution: => fixed Comment: In [changeset:"c675c3a5f231686bb5ce73fb6bcc1ba412c75dc7/macports-ports" c675c3a/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="c675c3a5f231686bb5ce73fb6bcc1ba412c75dc7" VLC: upgrade to 2.2.4 and provide private FFMpeg v2.8.6 - moves fluidsynth support to the base feature set and patches the fluidsynth module to find sf2 repository in ${prefix} (${prefix}/share/sounds/sf2). - works around the FFMpeg v3.x incompatibility issue by shipping a private, stripped-down FFMpeg 2.8.6 copy. Closes: #27 Closes: https://trac.macports.org/ticket/52535 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 00:02:53 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 00:02:53 -0000 Subject: [MacPorts] #51413: submission: phonon-backend-vlc with qt5 subport In-Reply-To: <041.002960c4ae3a6932302f53c42fdff330@macports.org> References: <041.002960c4ae3a6932302f53c42fdff330@macports.org> Message-ID: <056.3fc00d6bf094063f98de72721952ef74@macports.org> #51413: submission: phonon-backend-vlc with qt5 subport -------------------------------------+-------------------- Reporter: RJVB | Owner: mkae Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: phonon-backend-vlc-qt5 | -------------------------------------+-------------------- Changes (by mkae): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"fcf21805750934121a047572e2b45feff90a1711/macports-ports" fcf21805/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="fcf21805750934121a047572e2b45feff90a1711" phonon-backend-vlc(-qt5): new (sub)ports Closes: https://trac.macports.org/ticket/51413 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 00:10:05 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 00:10:05 -0000 Subject: [MacPorts] #51620: py-pyqt5: fix DBus module build and pyversion conflicts, support multiple Qt5 ports In-Reply-To: <041.878bbad1021a18186c191e6780e8baed@macports.org> References: <041.878bbad1021a18186c191e6780e8baed@macports.org> Message-ID: <056.b802592513b1d4d832cde6c60c5be837@macports.org> #51620: py-pyqt5: fix DBus module build and pyversion conflicts, support multiple Qt5 ports --------------------------+-------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: py-pyqt5 | --------------------------+-------------------- Changes (by mkae): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"d4bfb29413578d369a6b48b4f54610cd1fe93fbe/macports-ports" d4bfb294/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="d4bfb29413578d369a6b48b4f54610cd1fe93fbe" py-pyqt5: fix DBus module build and pyversion conflicts - also support multiple Qt5 ports - remove invalid keyword 'Id' Closes: https://trac.macports.org/ticket/51620 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 00:15:58 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 00:15:58 -0000 Subject: [MacPorts] #52500: py-pyqt5 @5.6: conflict between Python versions In-Reply-To: <044.d13f04b961b76931b075833a7608276a@macports.org> References: <044.d13f04b961b76931b075833a7608276a@macports.org> Message-ID: <059.7cf3de090661d31443bf3a5f241d5b7a@macports.org> #52500: py-pyqt5 @5.6: conflict between Python versions -----------------------+--------------------------------- Reporter: dliessi | Owner: mamoll Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch maintainer Port: py-pyqt5 | -----------------------+--------------------------------- Changes (by mkae): * status: new => closed * resolution: => fixed Comment: This has been fixed with [changeset:"d4bfb29413578d369a6b48b4f54610cd1fe93fbe/macports-ports" d4bfb294/macports-ports], see also #51620. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 00:19:30 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 00:19:30 -0000 Subject: [MacPorts] #50697: VLC @2.2.2: build fails when using recently released ffmpeg-3.0 In-Reply-To: <044.b96c932b3aafabdbb4e873f60bedb42c@macports.org> References: <044.b96c932b3aafabdbb4e873f60bedb42c@macports.org> Message-ID: <059.122eb6f59fdd65ddd774b2b2b7aa8319@macports.org> #50697: VLC @2.2.2: build fails when using recently released ffmpeg-3.0 ----------------------------+-------------------- Reporter: dbevans | Owner: RJVB Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: VLC VLC-devel | ----------------------------+-------------------- Changes (by mkae): * status: new => closed * resolution: => fixed Comment: This was fixed with above PR. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 00:59:13 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 00:59:13 -0000 Subject: [MacPorts] #52869: OpenSceneGraph: fails to build due to changes in jpeg port In-Reply-To: <041.605a25c238eb52e5ff80ed0a94ecc86d@macports.org> References: <041.605a25c238eb52e5ff80ed0a94ecc86d@macports.org> Message-ID: <056.3803e747289781e865c40a3413e5fee9@macports.org> #52869: OpenSceneGraph: fails to build due to changes in jpeg port -------------------------------------------------+------------------------- Reporter: mkae | Owner: macports- | tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: OpenSceneGraph OpenSceneGraph- | devel | -------------------------------------------------+------------------------- Changes (by mkae): * status: new => closed * resolution: => fixed Comment: In [changeset:"20d446bcaea3ceb7a783ddd750a9791565c947f5/macports-ports" 20d446bc/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="20d446bcaea3ceb7a783ddd750a9791565c947f5" OpenSceneGraph: introduce new patch as workaround for trouble with jpeg Closes: https://trac.macports.org/ticket/52869 See: https://github.com/openscenegraph/OpenSceneGraph/issues/58 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 01:26:54 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 01:26:54 -0000 Subject: [MacPorts] #49577: polkit-qt version update and qt5 subport In-Reply-To: <041.10c457beacec7a8439cb3cbbfa864b31@macports.org> References: <041.10c457beacec7a8439cb3cbbfa864b31@macports.org> Message-ID: <056.d6ca470820f41e6f7b1fbfa891e33297@macports.org> #49577: polkit-qt version update and qt5 subport ------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: polkit-qt | ------------------------+---------------------- Changes (by mkae): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"237b9a6fb0019b0a3292ab46b363f0d5e3e7474a/macports-ports" 237b9a6f/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="237b9a6fb0019b0a3292ab46b363f0d5e3e7474a" polkit-qt(5): upgrade to 0.112.0 and introduce *-qt5(-devel) subports - removed invalid keyword 'Id' Closes: https://trac.macports.org/ticket/49577 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 01:33:28 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 01:33:28 -0000 Subject: [MacPorts] #53082: py-pygrib: update to 2.0.2 (was: can pygrib be updated to 2.0.2) In-Reply-To: <043.577304d3ff1656f0fe045222bc374468@macports.org> References: <043.577304d3ff1656f0fe045222bc374468@macports.org> Message-ID: <058.1314a12b6124c7a0acd7386e9f5c09e2@macports.org> #53082: py-pygrib: update to 2.0.2 ------------------------+---------------------- Reporter: basmac | Owner: jswhit@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-pygrib | ------------------------+---------------------- Changes (by ryandesign): * keywords: pygrib => * owner: => jswhit@… * status: new => assigned * port: pygrib => py-pygrib -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 01:38:08 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 01:38:08 -0000 Subject: [MacPorts] #49109: port modifications required by making qt4-mac co-installable with Qt5 In-Reply-To: <041.ed916633811460a610cbd879f97870ef@macports.org> References: <041.ed916633811460a610cbd879f97870ef@macports.org> Message-ID: <056.713d0dbb8d218f1065dbc71d00f23349@macports.org> #49109: port modifications required by making qt4-mac co-installable with Qt5 --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: | --------------------------+---------------------- Comment (by mkae): In [changeset:"6982d654f53f45585e157ece80ee3ed698cc5d33/macports-ports" 6982d65/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="6982d654f53f45585e157ece80ee3ed698cc5d33" py-pyqt4: fix for the depends_lib reset caused by the Python PortGroup See also: https://trac.macports.org/ticket/49109 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 01:40:41 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 01:40:41 -0000 Subject: [MacPorts] #49109: port modifications required by making qt4-mac co-installable with Qt5 In-Reply-To: <041.ed916633811460a610cbd879f97870ef@macports.org> References: <041.ed916633811460a610cbd879f97870ef@macports.org> Message-ID: <056.38e936d078bacea2615d5bf5a4bddf25@macports.org> #49109: port modifications required by making qt4-mac co-installable with Qt5 --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: | --------------------------+---------------------- Changes (by mkae): * status: assigned => closed * resolution: => fixed Comment: I already mended {{{py-pyqt5}}} in #51620, so I guess this ticket can now be considered closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 01:50:21 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 01:50:21 -0000 Subject: [MacPorts] #53083: VLC: fails to build on Sierra due to QtKit Message-ID: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> #53083: VLC: fails to build on Sierra due to QtKit --------------------+----------------- Reporter: mkae | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: sierra | Port: VLC --------------------+----------------- This rings a bell: {{{ access/qtsound.m:44:9: fatal error: 'QTKit/QTKit.h' file not found #import ^ ../doltlibtool --tag=CC --mode=compile /usr/bin/clang -DHAVE_CONFIG_H -I. -I.. -DMODULE_STRING=\"$(p="access/vcd/libcdda_plugin_la-cdrom.lo"; p="${p##*/}"; p="${p#lib}"; p="${p%_plugin*}"; p="${p%.lo}"; echo "$p")\" -D__PLUGIN__ -I./access -I./codec -I../include -I../include -I/opt/local/include -D__unix__=1 -I/opt/local/lib/live/liveMedia/include -I/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_multimedia_VLC/VLC/work/vlc-2.2.4/contrib/include -I/opt/local/include -pipe -Os -arch x86_64 -D_INTL_REDIRECT_MACROS -I/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_multimedia_VLC/VLC/work/vlc-2.2.4/contrib/include -Wall -Wextra -Wsign-compare -Wundef -Wpointer-arith -Wbad-function-cast -Wwrite-strings -Wmissing-prototypes -Wvolatile-register-var -Werror- implicit-function-declaration -pipe -fvisibility=hidden -O3 -ffast-math -funroll-loops -fomit-frame-pointer -MT access/vcd/libcdda_plugin_la- cdrom.lo -MD -MP -MF access/vcd/.deps/libcdda_plugin_la-cdrom.Tpo -c -o access/vcd/libcdda_plugin_la-cdrom.lo `test -f 'access/vcd/cdrom.c' || echo './'`access/vcd/cdrom.c 1 error generated. make[4]: *** [access/qtsound.lo] Error 1 make[4]: *** Waiting for unfinished jobs.... 4 warnings generated. mv -f stream_filter/.deps/libhttplive_plugin_la-httplive.Tpo stream_filter/.deps/libhttplive_plugin_la-httplive.Plo libtool: compile: /usr/bin/clang -DHAVE_CONFIG_H -I. -I.. -DMODULE_STRING=\"qtcapture\" -D__PLUGIN__ -I./access -I./codec -I../include -I../include -I/opt/local/include -D__unix__=1 -I/opt/local/lib/live/liveMedia/include -I/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_multimedia_VLC/VLC/work/vlc-2.2.4/contrib/include -pipe -Os -arch x86_64 -D_INTL_REDIRECT_MACROS -std=gnu99 -I/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_multimedia_VLC/VLC/work/vlc-2.2.4/contrib/include -fvisibility=hidden -O3 -ffast-math -funroll-loops -fomit-frame-pointer -MT access/qtcapture.lo -MD -MP -MF access/.deps/qtcapture.Tpo -c access/qtcapture.m -fno-common -DPIC -o access/.libs/qtcapture.o access/qtcapture.m:42:9: fatal error: 'QTKit/QTKit.h' file not found #import ^ mv -f access/vcd/.deps/libcdda_plugin_la-cdrom.Tpo access/vcd/.deps /libcdda_plugin_la-cdrom.Plo 1 error generated. make[4]: *** [access/qtcapture.lo] Error 1 8 warnings generated. }}} We had a similar problem with {{{opencv}}} in #52328. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 02:11:08 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 02:11:08 -0000 Subject: [MacPorts] #53084: py-spyder: doesn't start Message-ID: <041.1d569096fff11e8cd8896b59fb6b6912@macports.org> #53084: py-spyder: doesn't start --------------------+----------------------- Reporter: mkae | Owner: eborisch Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: py-spyder --------------------+----------------------- When I start spyder on a console I get this crash: {{{ $ spyder Traceback (most recent call last): File "/opt/local/bin/spyder", line 2, in from spyderlib import start_app File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/spyderlib/start_app.py", line 15, in from spyderlib.baseconfig import get_conf_path, running_in_mac_app File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/spyderlib/baseconfig.py", line 241, in _ = get_translation("spyderlib") File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/spyderlib/baseconfig.py", line 216, in get_translation lang = locale.getdefaultlocale()[0] File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/locale.py", line 545, in getdefaultlocale return _parse_localename(localename) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/locale.py", line 477, in _parse_localename raise ValueError, 'unknown locale: %s' % localename ValueError: unknown locale: UTF-8 }}} Setting this: {{{ MVM7-5:mkae-macports-ports marko$ LANG=C spyder Segmentation fault: 11 }}} isn't better. What am I missing? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 02:14:36 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 02:14:36 -0000 Subject: [MacPorts] #53085: py34-spyder-devel: "port info" doesn't reveal that the port has a qt5 variant Message-ID: <041.91998ee8c42a5dce6616a203ab080c87@macports.org> #53085: py34-spyder-devel: "port info" doesn't reveal that the port has a qt5 variant --------------------+------------------------------- Reporter: mkae | Owner: eborisch Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: py35-spyder-devel --------------------+------------------------------- Look at this output: {{{ $ port info py35-spyder-devel py35-spyder-devel @3.0.2 (python, devel) Variants: docs, no_anti_alias, pil, small, tiny Description: ... }}} ... there's no sign of a {{{qt5}}} variant! This is quite somewhat confusing, as the port in fact does have a {{{qt5}}} variant. What's causing this? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 02:19:41 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 02:19:41 -0000 Subject: [MacPorts] #53086: marx @5.3.1_0: update to 5.3.2 Message-ID: <043.62107c135d671f5402c5058a670ff06c@macports.org> #53086: marx @5.3.1_0: update to 5.3.2 --------------------+------------------ Reporter: hamogu | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: marx --------------------+------------------ New marx version was released on 2016-12-15. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 02:20:04 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 02:20:04 -0000 Subject: [MacPorts] #53086: marx @5.3.1_0: update to 5.3.2 In-Reply-To: <043.62107c135d671f5402c5058a670ff06c@macports.org> References: <043.62107c135d671f5402c5058a670ff06c@macports.org> Message-ID: <058.bbdab8019dddbaed572e2f496b05a0bb@macports.org> #53086: marx @5.3.1_0: update to 5.3.2 ---------------------+----------------- Reporter: hamogu | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: marx | ---------------------+----------------- Changes (by hamogu): * Attachment "Portfile-marx.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 02:22:57 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 02:22:57 -0000 Subject: [MacPorts] #53084: py-spyder: doesn't start In-Reply-To: <041.1d569096fff11e8cd8896b59fb6b6912@macports.org> References: <041.1d569096fff11e8cd8896b59fb6b6912@macports.org> Message-ID: <056.1a8c42a65852f68fa839551f94b9d7b8@macports.org> #53084: py-spyder: doesn't start -------------------------------------------+---------------------- Reporter: mkae | Owner: eborisch Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-spyder, py35-spyder-devel | -------------------------------------------+---------------------- Changes (by mkae): * port: py-spyder => py-spyder, py35-spyder-devel Comment: Same happens for the Python 3.5 devel-version! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 02:55:34 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 02:55:34 -0000 Subject: [MacPorts] #53086: marx @5.3.1_0: update to 5.3.2 In-Reply-To: <043.62107c135d671f5402c5058a670ff06c@macports.org> References: <043.62107c135d671f5402c5058a670ff06c@macports.org> Message-ID: <058.8f5f436341b1ab80e535043a17d5a8b5@macports.org> #53086: marx @5.3.1_0: update to 5.3.2 ---------------------+---------------------- Reporter: hamogu | Owner: mkae Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: marx | ---------------------+---------------------- Changes (by mkae): * owner: => mkae * status: new => assigned Comment: [https://github.com/macports/macports- ports/commit/35e2d320891dd96d489a30b879af58347fe204e6 Committed]. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 02:55:43 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 02:55:43 -0000 Subject: [MacPorts] #53086: marx @5.3.1_0: update to 5.3.2 In-Reply-To: <043.62107c135d671f5402c5058a670ff06c@macports.org> References: <043.62107c135d671f5402c5058a670ff06c@macports.org> Message-ID: <058.f741ebbab2756c05a9747bd995b4e2f1@macports.org> #53086: marx @5.3.1_0: update to 5.3.2 ---------------------+-------------------- Reporter: hamogu | Owner: mkae Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: marx | ---------------------+-------------------- Changes (by mkae): * status: assigned => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 04:55:56 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 04:55:56 -0000 Subject: [MacPorts] #52140: upx @3.09_0: update to 3.09.1 In-Reply-To: <041.114fce6d652a999429ea67176e0d870d@macports.org> References: <041.114fce6d652a999429ea67176e0d870d@macports.org> Message-ID: <056.fa507f9aa3ee2d042b32f287ea74bbca@macports.org> #52140: upx @3.09_0: update to 3.09.1 ---------------------+---------------------------- Reporter: l2dy | Owner: cedric.luthi@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: upx | ---------------------+---------------------------- Comment (by l2dy): Now 3.92 (11 Dec 2016). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 07:00:48 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 07:00:48 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.29c1a0346d663ce3514e3e82531535a2@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by mkae): That's a good idea. Let's go this way and see what the reviewers advise. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 07:25:57 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 07:25:57 -0000 Subject: [MacPorts] #46496: co-installable qt4-mac and qt5-mac step2 : qt5-mac In-Reply-To: <041.873ee2a825d3590ea03ad935ff67433c@macports.org> References: <041.873ee2a825d3590ea03ad935ff67433c@macports.org> Message-ID: <056.a78607f931432525d5c96a6c16097c31@macports.org> #46496: co-installable qt4-mac and qt5-mac step2 : qt5-mac --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: qt5-mac | --------------------------+---------------------- Comment (by mkae): @RJBB, I guess this can be considered closed, right? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 08:02:11 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 08:02:11 -0000 Subject: [MacPorts] #53017: kerberos5 @1.15: build fails with libressl In-Reply-To: <045.2e6d5c80e4930d3d8f0c88d93b24a25b@macports.org> References: <045.2e6d5c80e4930d3d8f0c88d93b24a25b@macports.org> Message-ID: <060.61e8331b23ec3b4b686db2c519011db9@macports.org> #53017: kerberos5 @1.15: build fails with libressl ------------------------+------------------------ Reporter: bK4gYuRo | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: kerberos5 | ------------------------+------------------------ Changes (by jeremyhu): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"3b3928c623f215b8afb1c388fb7223e51db0515c/macports-ports" 3b3928c6/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="3b3928c623f215b8afb1c388fb7223e51db0515c" kerberos5: Fix build with libressl Fixes https://trac.macports.org/ticket/53017 Signed-off-by: Jeremy Huddleston Sequoia }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 09:07:45 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 09:07:45 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.35aa0772337dbbad6f9f65da3451f106@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by RJVB): I'm not so sure, I think it's a good idea only if we can indeed upgrade all PortGroup qt5 statements ourselves (well, you, evidently). If not, the problem with this approach is that it is likely to shoot us in the feet w.r.t. the drop-in replacement nature of qt5-kde. We're seeing it with cmake-1.1 already: what's the adoption rate of that? Of course that file is still in flux, but concerning new features that won't change anything for ports that don't require them. I'd hate to end up in a situation where we're told that we just have to provide our own PG and probably install qt5-kde in parallel. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 09:08:57 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 09:08:57 -0000 Subject: [MacPorts] #46496: co-installable qt4-mac and qt5-mac step2 : qt5-mac In-Reply-To: <041.873ee2a825d3590ea03ad935ff67433c@macports.org> References: <041.873ee2a825d3590ea03ad935ff67433c@macports.org> Message-ID: <056.e325bfba0bcf3793b822a50d499a608c@macports.org> #46496: co-installable qt4-mac and qt5-mac step2 : qt5-mac --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: qt5-mac | --------------------------+---------------------- Comment (by RJVB): Evidently... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 09:11:10 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 09:11:10 -0000 Subject: [MacPorts] #46496: co-installable qt4-mac and qt5-mac step2 : qt5-mac In-Reply-To: <041.873ee2a825d3590ea03ad935ff67433c@macports.org> References: <041.873ee2a825d3590ea03ad935ff67433c@macports.org> Message-ID: <056.395192cd9cd1eed982c1bb912f91adb5@macports.org> #46496: co-installable qt4-mac and qt5-mac step2 : qt5-mac --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: qt5-mac | --------------------------+---------------------- Changes (by mkae): * status: assigned => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 09:16:09 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 09:16:09 -0000 Subject: [MacPorts] #53083: VLC: fails to build on Sierra due to QtKit In-Reply-To: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> References: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> Message-ID: <056.9776c40107bb22c008f4f8c7d3d53dfb@macports.org> #53083: VLC: fails to build on Sierra due to QtKit ---------------------+-------------------- Reporter: mkae | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: sierra Port: VLC | ---------------------+-------------------- Comment (by RJVB): Indeed, I c/should have foreseen this. Do you have a VM to check if this patch fixes the issue? {{{ diff --git a/multimedia/VLC/Portfile b/multimedia/VLC/Portfile index 96cd43cb..6d859d84 100644 --- a/multimedia/VLC/Portfile +++ b/multimedia/VLC/Portfile @@ -335,8 +335,11 @@ if {(${subport} eq ${name}) || (${subport} eq "lib${name}")} { configure.args-replace --disable-dbus --enable-dbus } - variant qtkit description {Enable qtcapture and qtaudio} { - configure.args-replace --disable-macosx-qtkit --enable-macosx- qtkit + if {${os.major} <= 15} { + # QTKit was disabled in 10.12 "Sierra" + variant qtkit description {Enable qtcapture and qtaudio} { + configure.args-replace --disable-macosx-qtkit --enable- macosx-qtkit + } } variant svg description {Enable SVG rendering and decoding support} { @@ -448,7 +451,10 @@ if {(${subport} eq ${name}) || (${subport} eq "lib${name}")} { patchfiles-append patch-for-lua52.diff platform macosx { - default_variants-append +quartz +qtkit + default_variants-append +quartz + if {[variant_exists qtkit]} { + default_variants-append +qtkit + } configure.args-replace --disable-macosx-eyetv --enable-macosx- eyetv }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 09:22:30 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 09:22:30 -0000 Subject: [MacPorts] #53087: ntp @4.2.8p9: libressl compatibility patch Message-ID: <046.c4c29610c66168770169a645785ef6c3@macports.org> #53087: ntp @4.2.8p9: libressl compatibility patch -----------------------+------------------- Reporter: jerryyhom | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: haspatch | Port: ntp -----------------------+------------------- Version 4.2.8p9 uses newer OpenSSL 1.1 APIs but also has backwards compatibility with older OpenSSL. If building with LibreSSL, must specify to use older APIs. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 09:23:41 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 09:23:41 -0000 Subject: [MacPorts] #53087: ntp @4.2.8p9: libressl compatibility patch In-Reply-To: <046.c4c29610c66168770169a645785ef6c3@macports.org> References: <046.c4c29610c66168770169a645785ef6c3@macports.org> Message-ID: <061.998e2b09fd983db053a1144441f76235@macports.org> #53087: ntp @4.2.8p9: libressl compatibility patch ------------------------+---------------------- Reporter: jerryyhom | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: haspatch Port: ntp | ------------------------+---------------------- Changes (by jerryyhom): * Attachment "patch-libressl-compat.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 09:24:17 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 09:24:17 -0000 Subject: [MacPorts] #53087: ntp @4.2.8p9: libressl compatibility patch In-Reply-To: <046.c4c29610c66168770169a645785ef6c3@macports.org> References: <046.c4c29610c66168770169a645785ef6c3@macports.org> Message-ID: <061.843f6a3a0bd9d75a412bf56d25dacb63@macports.org> #53087: ntp @4.2.8p9: libressl compatibility patch ------------------------+---------------------- Reporter: jerryyhom | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: haspatch Port: ntp | ------------------------+---------------------- Changes (by jerryyhom): * Attachment "Portfile-ntp.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 09:33:35 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 09:33:35 -0000 Subject: [MacPorts] #51413: submission: phonon-backend-vlc with qt5 subport In-Reply-To: <041.002960c4ae3a6932302f53c42fdff330@macports.org> References: <041.002960c4ae3a6932302f53c42fdff330@macports.org> Message-ID: <056.7ca3f374b6094c3830c65d2b8fdab520@macports.org> #51413: submission: phonon-backend-vlc with qt5 subport -------------------------------------+-------------------- Reporter: RJVB | Owner: mkae Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: phonon-backend-vlc-qt5 | -------------------------------------+-------------------- Comment (by RJVB): Yes, this could use the 1.1 PG. The qt5 portgroup was also missing a depspec for the ECM. I guess that dependency must have been introduced sometime after I created the port. I'll attach a patch in a few moments. > Wouldn't it be better to make use of a released version. Is that possible? I'm not aware of any release version tarballs and I don't see any way to fetch from KDE's git servers other than through git. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 09:36:53 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 09:36:53 -0000 Subject: [MacPorts] #51413: submission: phonon-backend-vlc with qt5 subport In-Reply-To: <041.002960c4ae3a6932302f53c42fdff330@macports.org> References: <041.002960c4ae3a6932302f53c42fdff330@macports.org> Message-ID: <056.70c66e036d77ce83564959c305466c3a@macports.org> #51413: submission: phonon-backend-vlc with qt5 subport -------------------------------------+-------------------- Reporter: RJVB | Owner: mkae Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: phonon-backend-vlc-qt5 | -------------------------------------+-------------------- Comment (by mkae): No need for a patch anymore. I fixed it already and closed this issue. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 09:43:02 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 09:43:02 -0000 Subject: [MacPorts] #51413: submission: phonon-backend-vlc with qt5 subport In-Reply-To: <041.002960c4ae3a6932302f53c42fdff330@macports.org> References: <041.002960c4ae3a6932302f53c42fdff330@macports.org> Message-ID: <056.f6ef90db23bd418c8e9ccf26b3cff1ca@macports.org> #51413: submission: phonon-backend-vlc with qt5 subport -------------------------------------+-------------------- Reporter: RJVB | Owner: mkae Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: phonon-backend-vlc-qt5 | -------------------------------------+-------------------- Changes (by RJVB): * Attachment "pbvlc.diff" added. version upgrade, missing depspec and cleanup -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 09:45:24 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 09:45:24 -0000 Subject: [MacPorts] #51413: submission: phonon-backend-vlc with qt5 subport In-Reply-To: <041.002960c4ae3a6932302f53c42fdff330@macports.org> References: <041.002960c4ae3a6932302f53c42fdff330@macports.org> Message-ID: <056.235786fa96c14b48a5ac9456707b6135@macports.org> #51413: submission: phonon-backend-vlc with qt5 subport -------------------------------------+-------------------- Reporter: RJVB | Owner: mkae Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: phonon-backend-vlc-qt5 | -------------------------------------+-------------------- Comment (by RJVB): Replying to [comment:9 mkae]: > No need for a patch anymore. I fixed it already and closed this issue. Too bad, because you also didn't check if the attached Portfile was up-to- date ;) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 09:46:55 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 09:46:55 -0000 Subject: [MacPorts] #51413: submission: phonon-backend-vlc with qt5 subport In-Reply-To: <041.002960c4ae3a6932302f53c42fdff330@macports.org> References: <041.002960c4ae3a6932302f53c42fdff330@macports.org> Message-ID: <056.0b5e4d8004db1f8857cdcca65cd6067e@macports.org> #51413: submission: phonon-backend-vlc with qt5 subport -------------------------------------+-------------------- Reporter: RJVB | Owner: mkae Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: phonon-backend-vlc-qt5 | -------------------------------------+-------------------- Changes (by RJVB): * Attachment "pbvlc.2.diff" added. oops, that should have been a build depspec -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 09:57:11 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 09:57:11 -0000 Subject: [MacPorts] #51413: submission: phonon-backend-vlc with qt5 subport In-Reply-To: <041.002960c4ae3a6932302f53c42fdff330@macports.org> References: <041.002960c4ae3a6932302f53c42fdff330@macports.org> Message-ID: <056.b4c6aadc77ebd94ddf73c988b1aae21b@macports.org> #51413: submission: phonon-backend-vlc with qt5 subport -------------------------------------+-------------------- Reporter: RJVB | Owner: mkae Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: phonon-backend-vlc-qt5 | -------------------------------------+-------------------- Comment (by mkae): In [changeset:"8ea55b2d8868eab591b0c857dfb690f389b2ab6d/macports-ports" 8ea55b2d/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="8ea55b2d8868eab591b0c857dfb690f389b2ab6d" phonon-backend-vlc-qt5: update and polish See: https://trac.macports.org/ticket/51413 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 09:58:30 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 09:58:30 -0000 Subject: [MacPorts] #51413: submission: phonon-backend-vlc with qt5 subport In-Reply-To: <041.002960c4ae3a6932302f53c42fdff330@macports.org> References: <041.002960c4ae3a6932302f53c42fdff330@macports.org> Message-ID: <056.9121c50c2dcab775a783df19c7fc3a57@macports.org> #51413: submission: phonon-backend-vlc with qt5 subport -------------------------------------+-------------------- Reporter: RJVB | Owner: mkae Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: phonon-backend-vlc-qt5 | -------------------------------------+-------------------- Comment (by mkae): > oops, that should have been a build depspec Yes, I noticed and fixed it. Thanks for the update! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 10:10:58 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 10:10:58 -0000 Subject: [MacPorts] #53083: VLC: fails to build on Sierra due to QtKit In-Reply-To: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> References: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> Message-ID: <056.f46135f7a5c8fa621cef072a1ffbb905@macports.org> #53083: VLC: fails to build on Sierra due to QtKit ---------------------+-------------------- Reporter: mkae | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: sierra Port: VLC | ---------------------+-------------------- Comment (by mkae): It's better to attach patches as a file to tickets. One can not only see the diff nicely formatted right away, but with {{{trac-patch}}} also apply it after copying the raw link without additional effort. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 10:23:48 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 10:23:48 -0000 Subject: [MacPorts] #53083: VLC: fails to build on Sierra due to QtKit In-Reply-To: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> References: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> Message-ID: <056.62e6fbe0d45a4e22db7ad32dae16aafe@macports.org> #53083: VLC: fails to build on Sierra due to QtKit ---------------------+-------------------- Reporter: mkae | Owner: mkae Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: sierra Port: VLC | ---------------------+-------------------- Changes (by mkae): * status: new => closed * owner: => mkae * resolution: => fixed Comment: In [changeset:"494466b0368a00e05b2956f453d5cc4033004198/macports-ports" 494466b0/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="494466b0368a00e05b2956f453d5cc4033004198" VLC: fix build on Sierra in analogy to opencv Thanks, René, for providing a patch! Closes: https://trac.macports.org/ticket/53083 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 10:53:08 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 10:53:08 -0000 Subject: [MacPorts] #53083: VLC: fails to build on Sierra due to QtKit In-Reply-To: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> References: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> Message-ID: <056.65e679cc2be68f0d7ae0f49904b21cc1@macports.org> #53083: VLC: fails to build on Sierra due to QtKit ---------------------+---------------------- Reporter: mkae | Owner: mkae Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: sierra Port: VLC | ---------------------+---------------------- Changes (by mkae): * status: closed => reopened * resolution: fixed => Comment: Nope, that's not yet all, as our Sierra buildbot still complains: https://build.macports.org/builders/ports-10.12_x86_64-builder/builds/14962 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 11:34:52 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 11:34:52 -0000 Subject: [MacPorts] #52914: Cannot install ld64-latest In-Reply-To: <046.f53eaf4c9cf47c98c383d5e1932beba3@macports.org> References: <046.f53eaf4c9cf47c98c383d5e1932beba3@macports.org> Message-ID: <061.b008d709bd143b9e6f28de4ad8f4a5de@macports.org> #52914: Cannot install ld64-latest --------------------------+---------------------- Reporter: petrvokac | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: invalid | Keywords: Port: ld64-latest | --------------------------+---------------------- Changes (by jeremyhu): * status: assigned => closed * resolution: => invalid -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 11:35:34 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 11:35:34 -0000 Subject: [MacPorts] #52565: libopus --enable-custom-modes In-Reply-To: <051.b8a94fc4d630bf6f75b55399d5cba74a@macports.org> References: <051.b8a94fc4d630bf6f75b55399d5cba74a@macports.org> Message-ID: <066.dfe43f3114ceb9593fb46b016ed10b2c@macports.org> #52565: libopus --enable-custom-modes --------------------------+---------------------- Reporter: irony42@… | Owner: jeremyhu Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: wontfix | Keywords: Port: libopus | --------------------------+---------------------- Changes (by jeremyhu): * status: assigned => closed * resolution: => wontfix Comment: No response, so closing as wontfix. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 12:12:26 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 12:12:26 -0000 Subject: [MacPorts] #51939: python3*: backport pyport.h fix In-Reply-To: <042.1951187832923e44cd0b117494e23a5a@macports.org> References: <042.1951187832923e44cd0b117494e23a5a@macports.org> Message-ID: <057.467fc0480456cd8ad234b1ef9260fbac@macports.org> #51939: python3*: backport pyport.h fix -------------------------------------------------+------------------------- Reporter: Ionic | Owner: | jyrkiwahlstedt Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: python31 python32 python33 | python34 python35 | -------------------------------------------------+------------------------- Changes (by Mihai Moldovan ): * status: new => closed * resolution: => fixed Comment: In [changeset:"6afd3566b7fa71540f84676597e0c285d314d1ea/macports-ports" 6afd3566/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="6afd3566b7fa71540f84676597e0c285d314d1ea" python35: backport patch from #44288. Maintainer timeout. Fixes: https://trac.macports.org/ticket/51939 Additionally, drop legacy Id line. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 12:15:54 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 12:15:54 -0000 Subject: [MacPorts] #50100: clang-3.8 fails to support Boost.Python In-Reply-To: <042.4575f4a5b70d2eabd86be24da84fd5c5@macports.org> References: <042.4575f4a5b70d2eabd86be24da84fd5c5@macports.org> Message-ID: <057.4e099c2890f906dc43ae08f809e09d1f@macports.org> #50100: clang-3.8 fails to support Boost.Python ---------------------------------------+-------------------------------- Reporter: akimd | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: C++ Port: clang-3.8 boost python34 | ---------------------------------------+-------------------------------- Changes (by Ionic): * status: new => closed * cc: Ionic (added) * resolution: => fixed Comment: Should be fixed since all python ports have been modified with a backported patch as part of #51939. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 12:23:40 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 12:23:40 -0000 Subject: [MacPorts] #53083: VLC: fails to build on Sierra due to QtKit In-Reply-To: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> References: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> Message-ID: <056.8311b4f026961bc206a1501d9042255f@macports.org> #53083: VLC: fails to build on Sierra due to QtKit ---------------------+---------------------- Reporter: mkae | Owner: mkae Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: sierra Port: VLC | ---------------------+---------------------- Comment (by RJVB): Damn, I feared something like this might happen :( I have no time to look into this now. Sucks that (if?) there is no way to provide the 10.11 builds for 10.12, it's quite likely they'll work fine :-/ -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 15:14:13 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 15:14:13 -0000 Subject: [MacPorts] #48967: submission: port:qt5-kde In-Reply-To: <041.6050f0f0647a2426eb0e97ebbbe77cbd@macports.org> References: <041.6050f0f0647a2426eb0e97ebbbe77cbd@macports.org> Message-ID: <056.2968df7d90d50b48c368be1a66bf07b6@macports.org> #48967: submission: port:qt5-kde -------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: submission | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5-kde | -------------------------+---------------------- Changes (by RJVB): * Attachment "qt5-kde.tar.3.bz2" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 15:28:49 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 15:28:49 -0000 Subject: [MacPorts] #48967: submission: port:qt5-kde In-Reply-To: <041.6050f0f0647a2426eb0e97ebbbe77cbd@macports.org> References: <041.6050f0f0647a2426eb0e97ebbbe77cbd@macports.org> Message-ID: <056.02b7a450f0d445668364bae96b7ffb97@macports.org> #48967: submission: port:qt5-kde -------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: submission | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5-kde | -------------------------+---------------------- Comment (by RJVB): Qt's Assistant (the documentation browser from the QtTools component) has seen some (apparent) regressions in recent versions, causing degraded rendering of most if not all documentation. This turned out to be because of the QtWebKit deprecation, and our new approach of building QtWebKit as a separate component. I've solved this by building the qt5-kde main port (which includes QtTools) without building the Assistant, and shipping the Assistant in a small subport of its own. This makes it possible to provide a +qtwebkit variant. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 16:00:48 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 16:00:48 -0000 Subject: [MacPorts] #50986: Dependencies fail to install because hostnames cannot be resolved because we've run out of file descriptors In-Reply-To: <065.e9b6bca89adc00c5c4582978bef7bae7@macports.org> References: <065.e9b6bca89adc00c5c4582978bef7bae7@macports.org> Message-ID: <080.0e521d5dca1d207c74874bfdddd48450@macports.org> #50986: Dependencies fail to install because hostnames cannot be resolved because we've run out of file descriptors -----------------------------------+-------------------------------- Reporter: benedikt.hielscher@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: base | Version: 2.3.4 Resolution: | Keywords: elcapitan sierra Port: | -----------------------------------+-------------------------------- Comment (by jmroot): Doing a dry-run of a kdenlive install I see about 140 of these from `lsof -c tclsh8.5`: {{{ tclsh8.5 13379 root 148u IPv4 0xcb9ddeb2ae2c8ec3 0t0 TCP 10.0.0.4:49214->196-124-232-198.static.unitasglobal.net:https (CLOSE_WAIT) }}} 198.232.124.196 is what packages.macports.org and distfiles.macports.org resolve to for me. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 16:04:39 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 16:04:39 -0000 Subject: [MacPorts] #53088: py-pyqt5 @5.6_3+webengine does not build Message-ID: <048.20a8bc8768b5c8038286e59a8237e2a9@macports.org> #53088: py-pyqt5 @5.6_3+webengine does not build -------------------------+---------------------- Reporter: josephsacco | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: py-pyqt5 -------------------------+---------------------- There is a problem with the Portfile. See below. -Joseph {{{ DEBUG: Executing variant webkit provides webkit DEBUG: wrong # args: extra words after "else" clause in "if" command while executing "if {[info exists qt5.using_kde] && ${qt5.using_kde}} { set qt5main "qt5-kde" } if {${os.major} == 11} { set qt5main "q..." (procedure "qt5.depends_component" line 5) invoked from within "qt5.depends_component qtwebkit" (procedure "variant-webkit" line 6) invoked from within "variant-webkit" invoked from within "catch "variant-${name}" result" Error: py-pyqt5: Error executing webkit: wrong # args: extra words after "else" clause in "if" command DEBUG: Error evaluating variants while executing "error "Error evaluating variants"" (procedure "mportopen" line 50) invoked from within "mportopen $porturl [array get options] [array get requested_variations]" Error: Unable to open port: Error evaluating variants}}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 16:36:04 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 16:36:04 -0000 Subject: [MacPorts] #53089: option-contains Message-ID: <041.19a86c96487f4014cd9af6521f058fd0@macports.org> #53089: option-contains -------------------------+----------------- Reporter: RJVB | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: Keywords: haspatch | Port: -------------------------+----------------- This is a little prototype patch that adds a "contains" function to the options mechanism, something I've often missed when trying to do things like adding depspecs cleanly. Example: {{{ if {![depends_build-contains port:pkgconfig]} { # pkgconfig already added by one of the included PortGroups depends_build-append port:pkgconfig } }}} or {{{ variant qtA description {support Qt component "A"} { # someday: qt5.depends_component qt-a depends_lib-append port:qt5-qt-a } variant qtB description {support Qt component "B"} { # someday: qt5.depends_component qt-b depends_lib-append port:qt5-qt-b } ... # pull in some runtime dependency made necessary by either of the qt variants, # checking for the dependency pattern rather than using multiple variant_isset calls if {[depends_lib-contains -regexp port:qt5-qt-*]} { depends_run-append port:shared_runtime_dependency } }}} Ideally the handle_option-contains procedure would scan over $args and catch all lsearch arguments, but that may be overkill. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 16:36:19 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 16:36:19 -0000 Subject: [MacPorts] #53089: option-contains In-Reply-To: <041.19a86c96487f4014cd9af6521f058fd0@macports.org> References: <041.19a86c96487f4014cd9af6521f058fd0@macports.org> Message-ID: <056.a865acee357489a09a9e5e9ba39357c7@macports.org> #53089: option-contains --------------------------+---------------------- Reporter: RJVB | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: Resolution: | Keywords: haspatch Port: | --------------------------+---------------------- Changes (by RJVB): * Attachment "patch-options-contains.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 17:15:39 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 17:15:39 -0000 Subject: [MacPorts] #53087: ntp @4.2.8p9: libressl compatibility patch In-Reply-To: <046.c4c29610c66168770169a645785ef6c3@macports.org> References: <046.c4c29610c66168770169a645785ef6c3@macports.org> Message-ID: <061.2e60562f186ffe61193b624d27c365cd@macports.org> #53087: ntp @4.2.8p9: libressl compatibility patch ------------------------+---------------------- Reporter: jerryyhom | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: haspatch Port: ntp | ------------------------+---------------------- Comment (by danielluke): Have you pushed this patch back upstream too? If it's accepted upstream, I'd be inclined to include it - but otherwise, I'd be more inclined to just switch to port:openssl style-dependency. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 17:16:35 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 17:16:35 -0000 Subject: [MacPorts] #50986: Dependencies fail to install because hostnames cannot be resolved because we've run out of file descriptors In-Reply-To: <065.e9b6bca89adc00c5c4582978bef7bae7@macports.org> References: <065.e9b6bca89adc00c5c4582978bef7bae7@macports.org> Message-ID: <080.8765e88e501aaa4e7e69dcb2d60ce845@macports.org> #50986: Dependencies fail to install because hostnames cannot be resolved because we've run out of file descriptors -----------------------------------+-------------------------------- Reporter: benedikt.hielscher@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: High | Milestone: Component: base | Version: 2.3.4 Resolution: fixed | Keywords: elcapitan sierra Port: | -----------------------------------+-------------------------------- Changes (by jmroot): * status: new => closed * resolution: => fixed Comment: In [changeset:"0fd195fba36992044da9f3fe65457bd570e0cc18/macports-base" 0fd195f/macports-base]: {{{ #!ConfigurableCommitTicketReference repository="macports-base" revision="0fd195fba36992044da9f3fe65457bd570e0cc18" Stop stale curl handles persisting Local variables in 3 of the curl subcommands should have been removed in 99d934c which switched to reusing one global handle for all connections. As a result, new handles were still created for each invocation but never cleaned up. Fixes: https://trac.macports.org/ticket/50986 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 17:19:22 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 17:19:22 -0000 Subject: [MacPorts] #50986: Dependencies fail to install because hostnames cannot be resolved because we've run out of file descriptors In-Reply-To: <065.e9b6bca89adc00c5c4582978bef7bae7@macports.org> References: <065.e9b6bca89adc00c5c4582978bef7bae7@macports.org> Message-ID: <080.6558588732f8fc5e40c83d41b900c011@macports.org> #50986: Dependencies fail to install because hostnames cannot be resolved because we've run out of file descriptors -----------------------------------+-------------------------------- Reporter: benedikt.hielscher@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: High | Milestone: MacPorts 2.4.0 Component: base | Version: 2.3.4 Resolution: fixed | Keywords: elcapitan sierra Port: | -----------------------------------+-------------------------------- Changes (by jmroot): * milestone: => MacPorts 2.4.0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 17:46:37 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 17:46:37 -0000 Subject: [MacPorts] #53090: py-pyqt* multiple Qt depspecs Message-ID: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> #53090: py-pyqt* multiple Qt depspecs -------------------------+-------------------------------- Reporter: RJVB | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: py-pyqt4, py-pyqt5 -------------------------+-------------------------------- As discussed on the ML, the py-pyqt* ports have multiple dependencies declared on the same Qt port(s), which is redundant. The attached patches fix this by including the Qt PortGroup only for the subports that actually need it. Since this is after including the Python PG, the depends_lib reset done by that PortGroup is no longer an issue either. Neither Qt PG redefines the configure mechanism (and the subports define their own anyway), so it's safe to include the Qt PortGroups last. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 17:47:10 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 17:47:10 -0000 Subject: [MacPorts] #53083: VLC: fails to build on Sierra due to QtKit In-Reply-To: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> References: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> Message-ID: <056.179b69641f9e2e452d9bab4d996445e4@macports.org> #53083: VLC: fails to build on Sierra due to QtKit ---------------------+---------------------- Reporter: mkae | Owner: mkae Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: sierra Port: VLC | ---------------------+---------------------- Comment (by dbevans): The remaining problem is the use of variant_exists. Exists in this case doesn't mean the variant is defined in the port but that the variant is asserted. Will fail on update if the variant is already set in the previously installed version which it was since this was the default. The default variant should just be declared in the clause that checks that this is not Sierra. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 17:47:24 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 17:47:24 -0000 Subject: [MacPorts] #53090: py-pyqt* multiple Qt depspecs In-Reply-To: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> References: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> Message-ID: <056.538299d76bd87f29f56f45639a60ede2@macports.org> #53090: py-pyqt* multiple Qt depspecs ---------------------------------+---------------------- Reporter: RJVB | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: py-pyqt4, py-pyqt5 | ---------------------------------+---------------------- Changes (by RJVB): * Attachment "py-pyqt4.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 17:54:34 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 17:54:34 -0000 Subject: [MacPorts] #53090: py-pyqt* multiple Qt depspecs In-Reply-To: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> References: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> Message-ID: <056.edcf62cc13526ee2c711e995eedb10a7@macports.org> #53090: py-pyqt* multiple Qt depspecs ---------------------------------+---------------------- Reporter: RJVB | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: py-pyqt4, py-pyqt5 | ---------------------------------+---------------------- Comment (by RJVB): NB: a revbump isn't necessary for py*-pyqt4 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 17:59:37 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 17:59:37 -0000 Subject: [MacPorts] #53090: py-pyqt* multiple Qt depspecs In-Reply-To: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> References: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> Message-ID: <056.6f7b86c108341da6b76cad3c22bf0d43@macports.org> #53090: py-pyqt* multiple Qt depspecs ---------------------------------+---------------------- Reporter: RJVB | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: py-pyqt4, py-pyqt5 | ---------------------------------+---------------------- Changes (by RJVB): * Attachment "py-pyqt5.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 18:01:51 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 18:01:51 -0000 Subject: [MacPorts] #53090: py-pyqt* multiple Qt depspecs In-Reply-To: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> References: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> Message-ID: <056.62230f1ba09e02d4122889ab026df3ec@macports.org> #53090: py-pyqt* multiple Qt depspecs ---------------------------------+---------------------- Reporter: RJVB | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: py-pyqt4, py-pyqt5 | ---------------------------------+---------------------- Comment (by RJVB): py*-pyqt5 need a revbump because we forgot that mcalhoun's Qt5 portgroup only declares a dependency on the QtBase component, leading to significant feature-loss and non-reproducible builds (py-pyqt builds wrappers for all installed Qt components). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 18:05:05 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 18:05:05 -0000 Subject: [MacPorts] #53083: VLC: fails to build on Sierra due to QtKit In-Reply-To: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> References: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> Message-ID: <056.b7ce4c6561fc92a37cbda3f0e8efb5f9@macports.org> #53083: VLC: fails to build on Sierra due to QtKit ---------------------+---------------------- Reporter: mkae | Owner: mkae Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: sierra Port: VLC | ---------------------+---------------------- Comment (by RJVB): You're not wrong, but the build bots don't have an installed version (AFAIK) - certainly not on 10.12 because the port didn't build there. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 18:38:16 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 18:38:16 -0000 Subject: [MacPorts] #53083: VLC: fails to build on Sierra due to QtKit In-Reply-To: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> References: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> Message-ID: <056.8c30643285f94bdbff1018c292207730@macports.org> #53083: VLC: fails to build on Sierra due to QtKit ---------------------+---------------------- Reporter: mkae | Owner: mkae Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: sierra Port: VLC | ---------------------+---------------------- Comment (by RJVB): The problem is with the open.m file, which implements the file open dialog, and which contains features provided by QtKit. Annoyingly we only have a compiled nib file which describes the actual dialog, so I'll have to tinker around to see if and how this file can build without QtKit... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 19:35:22 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 19:35:22 -0000 Subject: [MacPorts] #53083: VLC: fails to build on Sierra due to QtKit In-Reply-To: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> References: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> Message-ID: <056.ec21f4b4bdc1e1ad80a81896cd09b312@macports.org> #53083: VLC: fails to build on Sierra due to QtKit ---------------------+---------------------- Reporter: mkae | Owner: mkae Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: sierra Port: VLC | ---------------------+---------------------- Changes (by RJVB): * Attachment "VLC-for-10.12.diff" added. This patch avoids all use of QTKit in open.m on 10.12 and later -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 19:39:34 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 19:39:34 -0000 Subject: [MacPorts] #53083: VLC: fails to build on Sierra due to QtKit In-Reply-To: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> References: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> Message-ID: <056.f50d5cdc713761bd8136f82e5b43d50f@macports.org> #53083: VLC: fails to build on Sierra due to QtKit ---------------------+---------------------- Reporter: mkae | Owner: mkae Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: sierra Port: VLC | ---------------------+---------------------- Comment (by RJVB): Please test this patch on 10.12 (in a VM?) before committing. I have only addressed the issue in open.m and not even looked if there are other locations. Please, if the build halts again on missing QTKit headers, try to get a log of as many instances as possible by doing something like {{{ (cd `port work VLC`/vlc-2.2.4 ; make -wk 2>&1 > `port logfile VLC`) }}} (or {{{(cd `port work VLC`/vlc-2.2.4 ; make -wk >& `port logfile VLC`)}}} when using a *csh shell). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 22:58:54 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 22:58:54 -0000 Subject: [MacPorts] #40792: ngrep @1.45 ipv6 support In-Reply-To: <054.9ca8ea3abf0f74acaa0469790a93f016@macports.org> References: <054.9ca8ea3abf0f74acaa0469790a93f016@macports.org> Message-ID: <069.d84728108537aa50e0f797ae63899e2e@macports.org> #40792: ngrep @1.45 ipv6 support --------------------------+--------------------- Reporter: akh@… | Owner: grace@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: fixed | Keywords: Port: ngrep | --------------------------+--------------------- Changes (by kurthindenburg): * status: new => closed * resolution: => fixed Comment: In [changeset:"d4a3c2901ecd163f437f80afeb9adea00f4e2e4b/macports-ports" d4a3c290/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="d4a3c2901ecd163f437f80afeb9adea00f4e2e4b" ngrep: add various patches + use pcre - avoid sourceforge redirects - add openmaintainer for now - maintainer timeout - use macports pcre instead of ngrep's regex - use Debian's patches : ipv6, man, building, locale - enable-ipv6 closes https://trac.macports.org/ticket/40792 closes https://trac.macports.org/ticket/52840 closes https://trac.macports.org/ticket/48123 closes https://trac.macports.org/ticket/52207 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 22:58:54 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 22:58:54 -0000 Subject: [MacPorts] #52840: ngrep install issue In-Reply-To: <044.91570960171f91790181183718763f20@macports.org> References: <044.91570960171f91790181183718763f20@macports.org> Message-ID: <059.331ec23d898830c9e6485743c243326e@macports.org> #52840: ngrep install issue ----------------------+---------------------- Reporter: schnide | Owner: ​grace@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: ngrep | ----------------------+---------------------- Changes (by kurthindenburg): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"d4a3c2901ecd163f437f80afeb9adea00f4e2e4b/macports-ports" d4a3c290/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="d4a3c2901ecd163f437f80afeb9adea00f4e2e4b" ngrep: add various patches + use pcre - avoid sourceforge redirects - add openmaintainer for now - maintainer timeout - use macports pcre instead of ngrep's regex - use Debian's patches : ipv6, man, building, locale - enable-ipv6 closes https://trac.macports.org/ticket/40792 closes https://trac.macports.org/ticket/52840 closes https://trac.macports.org/ticket/48123 closes https://trac.macports.org/ticket/52207 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 22:58:54 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 22:58:54 -0000 Subject: [MacPorts] #48123: after installing ngrep, "Could not open /opt/local/lib/libpcap.A.dylib" causes rebuild on every install In-Reply-To: <054.de7bbdded19c47e0f8f46d5132cdf071@macports.org> References: <054.de7bbdded19c47e0f8f46d5132cdf071@macports.org> Message-ID: <069.9eb6746cce6fb125ae95d65743877aff@macports.org> #48123: after installing ngrep, "Could not open /opt/local/lib/libpcap.A.dylib" causes rebuild on every install ------------------------+--------------------- Reporter: audvare@… | Owner: grace@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: fixed | Keywords: Port: ngrep | ------------------------+--------------------- Changes (by kurthindenburg): * status: new => closed * resolution: => fixed Comment: In [changeset:"d4a3c2901ecd163f437f80afeb9adea00f4e2e4b/macports-ports" d4a3c290/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="d4a3c2901ecd163f437f80afeb9adea00f4e2e4b" ngrep: add various patches + use pcre - avoid sourceforge redirects - add openmaintainer for now - maintainer timeout - use macports pcre instead of ngrep's regex - use Debian's patches : ipv6, man, building, locale - enable-ipv6 closes https://trac.macports.org/ticket/40792 closes https://trac.macports.org/ticket/52840 closes https://trac.macports.org/ticket/48123 closes https://trac.macports.org/ticket/52207 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 22:58:55 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 22:58:55 -0000 Subject: [MacPorts] #52207: ngrep @1.45: build failure with libpcap @1.8.0: no yacc restart func found In-Reply-To: <060.c76afbca202a43bf06fd7cfdfdab01d0@macports.org> References: <060.c76afbca202a43bf06fd7cfdfdab01d0@macports.org> Message-ID: <075.4a1cce3de889a795be2de20a5c6833c9@macports.org> #52207: ngrep @1.45: build failure with libpcap @1.8.0: no yacc restart func found -----------------------+--------------------- Reporter: marcel@… | Owner: grace@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: ngrep | -----------------------+--------------------- Changes (by kurthindenburg): * status: new => closed * resolution: => fixed Comment: In [changeset:"d4a3c2901ecd163f437f80afeb9adea00f4e2e4b/macports-ports" d4a3c290/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="d4a3c2901ecd163f437f80afeb9adea00f4e2e4b" ngrep: add various patches + use pcre - avoid sourceforge redirects - add openmaintainer for now - maintainer timeout - use macports pcre instead of ngrep's regex - use Debian's patches : ipv6, man, building, locale - enable-ipv6 closes https://trac.macports.org/ticket/40792 closes https://trac.macports.org/ticket/52840 closes https://trac.macports.org/ticket/48123 closes https://trac.macports.org/ticket/52207 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 23:04:28 2016 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2016 23:04:28 -0000 Subject: [MacPorts] #53091: [Port Abandoned] ngrep Message-ID: <051.ffd94b1820dac4c128565182886181ec@macports.org> #53091: [Port Abandoned] ngrep ----------------------------+--------------------- Reporter: kurthindenburg | Owner: grace@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: ngrep ----------------------------+--------------------- grace hasn't been [search:grace at flipt.com active] and had a bunch of ngrep open tickets before I fixed them. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 00:10:19 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 00:10:19 -0000 Subject: [MacPorts] #53092: field3d: version update Message-ID: <056.12c228dbeacccf61d2d30dd13e7a2986@macports.org> #53092: field3d: version update ---------------------------------+--------------------- Reporter: MarcusCalhoun-Lopez | Owner: blair Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: field3d ---------------------------------+--------------------- Attached is a patch to update field3d from 1.3.2 to 1.7.2. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 00:10:37 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 00:10:37 -0000 Subject: [MacPorts] #53092: field3d: version update In-Reply-To: <056.12c228dbeacccf61d2d30dd13e7a2986@macports.org> References: <056.12c228dbeacccf61d2d30dd13e7a2986@macports.org> Message-ID: <071.a1079dcfb003abd9e0de1b20dbbdb5fc@macports.org> #53092: field3d: version update ----------------------------------+------------------- Reporter: MarcusCalhoun-Lopez | Owner: blair Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: field3d | ----------------------------------+------------------- Changes (by MarcusCalhoun-Lopez): * Attachment "field3d.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 00:24:38 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 00:24:38 -0000 Subject: [MacPorts] #53093: poll call is broken on 10.12 Message-ID: <046.fda20e612e25a320b0f393352744bebd@macports.org> #53093: poll call is broken on 10.12 -----------------------+---------------------- Reporter: jwhowarth | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: python27 -----------------------+---------------------- As reported in https://bugs.python.org/issue28456 and radar://28372390 as well ashttps://daniel.haxx.se/blog/2016/10/11/poll-on-mac-10-12-is-broken/ Apple broke the poll() call again in Sierra resulting in failures in the python test suite at... {{{ ====================================================================== FAIL: test_handle_expt (test.test_asyncore.TestAPI_UsePoll) ---------------------------------------------------------------------- Traceback (most recent call last): File "/sw/src/fink.build/python27-2.7.12-1/Python-2.7.12/Lib/test/test_asyncore.py", line 620, in test_handle_expt self.loop_waiting_for_flag(client) File "/sw/src/fink.build/python27-2.7.12-1/Python-2.7.12/Lib/test/test_asyncore.py", line 519, in loop_waiting_for_flag self.fail("flag not set") AssertionError: flag not set ---------------------------------------------------------------------- Ran 41 tests in 6.847s FAILED (failures=1) test test_asyncore failed -- Traceback (most recent call last): File "/sw/src/fink.build/python27-2.7.12-1/Python-2.7.12/Lib/test/test_asyncore.py", line 620, in test_handle_expt self.loop_waiting_for_flag(client) File "/sw/src/fink.build/python27-2.7.12-1/Python-2.7.12/Lib/test/test_asyncore.py", line 519, in loop_waiting_for_flag self.fail("flag not set") AssertionError: flag not set 1 test failed again: test_asyncore make: [test] Error 1 (ignored) }}} Since the configure in python 2.7.12 doesn't have fine enough control to eliminate the usage of the poll() calls, I resorted to... {{{ perl -pi -e 's|\#define HAVE_POLL 1||' ./pyconfig.h perl -pi -e 's|\#define HAVE_POLL_H 1||g' ./pyconfig.h perl -pi -e 's|\#define HAVE_SYS_POLL_H 1||g' ./pyconfig.h }}} post-configure which allowed fink's python27 package to successfully pass 'make check'. MacPorts will need similar hack for the 10.12 python package builds. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 00:36:29 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 00:36:29 -0000 Subject: [MacPorts] #53094: vigra: doxygen should be a build dependency Message-ID: <056.8d04443670ea455516747c30569fdd1e@macports.org> #53094: vigra: doxygen should be a build dependency ---------------------------------+--------------------- Reporter: MarcusCalhoun-Lopez | Owner: BSeppke Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: vigra ---------------------------------+--------------------- Attached is a patch to make oxygen a build dependency instead of a library dependency. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 00:36:31 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 00:36:31 -0000 Subject: [MacPorts] #53087: ntp @4.2.8p9: libressl compatibility patch In-Reply-To: <046.c4c29610c66168770169a645785ef6c3@macports.org> References: <046.c4c29610c66168770169a645785ef6c3@macports.org> Message-ID: <061.c99b90f5865e3e939682485e1bcd62f3@macports.org> #53087: ntp @4.2.8p9: libressl compatibility patch ------------------------+---------------------- Reporter: jerryyhom | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: haspatch Port: ntp | ------------------------+---------------------- Comment (by jerryyhom): Oh, good point. Hm, I was just following the style of [https://trac.macports.org/ticket/53017], but it's up to you. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 00:36:46 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 00:36:46 -0000 Subject: [MacPorts] #53094: vigra: doxygen should be a build dependency In-Reply-To: <056.8d04443670ea455516747c30569fdd1e@macports.org> References: <056.8d04443670ea455516747c30569fdd1e@macports.org> Message-ID: <071.55106a196317bb7ed2f1a9ac5d7bfa24@macports.org> #53094: vigra: doxygen should be a build dependency ----------------------------------+--------------------- Reporter: MarcusCalhoun-Lopez | Owner: BSeppke Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: vigra | ----------------------------------+--------------------- Changes (by MarcusCalhoun-Lopez): * Attachment "Portfile.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 00:45:16 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 00:45:16 -0000 Subject: [MacPorts] #52739: perl5 @5.22.2: build_arch and universal not fully respected In-Reply-To: <056.4e6ca570aea71d217bf9e4d745049e68@macports.org> References: <056.4e6ca570aea71d217bf9e4d745049e68@macports.org> Message-ID: <071.c3a1f39ca908495d009ef6cf97b3c1db@macports.org> #52739: perl5 @5.22.2: build_arch and universal not fully respected ----------------------------------+---------------------- Reporter: MarcusCalhoun-Lopez | Owner: mojca@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: perl5 | ----------------------------------+---------------------- Comment (by MarcusCalhoun-Lopez): Is there anything I can do to resolve this ticket? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 09:47:20 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 09:47:20 -0000 Subject: [MacPorts] #52845: mpv: update to 0.22 In-Reply-To: <043.e673edb81f111939a6207eb0205e5927@macports.org> References: <043.e673edb81f111939a6207eb0205e5927@macports.org> Message-ID: <058.fae542de7d64ea588f160f4b0a55b8dc@macports.org> #52845: mpv: update to 0.22 ---------------------+-------------------- Reporter: iMiKED | Owner: Ionic Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: mpv | ---------------------+-------------------- Changes (by Mihai Moldovan ): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"7f9cb6933b08cc4d0de0afafb04f4698a1fed17b/macports-ports" 7f9cb693/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="7f9cb6933b08cc4d0de0afafb04f4698a1fed17b" multimedia/mpv: update to 0.22.0. Fixes: https://trac.macports.org/ticket/52878 (#52878), fixes: https://trac.macports.org/ticket/52845 (#52845) Changes: - Refresh 10.6 patchset. - Drop legacy Id line. - Move files from ${prefix}/share/examples/mpv to ${prefix}/share/doc/mpv/examples/. - Disable previous;y missed and new features. - Add new "zsh" variant for installing zsh completions. - Reformat notes a bit to remove redundant whitespaces. - Add comment regarding configure.args and why I cannot use it (yet?) - Fix @@NETWORK@@ reinplaces. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 09:47:20 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 09:47:20 -0000 Subject: [MacPorts] #52878: mpv @0.20.0_1-network: Configuration fails due to invalid sed expression In-Reply-To: <042.5f73d87d0b34daa5211f5e824fe7ebb0@macports.org> References: <042.5f73d87d0b34daa5211f5e824fe7ebb0@macports.org> Message-ID: <057.92bfba4fe5ed568d9d7a138df9d29fd4@macports.org> #52878: mpv @0.20.0_1-network: Configuration fails due to invalid sed expression ---------------------+-------------------- Reporter: Eitot | Owner: Ionic Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: mpv | ---------------------+-------------------- Changes (by Mihai Moldovan ): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"7f9cb6933b08cc4d0de0afafb04f4698a1fed17b/macports-ports" 7f9cb693/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="7f9cb6933b08cc4d0de0afafb04f4698a1fed17b" multimedia/mpv: update to 0.22.0. Fixes: https://trac.macports.org/ticket/52878 (#52878), fixes: https://trac.macports.org/ticket/52845 (#52845) Changes: - Refresh 10.6 patchset. - Drop legacy Id line. - Move files from ${prefix}/share/examples/mpv to ${prefix}/share/doc/mpv/examples/. - Disable previous;y missed and new features. - Add new "zsh" variant for installing zsh completions. - Reformat notes a bit to remove redundant whitespaces. - Add comment regarding configure.args and why I cannot use it (yet?) - Fix @@NETWORK@@ reinplaces. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 12:17:33 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 12:17:33 -0000 Subject: [MacPorts] #53095: gnuplot@5.0.5 on macOS 10.12.1 doesn't show a wxt terminal persistently Message-ID: <053.2ae6a094f475d881dce9aa32202a490c@macports.org> #53095: gnuplot at 5.0.5 on macOS 10.12.1 doesn't show a wxt terminal persistently ------------------------------+--------------------- Reporter: twanvanderschoot | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: wxt | Port: gnuplot ------------------------------+--------------------- The summary says it all ;-) When trying to use a wxt terminal in gnuplot script, running it with gnuplot opens a window, just long enough to show it did plot the graph, but then, about as quickly it opened, the window closes and disappears. set terminal wxt persist doesn't work, neither using persist on the command line FYI: aqua and x11 terminals do work as to be expected with persist -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 14:59:53 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 14:59:53 -0000 Subject: [MacPorts] #53096: fpc upgrade to 3.0.0 Message-ID: <041.fc85ccc502eaea98765fdcdc824e367a@macports.org> #53096: fpc upgrade to 3.0.0 ----------------------+----------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: fpc ----------------------+----------------- The attached patch upgrades fpc to the current 3.0.0 release version. 1 significant modification: the install location has been set to ${prefix}/libexec/fpc, to align with the principle that this is the location for port-specific "subprefices" (cf. the Qt and llvm ports, as well as MacPorts itself). Symlinks to the port's executables are installed in ${prefix}/bin. The port also contains the proposed/prototype subport for the chmcmd utility that is of more general interest and the subject of request #53077 (which is thus superseded by this ticket). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 15:00:09 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 15:00:09 -0000 Subject: [MacPorts] #53096: fpc upgrade to 3.0.0 In-Reply-To: <041.fc85ccc502eaea98765fdcdc824e367a@macports.org> References: <041.fc85ccc502eaea98765fdcdc824e367a@macports.org> Message-ID: <056.95d6ba1f42d4e8fb2249f8062fbaebe9@macports.org> #53096: fpc upgrade to 3.0.0 ---------------------+---------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: fpc | ---------------------+---------------------- Changes (by RJVB): * Attachment "fpc.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 15:01:48 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 15:01:48 -0000 Subject: [MacPorts] #53077: port request: chmcmd In-Reply-To: <041.e8a8c96ed295a98eb0ccd5f103127425@macports.org> References: <041.e8a8c96ed295a98eb0ccd5f103127425@macports.org> Message-ID: <056.6415eab78c4a9da0a556b104d642ab75@macports.org> #53077: port request: chmcmd -------------------------+----------------- Reporter: RJVB | Owner: Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: fpc chmcmd | -------------------------+----------------- Comment (by RJVB): Superseded by #53096. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 15:03:06 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 15:03:06 -0000 Subject: [MacPorts] #53096: fpc upgrade to 3.0.0 In-Reply-To: <041.fc85ccc502eaea98765fdcdc824e367a@macports.org> References: <041.fc85ccc502eaea98765fdcdc824e367a@macports.org> Message-ID: <056.2cbc121753adf12325147e97e344b39d@macports.org> #53096: fpc upgrade to 3.0.0 ---------------------+---------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: fpc | ---------------------+---------------------- Comment (by RJVB): Note that official builds are available on SourceForge. It would thus be possible to provide a fully autonomous chmcmd port which gets the chmcmd binary from the build image, no building required. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 15:36:19 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 15:36:19 -0000 Subject: [MacPorts] #51515: py-ipyparallel: needs a dependency on py-futures In-Reply-To: <053.22bbd42ddacfcd9eac92942383794148@macports.org> References: <053.22bbd42ddacfcd9eac92942383794148@macports.org> Message-ID: <068.a55399a1bf1d1e2caa0d3b78a6d882fe@macports.org> #51515: py-ipyparallel: needs a dependency on py-futures -----------------------------+---------------------- Reporter: akss@… | Owner: stromnov Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: py-ipyparallel | -----------------------------+---------------------- Changes (by kurthindenburg): * status: new => closed * resolution: => fixed Comment: In [changeset:"bd8067c571b80f09353e75515e1d97e790fa5a0f/macports-ports" bd8067c5/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="bd8067c571b80f09353e75515e1d97e790fa5a0f" py-ipyparallel: add py-notebook dep for python 3+ py-futures for python 2.7 was added months ago remove outdated $Id$ closes https://trac.macports.org/ticket/51515 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 15:58:55 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 15:58:55 -0000 Subject: [MacPorts] #53097: kchmviewer: upgrade to v7.7 and Qt 5.6 Message-ID: <041.7dfdbca789a1a5263d0166425da4e3d4@macports.org> #53097: kchmviewer: upgrade to v7.7 and Qt 5.6 ----------------------+------------------------ Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: kchmviewer ----------------------+------------------------ port:kchmviewer has been long obsolete and might not even build anymore on recent OS X versions. The attached patch updates the port to the current 7.7 version and builds it against Qt5. It works quite nicely, both with "real Win32" .chm files and with Doxygen documents converted to .chm with `chmcmd`. A number of the patches required to get this to build and function as intended have already been submitted upstream. They can be found here: https://github.com/RJVB/macstrop/tree/master/devel/kchmviewer/files See also #53077. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 15:59:04 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 15:59:04 -0000 Subject: [MacPorts] #53097: kchmviewer: upgrade to v7.7 and Qt 5.6 In-Reply-To: <041.7dfdbca789a1a5263d0166425da4e3d4@macports.org> References: <041.7dfdbca789a1a5263d0166425da4e3d4@macports.org> Message-ID: <056.c51642e72a6dd2db00585e88fc2d67ab@macports.org> #53097: kchmviewer: upgrade to v7.7 and Qt 5.6 -------------------------+---------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: kchmviewer | -------------------------+---------------------- Changes (by RJVB): * Attachment "kchmviewer.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 16:38:21 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 16:38:21 -0000 Subject: [MacPorts] #51321: nuweb: update to 1.58 In-Reply-To: <056.d8da97af15bdcddd0b0ad16609515764@macports.org> References: <056.d8da97af15bdcddd0b0ad16609515764@macports.org> Message-ID: <071.993a1bac6ebf03a19a41a126667c1348@macports.org> #51321: nuweb: update to 1.58 ---------------------------+---------------------- Reporter: ac.russell@… | Owner: kobold@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: nuweb | ---------------------------+---------------------- Changes (by kurthindenburg): * status: new => closed * resolution: => fixed Comment: In [changeset:"d54f32218871766e1cf191408897bae233d47963/macports-ports" d54f322/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="d54f32218871766e1cf191408897bae233d47963" nuweb: update to 1.58 - add openmaintainer for now - maintainer timeout - add patch to get correct compiler settings - add CFLAGs to compile old buggy code - enable tests - some fail closes https://trac.macports.org/ticket/51321 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 16:40:38 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 16:40:38 -0000 Subject: [MacPorts] #53098: [Port Abandoned] nuweb Message-ID: <051.a4600db685bcd0daa65785b9513d7a9d@macports.org> #53098: [Port Abandoned] nuweb ----------------------------+---------------------- Reporter: kurthindenburg | Owner: kobold@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: nuweb ----------------------------+---------------------- maintainer hasn't been [search:kobold at andrewkish.name active] and had a nuweb ticket before I fixed it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 16:51:13 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 16:51:13 -0000 Subject: [MacPorts] #53082: py-pygrib: update to 2.0.2 In-Reply-To: <043.577304d3ff1656f0fe045222bc374468@macports.org> References: <043.577304d3ff1656f0fe045222bc374468@macports.org> Message-ID: <058.4e891acc27742a6110b237ec8f073704@macports.org> #53082: py-pygrib: update to 2.0.2 ------------------------+---------------------- Reporter: basmac | Owner: jswhit Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-pygrib | ------------------------+---------------------- Changes (by jswhit): * Attachment "Portfile" added. new Portfile for py-pygrib version 2.0.2 (2.0.1 no longer works with latest macports Jasper lib) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 16:51:45 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 16:51:45 -0000 Subject: [MacPorts] #53082: py-pygrib: update to 2.0.2 In-Reply-To: <043.577304d3ff1656f0fe045222bc374468@macports.org> References: <043.577304d3ff1656f0fe045222bc374468@macports.org> Message-ID: <058.d10ea7ca5fa270a93a7371cc86af97a5@macports.org> #53082: py-pygrib: update to 2.0.2 ------------------------+---------------------- Reporter: basmac | Owner: jswhit Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-pygrib | ------------------------+---------------------- Comment (by jswhit): New Portfile attached. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 16:56:33 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 16:56:33 -0000 Subject: [MacPorts] #53077: port request: chmcmd In-Reply-To: <041.e8a8c96ed295a98eb0ccd5f103127425@macports.org> References: <041.e8a8c96ed295a98eb0ccd5f103127425@macports.org> Message-ID: <056.6ecf77ba4ab8ff87321c959bf18d0096@macports.org> #53077: port request: chmcmd -------------------------+-------------------- Reporter: RJVB | Owner: Type: request | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: duplicate | Keywords: Port: fpc chmcmd | -------------------------+-------------------- Changes (by raimue): * status: new => closed * resolution: => duplicate -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 17:24:04 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 17:24:04 -0000 Subject: [MacPorts] #53082: py-pygrib: update to 2.0.2 In-Reply-To: <043.577304d3ff1656f0fe045222bc374468@macports.org> References: <043.577304d3ff1656f0fe045222bc374468@macports.org> Message-ID: <058.d965b8f026f51cd9759389f99b165e0c@macports.org> #53082: py-pygrib: update to 2.0.2 ------------------------+---------------------- Reporter: basmac | Owner: jswhit Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-pygrib | ------------------------+---------------------- Comment (by mf2k): Thanks. [https://guide.macports.org/#development.patches Per the guidelines], please instead attach a unified diff of the Portfile so we can easily see what changes you are proposing. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 17:29:24 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 17:29:24 -0000 Subject: [MacPorts] #53053: atlas build fail -- Xcode can't create dynamic library? In-Reply-To: <045.1ab6c050d554c8c359441aa8e4c1f425@macports.org> References: <045.1ab6c050d554c8c359441aa8e4c1f425@macports.org> Message-ID: <060.4f15d5cb89eccf09d0abd2050faaebb3@macports.org> #53053: atlas build fail -- Xcode can't create dynamic library? -----------------------+---------------------- Reporter: Zippyzip | Owner: Veence Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: atlas | -----------------------+---------------------- Comment (by Zippyzip): Update: I solved the problem with the dead symlink by reinstalling libgcc. Since then atlas appears to build without problem. (I am still unsure what the deal was with the first error involving XCode, but apparently it does not break the build...) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 19:50:49 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 19:50:49 -0000 Subject: [MacPorts] #53099: cctools 895 doesn't work with llvm < 3.8 Message-ID: <045.ac0c94d67f64ec79bed6dd1540959598@macports.org> #53099: cctools 895 doesn't work with llvm < 3.8 ----------------------+--------------------- Reporter: devernay | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: cctools ----------------------+--------------------- cctools 895 doesn't work with llvm < 3.8 (tried 3.4-3.7) otool -L gives: {{{ llvm-objdump: Unknown command line argument '-dylibs-used'. Try: '/opt/local/libexec/llvm-3.4/bin/llvm-objdump -help' llvm-objdump: Did you mean '-mips-os16'? llvm-objdump: Unknown command line argument '-non-verbose'. Try: '/opt/local/libexec/llvm-3.4/bin/llvm-objdump -help' llvm-objdump: Did you mean '-asm-verbose'? fatal error: otool: internal objdump command failed }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 20:03:42 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 20:03:42 -0000 Subject: [MacPorts] #53082: py-pygrib: update to 2.0.2 In-Reply-To: <043.577304d3ff1656f0fe045222bc374468@macports.org> References: <043.577304d3ff1656f0fe045222bc374468@macports.org> Message-ID: <058.71a1e8960c2428860aea643625e041ea@macports.org> #53082: py-pygrib: update to 2.0.2 ------------------------+---------------------- Reporter: basmac | Owner: jswhit Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-pygrib | ------------------------+---------------------- Comment (by jswhit): The only thing that has changed is the version number and the checksums. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 20:25:44 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 20:25:44 -0000 Subject: [MacPorts] #53093: python27: poll call is broken on 10.12 (was: poll call is broken on 10.12) In-Reply-To: <046.fda20e612e25a320b0f393352744bebd@macports.org> References: <046.fda20e612e25a320b0f393352744bebd@macports.org> Message-ID: <061.4436e3c0706a70b2176a3c429b6546ce@macports.org> #53093: python27: poll call is broken on 10.12 ------------------------+---------------------------- Reporter: jwhowarth | Owner: jyrkiwahlstedt Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: python27 | ------------------------+---------------------------- Changes (by ryandesign): * owner: => jyrkiwahlstedt * status: new => assigned Old description: > As reported in https://bugs.python.org/issue28456 and radar://28372390 as > well ashttps://daniel.haxx.se/blog/2016/10/11/poll-on-mac-10-12-is- > broken/ Apple broke the poll() call again in Sierra resulting in failures > in the python test suite at... > > {{{ > ====================================================================== > FAIL: test_handle_expt (test.test_asyncore.TestAPI_UsePoll) > ---------------------------------------------------------------------- > Traceback (most recent call last): > File > "/sw/src/fink.build/python27-2.7.12-1/Python-2.7.12/Lib/test/test_asyncore.py", > line 620, in test_handle_expt > self.loop_waiting_for_flag(client) > File > "/sw/src/fink.build/python27-2.7.12-1/Python-2.7.12/Lib/test/test_asyncore.py", > line 519, in loop_waiting_for_flag > self.fail("flag not set") > AssertionError: flag not set > > ---------------------------------------------------------------------- > Ran 41 tests in 6.847s > > FAILED (failures=1) > test test_asyncore failed -- Traceback (most recent call last): > File > "/sw/src/fink.build/python27-2.7.12-1/Python-2.7.12/Lib/test/test_asyncore.py", > line 620, in test_handle_expt > self.loop_waiting_for_flag(client) > File > "/sw/src/fink.build/python27-2.7.12-1/Python-2.7.12/Lib/test/test_asyncore.py", > line 519, in loop_waiting_for_flag > self.fail("flag not set") > AssertionError: flag not set > > 1 test failed again: > test_asyncore > make: [test] Error 1 (ignored) > > }}} > Since the configure in python 2.7.12 doesn't have fine enough control to > eliminate the usage of the poll() calls, I resorted to... > > {{{ > perl -pi -e 's|\#define HAVE_POLL 1||' ./pyconfig.h > perl -pi -e 's|\#define HAVE_POLL_H 1||g' ./pyconfig.h > perl -pi -e 's|\#define HAVE_SYS_POLL_H 1||g' > ./pyconfig.h > }}} > > post-configure which allowed fink's python27 package to successfully pass > 'make check'. MacPorts will need similar hack for the 10.12 python > package builds. New description: As reported in https://bugs.python.org/issue28456 and rdar://28372390 as well as https://daniel.haxx.se/blog/2016/10/11/poll-on-mac-10-12-is- broken/ Apple broke the poll() call again in Sierra resulting in failures in the python test suite at... {{{ ====================================================================== FAIL: test_handle_expt (test.test_asyncore.TestAPI_UsePoll) ---------------------------------------------------------------------- Traceback (most recent call last): File "/sw/src/fink.build/python27-2.7.12-1/Python-2.7.12/Lib/test/test_asyncore.py", line 620, in test_handle_expt self.loop_waiting_for_flag(client) File "/sw/src/fink.build/python27-2.7.12-1/Python-2.7.12/Lib/test/test_asyncore.py", line 519, in loop_waiting_for_flag self.fail("flag not set") AssertionError: flag not set ---------------------------------------------------------------------- Ran 41 tests in 6.847s FAILED (failures=1) test test_asyncore failed -- Traceback (most recent call last): File "/sw/src/fink.build/python27-2.7.12-1/Python-2.7.12/Lib/test/test_asyncore.py", line 620, in test_handle_expt self.loop_waiting_for_flag(client) File "/sw/src/fink.build/python27-2.7.12-1/Python-2.7.12/Lib/test/test_asyncore.py", line 519, in loop_waiting_for_flag self.fail("flag not set") AssertionError: flag not set 1 test failed again: test_asyncore make: [test] Error 1 (ignored) }}} Since the configure in python 2.7.12 doesn't have fine enough control to eliminate the usage of the poll() calls, I resorted to... {{{ perl -pi -e 's|\#define HAVE_POLL 1||' ./pyconfig.h perl -pi -e 's|\#define HAVE_POLL_H 1||g' ./pyconfig.h perl -pi -e 's|\#define HAVE_SYS_POLL_H 1||g' ./pyconfig.h }}} post-configure which allowed fink's python27 package to successfully pass 'make check'. MacPorts will need similar hack for the 10.12 python package builds. -- Comment: This only affects python27, or also older and newer versions of python? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 20:26:35 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 20:26:35 -0000 Subject: [MacPorts] #53099: cctools @895: doesn't work with llvm < 3.8 (was: cctools 895 doesn't work with llvm < 3.8) In-Reply-To: <045.ac0c94d67f64ec79bed6dd1540959598@macports.org> References: <045.ac0c94d67f64ec79bed6dd1540959598@macports.org> Message-ID: <060.8560640c00ff06ce0ab474ab96f1da74@macports.org> #53099: cctools @895: doesn't work with llvm < 3.8 -----------------------+---------------------- Reporter: devernay | Owner: jeremyhu Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cctools | -----------------------+---------------------- Changes (by ryandesign): * owner: => jeremyhu * cc: jeremyhu (removed) * status: new => assigned Old description: > cctools 895 doesn't work with llvm < 3.8 (tried 3.4-3.7) > > otool -L gives: > > {{{ > llvm-objdump: Unknown command line argument '-dylibs-used'. Try: > '/opt/local/libexec/llvm-3.4/bin/llvm-objdump -help' > llvm-objdump: Did you mean '-mips-os16'? > llvm-objdump: Unknown command line argument '-non-verbose'. Try: > '/opt/local/libexec/llvm-3.4/bin/llvm-objdump -help' > llvm-objdump: Did you mean '-asm-verbose'? > fatal error: otool: internal objdump command failed > }}} New description: cctools 895 doesn't work with llvm < 3.8 (tried 3.4-3.7) `otool -L ` gives: {{{ llvm-objdump: Unknown command line argument '-dylibs-used'. Try: '/opt/local/libexec/llvm-3.4/bin/llvm-objdump -help' llvm-objdump: Did you mean '-mips-os16'? llvm-objdump: Unknown command line argument '-non-verbose'. Try: '/opt/local/libexec/llvm-3.4/bin/llvm-objdump -help' llvm-objdump: Did you mean '-asm-verbose'? fatal error: otool: internal objdump command failed }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 20:30:10 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 20:30:10 -0000 Subject: [MacPorts] #53096: fpc: upgrade to 3.0.0 (was: fpc upgrade to 3.0.0) In-Reply-To: <041.fc85ccc502eaea98765fdcdc824e367a@macports.org> References: <041.fc85ccc502eaea98765fdcdc824e367a@macports.org> Message-ID: <056.9328e7636ed332d60404911597e90bf9@macports.org> #53096: fpc: upgrade to 3.0.0 ---------------------+---------------------- Reporter: RJVB | Owner: tenomoto Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: fpc | ---------------------+---------------------- Changes (by ryandesign): * owner: => tenomoto * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 20:31:09 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 20:31:09 -0000 Subject: [MacPorts] #53095: gnuplot @5.0.5@ on macOS 10.12.1 doesn't show a wxt terminal persistently (was: gnuplot@5.0.5 on macOS 10.12.1 doesn't show a wxt terminal persistently) In-Reply-To: <053.2ae6a094f475d881dce9aa32202a490c@macports.org> References: <053.2ae6a094f475d881dce9aa32202a490c@macports.org> Message-ID: <068.386fbd0bce52df32d095053381589e1d@macports.org> #53095: gnuplot @5.0.5@ on macOS 10.12.1 doesn't show a wxt terminal persistently -------------------------------+---------------------- Reporter: twanvanderschoot | Owner: mojca Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: sierra Port: gnuplot | -------------------------------+---------------------- Changes (by ryandesign): * keywords: wxt => sierra * status: new => assigned * owner: => mojca Old description: > The summary says it all ;-) > > When trying to use a wxt terminal in gnuplot script, running it with > gnuplot opens a window, just long enough to show it did plot the graph, > but then, about as quickly it opened, the window closes and disappears. > > set terminal wxt persist > > doesn't work, neither using persist on the command line > > FYI: aqua and x11 terminals do work as to be expected with persist New description: The summary says it all ;-) When trying to use a wxt terminal in gnuplot script, running it with gnuplot opens a window, just long enough to show it did plot the graph, but then, about as quickly it opened, the window closes and disappears. {{{ set terminal wxt persist }}} doesn't work, neither using persist on the command line FYI: aqua and x11 terminals do work as to be expected with persist -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 20:34:26 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 20:34:26 -0000 Subject: [MacPorts] #53100: Upgrade py27-eyed3 to 0.7.10 Message-ID: <046.b37f76b8844d45796a615c52296964e3@macports.org> #53100: Upgrade py27-eyed3 to 0.7.10 -----------------------+------------------------ Reporter: RichieB2B | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: py27-eyed3 -----------------------+------------------------ Please upgrade py27-eyed3 to 0.7.10 to fix this issue: {{{ Uncaught exception: global name 'log' is not defined }}} which is known upstream as https://bitbucket.org/nicfit/eyed3/issues/97 /variable-not-defined and fixed in 0.7.10 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 20:54:55 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 20:54:55 -0000 Subject: [MacPorts] #53099: cctools @895: doesn't work with llvm < 3.8 In-Reply-To: <045.ac0c94d67f64ec79bed6dd1540959598@macports.org> References: <045.ac0c94d67f64ec79bed6dd1540959598@macports.org> Message-ID: <060.48004c90e2e8bcc3104b31fa5766f955@macports.org> #53099: cctools @895: doesn't work with llvm < 3.8 -----------------------+---------------------- Reporter: devernay | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: cctools | -----------------------+---------------------- Changes (by jeremyhu): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"10cc977fe3cfc8837a30b0bff544a70f3418a4fe/macports-ports" 10cc977f/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="10cc977fe3cfc8837a30b0bff544a70f3418a4fe" cctools: Don't use llvm-otool with older llvm versions Fixes https://trac.macports.org/ticket/53099 Signed-off-by: Jeremy Huddleston Sequoia }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 21:04:44 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 21:04:44 -0000 Subject: [MacPorts] #53101: jasper fails to build +universal due to glut/OpenGL problems Message-ID: <045.bf4f074c5732d25ad8009bd2582ab00f@macports.org> #53101: jasper fails to build +universal due to glut/OpenGL problems ----------------------+-------------------- Reporter: jeremyhu | Owner: jmroot Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: jasper ----------------------+-------------------- {{{ [ 87%] Linking C executable jiv cd /opt/local/var/macports/build/_Users_jeremy_src_macports_macports- ports_graphics_jasper/jasper/work/build/src/appl && /opt/local/bin/cmake -E cmake_link_script CMakeFiles/jiv.dir/link.txt --verbose=ON /usr/bin/clang -pipe -Os -DNDEBUG -arch x86_64 -arch i386 -mmacosx- version-min=10.12 -Wl,-search_paths_first -Wl,-headerpad_max_install_names -L/opt/local/lib -Wl,-headerpad_max_install_names CMakeFiles/jiv.dir/jiv.c.o -o jiv -Wl,-rpath,/opt/local/var/macports/build /_Users_jeremy_src_macports_macports- ports_graphics_jasper/jasper/work/build/src/libjasper ../libjasper/libjasper.4.0.0.dylib /opt/local/lib/libjpeg.dylib /opt/local/lib/libglut.dylib -framework OpenGL /usr/lib/libm.dylib ld: warning: ignoring file /opt/local/lib/libglut.dylib, file was built for x86_64 which is not the architecture being linked (i386): /opt/local/lib/libglut.dylib Undefined symbols for architecture i386: "_glutCreateWindow", referenced from: _main in jiv.c.o "_glutDisplayFunc", referenced from: _main in jiv.c.o "_glutGet", referenced from: _loadimage in jiv.c.o "_glutGetModifiers", referenced from: _specialfunc in jiv.c.o "_glutInit", referenced from: _main in jiv.c.o "_glutInitDisplayMode", referenced from: _main in jiv.c.o "_glutKeyboardFunc", referenced from: _main in jiv.c.o "_glutMainLoop", referenced from: _main in jiv.c.o "_glutPostRedisplay", referenced from: _specialfunc in jiv.c.o _keyboardfunc in jiv.c.o _loadimage in jiv.c.o "_glutReshapeFunc", referenced from: _main in jiv.c.o "_glutReshapeWindow", referenced from: _loadimage in jiv.c.o "_glutSetWindowTitle", referenced from: _loadimage in jiv.c.o "_glutSpecialFunc", referenced from: _main in jiv.c.o "_glutSwapBuffers", referenced from: _displayfunc in jiv.c.o "_glutTimerFunc", referenced from: _loadimage in jiv.c.o ld: symbol(s) not found for architecture i386 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[2]: *** [src/appl/jiv] Error 1 make[2]: Leaving directory `/opt/local/var/macports/build /_Users_jeremy_src_macports_macports- ports_graphics_jasper/jasper/work/build' make[1]: *** [src/appl/CMakeFiles/jiv.dir/all] Error 2 make[1]: Leaving directory `/opt/local/var/macports/build /_Users_jeremy_src_macports_macports- ports_graphics_jasper/jasper/work/build' make: *** [all] Error 2 make: Leaving directory `/opt/local/var/macports/build /_Users_jeremy_src_macports_macports- ports_graphics_jasper/jasper/work/build' Command failed: cd "/opt/local/var/macports/build /_Users_jeremy_src_macports_macports- ports_graphics_jasper/jasper/work/build" && /usr/bin/make -w all VERBOSE=ON Exit code: 2 Error: Failed to build jasper: command execution failed Error: See /opt/local/var/macports/logs /_Users_jeremy_src_macports_macports-ports_graphics_jasper/jasper/main.log for details. Error: Follow https://guide.macports.org/#project.tickets to report a bug. }}} The build is failing because /opt/local/lib/libglut.dylib is not +universal, but that's not the main problem. /opt/local/lib/libglut.dylib is provided by the freeglut port and uses GLX, not CGL. If jasper should be using GLX, it needs to link against /opt/local/lib/libGL.dylib (from mesa) rather than OpenGL.framework. If jasper should be using CGL, then it should be using GLUT.framework and not libglut.dylib -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 21:11:08 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 21:11:08 -0000 Subject: [MacPorts] #53101: jasper fails to build +universal due to glut/OpenGL problems In-Reply-To: <045.bf4f074c5732d25ad8009bd2582ab00f@macports.org> References: <045.bf4f074c5732d25ad8009bd2582ab00f@macports.org> Message-ID: <060.d205a5136ca412d14c6e222184800d0a@macports.org> #53101: jasper fails to build +universal due to glut/OpenGL problems -----------------------+-------------------- Reporter: jeremyhu | Owner: jmroot Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: jasper | -----------------------+-------------------- Comment (by jmroot): Yeah, this is an upstream problem, possibly introduced in the process of switching to cmake. Pretty sure the intent is to use GLUT.framework on macOS. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 21:36:14 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 21:36:14 -0000 Subject: [MacPorts] #53102: jasper dylib current version regressed Message-ID: <045.1d96a7542a3d6b123e5fe23a43d0875d@macports.org> #53102: jasper dylib current version regressed ----------------------+-------------------- Reporter: jeremyhu | Owner: jmroot Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: jasper ----------------------+-------------------- After updating jasper to 2.0.6, we see the following rev-upgrade errors: {{{ ---> Scanning binaries for linking errors Incompatible library version: /opt/local/bin/jpeg2ktopam requires version 5.0.0 or later, but /opt/local/lib/libjasper.4.dylib provides version 4.0.0 Incompatible library version: /opt/local/bin/jpeg2ktopam requires version 5.0.0 or later, but /opt/local/lib/libjasper.4.dylib provides version 4.0.0 Incompatible library version: /opt/local/bin/pamtojpeg2k requires version 5.0.0 or later, but /opt/local/lib/libjasper.4.dylib provides version 4.0.0 Incompatible library version: /opt/local/bin/pamtojpeg2k requires version 5.0.0 or later, but /opt/local/lib/libjasper.4.dylib provides version 4.0.0 Incompatible library version: /opt/local/lib/gimp/2.0/plug-ins/file- jp2-load requires version 5.0.0 or later, but /opt/local/lib/libjasper.4.dylib provides version 4.0.0 Incompatible library version: /opt/local/lib/gimp/2.0/plug-ins/file- jp2-load requires version 5.0.0 or later, but /opt/local/lib/libjasper.4.dylib provides version 4.0.0 Incompatible library version: /opt/local/bin/dcraw requires version 5.0.0 or later, but /opt/local/lib/libjasper.4.dylib provides version 4.0.0 Incompatible library version: /opt/local/bin/dcraw requires version 5.0.0 or later, but /opt/local/lib/libjasper.4.dylib provides version 4.0.0 Incompatible library version: /opt/local/bin/ufraw requires version 5.0.0 or later, but /opt/local/lib/libjasper.4.dylib provides version 4.0.0 Incompatible library version: /opt/local/bin/ufraw requires version 5.0.0 or later, but /opt/local/lib/libjasper.4.dylib provides version 4.0.0 Incompatible library version: /opt/local/bin/ufraw-batch requires version 5.0.0 or later, but /opt/local/lib/libjasper.4.dylib provides version 4.0.0 Incompatible library version: /opt/local/bin/ufraw-batch requires version 5.0.0 or later, but /opt/local/lib/libjasper.4.dylib provides version 4.0.0 Incompatible library version: /opt/local/lib/gimp/2.0/plug-ins/ufraw-gimp requires version 5.0.0 or later, but /opt/local/lib/libjasper.4.dylib provides version 4.0.0 Incompatible library version: /opt/local/lib/gimp/2.0/plug-ins/ufraw-gimp requires version 5.0.0 or later, but /opt/local/lib/libjasper.4.dylib provides version 4.0.0 Incompatible library version: /opt/local/lib/gegl-0.2/jp2-load.so requires version 5.0.0 or later, but /opt/local/lib/libjasper.4.dylib provides version 4.0.0 Incompatible library version: /opt/local/lib/gegl-0.2/jp2-load.so requires version 5.0.0 or later, but /opt/local/lib/libjasper.4.dylib provides version 4.0.0 Incompatible library version: /opt/local/lib/gdk-pixbuf-2.0/2.10.0/loaders /libpixbufloader-jasper.so requires version 5.0.0 or later, but /opt/local/lib/libjasper.4.dylib provides version 4.0.0 Incompatible library version: /opt/local/lib/gdk-pixbuf-2.0/2.10.0/loaders /libpixbufloader-jasper.so requires version 5.0.0 or later, but /opt/local/lib/libjasper.4.dylib provides version 4.0.0 }}} jasper-1.900.29 had current and compat versions of 5.0.0. jasper-2.0.6 has current and compat versions of 4.0.0. If jasper-2.0.6 is backwards compatible, it should have a compat version of 5.0.0 and a current version newer than 5.0.0. If jasper-2.0.6 is not backwards compatible, it should have a different dylib id and all dependents should be revbumped. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 21:53:31 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 21:53:31 -0000 Subject: [MacPorts] #48899: haskell-platform update? In-Reply-To: <061.8be93a9ce6c44468bc198dc28f6b78b4@macports.org> References: <061.8be93a9ce6c44468bc198dc28f6b78b4@macports.org> Message-ID: <076.4f2774cb20a0c12db70f954887a644e6@macports.org> #48899: haskell-platform update? -------------------------------+------------------------ Reporter: J.Gilbey@… | Owner: neverpanic Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: haskell-platform | -------------------------------+------------------------ Comment (by kprussing): Is a major hold up still the need to create all the Portfiles to build stack? I started on a few to get pandoc updated, but then I saw how many I would need to update. So, is there a communal place where the edits are being worked on (per the first comment in the linked message)? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 22:18:39 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 22:18:39 -0000 Subject: [MacPorts] #53103: ola @0.10.2_0: update to 0.10.3 Message-ID: <048.5d5ccd2422452c9521e8cc322bbd6f26@macports.org> #53103: ola @0.10.2_0: update to 0.10.3 ---------------------------------+----------------- Reporter: peternewman | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch maintainer | Port: ola ---------------------------------+----------------- Update to reflect the new upstream release. PR here: https://github.com/macports/macports-ports/pull/102 Hopefully this is the right way to do things now you're on GitHub, this page doesn't mention those changes: https://trac.macports.org/wiki/howto/Upgrade I don't think the other maintainers have migrated to the new GitHub Trac yet, so I can't CC them. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 22:28:51 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 22:28:51 -0000 Subject: [MacPorts] #53102: jasper dylib current version regressed In-Reply-To: <045.1d96a7542a3d6b123e5fe23a43d0875d@macports.org> References: <045.1d96a7542a3d6b123e5fe23a43d0875d@macports.org> Message-ID: <060.69982122c7e10b836b37799ad86b7971@macports.org> #53102: jasper dylib current version regressed -----------------------+-------------------- Reporter: jeremyhu | Owner: jmroot Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: jasper | -----------------------+-------------------- Comment (by jmroot): More fallout from switching to cmake, which doesn't appear to let you set compatibility_version independently of the soname/major version. So libjasper.4.dylib built by cmake will always have current and compat versions of 4.x.y. https://cmake.org/cmake/help/v3.7/prop_tgt/SOVERSION.html I think we might just need to rev bump the dependents. :/ -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 22:57:10 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 22:57:10 -0000 Subject: [MacPorts] #53104: leveldb @1.19_0 - links against libstdc++ on 10.6 with libcxx, preventing function. And workaround. Message-ID: <042.f2f647b18911eb4e534a9a8b21e28d7b@macports.org> #53104: leveldb @1.19_0 - links against libstdc++ on 10.6 with libcxx, preventing function. And workaround. --------------------+--------------------- Reporter: kencu | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: leveldb --------------------+--------------------- leveldb installs, but fails to link correctly when used, on 10.6 with libc++ (and I imagine other similar systems >10.9 upgraded to libc++). {{{ $ otool -L /opt/local/lib/libleveldb.dylib /opt/local/lib/libleveldb.dylib: /opt/local/lib/libleveldb.1.dylib (compatibility version 0.0.0, current version 0.0.0) /opt/local/lib/libsnappy.1.dylib (compatibility version 5.0.0, current version 5.0.0) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.11) }}} this resulted in a link error in the port that was using leveldb: {{{ Undefined symbols for architecture x86_64: "leveldb::DB::Open(leveldb::Options const&, std::__1::basic_string, std::__1::allocator > const&, leveldb::DB**)", referenced from: Database_LevelDB::Database_LevelDB(std::__1::basic_string, std::__1::allocator > const&) in database-leveldb.cpp.o ld: symbol(s) not found for architecture x86_64 }}} the `leveldb` portfile shows some shenanigans were done due to troubles finding the Snappy library. Adding the following references to libc++ into the portfile and building it `+universal` did work: {{{ if { [variant_isset universal] } { foreach arch ${configure.universal_archs} { set merger_build_env(${arch}) "CFLAGS=\"-arch ${arch}\" CXXFLAGS=\"-arch ${arch} -stdlib=libc++\" LDFLAGS=\"-arch ${arch} -stdlib=libc++ -L${prefix}/lib\"" } }}} and generated a proper binary {{{ $ otool -L /opt/local/lib/libleveldb.dylib /opt/local/lib/libleveldb.dylib: /opt/local/lib/libleveldb.1.dylib (compatibility version 0.0.0, current version 0.0.0) /opt/local/lib/libsnappy.1.dylib (compatibility version 5.0.0, current version 5.0.0) /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 3.9.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.11) /usr/lib/libc++abi.dylib (compatibility version 1.0.0, current version 3.9.0) }}} which in the end linked correctly with the final port that needed it. Although this works, it's clearly a bit of a hack -- no doubt the proper way to the fix this issue will be obvious to someone. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 23:05:33 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 23:05:33 -0000 Subject: [MacPorts] #53102: jasper dylib current version regressed In-Reply-To: <045.1d96a7542a3d6b123e5fe23a43d0875d@macports.org> References: <045.1d96a7542a3d6b123e5fe23a43d0875d@macports.org> Message-ID: <060.17dc0843bd448f33e5835cdb7b5f3820@macports.org> #53102: jasper dylib current version regressed -----------------------+-------------------- Reporter: jeremyhu | Owner: jmroot Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: jasper | -----------------------+-------------------- Changes (by dbevans): * cc: dbevans (added) Comment: Or revert jasper to the version version until these issues are ironed out. Quite a few ports are currently broken. The few that I currently have installed are: {{{ GraphicsMagick OpenSceneGraph OpenSceneGraph-devel dcraw gdk-pixbuf2 gegl gegl-0.3 gegl-devel gimp2 gimp2-devel gimp3-devel gstreamer010-gst-plugins-bad kdelibs4 kopete libraw netpbm opencv ufraw }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 23:33:43 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 23:33:43 -0000 Subject: [MacPorts] #53101: jasper fails to build +universal due to glut/OpenGL problems In-Reply-To: <045.bf4f074c5732d25ad8009bd2582ab00f@macports.org> References: <045.bf4f074c5732d25ad8009bd2582ab00f@macports.org> Message-ID: <060.acca87f1c091af75b781eb2d8b875208@macports.org> #53101: jasper fails to build +universal due to glut/OpenGL problems ---------------------------+-------------------- Reporter: jeremyhu | Owner: jmroot Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: jasper cmake | ---------------------------+-------------------- Changes (by jmroot): * cc: michaelld (added) * port: jasper => jasper cmake Comment: Can I see your configure output? I think this may be a problem with FindGLUT.cmake. It seems to find the framework when freeglut is not installed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 23:53:52 2016 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2016 23:53:52 -0000 Subject: [MacPorts] #53102: jasper dylib current version regressed In-Reply-To: <045.1d96a7542a3d6b123e5fe23a43d0875d@macports.org> References: <045.1d96a7542a3d6b123e5fe23a43d0875d@macports.org> Message-ID: <060.d426f62b926a59c20ff11f9013848c1c@macports.org> #53102: jasper dylib current version regressed -----------------------+-------------------- Reporter: jeremyhu | Owner: jmroot Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: jasper | -----------------------+-------------------- Comment (by jmroot): In [changeset:"9d7ddf349dcdfe5ed0b2f38c5634b68d90c363a9/macports-ports" 9d7ddf34/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="9d7ddf349dcdfe5ed0b2f38c5634b68d90c363a9" jasper dependents: rev bump Upstream's switch to cmake led to an apparently inadvertent change in library versioning. See: https://trac.macports.org/ticket/53102 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 02:07:41 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 02:07:41 -0000 Subject: [MacPorts] #53101: jasper fails to build +universal due to glut/OpenGL problems In-Reply-To: <045.bf4f074c5732d25ad8009bd2582ab00f@macports.org> References: <045.bf4f074c5732d25ad8009bd2582ab00f@macports.org> Message-ID: <060.6e4b25302acd57bb678f3404d22831fe@macports.org> #53101: jasper fails to build +universal due to glut/OpenGL problems ---------------------------+-------------------- Reporter: jeremyhu | Owner: jmroot Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: jasper cmake | ---------------------------+-------------------- Comment (by jeremyhu): {{{ -- Found OpenGL: //System/Library/Frameworks/OpenGL.framework JAS_ENABLE_OPENGL: ON OpenGL library found: TRUE OpenGL include directory: //System/Library/Frameworks/OpenGL.framework OpenGL libraries: //System/Library/Frameworks/OpenGL.framework -- Found GLUT: /opt/local/lib/libglut.dylib GLUT library found: TRUE GLUT include directory: //System/Library/Frameworks/GLUT.framework/Headers GLUT libraries: /opt/local/lib/libglut.dylib;//System/Library/Frameworks/Cocoa.framework -- Looking for include file GL/glut.h -- Looking for include file GL/glut.h - found -- Looking for include file glut.h -- Looking for include file glut.h - found JAS_HAVE_GLUT_H: 1 JAS_HAVE_GL_GLUT_H: 1 CMake Warning at CMakeLists.txt:256 (message): Clearing bogus value for GLUT_Xmu_LIBRARY. CMake Warning at CMakeLists.txt:257 (message): Your version of CMake may be buggy. CMake Warning at CMakeLists.txt:261 (message): Clearing bogus value for GLUT_Xmi_LIBRARY. CMake Warning at CMakeLists.txt:262 (message): Your version of CMake may be buggy. JAS_HAVE_OPENGL: 1 -- Configuring done }}} {{{ Determining if files GL/glut.h exist passed with the following output: Change Dir: /opt/local/var/macports/build /_Users_jeremy_src_macports_macports- ports_graphics_jasper/jasper/work/build/CMakeFiles/CMakeTmp Run Build Command:"/opt/local/bin/gmake" "cmTC_400e2/fast" /opt/local/bin/gmake -f CMakeFiles/cmTC_400e2.dir/build.make CMakeFiles/cmTC_400e2.dir/build gmake[1]: Entering directory '/opt/local/var/macports/build /_Users_jeremy_src_macports_macports- ports_graphics_jasper/jasper/work/build/CMakeFiles/CMakeTmp' Building C object CMakeFiles/cmTC_400e2.dir/CheckIncludeFiles.c.o /usr/bin/clang -I//System/Library/Frameworks/GLUT.framework/Headers -pipe -Os -arch x86_64 -arch i386 -mmacosx-version-min=10.12 -o CMakeFiles/cmTC_400e2.dir/CheckIncludeFiles.c.o -c /opt/local/var/macports/build/_Users_jeremy_src_macports_macports- ports_graphics_jasper/jasper/work/build/CMakeFiles/CMakeTmp/CheckIncludeFiles.c Linking C executable cmTC_400e2 /opt/local/bin/cmake -E cmake_link_script CMakeFiles/cmTC_400e2.dir/link.txt --verbose=1 /usr/bin/clang -pipe -Os -arch x86_64 -arch i386 -mmacosx-version- min=10.12 -Wl,-search_paths_first -Wl,-headerpad_max_install_names -L/opt/local/lib -Wl,-headerpad_max_install_names CMakeFiles/cmTC_400e2.dir/CheckIncludeFiles.c.o -o cmTC_400e2 gmake[1]: Leaving directory '/opt/local/var/macports/build /_Users_jeremy_src_macports_macports- ports_graphics_jasper/jasper/work/build/CMakeFiles/CMakeTmp' Determining if files glut.h exist passed with the following output: Change Dir: /opt/local/var/macports/build /_Users_jeremy_src_macports_macports- ports_graphics_jasper/jasper/work/build/CMakeFiles/CMakeTmp Run Build Command:"/opt/local/bin/gmake" "cmTC_f0767/fast" /opt/local/bin/gmake -f CMakeFiles/cmTC_f0767.dir/build.make CMakeFiles/cmTC_f0767.dir/build gmake[1]: Entering directory '/opt/local/var/macports/build /_Users_jeremy_src_macports_macports- ports_graphics_jasper/jasper/work/build/CMakeFiles/CMakeTmp' Building C object CMakeFiles/cmTC_f0767.dir/CheckIncludeFiles.c.o /usr/bin/clang -I//System/Library/Frameworks/GLUT.framework/Headers -pipe -Os -arch x86_64 -arch i386 -mmacosx-version-min=10.12 -o CMakeFiles/cmTC_f0767.dir/CheckIncludeFiles.c.o -c /opt/local/var/macports/build/_Users_jeremy_src_macports_macports- ports_graphics_jasper/jasper/work/build/CMakeFiles/CMakeTmp/CheckIncludeFiles.c Linking C executable cmTC_f0767 /opt/local/bin/cmake -E cmake_link_script CMakeFiles/cmTC_f0767.dir/link.txt --verbose=1 /usr/bin/clang -pipe -Os -arch x86_64 -arch i386 -mmacosx-version- min=10.12 -Wl,-search_paths_first -Wl,-headerpad_max_install_names -L/opt/local/lib -Wl,-headerpad_max_install_names CMakeFiles/cmTC_f0767.dir/CheckIncludeFiles.c.o -o cmTC_f0767 gmake[1]: Leaving directory '/opt/local/var/macports/build /_Users_jeremy_src_macports_macports- ports_graphics_jasper/jasper/work/build/CMakeFiles/CMakeTmp' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 07:33:08 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 07:33:08 -0000 Subject: [MacPorts] #53095: gnuplot @5.0.5@ on macOS 10.12.1 doesn't show a wxt terminal persistently In-Reply-To: <053.2ae6a094f475d881dce9aa32202a490c@macports.org> References: <053.2ae6a094f475d881dce9aa32202a490c@macports.org> Message-ID: <068.624d1f7eee221322d108480eb81330ca@macports.org> #53095: gnuplot @5.0.5@ on macOS 10.12.1 doesn't show a wxt terminal persistently -------------------------------+---------------------- Reporter: twanvanderschoot | Owner: mojca Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: sierra Port: gnuplot | -------------------------------+---------------------- Comment (by mojca): Can you please submit that bug report upstream and raise it on the mailing list? My hardware doesn't support Sierra and I cannot test this via SSH, but even if I could, this seems to be beyond a packaging problem. It might be a problem because most of the core developer are Linux users. It look a long time before wxt even became remotely usable on Mac. It might help if you could test an earlier version of Gnuplot to check whether this is a regression or not (whether it ever worked properly on Sierra). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 07:39:28 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 07:39:28 -0000 Subject: [MacPorts] #53095: gnuplot @5.0.5@ on macOS 10.12.1 doesn't show a wxt terminal persistently In-Reply-To: <053.2ae6a094f475d881dce9aa32202a490c@macports.org> References: <053.2ae6a094f475d881dce9aa32202a490c@macports.org> Message-ID: <068.3a353fa2f6f215732a4a28ebcff4c50e@macports.org> #53095: gnuplot @5.0.5@ on macOS 10.12.1 doesn't show a wxt terminal persistently -------------------------------+---------------------- Reporter: twanvanderschoot | Owner: mojca Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: sierra Port: gnuplot | -------------------------------+---------------------- Comment (by mojca): Btw, it's not entirely impossible that wxWidgets would be to blame. (That's not to say that you shouldn't contact the gnuplot community.) Could you perhaps try to replace `wxWidgets-3.0` with `wxWidgets-3.2` inside gnuplot's `Portfile`, add `revision 1`, rebuild gnuplot and check whether that makes any difference? (It might be even worse, I don't know, we never tested gnuplot against wxWidgets 3.1.) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 08:01:00 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 08:01:00 -0000 Subject: [MacPorts] #53105: qt5-qtbase @5.6.2: configure fails due to invalid compiler *clang* Message-ID: <047.71de0adf031ec43db9842370f4b572e1@macports.org> #53105: qt5-qtbase @5.6.2: configure fails due to invalid compiler *clang* ------------------------+------------------------ Reporter: mndavidoff | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: qt5-qtbase ------------------------+------------------------ I get the following error when trying to install qt5-qtbase. {{{ $ sudo port -vs install qt5-qtbase ... ---> Configuring qt5-qtbase Error: org.macports.configure for port qt5-qtbase returned: Invalid value for configure.compiler: *clang* }}} This problem might be related to [changeset:f892d8b4fb154a13288741cb6359225e810426e1/macports-ports f892d8b]. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 08:01:10 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 08:01:10 -0000 Subject: [MacPorts] #53105: qt5-qtbase @5.6.2: configure fails due to invalid compiler *clang* In-Reply-To: <047.71de0adf031ec43db9842370f4b572e1@macports.org> References: <047.71de0adf031ec43db9842370f4b572e1@macports.org> Message-ID: <062.03f710a0f4f0a7021c2737f47e203681@macports.org> #53105: qt5-qtbase @5.6.2: configure fails due to invalid compiler *clang* -------------------------+----------------- Reporter: mndavidoff | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5-qtbase | -------------------------+----------------- Changes (by mndavidoff): * Attachment "main.log.gz" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 10:31:39 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 10:31:39 -0000 Subject: [MacPorts] #53105: qt5-qtbase @5.6.2: configure fails due to invalid compiler *clang* In-Reply-To: <047.71de0adf031ec43db9842370f4b572e1@macports.org> References: <047.71de0adf031ec43db9842370f4b572e1@macports.org> Message-ID: <062.fe16ea4f8c8f89b886383860516fb21d@macports.org> #53105: qt5-qtbase @5.6.2: configure fails due to invalid compiler *clang* -------------------------+----------------- Reporter: mndavidoff | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5-qtbase | -------------------------+----------------- Comment (by BSeppke): This error occurs for me (MacPorts 2.3.5, Mac OS X Sierra 10.12.2, XCode 8.2 (8C38)) for opencv, too. Seems, that any port with that *clang* setting cannot be build, since that compiler cannot be found. Since this is more a system than a port dependent issue it should be fixed rather soon and gain high priority. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 10:47:48 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 10:47:48 -0000 Subject: [MacPorts] #53085: py34-spyder-devel: "port info" doesn't reveal that the port has a qt5 variant In-Reply-To: <041.91998ee8c42a5dce6616a203ab080c87@macports.org> References: <041.91998ee8c42a5dce6616a203ab080c87@macports.org> Message-ID: <056.defc1ddd4070c0581a6856b67b077a5f@macports.org> #53085: py34-spyder-devel: "port info" doesn't reveal that the port has a qt5 variant --------------------------------+---------------------- Reporter: mkae | Owner: eborisch Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py35-spyder-devel | --------------------------------+---------------------- Comment (by mojca): I don't see the variant in the Portfile. Do you have local modifications? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 10:57:08 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 10:57:08 -0000 Subject: [MacPorts] #52196: Consider not using @rpath for llvm and clang libraries In-Reply-To: <045.1030a3a150440dad10264a6cf2514c08@macports.org> References: <045.1030a3a150440dad10264a6cf2514c08@macports.org> Message-ID: <060.f4246f9deb389d208556175a613d55ac@macports.org> #52196: Consider not using @rpath for llvm and clang libraries -------------------------------------------+---------------------- Reporter: jeremyhu | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: llvm-3.8 llvm-3.9 llvm-devel | -------------------------------------------+---------------------- Changes (by jeremyhu): * status: new => closed * resolution: => fixed Comment: In [changeset:"c986f1ff0be895880a3731009a0786981d2dd3db/macports-ports" c986f1f/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="c986f1ff0be895880a3731009a0786981d2dd3db" clang-3.[89]: Update dylib ids to not be @rpath-based Fixes https://trac.macports.org/ticket/52196 Signed-off-by: Jeremy Huddleston Sequoia }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 11:03:24 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 11:03:24 -0000 Subject: [MacPorts] #53106: otools -L fails with /opt/local/bin/llvm-objdump not found Message-ID: <045.5d249478d4dc3afbe6c31fd4708dc968@macports.org> #53106: otools -L fails with /opt/local/bin/llvm-objdump not found ----------------------+--------------------- Reporter: dmarteau | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: cctools ----------------------+--------------------- The command 'otools -L' fails with the following error: {{{ fatal error: otool: can't find or exec: /opt/local/bin/llvm-objdump (No such file or directory) fatal error: otool: internal objdump command failed }}} otool-classic seems to work correctly as the native command /usr/bin/otool. System: OSX 10.11.6, XCode 7.3 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 11:04:30 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 11:04:30 -0000 Subject: [MacPorts] #53065: QGIS @2.18.0 build failure In-Reply-To: <047.acd0aebce4f8fa360df821a9edae7ed0@macports.org> References: <047.acd0aebce4f8fa360df821a9edae7ed0@macports.org> Message-ID: <062.77b1de4fb07e5a35140e5abdab1cf59d@macports.org> #53065: QGIS @2.18.0 build failure -------------------------+---------------------- Reporter: BuddyVolly | Owner: Veence Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: QGIS | -------------------------+---------------------- Comment (by BuddyVolly): Dear Chris, may thanks for your answer. I am still a bit new to macports, so I tried, but failed :) I have an older version of qca (2.1.0_2+qt4) that I activated using "port activate". And I also uninstalled the newer version of qca using port uninstall. Before reinstalling gis I uninstalled all qgis versions (after the upgrade attempt it did not work anyway with either of the versions) and did a port clean. When reinstalling qgis, it is however catching the new qca version so that I am again running into this problem. Can you indicate how to tell him to use the older version? Thanks in advance, Andreas -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 11:40:57 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 11:40:57 -0000 Subject: [MacPorts] #53105: qt5-qtbase @5.6.2: configure fails due to invalid compiler *clang* In-Reply-To: <047.71de0adf031ec43db9842370f4b572e1@macports.org> References: <047.71de0adf031ec43db9842370f4b572e1@macports.org> Message-ID: <062.49ecbe861a8ac0a550f35d875d60ff9c@macports.org> #53105: qt5-qtbase @5.6.2: configure fails due to invalid compiler *clang* ---------------------------------+----------------- Reporter: mndavidoff | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5-qtbase poppler | ---------------------------------+----------------- Changes (by dbevans): * port: qt5-qtbase => qt5-qtbase poppler Comment: This error applies to any port using PortGroup qt5. For instance, poppler-qt5 now fails in a similar fashion. As previously stated, appears to have been introduced by the use of {{{ compiler.whitelist *clang* }}} in https://github.com/macports/macports- ports/commit/f892d8b4fb154a13288741cb6359225e810426e1 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 14:25:07 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 14:25:07 -0000 Subject: [MacPorts] #53103: ola @0.10.2_0: update to 0.10.3 In-Reply-To: <048.5d5ccd2422452c9521e8cc322bbd6f26@macports.org> References: <048.5d5ccd2422452c9521e8cc322bbd6f26@macports.org> Message-ID: <063.a6229489515a8c9daa9c634798535a6d@macports.org> #53103: ola @0.10.2_0: update to 0.10.3 --------------------------+--------------------------------- Reporter: peternewman | Owner: Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch maintainer Port: ola | --------------------------+--------------------------------- Changes (by raimue): * cc: nomis52@…, interface@… (added) * status: new => closed * resolution: => fixed Comment: Please, do not open both a ticket and a pull request. After the PR was merged, the ticket stayed open because there was no reference to the ticket in the commit message. You can still CC maintainers by their email address on Trac. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 14:39:52 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 14:39:52 -0000 Subject: [MacPorts] #53103: ola @0.10.2_0: update to 0.10.3 In-Reply-To: <048.5d5ccd2422452c9521e8cc322bbd6f26@macports.org> References: <048.5d5ccd2422452c9521e8cc322bbd6f26@macports.org> Message-ID: <063.056390fbe0f2c6ef89b69b4f549ceab4@macports.org> #53103: ola @0.10.2_0: update to 0.10.3 --------------------------+--------------------------------- Reporter: peternewman | Owner: Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch maintainer Port: ola | --------------------------+--------------------------------- Comment (by peternewman): Thanks Rainer and sorry for the confusion. I looked at the last PR that had been merged ( https://github.com/macports/macports-ports/pull/100 ) and it seemed to have a Trac ticket too ( https://trac.macports.org/ticket/53005 ). So which is preferred, can I just do a PR, which seems a lot easier? Is someone going to update that page, or is there another page I should look at? I normally only do this every 3-6 months, so I'll update our notes with what we should do next time. I didn't realise a CC of an email would work as it didn't offer an auto- complete unlike usernames. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 15:06:03 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 15:06:03 -0000 Subject: [MacPorts] #53085: py34-spyder-devel: "port info" doesn't reveal that the port has a qt5 variant In-Reply-To: <041.91998ee8c42a5dce6616a203ab080c87@macports.org> References: <041.91998ee8c42a5dce6616a203ab080c87@macports.org> Message-ID: <056.cdd300734d0cd26f146978df3abd4025@macports.org> #53085: py34-spyder-devel: "port info" doesn't reveal that the port has a qt5 variant --------------------------------+---------------------- Reporter: mkae | Owner: eborisch Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py35-spyder-devel | --------------------------------+---------------------- Comment (by eborisch): Only the qt5 version exists anymore; at one point there may have been variants; do you have an old portfile? I see I should as a require_active_variants for pyNN-qtpy +qt5... to make things run smoother, however. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 15:13:54 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 15:13:54 -0000 Subject: [MacPorts] #53107: py27-pygrib @2.0.2 update Message-ID: <044.366915d58c1d778030237b2c332b9007@macports.org> #53107: py27-pygrib @2.0.2 update ---------------------+------------------------- Reporter: ForTozs | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: py27-pygrib ---------------------+------------------------- Here is a patch to update pygrib 2.0.1 to 2.0.2. This fixes a problem related to JasPer: {{{error: no member named 'inmem_' in 'jas_image_t'}}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 15:14:31 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 15:14:31 -0000 Subject: [MacPorts] #53107: py27-pygrib @2.0.2 update In-Reply-To: <044.366915d58c1d778030237b2c332b9007@macports.org> References: <044.366915d58c1d778030237b2c332b9007@macports.org> Message-ID: <059.2124614a73e7b5b06d97155799edf969@macports.org> #53107: py27-pygrib @2.0.2 update --------------------------+----------------- Reporter: ForTozs | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py27-pygrib | --------------------------+----------------- Changes (by ForTozs): * Attachment "py27-pygrib.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 15:20:45 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 15:20:45 -0000 Subject: [MacPorts] #53088: py-pyqt5 @5.6_3+webengine does not build In-Reply-To: <048.20a8bc8768b5c8038286e59a8237e2a9@macports.org> References: <048.20a8bc8768b5c8038286e59a8237e2a9@macports.org> Message-ID: <063.898a8221b3339d031bd150320dbecdf9@macports.org> #53088: py-pyqt5 @5.6_3+webengine does not build --------------------------+------------------- Reporter: josephsacco | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: py-pyqt5 | --------------------------+------------------- Comment (by josephsacco): Something new has appeared. The build process now fails during the configure stage for both py27 and py35. [See below] -Joseph {{{ ---> Configuring py27-pyqt5 Error: org.macports.configure for port py27-pyqt5 returned: Invalid value for configure.compiler: *clang* DEBUG: Error code: NONE DEBUG: Backtrace: Invalid value for configure.compiler: *clang* while executing "[ditem_key $ditem prerun] $targetname" }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 15:21:18 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 15:21:18 -0000 Subject: [MacPorts] #53085: py34-spyder-devel: "port info" doesn't reveal that the port has a qt5 variant In-Reply-To: <041.91998ee8c42a5dce6616a203ab080c87@macports.org> References: <041.91998ee8c42a5dce6616a203ab080c87@macports.org> Message-ID: <056.74e54031d37494d88cfcfbc632b32a27@macports.org> #53085: py34-spyder-devel: "port info" doesn't reveal that the port has a qt5 variant --------------------------------+---------------------- Reporter: mkae | Owner: eborisch Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: py35-spyder-devel | --------------------------------+---------------------- Changes (by eborisch): * status: new => closed * resolution: => fixed Comment: Added {{{reqiure_active_variants pyNN-qtpy +qt5}}} in https://github.com/macports/macports- ports/commit/cfcc107c07089f5a187e5bb06b156502ef97792b -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 16:38:19 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 16:38:19 -0000 Subject: [MacPorts] #51386: Remove JRuby dependency on Kaffe In-Reply-To: <047.259218f6dcac4307bb70bbdc5feafc43@macports.org> References: <047.259218f6dcac4307bb70bbdc5feafc43@macports.org> Message-ID: <062.c0ee2e4e4746e9d93c43e3d8a99cd52d@macports.org> #51386: Remove JRuby dependency on Kaffe --------------------------+------------------ Reporter: mouse07410 | Owner: ci42 Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: jruby | --------------------------+------------------ Comment (by mouse07410): Any updates? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 16:38:44 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 16:38:44 -0000 Subject: [MacPorts] #53087: ntp @4.2.8p9: libressl compatibility patch In-Reply-To: <046.c4c29610c66168770169a645785ef6c3@macports.org> References: <046.c4c29610c66168770169a645785ef6c3@macports.org> Message-ID: <061.719a3ed95fbac74e9b37070e25bb9c50@macports.org> #53087: ntp @4.2.8p9: libressl compatibility patch ------------------------+---------------------- Reporter: jerryyhom | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: haspatch Port: ntp | ------------------------+---------------------- Comment (by danielluke): Replying to [comment:2 jerryyhom]: > I was just following the style of [https://trac.macports.org/ticket/53017], but it's up to you. It's totally valid, I'd just like to see it submitted upstream as well (so everyone, not just MacPorts users, can benefit). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 18:23:08 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 18:23:08 -0000 Subject: [MacPorts] #53105: qt5-qtbase @5.6.2: configure fails due to invalid compiler *clang* In-Reply-To: <047.71de0adf031ec43db9842370f4b572e1@macports.org> References: <047.71de0adf031ec43db9842370f4b572e1@macports.org> Message-ID: <062.387e41e02af5fd00e438dffb33926ae0@macports.org> #53105: qt5-qtbase @5.6.2: configure fails due to invalid compiler *clang* ---------------------------------+--------------------------------- Reporter: mndavidoff | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: qt5-qtbase poppler | ---------------------------------+--------------------------------- Changes (by MarcusCalhoun-Lopez): * owner: => MarcusCalhoun-Lopez * status: new => closed * resolution: => fixed Comment: In [changeset:"e3fe45d39c5334a22a835de3a2650f743c01de54/macports-ports" e3fe45d3/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="e3fe45d39c5334a22a835de3a2650f743c01de54" qt5: revert https://github.com/macports/macports- ports/commit/f892d8b4fb154a13288741cb6359225e810426e1 Fixes https://trac.macports.org/ticket/53105 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 19:04:46 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 19:04:46 -0000 Subject: [MacPorts] #53105: qt5-qtbase @5.6.2: configure fails due to invalid compiler *clang* In-Reply-To: <047.71de0adf031ec43db9842370f4b572e1@macports.org> References: <047.71de0adf031ec43db9842370f4b572e1@macports.org> Message-ID: <062.809c42c87f0c773b1d79cf14493c7885@macports.org> #53105: qt5-qtbase @5.6.2: configure fails due to invalid compiler *clang* ---------------------------------+--------------------------------- Reporter: mndavidoff | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: qt5-qtbase poppler | ---------------------------------+--------------------------------- Changes (by jmroot): * cc: mcalhoun@…, jeremyhu@… (removed) * cc: jeremyhu (added) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 19:07:45 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 19:07:45 -0000 Subject: [MacPorts] #53105: qt5-qtbase @5.6.2: configure fails due to invalid compiler *clang* In-Reply-To: <047.71de0adf031ec43db9842370f4b572e1@macports.org> References: <047.71de0adf031ec43db9842370f4b572e1@macports.org> Message-ID: <062.7babd5d51b9a0d077d461cc84ab42c86@macports.org> #53105: qt5-qtbase @5.6.2: configure fails due to invalid compiler *clang* ---------------------------------+--------------------------------- Reporter: mndavidoff | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: qt5-qtbase poppler | ---------------------------------+--------------------------------- Comment (by jmroot): In [changeset:"d028ea23259ad8e6bac56bec31c1bf47acfbc796/macports-ports" d028ea23/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="d028ea23259ad8e6bac56bec31c1bf47acfbc796" Achieve the intent of f892d8b Globs can be used in the blacklist, so blacklist all the gccs, which is the same as whitelisting all the clangs, since those are the only two kinds of compiler in compiler.fallback. See: https://trac.macports.org/ticket/53105 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 19:59:08 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 19:59:08 -0000 Subject: [MacPorts] #53108: openssh 7.4p1 release Message-ID: <047.1e7e14f0247ff7de5f469ecdc5024132@macports.org> #53108: openssh 7.4p1 release ------------------------+--------------------- Reporter: danielluke | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: openssh ------------------------+--------------------- As per usual, a simple version bump works for me (but I did not test the +hpn or +gsskex variants - which usually need some attention). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 19:59:25 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 19:59:25 -0000 Subject: [MacPorts] #53108: openssh 7.4p1 release In-Reply-To: <047.1e7e14f0247ff7de5f469ecdc5024132@macports.org> References: <047.1e7e14f0247ff7de5f469ecdc5024132@macports.org> Message-ID: <062.e5cc6fa575ec2183f5d08d1d6236c695@macports.org> #53108: openssh 7.4p1 release -------------------------+----------------- Reporter: danielluke | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: openssh | -------------------------+----------------- Changes (by danielluke): * Attachment "openssh_version_bump.diff" added. simple version bump -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 20:40:56 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 20:40:56 -0000 Subject: [MacPorts] #53085: py34-spyder-devel: "port info" doesn't reveal that the port has a qt5 variant In-Reply-To: <041.91998ee8c42a5dce6616a203ab080c87@macports.org> References: <041.91998ee8c42a5dce6616a203ab080c87@macports.org> Message-ID: <056.da6e2ad994c0d670fab70fe48ee526e4@macports.org> #53085: py34-spyder-devel: "port info" doesn't reveal that the port has a qt5 variant --------------------------------+---------------------- Reporter: mkae | Owner: eborisch Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: py35-spyder-devel | --------------------------------+---------------------- Comment (by mkae): Thanks, Eric, that looks more consistent. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 21:32:09 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 21:32:09 -0000 Subject: [MacPorts] #53109: port select fails if invalid exists Message-ID: <048.2f7b828e94be005e9bddd1467ef8dc6e@macports.org> #53109: port select fails if invalid exists -------------------------+----------------- Reporter: nhojpatrick | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: -------------------------+----------------- I've just done a weekly upgrade and a prompt appeared about python. So I did as suggested, I then played around with other python versions and discovered select doesn't clean up if active versions are uninstalled and then you try and install a new version as active. $ sudo port select --list python3 Available versions for python3: none (active) python35 $ ls -l /opt/local/etc/select/python3/ total 32 -rw-r--r--+ 1 root admin 145 12 Sep 13:27 base lrwxr-xr-x 1 root admin 8 21 Aug 2015 current -> python34 -rw-r--r--+ 1 root admin 20 12 Sep 13:27 none -rw-r--r--+ 1 root admin 154 18 Oct 20:11 python35 $ sudo port select --set python3 python35 Selecting 'python35' for 'python3' failed: symlink: /opt/local/etc/select/python3/current -> python35: file already exists I would attempt a port but no idea where to start and already trying to fix the githut portgroup. I would guess this could happen with every port select. If an invalid symlink exists and you try and set a new one it should delete the existing symlink and create it as specified. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 22:11:58 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 22:11:58 -0000 Subject: [MacPorts] #53110: libomp and clang-3.8 fail on Lion Message-ID: <043.c5ec93166b62879945bea5439c7783d1@macports.org> #53110: libomp and clang-3.8 fail on Lion --------------------+------------------------------- Reporter: RobK88 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: libomp, clang-3.8 --------------------+------------------------------- Ran "sudo port -v selfupdate". Updated macports to the latest version on my Mac running 10.7.5. I then tried to update the outdated packages. Macports updated many of them but then started to fail. E.G. When I try to install libomp or clang-3.8 on Lion, it fails. Looks like there is a circular dependency. {{{ sudo port clean libomp clang-3.8 ---> Cleaning libomp ---> Cleaning clang-3.8 Grinchs-Mac-Pro:~ grinch$ sudo port install libomp ---> Computing dependencies for libomp ---> Dependencies to be installed: clang-3.8 libomp Error: The following dependencies were not installed: clang-3.8 libomp To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port libomp failed Grinchs-Mac-Pro:~ grinch$ Grinchs-Mac-Pro:~ grinch$ sudo port install clang-3.8 ---> Computing dependencies for clang-3.8 ---> Dependencies to be installed: libomp clang-3.8 Error: The following dependencies were not installed: libomp clang-3.8 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port clang-3.8 failed }}} Any ideas for a fix? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 23:47:36 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 23:47:36 -0000 Subject: [MacPorts] #52078: iTerm2 @3.0.5_0: pasting with the mouse between tabs does not work (anymore) In-Reply-To: <062.7038fee47b689585c64a9af194d6eab3@macports.org> References: <062.7038fee47b689585c64a9af194d6eab3@macports.org> Message-ID: <077.27be8f700451cf264aafa06230f03ff8@macports.org> #52078: iTerm2 @3.0.5_0: pasting with the mouse between tabs does not work (anymore) --------------------------------+---------------------- Reporter: graziosi.angelo@… | Owner: markemer Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: iTerm2 | --------------------------------+---------------------- Changes (by markemer): * Attachment "Screenshot 2016-12-19 18.45.45.png" added. iTerm2 Setup -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 23:56:24 2016 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2016 23:56:24 -0000 Subject: [MacPorts] #52078: iTerm2 @3.0.5_0: pasting with the mouse between tabs does not work (anymore) In-Reply-To: <062.7038fee47b689585c64a9af194d6eab3@macports.org> References: <062.7038fee47b689585c64a9af194d6eab3@macports.org> Message-ID: <077.1530bd9a78f2e43397705c12a508b15f@macports.org> #52078: iTerm2 @3.0.5_0: pasting with the mouse between tabs does not work (anymore) --------------------------------+---------------------- Reporter: graziosi.angelo@… | Owner: markemer Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: iTerm2 | --------------------------------+---------------------- Comment (by markemer): It seems like this is an upstream problem. Middle button single click is assigned to paste. We should close this as 'wontfix' or whatever fix upstream needs. [[Image(Screenshot 2016-12-19 18.45.45.png​, 700px)]] -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 00:17:17 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 00:17:17 -0000 Subject: [MacPorts] #53110: libomp and clang-3.8 fail on Lion In-Reply-To: <043.c5ec93166b62879945bea5439c7783d1@macports.org> References: <043.c5ec93166b62879945bea5439c7783d1@macports.org> Message-ID: <058.2cac3d0b0c3c2b6b429c1fd497b0b591@macports.org> #53110: libomp and clang-3.8 fail on Lion --------------------------------+------------------- Reporter: RobK88 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: libomp, clang-3.8 | --------------------------------+------------------- Comment (by kencu): Not quite enough information for me to help you. What do you have installed already? {{{ port -v installed | grep omp port -v installed | grep clang port -v installed | grep llvm port -v installed | grep libcxx port -v installed | grep libmacho port -v installed | grep libunwind }}} are you using libcxx as per [wiki:LibcxxOnOlderSystems] or the standard libstdc++ default installation? and would need the full log {{{ sudo port -v install omp sudo port -v install clang-3.8 }}} best, K -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 00:18:42 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 00:18:42 -0000 Subject: [MacPorts] #53088: py-pyqt5 @5.6_3+webengine does not build In-Reply-To: <048.20a8bc8768b5c8038286e59a8237e2a9@macports.org> References: <048.20a8bc8768b5c8038286e59a8237e2a9@macports.org> Message-ID: <063.1bdcfe0255310ec54baec264aaf24fa7@macports.org> #53088: py-pyqt5 @5.6_3+webengine does not build --------------------------+---------------------- Reporter: josephsacco | Owner: rjvb Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: py-pyqt5 | --------------------------+---------------------- Changes (by mkae): * owner: => rjvb * cc: mkae (added) * status: new => assigned Comment: René, you - like me - didn't run into this, right!? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 01:02:40 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 01:02:40 -0000 Subject: [MacPorts] #53090: py-pyqt* multiple Qt depspecs In-Reply-To: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> References: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> Message-ID: <056.4a63588c27cd84af026396a76e6fc8cb@macports.org> #53090: py-pyqt* multiple Qt depspecs ---------------------------------+---------------------- Reporter: RJVB | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: py-pyqt4, py-pyqt5 | ---------------------------------+---------------------- Comment (by mkae): The attached patch for Qt5 isn't applying anymore. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 01:03:30 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 01:03:30 -0000 Subject: [MacPorts] #53090: py-pyqt* multiple Qt depspecs In-Reply-To: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> References: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> Message-ID: <056.ce927c32afa266ebb5ff31bd6c577578@macports.org> #53090: py-pyqt* multiple Qt depspecs --------------------------------+---------------------- Reporter: RJVB | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: py-pyqt4 py-pyqt5 | --------------------------------+---------------------- Changes (by mkae): * port: py-pyqt4, py-pyqt5 => py-pyqt4 py-pyqt5 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 01:15:55 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 01:15:55 -0000 Subject: [MacPorts] #53110: libomp and clang-3.8 fail on Lion In-Reply-To: <043.c5ec93166b62879945bea5439c7783d1@macports.org> References: <043.c5ec93166b62879945bea5439c7783d1@macports.org> Message-ID: <058.19af5e03cb1a1e08ab767d180a882095@macports.org> #53110: libomp and clang-3.8 fail on Lion --------------------------------+------------------- Reporter: RobK88 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: libomp, clang-3.8 | --------------------------------+------------------- Comment (by ryandesign): Circular dependency. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 01:19:30 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 01:19:30 -0000 Subject: [MacPorts] #53090: py-pyqt* multiple Qt depspecs In-Reply-To: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> References: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> Message-ID: <056.949192955c3683361035b576784c6af6@macports.org> #53090: py-pyqt* multiple Qt depspecs --------------------------------+---------------------- Reporter: RJVB | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: py-pyqt4 py-pyqt5 | --------------------------------+---------------------- Comment (by mkae): In [changeset:"ad1309c5124a7ec5f3dddedb10d29a125d40e193/macports-ports" ad1309c/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="ad1309c5124a7ec5f3dddedb10d29a125d40e193" py-pyqt4: fix dependencies See: https://trac.macports.org/ticket/53090 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 01:19:31 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 01:19:31 -0000 Subject: [MacPorts] #53090: py-pyqt* multiple Qt depspecs In-Reply-To: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> References: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> Message-ID: <056.e78159f7de96a01c736d695c955792c7@macports.org> #53090: py-pyqt* multiple Qt depspecs --------------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: py-pyqt4 py-pyqt5 | --------------------------------+---------------------- Changes (by mkae): * status: new => closed * owner: => mkae * resolution: => fixed Comment: In [changeset:"f164c1e8ffdcf126d56c8d9f1f0d2e7109072c88/macports-ports" f164c1e8/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="f164c1e8ffdcf126d56c8d9f1f0d2e7109072c88" py-pyqt5: fix dependencies Closes: https://trac.macports.org/ticket/53090 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 01:22:01 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 01:22:01 -0000 Subject: [MacPorts] #53109: port select fails if invalid exists In-Reply-To: <048.2f7b828e94be005e9bddd1467ef8dc6e@macports.org> References: <048.2f7b828e94be005e9bddd1467ef8dc6e@macports.org> Message-ID: <063.da65317125e6c9ca79eeefd9eee51a95@macports.org> #53109: port select fails if invalid exists --------------------------+-------------------- Reporter: nhojpatrick | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: Resolution: duplicate | Keywords: Port: | --------------------------+-------------------- Changes (by ryandesign): * status: new => closed * resolution: => duplicate * component: ports => base Old description: > I've just done a weekly upgrade and a prompt appeared about python. So I > did as suggested, I then played around with other python versions and > discovered select doesn't clean up if active versions are uninstalled and > then you try and install a new version as active. > > $ sudo port select --list python3 > Available versions for python3: > none (active) > python35 > $ ls -l /opt/local/etc/select/python3/ > total 32 > -rw-r--r--+ 1 root admin 145 12 Sep 13:27 base > lrwxr-xr-x 1 root admin 8 21 Aug 2015 current -> python34 > -rw-r--r--+ 1 root admin 20 12 Sep 13:27 none > -rw-r--r--+ 1 root admin 154 18 Oct 20:11 python35 > $ sudo port select --set python3 python35 > Selecting 'python35' for 'python3' failed: symlink: > /opt/local/etc/select/python3/current -> python35: file already exists > > I would attempt a port but no idea where to start and already trying to > fix the githut portgroup. > > I would guess this could happen with every port select. If an invalid > symlink exists and you try and set a new one it should delete the > existing symlink and create it as specified. New description: I've just done a weekly upgrade and a prompt appeared about python. So I did as suggested, I then played around with other python versions and discovered select doesn't clean up if active versions are uninstalled and then you try and install a new version as active. {{{ $ sudo port select --list python3 Available versions for python3: none (active) python35 $ ls -l /opt/local/etc/select/python3/ total 32 -rw-r--r--+ 1 root admin 145 12 Sep 13:27 base lrwxr-xr-x 1 root admin 8 21 Aug 2015 current -> python34 -rw-r--r--+ 1 root admin 20 12 Sep 13:27 none -rw-r--r--+ 1 root admin 154 18 Oct 20:11 python35 $ sudo port select --set python3 python35 Selecting 'python35' for 'python3' failed: symlink: /opt/local/etc/select/python3/current -> python35: file already exists }}} I would attempt a port but no idea where to start and already trying to fix the githut portgroup. I would guess this could happen with every port select. If an invalid symlink exists and you try and set a new one it should delete the existing symlink and create it as specified. -- Comment: Duplicate of #31702. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 01:22:05 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 01:22:05 -0000 Subject: [MacPorts] #47755: Broken symlink left by select code when selected port is deactivated causes poppler and other ports using aclocal to fail during configuration. In-Reply-To: <052.315fef8b0a8cb75b4bbd275d964888b4@macports.org> References: <052.315fef8b0a8cb75b4bbd275d964888b4@macports.org> Message-ID: <067.951b021b5f219866c3adbe634e138969@macports.org> #47755: Broken symlink left by select code when selected port is deactivated causes poppler and other ports using aclocal to fail during configuration. ------------------------+-------------------------------- Reporter: lukasz@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.3.3 Resolution: duplicate | Keywords: Port: | ------------------------+-------------------------------- Changes (by ryandesign): * status: new => closed * resolution: => duplicate Comment: Duplicate of #31702. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 01:22:09 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 01:22:09 -0000 Subject: [MacPorts] #31702: port select fails if symlink already exists from earlier installation or from uninstalled port (was: port select fails if symlink already exists from earlier installation) In-Reply-To: <057.89a547c3cc002e2c43142fc7b9f471d7@macports.org> References: <057.89a547c3cc002e2c43142fc7b9f471d7@macports.org> Message-ID: <072.91e9c0e06cc0f1b11b0f82e3af0554dd@macports.org> #31702: port select fails if symlink already exists from earlier installation or from uninstalled port ---------------------------+-------------------------------- Reporter: gunnlaugur@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.0.3 Resolution: | Keywords: Port: | ---------------------------+-------------------------------- Changes (by ryandesign): * cc: neverpanic, jyrkiwahlstedt, dbevans, larryv, ryandesign, charlie.clark@…, mojca, brookemgilbert@…, poorsod@…, tim@…, keybounce, lukasz@…, David.Epstein@…, nhojpatrick (added) Comment: Has duplicates #47755 (with much discussion) and #53109. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 01:23:45 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 01:23:45 -0000 Subject: [MacPorts] #53106: cctools: otool -L fails with /opt/local/bin/llvm-objdump not found (was: otools -L fails with /opt/local/bin/llvm-objdump not found) In-Reply-To: <045.5d249478d4dc3afbe6c31fd4708dc968@macports.org> References: <045.5d249478d4dc3afbe6c31fd4708dc968@macports.org> Message-ID: <060.8e640c7bc82c4788e7fa06bafd3ac6c3@macports.org> #53106: cctools: otool -L fails with /opt/local/bin/llvm-objdump not found -----------------------+---------------------- Reporter: dmarteau | Owner: jeremyhu Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: cctools | -----------------------+---------------------- Changes (by ryandesign): * owner: => jeremyhu * cc: jeremyhu@… (removed) * status: new => assigned Old description: > The command 'otools -L' fails with the following error: > > {{{ > fatal error: otool: can't find or exec: /opt/local/bin/llvm-objdump (No > such file or directory) > fatal error: otool: internal objdump command failed > }}} > > otool-classic seems to work correctly as the native command > /usr/bin/otool. > > System: OSX 10.11.6, XCode 7.3 New description: The command 'otool -L' fails with the following error: {{{ fatal error: otool: can't find or exec: /opt/local/bin/llvm-objdump (No such file or directory) fatal error: otool: internal objdump command failed }}} otool-classic seems to work correctly as the native command /usr/bin/otool. System: OSX 10.11.6, XCode 7.3 -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 01:31:50 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 01:31:50 -0000 Subject: [MacPorts] #53110: libomp and clang-3.8 fail on Lion In-Reply-To: <043.c5ec93166b62879945bea5439c7783d1@macports.org> References: <043.c5ec93166b62879945bea5439c7783d1@macports.org> Message-ID: <058.ffb2b12bc13a84ae161fdf152400d36d@macports.org> #53110: libomp and clang-3.8 fail on Lion --------------------------------+------------------- Reporter: RobK88 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: libomp, clang-3.8 | --------------------------------+------------------- Changes (by RobK88): * Attachment "libomp.main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 01:32:00 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 01:32:00 -0000 Subject: [MacPorts] #53110: libomp and clang-3.8 fail on Lion In-Reply-To: <043.c5ec93166b62879945bea5439c7783d1@macports.org> References: <043.c5ec93166b62879945bea5439c7783d1@macports.org> Message-ID: <058.f814a3dde3738b72e5842272afe36368@macports.org> #53110: libomp and clang-3.8 fail on Lion --------------------------------+------------------- Reporter: RobK88 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: libomp, clang-3.8 | --------------------------------+------------------- Changes (by RobK88): * Attachment "clang-3.8.main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 01:33:37 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 01:33:37 -0000 Subject: [MacPorts] #53111: update after installing OSX security patches fails Message-ID: <050.e95dfc8b93468f285f7e9c5c71f911fb@macports.org> #53111: update after installing OSX security patches fails ---------------------------+------------------- Reporter: gaming-hacker | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.5 Keywords: | Port: ---------------------------+------------------- i installed OSX latest security patches {{{ https://support.apple.com/en-us/HT201222 }}} then later went to update macports {{{ sudo port -v selfupdate }}} {{{ Updating MacPorts base sources using rsync rsync: failed to connect to sea.us.rsync.macports.org: Operation timed out (60) rsync error: error in socket IO (code 10) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-47/rsync/clientserver.c(105) [receiver=2.6.9] Command failed: /usr/bin/rsync -rtzv --delete-after rsync://sea.us.rsync.macports.org/release/tarballs/base.tar /opt/local/var/macports/sources/sea.us.rsync.macports.org/release/tarballs Exit code: 10 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 }}} so i pinged the server {{{ ping sea.us.rsync.macports.org PING mirror.pnl.gov (192.101.102.2): 56 data bytes 64 bytes from 192.101.102.2: icmp_seq=0 ttl=50 time=439.121 ms 64 bytes from 192.101.102.2: icmp_seq=1 ttl=50 time=334.356 ms 64 bytes from 192.101.102.2: icmp_seq=2 ttl=50 time=383.321 ms }}} i also tried servers lil.fr.rsync.macports.org rsync.macports.org jnb.za.rsync.macports.org all fail -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 01:35:46 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 01:35:46 -0000 Subject: [MacPorts] #53110: libomp and clang-3.8 fail on Lion In-Reply-To: <043.c5ec93166b62879945bea5439c7783d1@macports.org> References: <043.c5ec93166b62879945bea5439c7783d1@macports.org> Message-ID: <058.59fbf737e2f4db82097fa32e59c0aba2@macports.org> #53110: libomp and clang-3.8 fail on Lion --------------------------------+------------------- Reporter: RobK88 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: libomp, clang-3.8 | --------------------------------+------------------- Comment (by RobK88): I am using libcc++. I have attached the main.log files for the failed installations of libomp and clang-3.8 Here is output of the commands: {{{ bash-3.2$ port -v installed | grep omp bash-3.2$ port -v installed | grep clang clang-3.4 @3.4.2_12+analyzer+arm_runtime (active) platform='darwin 11' archs='x86_64' clang-3.6 @3.6.2_5+analyzer (active) platform='darwin 11' archs='x86_64' clang-3.7 @3.7.1_5+analyzer (active) platform='darwin 11' archs='x86_64' clang_select @2_0 (active) platform='darwin 11' archs='noarch' bash-3.2$ port -v installed | grep llvm cctools @895_2+llvm34 (active) platform='darwin 11' archs='x86_64' ld64-latest @274.1_0+llvm34 (active) platform='darwin 11' archs='x86_64' llvm-3.4 @3.4.2_11 (active) platform='darwin 11' archs='x86_64' llvm-3.6 @3.6.2_4 (active) platform='darwin 11' archs='x86_64' llvm-3.7 @3.7.1_4 (active) platform='darwin 11' archs='x86_64' llvm-3.8 @3.8.1_0 (active) platform='darwin 11' archs='x86_64' llvm_select @2_0 (active) platform='darwin 11' archs='noarch' bash-3.2$ port -v installed | grep libcxx libcxx @3.9.0_0+universal (active) platform='darwin 11' archs='i386 x86_64' bash-3.2$ port -v installed | grep libmacho libmacho-headers @895_0 (active) platform='darwin 11' archs='noarch' bash-3.2$ port -v installed | grep libunwind libunwind-headers @3.9.0_0 (active) platform='darwin 11' archs='noarch' bash-3.2$ bash-3.2$ sudo port -v install libomp ---> Computing dependencies for libomp.... ---> Dependencies to be installed: clang-3.8 libomp Error: The following dependencies were not installed: clang-3.8 libomp To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port libomp failed bash-3.2$ sudo port -v install clang-3.8 ---> Computing dependencies for clang-3.8... ---> Dependencies to be installed: libomp clang-3.8 Error: The following dependencies were not installed: libomp clang-3.8 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port clang-3.8 failed bash-3.2$ }}} Hope you can see a fix. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 02:17:46 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 02:17:46 -0000 Subject: [MacPorts] #53110: libomp and clang-3.8 fail on Lion In-Reply-To: <043.c5ec93166b62879945bea5439c7783d1@macports.org> References: <043.c5ec93166b62879945bea5439c7783d1@macports.org> Message-ID: <058.a6cf0d015a132bfecfcefa3d0fb37395@macports.org> #53110: libomp and clang-3.8 fail on Lion --------------------------------+------------------- Reporter: RobK88 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: libomp, clang-3.8 | --------------------------------+------------------- Comment (by kencu): Try this: {{{ sudo port -v install libomp configure.compiler=macports-clang-3.7 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 02:21:11 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 02:21:11 -0000 Subject: [MacPorts] #53110: libomp and clang-3.8 fail on Lion In-Reply-To: <043.c5ec93166b62879945bea5439c7783d1@macports.org> References: <043.c5ec93166b62879945bea5439c7783d1@macports.org> Message-ID: <058.e73aeef21f657caf543140b9f4f45c34@macports.org> #53110: libomp and clang-3.8 fail on Lion --------------------------------+------------------- Reporter: RobK88 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: libomp, clang-3.8 | --------------------------------+------------------- Comment (by kencu): If that doesn't work, peg clang-3.8 to the last version so macports thinks it's current and stops asking to update it for the moment, then update libomp. If that works (it should), unpeg clang-3.8 and update it after libomp is current. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 02:29:06 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 02:29:06 -0000 Subject: [MacPorts] #53065: QGIS @2.18.0 build failure In-Reply-To: <047.acd0aebce4f8fa360df821a9edae7ed0@macports.org> References: <047.acd0aebce4f8fa360df821a9edae7ed0@macports.org> Message-ID: <062.ade271d108800d64ba86fa4315c89ecb@macports.org> #53065: QGIS @2.18.0 build failure -------------------------+---------------------- Reporter: BuddyVolly | Owner: Veence Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: QGIS | -------------------------+---------------------- Comment (by EJFielding): I am getting the same build failure trying to update from QGIS @2.18.0 which I have been using for a while to @2.18.0.1. I tried deactivating my qca @2.1.0_4 and activating qca @2.1.0_3+qt4 (which required deactivating qgis and qca-ossl first). Then I tried to update qgis, but it still failed. MacPorts first reactivated qca-ossl @2.1.0_4, but then it seems to not find the correct qcaossl files. main.log excerpt: {{{ :info:configure -- Found QScintilla2: /opt/local/libexec/qt4/lib/libqscintilla2.dylib (2.9.3) :info:configure -- Found QCA: /opt/local/lib/libqca.dylib (2.1.0) :info:configure CMake Error at cmake/QCAMacros.cmake:64 (message): :info:configure QCA OpenSSL plugin not found (run-time/unit-test dependency) :info:configure Call Stack (most recent call first): :info:configure CMakeLists.txt:327 (FIND_QCAOSSL_PLUGIN_CPP) }}} Is there another hint we can try? Thanks, ++Eric -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 02:39:58 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 02:39:58 -0000 Subject: [MacPorts] #53107: py27-pygrib @2.0.2 update In-Reply-To: <044.366915d58c1d778030237b2c332b9007@macports.org> References: <044.366915d58c1d778030237b2c332b9007@macports.org> Message-ID: <059.1c081f324dc179cd277ab307913cf666@macports.org> #53107: py27-pygrib @2.0.2 update --------------------------+----------------- Reporter: ForTozs | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py27-pygrib | --------------------------+----------------- Comment (by EJFielding): It does seem that py27-pygrib @2.0.1 is broken. {{{ sudo port upgrade py27-matplotlib-basemap ---> Scanning binaries for linking errors ---> Found 4 broken file(s), matching files to ports ---> Found 3 broken port(s), determining rebuild order ---> Rebuilding in order py27-matplotlib-basemap @1.0.7 py27-pygrib @2.0.1 qca-ossl @2.1.0 ---> Computing dependencies for py27-matplotlib-basemap ---> Cleaning py27-matplotlib-basemap ---> Computing dependencies for py27-pygrib ---> Fetching archive for py27-pygrib ---> Attempting to fetch py27-pygrib-2.0.1_1.darwin_15.x86_64.tbz2 from https://packages.macports.org/py27-pygrib ---> Attempting to fetch py27-pygrib-2.0.1_1.darwin_15.x86_64.tbz2 from http://sea.us.packages.macports.org/macports/packages/py27-pygrib ---> Attempting to fetch py27-pygrib-2.0.1_1.darwin_15.x86_64.tbz2 from http://lil.fr.packages.macports.org/py27-pygrib ---> Fetching distfiles for py27-pygrib ---> Verifying checksums for py27-pygrib ---> Extracting py27-pygrib ---> Configuring py27-pygrib ---> Building py27-pygrib Error: org.macports.build for port py27-pygrib returned: command execution failed Please see the log file for port py27-pygrib for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_python_py-pygrib/py27-pygrib/main.log Error: Unable to upgrade port: 1 Error rebuilding py27-pygrib while executing "error "Error rebuilding $portname"" (procedure "revupgrade_scanandrebuild" line 395) invoked from within "revupgrade_scanandrebuild broken_port_counts $opts" (procedure "macports::revupgrade" line 5) invoked from within "macports::revupgrade $opts" (procedure "action_revupgrade" line 2) invoked from within "action_revupgrade $action $portlist $opts" (procedure "action_upgrade" line 25) invoked from within "$action_proc $action $portlist [array get global_options]" (procedure "process_cmd" line 103) invoked from within "process_cmd $remaining_args" invoked from within "if { [llength $remaining_args] > 0 } { # If there are remaining arguments, process those as a command set exit_status [process_cmd $remaining..." (file "/opt/local/bin/port" line 5286) }}} main.log excerpt: {{{ :info:build g2clib_src/enc_jpeg2000.c:124:11: error: no member named 'inmem_' in 'jas_image_t' :info:build image.inmem_=1; :info:build ~~~~~ ^ :info:build 1 error generated. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 02:52:31 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 02:52:31 -0000 Subject: [MacPorts] #52263: py-robotframework-selenium2library @1.8.0: needs setuptools dependency? In-Reply-To: <047.4f62de7bf631c5d75eec2d5908d2cd49@macports.org> References: <047.4f62de7bf631c5d75eec2d5908d2cd49@macports.org> Message-ID: <062.d43fdf9724c1557fb5f5d3d8a22e57c1@macports.org> #52263: py-robotframework-selenium2library @1.8.0: needs setuptools dependency? -------------------------------------------------+------------------------- Reporter: ryandesign | Owner: | jyrkiwahlstedt Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: py-robotframework-selenium2library | -------------------------------------------------+------------------------- Changes (by kurthindenburg): * cc: khindenburg (added) Comment: It build here fine - It doesn't appear to use the standard setuptools instead using ez_setup - also isn't that SSL issue one we've seen before? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 02:58:59 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 02:58:59 -0000 Subject: [MacPorts] #52180: flex @2.6.0_0: build failure In-Reply-To: <059.87ff39f54de1688c967843e3bd201df2@macports.org> References: <059.87ff39f54de1688c967843e3bd201df2@macports.org> Message-ID: <074.8c9dcba075bb09070075cc7235543833@macports.org> #52180: flex @2.6.0_0: build failure --------------------------+------------------- Reporter: geoffdown@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: tiger Port: flex | --------------------------+------------------- Changes (by kurthindenburg): * cc: khindenburg (added) Comment: I'm not sure anyone will be able to debug 10.4 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 05:04:56 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 05:04:56 -0000 Subject: [MacPorts] #53112: Update to mariadb 10.1.20 Message-ID: <046.b7a7791505ab3c823419b08e9f3f74cc@macports.org> #53112: Update to mariadb 10.1.20 ---------------------------------+--------------------------------- Reporter: patrixgdd | Owner: Type: update | Status: new Priority: Normal | Milestone: MacPorts 2.3.6 Component: ports | Version: 2.3.5 Keywords: mariadb-10.1-server | Port: mariadb-10.1-server ---------------------------------+--------------------------------- Hi everyone, Could you please update the current mariadb-server to 10.1.20? many thanks -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 05:50:46 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 05:50:46 -0000 Subject: [MacPorts] #53102: jasper dylib current version regressed In-Reply-To: <045.1d96a7542a3d6b123e5fe23a43d0875d@macports.org> References: <045.1d96a7542a3d6b123e5fe23a43d0875d@macports.org> Message-ID: <060.0a37b757953e90e6eef83842d8d7945a@macports.org> #53102: jasper dylib current version regressed -----------------------+-------------------- Reporter: jeremyhu | Owner: jmroot Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: jasper | -----------------------+-------------------- Comment (by ryandesign): Replying to [comment:1 jmroot]: > More fallout from switching to cmake, which doesn't appear to let you set compatibility_version independently of the soname/major version. So libjasper.4.dylib built by cmake will always have current and compat versions of 4.x.y. Remind me why does anybody use this idiotic broken build system? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 05:53:25 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 05:53:25 -0000 Subject: [MacPorts] #53101: jasper fails to build +universal due to glut/OpenGL problems In-Reply-To: <045.bf4f074c5732d25ad8009bd2582ab00f@macports.org> References: <045.bf4f074c5732d25ad8009bd2582ab00f@macports.org> Message-ID: <060.a4739d42d5d8c4895d85f79568f11af3@macports.org> #53101: jasper fails to build +universal due to glut/OpenGL problems ---------------------------+-------------------- Reporter: jeremyhu | Owner: jmroot Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: jasper cmake | ---------------------------+-------------------- Changes (by ryandesign): * cc: MarcusCalhoun-Lopez (added) Comment: Marcus committed a fix to the jasper port in changeset:caae5b2254cc2926741d09b222c9483b13515ed0/macports-ports -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 06:14:16 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 06:14:16 -0000 Subject: [MacPorts] #53113: expected boolean value but got ""no"" Message-ID: <047.4dfc9c6163c3085f1a025bdeeb3958e5@macports.org> #53113: expected boolean value but got ""no"" ------------------------+-------------------- Reporter: ryandesign | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.99 Keywords: | Port: ------------------------+-------------------- I used to be able to disable ccache for a single port build by adding `configure.ccache=no` to the command line invocation, but with the latest base code I now get an error: {{{ sudo port -s install php53-vld configure.ccache=no ---> Cleaning php53-vld ---> Computing dependencies for php53-vld Error: expected boolean value but got ""no"" Error: See /opt/local/var/macports/logs/_Users_rschmidt_macports_macports- ports_php_php-vld/php53-vld/main.log for details. Error: Follow https://guide.macports.org/#project.tickets to report a bug. Error: Processing of port php53-vld failed }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 06:29:42 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 06:29:42 -0000 Subject: [MacPorts] #52596: Add port for i3 window manager In-Reply-To: <048.ecfdc0bb3152801545a1aa0374a8c5f8@macports.org> References: <048.ecfdc0bb3152801545a1aa0374a8c5f8@macports.org> Message-ID: <063.2d16da725353846321864fa267f1dc77@macports.org> #52596: Add port for i3 window manager --------------------------+-------------------------------- Reporter: jenstroeger | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: i3 | --------------------------+-------------------------------- Comment (by jenstroeger): I started to look into this and would like to track progress and blocking issues here. First, I had to add a second port on which the [https://github.com/jpouellet/MacPorts/tree/master/x11/i3 i3 port] depends: [https://github.com/jpouellet/MacPorts/tree/master/x11/xkbcommon xkbcommon] by jpo at vt.edu. Compiling the xkbcommon port requires the ''cairo/cairo-xcb.h'' include which doesn't seem to come with the default cairo port. This seems to be a circular dependency? [https://trac.macports.org/ticket/23483 Ticket #23483] seems to be related, by quite dated. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 07:21:56 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 07:21:56 -0000 Subject: [MacPorts] #53114: redis 3.2.4 update request Message-ID: <046.7dda2634b02827b4653ce0306bb3677d@macports.org> #53114: redis 3.2.4 update request -----------------------+---------------------------- Reporter: patrixgdd | Owner: Type: update | Status: new Priority: Normal | Milestone: MacPorts 2.3.6 Component: ports | Version: 2.3.5 Keywords: redis | Port: redis -----------------------+---------------------------- Hello, Could anyone update the redis to 3.2.6? many thanks -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 07:30:21 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 07:30:21 -0000 Subject: [MacPorts] #53114: redis 3.2.4 update request In-Reply-To: <046.7dda2634b02827b4653ce0306bb3677d@macports.org> References: <046.7dda2634b02827b4653ce0306bb3677d@macports.org> Message-ID: <061.c68f4a8609cd7479c26dd9732e5b95ab@macports.org> #53114: redis 3.2.4 update request ------------------------+------------------- Reporter: patrixgdd | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: redis | ------------------------+------------------- Changes (by ryandesign): * keywords: redis => * milestone: MacPorts 2.3.6 => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 07:30:59 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 07:30:59 -0000 Subject: [MacPorts] #53112: mariadb-10.1: update to 10.1.20 (was: Update to mariadb 10.1.20) In-Reply-To: <046.b7a7791505ab3c823419b08e9f3f74cc@macports.org> References: <046.b7a7791505ab3c823419b08e9f3f74cc@macports.org> Message-ID: <061.c1b56d4d63858a6dfa56a42e48cb834a@macports.org> #53112: mariadb-10.1: update to 10.1.20 ---------------------------+---------------------- Reporter: patrixgdd | Owner: pixilla Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: mariadb-10.1 | ---------------------------+---------------------- Changes (by ryandesign): * status: new => assigned * owner: => pixilla * milestone: MacPorts 2.3.6 => * keywords: mariadb-10.1-server => * port: mariadb-10.1-server => mariadb-10.1 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 07:32:55 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 07:32:55 -0000 Subject: [MacPorts] #53111: rsync: failed to connect to sea.us.rsync.macports.org: Operation timed out (60) (was: update after installing OSX security patches fails) In-Reply-To: <050.e95dfc8b93468f285f7e9c5c71f911fb@macports.org> References: <050.e95dfc8b93468f285f7e9c5c71f911fb@macports.org> Message-ID: <065.c574b4a80abf90dfb3fe46d2df67e233@macports.org> #53111: rsync: failed to connect to sea.us.rsync.macports.org: Operation timed out (60) ----------------------------+------------------- Reporter: gaming-hacker | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.5 Resolution: | Keywords: Port: | ----------------------------+------------------- Comment (by ryandesign): This error message usually indicates that there is a problem with your network. Try accessing these and other rsync servers at the command line, for example: {{{ rsync rsync://rsync.macports.org/macports/ }}} If it doesn't work, contact your network administrator. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 08:58:11 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 08:58:11 -0000 Subject: [MacPorts] #53105: qt5-qtbase @5.6.2: configure fails due to invalid compiler *clang* In-Reply-To: <047.71de0adf031ec43db9842370f4b572e1@macports.org> References: <047.71de0adf031ec43db9842370f4b572e1@macports.org> Message-ID: <062.cfecea4ed7f9986400688516e4ae91ae@macports.org> #53105: qt5-qtbase @5.6.2: configure fails due to invalid compiler *clang* ---------------------------------+--------------------------------- Reporter: mndavidoff | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: qt5-qtbase poppler | ---------------------------------+--------------------------------- Comment (by RJVB): Isn't blacklisting all gcc compilers something that should only be done on 10.9 and up which have sufficient C++11 support in clang? I know that building with gcc isn't supported officially as a substitute for doing a libc++ conversion, but is that a reason to make it impossible? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 09:00:39 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 09:00:39 -0000 Subject: [MacPorts] #53090: py-pyqt* multiple Qt depspecs In-Reply-To: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> References: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> Message-ID: <056.6ec97c3d45556ed0e23cbaad7f9889d3@macports.org> #53090: py-pyqt* multiple Qt depspecs --------------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: py-pyqt4 py-pyqt5 | --------------------------------+---------------------- Comment (by RJVB): Replying to [comment:3 mkae]: > The attached patch for Qt5 isn't applying anymore. So you sorted this out? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 09:17:43 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 09:17:43 -0000 Subject: [MacPorts] #53090: py-pyqt* multiple Qt depspecs In-Reply-To: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> References: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> Message-ID: <056.e0c09398b665fbf4e283161324b3746e@macports.org> #53090: py-pyqt* multiple Qt depspecs --------------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: py-pyqt4 py-pyqt5 | --------------------------------+---------------------- Comment (by RJVB): Apparently not exactly so; a fixed version is on its way. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 09:26:52 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 09:26:52 -0000 Subject: [MacPorts] #53105: qt5-qtbase @5.6.2: configure fails due to invalid compiler *clang* In-Reply-To: <047.71de0adf031ec43db9842370f4b572e1@macports.org> References: <047.71de0adf031ec43db9842370f4b572e1@macports.org> Message-ID: <062.609f92c16438086045e2fd231541264a@macports.org> #53105: qt5-qtbase @5.6.2: configure fails due to invalid compiler *clang* ---------------------------------+--------------------------------- Reporter: mndavidoff | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: qt5-qtbase poppler | ---------------------------------+--------------------------------- Comment (by jeremyhu): It's odd that `port lint` caught that `compiler.whitelist clang` was not valid but did not catch that `compiler.whitelist *clang*` was not valid. Any idea why that is? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 09:29:24 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 09:29:24 -0000 Subject: [MacPorts] #53106: cctools: otool -L fails with /opt/local/bin/llvm-objdump not found In-Reply-To: <045.5d249478d4dc3afbe6c31fd4708dc968@macports.org> References: <045.5d249478d4dc3afbe6c31fd4708dc968@macports.org> Message-ID: <060.de415864e43e481316a6fa53977df4ff@macports.org> #53106: cctools: otool -L fails with /opt/local/bin/llvm-objdump not found ------------------------+---------------------- Reporter: dmarteau | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: duplicate | Keywords: Port: cctools | ------------------------+---------------------- Changes (by jeremyhu): * status: assigned => closed * resolution: => duplicate Comment: This was fixed prior to your ticket. I suggest you update and try again. See #53099 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 09:29:52 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 09:29:52 -0000 Subject: [MacPorts] #53106: cctools: otool -L fails with /opt/local/bin/llvm-objdump not found In-Reply-To: <045.5d249478d4dc3afbe6c31fd4708dc968@macports.org> References: <045.5d249478d4dc3afbe6c31fd4708dc968@macports.org> Message-ID: <060.3ad6d00e269b8ec441564c76889022b0@macports.org> #53106: cctools: otool -L fails with /opt/local/bin/llvm-objdump not found ------------------------+---------------------- Reporter: dmarteau | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: duplicate | Keywords: Port: cctools | ------------------------+---------------------- Comment (by jeremyhu): Actually, this issue was fixed even before #53099. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 09:34:08 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 09:34:08 -0000 Subject: [MacPorts] #53102: jasper dylib current version regressed In-Reply-To: <045.1d96a7542a3d6b123e5fe23a43d0875d@macports.org> References: <045.1d96a7542a3d6b123e5fe23a43d0875d@macports.org> Message-ID: <060.e2909daa255189891b9c7cf28ed959c2@macports.org> #53102: jasper dylib current version regressed -----------------------+-------------------- Reporter: jeremyhu | Owner: jmroot Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: jasper | -----------------------+-------------------- Comment (by jeremyhu): Replying to [comment:5 ryandesign]: > Remind me why does anybody use this idiotic broken build system? Because it has a more permissive license than the other idiotic broken build system that everyone else uses. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 10:05:15 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 10:05:15 -0000 Subject: [MacPorts] #52632: Inkscape-app quits immediately after install In-Reply-To: <056.34df243aa80de466541391e09f3b22b1@macports.org> References: <056.34df243aa80de466541391e09f3b22b1@macports.org> Message-ID: <071.e326d7b9124650fdf6bbcbf54b00bf5d@macports.org> #52632: Inkscape-app quits immediately after install ---------------------------+-------------------------------- Reporter: iansidor@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: inkscape-app | ---------------------------+-------------------------------- Comment (by ichbindannmalwegmann): With environment variable "LANG" set to "de_CH.UTF-8" and "LC_CTYPE" unset Inkscape crashes but with "LC_CTYPE" set to "UTF-8" additionally it works. I discovered this by enabling the setting "Set locale environment variables on startup" in the tab "Advanced" in the "Peferences..." menu item of the "Terminal" application. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 10:16:39 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 10:16:39 -0000 Subject: [MacPorts] #53065: QGIS @2.18.0 build failure In-Reply-To: <047.acd0aebce4f8fa360df821a9edae7ed0@macports.org> References: <047.acd0aebce4f8fa360df821a9edae7ed0@macports.org> Message-ID: <062.d54419a6d1f35e18dd0c7b670fb7cc8d@macports.org> #53065: QGIS @2.18.0 build failure -------------------------+---------------------- Reporter: BuddyVolly | Owner: Veence Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: QGIS | -------------------------+---------------------- Comment (by Veence): I’m currently working on it, but I had to start over given the current Jasper woes and some other minor roadblocks. Expect something today. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 12:22:58 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 12:22:58 -0000 Subject: [MacPorts] #53115: argtable armadillo libpointing : Remove maintainer Message-ID: <053.42672d0e8653539f8a48a55963b730b3@macports.org> #53115: argtable armadillo libpointing : Remove maintainer ------------------------------+-------------------------------------------- Reporter: ChristianFrisson | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: argtable armadillo libpointing ------------------------------+-------------------------------------------- Hi, I had to switch to Homebrew for the sake of compatibility with colleagues. May I be removed from the maintainers of ports: argtable, armadillo, libpointing? https://github.com/macports/macports-ports/search?q=frisson Best regards, Christian Frisson -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 12:23:23 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 12:23:23 -0000 Subject: [MacPorts] #53005: coreutils @8.25: update to 8.26 In-Reply-To: <041.7260f4c736b0e373376e8f50949d41aa@macports.org> References: <041.7260f4c736b0e373376e8f50949d41aa@macports.org> Message-ID: <056.50b3931bdf6aa971d1a5b3f062b5c5ce@macports.org> #53005: coreutils @8.25: update to 8.26 ------------------------+---------------------- Reporter: l2dy | Owner: larryv Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: coreutils | ------------------------+---------------------- Comment (by l2dy): Fixed in 8daa55f75db9cf3378a8d8562b2a1237c84a75af. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 14:04:17 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 14:04:17 -0000 Subject: [MacPorts] #53090: py-pyqt* multiple Qt depspecs In-Reply-To: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> References: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> Message-ID: <056.fa8e01befd4e440a3e0716a0dc67315b@macports.org> #53090: py-pyqt* multiple Qt depspecs --------------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: py-pyqt4 py-pyqt5 | --------------------------------+---------------------- Changes (by RJVB): * Attachment "Portfile" added. fixed py-pyqt5 Portfile -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 14:05:37 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 14:05:37 -0000 Subject: [MacPorts] #53090: py-pyqt* multiple Qt depspecs In-Reply-To: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> References: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> Message-ID: <056.09e8cbc05f2c249f30af0f82c7ebdedc@macports.org> #53090: py-pyqt* multiple Qt depspecs --------------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: py-pyqt4 py-pyqt5 | --------------------------------+---------------------- Comment (by RJVB): Marko missed 2 crucial lines in his latest commit causing portindex to fail. Attached is the fixed version if anyone can commit this before he can get around to doing that. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 14:25:42 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 14:25:42 -0000 Subject: [MacPorts] #53107: py27-pygrib @2.0.2 update In-Reply-To: <044.366915d58c1d778030237b2c332b9007@macports.org> References: <044.366915d58c1d778030237b2c332b9007@macports.org> Message-ID: <059.f317c5a7826f1d71bba259ad26cfee73@macports.org> #53107: py27-pygrib @2.0.2 update --------------------------+----------------- Reporter: ForTozs | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py27-pygrib | --------------------------+----------------- Comment (by jswhit): It was broken by the latest update to the Jasper library. 2.0.2 fixes compatibility with the new Jasper. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 14:37:10 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 14:37:10 -0000 Subject: [MacPorts] #53100: Upgrade py27-eyed3 to 0.7.10 In-Reply-To: <046.b37f76b8844d45796a615c52296964e3@macports.org> References: <046.b37f76b8844d45796a615c52296964e3@macports.org> Message-ID: <061.716a634174e6467994fb66e661085c66@macports.org> #53100: Upgrade py27-eyed3 to 0.7.10 ------------------------+---------------------- Reporter: RichieB2B | Owner: elelay Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-eyed3 | ------------------------+---------------------- Changes (by mf2k): * owner: => elelay * status: new => assigned * type: defect => update * port: py27-eyed3 => py-eyed3 Comment: In the future, please Cc the port maintainers ({{{port info --maintainers py27-eyed3}}}), if any. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 14:44:02 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 14:44:02 -0000 Subject: [MacPorts] #53107: py27-pygrib @2.0.2 update In-Reply-To: <044.366915d58c1d778030237b2c332b9007@macports.org> References: <044.366915d58c1d778030237b2c332b9007@macports.org> Message-ID: <059.57b9b84ea8d290802fb3bed283ff1339@macports.org> #53107: py27-pygrib @2.0.2 update --------------------------+----------------- Reporter: ForTozs | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py27-pygrib | --------------------------+----------------- Comment (by jswhit): BTW: this is a duplicate of -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 14:45:14 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 14:45:14 -0000 Subject: [MacPorts] #53082: py-pygrib: update to 2.0.2 In-Reply-To: <043.577304d3ff1656f0fe045222bc374468@macports.org> References: <043.577304d3ff1656f0fe045222bc374468@macports.org> Message-ID: <058.281ab3362904a69a272950c6dc9b4e4c@macports.org> #53082: py-pygrib: update to 2.0.2 ------------------------+---------------------- Reporter: basmac | Owner: jswhit Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-pygrib | ------------------------+---------------------- Comment (by jswhit): diff available in the duplicate ticket -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 14:45:32 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 14:45:32 -0000 Subject: [MacPorts] #53116: arc @5.21o_1: update to 5.21p Message-ID: <041.707e6f126be59a447916450f879d60bb@macports.org> #53116: arc @5.21o_1: update to 5.21p --------------------+----------------- Reporter: l2dy | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: arc --------------------+----------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 14:46:39 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 14:46:39 -0000 Subject: [MacPorts] #53101: jasper fails to build +universal due to glut/OpenGL problems In-Reply-To: <045.bf4f074c5732d25ad8009bd2582ab00f@macports.org> References: <045.bf4f074c5732d25ad8009bd2582ab00f@macports.org> Message-ID: <060.43fb58bfa33514c8859c165bba85e56b@macports.org> #53101: jasper fails to build +universal due to glut/OpenGL problems ---------------------------+-------------------- Reporter: jeremyhu | Owner: jmroot Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: jasper cmake | ---------------------------+-------------------- Comment (by dershow): I'm still not able to get it to build. My log is attached. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 14:46:56 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 14:46:56 -0000 Subject: [MacPorts] #52193: [libutf8proc] update to 2.0.2 In-Reply-To: <053.e845653e4ab4b11d7f99ee975e8d179d@macports.org> References: <053.e845653e4ab4b11d7f99ee975e8d179d@macports.org> Message-ID: <068.816c32a83eb4e4302d133754adea7364@macports.org> #52193: [libutf8proc] update to 2.0.2 --------------------------+-------------------- Reporter: danchr@… | Owner: mww@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: libutf8proc | --------------------------+-------------------- Changes (by kurthindenburg): * status: new => closed * resolution: => fixed Comment: In [changeset:"fde15dcc9432c0b1f03dd7e6812f5a62935e664e/macports-ports" fde15dcc/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="fde15dcc9432c0b1f03dd7e6812f5a62935e664e" libutf8proc: update to 2.0.2 - maintainer timeout - move to github - add license - enable tests - not revbump only dep msort - doesn't build for me ATM closes https://trac.macports.org/ticket/52193 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 14:47:05 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 14:47:05 -0000 Subject: [MacPorts] #53108: openssh 7.4p1 release In-Reply-To: <047.1e7e14f0247ff7de5f469ecdc5024132@macports.org> References: <047.1e7e14f0247ff7de5f469ecdc5024132@macports.org> Message-ID: <062.1660e6586da1cb7e5fe598924940b6b0@macports.org> #53108: openssh 7.4p1 release -------------------------+---------------------- Reporter: danielluke | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: openssh | -------------------------+---------------------- Changes (by mf2k): * keywords: => haspatch * type: defect => update -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 14:47:22 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 14:47:22 -0000 Subject: [MacPorts] #53101: jasper fails to build +universal due to glut/OpenGL problems In-Reply-To: <045.bf4f074c5732d25ad8009bd2582ab00f@macports.org> References: <045.bf4f074c5732d25ad8009bd2582ab00f@macports.org> Message-ID: <060.1c2936ada9a93e3d010ff3e6aed14cc1@macports.org> #53101: jasper fails to build +universal due to glut/OpenGL problems ---------------------------+-------------------- Reporter: jeremyhu | Owner: jmroot Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: jasper cmake | ---------------------------+-------------------- Changes (by dershow): * Attachment "main.log" added. Failed build log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 15:07:01 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 15:07:01 -0000 Subject: [MacPorts] #52910: glbinding 2.1.1 submission In-Reply-To: <058.43f97ed30a6fdabdf3b11fe6c21818e3@macports.org> References: <058.43f97ed30a6fdabdf3b11fe6c21818e3@macports.org> Message-ID: <073.163bad8d6b04e218a90944f43f061a3e@macports.org> #52910: glbinding 2.1.1 submission ------------------------------------+-------------------------------- Reporter: ken-cunningham-webuse | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: glbinding | ------------------------------------+-------------------------------- Changes (by kencu): * Attachment "Portfile.2" added. Portfile.update.20161220 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 15:08:03 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 15:08:03 -0000 Subject: [MacPorts] #52910: glbinding 2.1.1 submission In-Reply-To: <058.43f97ed30a6fdabdf3b11fe6c21818e3@macports.org> References: <058.43f97ed30a6fdabdf3b11fe6c21818e3@macports.org> Message-ID: <073.b1ad7dcd7d8b784f553d488585d7ace7@macports.org> #52910: glbinding 2.1.1 submission ------------------------------------+-------------------------------- Reporter: ken-cunningham-webuse | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: glbinding | ------------------------------------+-------------------------------- Comment (by kencu): I have updated the glbinding portfile with some minor edits to description and whitespace -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 15:09:00 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 15:09:00 -0000 Subject: [MacPorts] #52927: cpplocate submission In-Reply-To: <058.b214ea1ffb947dd392cd255bad94914e@macports.org> References: <058.b214ea1ffb947dd392cd255bad94914e@macports.org> Message-ID: <073.cb368026c8797e2418fd218e006ec713@macports.org> #52927: cpplocate submission ------------------------------------+-------------------------------- Reporter: ken-cunningham-webuse | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: cpplocate | ------------------------------------+-------------------------------- Changes (by kencu): * Attachment "Portfile.3" added. Portfile update 20161220 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 15:09:24 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 15:09:24 -0000 Subject: [MacPorts] #52927: cpplocate submission In-Reply-To: <058.b214ea1ffb947dd392cd255bad94914e@macports.org> References: <058.b214ea1ffb947dd392cd255bad94914e@macports.org> Message-ID: <073.14bddc66c1cdbf6f07da1383a96eff74@macports.org> #52927: cpplocate submission ------------------------------------+-------------------------------- Reporter: ken-cunningham-webuse | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: cpplocate | ------------------------------------+-------------------------------- Comment (by kencu): I have updated the cpplocate portfile with some minor edits to description and whitespace -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 15:16:23 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 15:16:23 -0000 Subject: [MacPorts] #52123: rtmpdump @2.4_2: needs updating In-Reply-To: <046.d0d0f77325a120eaceacc5b7aa0de6d1@macports.org> References: <046.d0d0f77325a120eaceacc5b7aa0de6d1@macports.org> Message-ID: <061.11353d84fdeef46e95dded2f8d3db2b2@macports.org> #52123: rtmpdump @2.4_2: needs updating ------------------------+------------------------ Reporter: keybounce | Owner: captsolo@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rtmpdump | ------------------------+------------------------ Changes (by kurthindenburg): * cc: khindenburg (added) Comment: Ideally, they should release a new version You can read https://guide.macports.org/#development and https://guide.macports.org/#reference.phases.fetch.advanced Also, looking at other Portfiles that use git is often helpful -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 15:16:30 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 15:16:30 -0000 Subject: [MacPorts] #53082: py-pygrib: update to 2.0.2 In-Reply-To: <043.577304d3ff1656f0fe045222bc374468@macports.org> References: <043.577304d3ff1656f0fe045222bc374468@macports.org> Message-ID: <058.fbe1b8efd73dbc1e1f6f0d3b7a8f7563@macports.org> #53082: py-pygrib: update to 2.0.2 ------------------------+-------------------- Reporter: basmac | Owner: jswhit Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: duplicate | Keywords: Port: py-pygrib | ------------------------+-------------------- Changes (by mf2k): * status: assigned => closed * resolution: => duplicate Comment: #53107 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 15:16:40 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 15:16:40 -0000 Subject: [MacPorts] #53065: QGIS @2.18.0 build failure In-Reply-To: <047.acd0aebce4f8fa360df821a9edae7ed0@macports.org> References: <047.acd0aebce4f8fa360df821a9edae7ed0@macports.org> Message-ID: <062.686d6524efa21c882d6e365a0d5c5e12@macports.org> #53065: QGIS @2.18.0 build failure -------------------------+---------------------- Reporter: BuddyVolly | Owner: Veence Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: QGIS | -------------------------+---------------------- Comment (by Veence): It’s been updated ans should be fixed. Please note that the buildbot failed to install any other version than the 10.12-based one, because of timeouts (internal errors I’ve no control over). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 15:17:08 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 15:17:08 -0000 Subject: [MacPorts] #53107: py-pygrib @2.0.2 update (was: py27-pygrib @2.0.2 update) In-Reply-To: <044.366915d58c1d778030237b2c332b9007@macports.org> References: <044.366915d58c1d778030237b2c332b9007@macports.org> Message-ID: <059.029cefbbf866b0bd59e5892498f8e111@macports.org> #53107: py-pygrib @2.0.2 update ------------------------+---------------------- Reporter: ForTozs | Owner: jswhit Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: py-pygrib | ------------------------+---------------------- Changes (by mf2k): * status: new => assigned * cc: jswhit@… (removed) * owner: => jswhit * keywords: => haspatch * port: py27-pygrib => py-pygrib -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 15:18:17 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 15:18:17 -0000 Subject: [MacPorts] #50100: clang-3.8 fails to support Boost.Python In-Reply-To: <042.4575f4a5b70d2eabd86be24da84fd5c5@macports.org> References: <042.4575f4a5b70d2eabd86be24da84fd5c5@macports.org> Message-ID: <057.56fd062d9b8a980740fe1e1532375b87@macports.org> #50100: clang-3.8 fails to support Boost.Python ---------------------------------------+-------------------------------- Reporter: akimd | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: C++ Port: clang-3.8 boost python34 | ---------------------------------------+-------------------------------- Comment (by akimd): you are right, it works. Thanks! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 15:19:14 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 15:19:14 -0000 Subject: [MacPorts] #52115: p7zip @15.14.1_1: update to 16.02 In-Reply-To: <041.23adb3d26c4c3733eb40378127235960@macports.org> References: <041.23adb3d26c4c3733eb40378127235960@macports.org> Message-ID: <056.05ff3a9ae625d8e59768124041d5fe04@macports.org> #52115: p7zip @15.14.1_1: update to 16.02 ---------------------+----------------------------- Reporter: l2dy | Owner: stuartwesterman Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: p7zip | ---------------------+----------------------------- Changes (by kurthindenburg): * status: new => closed * cc: khindenburg (added) * resolution: => fixed Comment: This was updated last month -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 15:22:29 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 15:22:29 -0000 Subject: [MacPorts] #53117: Trac is unreliable Message-ID: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> #53117: Trac is unreliable ----------------------------+--------------------- Reporter: mf2k | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Keywords: | Port: ----------------------------+--------------------- As a frequent user of the new Trac, I see it fail to accept my changes about 10-20% of the time. What happens is that I press the "Preview" or "Update" button and get a timeout page. I will update this ticket with more precise details the next it happens to me. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 15:30:24 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 15:30:24 -0000 Subject: [MacPorts] #53117: Trac is unreliable In-Reply-To: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> References: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> Message-ID: <056.2c1955a583b749e5da3287ac2794d337@macports.org> #53117: Trac is unreliable -----------------------------+--------------------- Reporter: mf2k | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+--------------------- Comment (by neverpanic): I don't see anything out of the ordinary in the statistics. If you have a timestamp I can look into the logs. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 15:33:26 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 15:33:26 -0000 Subject: [MacPorts] #53117: Trac is unreliable In-Reply-To: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> References: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> Message-ID: <056.126f2b274a58daf9ec0d2cb1aeaa08ea@macports.org> #53117: Trac is unreliable -----------------------------+--------------------- Reporter: mf2k | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+--------------------- Comment (by mf2k): Last time it happened to me was approximately 8:15 am MST (about 18 minutes before this post). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 15:47:55 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 15:47:55 -0000 Subject: [MacPorts] #53118: add nccmp into macports ? Message-ID: <043.1244f8056d17c36ca50189d9d0741e3b@macports.org> #53118: add nccmp into macports ? -----------------------+------------------- Reporter: basmac | Owner: Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: add nccmp | Port: nccmp -----------------------+------------------- Its in home-brew, so can some kind person include it into macports ? http://nccmp.sourceforge.net/#download -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 15:56:16 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 15:56:16 -0000 Subject: [MacPorts] #53118: add nccmp into macports ? In-Reply-To: <043.1244f8056d17c36ca50189d9d0741e3b@macports.org> References: <043.1244f8056d17c36ca50189d9d0741e3b@macports.org> Message-ID: <058.4e15f7aa1a2d806400b66fc17ad22889@macports.org> #53118: add nccmp into macports ? ----------------------+----------------- Reporter: basmac | Owner: Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: nccmp | ----------------------+----------------- Changes (by mf2k): * keywords: add nccmp => * version: 2.3.5 => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 16:09:55 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 16:09:55 -0000 Subject: [MacPorts] #53110: libomp and clang-3.8 fail on Lion In-Reply-To: <043.c5ec93166b62879945bea5439c7783d1@macports.org> References: <043.c5ec93166b62879945bea5439c7783d1@macports.org> Message-ID: <058.d79e663f355747a86c9c76269753a4d6@macports.org> #53110: libomp and clang-3.8 fail on Lion --------------------------------+------------------- Reporter: RobK88 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: libomp, clang-3.8 | --------------------------------+------------------- Comment (by RobK88): I ran: {{{ sudo port -v install libomp configure.compiler=macports-clang-3.7 }}} It worked. libomp compiled and was installed. Then I ran: {{{ sudo port -v install clang-3.8 }}} Clang-3.8 was compiled and installed. Do I need to recompile libomp with clang-3.8? If so, how would I do this. And finally, I ran: {{{ sodo port upgrade outdated }}} All my outdated packages were upgraded. (But there was one broken package -- speex. Looks liked a dependency issue with ffmpeg. But the package was automatically uninstalled, deactivated etc and there were no broken packages at the end). So my system looks like it is finally updated. Many thanks for all your help. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 17:23:45 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 17:23:45 -0000 Subject: [MacPorts] #53110: libomp and clang-3.8 fail on Lion In-Reply-To: <043.c5ec93166b62879945bea5439c7783d1@macports.org> References: <043.c5ec93166b62879945bea5439c7783d1@macports.org> Message-ID: <058.5b0d8e0220806ba9d0eb704312f845ad@macports.org> #53110: libomp and clang-3.8 fail on Lion --------------------------------+------------------- Reporter: RobK88 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: libomp, clang-3.8 | --------------------------------+------------------- Comment (by kencu): I don't think you need to rebuild libomp with clang-3.8. The version you built should be fine. Glad it worked! -- K -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 17:51:11 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 17:51:11 -0000 Subject: [MacPorts] #53102: jasper dylib current version regressed In-Reply-To: <045.1d96a7542a3d6b123e5fe23a43d0875d@macports.org> References: <045.1d96a7542a3d6b123e5fe23a43d0875d@macports.org> Message-ID: <060.1bd937fc64f23121be6459b69b60cfba@macports.org> #53102: jasper dylib current version regressed -----------------------+-------------------- Reporter: jeremyhu | Owner: jmroot Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: jasper | -----------------------+-------------------- Comment (by basmac): I see the problem with ncl build with the new lib jasper and then copying back the pre-current lib jasper Current libjasper sh-3.2$ ncl /Users/bmcinnes/test/bar.ncl dyld: Library not loaded: /opt/local/lib/libjasper.4.dylib Referenced from: /usr/local/ncl/bin/ncl Reason: Incompatible library version: ncl requires version 5.0.0 or later, but libjasper.4.dylib provides version 4.0.0 /usr/local/bin/ncl: line 6: 39341 Abort trap: 6 $NCARG_ROOT/bin/ncl "$@" sh-3.2$ locate libjasper.4.dylib /Volumes/Cluster/opt/local/lib/libjasper.4.dylib /opt/local/lib/libjasper.4.dylib sh-3.2$ ls -l /opt/local/lib/libjasper.4.dylib lrwxr-xr-x 1 root admin 21 Dec 19 17:48 /opt/local/lib/libjasper.4.dylib -> libjasper.4.0.0.dylib Copying back previous libjasper sh-3.2$ ncl /Users/bmcinnes/test/bar.ncl Copyright (C) 1995-2015 - All Rights Reserved University Corporation for Atmospheric Research NCAR Command Language Version 6.3.0 The use of this software is governed by a License Agreement. See http://www.ncl.ucar.edu/ for more details. Variable: nc_file_type Type: string Total Size: 8 bytes 1 values Number of Dimensions: 1 Dimensions and sizes: [1] Coordinates: (0) netcdf3 Variable: nc_file_type Type: string Total Size: 8 bytes 1 values Number of Dimensions: 1 Dimensions and sizes: [1] Coordinates: (0) netcdf4 Variable: nc_file_type Type: string Total Size: 8 bytes 1 values Number of Dimensions: 1 Dimensions and sizes: [1] Coordinates: (0) netcdf3 sh-3.2$ -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 18:01:10 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 18:01:10 -0000 Subject: [MacPorts] #53119: Jasper fails to build Message-ID: <044.7102706dad0c13d0dcbcddf3d9b187fc@macports.org> #53119: Jasper fails to build ---------------------+-------------------- Reporter: dershow | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: jasper ---------------------+-------------------- Jasper upgrade from 1.999.29_0 to 2.0.6 was failing, there was then an update to 2.0.6_1 but that fails to build for me. I have attached the log file. I'm running 10.11.6 and I have tried both Xcode 7.3.1 (log attached) as well as 8.2. This is particularly significant because many other ports depend on jasper. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 18:02:51 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 18:02:51 -0000 Subject: [MacPorts] #53119: Jasper fails to build In-Reply-To: <044.7102706dad0c13d0dcbcddf3d9b187fc@macports.org> References: <044.7102706dad0c13d0dcbcddf3d9b187fc@macports.org> Message-ID: <059.9f0b957796a359ca1f13114783cb8049@macports.org> #53119: Jasper fails to build ----------------------+----------------- Reporter: dershow | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: jasper | ----------------------+----------------- Changes (by dershow): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 18:03:47 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 18:03:47 -0000 Subject: [MacPorts] #53119: Jasper fails to build In-Reply-To: <044.7102706dad0c13d0dcbcddf3d9b187fc@macports.org> References: <044.7102706dad0c13d0dcbcddf3d9b187fc@macports.org> Message-ID: <059.0b807c556468b92ad3fe62ff642d0d89@macports.org> #53119: Jasper fails to build ----------------------+----------------- Reporter: dershow | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: jasper | ----------------------+----------------- Comment (by dershow): Note that this error is different from ticket: https://trac.macports.org/ticket/53101 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 18:24:17 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 18:24:17 -0000 Subject: [MacPorts] #53065: QGIS @2.18.0 build failure In-Reply-To: <047.acd0aebce4f8fa360df821a9edae7ed0@macports.org> References: <047.acd0aebce4f8fa360df821a9edae7ed0@macports.org> Message-ID: <062.d356a042570567db2381afdef1421907@macports.org> #53065: QGIS @2.18.0 build failure -------------------------+---------------------- Reporter: BuddyVolly | Owner: Veence Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: QGIS | -------------------------+---------------------- Comment (by BuddyVolly): Dear Vincent, you know, in heaven, there must be a magical place for guys like you! For me it works. Thanks a lot, Andreas -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 19:17:55 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 19:17:55 -0000 Subject: [MacPorts] #53120: Checksum mismatch - EiffelStudio Message-ID: <048.ce2411c5e538d88ac602ab4e1cb3a4cc@macports.org> #53120: Checksum mismatch - EiffelStudio -------------------------+----------------- Reporter: Dexterfreak | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: -------------------------+----------------- Hello, i have been trying to install eiffelstudio and i keep getting this error: {{{ ---> Computing dependencies for eiffelstudio ---> Verifying checksums for eiffelstudio Error: Checksum (rmd160) mismatch for eiffelstudio-16.05.tar Error: Checksum (sha256) mismatch for eiffelstudio-16.05.tar Error: org.macports.checksum for port eiffelstudio returned: Unable to verify file checksums Please see the log file for port eiffelstudio for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_eiffelstudio/eiffelstudio/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port eiffelstudio failed }}} I have tried cleaning, reinstalling again and again.. restart , i chekced the FAQ about Checksum and i couldn't get it solved, i really need eiffelstudio for school, thanks. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 19:19:34 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 19:19:34 -0000 Subject: [MacPorts] #53110: libomp and clang-3.8 fail on Lion In-Reply-To: <043.c5ec93166b62879945bea5439c7783d1@macports.org> References: <043.c5ec93166b62879945bea5439c7783d1@macports.org> Message-ID: <058.bd33dc714ea1de1b096603de40e2f102@macports.org> #53110: libomp and clang-3.8 fail on Lion --------------------------------+------------------- Reporter: RobK88 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: libomp, clang-3.8 | --------------------------------+------------------- Comment (by RobK88): Thanks again for all your help. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 19:23:35 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 19:23:35 -0000 Subject: [MacPorts] #53121: Trac should automatically Cc port maintainers Message-ID: <046.5b9f9533d5da25e9542c640900b6dda0@macports.org> #53121: Trac should automatically Cc port maintainers ----------------------------+--------------------- Reporter: RichieB2B | Owner: admin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Keywords: | Port: ----------------------------+--------------------- When a new ticket is filed for a port, Trac should automatically Cc the port maintainers ({{{port info --maintainers }}}), if any. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 19:44:44 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 19:44:44 -0000 Subject: [MacPorts] #53119: Jasper fails to build In-Reply-To: <044.7102706dad0c13d0dcbcddf3d9b187fc@macports.org> References: <044.7102706dad0c13d0dcbcddf3d9b187fc@macports.org> Message-ID: <059.cdc67a1d5adff3cd77d1dbd3bd4a65f7@macports.org> #53119: Jasper fails to build ----------------------+--------------------------------- Reporter: dershow | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: jasper | ----------------------+--------------------------------- Changes (by MarcusCalhoun-Lopez): * owner: => MarcusCalhoun-Lopez * status: new => closed * resolution: => fixed Comment: In [changeset:"c333001faf7ae274f271fcecb6667534dde090b6/macports-ports" c333001f/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="c333001faf7ae274f271fcecb6667534dde090b6" jasper: control if and how documentation is built Fixes https://trac.macports.org/ticket/53119 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 19:45:37 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 19:45:37 -0000 Subject: [MacPorts] #53101: jasper fails to build +universal due to glut/OpenGL problems In-Reply-To: <045.bf4f074c5732d25ad8009bd2582ab00f@macports.org> References: <045.bf4f074c5732d25ad8009bd2582ab00f@macports.org> Message-ID: <060.0761d6bb28e7178a4422c5a119eebc66@macports.org> #53101: jasper fails to build +universal due to glut/OpenGL problems ---------------------------+-------------------- Reporter: jeremyhu | Owner: jmroot Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: jasper cmake | ---------------------------+-------------------- Changes (by jmroot): * status: new => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 19:51:47 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 19:51:47 -0000 Subject: [MacPorts] #53121: Trac should automatically Cc port maintainers In-Reply-To: <046.5b9f9533d5da25e9542c640900b6dda0@macports.org> References: <046.5b9f9533d5da25e9542c640900b6dda0@macports.org> Message-ID: <061.3d18967d55c5a53f10b2a9e08eddb5a8@macports.org> #53121: Trac should automatically Cc port maintainers -----------------------------+--------------------- Reporter: RichieB2B | Owner: admin@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: duplicate | Keywords: Port: | -----------------------------+--------------------- Changes (by jmroot): * status: new => closed * resolution: => duplicate Comment: #40987 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 20:24:26 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 20:24:26 -0000 Subject: [MacPorts] #53021: octave @4.2.0_1 +gcc6 +openblas: build failure In-Reply-To: <041.a9100f410b771f7245060d742521900f@macports.org> References: <041.a9100f410b771f7245060d742521900f@macports.org> Message-ID: <056.2840b1aa4cb1a51a196c9d2ad92a5c7c@macports.org> #53021: octave @4.2.0_1 +gcc6 +openblas: build failure ---------------------+--------------------------------- Reporter: mf2k | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: octave | ---------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): In [changeset:"7519f9aeb46b10b14cb9d36589b55664df487403/macports-ports" 7519f9ae/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="7519f9aeb46b10b14cb9d36589b55664df487403" octave: allow GCC to compile Carbon API See https://trac.macports.org/ticket/53021 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 20:26:17 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 20:26:17 -0000 Subject: [MacPorts] #53117: Trac is unreliable In-Reply-To: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> References: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> Message-ID: <056.e2f240de91418433e8ac6ea765023894@macports.org> #53117: Trac is unreliable -----------------------------+--------------------- Reporter: mf2k | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+--------------------- Comment (by mf2k): It happened just now when trying to update a ticket. Attaching a screenshot of the error from Safari. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 20:26:37 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 20:26:37 -0000 Subject: [MacPorts] #53117: Trac is unreliable In-Reply-To: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> References: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> Message-ID: <056.37d2234aa512a9594eac1f47cf916188@macports.org> #53117: Trac is unreliable -----------------------------+--------------------- Reporter: mf2k | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+--------------------- Changes (by mf2k): * Attachment "Screen Shot 2016-12-20 at 1.25.25 PM.png" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 20:27:11 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 20:27:11 -0000 Subject: [MacPorts] #53120: Checksum mismatch - EiffelStudio In-Reply-To: <048.ce2411c5e538d88ac602ab4e1cb3a4cc@macports.org> References: <048.ce2411c5e538d88ac602ab4e1cb3a4cc@macports.org> Message-ID: <063.9b2a3f7086528a661ea9adc860ae8281@macports.org> #53120: Checksum mismatch - EiffelStudio ---------------------------+---------------------- Reporter: Dexterfreak | Owner: jann@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: EiffelStudio | ---------------------------+---------------------- Changes (by mf2k): * status: new => assigned * owner: => jann@… * port: => EiffelStudio Comment: In the future, please fill in the Port field and Cc the port maintainers ({{{port info --maintainers EiffelStudio}}}), if any. Per the [wiki:FAQ#checksums FAQ about checksum errors], you did not specify the mirror that you downloaded the archive from. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 20:29:47 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 20:29:47 -0000 Subject: [MacPorts] #53021: octave @4.2.0_1 +gcc6 +openblas: build failure In-Reply-To: <041.a9100f410b771f7245060d742521900f@macports.org> References: <041.a9100f410b771f7245060d742521900f@macports.org> Message-ID: <056.6e8adf4edfdb9964b06331336a7528a2@macports.org> #53021: octave @4.2.0_1 +gcc6 +openblas: build failure ---------------------+--------------------------------- Reporter: mf2k | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: octave | ---------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): There seems to be two problems here.[[BR]] Apparently, clang and gcc [http://stackoverflow.com/questions/21592494 /initializer-element-is-not-constant-error-for-no-reason-in-linux-gcc- compilin treat constants differently].[[BR]] Further, newer versions of Xcode use {{{__attribute__}}} in a way GCC does not understand.[[BR]] [changeset:"7519f9aeb46b10b14cb9d36589b55664df487403/macports-ports" 7519f9ae/macports-ports] is certainly not pretty, but does it solve the problem? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 20:41:40 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 20:41:40 -0000 Subject: [MacPorts] #53100: Upgrade py27-eyed3 to 0.7.10 In-Reply-To: <046.b37f76b8844d45796a615c52296964e3@macports.org> References: <046.b37f76b8844d45796a615c52296964e3@macports.org> Message-ID: <061.119547bcbacef082f1b5537dc87e986b@macports.org> #53100: Upgrade py27-eyed3 to 0.7.10 ------------------------+-------------------- Reporter: RichieB2B | Owner: elelay Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: py-eyed3 | ------------------------+-------------------- Changes (by elelay): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"03702683c2f11b65896dfe400a289ccbfc0b2f68/macports-ports" 03702683/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="03702683c2f11b65896dfe400a289ccbfc0b2f68" py*-eyed3 upgrade to 0.7.10 closes https://trac.macports.org/ticket/53100 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 20:47:02 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 20:47:02 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.daa86a399f104f06dacf7546b67fe5a7@macports.org> #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): Replying to [comment:12 mojca]: > Oh, wait ... I just tried to run `octave` now to test it and I get a GUI instead of the command line? Is this something new from version 4.2 or is that because I disabled graphicsmagick? I like the GUI of course, but is there any trick to force it to stay in the Terminal? And the GUI is stalled at exit. I have to force quit it. {{{sudo port install octave -qt4 -qt5}}} should install octave without the GUI.[[BR]] To force octave to run without the GUI, either run {{{octave-cli}}} instead of {{{octave}}} or run {{{octave --no-gui-libs}}}. Replying to [comment:4 mojca]: > What role does GraphicsMagick play for Octave? Could it be disabled on older platforms if that is the likely source of troubles? Or is it absolutely necessary to do any plotting? It is not necessary for plotting.[[BR]] To quote the configure script: {{{ configure: WARNING: --without-magick specified. The imread, imwrite, and imfinfo functions for reading and writing image files will not be fully functional. }}} I use them quite a bit, so I was just trying to get it to work for others.[[BR]] I will make one more attempt to get everything working before I turn off graphicsmagick on older systems. Thanks for your patience and help. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 20:54:25 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 20:54:25 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.cac154715ab07d61560d9a71e4d63d8f@macports.org> #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): In [changeset:"35f9174550d198e64c2bd56552a1cf6137afa70b/macports-ports" 35f9174/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="35f9174550d198e64c2bd56552a1cf6137afa70b" octave: use older libstdc++ ABI on older system See https://trac.macports.org/ticket/53044 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 22:06:16 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 22:06:16 -0000 Subject: [MacPorts] #53122: gpgme : upgrade to 1.8.0 and +qt5 variant Message-ID: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> #53122: gpgme : upgrade to 1.8.0 and +qt5 variant ----------------------+------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: gpgme ----------------------+------------------- This is an upgrade for port:gpgme to bring it to 1.8.0 and also introduce a +qt5 variant so that future KF5 ports can use its QGpgME library. Surprisingly gpgme 1.8 introduces a number of missing function declarations which apparently were declared properly in 1.7.0 (or not used). We may want to notify upstream, but maybe we should first figure out the best fix. The current implementation provides the missing prototypes, as I am not sure what the effect would be of using an alternative (better?) fix: `configure.cppflags-append -D__DARWIN_C_LEVEL=200112L`. There are also a few cases where I could use a proper fix (add a missing strings.h header and use the `qstrdup()` equivalent of `strdup()` in Qt code). Similarly, the CMake files need correction of the shared library extension, something done currently in the post-destroot but that probably ought to be reported upstream as it wasn't required in the earlier versions. The QGpgME library is call `libqgpgme` by default, which unfortunately is the same name used by the equivalent (but Qt4-based) library provided by port:kdepimlibs4 . The current proposal avoids this through a patch of the build system that renames the library to `libq5gpgme`, rather than figuring out how to change that port once more to allow co-existence. This has been tested and seems to work for me. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 22:06:51 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 22:06:51 -0000 Subject: [MacPorts] #53122: gpgme : upgrade to 1.8.0 and +qt5 variant In-Reply-To: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> References: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> Message-ID: <056.3a60734a6bda746ec015011bb78fd706@macports.org> #53122: gpgme : upgrade to 1.8.0 and +qt5 variant ---------------------+---------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: gpgme | ---------------------+---------------------- Changes (by RJVB): * Attachment "gpgme.diff" added. updated Portfile (diff against macports-ports master/head) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 22:07:12 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 22:07:12 -0000 Subject: [MacPorts] #53122: gpgme : upgrade to 1.8.0 and +qt5 variant In-Reply-To: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> References: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> Message-ID: <056.5155c0b91b046e9540d578cb0123fadb@macports.org> #53122: gpgme : upgrade to 1.8.0 and +qt5 variant ---------------------+---------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: gpgme | ---------------------+---------------------- Changes (by RJVB): * Attachment "patch-missing-prototypes.diff" added. adds the missing function declarations -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 22:07:29 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 22:07:29 -0000 Subject: [MacPorts] #53122: gpgme : upgrade to 1.8.0 and +qt5 variant In-Reply-To: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> References: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> Message-ID: <056.f3263ad4d90ce73076d23a577fa8a3af@macports.org> #53122: gpgme : upgrade to 1.8.0 and +qt5 variant ---------------------+---------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: gpgme | ---------------------+---------------------- Changes (by RJVB): * Attachment "patch-libqgpgme-name.diff" added. renames libqgpgme to libq5gpgme -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 22:08:37 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 22:08:37 -0000 Subject: [MacPorts] #53122: gpgme : upgrade to 1.8.0 and +qt5 variant In-Reply-To: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> References: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> Message-ID: <056.a74e9fb26ec634956e59a9a0d83a94b4@macports.org> #53122: gpgme : upgrade to 1.8.0 and +qt5 variant ---------------------+---------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: gpgme | ---------------------+---------------------- Changes (by RJVB): * Attachment "gpgme.2.diff" added. updated Portfile (diff against macports-ports master/head) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 22:20:37 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 22:20:37 -0000 Subject: [MacPorts] #51520: llvm-3.9 @3.9-r270400_0+assertions+debug build failure on snow leopard due to missing strnlen function - and fix In-Reply-To: <067.fcaa7e4195b6cce47cbccee919b1a2f0@macports.org> References: <067.fcaa7e4195b6cce47cbccee919b1a2f0@macports.org> Message-ID: <082.c6bcab8badec6d5776e263b77971680c@macports.org> #51520: llvm-3.9 @3.9-r270400_0+assertions+debug build failure on snow leopard due to missing strnlen function - and fix -------------------------------------+------------------------- Reporter: kenneth.f.cunningham@… | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: snowleopard Port: llvm-3.9 clang-3.9 | -------------------------------------+------------------------- Changes (by jeremyhu): * status: new => closed * resolution: => fixed Comment: In [changeset:"e5c93e651600c064398f25a8af61b9242cb9ed42/macports-ports" e5c93e65/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="e5c93e651600c064398f25a8af61b9242cb9ed42" llvm-{3.9,devel}: Provide implementation of strnlen for pre-Lion Fixes https://trac.macports.org/ticket/51520 Signed-off-by: Jeremy Huddleston Sequoia }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 22:45:39 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 22:45:39 -0000 Subject: [MacPorts] #53122: gpgme : upgrade to 1.8.0 and +qt5 variant In-Reply-To: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> References: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> Message-ID: <056.89513d8734e67110ef8ab5f74ae877d9@macports.org> #53122: gpgme : upgrade to 1.8.0 and +qt5 variant ---------------------+---------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: gpgme | ---------------------+---------------------- Comment (by lbschenkel): I do not necessarily oppose merging your contributions, but I would like to raise the question if we should report this to upstream instead and wait for a bugfix release instead of making divergent changes downstream which would increase the burden of maintaining the package. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 23:04:18 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 23:04:18 -0000 Subject: [MacPorts] #53122: gpgme : upgrade to 1.8.0 and +qt5 variant In-Reply-To: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> References: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> Message-ID: <056.1f012934ef82f74a72b39ed14d6fd7a0@macports.org> #53122: gpgme : upgrade to 1.8.0 and +qt5 variant ---------------------+------------------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch upstream Port: gpgme | ---------------------+------------------------------- Changes (by dbevans): * keywords: haspatch => haspatch upstream Comment: I agree with Leonardo. These issues and proposed solutions should be forwarded upstream. Additionally, there really are two differenct issues here that should be addressed individually {{{ * the missing symbol issues that cause the basic build of 1.8 to fail * support for qt5 }}} I have to confess that I haven't done anything with the first issue for a while because I thought the appropriate bug fix release must surely be in the works but apparently not. I'll get the lead out and give them a push on this. As to qt5 support, renaming libraries, etc I suggest the reporter take the lead in coordinating that upstream before we do anything further here. Marking this as an upstream issue for now. Please attach a reference to any upstream bug reports that may be generated so the issues can be tracked. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 23:19:43 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 23:19:43 -0000 Subject: [MacPorts] #53122: gpgme : upgrade to 1.8.0 and +qt5 variant In-Reply-To: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> References: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> Message-ID: <056.6fb63fc3262eb9ba55c57b9b53722516@macports.org> #53122: gpgme : upgrade to 1.8.0 and +qt5 variant ---------------------+------------------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch upstream Port: gpgme | ---------------------+------------------------------- Comment (by RJVB): I can look into reporting upstream tomorrow, but I think we should also figure out the proper way to get the strdup prototype from the string.h header. Once we have a few correct patches for what are clearly issues it should be much easier to get those patches accepted. Either way, it is rarely a good idea to wait for a bugfix release if you already have fixes and/or workarounds. The only question I have is when 1.8.1 can be expected. I think I've already seen it mentioned somewhere (IIRC in relation to bugs in 1.8.0), but to me gpgme is just another dependency, not something I work with directly so I'm following its evolution closely. I'd expect the port maintainers to be doing that a bit more ;) David: the library renaming is all that's advisable for Qt5 support, and it is not really an upstream issue. We can raise the idea upstream, but I think their position will be that we should find our own solution if we want to be able to install the Qt4 and Qt5 libraries in the same directory, and it's not like we've never done this kind of thing before. From what I understand, QGpgME is included with gpgme as largely a courtesy so the KDE PIM developers don't have to continue to provide it. KDE PIM 5 has done nothing to allow coinstallation with KDE PIM 4, which probably explains why the library wasn't renamed as the Qt5 versions of so many other libraries were. Sadly we're not close to being able to retire kdepimlibs4, and it's a crucial package for me. We *could* try to change the Qt4 gpgme libraries, but I have a feeling that might be less straightforward than with the Qt5 version. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 23:33:10 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 23:33:10 -0000 Subject: [MacPorts] #53122: gpgme : upgrade to 1.8.0 and +qt5 variant In-Reply-To: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> References: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> Message-ID: <056.68338559963704f0868789696372f277@macports.org> #53122: gpgme : upgrade to 1.8.0 and +qt5 variant ---------------------+------------------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch upstream Port: gpgme | ---------------------+------------------------------- Comment (by RJVB): If you prefer we (Marko and I) can also take care of the QGpgME library as a separate port (depending on port:gpgme), so we can address any issues with it ourselves. That would make sense, given how the component comes from KDE and will presumably be used primarily by KDE (KF5) applications. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 23:48:10 2016 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2016 23:48:10 -0000 Subject: [MacPorts] #53122: gpgme : upgrade to 1.8.0 and +qt5 variant In-Reply-To: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> References: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> Message-ID: <056.46310853772a686b89332e87727680f3@macports.org> #53122: gpgme : upgrade to 1.8.0 and +qt5 variant ---------------------+------------------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch upstream Port: gpgme | ---------------------+------------------------------- Comment (by dbevans): I agree that sounds like a better approach and would allow you guys to work on that independently in a more contained environment. I'll look at the strdup issues in the next day or so with an eye to a slightly simpler solution after I understand more clearly exactly what's going on. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 00:08:09 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 00:08:09 -0000 Subject: [MacPorts] #53122: gpgme : upgrade to 1.8.0 and +qt5 variant In-Reply-To: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> References: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> Message-ID: <056.381d775275cc4c43fa8e4250355984c6@macports.org> #53122: gpgme : upgrade to 1.8.0 and +qt5 variant ---------------------+------------------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch upstream Port: gpgme | ---------------------+------------------------------- Comment (by dbevans): Apparently the macOS strdup issue has been discussed upstream and they recommend adding {{{ -D_DARWIN_C_SOURCE=900000L }}} to the CFLAGS and CXXFLAGS. See https://www.mail-archive.com/gnupg-users at gnupg.org/msg31883.html -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 00:36:40 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 00:36:40 -0000 Subject: [MacPorts] #53065: QGIS @2.18.0 build failure In-Reply-To: <047.acd0aebce4f8fa360df821a9edae7ed0@macports.org> References: <047.acd0aebce4f8fa360df821a9edae7ed0@macports.org> Message-ID: <062.8285606106287ac60e43997787f3e07c@macports.org> #53065: QGIS @2.18.0 build failure -------------------------+---------------------- Reporter: BuddyVolly | Owner: Veence Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: QGIS | -------------------------+---------------------- Comment (by EJFielding): I upgraded to the new @2_18_2_0 and it built with no problems after I cleaned it. Thanks! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 01:26:48 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 01:26:48 -0000 Subject: [MacPorts] #53107: py-pygrib @2.0.2 update In-Reply-To: <044.366915d58c1d778030237b2c332b9007@macports.org> References: <044.366915d58c1d778030237b2c332b9007@macports.org> Message-ID: <059.59e9b4938160669afec4272ef3d1230b@macports.org> #53107: py-pygrib @2.0.2 update ------------------------+---------------------- Reporter: ForTozs | Owner: jswhit Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: py-pygrib | ------------------------+---------------------- Comment (by EJFielding): Applying the attached patch to /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/python /py-pygrib/Portfile fixes the build problem. Thanks! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 01:38:51 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 01:38:51 -0000 Subject: [MacPorts] #51884: sudo port -v selfupdate not working In-Reply-To: <065.1a3bb7a25ed214c0f8477c9f0cf7a9cd@macports.org> References: <065.1a3bb7a25ed214c0f8477c9f0cf7a9cd@macports.org> Message-ID: <080.eda29122d88032c55bfbe1617bb463e0@macports.org> #51884: sudo port -v selfupdate not working -----------------------------------+-------------------------------- Reporter: vidyapriyadarshini@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.3.4 Resolution: invalid | Keywords: Port: | -----------------------------------+-------------------------------- Changes (by kurthindenburg): * cc: khindenburg (added) * status: new => closed * resolution: => invalid Comment: closing for now - reopen if you still have issues and think it is macports related. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 01:46:24 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 01:46:24 -0000 Subject: [MacPorts] #53090: py-pyqt* multiple Qt depspecs In-Reply-To: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> References: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> Message-ID: <056.c3e68d2bf88a221330cef5c945136c21@macports.org> #53090: py-pyqt* multiple Qt depspecs --------------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: reopened Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: py-pyqt4 py-pyqt5 | --------------------------------+---------------------- Changes (by netgamer7): * status: closed => reopened * resolution: fixed => Comment: is reopening this appropriate? Please let me know if not, and I won't do this again if something is broken. @rjvb 's fix works for me. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 01:59:13 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 01:59:13 -0000 Subject: [MacPorts] #53123: botan links against libstdc++ on 10.6 with libcxx, preventing qca from building. And workaround. Message-ID: <042.c6ed3875ce93ad7a203783ef4a68231d@macports.org> #53123: botan links against libstdc++ on 10.6 with libcxx, preventing qca from building. And workaround. --------------------+------------------- Reporter: kencu | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: botan --------------------+------------------- on systems upgraded with [wiki:LibcxxOnOlderSystems] upgrading qca will likely fail as it did here: {{{ :info:build [ 38%] Linking CXX shared module ../../lib/qca/crypto/libqca- botan.dylib :info:build cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_qca/qca/work/build/plugins /qca-botan && /opt/local/bin/cmake -E cmake_link_script CMakeFiles/qca- botan.dir/link.txt --verbose=ON :info:build /opt/local/bin/clang++-mp-3.7 -pipe -Os -DNDEBUG -stdlib=libc++ -arch x86_64 -mmacosx-version-min=10.6 -bundle -Wl,-headerpad_max_install_names -L/opt/local/lib -Wl,-headerpad_max_install_names -o ../../lib/qca/crypto/libqca- botan.dylib CMakeFiles/qca-botan.dir/qca-botan.cpp.o -Wl,-rpath,/opt/local/lib /opt/local/libexec/qt4/lib/libQtCore.dylib ../../lib/libqca.2.1.0.dylib -L/opt/local/lib -lbotan-1.10 -lbz2 -lcrypto -lpthread -lz /opt/local/libexec/qt4/lib/libQtCore.dylib -framework Carbon -framework Security :info:build Undefined symbols for architecture x86_64: :info:build "Botan::get_cipher(std::__1::basic_string, std::__1::allocator > const&, Botan::OctetString const&, Botan::Cipher_Dir)", referenced from: :info:build BotanCipherContext::setup(QCA::Direction, QCA::SymmetricKey const&, QCA::InitializationVector const&) in qca- botan.cpp.o :info:build "Botan::get_cipher(std::__1::basic_string, std::__1::allocator > const&, Botan::OctetString const&, Botan::OctetString const&, Botan::Cipher_Dir)", referenced from: :info:build BotanCipherContext::setup(QCA::Direction, QCA::SymmetricKey const&, QCA::InitializationVector const&) in qca- botan.cpp.o :info:build "Botan::OctetString::change(std::__1::basic_string, std::__1::allocator > const&)", referenced from: :info:build Botan::OctetString::OctetString(std::__1::basic_string, std::__1::allocator > const&) in qca- botan.cpp.o :info:build "Botan::block_size_of(std::__1::basic_string, std::__1::allocator > const&)", referenced from: :info:build BotanCipherContext::blockSize() const in qca-botan.cpp.o :info:build "Botan::Algorithm_Factory::prototype_mac(std::__1::basic_string, std::__1::allocator > const&, std::__1::basic_string, std::__1::allocator > const&)", referenced from: :info:build BotanCipherContext::keyLength() const in qca-botan.cpp.o :info:build "Botan::Algorithm_Factory::make_hash_function(std::__1::basic_string, std::__1::allocator > const&, std::__1::basic_string, std::__1::allocator > const&)", referenced from: :info:build BotanHashContext::BotanHashContext(QString const&, QCA::Provider*, QString const&) in qca-botan.cpp.o :info:build BotanHMACContext::BotanHMACContext(QString const&, QCA::Provider*, QString const&) in qca-botan.cpp.o :info:build "Botan::Algorithm_Factory::prototype_block_cipher(std::__1::basic_string, std::__1::allocator > const&, std::__1::basic_string, std::__1::allocator > const&)", referenced from: :info:build BotanCipherContext::keyLength() const in qca-botan.cpp.o :info:build "Botan::Algorithm_Factory::prototype_stream_cipher(std::__1::basic_string, std::__1::allocator > const&, std::__1::basic_string, std::__1::allocator > const&)", referenced from: :info:build BotanCipherContext::keyLength() const in qca-botan.cpp.o :info:build "Botan::LibraryInitializer::initialize(std::__1::basic_string, std::__1::allocator > const&)", referenced from: :info:build botanProvider::init() in qca-botan.cpp.o :info:build "Botan::get_pbkdf(std::__1::basic_string, std::__1::allocator > const&)", referenced from: :info:build BotanPBKDFContext::BotanPBKDFContext(QString const&, QCA::Provider*, QString const&) in qca-botan.cpp.o :info:build ld: symbol(s) not found for architecture x86_64 }}} the problem is not in qca, but in the library it's trying to link against, botan. It has built against libstdc++, instead of libc++. {{{ $ otool -L /opt/local/lib/libbotan-1.10.dylib /opt/local/lib/libbotan-1.10.dylib: /opt/local/lib/libbotan-1.10.dylib.0 (compatibility version 0.0.0, current version 0.0.0) /opt/local/lib/libbz2.1.0.dylib (compatibility version 1.0.0, current version 1.0.6) /opt/local/lib/libcrypto.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.11) /opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.8) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0) }}} The fix, as always, is to get `-stdlib=libc++` onto the build line. Usually this happens automagically, but looking over the Portfile for botan, you can see there are some nonstandard things done to get it to work. There are different ways you might do that, but one way is to add it to the build.args line in the botan portfile. In this case, I'm just building x86_64, so it can go here: {{{ x86_64 { build.args CXX="${configure.cxx} -m64 -stdlib=libc++" } }}} no doubt, there is a better way to do it. Then, force a rebuild of botan `sudo port -v -n upgrade --force botan` which will now hopefully build against libc++, and it does: {{{ $ otool -L /opt/local/lib/libbotan-1.10.dylib /opt/local/lib/libbotan-1.10.dylib: /opt/local/lib/libbotan-1.10.dylib.0 (compatibility version 0.0.0, current version 0.0.0) /opt/local/lib/libbz2.1.0.dylib (compatibility version 1.0.0, current version 1.0.6) /opt/local/lib/libcrypto.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.11) /opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.8) /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 3.9.0) /usr/lib/libc++abi.dylib (compatibility version 1.0.0, current version 3.9.0) }}} and then the upgrade of qca can proceed, without further link errors: {{{ $ port -v installed | grep qca qca @2.1.0_3+qt4 platform='darwin 10' archs='x86_64' qca @2.1.0_4 (active) platform='darwin 10' archs='x86_64' }}} hope this helps someone. This is the second time I've come across this issue in as many days... I wonder if there could be a more generic fix for this, such as adding something like this somewhere where it will be found widely... {{{ CXX="${configure.cxx} -stdlib=libc++" }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 02:01:48 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 02:01:48 -0000 Subject: [MacPorts] #51991: Update ocaml zarith to 1.4.1 In-Reply-To: <073.3baca53d356e7a7673f6195cf994dbae@macports.org> References: <073.3baca53d356e7a7673f6195cf994dbae@macports.org> Message-ID: <088.2e37989e2b8b9075a0e1bf9fed332fa6@macports.org> #51991: Update ocaml zarith to 1.4.1 -------------------------------------------+-------------------- Reporter: louis.granboulan.developer@… | Owner: mww@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: ocaml-zarith | -------------------------------------------+-------------------- Changes (by kurthindenburg): * status: new => closed * resolution: => fixed Comment: In [changeset:"ae81c668093b56cc220726e69154fa6f73e23f2d/macports-ports" ae81c668/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="ae81c668093b56cc220726e69154fa6f73e23f2d" ocaml-zarith: update to 1.4.1 closes https://trac.macports.org/ticket/51991 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 06:42:31 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 06:42:31 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.c34d68b9e4eaf87929c1b49d2eb85107@macports.org> #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Comment (by mojca): I don't understand how this was supposed to fix the problem. (And the builds on the buildbot still fail.) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 07:58:06 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 07:58:06 -0000 Subject: [MacPorts] #53124: Update Julia to version 0.5 Message-ID: <045.fc17f67b995cc13ab11a9440273f871f@macports.org> #53124: Update Julia to version 0.5 ----------------------+----------------- Reporter: manuSrep | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: ----------------------+----------------- Please update Julia to the current version. Thanks Manuel -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 08:34:11 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 08:34:11 -0000 Subject: [MacPorts] #53019: mogenerator: update to v1.31 In-Reply-To: <050.8a174741fb7e44432b228be9a4819fd2@macports.org> References: <050.8a174741fb7e44432b228be9a4819fd2@macports.org> Message-ID: <065.e81ad3c35cda8f79c80542f27cd1638f@macports.org> #53019: mogenerator: update to v1.31 ----------------------------+------------------------------- Reporter: steventondeur | Owner: public+macports@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: mogenerator | ----------------------------+------------------------------- Changes (by g5pw): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"a8560584ef98845ee884a14564ec9a8cbf481c2f/macports-ports" a8560584/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="a8560584ef98845ee884a14564ec9a8cbf481c2f" devel/mogenerator: update to 1.31 Maintainer timeout, Closes: https://trac.macports.org/ticket/53019 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 08:52:10 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 08:52:10 -0000 Subject: [MacPorts] #53125: Clarify the difference between eigen3 and eigen3-devel Message-ID: <041.2e98dad885d2df9e1b7576ce8f82258b@macports.org> #53125: Clarify the difference between eigen3 and eigen3-devel -------------------------+-------------------- Reporter: ksze | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: eigen3 -------------------------+-------------------- `eigen3-devel` is a sub-port of `eigen3`, and the two ports conflict each other. However, their descriptions are exactly the same. What's the difference between the two? I would presume `eigen3-devel` is a development version, but does that mean it would be built without optimizations or with debug symbols? The description does not say. Please clarify in the port description. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 08:53:51 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 08:53:51 -0000 Subject: [MacPorts] #53126: opencv @3.1.0_8 +avx2 +contrib +eigen +gdal +opencl +java +python27 +python35 +qt5 +tbb fails to build Message-ID: <041.3f35f94de3ddb392dfa4b95fae6a35b8@macports.org> #53126: opencv @3.1.0_8 +avx2 +contrib +eigen +gdal +opencl +java +python27 +python35 +qt5 +tbb fails to build --------------------+-------------------- Reporter: ksze | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: build | Port: opencv --------------------+-------------------- * macOS Sierra 10.12.2 * Xcode 8.2.1 * Command Line Tools (macOS Sierra version 10.12.2) for Xcode (version 8.2) * MacPorts 2.3.5 Just like that title says. `opencv @3.1.0_8` with those variants specified fails to build. Build log attached. Note that although the build log alludes to syntax errors in eigen3 headers, building with just `+eigen` (and none of the other variants) actually works fine. In case it's relevant, I have `eigen3 @3.3.1_0+blas+clang39+gfortran` installed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 08:54:35 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 08:54:35 -0000 Subject: [MacPorts] #53126: opencv @3.1.0_8 +avx2 +contrib +eigen +gdal +opencl +java +python27 +python35 +qt5 +tbb fails to build In-Reply-To: <041.3f35f94de3ddb392dfa4b95fae6a35b8@macports.org> References: <041.3f35f94de3ddb392dfa4b95fae6a35b8@macports.org> Message-ID: <056.7401e1c3c064c905c21bda51bc865d09@macports.org> #53126: opencv @3.1.0_8 +avx2 +contrib +eigen +gdal +opencl +java +python27 +python35 +qt5 +tbb fails to build ---------------------+------------------- Reporter: ksze | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: build Port: opencv | ---------------------+------------------- Changes (by ksze): * Attachment "main.log" added. Build log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 08:55:20 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 08:55:20 -0000 Subject: [MacPorts] #53065: QGIS @2.18.0 build failure In-Reply-To: <047.acd0aebce4f8fa360df821a9edae7ed0@macports.org> References: <047.acd0aebce4f8fa360df821a9edae7ed0@macports.org> Message-ID: <062.fa800f7e38ebad565db09a725a02ff10@macports.org> #53065: QGIS @2.18.0 build failure -------------------------+-------------------- Reporter: BuddyVolly | Owner: Veence Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: QGIS | -------------------------+-------------------- Changes (by Veence): * status: assigned => closed * resolution: => fixed Comment: Replying to [comment:9 BuddyVolly]: > Dear Vincent, > you know, in heaven, there must be a magical place for guys like you! For me it works. I’m not sure I deserve a place in paradise for such a small thing, but I’m happy it made your day. Take care and merry Xmas to both. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:11 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:11 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.14206debd2851365927c4a3756cd21cb@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"0e51d256cc58b11a6019c0026e9153c29a18f4d2/macports-ports" 0e51d256/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="0e51d256cc58b11a6019c0026e9153c29a18f4d2" arm-elf-binutils: upgrade to 2.27 License is part of the PortGroup and not needed here. See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:11 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:11 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.d43fa06ef760719e736eb289298ffe20@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"51b0f70bbccafd833a7dae62bd0fb6688c5ea04c/macports-ports" 51b0f70b/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="51b0f70bbccafd833a7dae62bd0fb6688c5ea04c" arm-none-eabi-binutils: upgrade to 2.27 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:12 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:12 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.62862ab69b33838d4141da70b0c2428b@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"51b0f70bbccafd833a7dae62bd0fb6688c5ea04c/macports-ports" 51b0f70b/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="51b0f70bbccafd833a7dae62bd0fb6688c5ea04c" arm-none-eabi-binutils: upgrade to 2.27 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:12 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:12 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.9c6226b12d432e89165afd4803aecefe@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"218cd7b42524e6f406da6c0307fe8c446ba27520/macports-ports" 218cd7b4/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="218cd7b42524e6f406da6c0307fe8c446ba27520" x86_64-elf-binutils: upgrade to 2.27 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:09 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:09 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.302b07f8913d62b726695ccd4498ed3c@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"87373c8707416cd7deed7af427921ea7d646cc9e/macports-ports" 87373c87/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="87373c8707416cd7deed7af427921ea7d646cc9e" crossbinutils-1.0: move libiberty header Fix location of ${prefix}/include/libiberty/*.h that caused conflicts in *-binutils ports. See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:09 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:09 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.3a2f04f2683f9a245f90bc42f7e01d36@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"86b7e10f0bf1c8b5083dd68cde11a269bae3d4b0/macports-ports" 86b7e10f/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="86b7e10f0bf1c8b5083dd68cde11a269bae3d4b0" arm-aout-binutils: upgrade to 2.27 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:09 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:09 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.9e9fcb2dde342b96783fda6b76cf2154@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"86b7e10f0bf1c8b5083dd68cde11a269bae3d4b0/macports-ports" 86b7e10f/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="86b7e10f0bf1c8b5083dd68cde11a269bae3d4b0" arm-aout-binutils: upgrade to 2.27 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:10 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:10 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.a611383aa54a9c9a7442032074f97b80@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"052712f9f362d3de0f91ffc0eab02e90e49cc409/macports-ports" 052712f9/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="052712f9f362d3de0f91ffc0eab02e90e49cc409" avr-binutils: remove libiberty patch, revbump * Remove $Id$ line. * Patch for libiberty is no longer needed, but we need a revbump. See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:10 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:10 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.9ec645596a49941572beb4a5ed105a69@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"ac2c4a0fd67c793876bb6ed7620ccc33278e898a/macports-ports" ac2c4a0f/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="ac2c4a0fd67c793876bb6ed7620ccc33278e898a" spu-binutils: upgrade to 2.27 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:10 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:10 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.b5121b207d55c07d462eedcbb759a312@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"ac2c4a0fd67c793876bb6ed7620ccc33278e898a/macports-ports" ac2c4a0f/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="ac2c4a0fd67c793876bb6ed7620ccc33278e898a" spu-binutils: upgrade to 2.27 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:10 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:10 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.30c86a08ace11f516bd2a0296457890d@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"45f441f59958a82dd72a632e489bd0851acea2ac/macports-ports" 45f441f5/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="45f441f59958a82dd72a632e489bd0851acea2ac" ppc-linux-binutils: upgrade to 2.27 Patches no longer needed (included upstream). See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:10 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:10 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.501199aa2e65acda598124a46e13494b@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"45f441f59958a82dd72a632e489bd0851acea2ac/macports-ports" 45f441f5/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="45f441f59958a82dd72a632e489bd0851acea2ac" ppc-linux-binutils: upgrade to 2.27 Patches no longer needed (included upstream). See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:10 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:10 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.94d1a715c182c2f54fc5c794e5a1e528@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"0e51d256cc58b11a6019c0026e9153c29a18f4d2/macports-ports" 0e51d256/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="0e51d256cc58b11a6019c0026e9153c29a18f4d2" arm-elf-binutils: upgrade to 2.27 License is part of the PortGroup and not needed here. See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:12 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:12 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.9938b7255092582d7897c4a4a528fe52@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"218cd7b42524e6f406da6c0307fe8c446ba27520/macports-ports" 218cd7b4/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="218cd7b42524e6f406da6c0307fe8c446ba27520" x86_64-elf-binutils: upgrade to 2.27 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:12 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:12 -0000 Subject: [MacPorts] #53027: binutils: libiberty installed to $prefix/include, conflicts in ports In-Reply-To: <042.21ff840f0fef05e892d836e1deca028c@macports.org> References: <042.21ff840f0fef05e892d836e1deca028c@macports.org> Message-ID: <057.3b7eb11f425bc6fc9f189e2f8650fd16@macports.org> #53027: binutils: libiberty installed to $prefix/include, conflicts in ports -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-rtems-binutils | i960-rtems-binutils lm32-rtems-binutils m68k- | elf-binutils m68k-rtems-binutils mips-elf- | binutils mips-rtems-binutils mipsel-linux- | binutils msp430-binutils powerpc-rtems- | binutils ppc-linux-binutils sh-rtems-binutils | sparc-rtems-binutils spu-binutils x86_64-elf- | binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"07cded638db076b83b020486a7fb4ce5b54a17c1/macports-ports" 07cded63/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="07cded638db076b83b020486a7fb4ce5b54a17c1" i386-elf-binutils: upgrade to 2.27 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:12 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:12 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.f5fb434e5fea8b746253657e1598f730@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"07cded638db076b83b020486a7fb4ce5b54a17c1/macports-ports" 07cded63/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="07cded638db076b83b020486a7fb4ce5b54a17c1" i386-elf-binutils: upgrade to 2.27 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53027 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:13 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:13 -0000 Subject: [MacPorts] #40174: MinGW-w64: add win64 cross-compiler In-Reply-To: <059.6f05edcab273d7fe0bf88ffe97aec928@macports.org> References: <059.6f05edcab273d7fe0bf88ffe97aec928@macports.org> Message-ID: <074.8610b34a9bfbd311bc4c55ccac28b922@macports.org> #40174: MinGW-w64: add win64 cross-compiler -------------------------------------------------+------------------------- Reporter: sam.halliday@… | Owner: mojca Type: request | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: mingw-w64 i686-w64-mingw32-gcc | x86_64-w64-mingw32-gcc | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"e2e60373506a2a4854095c2bfda51422a35a91c0/macports-ports" e2e60373/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="e2e60373506a2a4854095c2bfda51422a35a91c0" {i686|x86_64}-w64-mingw32-binutils: new ports Closes: https://trac.macports.org/ticket/13606 See: https://trac.macports.org/ticket/40174 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:13 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:13 -0000 Subject: [MacPorts] #13606: New cross/x86_64-pc-mingw32-binutils port In-Reply-To: <064.be87212c54e36dd7f12a7c084694b2c3@macports.org> References: <064.be87212c54e36dd7f12a7c084694b2c3@macports.org> Message-ID: <079.ea44242dd6ee2a7ccb4f01b83d3a3621@macports.org> #13606: New cross/x86_64-pc-mingw32-binutils port -------------------------------------+------------------------------------- Reporter: jljusten macports@… | Owner: mojca Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: cross mingw x86_64 x64 Port: i386-mingw32-binutils, | binutils mingw-w64 | -------------------------------------+------------------------------------- Comment (by mojca): In [changeset:"e2e60373506a2a4854095c2bfda51422a35a91c0/macports-ports" e2e60373/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="e2e60373506a2a4854095c2bfda51422a35a91c0" {i686|x86_64}-w64-mingw32-binutils: new ports Closes: https://trac.macports.org/ticket/13606 See: https://trac.macports.org/ticket/40174 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:13 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:13 -0000 Subject: [MacPorts] #46507: QtCurve update with support for Qt5 In-Reply-To: <041.a4bd6944c8c9acbfeb8df11e1b349a18@macports.org> References: <041.a4bd6944c8c9acbfeb8df11e1b349a18@macports.org> Message-ID: <056.3c59513d97829c0a2605e3f575213b13@macports.org> #46507: QtCurve update with support for Qt5 --------------------------+--------------------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch maintainer Port: QtCurve | --------------------------+--------------------------------- Comment (by mkae): In [changeset:"eb318efab6ce493951cb5c0566c3e13a664316cd/macports-ports" eb318efa/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="eb318efab6ce493951cb5c0566c3e13a664316cd" qtcurve: New subport qtcurve-extra + patch for KCM Upstreamed patch to prevent the killTimer warning when changing styles via the styles KCM. Fixed the GTk2 theme upstream. Ship Mac-appropriate kdeglobals file for this theme. Code cleanup & introduction of a libcxx variant for 10.6 (and earlier). qtcurve{,-qt5,-gtk2}: revive function that scans for system-wide config file. qtcurve-extra: install a system-wide config file (stylerc) that provides a Mac-like look. Deactivate config pages that don't make sense on OS X and/or don't work properly anywhere. qtcurve-qt5: Adapt to the new cmake.install_rpath syntax. qtcurve : Add a setting to use a non-native ("in-window") menubar with select applications; incorporated upstream. qtcurve(-qt5): Implements qt4 & qt5 UIs and previews for the onlyTicksInMenu feature which was incorporated upstream. Another upstreamed fix that prevents the well-known menu-rendering glitch under Qt4 (happened also with qtcurve when popup menus were rounded). D-Bus patching. The Qt5 subport is "KF5-ready" but will install as +qtonly by default until the required KF5 dependencies are available in MacPorts. Closes: https://trac.macports.org/ticket/46507 Closes: #7 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:14 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:14 -0000 Subject: [MacPorts] #53042: gnuradio @3.7.10.1_1 install fails on Snow Leopard due to undeclared long long math prototypes - and fix In-Reply-To: <042.83f707075941558260948d2d3f3e7ca4@macports.org> References: <042.83f707075941558260948d2d3f3e7ca4@macports.org> Message-ID: <057.f504514ec166dccad721a53fbfd21db0@macports.org> #53042: gnuradio @3.7.10.1_1 install fails on Snow Leopard due to undeclared long long math prototypes - and fix -----------------------+------------------------- Reporter: kencu | Owner: michaelld Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: snowleopard Port: gnuradio | -----------------------+------------------------- Comment (by michaelld): In [changeset:"b7a93dbac8ac78e0725d35dd7f47a60e90e6d710/macports-ports" b7a93dba/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="b7a93dbac8ac78e0725d35dd7f47a60e90e6d710" gnuradio: update devel to 0ec18440 (20161210); remove $id$ line; add patch to fix building on 10.6 Snow Leopard due to missing function prototype, which addresses ticket https://trac.macports.org/ticket/53042 . }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:14 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:14 -0000 Subject: [MacPorts] #53052: Homebank @5.1.2 updating a port to a newer upstream version In-Reply-To: <044.8ba0eb9389d23fa485124fe651dee17b@macports.org> References: <044.8ba0eb9389d23fa485124fe651dee17b@macports.org> Message-ID: <059.78d417552d067a64b6b977ca9043ac49@macports.org> #53052: Homebank @5.1.2 updating a port to a newer upstream version -----------------------+--------------------------------- Reporter: sibador | Owner: ryandesign Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch maintainer Port: homebank | -----------------------+--------------------------------- Comment (by ryandesign): In [changeset:"ac5a46021e3e0277614e5ada8b52759cebdadd3c/macports-ports" ac5a4602/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="ac5a46021e3e0277614e5ada8b52759cebdadd3c" homebank: Update to 5.1.2 Closes: https://trac.macports.org/ticket/53052 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:14 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:14 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.5cb081719b9641c3d0b3e13bdf875d85@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"feb6c72d77816abfebe7b62707488ef682a4eda6/macports-ports" feb6c72d/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="feb6c72d77816abfebe7b62707488ef682a4eda6" mips-elf-binutils: upgrade to 2.27, use portgroup * Upgrade to binutils 2.27 * Add the crossbinutils portgroup * Patch is no longer needed See: https://trac.macports.org/ticket/51935 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:14 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:14 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.ef31594a0c5eae93115af0474264c61e@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"60d740bbe5ca57c84de4d52dfb63f1493e236ea6/macports-ports" 60d740bb/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="60d740bbe5ca57c84de4d52dfb63f1493e236ea6" m68k-elf-binutils: upgrade to 2.27, use portgroup * Upgrade to binutils 2.27 * Add the crossbinutils portgroup * Patch is no longer needed See: https://trac.macports.org/ticket/51935 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:14 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:14 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.abf3c22e01bfd2dc4d0d802b7a7f4f55@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"6b583ace0e7ca4921433a70a9f235e57c54acdd1/macports-ports" 6b583ace/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="6b583ace0e7ca4921433a70a9f235e57c54acdd1" arm-none-linux-gnueabi-binutils: upgrade to 2.27 * Upgrade to binutils 2.27 * Add the crossbinutils portgroup * Patch is no longer needed * Maintainer timeout See: https://trac.macports.org/ticket/51935 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:14 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:14 -0000 Subject: [MacPorts] #53046: editors/neovim: please update to 0.1.7 (released Nov 27) In-Reply-To: <039.10a4f815af396149e4935bf28477d027@macports.org> References: <039.10a4f815af396149e4935bf28477d027@macports.org> Message-ID: <054.83c5970e93589759f13898d5389349b1@macports.org> #53046: editors/neovim: please update to 0.1.7 (released Nov 27) ---------------------+-------------------- Reporter: jf | Owner: raimue Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: neovim | ---------------------+-------------------- Comment (by raimue): In [changeset:"391e33036addf570417db8e0800efacab932e7d5/macports-ports" 391e3303/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="391e33036addf570417db8e0800efacab932e7d5" neovim: Update to version 0.1.7 Closes: https://trac.macports.org/ticket/53046 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:14 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:14 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.54533c90f3c9537b40a0819710bb211a@macports.org> #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): In [changeset:"7ea864453d4e0eb23e168215a183c492f408c83a/macports-ports" 7ea8644/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="7ea864453d4e0eb23e168215a183c492f408c83a" octave: use compiler that works for OS and cxx_stdlib values For a full build, octave requires a C++11 compatible compiler with the same standard library (libc++ or libstdc++) as its dependencies. See https://trac.macports.org/ticket/53044 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:15 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:15 -0000 Subject: [MacPorts] #50500: simpler up-to-date qca Port allowing concurrent Qt4 and Qt5 installations In-Reply-To: <041.5a8cf720b2316dc3a82d28ba5f1c267c@macports.org> References: <041.5a8cf720b2316dc3a82d28ba5f1c267c@macports.org> Message-ID: <056.51c0499a29d835aaf3647168a9d5a465@macports.org> #50500: simpler up-to-date qca Port allowing concurrent Qt4 and Qt5 installations ---------------------+-------------------------------- Reporter: RJVB | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: qca | ---------------------+-------------------------------- Comment (by RJVB): In [changeset:"6d430c18e48fbcdb25584500ef0e027d3e5610e5/macports-ports" 6d430c18/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="6d430c18e48fbcdb25584500ef0e027d3e5610e5" port:qca* : proposed adoption and introduction of Qt5 subports The QCA ports have been without maintainer for a bit now, and lack the possibility to install for Qt4 and Qt5 concurrently. That possibility is essential for the future KF5 ports, so I propose that Marko and I adopt this port and introduce the required changes. The ports as defined by the current Portfile have seen thorough testing by both of us as well as by a few "beta testers" of my KF5 ports. I don't think there is any point in maintaining the Qt4 and Qt5 variants. The current version also introduces a few changes that are unrelated to Qt5/KF5 but aim to simplify dependencies by reducing the number of subports. This is open for discussion w.r.t. the Qt4 versions. I don't think there is much justification (for use with MacPorts) to build QCA as a framework, but this could be reintroduced as a variant. Closes: #59 Closes: https://trac.macports.org/ticket/50500 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:15 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:15 -0000 Subject: [MacPorts] #53054: vcsn @2.2: update to 2.4 In-Reply-To: <042.8c0aba0378d281d075c02dee4fd8e96e@macports.org> References: <042.8c0aba0378d281d075c02dee4fd8e96e@macports.org> Message-ID: <057.b1c1e54e71aece44a5d971670bd282cf@macports.org> #53054: vcsn @2.2: update to 2.4 ---------------------+--------------------------------- Reporter: akimd | Owner: larryv Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch maintainer Port: vcsn | ---------------------+--------------------------------- Comment (by akimd): In [changeset:"81c3d88c92145942ebebb4ba92807771d725c7dc/macports-ports" 81c3d88c/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="81c3d88c92145942ebebb4ba92807771d725c7dc" vcsn: Update to 2.4, switch to Python 3.5 Closes: https://trac.macports.org/ticket/53054 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:15 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:15 -0000 Subject: [MacPorts] #46558: phonon-backend-gstreamer update to 4.8.2 and qt5 support In-Reply-To: <041.71a41150aa5e01a45a493a76643c7c35@macports.org> References: <041.71a41150aa5e01a45a493a76643c7c35@macports.org> Message-ID: <056.cb04447669f463bdab3b235dd06f3e4a@macports.org> #46558: phonon-backend-gstreamer update to 4.8.2 and qt5 support ---------------------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: phonon-backend-gstreamer | ---------------------------------------+---------------------- Comment (by mkae): In [changeset:"414fbb185ce8d5cb66fa3fb10d48370f85aca848/macports-ports" 414fbb18/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="414fbb185ce8d5cb66fa3fb10d48370f85aca848" phonon-backend-gstreamer(-qt5): update to 4.9.0 and introduce new subport Squash commit: commit 5084c0bb0f4edef8ad380910182fad25a5c203f8 Author: Marko Käning Date: Tue Dec 13 04:51:38 2016 +0100 phonon-backend-gstreamer-qt5: michaelld drops maintainership commit 848cd25de1d3fa80eab96d6b5aa4d7deb9cb513f Author: Marko Käning Date: Tue Dec 13 04:47:21 2016 +0100 phonon-backend-gstreamer(-qt5): master_sites's folder changed for 4.9.0 commit 909946083acb91e66b8d88a489773ba066e6954e Author: Marko Käning Date: Tue Dec 13 04:31:20 2016 +0100 phonon-backend-gstreamer: update to 4.9.0 - avoiding building the X11 renderer has changed => new patch - remove unused patches commit ccaa0e34a4aa2fafc8276a6fb8d86fa8af7398a2 Author: Marko Käning Date: Tue Dec 13 03:09:55 2016 +0100 phonon-backend-gstreamer: introduce qt5 support - add co-maintainership for RJVB Closes: https://trac.macports.org/ticket/46558 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:15 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:15 -0000 Subject: [MacPorts] #52951: wxWidgets-3.2 does not build In-Reply-To: <045.5ccbbc3b9cc1ea7e021e5dbb885d68cb@macports.org> References: <045.5ccbbc3b9cc1ea7e021e5dbb885d68cb@macports.org> Message-ID: <060.899a02a1d2a6566da8f4a611f8c6e541@macports.org> #52951: wxWidgets-3.2 does not build ----------------------------+-------------------- Reporter: rkitover | Owner: mojca Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: sierra Port: wxWidgets-3.2 | ----------------------------+-------------------- Comment (by mojca): In [changeset:"d26da196a3a32933b123853454643c8206522d8e/macports-ports" d26da196/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="d26da196a3a32933b123853454643c8206522d8e" wxWidgets-3.2: upgrade to commit 159186d from git * Use commit 159186d (2016-12-12) from master to add support for newer platforms without extensive patching. * Remove two patches from upstream. Closes: https://trac.macports.org/ticket/52951 See: https://github.com/wxWidgets/wxWidgets/pull/370 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:15 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:15 -0000 Subject: [MacPorts] #53059: octave-audio @1.1.4: patchfile patch-objcflags.diff is missing In-Reply-To: <050.a1ae3ff9782c98acde09c42ac011f456@macports.org> References: <050.a1ae3ff9782c98acde09c42ac011f456@macports.org> Message-ID: <065.4001cb27dbfda199a5ce8c960bbc1197@macports.org> #53059: octave-audio @1.1.4: patchfile patch-objcflags.diff is missing ----------------------------+--------------------------------- Reporter: gjolleyrogers | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: octave-audio | ----------------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): In [changeset:"eb8e32078deca5dcf5335efce0aedd4edb323121/macports-ports" eb8e3207/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="eb8e32078deca5dcf5335efce0aedd4edb323121" octave-audio: add missing patchfile Fixes https://trac.macports.org/ticket/53059 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:15 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:15 -0000 Subject: [MacPorts] #53041: p5-xml-twig: update to version 3.52 In-Reply-To: <044.4f82598ac31c02610396d014082d8f12@macports.org> References: <044.4f82598ac31c02610396d014082d8f12@macports.org> Message-ID: <059.a53f8f409b170aa21ebee86373637a4c@macports.org> #53041: p5-xml-twig: update to version 3.52 --------------------------+------------------------------- Reporter: dbevans | Owner: frank.mcpherson@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: p5-xml-twig | --------------------------+------------------------------- Comment (by dbevans): In [changeset:"906abba9ea647b8157025d295e98d5fd2d23331b/macports-ports" 906abba9/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="906abba9ea647b8157025d295e98d5fd2d23331b" p5-xml-twig: update to version 3.52 Remove outdated Id tag line and comment. Maintainer timeout. Closes: https://trac.macports.org/ticket/53041 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:15 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:15 -0000 Subject: [MacPorts] #40174: MinGW-w64: add win64 cross-compiler In-Reply-To: <059.6f05edcab273d7fe0bf88ffe97aec928@macports.org> References: <059.6f05edcab273d7fe0bf88ffe97aec928@macports.org> Message-ID: <074.d015c6138181dd291c733537152bc9aa@macports.org> #40174: MinGW-w64: add win64 cross-compiler -------------------------------------------------+------------------------- Reporter: sam.halliday@… | Owner: mojca Type: request | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: mingw-w64 i686-w64-mingw32-gcc | x86_64-w64-mingw32-gcc | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"f03d7616ab97d841555a16648bed837b8d54afae/macports-ports" f03d761/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="f03d7616ab97d841555a16648bed837b8d54afae" mingw-w64: new cross-compiler for Windows Following: * ${arch}-w64-mingw32-binutils this completes the cross-compiler for Windows with the following subports: * ${arch}-w64-mingw32-headers * ${arch}-w64-mingw32-crt * ${arch}-w64-mingw32-gcc-bootstrap * ${arch}-w64-mingw32-gcc with `arch=i686|x86_64`. The first two ports come from the MinGW-w64 project, while GCC is compiled from original GCC sources. The `*-gcc-bootstrap` port is needed to compile `*-crt` and `*-gcc` itself. Not (yet?) implemented: * support for Ada * support for pthreads-win32 & OpenMP * support for parallel installation of multiple GCC compilers Closes: https://trac.macports.org/ticket/40174 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:16 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:16 -0000 Subject: [MacPorts] #51344: seqan @2.1.1_0 Fixes installation of missing files In-Reply-To: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> References: <042.5d0a62985900b4314e3a5a84ac8d7b8e@macports.org> Message-ID: <057.4c91df6cf212abdb7cdcf9d5cace3828@macports.org> #51344: seqan @2.1.1_0 Fixes installation of missing files ---------------------+--------------------------------- Reporter: rrahn | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: haspatch maintainer Port: seqan | ---------------------+--------------------------------- Comment (by raimue): In [changeset:"7a949509d2dc33a3688af412afd844ff1f9ab798/macports-ports" 7a94950/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="7a949509d2dc33a3688af412afd844ff1f9ab798" seqan: fix installation of missing files Closes: https://trac.macports.org/ticket/51344 (maintainer) }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:16 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:16 -0000 Subject: [MacPorts] #53043: py-sphinx dependents: remove py26 and py33 In-Reply-To: <043.c9ddeb2c0ac22f69cf03bf226e020391@macports.org> References: <043.c9ddeb2c0ac22f69cf03bf226e020391@macports.org> Message-ID: <058.4ae2d16ec609ca51f7870fb67e48f3b2@macports.org> #53043: py-sphinx dependents: remove py26 and py33 -------------------------------------------------+------------------------- Reporter: jmroot | Owner: seanfarley Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: py26-hieroglyph py33-hieroglyph | py26-pydicom | -------------------------------------------------+------------------------- Comment (by jmroot): In [changeset:"6adae8f80e4ef2d5f76d7e110118cc9deb4d806c/macports-ports" 6adae8f8/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="6adae8f80e4ef2d5f76d7e110118cc9deb4d806c" py-sphinx dependents: remove 26 and 33 subports Sphinx 1.5 has dropped support for Python 2.6 and 3.3. Maintainer timeout. Closes: https://trac.macports.org/ticket/53043 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:16 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:16 -0000 Subject: [MacPorts] #38304: i386-mingw32-binutils @2.21-3_0: windres converts resource string to UTF-16 with wrong endianness, PATCH In-Reply-To: <046.c7f4ac96bb5cf0ccbd7a5c9dbc380086@macports.org> References: <046.c7f4ac96bb5cf0ccbd7a5c9dbc380086@macports.org> Message-ID: <061.a27f12168361899911ec7e79d74ac637@macports.org> #38304: i386-mingw32-binutils @2.21-3_0: windres converts resource string to UTF-16 with wrong endianness, PATCH ------------------------------------+----------------------- Reporter: tuffnatty | Owner: landonf@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: i386-mingw32-binutils | ------------------------------------+----------------------- Comment (by mojca): In [changeset:"dd6de2b3fd5bbdd49e119803dd9f282a77f2178f/macports-ports" dd6de2b3/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="dd6de2b3fd5bbdd49e119803dd9f282a77f2178f" i386-mingw32-binutils: upgrade to 2.25.1-1 * Upgrade to version 2.25.1-1 * Add license GPL-3+ * Remove `$Id$` line Closes: https://trac.macports.org/ticket/38304 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53061 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:16 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:16 -0000 Subject: [MacPorts] #53061: i386-mingw32: remove ports, replaced by i686-w64-mingw32 In-Reply-To: <042.2f80d4e0beb184bcb48851c3a692428b@macports.org> References: <042.2f80d4e0beb184bcb48851c3a692428b@macports.org> Message-ID: <057.599f63b8aff31304ce5e5187b74d0df6@macports.org> #53061: i386-mingw32: remove ports, replaced by i686-w64-mingw32 -------------------------------------------------+------------------------- Reporter: mojca | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: i386-mingw32-binutils | i386-mingw32-gcc i386-mingw32-libunicows | i386-mingw32-runtime i386-mingw32-w32api | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"dd6de2b3fd5bbdd49e119803dd9f282a77f2178f/macports-ports" dd6de2b3/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="dd6de2b3fd5bbdd49e119803dd9f282a77f2178f" i386-mingw32-binutils: upgrade to 2.25.1-1 * Upgrade to version 2.25.1-1 * Add license GPL-3+ * Remove `$Id$` line Closes: https://trac.macports.org/ticket/38304 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53061 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:16 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:16 -0000 Subject: [MacPorts] #51935: binutils: upgrade to 2.27 In-Reply-To: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> References: <042.164f82be1c71c3bfa9bf7a84f15e2c55@macports.org> Message-ID: <057.2429ac192df3d03425f9fa047111c873@macports.org> #51935: binutils: upgrade to 2.27 -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arm-aout-binutils arm-elf-binutils | arm-none-eabi-binutils arm-none-linux- | gnueabi-binutils arm-rtems-binutils avr- | binutils i386-elf-binutils | i386-mingw32-binutils i386-mingw32-binutils | i386-rtems-binutils i960-rtems-binutils lm32 | -rtems-binutils m68k-elf-binutils m68k-rtems- | binutils mips-elf-binutils mips-rtems- | binutils mipsel-linux-binutils | msp430-binutils msp430-binutils-devel | powerpc-rtems-binutils ppc-linux-binutils sh- | rtems-binutils sparc-rtems-binutils spu- | binutils x86_64-elf-binutils | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"dd6de2b3fd5bbdd49e119803dd9f282a77f2178f/macports-ports" dd6de2b3/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="dd6de2b3fd5bbdd49e119803dd9f282a77f2178f" i386-mingw32-binutils: upgrade to 2.25.1-1 * Upgrade to version 2.25.1-1 * Add license GPL-3+ * Remove `$Id$` line Closes: https://trac.macports.org/ticket/38304 See: https://trac.macports.org/ticket/51935 See: https://trac.macports.org/ticket/53061 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:17 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:17 -0000 Subject: [MacPorts] #47197: cmake-based ports: add cmake.out_of_source yes/no In-Reply-To: <042.143327c5ff7caac583f0e30b8a2e7ab1@macports.org> References: <042.143327c5ff7caac583f0e30b8a2e7ab1@macports.org> Message-ID: <057.0ea6bae6badf3e08ca98aaf804373675@macports.org> #47197: cmake-based ports: add cmake.out_of_source yes/no -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: Cockatrice Io LucenePlusPlus | OpenSceneGraph OpenSceneGraph-devel | PlasmaClient PlasmaShop TOra Vidalia allegro | allegro5 alps apbs apiextractor assimp2 | autopano-sift-c blosc bob box2d cgal charm | chemkit chipmunk choqok clucene clucene-devel | coinor-liblemon collada-dom dolfin ebook- | tools efte emergent ettercap exiv2 falcon | fann freealut freecad freecell-solver gccxml- | devel generatorrunner graphite2 indi | indi_maxdomeii json_spirit kealib libdynd | libftdi libhsplasma liblas libmsn | libmusicbrainz3 libpcl libplist libtuxcap | lua-luabitop metis mysql55-connector-cpp | newmat nifticlib nomacs oce ogre openal-soft | openbabel opencv openjpeg orocos-kdl orocos- | rtt osgswig-devel parmetis pgrouting physfs | piklab playerstage-player playerstage-stage | polkit-qt portmidi py-dynd qfsm qgis | qlandkartegt qlandkartegt-garmindev qlipper | qore-qt4-module rabbitmq-c rsgislib rspamd | scalapack scribus sdcv seqan-apps sfcgal | shogun-devel sigil soci streamlog synergy | synergy-devel sysdig tagainijisho toluapp | usbmuxd viennacl vigra vrpn vtk vtk5 vxl | wbxml2 widelands | -------------------------------------------------+------------------------- Comment (by mojca): In [changeset:"36999386ff410798c7c5b578650054b677f65be6/macports-ports" 3699938/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="36999386ff410798c7c5b578650054b677f65be6" wbxml2: upgrade to 0.11.4 * Upgrade to version 0.11.4 * Add `cmake.out_of_source yes` * Avoid installing `FindLibWbxml2.cmake` to version-dependent location `${prefix}/share/cmake-3.7/Modules/FindLibWbxml2.cmake` See: https://trac.macports.org/ticket/47197 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:17 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:17 -0000 Subject: [MacPorts] #53036: [Port New] libchewing In-Reply-To: <042.8b452ee8a9de3a161a300385f4be9866@macports.org> References: <042.8b452ee8a9de3a161a300385f4be9866@macports.org> Message-ID: <057.db4b20e2b8679be1a7def84026a204c8@macports.org> #53036: [Port New] libchewing -------------------------+-------------------- Reporter: cwlin | Owner: cwlin Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: libchewing | -------------------------+-------------------- Comment (by cwlin): In [changeset:"cf89674f39ac0a3f07966d84b4c3162bbe28c1da/macports-ports" cf89674/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="cf89674f39ac0a3f07966d84b4c3162bbe28c1da" libchewing: new port The intelligent phonetic input method library The Chewing is an intelligent phonetic (Zhuyin/Bopomofo) input method, one of the most popular choices for Traditional Chinese users. Chewing was inspired by other proprietary intelligent Zhuyin input methods under Microsoft Windows, namely, Wang-Xin by Eten, Microsoft New Zhuyin, and Nature Zhuyin. Closes: https://trac.macports.org/ticket/53036 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:17 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:17 -0000 Subject: [MacPorts] #53069: uhd +python35 build failure In-Reply-To: <041.2b7d697f3b931da26189c5328053513f@macports.org> References: <041.2b7d697f3b931da26189c5328053513f@macports.org> Message-ID: <056.bd7197ca9ffa894561edf5bd3b066710@macports.org> #53069: uhd +python35 build failure ----------------------------+----------------------- Reporter: mf2k | Owner: michaelld Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: uhd uhd-devel | ----------------------------+----------------------- Comment (by michaelld): In [changeset:"7990b2667f5597c53f36eecb3828c7f35b7385f2/macports-ports" 7990b266/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="7990b2667f5597c53f36eecb3828c7f35b7385f2" uhd: add temporary patch to fix building on Python 3.5; works with older Python too; addresses ticket https://trac.macports.org/ticket/53069 . }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:17 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:17 -0000 Subject: [MacPorts] #53079: cctools @895 does not build on a PPC running leopard In-Reply-To: <048.e4ab1f1e512b4bd19f57bb41b870c232@macports.org> References: <048.e4ab1f1e512b4bd19f57bb41b870c232@macports.org> Message-ID: <063.6fa23eee6d9d015bac749f4f276f5b3d@macports.org> #53079: cctools @895 does not build on a PPC running leopard --------------------------+------------------------- Reporter: josephsacco | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: PPC leopard Port: cctools | --------------------------+------------------------- Comment (by jeremyhu): In [changeset:"250e2336d354b8c05088504ef9e22174a7776be2/macports-ports" 250e2336/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="250e2336d354b8c05088504ef9e22174a7776be2" cctools: Address ppc build failure Fixes https://trac.macports.org/ticket/53079 Signed-off-by: Jeremy Huddleston Sequoia }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:18 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:18 -0000 Subject: [MacPorts] #53072: chromaprint @1.4.0: default build fails on 10.8 and earlier due to inclusion of C++11 header In-Reply-To: <044.a96bc61b1ea83cf3406c5aadf3f008e3@macports.org> References: <044.a96bc61b1ea83cf3406c5aadf3f008e3@macports.org> Message-ID: <059.0976e56ff1d7388f993096bb152bb425@macports.org> #53072: chromaprint @1.4.0: default build fails on 10.8 and earlier due to inclusion of C++11 header --------------------------+---------------------------- Reporter: dbevans | Owner: kurthindenburg Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: chromaprint | --------------------------+---------------------------- Comment (by dbevans): In [changeset:"3683ed1a837f78a75bc94625bb8e5ec0eea1894f/macports-ports" 3683ed1/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="3683ed1a837f78a75bc94625bb8e5ec0eea1894f" gstreamer1-gst-plugins-bad: disable chromaprint plugin if cxx_stdlib is libstdc++ chromaprint 1.4+ build requires libc++. See: https://trac.macports.org/ticket/53072 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:18 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:18 -0000 Subject: [MacPorts] #51411: mlt: qt5 subport In-Reply-To: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> References: <041.887cb907bb85690fe84bbe5f21a4d579@macports.org> Message-ID: <056.5a1af42aae4cf86547e7a4ac3d94c813@macports.org> #51411: mlt: qt5 subport --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: mlt | --------------------------+---------------------- Comment (by mkae): In [changeset:"896b35c26af9a261eeaaa0555f1181d8bd80770b/macports-ports" 896b35c2/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="896b35c26af9a261eeaaa0555f1181d8bd80770b" mlt-qt5: new port - add RJVB as co-maintainer - drop invalid keyword Id Closes: https://trac.macports.org/ticket/51411 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:18 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:18 -0000 Subject: [MacPorts] #52535: Installing libVLC fails at configure stage In-Reply-To: <053.df925bcddc583457bb7040eddda657cf@macports.org> References: <053.df925bcddc583457bb7040eddda657cf@macports.org> Message-ID: <068.7d0d86f7ba90bad99f6ba5bace5b3341@macports.org> #52535: Installing libVLC fails at configure stage -----------------------+-------------------- Reporter: rakesh@… | Owner: RJVB Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: libVLC | -----------------------+-------------------- Comment (by mkae): In [changeset:"21df8c9b5d38470b52385ee33924d5c44343bb0d/macports-ports" 21df8c9/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="21df8c9b5d38470b52385ee33924d5c44343bb0d" VLC: upgrade to 2.2.4 and provide private FFMpeg v2.8.6 - moves fluidsynth support to the base feature set and patches the fluidsynth module to find sf2 repository in ${prefix} (${prefix}/share/sounds/sf2). - works around the FFMpeg v3.x incompatibility issue by shipping a private, stripped-down FFMpeg 2.8.6 copy. Closes: #27 Closes: https://trac.macports.org/ticket/52535 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:18 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:18 -0000 Subject: [MacPorts] #51413: submission: phonon-backend-vlc with qt5 subport In-Reply-To: <041.002960c4ae3a6932302f53c42fdff330@macports.org> References: <041.002960c4ae3a6932302f53c42fdff330@macports.org> Message-ID: <056.a73cb7e72dcc08c6413d59264c686213@macports.org> #51413: submission: phonon-backend-vlc with qt5 subport -------------------------------------+-------------------- Reporter: RJVB | Owner: mkae Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: phonon-backend-vlc-qt5 | -------------------------------------+-------------------- Comment (by mkae): In [changeset:"f6d97dca55a88b81dd65ff1c3f2d580714af2b79/macports-ports" f6d97dc/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="f6d97dca55a88b81dd65ff1c3f2d580714af2b79" phonon-backend-vlc(-qt5): new (sub)ports Closes: https://trac.macports.org/ticket/51413 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:18 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:18 -0000 Subject: [MacPorts] #51620: py-pyqt5: fix DBus module build and pyversion conflicts, support multiple Qt5 ports In-Reply-To: <041.878bbad1021a18186c191e6780e8baed@macports.org> References: <041.878bbad1021a18186c191e6780e8baed@macports.org> Message-ID: <056.880b0c5459aa38c7f282ef4d92992a16@macports.org> #51620: py-pyqt5: fix DBus module build and pyversion conflicts, support multiple Qt5 ports --------------------------+-------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: py-pyqt5 | --------------------------+-------------------- Comment (by mkae): In [changeset:"0229294abfd80a5801503e086e6b67c4dfcbeb49/macports-ports" 0229294a/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="0229294abfd80a5801503e086e6b67c4dfcbeb49" py-pyqt5: fix DBus module build and pyversion conflicts - also support multiple Qt5 ports - remove invalid keyword 'Id' Closes: https://trac.macports.org/ticket/51620 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:18 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:18 -0000 Subject: [MacPorts] #52869: OpenSceneGraph: fails to build due to changes in jpeg port In-Reply-To: <041.605a25c238eb52e5ff80ed0a94ecc86d@macports.org> References: <041.605a25c238eb52e5ff80ed0a94ecc86d@macports.org> Message-ID: <056.88ccd74c254360e5170aaccd99a7997c@macports.org> #52869: OpenSceneGraph: fails to build due to changes in jpeg port -------------------------------------------------+------------------------- Reporter: mkae | Owner: macports- | tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: OpenSceneGraph OpenSceneGraph- | devel | -------------------------------------------------+------------------------- Comment (by mkae): In [changeset:"a54de1ab6029d40b16fce50285b37390b54a584c/macports-ports" a54de1ab/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="a54de1ab6029d40b16fce50285b37390b54a584c" OpenSceneGraph: introduce new patch as workaround for trouble with jpeg Closes: https://trac.macports.org/ticket/52869 See: https://github.com/openscenegraph/OpenSceneGraph/issues/58 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:19 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:19 -0000 Subject: [MacPorts] #49577: polkit-qt version update and qt5 subport In-Reply-To: <041.10c457beacec7a8439cb3cbbfa864b31@macports.org> References: <041.10c457beacec7a8439cb3cbbfa864b31@macports.org> Message-ID: <056.db1528cb513ba821f46563e4070a1587@macports.org> #49577: polkit-qt version update and qt5 subport ------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: polkit-qt | ------------------------+---------------------- Comment (by mkae): In [changeset:"70e1a6016e32067481006f83a0c60b7e0dd8a762/macports-ports" 70e1a601/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="70e1a6016e32067481006f83a0c60b7e0dd8a762" polkit-qt(5): upgrade to 0.112.0 and introduce *-qt5(-devel) subports - removed invalid keyword 'Id' Closes: https://trac.macports.org/ticket/49577 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:19 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:19 -0000 Subject: [MacPorts] #49109: port modifications required by making qt4-mac co-installable with Qt5 In-Reply-To: <041.ed916633811460a610cbd879f97870ef@macports.org> References: <041.ed916633811460a610cbd879f97870ef@macports.org> Message-ID: <056.e4a9a1e37e04da4867d355b47cdb23e5@macports.org> #49109: port modifications required by making qt4-mac co-installable with Qt5 --------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: | --------------------------+---------------------- Comment (by mkae): In [changeset:"d0ab43877132fc631002f67ce177d4435127105f/macports-ports" d0ab4387/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="d0ab43877132fc631002f67ce177d4435127105f" py-pyqt4: fix for the depends_lib reset caused by the Python PortGroup See also: https://trac.macports.org/ticket/49109 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:19 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:19 -0000 Subject: [MacPorts] #53017: kerberos5 @1.15: build fails with libressl In-Reply-To: <045.2e6d5c80e4930d3d8f0c88d93b24a25b@macports.org> References: <045.2e6d5c80e4930d3d8f0c88d93b24a25b@macports.org> Message-ID: <060.c7f3fe872ec48a42d43f246a7617cffa@macports.org> #53017: kerberos5 @1.15: build fails with libressl ------------------------+------------------------ Reporter: bK4gYuRo | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: kerberos5 | ------------------------+------------------------ Comment (by jeremyhu): In [changeset:"22190bd97e38baebf80cacc35678b23a83fa8549/macports-ports" 22190bd9/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="22190bd97e38baebf80cacc35678b23a83fa8549" kerberos5: Fix build with libressl Fixes https://trac.macports.org/ticket/53017 Signed-off-by: Jeremy Huddleston Sequoia }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:19 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:19 -0000 Subject: [MacPorts] #51413: submission: phonon-backend-vlc with qt5 subport In-Reply-To: <041.002960c4ae3a6932302f53c42fdff330@macports.org> References: <041.002960c4ae3a6932302f53c42fdff330@macports.org> Message-ID: <056.6ce97d90d206a90ade7f16e0ca23a690@macports.org> #51413: submission: phonon-backend-vlc with qt5 subport -------------------------------------+-------------------- Reporter: RJVB | Owner: mkae Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: phonon-backend-vlc-qt5 | -------------------------------------+-------------------- Comment (by mkae): In [changeset:"aa69a768623faaef4a56e3b5454175691a75a121/macports-ports" aa69a768/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="aa69a768623faaef4a56e3b5454175691a75a121" phonon-backend-vlc-qt5: update and polish See: https://trac.macports.org/ticket/51413 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:19 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:19 -0000 Subject: [MacPorts] #53083: VLC: fails to build on Sierra due to QtKit In-Reply-To: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> References: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> Message-ID: <056.0a890ed4ad31db2d2f04377a01447204@macports.org> #53083: VLC: fails to build on Sierra due to QtKit ---------------------+-------------------- Reporter: mkae | Owner: mkae Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: sierra Port: VLC | ---------------------+-------------------- Changes (by mkae): * status: reopened => closed * resolution: => fixed Comment: In [changeset:"50fa06ddc8dea37dd855129f584aacae4f81bc6e/macports-ports" 50fa06dd/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="50fa06ddc8dea37dd855129f584aacae4f81bc6e" VLC: fix build on Sierra in analogy to opencv Thanks, René, for providing a patch! Closes: https://trac.macports.org/ticket/53083 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:19 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:19 -0000 Subject: [MacPorts] #51939: python3*: backport pyport.h fix In-Reply-To: <042.1951187832923e44cd0b117494e23a5a@macports.org> References: <042.1951187832923e44cd0b117494e23a5a@macports.org> Message-ID: <057.e1be508dbe54f909b6136a581307c56c@macports.org> #51939: python3*: backport pyport.h fix -------------------------------------------------+------------------------- Reporter: Ionic | Owner: | jyrkiwahlstedt Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: python31 python32 python33 | python34 python35 | -------------------------------------------------+------------------------- Comment (by Mihai Moldovan ): In [changeset:"7285fd1ce914c9a285f702ec58db267f64e33287/macports-ports" 7285fd1c/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="7285fd1ce914c9a285f702ec58db267f64e33287" python35: backport patch from #44288. Maintainer timeout. Fixes: https://trac.macports.org/ticket/51939 Additionally, drop legacy Id line. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:19 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:19 -0000 Subject: [MacPorts] #40792: ngrep @1.45 ipv6 support In-Reply-To: <054.9ca8ea3abf0f74acaa0469790a93f016@macports.org> References: <054.9ca8ea3abf0f74acaa0469790a93f016@macports.org> Message-ID: <069.b184a778464acf76b6f5956e8be7da1b@macports.org> #40792: ngrep @1.45 ipv6 support --------------------------+--------------------- Reporter: akh@… | Owner: grace@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: fixed | Keywords: Port: ngrep | --------------------------+--------------------- Comment (by kurthindenburg): In [changeset:"4c47444afbeadc8c3e9ff40068ae8dbf5f26ba8b/macports-ports" 4c47444/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="4c47444afbeadc8c3e9ff40068ae8dbf5f26ba8b" ngrep: add various patches + use pcre - avoid sourceforge redirects - add openmaintainer for now - maintainer timeout - use macports pcre instead of ngrep's regex - use Debian's patches : ipv6, man, building, locale - enable-ipv6 closes https://trac.macports.org/ticket/40792 closes https://trac.macports.org/ticket/52840 closes https://trac.macports.org/ticket/48123 closes https://trac.macports.org/ticket/52207 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:20 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:20 -0000 Subject: [MacPorts] #52840: ngrep install issue In-Reply-To: <044.91570960171f91790181183718763f20@macports.org> References: <044.91570960171f91790181183718763f20@macports.org> Message-ID: <059.61899b907aa581a9144f8579afae7407@macports.org> #52840: ngrep install issue ----------------------+---------------------- Reporter: schnide | Owner: ​grace@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: ngrep | ----------------------+---------------------- Comment (by kurthindenburg): In [changeset:"4c47444afbeadc8c3e9ff40068ae8dbf5f26ba8b/macports-ports" 4c47444/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="4c47444afbeadc8c3e9ff40068ae8dbf5f26ba8b" ngrep: add various patches + use pcre - avoid sourceforge redirects - add openmaintainer for now - maintainer timeout - use macports pcre instead of ngrep's regex - use Debian's patches : ipv6, man, building, locale - enable-ipv6 closes https://trac.macports.org/ticket/40792 closes https://trac.macports.org/ticket/52840 closes https://trac.macports.org/ticket/48123 closes https://trac.macports.org/ticket/52207 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:20 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:20 -0000 Subject: [MacPorts] #48123: after installing ngrep, "Could not open /opt/local/lib/libpcap.A.dylib" causes rebuild on every install In-Reply-To: <054.de7bbdded19c47e0f8f46d5132cdf071@macports.org> References: <054.de7bbdded19c47e0f8f46d5132cdf071@macports.org> Message-ID: <069.6797c54a7fbdbec4e0419c38802d4e42@macports.org> #48123: after installing ngrep, "Could not open /opt/local/lib/libpcap.A.dylib" causes rebuild on every install ------------------------+--------------------- Reporter: audvare@… | Owner: grace@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: fixed | Keywords: Port: ngrep | ------------------------+--------------------- Comment (by kurthindenburg): In [changeset:"4c47444afbeadc8c3e9ff40068ae8dbf5f26ba8b/macports-ports" 4c47444/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="4c47444afbeadc8c3e9ff40068ae8dbf5f26ba8b" ngrep: add various patches + use pcre - avoid sourceforge redirects - add openmaintainer for now - maintainer timeout - use macports pcre instead of ngrep's regex - use Debian's patches : ipv6, man, building, locale - enable-ipv6 closes https://trac.macports.org/ticket/40792 closes https://trac.macports.org/ticket/52840 closes https://trac.macports.org/ticket/48123 closes https://trac.macports.org/ticket/52207 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:20 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:20 -0000 Subject: [MacPorts] #52207: ngrep @1.45: build failure with libpcap @1.8.0: no yacc restart func found In-Reply-To: <060.c76afbca202a43bf06fd7cfdfdab01d0@macports.org> References: <060.c76afbca202a43bf06fd7cfdfdab01d0@macports.org> Message-ID: <075.4ab5e89de9253050c193d6cc52ab5a9a@macports.org> #52207: ngrep @1.45: build failure with libpcap @1.8.0: no yacc restart func found -----------------------+--------------------- Reporter: marcel@… | Owner: grace@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: ngrep | -----------------------+--------------------- Comment (by kurthindenburg): In [changeset:"4c47444afbeadc8c3e9ff40068ae8dbf5f26ba8b/macports-ports" 4c47444/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="4c47444afbeadc8c3e9ff40068ae8dbf5f26ba8b" ngrep: add various patches + use pcre - avoid sourceforge redirects - add openmaintainer for now - maintainer timeout - use macports pcre instead of ngrep's regex - use Debian's patches : ipv6, man, building, locale - enable-ipv6 closes https://trac.macports.org/ticket/40792 closes https://trac.macports.org/ticket/52840 closes https://trac.macports.org/ticket/48123 closes https://trac.macports.org/ticket/52207 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:20 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:20 -0000 Subject: [MacPorts] #52845: mpv: update to 0.22 In-Reply-To: <043.e673edb81f111939a6207eb0205e5927@macports.org> References: <043.e673edb81f111939a6207eb0205e5927@macports.org> Message-ID: <058.fc8a08f242b749dfecb020007c529929@macports.org> #52845: mpv: update to 0.22 ---------------------+-------------------- Reporter: iMiKED | Owner: Ionic Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: mpv | ---------------------+-------------------- Comment (by Mihai Moldovan ): In [changeset:"29fd6b3cebd9f0f68c276587e9d7bbe7daff0f60/macports-ports" 29fd6b3c/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="29fd6b3cebd9f0f68c276587e9d7bbe7daff0f60" multimedia/mpv: update to 0.22.0. Fixes: https://trac.macports.org/ticket/52878 (#52878), fixes: https://trac.macports.org/ticket/52845 (#52845) Changes: - Refresh 10.6 patchset. - Drop legacy Id line. - Move files from ${prefix}/share/examples/mpv to ${prefix}/share/doc/mpv/examples/. - Disable previous;y missed and new features. - Add new "zsh" variant for installing zsh completions. - Reformat notes a bit to remove redundant whitespaces. - Add comment regarding configure.args and why I cannot use it (yet?) - Fix @@NETWORK@@ reinplaces. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:20 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:20 -0000 Subject: [MacPorts] #52878: mpv @0.20.0_1-network: Configuration fails due to invalid sed expression In-Reply-To: <042.5f73d87d0b34daa5211f5e824fe7ebb0@macports.org> References: <042.5f73d87d0b34daa5211f5e824fe7ebb0@macports.org> Message-ID: <057.0d992b780a1ea2ae8e05fa572f8a1572@macports.org> #52878: mpv @0.20.0_1-network: Configuration fails due to invalid sed expression ---------------------+-------------------- Reporter: Eitot | Owner: Ionic Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: mpv | ---------------------+-------------------- Comment (by Mihai Moldovan ): In [changeset:"29fd6b3cebd9f0f68c276587e9d7bbe7daff0f60/macports-ports" 29fd6b3c/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="29fd6b3cebd9f0f68c276587e9d7bbe7daff0f60" multimedia/mpv: update to 0.22.0. Fixes: https://trac.macports.org/ticket/52878 (#52878), fixes: https://trac.macports.org/ticket/52845 (#52845) Changes: - Refresh 10.6 patchset. - Drop legacy Id line. - Move files from ${prefix}/share/examples/mpv to ${prefix}/share/doc/mpv/examples/. - Disable previous;y missed and new features. - Add new "zsh" variant for installing zsh completions. - Reformat notes a bit to remove redundant whitespaces. - Add comment regarding configure.args and why I cannot use it (yet?) - Fix @@NETWORK@@ reinplaces. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:21 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:21 -0000 Subject: [MacPorts] #51515: py-ipyparallel: needs a dependency on py-futures In-Reply-To: <053.22bbd42ddacfcd9eac92942383794148@macports.org> References: <053.22bbd42ddacfcd9eac92942383794148@macports.org> Message-ID: <068.33891045e4862f95288cd3ef669d465a@macports.org> #51515: py-ipyparallel: needs a dependency on py-futures -----------------------------+---------------------- Reporter: akss@… | Owner: stromnov Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: py-ipyparallel | -----------------------------+---------------------- Comment (by kurthindenburg): In [changeset:"d1fe04963c13950e689e80bf628f9d9237e9ad62/macports-ports" d1fe0496/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="d1fe04963c13950e689e80bf628f9d9237e9ad62" py-ipyparallel: add py-notebook dep for python 3+ py-futures for python 2.7 was added months ago remove outdated $Id$ closes https://trac.macports.org/ticket/51515 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:21 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:21 -0000 Subject: [MacPorts] #51321: nuweb: update to 1.58 In-Reply-To: <056.d8da97af15bdcddd0b0ad16609515764@macports.org> References: <056.d8da97af15bdcddd0b0ad16609515764@macports.org> Message-ID: <071.947bdf50d9a1e65be3e0a4c6de1a812b@macports.org> #51321: nuweb: update to 1.58 ---------------------------+---------------------- Reporter: ac.russell@… | Owner: kobold@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: nuweb | ---------------------------+---------------------- Comment (by kurthindenburg): In [changeset:"afc9c728ef30c1073e4cc7f95f019a9612f6046e/macports-ports" afc9c728/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="afc9c728ef30c1073e4cc7f95f019a9612f6046e" nuweb: update to 1.58 - add openmaintainer for now - maintainer timeout - add patch to get correct compiler settings - add CFLAGs to compile old buggy code - enable tests - some fail closes https://trac.macports.org/ticket/51321 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:21 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:21 -0000 Subject: [MacPorts] #53099: cctools @895: doesn't work with llvm < 3.8 In-Reply-To: <045.ac0c94d67f64ec79bed6dd1540959598@macports.org> References: <045.ac0c94d67f64ec79bed6dd1540959598@macports.org> Message-ID: <060.c2d649704307577f59bea2833760cf35@macports.org> #53099: cctools @895: doesn't work with llvm < 3.8 -----------------------+---------------------- Reporter: devernay | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: cctools | -----------------------+---------------------- Comment (by jeremyhu): In [changeset:"96b027d5c02e29997fab96bccec8bc6515ec2ab3/macports-ports" 96b027d5/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="96b027d5c02e29997fab96bccec8bc6515ec2ab3" cctools: Don't use llvm-otool with older llvm versions Fixes https://trac.macports.org/ticket/53099 Signed-off-by: Jeremy Huddleston Sequoia }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:21 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:21 -0000 Subject: [MacPorts] #53102: jasper dylib current version regressed In-Reply-To: <045.1d96a7542a3d6b123e5fe23a43d0875d@macports.org> References: <045.1d96a7542a3d6b123e5fe23a43d0875d@macports.org> Message-ID: <060.19710075038804846290c3599bf6c38d@macports.org> #53102: jasper dylib current version regressed -----------------------+-------------------- Reporter: jeremyhu | Owner: jmroot Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: jasper | -----------------------+-------------------- Comment (by jmroot): In [changeset:"e5594bd1cae69afb0dcba118cb0f842ff37bef41/macports-ports" e5594bd1/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="e5594bd1cae69afb0dcba118cb0f842ff37bef41" jasper dependents: rev bump Upstream's switch to cmake led to an apparently inadvertent change in library versioning. See: https://trac.macports.org/ticket/53102 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:22 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:22 -0000 Subject: [MacPorts] #53090: py-pyqt* multiple Qt depspecs In-Reply-To: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> References: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> Message-ID: <056.b9dc1dae4a71bcb42d82a6b31a6a9d59@macports.org> #53090: py-pyqt* multiple Qt depspecs --------------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: py-pyqt4 py-pyqt5 | --------------------------------+---------------------- Changes (by mkae): * status: reopened => closed * resolution: => fixed Comment: In [changeset:"1a9212c453e9be0e511d7d9f406b9c7e3d9eb81f/macports-ports" 1a9212c4/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="1a9212c453e9be0e511d7d9f406b9c7e3d9eb81f" py-pyqt5: fix dependencies Closes: https://trac.macports.org/ticket/53090 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:22 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:22 -0000 Subject: [MacPorts] #52193: [libutf8proc] update to 2.0.2 In-Reply-To: <053.e845653e4ab4b11d7f99ee975e8d179d@macports.org> References: <053.e845653e4ab4b11d7f99ee975e8d179d@macports.org> Message-ID: <068.782678a1a7d35c00b59c955f1a29cf08@macports.org> #52193: [libutf8proc] update to 2.0.2 --------------------------+-------------------- Reporter: danchr@… | Owner: mww@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: libutf8proc | --------------------------+-------------------- Comment (by kurthindenburg): In [changeset:"bda8962df6db230f2e71b21339c6079b1077b24b/macports-ports" bda8962d/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="bda8962df6db230f2e71b21339c6079b1077b24b" libutf8proc: update to 2.0.2 - maintainer timeout - move to github - add license - enable tests - not revbump only dep msort - doesn't build for me ATM closes https://trac.macports.org/ticket/52193 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:22 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:22 -0000 Subject: [MacPorts] #53119: Jasper fails to build In-Reply-To: <044.7102706dad0c13d0dcbcddf3d9b187fc@macports.org> References: <044.7102706dad0c13d0dcbcddf3d9b187fc@macports.org> Message-ID: <059.5d8307930747eb0583f15762cf308c15@macports.org> #53119: Jasper fails to build ----------------------+--------------------------------- Reporter: dershow | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: jasper | ----------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): In [changeset:"46b289ae0ceeb467f8878fc60f08c4619b22a274/macports-ports" 46b289ae/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="46b289ae0ceeb467f8878fc60f08c4619b22a274" jasper: control if and how documentation is built Fixes https://trac.macports.org/ticket/53119 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:22 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:22 -0000 Subject: [MacPorts] #53021: octave @4.2.0_1 +gcc6 +openblas: build failure In-Reply-To: <041.a9100f410b771f7245060d742521900f@macports.org> References: <041.a9100f410b771f7245060d742521900f@macports.org> Message-ID: <056.08feb3179a27899338b5470494b7992c@macports.org> #53021: octave @4.2.0_1 +gcc6 +openblas: build failure ---------------------+--------------------------------- Reporter: mf2k | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: octave | ---------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): In [changeset:"17e79f166fe9bf1c3636730b56e8620e2f116c09/macports-ports" 17e79f16/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="17e79f166fe9bf1c3636730b56e8620e2f116c09" octave: allow GCC to compile Carbon API See https://trac.macports.org/ticket/53021 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:22 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:22 -0000 Subject: [MacPorts] #53100: Upgrade py27-eyed3 to 0.7.10 In-Reply-To: <046.b37f76b8844d45796a615c52296964e3@macports.org> References: <046.b37f76b8844d45796a615c52296964e3@macports.org> Message-ID: <061.bc1cd994c6143fa54095e9a9fa920115@macports.org> #53100: Upgrade py27-eyed3 to 0.7.10 ------------------------+-------------------- Reporter: RichieB2B | Owner: elelay Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: py-eyed3 | ------------------------+-------------------- Comment (by elelay): In [changeset:"9aa13acef1e1ef26d6a69d61c511e5ec0f6d4f38/macports-ports" 9aa13ac/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="9aa13acef1e1ef26d6a69d61c511e5ec0f6d4f38" py*-eyed3 upgrade to 0.7.10 closes https://trac.macports.org/ticket/53100 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:22 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:22 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.e76b84d745b314599f8ea3fa1625bafc@macports.org> #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): In [changeset:"f9ab7cac0c41427968293f1fc1fadbafe3c294b0/macports-ports" f9ab7cac/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="f9ab7cac0c41427968293f1fc1fadbafe3c294b0" octave: use older libstdc++ ABI on older system See https://trac.macports.org/ticket/53044 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:22 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:22 -0000 Subject: [MacPorts] #51520: llvm-3.9 @3.9-r270400_0+assertions+debug build failure on snow leopard due to missing strnlen function - and fix In-Reply-To: <067.fcaa7e4195b6cce47cbccee919b1a2f0@macports.org> References: <067.fcaa7e4195b6cce47cbccee919b1a2f0@macports.org> Message-ID: <082.075384933a8a19c549fbdb2b2732782a@macports.org> #51520: llvm-3.9 @3.9-r270400_0+assertions+debug build failure on snow leopard due to missing strnlen function - and fix -------------------------------------+------------------------- Reporter: kenneth.f.cunningham@… | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: snowleopard Port: llvm-3.9 clang-3.9 | -------------------------------------+------------------------- Comment (by jeremyhu): In [changeset:"b9031fa3d215bab2f29095337d4f351508eab50f/macports-ports" b9031fa3/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="b9031fa3d215bab2f29095337d4f351508eab50f" llvm-{3.9,devel}: Provide implementation of strnlen for pre-Lion Fixes https://trac.macports.org/ticket/51520 Signed-off-by: Jeremy Huddleston Sequoia }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:23 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:23 -0000 Subject: [MacPorts] #51991: Update ocaml zarith to 1.4.1 In-Reply-To: <073.3baca53d356e7a7673f6195cf994dbae@macports.org> References: <073.3baca53d356e7a7673f6195cf994dbae@macports.org> Message-ID: <088.589f2481cb4864deff25b466bc6f2acf@macports.org> #51991: Update ocaml zarith to 1.4.1 -------------------------------------------+-------------------- Reporter: louis.granboulan.developer@… | Owner: mww@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: ocaml-zarith | -------------------------------------------+-------------------- Comment (by kurthindenburg): In [changeset:"d4bae7cb7865137ae56eeb38fdb8a4f70bb9f020/macports-ports" d4bae7cb/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="d4bae7cb7865137ae56eeb38fdb8a4f70bb9f020" ocaml-zarith: update to 1.4.1 closes https://trac.macports.org/ticket/51991 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:23 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:23 -0000 Subject: [MacPorts] #53019: mogenerator: update to v1.31 In-Reply-To: <050.8a174741fb7e44432b228be9a4819fd2@macports.org> References: <050.8a174741fb7e44432b228be9a4819fd2@macports.org> Message-ID: <065.2934d4f613dee3bbf8d7441643dedc7f@macports.org> #53019: mogenerator: update to v1.31 ----------------------------+------------------------------- Reporter: steventondeur | Owner: public+macports@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: mogenerator | ----------------------------+------------------------------- Comment (by g5pw): In [changeset:"347f4b6f3c22bfb86defbe66a507bab9d7a83dd6/macports-ports" 347f4b6f/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="347f4b6f3c22bfb86defbe66a507bab9d7a83dd6" devel/mogenerator: update to 1.31 Maintainer timeout, Closes: https://trac.macports.org/ticket/53019 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:21 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:21 -0000 Subject: [MacPorts] #52196: Consider not using @rpath for llvm and clang libraries In-Reply-To: <045.1030a3a150440dad10264a6cf2514c08@macports.org> References: <045.1030a3a150440dad10264a6cf2514c08@macports.org> Message-ID: <060.4b1c83b6538a9ec345fc71f8877d99d3@macports.org> #52196: Consider not using @rpath for llvm and clang libraries -------------------------------------------+---------------------- Reporter: jeremyhu | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: llvm-3.8 llvm-3.9 llvm-devel | -------------------------------------------+---------------------- Comment (by jeremyhu): In [changeset:"7b64baf3fabb696d61573828e5a5de2f9063227b/macports-ports" 7b64baf3/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="7b64baf3fabb696d61573828e5a5de2f9063227b" clang-3.[89]: Update dylib ids to not be @rpath-based Fixes https://trac.macports.org/ticket/52196 Signed-off-by: Jeremy Huddleston Sequoia }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:21 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:21 -0000 Subject: [MacPorts] #53105: qt5-qtbase @5.6.2: configure fails due to invalid compiler *clang* In-Reply-To: <047.71de0adf031ec43db9842370f4b572e1@macports.org> References: <047.71de0adf031ec43db9842370f4b572e1@macports.org> Message-ID: <062.04a0d1e38df2c331777448beb367dcce@macports.org> #53105: qt5-qtbase @5.6.2: configure fails due to invalid compiler *clang* ---------------------------------+--------------------------------- Reporter: mndavidoff | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: qt5-qtbase poppler | ---------------------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): In [changeset:"f279d7b542a0e54d8cc19754a9d63b13a9a8096e/macports-ports" f279d7b5/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="f279d7b542a0e54d8cc19754a9d63b13a9a8096e" qt5: revert https://github.com/macports/macports- ports/commit/f892d8b4fb154a13288741cb6359225e810426e1 Fixes https://trac.macports.org/ticket/53105 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:22 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:22 -0000 Subject: [MacPorts] #53105: qt5-qtbase @5.6.2: configure fails due to invalid compiler *clang* In-Reply-To: <047.71de0adf031ec43db9842370f4b572e1@macports.org> References: <047.71de0adf031ec43db9842370f4b572e1@macports.org> Message-ID: <062.b1d023991981566655e5a275a0c0e526@macports.org> #53105: qt5-qtbase @5.6.2: configure fails due to invalid compiler *clang* ---------------------------------+--------------------------------- Reporter: mndavidoff | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: qt5-qtbase poppler | ---------------------------------+--------------------------------- Comment (by jmroot): In [changeset:"761cbc0bbce6e3595face125c2150e6dfb9737b8/macports-ports" 761cbc0b/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="761cbc0bbce6e3595face125c2150e6dfb9737b8" Achieve the intent of f892d8b Globs can be used in the blacklist, so blacklist all the gccs, which is the same as whitelisting all the clangs, since those are the only two kinds of compiler in compiler.fallback. See: https://trac.macports.org/ticket/53105 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:38:22 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:38:22 -0000 Subject: [MacPorts] #53090: py-pyqt* multiple Qt depspecs In-Reply-To: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> References: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> Message-ID: <056.5b70f2eb63fb43dd7ddf10ce2190d851@macports.org> #53090: py-pyqt* multiple Qt depspecs --------------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: reopened Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: py-pyqt4 py-pyqt5 | --------------------------------+---------------------- Comment (by mkae): In [changeset:"e8ac41907098888eba3e23a6c096cbf76acff3a2/macports-ports" e8ac4190/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="e8ac41907098888eba3e23a6c096cbf76acff3a2" py-pyqt4: fix dependencies See: https://trac.macports.org/ticket/53090 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 09:59:13 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 09:59:13 -0000 Subject: [MacPorts] #53122: gpgme : upgrade to 1.8.0 and +qt5 variant In-Reply-To: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> References: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> Message-ID: <056.b837da3b042f17fa2668d7df21c1f2d7@macports.org> #53122: gpgme : upgrade to 1.8.0 and +qt5 variant ---------------------+------------------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch upstream Port: gpgme | ---------------------+------------------------------- Comment (by RJVB): OK, I'll see how easy it is to build just the QGpgME component; hopefully it's just a matter of setting `languages=qt`. I didn't want to say it, but yeah, it'll allow us to avoid multiple-captains-on-a-ship disagreements ;) Either way, having a gpgme-qt5 port will allow dependents to use a regular depspec and not the active_variants hack. If others have tested the easy solution of setting _DARWIN_C_SOURCE to a suitable value that that will indeed be the more elegant approach. Check the patchfile though, there are 1 or 2 locations where I had to include a headerfile (strings.h) for `strcasecmp`, without having to provide an explicit prototype. Maybe that header will be included automagically when _DARWIN_C_SOURCE is set, but I don't think that that would be a proper fix. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 10:23:34 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 10:23:34 -0000 Subject: [MacPorts] #53122: gpgme : upgrade to 1.8.0 and +qt5 variant In-Reply-To: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> References: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> Message-ID: <056.43cf71529cbd7f58ec980ee0e33aa0ff@macports.org> #53122: gpgme : upgrade to 1.8.0 and +qt5 variant ---------------------+------------------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch upstream Port: gpgme | ---------------------+------------------------------- Comment (by RJVB): https://bugs.gnupg.org/gnupg/msg9634 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 11:26:25 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 11:26:25 -0000 Subject: [MacPorts] #53125: Clarify the difference between eigen3 and eigen3-devel In-Reply-To: <041.2e98dad885d2df9e1b7576ce8f82258b@macports.org> References: <041.2e98dad885d2df9e1b7576ce8f82258b@macports.org> Message-ID: <056.3e062910dcc46af5a4cdff1ef528e725@macports.org> #53125: Clarify the difference between eigen3 and eigen3-devel --------------------------+---------------------- Reporter: ksze | Owner: eborisch Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: eigen3 | --------------------------+---------------------- Changes (by ryandesign): * status: new => assigned * owner: => eborisch Comment: Replying to [ticket:53125 ksze]: > `eigen3-devel` is a sub-port of `eigen3`, and the two ports conflict each other. However, their descriptions are exactly the same. > > What's the difference between the two? > > I would presume `eigen3-devel` is a development version, That's correct. > but does that mean it would be built without optimizations or with debug symbols? No difference in how the stable and development versions are built. > The description does not say. > > Please clarify in the port description. You could make the same complaint about virtually every other -devel port. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 11:28:27 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 11:28:27 -0000 Subject: [MacPorts] #53124: julia: Update to version 0.5 (was: Update Julia to version 0.5) In-Reply-To: <045.fc17f67b995cc13ab11a9440273f871f@macports.org> References: <045.fc17f67b995cc13ab11a9440273f871f@macports.org> Message-ID: <060.8d910d4b2d84369ae2bcf541dde8b04c@macports.org> #53124: julia: Update to version 0.5 -----------------------+------------------------ Reporter: manuSrep | Owner: seanfarley Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: julia | -----------------------+------------------------ Changes (by ryandesign): * status: new => assigned * owner: => seanfarley * port: => julia -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 14:17:18 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 14:17:18 -0000 Subject: [MacPorts] #53123: botan links against libstdc++ on 10.6 with libcxx, preventing qca from building. And workaround. In-Reply-To: <042.c6ed3875ce93ad7a203783ef4a68231d@macports.org> References: <042.c6ed3875ce93ad7a203783ef4a68231d@macports.org> Message-ID: <057.31a0ba5c4f06b86f4627a93559c52a66@macports.org> #53123: botan links against libstdc++ on 10.6 with libcxx, preventing qca from building. And workaround. ---------------------+------------------------- Reporter: kencu | Owner: mww@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: botan | ---------------------+------------------------- Changes (by mf2k): * keywords: => snowleopard * status: new => assigned * owner: => mww@… * cc: mww@… (removed) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 14:19:46 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 14:19:46 -0000 Subject: [MacPorts] #53127: (10.5.8PPC) Osxfuse - Fetch failed Message-ID: <044.50bcf03fed00657f19e635ea522c0cae@macports.org> #53127: (10.5.8PPC) Osxfuse - Fetch failed -------------------------------------+--------------------- Reporter: mrkapqa | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: osxfuse ntfs-3g leopard | Port: osxfuse -------------------------------------+--------------------- Fetching distfiles for osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://lil.fr.distfiles.macports.org/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://distfiles.macports.org/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://nue.de.distfiles.macports.org/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://osl.no.distfiles.macports.org/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from https://github.com/osxfuse/osxfuse/tarball/99a3c2e/ ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://sea.us.distfiles.macports.org/macports/distfiles/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://jog.id.distfiles.macports.org/macports/distfiles/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://jnb.za.distfiles.macports.org/distfiles/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://pek.cn.distfiles.macports.org/macports/distfiles/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://cjj.kr.distfiles.macports.org/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://her.gr.distfiles.macports.org/osxfuse Error: org.macports.fetch for port osxfuse returned: fetch failed Please see the log file for port osxfuse for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port osxfuse failed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 14:23:19 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 14:23:19 -0000 Subject: [MacPorts] #53128: [Port Abandoned] mogenerator Message-ID: <041.7e833aae0632935c7ed194f824a17512@macports.org> #53128: [Port Abandoned] mogenerator --------------------+------------------------------- Reporter: mf2k | Owner: public+macports@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: mogenerator --------------------+------------------------------- The maintainer of mogenerator has not been seen [search:public%2Bmacports @francisco-garcia.net since 2013] and has [query:owner=public%2Bmacports @francisco- garcia.net&status=accepted&status=assigned&status=closed&status=new&status=reopened&order=priority not responded to tickets] about this port. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 14:23:54 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 14:23:54 -0000 Subject: [MacPorts] #53128: [Port Abandoned] mogenerator In-Reply-To: <041.7e833aae0632935c7ed194f824a17512@macports.org> References: <041.7e833aae0632935c7ed194f824a17512@macports.org> Message-ID: <056.2f2741e1a6765f1f7ea87c8c9b345a65@macports.org> #53128: [Port Abandoned] mogenerator --------------------------+------------------------------- Reporter: mf2k | Owner: public+macports@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: mogenerator | --------------------------+------------------------------- Description changed by mf2k: Old description: > The maintainer of mogenerator has not been seen [search:public%2Bmacports > @francisco-garcia.net since 2013] and has [query:owner=public%2Bmacports > @francisco- > garcia.net&status=accepted&status=assigned&status=closed&status=new&status=reopened&order=priority > not responded to tickets] about this port. New description: The maintainer of mogenerator has not been seen [search:public+macports @francisco-garcia.net since 2013] and has [query:owner=public+macports @francisco- garcia.net&status=accepted&status=assigned&status=closed&status=new&status=reopened&order=priority not responded to tickets] about this port. -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 14:28:48 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 14:28:48 -0000 Subject: [MacPorts] #53126: opencv @3.1.0_8 +avx2 +contrib +eigen +gdal +opencl +java +python27 +python35 +qt5 +tbb fails to build In-Reply-To: <041.3f35f94de3ddb392dfa4b95fae6a35b8@macports.org> References: <041.3f35f94de3ddb392dfa4b95fae6a35b8@macports.org> Message-ID: <056.e2b7e5883bb74c34c5a39ee663d57f03@macports.org> #53126: opencv @3.1.0_8 +avx2 +contrib +eigen +gdal +opencl +java +python27 +python35 +qt5 +tbb fails to build ---------------------+---------------------- Reporter: ksze | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: opencv | ---------------------+---------------------- Changes (by mf2k): * status: new => assigned * owner: => stromnov * keywords: build => Comment: In the future, please Cc the port maintainers ({{{port info --maintainers opencv}}}), if any. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 14:49:07 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 14:49:07 -0000 Subject: [MacPorts] #53122: gpgme : upgrade to 1.8.0 and +qt5 variant In-Reply-To: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> References: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> Message-ID: <056.7b8fca73b2b41ad7ee60c7befa816b37@macports.org> #53122: gpgme : upgrade to 1.8.0 and +qt5 variant ---------------------+------------------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch upstream Port: gpgme | ---------------------+------------------------------- Comment (by dbevans): Replying to [comment:7 RJVB]: > OK, I'll see how easy it is to build just the QGpgME component; hopefully it's just a matter of setting `languages=qt`. I didn't want to say it, but yeah, it'll allow us to avoid multiple-captains-on-a-ship disagreements ;) > Either way, having a gpgme-qt5 port will allow dependents to use a regular depspec and not the active_variants hack. You've changed the proposal a bit. We agreed on QGpgME (using qt5 and depending on gpgme) as a separate port. If you want gpgme-qt5 it needs to be a subport of gpgme to avoid confusion. > > If others have tested the easy solution of setting _DARWIN_C_SOURCE to a suitable value that that will indeed be the more elegant approach. Check the patchfile though, there are 1 or 2 locations where I had to include a headerfile (strings.h) for `strcasecmp`, without having to provide an explicit prototype. Maybe that header will be included automagically when _DARWIN_C_SOURCE is set, but I don't think that that would be a proper fix. Manually setting _DARWIN_C_SOURCE bothers me a bit but is what upstream insists on using saying "works for me" (but only testing on darwin15). I'm thinking that including instead of may be another alternative. Will check this out after getting a cup of coffee under my belt. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 15:01:48 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 15:01:48 -0000 Subject: [MacPorts] #53122: gpgme : upgrade to 1.8.0 and +qt5 variant In-Reply-To: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> References: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> Message-ID: <056.e3f902bf6aa57759f9f7a736003a5a3a@macports.org> #53122: gpgme : upgrade to 1.8.0 and +qt5 variant ---------------------+------------------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch upstream Port: gpgme | ---------------------+------------------------------- Comment (by RJVB): Replying to [comment:9 dbevans]: > You've changed the proposal a bit. We agreed on QGpgME (using qt5 and depending on gpgme) as a separate port. If you want gpgme-qt5 it needs to be a subport of gpgme to avoid confusion. No problem. I think we'd be the only ones making a difference between qpgme-qt5 as a subport or as a separate port, but I have already started working on a port:qgpgme so the point is moot. > Manually setting _DARWIN_C_SOURCE bothers me a bit but is what upstream insists on It also bothered me hence the alternative patch - but at least if this does lead to unforeseen side-effects there will be reason to file a bug report. Actually, I considered setting _DARWIN_C_LEVEL, because that's what my string.h contains (but I'm not on my Mac right now). What surprises me is that I've never run into this issue before. Wouldn't _DARWIN_C_LEVEL and/or _DARWIN_C_SOURCE be set appropriately by selecting the right C dialect using a directive? I think that would be more correct, no? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 15:14:07 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 15:14:07 -0000 Subject: [MacPorts] #53129: (10.5.8PPC) CCTools - Fetch Failes Message-ID: <044.ba00bff09faf7c49f492b9618c3bcc1f@macports.org> #53129: (10.5.8PPC) CCTools - Fetch Failes --------------------------+------------------ Reporter: mrkapqa | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: gcc5 cctools | Port: gcc5 --------------------------+------------------ ---> Fetching archive for cctools ---> Attempting to fetch cctools-895_3+llvm33.darwin_9.ppc.tbz2 from http://fco.it.packages.macports.org/mirrors/macports- packages/cctools/cctools ---> Attempting to fetch cctools-895_3+llvm33.darwin_9.ppc.tbz2 from http://lil.fr.packages.macports.org/cctools ---> Attempting to fetch cctools-895_3+llvm33.darwin_9.ppc.tbz2 from http://packages.macports.org/cctools ---> Fetching distfiles for cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://opensource.apple.com/tarballs/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://opensource.apple.com/tarballs/ld64 ---> Attempting to fetch ld64-274.1.tar.gz from http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://lil.fr.distfiles.macports.org/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://distfiles.macports.org/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://nue.de.distfiles.macports.org/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://osl.no.distfiles.macports.org/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://sea.us.distfiles.macports.org/macports/distfiles/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://jog.id.distfiles.macports.org/macports/distfiles/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://jnb.za.distfiles.macports.org/distfiles/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://pek.cn.distfiles.macports.org/macports/distfiles/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://cjj.kr.distfiles.macports.org/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://her.gr.distfiles.macports.org/cctools Error: org.macports.fetch for port cctools returned: fetch failed Error: Failed to install cctools Please see the log file for port cctools for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/main.log Error: The following dependencies were not installed: cctools gcc_select gmp isl ld64 ld64-127 libmacho-headers libgcc libmpc mpfr To report a bug, follow the instructions in the guide: this happend when tyring to insstall sudo port install gcc5 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 15:24:19 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 15:24:19 -0000 Subject: [MacPorts] #53127: (10.5.8PPC) Osxfuse - Fetch failed In-Reply-To: <044.50bcf03fed00657f19e635ea522c0cae@macports.org> References: <044.50bcf03fed00657f19e635ea522c0cae@macports.org> Message-ID: <059.b7c2ab40ed47d7f6810637b2003b9170@macports.org> #53127: (10.5.8PPC) Osxfuse - Fetch failed ----------------------+---------------------- Reporter: mrkapqa | Owner: drkp Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: leopard Port: osxfuse | ----------------------+---------------------- Changes (by mf2k): * keywords: osxfuse ntfs-3g leopard => leopard * status: new => assigned * owner: => drkp Comment: In the future, please use WikiFormatting and Cc the port maintainers ({{{port info --maintainers osxfuse}}}), if any. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 15:24:35 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 15:24:35 -0000 Subject: [MacPorts] #53127: (10.5.8PPC) Osxfuse - Fetch failed In-Reply-To: <044.50bcf03fed00657f19e635ea522c0cae@macports.org> References: <044.50bcf03fed00657f19e635ea522c0cae@macports.org> Message-ID: <059.b7e763e42fb50c4e35ca8d43df72f4f5@macports.org> #53127: (10.5.8PPC) Osxfuse - Fetch failed ----------------------+---------------------- Reporter: mrkapqa | Owner: drkp Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: leopard Port: osxfuse | ----------------------+---------------------- Description changed by mf2k: Old description: > Fetching distfiles for osxfuse > ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from > http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/osxfuse > ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from > http://lil.fr.distfiles.macports.org/osxfuse > ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from > http://distfiles.macports.org/osxfuse > ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from > http://nue.de.distfiles.macports.org/osxfuse > ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from > http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/osxfuse > ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from > http://osl.no.distfiles.macports.org/osxfuse > ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from > https://github.com/osxfuse/osxfuse/tarball/99a3c2e/ > ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from > http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/osxfuse > ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from > http://sea.us.distfiles.macports.org/macports/distfiles/osxfuse > ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from > http://jog.id.distfiles.macports.org/macports/distfiles/osxfuse > ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from > http://jnb.za.distfiles.macports.org/distfiles/osxfuse > ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from > http://pek.cn.distfiles.macports.org/macports/distfiles/osxfuse > ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from > http://cjj.kr.distfiles.macports.org/osxfuse > ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from > http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/osxfuse > ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from > http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/osxfuse > ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from > http://her.gr.distfiles.macports.org/osxfuse > Error: org.macports.fetch for port osxfuse returned: fetch failed > Please see the log file for port osxfuse for details: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/main.log > To report a bug, follow the instructions in the guide: > http://guide.macports.org/#project.tickets > Error: Processing of port osxfuse failed New description: {{{ Fetching distfiles for osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://lil.fr.distfiles.macports.org/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://distfiles.macports.org/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://nue.de.distfiles.macports.org/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://osl.no.distfiles.macports.org/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from https://github.com/osxfuse/osxfuse/tarball/99a3c2e/ ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://sea.us.distfiles.macports.org/macports/distfiles/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://jog.id.distfiles.macports.org/macports/distfiles/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://jnb.za.distfiles.macports.org/distfiles/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://pek.cn.distfiles.macports.org/macports/distfiles/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://cjj.kr.distfiles.macports.org/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/osxfuse ---> Attempting to fetch osxfuse-99a3c2e.tar.gz from http://her.gr.distfiles.macports.org/osxfuse Error: org.macports.fetch for port osxfuse returned: fetch failed Please see the log file for port osxfuse for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port osxfuse failed }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 15:28:39 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 15:28:39 -0000 Subject: [MacPorts] #53125: Clarify the difference between eigen3 and eigen3-devel In-Reply-To: <041.2e98dad885d2df9e1b7576ce8f82258b@macports.org> References: <041.2e98dad885d2df9e1b7576ce8f82258b@macports.org> Message-ID: <056.b89c5973458dfa6fda26a2b2ea0a7869@macports.org> #53125: Clarify the difference between eigen3 and eigen3-devel --------------------------+---------------------- Reporter: ksze | Owner: eborisch Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: eigen3 | --------------------------+---------------------- Changes (by eborisch): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"6a278d613609af39809fce5a31bdcf35f4ca545e/macports-ports" 6a278d61/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="6a278d613609af39809fce5a31bdcf35f4ca545e" eigen3-devel: Enhance description. Closes: https://trac.macports.org/ticket/53125 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 15:29:18 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 15:29:18 -0000 Subject: [MacPorts] #53125: Clarify the difference between eigen3 and eigen3-devel In-Reply-To: <041.2e98dad885d2df9e1b7576ce8f82258b@macports.org> References: <041.2e98dad885d2df9e1b7576ce8f82258b@macports.org> Message-ID: <056.ee11d0b9bd203226f754ccb56cebdb7e@macports.org> #53125: Clarify the difference between eigen3 and eigen3-devel --------------------------+---------------------- Reporter: ksze | Owner: eborisch Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: eigen3 | --------------------------+---------------------- Comment (by eborisch): The -devel version tracks pre-release (-rcN, -beta, ...) versions of eigen3 when they are available. Currently there is no pre-release version, so they both point to the same thing. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 15:30:09 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 15:30:09 -0000 Subject: [MacPorts] #53129: (10.5.8PPC) CCTools - Fetch Failes In-Reply-To: <044.ba00bff09faf7c49f492b9618c3bcc1f@macports.org> References: <044.ba00bff09faf7c49f492b9618c3bcc1f@macports.org> Message-ID: <059.d842830aad8333c2c8ec7997c3b4e434@macports.org> #53129: (10.5.8PPC) CCTools - Fetch Failes ----------------------+---------------------- Reporter: mrkapqa | Owner: jeremyhu Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cctools | ----------------------+---------------------- Changes (by mf2k): * keywords: gcc5 cctools => * owner: => jeremyhu * status: new => assigned * port: gcc5 => cctools Comment: In the future, please use WikiFormatting, fill in the Port field with the port that actually failed to build and Cc the port maintainers ({{{port info --maintainers cctools}}}), if any. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 15:30:39 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 15:30:39 -0000 Subject: [MacPorts] #53129: (10.5.8PPC) CCTools - Fetch Failes In-Reply-To: <044.ba00bff09faf7c49f492b9618c3bcc1f@macports.org> References: <044.ba00bff09faf7c49f492b9618c3bcc1f@macports.org> Message-ID: <059.78ee80e8addf450c2d52b0498c6c0f15@macports.org> #53129: (10.5.8PPC) CCTools - Fetch Failes ----------------------+---------------------- Reporter: mrkapqa | Owner: jeremyhu Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: leopard Port: cctools | ----------------------+---------------------- Changes (by mf2k): * keywords: => leopard Old description: > ---> Fetching archive for cctools > ---> Attempting to fetch cctools-895_3+llvm33.darwin_9.ppc.tbz2 from > http://fco.it.packages.macports.org/mirrors/macports- > packages/cctools/cctools > ---> Attempting to fetch cctools-895_3+llvm33.darwin_9.ppc.tbz2 from > http://lil.fr.packages.macports.org/cctools > ---> Attempting to fetch cctools-895_3+llvm33.darwin_9.ppc.tbz2 from > http://packages.macports.org/cctools > ---> Fetching distfiles for cctools > ---> Attempting to fetch ld64-274.1.tar.gz from > http://opensource.apple.com/tarballs/cctools > ---> Attempting to fetch ld64-274.1.tar.gz from > http://opensource.apple.com/tarballs/ld64 > ---> Attempting to fetch ld64-274.1.tar.gz from > http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/cctools > ---> Attempting to fetch ld64-274.1.tar.gz from > http://lil.fr.distfiles.macports.org/cctools > ---> Attempting to fetch ld64-274.1.tar.gz from > http://distfiles.macports.org/cctools > ---> Attempting to fetch ld64-274.1.tar.gz from > http://nue.de.distfiles.macports.org/cctools > ---> Attempting to fetch ld64-274.1.tar.gz from > http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/cctools > ---> Attempting to fetch ld64-274.1.tar.gz from > http://osl.no.distfiles.macports.org/cctools > ---> Attempting to fetch ld64-274.1.tar.gz from > http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/cctools > ---> Attempting to fetch ld64-274.1.tar.gz from > http://sea.us.distfiles.macports.org/macports/distfiles/cctools > ---> Attempting to fetch ld64-274.1.tar.gz from > http://jog.id.distfiles.macports.org/macports/distfiles/cctools > ---> Attempting to fetch ld64-274.1.tar.gz from > http://jnb.za.distfiles.macports.org/distfiles/cctools > ---> Attempting to fetch ld64-274.1.tar.gz from > http://pek.cn.distfiles.macports.org/macports/distfiles/cctools > ---> Attempting to fetch ld64-274.1.tar.gz from > http://cjj.kr.distfiles.macports.org/cctools > ---> Attempting to fetch ld64-274.1.tar.gz from > http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/cctools > ---> Attempting to fetch ld64-274.1.tar.gz from > http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/cctools > ---> Attempting to fetch ld64-274.1.tar.gz from > http://her.gr.distfiles.macports.org/cctools > Error: org.macports.fetch for port cctools returned: fetch failed > Error: Failed to install cctools > Please see the log file for port cctools for details: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/main.log > Error: The following dependencies were not installed: cctools gcc_select > gmp isl ld64 ld64-127 libmacho-headers libgcc libmpc mpfr > To report a bug, follow the instructions in the guide: > > this happend when tyring to insstall sudo port install gcc5 New description: {{{ ---> Fetching archive for cctools ---> Attempting to fetch cctools-895_3+llvm33.darwin_9.ppc.tbz2 from http://fco.it.packages.macports.org/mirrors/macports- packages/cctools/cctools ---> Attempting to fetch cctools-895_3+llvm33.darwin_9.ppc.tbz2 from http://lil.fr.packages.macports.org/cctools ---> Attempting to fetch cctools-895_3+llvm33.darwin_9.ppc.tbz2 from http://packages.macports.org/cctools ---> Fetching distfiles for cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://opensource.apple.com/tarballs/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://opensource.apple.com/tarballs/ld64 ---> Attempting to fetch ld64-274.1.tar.gz from http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://lil.fr.distfiles.macports.org/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://distfiles.macports.org/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://nue.de.distfiles.macports.org/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://osl.no.distfiles.macports.org/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://sea.us.distfiles.macports.org/macports/distfiles/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://jog.id.distfiles.macports.org/macports/distfiles/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://jnb.za.distfiles.macports.org/distfiles/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://pek.cn.distfiles.macports.org/macports/distfiles/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://cjj.kr.distfiles.macports.org/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/cctools ---> Attempting to fetch ld64-274.1.tar.gz from http://her.gr.distfiles.macports.org/cctools Error: org.macports.fetch for port cctools returned: fetch failed Error: Failed to install cctools Please see the log file for port cctools for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/main.log Error: The following dependencies were not installed: cctools gcc_select gmp isl ld64 ld64-127 libmacho-headers libgcc libmpc mpfr To report a bug, follow the instructions in the guide: }}} this happend when tyring to insstall sudo port install gcc5 -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 16:41:35 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 16:41:35 -0000 Subject: [MacPorts] #53090: py-pyqt* multiple Qt depspecs In-Reply-To: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> References: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> Message-ID: <056.9697b7579e545f3bb1885c66e88292bf@macports.org> #53090: py-pyqt* multiple Qt depspecs --------------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: reopened Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: py-pyqt4 py-pyqt5 | --------------------------------+---------------------- Changes (by eborisch): * status: closed => reopened * resolution: fixed => Comment: The pt-pyqt5 version in 1a9212c4 appears broken. The qt5 portgroup as well as the name != subport tests got lost... It does not match the attached [attachment:Portfile] from René. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 16:56:35 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 16:56:35 -0000 Subject: [MacPorts] #53123: botan links against libstdc++ on 10.6 with libcxx, preventing qca from building. And workaround. In-Reply-To: <042.c6ed3875ce93ad7a203783ef4a68231d@macports.org> References: <042.c6ed3875ce93ad7a203783ef4a68231d@macports.org> Message-ID: <057.275f9da2ae3d472131bfdbe4c5ff60c9@macports.org> #53123: botan links against libstdc++ on 10.6 with libcxx, preventing qca from building. And workaround. ---------------------+------------------------- Reporter: kencu | Owner: mww@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: botan | ---------------------+------------------------- Comment (by kencu): I'm going to try a different, more comprehensive approach to this issue. I patched macports-clang-3.x to default to `-stdlib=libc++` instead of `-stdlib=libstdc++` on all systems, including 10.6. So far, it fixes the issue with botan, and I think it will also solve the wx-widgets issue and the leveldb issue as well. Will see how it goes. If it works well, Jeremy can decide if that's appropriate or not for general use. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 17:21:19 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 17:21:19 -0000 Subject: [MacPorts] #53130: iTerm2 3.0.13 build failure Message-ID: <047.23e8616a492b84ae8ad967f6d87c79a6@macports.org> #53130: iTerm2 3.0.13 build failure ------------------------+----------------- Reporter: EJFielding | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: ------------------------+----------------- I was doing a "port upgrade outdated" and the build of iTerm2-3.0.13_0 failed on my OS X 10.10.5 system. This looks like the relevant part of the "main.log" file: {{{ :info:build CompileC build/iTerm2.build/Deployment/iTerm2Shared.build /Objects-normal/x86_64/PTYWindow.o sources/PTYWindow.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler :info:build cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13 :info:build export LANG=en_US.US-ASCII :info:build /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x objective-c -arch x86_64 -fmessage-length=0 -fdiagnostics-show-note- include-stack -fmacro-backtrace-limit=0 -std=gnu99 -fmodules -gmodules -fmodules-prune-interval=86400 -fmodules-prune-after=345600 -fbuild- session- file=/var/folders/km/0cb0wxfj7pj82g5swgrp0mhw0000gq/C/org.llvm.clang/ModuleCache/Session.modulevalidation -fmodules-validate-once-per-build-session -Wnon-modular-include-in- framework-module -Werror=non-modular-include-in-framework-module -Wno- trigraphs -fpascal-strings -Os -Wno-missing-field-initializers -Wno- missing-prototypes -Werror=return-type -Wno-implicit-atomic-properties -Werror=deprecated-objc-isa-usage -Werror=objc-root-class -Wno-arc- repeated-use-of-weak -Wduplicate-method-match -Wno-missing-braces -Wparentheses -Wswitch -Wunused-function -Wno-unused-label -Wno-unused- parameter -Wunused-variable -Wunused-value -Wempty-body -Wconditional- uninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion -Wconstant-conversion -Wint-conversion -Wbool-conversion -Wenum-conversion -Wno-shorten-64-to-32 -Wpointer-sign -Wno-newline-eof -Wno-selector -Wno-strict-selector-match -Wundeclared-selector -Wno- deprecated-implementations -DNS_BLOCK_ASSERTIONS=1 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk -fasm-blocks -fstrict-aliasing -Wprotocol -Wdeprecated-declarations -mmacosx-version-min=10.8 -g -Wno-sign-conversion -iquote /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/build/iTerm2.build/Deployment/iTerm2Shared.build /iTerm2Shared-generated-files.hmap -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/build/iTerm2.build/Deployment/iTerm2Shared.build /iTerm2Shared-own-target-headers.hmap -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/build/iTerm2.build/Deployment/iTerm2Shared.build /iTerm2Shared-all-target-headers.hmap -iquote /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/build/iTerm2.build/Deployment/iTerm2Shared.build /iTerm2Shared-project-headers.hmap -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/build/Deployment/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/build/iTerm2.build/Deployment/iTerm2Shared.build/DerivedSources/x86_64 -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/build/iTerm2.build/Deployment/iTerm2Shared.build/DerivedSources -Wall -F/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/build/Deployment -F/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13 -F/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/ColorPicker -F/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/ThirdParty -include /var/folders/km/0cb0wxfj7pj82g5swgrp0mhw0000gq/C/com.apple.DeveloperTools/7.0-7A220/Xcode/SharedPrecompiledHeaders/iTerm2-axpumeaplfewijcmsdufnqkbhjtm/iTerm2.pch -MMD -MT dependencies -MF /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/build/iTerm2.build/Deployment/iTerm2Shared.build /Objects-normal/x86_64/PTYWindow.d --serialize-diagnostics /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/build/iTerm2.build/Deployment/iTerm2Shared.build /Objects-normal/x86_64/PTYWindow.dia -c /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/sources/PTYWindow.m -o /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/build/iTerm2.build/Deployment/iTerm2Shared.build /Objects-normal/x86_64/PTYWindow.o :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/sources/PTYWindow.m:65:68: error: expected a type :info:build - (instancetype)initWithContentRect:(NSRect)contentRect styleMask:(NSWindowStyleMask)aStyle backing:(NSBackingStoreType)bufferingType defer:(BOOL)flag { :info:build ^ :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/sources/PTYWindow.m:74:38: error: expected a type :info:build styleMask:(NSWindowStyleMask)aStyle :info:build ^ :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/sources/PTYWindow.m:66:61: warning: incompatible pointer to integer conversion sending 'id' to parameter of type 'NSUInteger' (aka 'unsigned long') [-Wint-conversion] :info:build self = [super initWithContentRect:contentRect styleMask:aStyle backing:bufferingType defer:flag]; :info:build ^~~~~~ :info:build In module 'AppKit' imported from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/sources/ProfileTableView.h:8: :info:build /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/System/Library/Frameworks/AppKit.framework/Headers/NSWindow.h:279:79: note: passing argument to parameter 'aStyle' here :info:build - (instancetype)initWithContentRect:(NSRect)contentRect styleMask:(NSUInteger)aStyle backing:(NSBackingStoreType)bufferingType defer:(BOOL)flag; :info:build ^ :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/sources/PTYWindow.m:79:39: warning: incompatible pointer to integer conversion sending 'id' to parameter of type 'NSUInteger' (aka 'unsigned long') [-Wint-conversion] :info:build styleMask:aStyle :info:build ^~~~~~ :info:build In module 'AppKit' imported from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/sources/ProfileTableView.h:8: :info:build /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/System/Library/Frameworks/AppKit.framework/Headers/NSWindow.h:280:79: note: passing argument to parameter 'aStyle' here :info:build - (instancetype)initWithContentRect:(NSRect)contentRect styleMask:(NSUInteger)aStyle backing:(NSBackingStoreType)bufferingType defer:(BOOL)flag screen:(nullable NSScreen *)screen; :info:build ^ :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/sources/PTYWindow.m:65:86: warning: conflicting parameter types in implementation of 'initWithContentRect:styleMask:backing:defer:': 'NSUInteger' (aka 'unsigned long') vs 'id' [-Wmismatched-parameter-types] :info:build - (instancetype)initWithContentRect:(NSRect)contentRect styleMask:(NSWindowStyleMask)aStyle backing:(NSBackingStoreType)bufferingType defer:(BOOL)flag { :info:build ^ :info:build In module 'AppKit' imported from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/sources/ProfileTableView.h:8: :info:build /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/System/Library/Frameworks/AppKit.framework/Headers/NSWindow.h:279:79: note: previous definition is here :info:build - (instancetype)initWithContentRect:(NSRect)contentRect styleMask:(NSUInteger)aStyle backing:(NSBackingStoreType)bufferingType defer:(BOOL)flag; :info:build ~~~~~~~~~~ ^ :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/sources/PTYWindow.m:74:56: warning: conflicting parameter types in implementation of 'initWithContentRect:styleMask:backing:defer:screen:': 'NSUInteger' (aka 'unsigned long') vs 'id' [-Wmismatched-parameter-types] :info:build styleMask:(NSWindowStyleMask)aStyle :info:build ^ :info:build In module 'AppKit' imported from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_iTerm2/iTerm2/work/iTerm2-3.0.13/sources/ProfileTableView.h:8: :info:build /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/System/Library/Frameworks/AppKit.framework/Headers/NSWindow.h:280:79: note: previous definition is here :info:build - (instancetype)initWithContentRect:(NSRect)contentRect styleMask:(NSUInteger)aStyle backing:(NSBackingStoreType)bufferingType defer:(BOOL)flag screen:(nullable NSScreen *)screen; :info:build ~~~~~~~~~~ ^ :info:build 4 warnings and 2 errors generated. }}} I also attach the full log file. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 17:22:10 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 17:22:10 -0000 Subject: [MacPorts] #53130: iTerm2 3.0.13 build failure In-Reply-To: <047.23e8616a492b84ae8ad967f6d87c79a6@macports.org> References: <047.23e8616a492b84ae8ad967f6d87c79a6@macports.org> Message-ID: <062.538d4778574dc888287ec53de6434736@macports.org> #53130: iTerm2 3.0.13 build failure -------------------------+----------------- Reporter: EJFielding | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | -------------------------+----------------- Changes (by EJFielding): * Attachment "main.log" added. main.log file -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 17:58:30 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 17:58:30 -0000 Subject: [MacPorts] #53131: drumstick, vmpk (virtual midi piano keyboard): new ports Message-ID: <042.f1ab49614520911e77cc85deae9433f2@macports.org> #53131: drumstick, vmpk (virtual midi piano keyboard): new ports ------------------------+---------------------------- Reporter: mojca | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: drumstick vmpk ------------------------+---------------------------- I would like to use vmpk (virtual midi piano keyboard) that depends on drumstick. I created a Portfile, but the software quits as soon as it starts and I have no clue how to debug it. Open to additional maintainers and patches. Upstream binaries crash on older OSes. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 17:58:56 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 17:58:56 -0000 Subject: [MacPorts] #53131: drumstick, vmpk (virtual midi piano keyboard): new ports In-Reply-To: <042.f1ab49614520911e77cc85deae9433f2@macports.org> References: <042.f1ab49614520911e77cc85deae9433f2@macports.org> Message-ID: <057.53e7635a5db43d48d9fa49e673696c6b@macports.org> #53131: drumstick, vmpk (virtual midi piano keyboard): new ports -----------------------------+----------------- Reporter: mojca | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: drumstick vmpk | -----------------------------+----------------- Changes (by mojca): * Attachment "drumstick.Portfile" added. Portfile for drumstick -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 17:59:14 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 17:59:14 -0000 Subject: [MacPorts] #53131: drumstick, vmpk (virtual midi piano keyboard): new ports In-Reply-To: <042.f1ab49614520911e77cc85deae9433f2@macports.org> References: <042.f1ab49614520911e77cc85deae9433f2@macports.org> Message-ID: <057.a116e586cef988b24d4e3556778c161f@macports.org> #53131: drumstick, vmpk (virtual midi piano keyboard): new ports -----------------------------+----------------- Reporter: mojca | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: drumstick vmpk | -----------------------------+----------------- Changes (by mojca): * Attachment "vmpk.Portfile" added. Portfile for vmpk -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 18:17:03 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 18:17:03 -0000 Subject: [MacPorts] #53117: Braeburn POST requests (Trac, Mailman) are unreliable (was: Trac is unreliable) In-Reply-To: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> References: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> Message-ID: <056.a161f51344ec6ac18ed5a88f8745a427@macports.org> #53117: Braeburn POST requests (Trac, Mailman) are unreliable -----------------------------+--------------------- Reporter: mf2k | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+--------------------- Changes (by ryandesign): * cc: ryandesign (added) Comment: This has been happening to me intermittently ever since we moved to Braeburn, as I've previously reported by email. It's not limited to Trac either; I've seen the same problem with Mailman. It doesn't matter what network I'm on. It seems to be limited to POST requests. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 18:25:54 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 18:25:54 -0000 Subject: [MacPorts] #53131: drumstick, vmpk (virtual midi piano keyboard): new ports In-Reply-To: <042.f1ab49614520911e77cc85deae9433f2@macports.org> References: <042.f1ab49614520911e77cc85deae9433f2@macports.org> Message-ID: <057.6e2d0939523cf31a1c36362cceb87cdf@macports.org> #53131: drumstick, vmpk (virtual midi piano keyboard): new ports -----------------------------+----------------- Reporter: mojca | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: drumstick vmpk | -----------------------------+----------------- Comment (by RJVB): I don't have much time to look into this now, but in my own experiments drumstick is only partly functional on OS X; the only application that plays actual sound is drumstick-vpiano. I did patch the software so that it builds as regular shared libraries, IIRC this was more or less a requirement to use if with KDE's Minuet. Building 1.1.0 is possible on 10.10 and earlier by including AudioUnit.h instead of AUAudioUnit.h . For reference and/or perusal: https://github.com/RJVB/macstrop/tree/master/audio/drumstick . -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 18:31:19 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 18:31:19 -0000 Subject: [MacPorts] #53122: gpgme : upgrade to 1.8.0 and +qt5 variant In-Reply-To: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> References: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> Message-ID: <056.7dd025294538c158df8e725eda31799b@macports.org> #53122: gpgme : upgrade to 1.8.0 and +qt5 variant ---------------------+------------------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch upstream Port: gpgme | ---------------------+------------------------------- Comment (by RJVB): OK, I have a working `port:qgpgme` port. Turns out qgpgme 1.7.0 builds and runs fine against gpgme 1.8.0 . Keep me posted what you plan to do with gpgme, upgrade to 1.8.0 asap or wait for upstream fixes. I don't think there's haste with qgpgme so it can wait for gpgme 1.8x to land. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 18:43:59 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 18:43:59 -0000 Subject: [MacPorts] #53131: drumstick, vmpk (virtual midi piano keyboard): new ports In-Reply-To: <042.f1ab49614520911e77cc85deae9433f2@macports.org> References: <042.f1ab49614520911e77cc85deae9433f2@macports.org> Message-ID: <057.3af63409fbb9fa7f61c92ec1fc86303d@macports.org> #53131: drumstick, vmpk (virtual midi piano keyboard): new ports -----------------------------+----------------- Reporter: mojca | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: drumstick vmpk | -----------------------------+----------------- Comment (by mojca): Nice, I didn't check your repository before starting either. There is absolutely no hurry, I'll need to take some time to test your ports as well. I tested `drumstick-vpiano` and it seems to be crashing once I press a button. The crash logs contain some references to `libc++`, but I'm not sure where exactly they come from. At least the version 1.0.2 compiles against `libstdc++`. Apparently I'll have to test on a newer OS. Just curious, why does your port use the `cxx11` portgroup? I can imagine that this is indeed the only way to make it work, but I would like to understand. (Maybe version 1.1.0 is the one that requires C++11?) I added drumstick just because I vmpk asked for `drumstick-rt` during configuration. Without testing anything, you might perhaps have any clue why {{{ -DQt5LinguistTools_DIR=${prefix}/libexec/qt5/lib/cmake/Qt5LinguistTools/ }}} is needed to find `Qt5LinguistToolsConfig.cmake`. That is: why doesn't the qt5 PortGroup take care of finding its location or why doesn't Qt5 put the cmake files to a more reasonable location? (Let me guess: your patches for Qt5 already fix the issue.) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 18:57:15 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 18:57:15 -0000 Subject: [MacPorts] #53129: (10.5.8PPC) CCTools - Fetch Failes In-Reply-To: <044.ba00bff09faf7c49f492b9618c3bcc1f@macports.org> References: <044.ba00bff09faf7c49f492b9618c3bcc1f@macports.org> Message-ID: <059.4507e2917a24144c5ba4a6075d4f5003@macports.org> #53129: (10.5.8PPC) CCTools - Fetch Failes -------------------------+---------------------- Reporter: mrkapqa | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: worksforme | Keywords: leopard Port: cctools | -------------------------+---------------------- Changes (by jeremyhu): * status: assigned => closed * resolution: => worksforme Comment: While those are http:// URLs, opensource.apple.com redirects to https://opensource.apple.com/tarballs/ld64/ld64-274.1.tar.gz, and Leopard's libcurl+OpenSSL are too old. I suggest you update base to use libcurl from MacPorts instead of Leopard. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 19:39:44 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 19:39:44 -0000 Subject: [MacPorts] #53131: drumstick, vmpk (virtual midi piano keyboard): new ports In-Reply-To: <042.f1ab49614520911e77cc85deae9433f2@macports.org> References: <042.f1ab49614520911e77cc85deae9433f2@macports.org> Message-ID: <057.6e48d2a5f158b9157ff6eb0b0404bd35@macports.org> #53131: drumstick, vmpk (virtual midi piano keyboard): new ports -----------------------------+----------------- Reporter: mojca | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: drumstick vmpk | -----------------------------+----------------- Comment (by RJVB): Replying to [comment:2 mojca]: > I tested `drumstick-vpiano` and it seems to be crashing once I press a button. The Not for me... > Just curious, why does your port use the `cxx11` portgroup? I can imagine that this I must have seen a reference to C++11 somewhere. Using that PortGroup is a "noop" on 10.9 and up because those already use libc++ as the system C++ runtime. You're on 10.9 too, no? > Without testing anything, you might perhaps have any clue why > {{{ > -DQt5LinguistTools_DIR=${prefix}/libexec/qt5/lib/cmake/Qt5LinguistTools/ > }}} > is needed to find `Qt5LinguistToolsConfig.cmake`. That is: why doesn't the qt5 PortGroup take care of finding its location or why doesn't Qt5 put the cmake files to a more reasonable location? > (Let me guess: your patches for Qt5 already fix the issue.) To answer that question first: yes and no. There's no need to patch Qt for that, just to let it install the files to a standard location, and that's what my port:qt5-kde does. Installing everything somewhere under libexec is nice and easy to avoid conflicts with other Qt ports, but makes things a lot more annoying for dependents. In case of Qt it isn't even necessary, and I had sufficient proof of that by the time Michael and mcalhoun started making their ports co-installable. Mcalhoun's Qt5 PortGroup does define `qt_cmake_module_dir` which you can add to CMake's CMAKE_MODULE_PATH, but even the cmake 1.1 portgroup doesn't provide an easy API to append elements to that path. That's something I should have realised before... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 19:58:52 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 19:58:52 -0000 Subject: [MacPorts] #52910: glbinding 2.1.1 submission In-Reply-To: <058.43f97ed30a6fdabdf3b11fe6c21818e3@macports.org> References: <058.43f97ed30a6fdabdf3b11fe6c21818e3@macports.org> Message-ID: <073.b3904f0815baf8780427940831b38fbd@macports.org> #52910: glbinding 2.1.1 submission ------------------------------------+-------------------------------- Reporter: ken-cunningham-webuse | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: glbinding | ------------------------------------+-------------------------------- Comment (by michaelld): There's a little more work to be done. I think all of this should be pushed back upstream, if nothing else than for their information. I'm going to attach a tarball of the current whole proposed directory structure, with my updates listed below in place. So ... IMHO, you need to address (2) and (5) for full port functionality. 1) I'm not sure what SYSTEM_DIR_INSTALL is supposed to do internally, but checking for just /usr and /usr/local is pretty limiting. There has got to be a better way to do whatever they think they are doing with this variable that is more generic. Your patch is good enough for MacPorts' needs. 2) This project stealth-links against other ports under specific variants. For example, if Qt5 is install then +examples will use the qt5 (>= 5.1) install without requiring is as a dependency. I don't think you want qt5-qtbase as a required dependency for this variant; I think it's best off as a separate variant (e.g., "qt_examples"). But, there needs to be an OPTION to select this on or off that's honored. Stealth-linking isn't a good idea. I don't know what other stealth-linking is going on; haven't had time to check. {{{ $ port installed "glbi*" glbinding-devel @20161219_0+docs+examples (active) $ port contents glbinding-devel | grep -i qt /opt/local/share/glbinding/cubescape-qt.app/Contents/Info.plist /opt/local/share/glbinding/cubescape-qt.app/Contents/MacOS/cubescape-qt $ otool -L $(port contents glbinding-devel | grep MacOS) | grep -i qt /opt/local/share/glbinding/cubescape-qt.app/Contents/MacOS/cubescape-qt: /opt/local/libexec/qt5/lib/QtWidgets.framework/Versions/5/QtWidgets (compatibility version 5.6.0, current version 5.6.2) /opt/local/libexec/qt5/lib/QtGui.framework/Versions/5/QtGui (compatibility version 5.6.0, current version 5.6.2) /opt/local/libexec/qt5/lib/QtCore.framework/Versions/5/QtCore (compatibility version 5.6.0, current version 5.6.2) $ port rdeps glbinding-devel +docs +examples | grep -i qt $ }}} 3) When building documentation with doxygen, also include path:bin/dot:graphviz for dot (graph) files; I added this in already. 4) For many actively-developed ports, having a release and devel version makes sense. I do this for many of mine & other MPdevs also do. I added in the code to the Portfile to do this properly. 5) cmake files are usually placed into ${prefix}/share/cmake . No so for this port by default: {{{ $ port contents glbinding-devel | grep cmake /opt/local/share/glbinding/cmake/glbinding/glbinding-export- release.cmake /opt/local/share/glbinding/cmake/glbinding/glbinding-export.cmake /opt/local/share/glbinding/glbinding-config.cmake }}} I haven't looked into how to change this install directory, but these devs seem to make such changes pretty simple. I'd much prefer to see the cmake files in their correct directory rather than a project-specific one; just easier to find. Ideally this would be set via configure.args as a way to override the default provided. See, e.g., gr-ais and the variable CMAKE_MODULES_DIR in the patch and top-level CMakeLists.txt for one way to do this. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 19:59:30 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 19:59:30 -0000 Subject: [MacPorts] #52910: glbinding 2.1.1 submission In-Reply-To: <058.43f97ed30a6fdabdf3b11fe6c21818e3@macports.org> References: <058.43f97ed30a6fdabdf3b11fe6c21818e3@macports.org> Message-ID: <073.3b9a46b9a17b7114b6e347bb8a6e0c90@macports.org> #52910: glbinding 2.1.1 submission ------------------------------------+-------------------------------- Reporter: ken-cunningham-webuse | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: glbinding | ------------------------------------+-------------------------------- Changes (by michaelld): * Attachment "glbinding_mld_0.tar.bz2" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 19:59:54 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 19:59:54 -0000 Subject: [MacPorts] #52927: cpplocate submission In-Reply-To: <058.b214ea1ffb947dd392cd255bad94914e@macports.org> References: <058.b214ea1ffb947dd392cd255bad94914e@macports.org> Message-ID: <073.c02c070d616bbb74c35d9a153d6467aa@macports.org> #52927: cpplocate submission ------------------------------------+-------------------------------- Reporter: ken-cunningham-webuse | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: cpplocate | ------------------------------------+-------------------------------- Comment (by michaelld): There's a little more work to be done. I think all of this should be pushed back upstream, if nothing else than for their information. I'm going to attach a tarball of the current whole proposed directory structure, with my updates listed below in place. So ... IMHO, you need to address (3) for full port functionality. 1) I'm not sure what SYSTEM_DIR_INSTALL is supposed to do internally, but checking for just /usr and /usr/local is pretty limiting. There has got to be a better way to do whatever they think they are doing with this variable that is more generic. Your patch is good enough for MacPorts' needs. 2) When building documentation with doxygen, also include path:bin/dot:graphviz for dot (graph) files; I added this in already. 3) cmake files are usually placed into ${prefix}/share/cmake . No so for this port by default: {{{ $ port contents cpplocate | grep cmake /opt/local/share/cpplocate/cmake/ModuleInformation.cmake /opt/local/share/cpplocate/cmake/cpplocate/cpplocate-export- release.cmake /opt/local/share/cpplocate/cmake/cpplocate/cpplocate-export.cmake /opt/local/share/cpplocate/cpplocate-config.cmake }}} I haven't looked into how to change this install directory, but these devs seem to make such changes pretty simple. I'd much prefer to see the cmake files in their correct directory rather than a project-specific one; just easier to find. Ideally this would be set via configure.args as a way to override the default provided. See, e.g., gr-ais and the variable CMAKE_MODULES_DIR in the patch and top-level CMakeLists.txt for one way to do this. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 20:00:11 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 20:00:11 -0000 Subject: [MacPorts] #52927: cpplocate submission In-Reply-To: <058.b214ea1ffb947dd392cd255bad94914e@macports.org> References: <058.b214ea1ffb947dd392cd255bad94914e@macports.org> Message-ID: <073.2d56be1e53415728d44c71d8b2330ec4@macports.org> #52927: cpplocate submission ------------------------------------+-------------------------------- Reporter: ken-cunningham-webuse | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: cpplocate | ------------------------------------+-------------------------------- Changes (by michaelld): * Attachment "cpplocate_mld_0.tar.bz2" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 20:01:53 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 20:01:53 -0000 Subject: [MacPorts] #53083: VLC: fails to build on Sierra due to QtKit In-Reply-To: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> References: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> Message-ID: <056.56626ed0a51a65fc2a73b03cc116c5a5@macports.org> #53083: VLC: fails to build on Sierra due to QtKit ---------------------+-------------------- Reporter: mkae | Owner: mkae Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: sierra Port: VLC | ---------------------+-------------------- Comment (by mkae): In [changeset:"645127acebda70d5d70f0e1113942493ac07517d/macports-ports" 645127ac/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="645127acebda70d5d70f0e1113942493ac07517d" VLC: fix build on Sierra Closes: https://trac.macports.org/ticket/53083 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 20:14:07 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 20:14:07 -0000 Subject: [MacPorts] #52910: glbinding 2.1.1 submission In-Reply-To: <058.43f97ed30a6fdabdf3b11fe6c21818e3@macports.org> References: <058.43f97ed30a6fdabdf3b11fe6c21818e3@macports.org> Message-ID: <073.3d0736c2db00c90d08149bb2c2fc975c@macports.org> #52910: glbinding 2.1.1 submission ------------------------------------+-------------------------------- Reporter: ken-cunningham-webuse | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: glbinding | ------------------------------------+-------------------------------- Comment (by kencu): greatly appreciate the time you spent. Thanks!. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 20:16:16 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 20:16:16 -0000 Subject: [MacPorts] #53130: iTerm2 3.0.13 build failure In-Reply-To: <047.23e8616a492b84ae8ad967f6d87c79a6@macports.org> References: <047.23e8616a492b84ae8ad967f6d87c79a6@macports.org> Message-ID: <062.5d79b1506f747517e071d08577149da1@macports.org> #53130: iTerm2 3.0.13 build failure -------------------------+---------------------- Reporter: EJFielding | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: duplicate | Keywords: yosemite Port: iTerm2 | -------------------------+---------------------- Changes (by ryandesign): * keywords: => yosemite * status: new => closed * resolution: => duplicate * port: => iTerm2 * cc: markemer (added) Comment: Duplicate of #51983. The current version of iTerm2 requires OS X 10.11 or later to build. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 20:18:55 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 20:18:55 -0000 Subject: [MacPorts] #51983: iTerm2 upgrade fails In-Reply-To: <044.c50edffe9a69eae3123be2bf8201f50c@macports.org> References: <044.c50edffe9a69eae3123be2bf8201f50c@macports.org> Message-ID: <059.a145945059ac3542080df2879fe103a0@macports.org> #51983: iTerm2 upgrade fails ----------------------+--------------------------------------------- Reporter: watsodw | Owner: markemer Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: mountainlion mavericks yosemite Port: iTerm2 | ----------------------+--------------------------------------------- Changes (by ryandesign): * cc: EJFielding (added) Comment: Replying to [comment:4 markemer]: > Maybe we can build a clang on 10.8 that will build iterm2? I don't know that the compiler capabilities are the problem. It might be a requirement for the 10.11 or newer SDK. If it is a compiler requirement, we have no way to use a MacPorts-provided compiler with xcodebuild (#40762), which is what iTerm2 builds with. Has duplicate #53130. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 20:22:26 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 20:22:26 -0000 Subject: [MacPorts] #53090: py-pyqt* multiple Qt depspecs In-Reply-To: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> References: <041.398fe32a1c44f487e5d2dac70eb1d843@macports.org> Message-ID: <056.d345a07a48841cf3b7d94f4ca45e8bac@macports.org> #53090: py-pyqt* multiple Qt depspecs --------------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: py-pyqt4 py-pyqt5 | --------------------------------+---------------------- Changes (by mkae): * status: reopened => closed * resolution: => fixed Comment: In [changeset:"8582b1233d323493a8c5b9f60848122919c014da/macports-ports" 8582b123/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="8582b1233d323493a8c5b9f60848122919c014da" py-pyqt5: fix previously wrongly applied patch Finally fixes: https://trac.macports.org/ticket/53090 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 20:23:15 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 20:23:15 -0000 Subject: [MacPorts] #53130: iTerm2 3.0.13 build failure In-Reply-To: <047.23e8616a492b84ae8ad967f6d87c79a6@macports.org> References: <047.23e8616a492b84ae8ad967f6d87c79a6@macports.org> Message-ID: <062.d9e2c7bbcb30ac6f75660e5e6e58a4ff@macports.org> #53130: iTerm2 3.0.13 build failure -------------------------+---------------------- Reporter: EJFielding | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: duplicate | Keywords: yosemite Port: iTerm2 | -------------------------+---------------------- Comment (by EJFielding): Thanks for the fast response. Sorry I did not find the other ticket when I searched on iTerm2. Maybe the iTerm2 port could check the OS X version before attempting the build? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 20:26:51 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 20:26:51 -0000 Subject: [MacPorts] #53083: VLC: fails to build on Sierra due to QtKit In-Reply-To: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> References: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> Message-ID: <056.83b1b92418965a238477620488501265@macports.org> #53083: VLC: fails to build on Sierra due to QtKit ---------------------+-------------------- Reporter: mkae | Owner: mkae Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: sierra Port: VLC | ---------------------+-------------------- Comment (by mkae): So, the Sierra buildbot is [https://build.macports.org/builders/ports-10.12_x86_64-watcher/builds/2596 finally happy] and caught only warnings now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 20:43:14 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 20:43:14 -0000 Subject: [MacPorts] #53132: VLC fails to build its +qt5 variant Message-ID: <041.7781cd90aa02f971114060658305dd30@macports.org> #53132: VLC fails to build its +qt5 variant --------------------+----------------- Reporter: mkae | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: VLC --------------------+----------------- VLC alone builds fine on all buildbots, but the qt5 variant seems to have trouble, at least on El Capitan (being the only system tested this on now): {{{ :info:build mv -f .deps/libqt4_plugin_la-actions_manager.Tpo .deps /libqt4_plugin_la-actions_manager.Plo :info:build ../../../doltlibtool --tag=CXX --mode=compile /usr/bin/clang++ -DHAVE_CONFIG_H -I. -I../../.. -DMODULE_STRING=\"$(p ="libqt4_plugin_la-recents. lo"; p="${p##*/}"; p="${p#lib}"; p="${p%_plugin*}"; p="${p%.lo}"; echo "$p")\" -D__PLUGIN__ -I../../../include -I../../../include -I/opt/local/include - D__unix__=1 -I/opt/local/lib/live/liveMedia/include -I/opt/local/var/macports/build/_Users_marko_WC_GIT_MP_mkae-macports- ports_multimedia_VLC/VLC/work/vlc-2.2.4/ contrib/include -I/opt/local/libexec/qt5/include/QtWidgets -I/opt/local/libexec/qt5/include -I/opt/local/libexec/qt5/include/QtGui -I/opt/local/libexec/qt5/ include -I/opt/local/libexec/qt5/include/QtCore -I/opt/local/libexec/qt5/include -pipe -Os -arch x86_64 -stdlib=libc++ -D_INTL_REDIRECT_MACROS -I/opt/local/var/ macports/build/_Users_marko_WC_GIT_MP_mkae-macports- ports_multimedia_VLC/VLC/work/vlc-2.2.4/contrib/include -Wall -Wextra -Wsign-compare -Wundef -Wpointer-arith -Wvolatile-register-var -fvisibility=hidden -O3 -ffast-math -funroll-loops -fomit-frame-pointer -MT libqt4_plugin_la-recents.lo -MD -MP -MF .deps/libqt4_plugin_la- recents.Tpo -c -o libqt4_plugin_la-recents.lo `test -f 'recents.cpp' || echo './'`recents.cpp :info:build 1 warning generated. :info:build mv -f .deps/libqt4_plugin_la-extensions_manager.Tpo .deps /libqt4_plugin_la-extensions_manager.Plo :info:build 2 warnings generated. :info:build mv -f .deps/libqt4_plugin_la-dialogs_provider.Tpo .deps /libqt4_plugin_la-dialogs_provider.Plo :info:build 4 warnings generated. :info:build make[7]: *** No rule to make target `util/searchlineedit_mac.mm', needed by `util/libqt4_plugin_la- searchlineedit_mac.lo'. Stop. :info:build make[7]: *** Waiting for unfinished jobs.... :info:build mv -f .deps/libqt4_plugin_la-menus.Tpo .deps/libqt4_plugin_la- menus.Plo :info:build In file included from recents.cpp:27: :info:build In file included from ./dialogs_provider.hpp:29: :info:build ../../../config.h:796:9: warning: 'static_assert' macro redefined [-Wmacro-redefined] :info:build #define static_assert _Static_assert :info:build ^ :info:build /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/__config:596:9: note: previous definition is here :info:build #define static_assert(__b, __m) \ :info:build ^ :info:build 1 warning generated. :info:build mv -f .deps/libqt4_plugin_la-recents.Tpo .deps /libqt4_plugin_la-recents.Plo :info:build make[7]: Leaving directory `/opt/local/var/macports/build /_Users_marko_WC_GIT_MP_mkae-macports- ports_multimedia_VLC/VLC/work/vlc-2.2.4/modules/gui/ qt4' :info:build make[6]: *** [all] Error 2 :info:build make[6]: Leaving directory `/opt/local/var/macports/build /_Users_marko_WC_GIT_MP_mkae-macports- ports_multimedia_VLC/VLC/work/vlc-2.2.4/modules/gui/ qt4' :info:build make[5]: *** [all-recursive] Error 1 :info:build make[5]: Leaving directory `/opt/local/var/macports/build /_Users_marko_WC_GIT_MP_mkae-macports- ports_multimedia_VLC/VLC/work/vlc-2.2.4/modules/gui' :info:build make[4]: *** [all] Error 2 :info:build make[4]: Leaving directory `/opt/local/var/macports/build /_Users_marko_WC_GIT_MP_mkae-macports- ports_multimedia_VLC/VLC/work/vlc-2.2.4/modules/gui' :info:build make[3]: *** [all-recursive] Error 1 :info:build make[3]: Leaving directory `/opt/local/var/macports/build /_Users_marko_WC_GIT_MP_mkae-macports- ports_multimedia_VLC/VLC/work/vlc-2.2.4/modules' :info:build make[2]: *** [all] Error 2 :info:build make[2]: Leaving directory `/opt/local/var/macports/build /_Users_marko_WC_GIT_MP_mkae-macports- ports_multimedia_VLC/VLC/work/vlc-2.2.4/modules' :info:build make[1]: *** [all-recursive] Error 1 :info:build make[1]: Leaving directory `/opt/local/var/macports/build /_Users_marko_WC_GIT_MP_mkae-macports- ports_multimedia_VLC/VLC/work/vlc-2.2.4' :info:build make: *** [all] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build /_Users_marko_WC_GIT_MP_mkae-macports- ports_multimedia_VLC/VLC/work/vlc-2.2.4' :info:build Command failed: cd "/opt/local/var/macports/build /_Users_marko_WC_GIT_MP_mkae-macports- ports_multimedia_VLC/VLC/work/vlc-2.2.4" && /usr/bin/make - j5 -w all DESTDIR=/opt/local/var/macports/build/_Users_marko_WC_GIT_MP_mkae- macports-ports_multimedia_VLC/VLC/work/vlc-2.2.4/dest_ignore V=1 :info:build Exit code: 2 :error:build org.macports.build for port VLC returned: command execution failed }}} Weird seeing {{{Qt4}}} stuff being built, although the {{{qt5}}} variant is wanted. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 20:45:04 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 20:45:04 -0000 Subject: [MacPorts] #51983: iTerm2 upgrade fails In-Reply-To: <044.c50edffe9a69eae3123be2bf8201f50c@macports.org> References: <044.c50edffe9a69eae3123be2bf8201f50c@macports.org> Message-ID: <059.c264a867313778225958f6eb4dec9e22@macports.org> #51983: iTerm2 upgrade fails ----------------------+--------------------------------------------- Reporter: watsodw | Owner: markemer Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: mountainlion mavericks yosemite Port: iTerm2 | ----------------------+--------------------------------------------- Comment (by EJFielding): I looked again at what I have already installed on my OS X 10.10.5 machine, and I have iTerm2 @3.0.5_0, so it seems the build of 3.0.5 was configured to run on 10.10. Maybe I got a 3.0.5 binary some time ago that was built on 10.11? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 20:54:16 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 20:54:16 -0000 Subject: [MacPorts] #53132: VLC fails to build its +qt5 variant In-Reply-To: <041.7781cd90aa02f971114060658305dd30@macports.org> References: <041.7781cd90aa02f971114060658305dd30@macports.org> Message-ID: <056.0e740c493b4c41bab90be71b345e4701@macports.org> #53132: VLC fails to build its +qt5 variant ---------------------+----------------- Reporter: mkae | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: VLC | ---------------------+----------------- Comment (by RJVB): To be honest, I'm not sure why I have preserved the Qt variants. They built at some point, but there's something fundamentally wrong in how they handle the event loop on OS X (IIRC not on the main thread where it has to be). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 20:58:28 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 20:58:28 -0000 Subject: [MacPorts] #53132: VLC fails to build its +qt5 variant In-Reply-To: <041.7781cd90aa02f971114060658305dd30@macports.org> References: <041.7781cd90aa02f971114060658305dd30@macports.org> Message-ID: <056.ecf08bfda12c06659b4001af832be26b@macports.org> #53132: VLC fails to build its +qt5 variant ---------------------+----------------- Reporter: mkae | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: VLC | ---------------------+----------------- Comment (by mkae): So, perhaps it's a good idea to keep some notes in {{{VLC}}}'s Portfile hinting that out?! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 21:02:38 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 21:02:38 -0000 Subject: [MacPorts] #52341: gpgme 1.7.0 fails to build when Qt5 is active In-Reply-To: <042.ff507f7ad43ff5959aaf8b9c98365fc0@macports.org> References: <042.ff507f7ad43ff5959aaf8b9c98365fc0@macports.org> Message-ID: <057.179d99b7df78beb353baf2775eb6898d@macports.org> #52341: gpgme 1.7.0 fails to build when Qt5 is active ---------------------+---------------------- Reporter: blair | Owner: dbevans Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: gpgme | ---------------------+---------------------- Changes (by mkae): * cc: RJVB (added) Comment: René, I guess this is superseded by #53122, right? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 21:21:48 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 21:21:48 -0000 Subject: [MacPorts] #52341: gpgme 1.7.0 fails to build when Qt5 is active In-Reply-To: <042.ff507f7ad43ff5959aaf8b9c98365fc0@macports.org> References: <042.ff507f7ad43ff5959aaf8b9c98365fc0@macports.org> Message-ID: <057.7373c2d8ef9ce0dd31e52492acda16ed@macports.org> #52341: gpgme 1.7.0 fails to build when Qt5 is active ---------------------+---------------------- Reporter: blair | Owner: dbevans Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: gpgme | ---------------------+---------------------- Comment (by RJVB): Not really, and I think the issue was resolved already in r153086. #53122 is in part about adding support for Qt5. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 21:22:40 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 21:22:40 -0000 Subject: [MacPorts] #53132: VLC fails to build its +qt5 variant In-Reply-To: <041.7781cd90aa02f971114060658305dd30@macports.org> References: <041.7781cd90aa02f971114060658305dd30@macports.org> Message-ID: <056.cf399b44ec6c9bf41228b934fc1bb2cf@macports.org> #53132: VLC fails to build its +qt5 variant ---------------------+----------------- Reporter: mkae | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: VLC | ---------------------+----------------- Comment (by RJVB): The variant description is clear enough already, don't you think? {{{ qt4: Build using Qt4 UI. This will use qt4-mac. Experimental and probably dysfunctional * conflicts with qt5 qt5: Build using Qt5 UI. This will use qt5-mac. Experimental and probably dysfunctional * conflicts with qt4 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 21:23:38 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 21:23:38 -0000 Subject: [MacPorts] #52341: gpgme 1.7.0 fails to build when Qt5 is active In-Reply-To: <042.ff507f7ad43ff5959aaf8b9c98365fc0@macports.org> References: <042.ff507f7ad43ff5959aaf8b9c98365fc0@macports.org> Message-ID: <057.a126510c7ce2f48075eb26c1758d5c74@macports.org> #52341: gpgme 1.7.0 fails to build when Qt5 is active ---------------------+---------------------- Reporter: blair | Owner: dbevans Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: gpgme | ---------------------+---------------------- Comment (by mkae): David, can this issue be closed then? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 21:26:48 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 21:26:48 -0000 Subject: [MacPorts] #53132: VLC fails to build its +qt5 variant In-Reply-To: <041.7781cd90aa02f971114060658305dd30@macports.org> References: <041.7781cd90aa02f971114060658305dd30@macports.org> Message-ID: <056.f32099b72c8d1fe23d3cc043f6ad3631@macports.org> #53132: VLC fails to build its +qt5 variant ---------------------+----------------- Reporter: mkae | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: VLC | ---------------------+----------------- Comment (by mkae): Yes, it indeed is, sorry for not checking before commenting. :) So, shall we close this issue as "WontFix" for now and let anyone reopen it if there are new suggestions how to tackle this? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 21:37:53 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 21:37:53 -0000 Subject: [MacPorts] #52341: gpgme 1.7.0 fails to build when Qt5 is active In-Reply-To: <042.ff507f7ad43ff5959aaf8b9c98365fc0@macports.org> References: <042.ff507f7ad43ff5959aaf8b9c98365fc0@macports.org> Message-ID: <057.600cebaded93f1181839dadb1461d842@macports.org> #52341: gpgme 1.7.0 fails to build when Qt5 is active ---------------------+--------------------- Reporter: blair | Owner: dbevans Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: gpgme | ---------------------+--------------------- Changes (by dbevans): * status: assigned => closed * resolution: => fixed Comment: Replying to [comment:6 mkae]: > David, can this issue be closed then? Yes, the originally reported failure no longer occurs although python and qt5 support are currently disabled as we all know. As René says the Qt part of #53122 addresses adding Qt5 support. Python remains to do. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 21:53:40 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 21:53:40 -0000 Subject: [MacPorts] #53110: libomp and clang-3.8 fail on Lion In-Reply-To: <043.c5ec93166b62879945bea5439c7783d1@macports.org> References: <043.c5ec93166b62879945bea5439c7783d1@macports.org> Message-ID: <058.7049c21c01b6a9c354c3fb20858bc027@macports.org> #53110: libomp and clang-3.8 fail on Lion --------------------------------+------------------- Reporter: RobK88 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: libomp, clang-3.8 | --------------------------------+------------------- Comment (by eborisch): How's this look for fixing this? {{{#!diff @@ -67,8 +67,19 @@ if {${subport} ne ${name}} { cmake.out_of_source yes -# According to documentation builds with clang >= 3.3 -compiler.blacklist-append {clang < 500} *gcc* +# According to documentation builds with clang >= 3.3, but macports- clang-3.x +# for x >= 8 depend on this port. Avoid circular dependencies. +if {[vercmp $xcodeversion 5.0] >= 0} { + # Use the system compiler and have no extra build deps. + configure.compiler clang +} else { + # Install a clang from MP that we can use to build. + compiler.whitelist macports-clang-3.7 \ + macports-clang-3.6 \ + macports-clang-3.5 \ + macports-clang-3.4 \ + macports-clang-3.3 +} default_variants +universal }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 21:56:05 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 21:56:05 -0000 Subject: [MacPorts] #53083: VLC: fails to build on Sierra due to QtKit In-Reply-To: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> References: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> Message-ID: <056.ad6f8a6f2c7bcf86f662df674aca1929@macports.org> #53083: VLC: fails to build on Sierra due to QtKit ---------------------+-------------------- Reporter: mkae | Owner: mkae Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: sierra Port: VLC | ---------------------+-------------------- Comment (by dbevans): I haven't had an opportunity to test VLC on Sierra as yet (that machine is otherwise busy) but does this patch actually work after building? As I understand it the patch just removes references to QTKit in open.m without making any suitable replacement. Perhaps a more rigorous fix would be to port open.m from QTKit to AVFoundation which is the recommended replacement on Sierra. This has been done recently in upstream VLC master although it hasn't been backported to the 2.2 maintenance branch. See https://git.videolan.org/?p=vlc.git;a=commitdiff;h=183373239d8ab567c2a2f014c88b93b461e08b35 There's been a lot of water under the bridge between our 2.2.x version and master but at least this might serve as a guide on how to proceed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 21:57:58 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 21:57:58 -0000 Subject: [MacPorts] #53132: VLC fails to build its +qt5 variant In-Reply-To: <041.7781cd90aa02f971114060658305dd30@macports.org> References: <041.7781cd90aa02f971114060658305dd30@macports.org> Message-ID: <056.802e1bc57f9abd69f5cc7f2e9da37109@macports.org> #53132: VLC fails to build its +qt5 variant ---------------------+----------------- Reporter: mkae | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: VLC | ---------------------+----------------- Comment (by RJVB): Fine with me. In fact, I think we could remove the Qt variants. IIRC they're not supported for Mac by VideoLan, and they have little interest since there's a good native interface. We can also wait and see when VLC 3 is released. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 22:13:56 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 22:13:56 -0000 Subject: [MacPorts] #53122: gpgme : upgrade to 1.8.0 and +qt5 variant In-Reply-To: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> References: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> Message-ID: <056.0dcd667e345d3122052e382dac0be8b4@macports.org> #53122: gpgme : upgrade to 1.8.0 and +qt5 variant ---------------------+------------------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch upstream Port: gpgme | ---------------------+------------------------------- Comment (by dbevans): Will do. Should have something by the end of this week. Lots of stuff wants to get done before then. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 22:19:36 2016 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2016 22:19:36 -0000 Subject: [MacPorts] #53083: VLC: fails to build on Sierra due to QtKit In-Reply-To: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> References: <041.cdf4f31539738eb6b5aa8636a0aba43f@macports.org> Message-ID: <056.08599c87f7eee6b722b88c520c23574e@macports.org> #53083: VLC: fails to build on Sierra due to QtKit ---------------------+-------------------- Reporter: mkae | Owner: mkae Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: sierra Port: VLC | ---------------------+-------------------- Comment (by RJVB): Evidently I tested the patch locally. On 10.9, but the principle of stripping QtKit from the file dialog should have the same effects everywhere. If someone feels like backporting the QTKit->AVF conversion to 2.2.x, by all means go ahead and I'll even test it. But I'm not going to do this myself. Frankly, I couldn't even determine exactly what was missing from the dialog when I tried it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 00:49:24 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 00:49:24 -0000 Subject: [MacPorts] #53133: sbt @0.13.11: upgrade to 0.13.13 Message-ID: <048.c986743b9245fa762ef56417535fc28b@macports.org> #53133: sbt @0.13.11: upgrade to 0.13.13 -------------------------+----------------- Reporter: nhojpatrick | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: sbt -------------------------+----------------- I can't see an Owner's field as per the "Ticket Guidelines", so have put it in the CC field. Has Pull Request -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 00:53:26 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 00:53:26 -0000 Subject: [MacPorts] #53133: sbt @0.13.11: upgrade to 0.13.13 In-Reply-To: <048.c986743b9245fa762ef56417535fc28b@macports.org> References: <048.c986743b9245fa762ef56417535fc28b@macports.org> Message-ID: <063.01bac357293a0abb1b0fc1a68a810a37@macports.org> #53133: sbt @0.13.11: upgrade to 0.13.13 --------------------------+---------------------- Reporter: nhojpatrick | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: sbt | --------------------------+---------------------- Comment (by nhojpatrick): Pull Request https://github.com/macports/macports-ports/pull/108 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 01:18:05 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 01:18:05 -0000 Subject: [MacPorts] #53087: ntp @4.2.8p9: libressl compatibility patch In-Reply-To: <046.c4c29610c66168770169a645785ef6c3@macports.org> References: <046.c4c29610c66168770169a645785ef6c3@macports.org> Message-ID: <061.08dfc5386c9305ab6a4609d992989397@macports.org> #53087: ntp @4.2.8p9: libressl compatibility patch ------------------------+---------------------- Reporter: jerryyhom | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: haspatch Port: ntp | ------------------------+---------------------- Comment (by jerryyhom): Well, NTP seems to be refusing bug/patch reports from outsiders, or their email system is on lockdown. If you have a bug account with NTP, I suggest you submit the patch. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 03:19:36 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 03:19:36 -0000 Subject: [MacPorts] #53059: octave-audio @1.1.4: patchfile patch-objcflags.diff is missing In-Reply-To: <050.a1ae3ff9782c98acde09c42ac011f456@macports.org> References: <050.a1ae3ff9782c98acde09c42ac011f456@macports.org> Message-ID: <065.e037a806e931b83820d73c5ad909cb85@macports.org> #53059: octave-audio @1.1.4: patchfile patch-objcflags.diff is missing ----------------------------+--------------------------------- Reporter: gjolleyrogers | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: octave-audio | ----------------------------+--------------------------------- Comment (by gjolleyrogers): thanks -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 07:58:19 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 07:58:19 -0000 Subject: [MacPorts] #53110: libomp and clang-3.8 fail on Lion In-Reply-To: <043.c5ec93166b62879945bea5439c7783d1@macports.org> References: <043.c5ec93166b62879945bea5439c7783d1@macports.org> Message-ID: <058.3b0e30aef2180c00375f8584ee45998f@macports.org> #53110: libomp and clang-3.8 fail on Lion --------------------------------+------------------- Reporter: RobK88 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: libomp, clang-3.8 | --------------------------------+------------------- Comment (by jeremyhu): Don't use clang-3.3. It's only purpose for existing is bootstrapping newer clang on Leopard and webkit-gtk-2.0. I suggest you blacklist based on whether or not the compiler is installed, similar to what we do in the llvm ports: {{{ foreach ver {3.8 3.9 devel} { if {![file exists ${prefix}/bin/clang-mp-${ver}]} { compiler.blacklist-append macports-clang-${ver} } } }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 08:36:29 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 08:36:29 -0000 Subject: [MacPorts] #53110: libomp and clang-3.8 fail on Lion In-Reply-To: <043.c5ec93166b62879945bea5439c7783d1@macports.org> References: <043.c5ec93166b62879945bea5439c7783d1@macports.org> Message-ID: <058.41cb3e5c963ab4f53e9c6d016c2cf34b@macports.org> #53110: libomp and clang-3.8 fail on Lion --------------------------------+---------------------- Reporter: RobK88 | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: libomp, clang-3.8 | --------------------------------+---------------------- Changes (by jeremyhu): * owner: => jeremyhu * status: new => closed * resolution: => fixed Comment: In [changeset:"2d700e8b25f962cd1a0f73f9889d8b3b4c7dd27a/macports-ports" 2d700e8b/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="2d700e8b25f962cd1a0f73f9889d8b3b4c7dd27a" libomp: Avoid dependency cycle with clang ports Fixes https://trac.macports.org/ticket/53110 Signed-off-by: Jeremy Huddleston Sequoia }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 11:52:53 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 11:52:53 -0000 Subject: [MacPorts] #53134: Chicken of VNC crash after ports upgrade Message-ID: <045.0d1b05e5b977c70d45dc263cce6eb207@macports.org> #53134: Chicken of VNC crash after ports upgrade ----------------------+------------------------------ Reporter: emiglior | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: cotvnc @2.2b2_0 ----------------------+------------------------------ Dear experts, I am using a MB with osx 10.10.5 After running a port upgrade (yesterday) I have crash when launching ChickenOfVNC. Below you can find the dump I get after the crash. Is there any mismatched/missing library? Thanks in advance for the assistance. Regards Ernesto ---- Process: Chicken [310] Path: /Applications/MacPorts/Chicken.app/Contents/MacOS/Chicken Identifier: net.sourceforge.chicken Version: 2.2b2 (2.2b2) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: Chicken [310] User ID: 501 Date/Time: 2016-12-22 12:35:38.961 +0100 OS Version: Mac OS X 10.10.5 (14F2109) Report Version: 11 Anonymous UUID: E3896221-6692-E1BE-7C31-A9B65EC7063F Time Awake Since Boot: 66 seconds Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00007f9d00000018 VM Regions Near 0x7f9d00000018: CG backing stores 000000010ec21000-000000010eef6000 [ 2900K] rw-/rw- SM=SHM --> MALLOC_TINY 00007f9dd9400000-00007f9dd9500000 [ 1024K] rw-/rwx SM=PRV Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 net.sourceforge.chicken 0x0000000106db4cac 0x106da0000 + 85164 1 com.apple.AppKit 0x00007fff91d7f689 -[NSView _drawRect:clip:] + 4238 2 com.apple.AppKit 0x00007fff91d7dcfa -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1875 3 com.apple.AppKit 0x00007fff91d7e0fe -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2903 4 com.apple.AppKit 0x00007fff91d7e0fe -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2903 5 com.apple.AppKit 0x00007fff91d7e0fe -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2903 6 com.apple.AppKit 0x00007fff91d7e0fe -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2903 7 com.apple.AppKit 0x00007fff91d7bb96 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 913 8 com.apple.AppKit 0x00007fff91d7b2f3 -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 333 9 com.apple.AppKit 0x00007fff91d7768b -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 2761 10 com.apple.AppKit 0x00007fff91d2f1ae -[NSView displayIfNeeded] + 1876 11 com.apple.AppKit 0x00007fff91d2ea09 -[NSWindow displayIfNeeded] + 236 12 com.apple.AppKit 0x00007fff91d2e672 _handleWindowNeedsDisplayOrLayoutOrUpdateConstraints + 936 13 com.apple.AppKit 0x00007fff92464171 __83-[NSWindow _postWindowNeedsDisplayOrLayoutOrUpdateConstraintsUnlessPostingDisabled]_block_invoke1540 + 46 14 com.apple.CoreFoundation 0x00007fff8fe5b127 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 15 com.apple.CoreFoundation 0x00007fff8fe5b080 __CFRunLoopDoObservers + 368 16 com.apple.CoreFoundation 0x00007fff8fe4d188 __CFRunLoopRun + 872 17 com.apple.CoreFoundation 0x00007fff8fe4cbd8 CFRunLoopRunSpecific + 296 18 com.apple.HIToolbox 0x00007fff9071156f RunCurrentEventLoopInMode + 235 19 com.apple.HIToolbox 0x00007fff907112ea ReceiveNextEventCommon + 431 20 com.apple.HIToolbox 0x00007fff9071112b _BlockUntilNextEventMatchingListInModeWithFilter + 71 21 com.apple.AppKit 0x00007fff91d2b8ab _DPSNextEvent + 978 22 com.apple.AppKit 0x00007fff91d2ae58 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346 23 com.apple.AppKit 0x00007fff91d20af3 -[NSApplication run] + 594 24 com.apple.AppKit 0x00007fff91c9d244 NSApplicationMain + 1832 25 libdyld.dylib 0x00007fff9761d5c9 start + 1 Thread 1:: Dispatch queue: com.apple.libdispatch-manager 0 libsystem_kernel.dylib 0x00007fff8ae10232 kevent64 + 10 1 libdispatch.dylib 0x00007fff9594a26e _dispatch_mgr_thread + 52 Thread 2: 0 libsystem_kernel.dylib 0x00007fff8ae0f94a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread + 13 Thread 3: 0 libsystem_kernel.dylib 0x00007fff8ae0f94a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread + 13 Thread 4:: Dispatch queue: NSUIHeartBeatOperationQueue :: NSOperation 0x7f9dd9513dd0 (QOS: USER_INITIATED) 0 libsystem_kernel.dylib 0x00007fff8ae0f166 __psynch_mutexwait + 10 1 com.apple.Foundation 0x00007fff95c9f817 -[NSLock lock] + 145 2 com.apple.AppKit 0x00007fff91fadbcf __37-[NSUIHeartBeat updateHeartBeatState]_block_invoke142 + 60 3 com.apple.Foundation 0x00007fff95cf68b8 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 7 4 com.apple.Foundation 0x00007fff95cf6685 -[NSBlockOperation main] + 97 5 com.apple.Foundation 0x00007fff95cf5b3c -[__NSOperationInternal _start:] + 653 6 com.apple.Foundation 0x00007fff95cf5613 __NSOQSchedule_f + 184 7 libdispatch.dylib 0x00007fff95945e73 _dispatch_client_callout + 8 8 libdispatch.dylib 0x00007fff959495cd _dispatch_queue_drain + 1100 9 libdispatch.dylib 0x00007fff95949030 _dispatch_queue_invoke + 202 10 libdispatch.dylib 0x00007fff95948bef _dispatch_root_queue_drain + 463 11 libdispatch.dylib 0x00007fff95948a1c _dispatch_worker_thread3 + 91 12 libsystem_pthread.dylib 0x00007fff8efd5a9d _pthread_wqthread + 729 13 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread + 13 Thread 5: 0 libsystem_kernel.dylib 0x00007fff8ae0f94a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread + 13 Thread 6:: com.apple.CFSocket.private 0 libsystem_kernel.dylib 0x00007fff8ae0f3fa __select + 10 1 libsystem_pthread.dylib 0x00007fff8efd605a _pthread_body + 131 2 libsystem_pthread.dylib 0x00007fff8efd5fd7 _pthread_start + 176 3 libsystem_pthread.dylib 0x00007fff8efd33ed thread_start + 13 Thread 7: 0 libsystem_kernel.dylib 0x00007fff8ae0a4de mach_msg_trap + 10 1 libsystem_kernel.dylib 0x00007fff8ae0964f mach_msg + 55 2 com.apple.CoreFoundation 0x00007fff8fe4deb4 __CFRunLoopServiceMachPort + 212 3 com.apple.CoreFoundation 0x00007fff8fe4d37b __CFRunLoopRun + 1371 4 com.apple.CoreFoundation 0x00007fff8fe4cbd8 CFRunLoopRunSpecific + 296 5 com.apple.AppKit 0x00007fff91df356b _NSEventThread + 137 6 libsystem_pthread.dylib 0x00007fff8efd605a _pthread_body + 131 7 libsystem_pthread.dylib 0x00007fff8efd5fd7 _pthread_start + 176 8 libsystem_pthread.dylib 0x00007fff8efd33ed thread_start + 13 Thread 8: 0 libsystem_kernel.dylib 0x00007fff8ae0f94a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread + 13 Thread 9: 0 libsystem_kernel.dylib 0x00007fff8ae0f94a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread + 13 Thread 10: 0 libsystem_kernel.dylib 0x00007fff8ae0f94a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread + 13 Thread 11: 0 libsystem_kernel.dylib 0x00007fff8ae0f94a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread + 13 Thread 12: 0 libsystem_kernel.dylib 0x00007fff8ae0f94a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread + 13 Thread 13:: com.apple.appkit-heartbeat 0 libsystem_kernel.dylib 0x00007fff8ae0f48a __semwait_signal + 10 1 libsystem_c.dylib 0x00007fff939f6e34 usleep + 54 2 com.apple.AppKit 0x00007fff91fa1e43 -[NSUIHeartBeat _heartBeatThread:] + 2376 3 com.apple.Foundation 0x00007fff95cdae92 __NSThread__main__ + 1345 4 libsystem_pthread.dylib 0x00007fff8efd605a _pthread_body + 131 5 libsystem_pthread.dylib 0x00007fff8efd5fd7 _pthread_start + 176 6 libsystem_pthread.dylib 0x00007fff8efd33ed thread_start + 13 Thread 0 crashed with X86 Thread State (64-bit): rax: 0x00007f9d00000000 rbx: 0x0000000000000000 rcx: 0x00007f9dda009188 rdx: 0x00007fff58e5c788 rdi: 0x00007f9dd9476680 rsi: 0x00007fff96cd0fff rbp: 0x00007fff58e5c920 rsp: 0x00007fff58e5c880 r8: 0x000000000000007f r9: 0x00007f9dd9476680 r10: 0x00007f9dd97cf460 r11: 0x00007fff79a3dc60 r12: 0x00000000000000c8 r13: 0x00007f9dd95a7e20 r14: 0x0000000106de41bf r15: 0x0000000000000000 rip: 0x0000000106db4cac rfl: 0x0000000000010246 cr2: 0x00007f9d00000018 Logical CPU: 0 Error Code: 0x00000004 Trap Number: 14 Binary Images: 0x106da0000 - 0x106df4fff +net.sourceforge.chicken (2.2b2 - 2.2b2) <6D2FD694-6FB8-3F28-B85A-F38E2772A27F> /Applications/MacPorts/Chicken.app/Contents/MacOS/Chicken 0x106e16000 - 0x106e2dfff +org.andymatuschak.Sparkle (1.5 Beta 6 - 313) <9253F8F7-250B-1114-7AE9-A10A54EB2298> /Applications/MacPorts/Chicken.app/Contents/Frameworks/Sparkle.framework/Versions/A/Sparkle 0x10b285000 - 0x10b28cff7 libCGCMS.A.dylib (788.3.6) <09FA0C10-FAF1-362E-B0D7-2FC0BB19D386> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGCMS.A.dylib 0x10c098000 - 0x10c09bffb libCGXType.A.dylib (788.3.6) <2E327789-01E0-34C4-B387-A984A8DA7189> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGXType.A.dylib 0x10c5c9000 - 0x10c5f1fff libRIP.A.dylib (788.3.6) <903F88F3-DA15-3A95-AD1C-F0EA0AFC57C9> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib 0x10e3fe000 - 0x10e3fefef +cl_kernels (???) cl_kernels 0x10e40c000 - 0x10e40cff5 +cl_kernels (???) <145CB753-4111-446D-9269-DE8B92FB9A15> cl_kernels 0x10e40e000 - 0x10e4f4fef unorm8_bgra.dylib (2.4.5) <9980365E-FADF-36CB-97CC-2530BB70BA8A> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/ImageFormats/unorm8_bgra.dylib 0x7fff6d6db000 - 0x7fff6d71192f dyld (353.2.4) <708E385E- 50C6-32A3-983C-42E97BEE4346> /usr/lib/dyld 0x7fff88121000 - 0x7fff8816bfff com.apple.HIServices (1.22 - 523) <99ADA325-53C8-368E-A5FA-3F913CD2245A> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices 0x7fff881cc000 - 0x7fff881d9ff7 libbz2.1.0.dylib (36) <2DF83FBC- 5C08-39E1-94F5-C28653791B5F> /usr/lib/libbz2.1.0.dylib 0x7fff8829b000 - 0x7fff8829ffff com.apple.TCC (1.0 - 1) /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC 0x7fff882a0000 - 0x7fff882acff7 com.apple.OpenDirectory (10.10 - 187) <22FF4721-03D8-381B-AA83-2B07D690C777> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory 0x7fff882ad000 - 0x7fff882adfff com.apple.ApplicationServices (48 - 48) <5BF7910B-C328-3BF8-BA4F-CE52B574CE01> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices 0x7fff8855a000 - 0x7fff8859aff7 libGLImage.dylib (11.1.6) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib 0x7fff885ab000 - 0x7fff885b0fff com.apple.DiskArbitration (2.6 - 2.6) <0DFF4D9B-2AC3-3B82-B5C5-30F4EFBD2DB9> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration 0x7fff88684000 - 0x7fff8869eff7 com.apple.Kerberos (3.0 - 1) <7760E0C2-A222-3709-B2A6-B692D900CEB1> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos 0x7fff8869f000 - 0x7fff886aaff7 libkxld.dylib (2782.50.9) /usr/lib/system/libkxld.dylib 0x7fff886ab000 - 0x7fff88767ff7 libcrypto.0.9.7.dylib (106) /usr/lib/libcrypto.0.9.7.dylib 0x7fff88768000 - 0x7fff88775ff3 com.apple.ProtocolBuffer (1 - 228.0.1) <3429EB06-9F0E-355F-B9AB-F72879177398> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer 0x7fff88776000 - 0x7fff887a6ff3 com.apple.GSS (4.0 - 2.0) <97F2A028-44CF-3188-B863-F4EEB39CBDBD> /System/Library/Frameworks/GSS.framework/Versions/A/GSS 0x7fff887a7000 - 0x7fff887a7ff7 libunc.dylib (29) <5676F7EA-C1DF- 329F-B006-D2C3022B7D70> /usr/lib/system/libunc.dylib 0x7fff887be000 - 0x7fff887d0ff7 libsasl2.2.dylib (194.1) <35371406-75EF-304A-A073-956C40373555> /usr/lib/libsasl2.2.dylib 0x7fff8885c000 - 0x7fff88861fff libsystem_stats.dylib (163.30.2) /usr/lib/system/libsystem_stats.dylib 0x7fff88862000 - 0x7fff88862fff com.apple.Accelerate (1.10 - Accelerate 1.10) <2C8AF258-4F11-3BEC-A826-22D7199B3975> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate 0x7fff88904000 - 0x7fff8892dff3 libxslt.1.dylib (13.12) <19B2D915-DC29-3F79-9756-D7EB9051FEFF> /usr/lib/libxslt.1.dylib 0x7fff8892e000 - 0x7fff88934fff com.apple.speech.recognition.framework (5.0.9 - 5.0.9) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition 0x7fff88935000 - 0x7fff88c68ff7 libmecabra.dylib (666.7) <0ED8AE5E-7A5B-34A6-A2EE-2B852E60E1E2> /usr/lib/libmecabra.dylib 0x7fff88c69000 - 0x7fff88cb5fff com.apple.corelocation (1486.17 - 1615.24) <8825B3E2-E053-3E01-AE31-793443962D06> /System/Library/Frameworks/CoreLocation.framework/Versions/A/CoreLocation 0x7fff88cbc000 - 0x7fff88cc1ffb libheimdal-asn1.dylib (398.40.1) <7D2BE3DE-60F7-3A6E-A92E-DA0EF9D3417E> /usr/lib/libheimdal-asn1.dylib 0x7fff88cc2000 - 0x7fff88e0aff7 com.apple.WebKitLegacy (10600 - 10600.8.9) /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebKitLegacy.framework/Versions/A/WebKitLegacy 0x7fff88e0b000 - 0x7fff88e0ffff libcache.dylib (69) <45E9A2E7-99C4-36B2-BEE3-0C4E11614AD1> /usr/lib/system/libcache.dylib 0x7fff88e10000 - 0x7fff88e11ff7 com.apple.print.framework.Print (10.0 - 265) <3BC4FE7F-78A0-3E57-8F4C-520E7EFD36FA> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print 0x7fff88e15000 - 0x7fff88f39ff7 com.apple.LaunchServices (644.56 - 644.56) <20AABB1C-9319-3E4D-A024-51B0DD5FCD3B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices 0x7fff89931000 - 0x7fff8993cfff libGL.dylib (11.1.6) <38B3FF9A-5660-3080-9DB8-1CAE0E8CD739> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib 0x7fff89945000 - 0x7fff89969ff7 com.apple.Sharing (328.17 - 328.17) /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing 0x7fff8996a000 - 0x7fff8a1aeff7 com.apple.CoreGraphics (1.600.0 - 788.3.6) <3C5D7B35-2EB7-3907-A6B1-9186BDEA2CC8> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics 0x7fff8a1af000 - 0x7fff8a1b0ff3 libSystem.B.dylib (1213) <4B24B5BE-45F2-355A-9A35-D438A516D140> /usr/lib/libSystem.B.dylib 0x7fff8a1b1000 - 0x7fff8a396ff7 libicucore.A.dylib (531.50) /usr/lib/libicucore.A.dylib 0x7fff8a58a000 - 0x7fff8a592ff7 com.apple.AppleSRP (5.0 - 1) <68F0C577-ED96-34F2-B701-CE3023367D4D> /System/Library/PrivateFrameworks/AppleSRP.framework/Versions/A/AppleSRP 0x7fff8a598000 - 0x7fff8a637e27 com.apple.AppleJPEG (1.0 - 1) <6627DDD9-A8FE-3968-B23A-B6A29AA3919A> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG 0x7fff8a638000 - 0x7fff8a6c9ff7 libCoreStorage.dylib (471.30.1) <9D95399F-1AC5-325F-8337-6E13AD99E44B> /usr/lib/libCoreStorage.dylib 0x7fff8a759000 - 0x7fff8a7c7ff3 com.apple.Heimdal (4.0 - 2.0) <8D1667CF-D454-3E07-A58E-E15591B5A95E> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal 0x7fff8a7c8000 - 0x7fff8abf8fff com.apple.vision.FaceCore (3.1.6 - 3.1.6) /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore 0x7fff8abfe000 - 0x7fff8ac87ff7 com.apple.CoreSymbolication (3.1 - 57020.2) /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication 0x7fff8ac88000 - 0x7fff8ada1ffb com.apple.CoreText (454.11 - 454.11) <7E5228C8-8657-3B6C-B3A4-98B79A3041EA> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText 0x7fff8adf9000 - 0x7fff8ae16fff libsystem_kernel.dylib (2782.50.9) /usr/lib/system/libsystem_kernel.dylib 0x7fff8b0f7000 - 0x7fff8b175fff com.apple.CoreServices.OSServices (640.4 - 640.4) <9D175CD9-B27F-3529-8269-66D8AA83582E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices 0x7fff8b179000 - 0x7fff8b1e5ff3 com.apple.MMCS (1.3 - 327.5) /System/Library/PrivateFrameworks/MMCS.framework/Versions/A/MMCS 0x7fff8b279000 - 0x7fff8b281fff libsystem_dnssd.dylib (576.50.2) <9EC5AF92-D0D2-3BDE-92B6-D3730D3865C8> /usr/lib/system/libsystem_dnssd.dylib 0x7fff8b34b000 - 0x7fff8b3c3ff7 com.apple.SystemConfiguration (1.14.4 - 1.14) <3DFFD7F7-BD23-3F4C-A209-C4A0D99F6573> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration 0x7fff8b3dc000 - 0x7fff8b4cdfff libJP2.dylib (1247) /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib 0x7fff8b4dd000 - 0x7fff8b598ff7 com.apple.DiscRecording (9.0 - 9000.4.2) <4655B4B8-523D-3AE6-92A0-8486A2258B3B> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording 0x7fff8b599000 - 0x7fff8b5d4fff com.apple.QD (301 - 301) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD 0x7fff8b627000 - 0x7fff8b693fff com.apple.framework.CoreWLAN (5.0 - 500.35.2) <03697149-1CDD-32FF-B564-1C1EF5E9E5C3> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN 0x7fff8b694000 - 0x7fff8b6affff com.apple.AppleVPAFramework (1.4.5 - 1.4.5) /System/Library/PrivateFrameworks/AppleVPA.framework/Versions/A/AppleVPA 0x7fff8b6f4000 - 0x7fff8b6ffff7 com.apple.CrashReporterSupport (10.10 - 631) /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport 0x7fff8b700000 - 0x7fff8b730fff libsystem_m.dylib (3086.1) <1E12AB45-6D96-36D0-A226-F24D9FB0D9D6> /usr/lib/system/libsystem_m.dylib 0x7fff8b7e9000 - 0x7fff8b7ecfff com.apple.xpc.ServiceManagement (1.0 - 1) /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement 0x7fff8b7ed000 - 0x7fff8b88ffff com.apple.Bluetooth (4.3.6 - 4.3.6f4) /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth 0x7fff8bbbd000 - 0x7fff8bbd4ff7 libLinearAlgebra.dylib (1128) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib 0x7fff8bbd5000 - 0x7fff8bc02fff com.apple.CoreVideo (1.8 - 145.1) <18DB07E0-B927-3260-A234-636F298D1917> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo 0x7fff8bc2e000 - 0x7fff8bc52fef libJPEG.dylib (1247) <78AA0479 -176D-3C69-ADFB-4609A4A676FF> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib 0x7fff8bc57000 - 0x7fff8bc57ff7 libkeymgr.dylib (28) <77845842-DE70-3CC5-BD01-C3D14227CED5> /usr/lib/system/libkeymgr.dylib 0x7fff8bc81000 - 0x7fff8bca9fff libsystem_info.dylib (459.40.1) <2E16C4B3-A327-3957-9C41-143911979A1E> /usr/lib/system/libsystem_info.dylib 0x7fff8bcaa000 - 0x7fff8bcb2ffb libcopyfile.dylib (118.1.2) <0C68D3A6-ACDD-3EF3-991A-CC82C32AB836> /usr/lib/system/libcopyfile.dylib 0x7fff8be1e000 - 0x7fff8be20fff libsystem_configuration.dylib (699.40.2) <56F94DCE-DBDE-3615-8F07-DE6270D9F8BE> /usr/lib/system/libsystem_configuration.dylib 0x7fff8be30000 - 0x7fff8be38fff libsystem_platform.dylib (63) <64E34079-D712-3D66-9CE2-418624A5C040> /usr/lib/system/libsystem_platform.dylib 0x7fff8be39000 - 0x7fff8be3cfff com.apple.IOSurface (97.4 - 97.4) /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface 0x7fff8be3d000 - 0x7fff8ce00ff3 com.apple.WebCore (10600 - 10600.8.9) /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/WebCore 0x7fff8ce01000 - 0x7fff8ce68ff7 com.apple.framework.CoreWiFi (3.0 - 300.4) <19269C1D-EB29-384A-83F3-7DDDEB7D9DAD> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi 0x7fff8ce69000 - 0x7fff8cec8fff com.apple.AE (681.5 - 681.7) <2BF39455-1CDD-392C-824A-9972C6B1FB57> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE 0x7fff8cec9000 - 0x7fff8cee4ff7 libCRFSuite.dylib (34) /usr/lib/libCRFSuite.dylib 0x7fff8d14e000 - 0x7fff8d2dcfff libBLAS.dylib (1128) <497912C1-A98E-3281-BED7-E9C751552F61> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib 0x7fff8d2dd000 - 0x7fff8d2e5fe7 libcldcpuengine.dylib (2.4.5) /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib 0x7fff8d2f1000 - 0x7fff8d2f3fff com.apple.loginsupport (1.0 - 1) /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport 0x7fff8daa9000 - 0x7fff8db9dff7 libFontParser.dylib (134.10) <6CF434A2-91CA-3477-BDE2-124508EDA05D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib 0x7fff8dbc5000 - 0x7fff8dfd2ff7 libLAPACK.dylib (1128) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib 0x7fff8e054000 - 0x7fff8e087fff com.apple.MediaKit (16 - 757.2) <2912E5C2-085F-3FE2-8531-23B6E894B0F0> /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit 0x7fff8e12d000 - 0x7fff8e146ff7 com.apple.CFOpenDirectory (10.10 - 187) /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory 0x7fff8e297000 - 0x7fff8e298ff7 libsystem_blocks.dylib (65) <9615D10A-FCA7-3BE4-AA1A-1B195DACE1A1> /usr/lib/system/libsystem_blocks.dylib 0x7fff8e2e8000 - 0x7fff8e34fffb com.apple.datadetectorscore (6.0 - 396.1.2) /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore 0x7fff8e350000 - 0x7fff8e350fff com.apple.audio.units.AudioUnit (1.12 - 1.12) /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit 0x7fff8e351000 - 0x7fff8e356ff7 libunwind.dylib (35.3) /usr/lib/system/libunwind.dylib 0x7fff8e357000 - 0x7fff8e378fff com.apple.framework.Apple80211 (10.3 - 1030.71.6) /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211 0x7fff8e379000 - 0x7fff8e37bfff libsystem_sandbox.dylib (358.20.5) <3F5E973F-C702-31AC-97BC-05F5C195683C> /usr/lib/system/libsystem_sandbox.dylib 0x7fff8e37c000 - 0x7fff8e38eff7 com.apple.ImageCapture (9.0 - 9.0) <7FB65DD4-56B5-35C4-862C-7A2DED991D1F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture 0x7fff8e4aa000 - 0x7fff8e4c4ff7 liblzma.5.dylib (7) <1D03E875-A7C0-3028-814C-3C27F7B7C079> /usr/lib/liblzma.5.dylib 0x7fff8e4f5000 - 0x7fff8e630fff com.apple.ImageIO.framework (3.3.0 - 1247) /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO 0x7fff8e631000 - 0x7fff8e640fff com.apple.LangAnalysis (1.7.0 - 1.7.0) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis 0x7fff8efac000 - 0x7fff8efd1fff libPng.dylib (1247) <1E8B06AA- 1DC5-3845-88D9-B2F8E6E1E540> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib 0x7fff8efd2000 - 0x7fff8efdbfff libsystem_pthread.dylib (105.40.1) /usr/lib/system/libsystem_pthread.dylib 0x7fff8efdc000 - 0x7fff8efecff7 libbsm.0.dylib (34) /usr/lib/libbsm.0.dylib 0x7fff8f0b1000 - 0x7fff8f327fff com.apple.security (7.0 - 57031.40.8) /System/Library/Frameworks/Security.framework/Versions/A/Security 0x7fff8f328000 - 0x7fff8f32bfff com.apple.help (1.3.3 - 46) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help 0x7fff8f387000 - 0x7fff8f89cfff com.apple.JavaScriptCore (10600 - 10600.8.7.1) <4C48FD32-ACA3-358F-95D9-05DBB56A1DED> /System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore 0x7fff8f89d000 - 0x7fff8f8f1fff libc++.1.dylib (120) <1B9530FD- 989B-3174-BB1C-BDC159501710> /usr/lib/libc++.1.dylib 0x7fff8f8f2000 - 0x7fff8f9a1fe7 libvMisc.dylib (516) <6739E390-46E7-3BFA-9B69-B278562326E6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib 0x7fff8f9a2000 - 0x7fff8f9edff7 com.apple.CloudDocs (1.0 - 321.10) /System/Library/PrivateFrameworks/CloudDocs.framework/Versions/A/CloudDocs 0x7fff8f9ee000 - 0x7fff8fa3dff7 libcurl.4.dylib (83.40.2) /usr/lib/libcurl.4.dylib 0x7fff8fd2b000 - 0x7fff8fd9cffb com.apple.ApplicationServices.ATS (360 - 375.4) <888FE0B1-835C-30B1-80AD-5066CADB0364> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS 0x7fff8fddb000 - 0x7fff90173ff7 com.apple.CoreFoundation (6.9 - 1153.18) <5C0892B8-9691-341F-9279-CA3A74D59AA0> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 0x7fff90174000 - 0x7fff90186ff7 com.apple.CoreDuetDaemonProtocol (1.0 - 1) /System/Library/PrivateFrameworks/CoreDuetDaemonProtocol.framework/Versions/A/CoreDuetDaemonProtocol 0x7fff9018a000 - 0x7fff90409ff7 com.apple.CoreData (111 - 526.3) <5A27E0D8-5E5A-335B-B3F6-2601C7B976FA> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData 0x7fff9040a000 - 0x7fff906cdff7 com.apple.WebKit (10600 - 10600.8.9) <8EE5A9F9-DE98-3202-92C0-23F6E6E5E274> /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit 0x7fff906ce000 - 0x7fff906dbfff libxar.1.dylib (255) <7CD69BB5-97BA-3858-8A8B-2F33F129E6E7> /usr/lib/libxar.1.dylib 0x7fff906dc000 - 0x7fff906deff7 libsystem_coreservices.dylib (9) <41B7C578-5A53-31C8-A96F-C73E030B0938> /usr/lib/system/libsystem_coreservices.dylib 0x7fff906df000 - 0x7fff909e4ff3 com.apple.HIToolbox (2.1.1 - 758.7) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox 0x7fff909ee000 - 0x7fff90a5dfff com.apple.SearchKit (1.4.0 - 1.4.0) <80883BD1-C9BA-3794-A20E-476F94DD89A9> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit 0x7fff90a5e000 - 0x7fff90b50ff7 libiconv.2.dylib (42) <2A06D02F- 8B76-3864-8D96-64EF5B40BC6C> /usr/lib/libiconv.2.dylib 0x7fff90b92000 - 0x7fff90bacff7 libextension.dylib (55.2) <3BB019CA-199A-36AC-AA22-14B562138545> /usr/lib/libextension.dylib 0x7fff90bad000 - 0x7fff90bb3ff7 libsystem_networkextension.dylib (167.40.3) /usr/lib/system/libsystem_networkextension.dylib 0x7fff90bb4000 - 0x7fff90c49ff7 com.apple.ColorSync (4.9.0 - 4.9.0) <9150C2B7-2E6E-3509-96EA-7B3F959F049E> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync 0x7fff90cde000 - 0x7fff90fadff3 com.apple.CoreImage (10.3.5) <0224F5A6-636A-374B-B46C-13E066596725> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/CoreImage.framework/Versions/A/CoreImage 0x7fff914f7000 - 0x7fff916a7ff3 com.apple.QuartzCore (1.10 - 361.19) /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore 0x7fff916cb000 - 0x7fff91761ff7 com.apple.cloudkit.CloudKit (283.67.4 - 283.67.4) /System/Library/Frameworks/CloudKit.framework/Versions/A/CloudKit 0x7fff91793000 - 0x7fff9179cff7 libsystem_notify.dylib (133.1.1) <61147800-F320-3DAA-850C-BADF33855F29> /usr/lib/system/libsystem_notify.dylib 0x7fff918d2000 - 0x7fff91918ff7 libFontRegistry.dylib (134.1) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib 0x7fff91919000 - 0x7fff91926ff7 com.apple.SpeechRecognitionCore (2.1.2 - 2.1.2) <551322E2-C1E4-3378-A218-F362985E3E3C> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore 0x7fff91927000 - 0x7fff91ba5ff7 com.apple.RawCamera.bundle (6.04.1 - 798) <7988A25F-2A69-311E-929E-B70D164739F4> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera 0x7fff91ba6000 - 0x7fff91bc5fff com.apple.CoreDuet (1.0 - 1) <36AA9FD5-2685-314D-B364-3FA4688D86BD> /System/Library/PrivateFrameworks/CoreDuet.framework/Versions/A/CoreDuet 0x7fff91bc6000 - 0x7fff91c20ff7 com.apple.LanguageModeling (1.0 - 1) /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling 0x7fff91c4f000 - 0x7fff91c60ff7 libz.1.dylib (55) <88C7C7DE-04B8 -316F-8B74-ACD9F3DE1AA1> /usr/lib/libz.1.dylib 0x7fff91c61000 - 0x7fff91c99fff com.apple.RemoteViewServices (2.0 - 99) /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices 0x7fff91c9a000 - 0x7fff9281bff7 com.apple.AppKit (6.9 - 1348.17) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit 0x7fff9281c000 - 0x7fff9294cfff com.apple.UIFoundation (1.0 - 1) <466BDFA8-0B9F-3AB0-989D-F9779422926A> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation 0x7fff9294d000 - 0x7fff92966ff3 com.apple.openscripting (1.6.4 - 162.2) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting 0x7fff92967000 - 0x7fff92998ff7 com.apple.ProtectedCloudStorage (1.0 - 1) <9D76F2E0-C28A-3DBC-A91F-E87888D46BF0> /System/Library/PrivateFrameworks/ProtectedCloudStorage.framework/Versions/A/ProtectedCloudStorage 0x7fff9323e000 - 0x7fff93269fff libc++abi.dylib (125) <88A22A0F- 87C6-3002-BFBA-AC0F2808B8B9> /usr/lib/libc++abi.dylib 0x7fff9326a000 - 0x7fff9326afff com.apple.Carbon (154 - 157) <9BF51672-1684-3FDE-A561-FC59A2864EF8> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon 0x7fff93278000 - 0x7fff93281fff libGFXShared.dylib (11.1.6) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib 0x7fff93282000 - 0x7fff93342ff7 com.apple.backup.framework (1.6.5 - 1.6.5) <86396038-33EA-3046-9F70-093A3D6407D4> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup 0x7fff93347000 - 0x7fff93358ff3 libsystem_coretls.dylib (35.40.1) <155DA0A9-2046-332E-BFA3-D7974A51F731> /usr/lib/system/libsystem_coretls.dylib 0x7fff93359000 - 0x7fff93640ffb com.apple.CoreServices.CarbonCore (1108.6 - 1108.6) <8953580E-7857-33B2-AA64-98296830D3A8> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore 0x7fff936bf000 - 0x7fff93753fff com.apple.ink.framework (10.9 - 213) <8E029630-1530-3734-A446-13353F0E7AC5> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink 0x7fff93855000 - 0x7fff938c9ffb com.apple.securityfoundation (6.0 - 55126) <344401F5-4016-3AEB-BFDC-CE8E5546D39F> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation 0x7fff938ca000 - 0x7fff93904ffb com.apple.DebugSymbols (115 - 115) <6F03761D-7C3A-3C80-8031-AA1C1AD7C706> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols 0x7fff93905000 - 0x7fff93960fe7 libTIFF.dylib (1247) <43CB4BDE- 84FD-3CCE-96C0-FB33BA2753BD> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib 0x7fff93961000 - 0x7fff93977ff7 libsystem_asl.dylib (267) /usr/lib/system/libsystem_asl.dylib 0x7fff93978000 - 0x7fff93a04fef libsystem_c.dylib (1044.40.3) <2E673D96-E334-37D2-833A-E57383BBA377> /usr/lib/system/libsystem_c.dylib 0x7fff93a1b000 - 0x7fff93a68ff7 com.apple.print.framework.PrintCore (10.3 - 451.1) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore 0x7fff93ebf000 - 0x7fff93f5dfff com.apple.Metadata (10.7.0 - 917.36) <00C4CB5D-E723-3612-84E0-439098392CDD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata 0x7fff93f5e000 - 0x7fff93fd0fff com.apple.framework.IOKit (2.0.2 - 1050.20.2) <09C0518C-90DF-3FC3-96D6-34D35F72C8EF> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit 0x7fff93fd1000 - 0x7fff93fedff7 libsystem_malloc.dylib (53.30.1) /usr/lib/system/libsystem_malloc.dylib 0x7fff93ffe000 - 0x7fff9403ffff libGLU.dylib (11.1.6) <4BC6579D- A6D0-3A19-880E-E29FAEA698E7> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib 0x7fff94040000 - 0x7fff940c4fff com.apple.PerformanceAnalysis (1.0 - 1) <095E6B1C-DC20-38DC-8931-16041B0489C7> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis 0x7fff94130000 - 0x7fff94135ff7 libmacho.dylib (862) <126CA2ED- DE91-308F-8881-B9DAEC3C63B6> /usr/lib/system/libmacho.dylib 0x7fff9413a000 - 0x7fff94171ffb com.apple.LDAPFramework (2.4.28 - 194.5) /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP 0x7fff94172000 - 0x7fff94183fff libcmph.dylib (1) <46EC3997-DB5E- 38AE-BBBB-A035A54AD3C0> /usr/lib/libcmph.dylib 0x7fff941da000 - 0x7fff9420cff3 com.apple.frameworks.CoreDaemon (1.3 - 1.3) /System/Library/PrivateFrameworks/CoreDaemon.framework/Versions/B/CoreDaemon 0x7fff9439b000 - 0x7fff943affeb libCGInterfaces.dylib (294.1) <390D4B3F-B738-3D33-BEDB-07E3F0F6B42C> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib 0x7fff943b5000 - 0x7fff94401ff7 libcups.2.dylib (408.2) /usr/lib/libcups.2.dylib 0x7fff9444f000 - 0x7fff9446cffb libresolv.9.dylib (57) <26B38E61 -298A-3C3A-82C1-3B5E98AD5E29> /usr/lib/libresolv.9.dylib 0x7fff945fd000 - 0x7fff9470fff7 libvDSP.dylib (516) <151B3CCB- 77D3-3715-A3D0-7C74CD5C7FFC> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib 0x7fff94795000 - 0x7fff948dbfef libsqlite3.dylib (168.2) <53F6A294-15D7-3804-9ABF-47D35E15CDFB> /usr/lib/libsqlite3.dylib 0x7fff948dc000 - 0x7fff94907ff7 com.apple.DictionaryServices (1.2 - 229.1) <62EC3E1B-5A28-3252-90FF-C2E9999C2A2A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices 0x7fff94908000 - 0x7fff94914fff com.apple.speech.synthesis.framework (5.3.11 - 5.3.11) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis 0x7fff94d01000 - 0x7fff94d27fff com.apple.ChunkingLibrary (2.1 - 163.6) <29D4CB95-42EF-34C6-8182-BDB6F7BB1E79> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary 0x7fff94d28000 - 0x7fff95043fcf com.apple.vImage (8.0 - 8.0) <1183FE6A-FDB6-3B3B-928D-50C7909F2308> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage 0x7fff95049000 - 0x7fff95074ffb libarchive.2.dylib (30.50.1) /usr/lib/libarchive.2.dylib 0x7fff950b0000 - 0x7fff950b0fff libOpenScriptingUtil.dylib (162.2) /usr/lib/libOpenScriptingUtil.dylib 0x7fff951b1000 - 0x7fff951b3fff libquarantine.dylib (76.20.1) <7AF90041-2768-378A-925A-D83161863642> /usr/lib/system/libquarantine.dylib 0x7fff951b4000 - 0x7fff951b6fff libRadiance.dylib (1247) <0028A2E3-7928-3479-9BF7-CB64234F85AF> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib 0x7fff951ba000 - 0x7fff951bcfff libCVMSPluginSupport.dylib (11.1.6) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib 0x7fff95243000 - 0x7fff95244fff libsystem_secinit.dylib (18) <581DAD0F-6B63-3A48-B63B-917AF799ABAA> /usr/lib/system/libsystem_secinit.dylib 0x7fff95245000 - 0x7fff95246ffb libremovefile.dylib (35) <3485B5F4-6CE8-3C62-8DFD-8736ED6E8531> /usr/lib/system/libremovefile.dylib 0x7fff952f2000 - 0x7fff9531afff libxpc.dylib (559.40.1) <5C829202-962E-3744-8B50-00D38CC88E84> /usr/lib/system/libxpc.dylib 0x7fff9531b000 - 0x7fff953fffff libcrypto.0.9.8.dylib (52.40.1) /usr/lib/libcrypto.0.9.8.dylib 0x7fff95400000 - 0x7fff95401fff libDiagnosticMessagesClient.dylib (100) <2EE8E436-5CDC-34C5-9959-5BA218D507FB> /usr/lib/libDiagnosticMessagesClient.dylib 0x7fff95402000 - 0x7fff954f4ff7 libxml2.2.dylib (26.12) <769FD755 -D24A-3A7C-ABEE-9A82BB1196D0> /usr/lib/libxml2.2.dylib 0x7fff954f5000 - 0x7fff954fcff7 libcompiler_rt.dylib (35) /usr/lib/system/libcompiler_rt.dylib 0x7fff954fd000 - 0x7fff95501ff7 libGIF.dylib (1247) <5EA6D19A-9922-39F6-82DB-DE7A5B8860CF> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib 0x7fff95817000 - 0x7fff95817fff com.apple.Cocoa (6.8 - 21) /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa 0x7fff95821000 - 0x7fff95930ff3 com.apple.desktopservices (1.9.3 - 1.9.3) /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv 0x7fff95944000 - 0x7fff9596eff7 libdispatch.dylib (442.50.1) /usr/lib/system/libdispatch.dylib 0x7fff9596f000 - 0x7fff95b7fff7 com.apple.CFNetwork (720.5.7 - 720.5.7) /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork 0x7fff95c13000 - 0x7fff95c8cfe7 libcorecrypto.dylib (233.30.1) <5779FFA0-4D9A-3AD4-B7F2-618227621DC8> /usr/lib/system/libcorecrypto.dylib 0x7fff95c8d000 - 0x7fff95c8ffff com.apple.EFILogin (2.0 - 2) <3BA837D8-94F5-3240-9CF7-E40DC2808446> /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/EFILogin 0x7fff95c90000 - 0x7fff95c9bfff libcommonCrypto.dylib (60061.30.1) /usr/lib/system/libcommonCrypto.dylib 0x7fff95c9c000 - 0x7fff95fcdfff com.apple.Foundation (6.9 - 1154) <49EE64E1-9F53-35D1-A481-2EFE2789B254> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation 0x7fff9607b000 - 0x7fff96095ff3 com.apple.Ubiquity (1.3 - 313) /System/Library/PrivateFrameworks/Ubiquity.framework/Versions/A/Ubiquity 0x7fff9618e000 - 0x7fff96264ff3 com.apple.DiskImagesFramework (10.10.5 - 398) <37291661-BCB2-3F95-B446-5E5DB1D1E472> /System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/DiskImages 0x7fff96265000 - 0x7fff96266fff com.apple.TrustEvaluationAgent (2.0 - 25) <2D61A2C3-C83E-3A3F-8EC1-736DBEC250AB> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent 0x7fff96274000 - 0x7fff96274fff com.apple.Accelerate.vecLib (3.10 - vecLib 3.10) <9D749502-A228-3BF1-B52F-A182DEEB2C4D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib 0x7fff965a1000 - 0x7fff965a9ff7 com.apple.icloud.FindMyDevice (1.0 - 1) <9CE67F85-2BA8-3093-97BA-07BF5C04A5D6> /System/Library/PrivateFrameworks/FindMyDevice.framework/Versions/A/FindMyDevice 0x7fff965aa000 - 0x7fff965b8ff7 com.apple.opengl (11.1.6 - 11.1.6) /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL 0x7fff965d2000 - 0x7fff967cc46f libobjc.A.dylib (647) <759E155D- BC42-3D4E-869B-6F57D477177C> /usr/lib/libobjc.A.dylib 0x7fff967cd000 - 0x7fff967d6ff3 com.apple.CommonAuth (4.0 - 2.0) <9A484EE6-0003-3AB1-AE4F-AA543BBBF53F> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth 0x7fff967d7000 - 0x7fff967e1ff7 com.apple.NetAuth (5.2 - 5.2) <2BBD749A-8E18-35B8-8E48-A90347C1CCA7> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth 0x7fff967e2000 - 0x7fff967e6fff libpam.2.dylib (20) /usr/lib/libpam.2.dylib 0x7fff96cd8000 - 0x7fff96d10fff libsystem_network.dylib (412.20.3) <6105C134-6722-3C0A-A4CE-5E1261E2E1CC> /usr/lib/system/libsystem_network.dylib 0x7fff96d11000 - 0x7fff96e39ff7 com.apple.coreui (2.1 - 308.6) <9E0E9C6A-68F5-34C1-A17C-96226D401D4D> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI 0x7fff96e3a000 - 0x7fff96e5afff com.apple.IconServices (47.1 - 47.1) /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices 0x7fff96ee0000 - 0x7fff96f2fff7 com.apple.opencl (2.4.2 - 2.4.2) <590504FA-E5D2-37C2-91A7-09F5F039F971> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL 0x7fff96f30000 - 0x7fff96f4cfff com.apple.GenerationalStorage (2.0 - 209.11) <9FF8DD11-25FB-3047-A5BF-9415339B3EEC> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage 0x7fff96f4d000 - 0x7fff9724fffb com.apple.GeoServices (1.0 - 1077.0.18) <2BBF8B44-DD46-3432-8C84-6D6AA004C233> /System/Library/PrivateFrameworks/GeoServices.framework/Versions/A/GeoServices 0x7fff972db000 - 0x7fff972e2fff com.apple.NetFS (6.0 - 4.0) /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS 0x7fff9737d000 - 0x7fff97385ff3 com.apple.CoreServices.FSEvents (1210.20.1 - 1210.20.1) <84F79D3E-7B5E-3C93-8479-35794A3F125E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents 0x7fff97387000 - 0x7fff97387ff7 liblaunch.dylib (559.40.1) <4F81CA3A-D2CE-3030-A89D-42F3DAD7BA8F> /usr/lib/system/liblaunch.dylib 0x7fff97472000 - 0x7fff97476fff com.apple.CommonPanels (1.2.6 - 96) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels 0x7fff97477000 - 0x7fff974c8fff com.apple.audio.CoreAudio (4.3.0 - 4.3.0) <8E6AE326-9F3E-3182-BD9E-FDF561211E2E> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio 0x7fff974c9000 - 0x7fff974dcff7 com.apple.CoreBluetooth (1.0 - 1) <8D7BA9BA-EB36-307A-9119-0B3D9732C953> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth 0x7fff974e5000 - 0x7fff9752bff7 libauto.dylib (186) /usr/lib/libauto.dylib 0x7fff9752c000 - 0x7fff9752eff7 libutil.dylib (38) <471AD65E- B86E-3C4A-8ABD-B8665A2BCE3F> /usr/lib/libutil.dylib 0x7fff9752f000 - 0x7fff97530fff liblangid.dylib (117) /usr/lib/liblangid.dylib 0x7fff97549000 - 0x7fff97549fff com.apple.CoreServices (62 - 62) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices 0x7fff9756e000 - 0x7fff97574fff libsystem_trace.dylib (72.20.1) <840F5301-B55A-3078-90B9-FEFFD6CD741A> /usr/lib/system/libsystem_trace.dylib 0x7fff975d9000 - 0x7fff975e4ff7 libcsfde.dylib (471.30.1) /usr/lib/libcsfde.dylib 0x7fff975e5000 - 0x7fff975e9fff libCoreVMClient.dylib (79.1) <201EF6DF-5074-3CB7-A361-398CF957A264> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib 0x7fff975ea000 - 0x7fff97619ff7 com.apple.CoreServicesInternal (221.7.2 - 221.7.2) /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal 0x7fff9761a000 - 0x7fff9761dff7 libdyld.dylib (353.2.4) <224F35C5-6E35-3EC4-A97C-80949CE444E7> /usr/lib/system/libdyld.dylib 0x7fff9763d000 - 0x7fff9763fff7 com.apple.securityhi (9.0 - 55006) <15D38919-9697-3E3A-BCB9-4E3271BC2C7E> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI 0x7fff978e5000 - 0x7fff97905ff7 com.apple.MultitouchSupport.framework (264.6 - 264.6) <1539F1F6-6334-37F3-9C52-02EFFBF4835D> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport 0x7fff97906000 - 0x7fff97a6dffb com.apple.audio.toolbox.AudioToolbox (1.12 - 1.12) <5678FC94-456A-3F5F- BA9A-10EB6E462997> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox 0x7fff97a6e000 - 0x7fff97a70fff com.apple.CoreDuetDebugLogging (1.0 - 1) <9A6E5710-EA99-366E-BF40-9A65EC1B46A1> /System/Library/PrivateFrameworks/CoreDuetDebugLogging.framework/Versions/A/CoreDuetDebugLogging 0x7fff97a8b000 - 0x7fff97ac6fff com.apple.Symbolication (1.4 - 56045) /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication External Modification Summary: Calls made by other processes targeting this process: task_for_pid: 1 thread_create: 0 thread_set_state: 0 Calls made by this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by all processes on this machine: task_for_pid: 297 thread_create: 0 thread_set_state: 0 VM Region Summary: ReadOnly portion of Libraries: Total=211.4M resident=108.2M(51%) swapped_out_or_unallocated=103.2M(49%) Writable regions: Total=139.9M written=7136K(5%) resident=22.7M(16%) swapped_out=0K(0%) unallocated=117.2M(84%) REGION TYPE VIRTUAL =========== ======= Activity Tracing 2048K CG backing stores 7792K CG image 796K CG shared images 368K CoreAnimation 3200K CoreImage 16K CoreUI image data 440K Dispatch continuations 16.0M Foundation 4K Image IO 464K Kernel Alloc Once 8K MALLOC 77.9M MALLOC (admin) 48K Memory Tag 242 12K Memory Tag 251 8K OpenCL 16K STACK GUARD 56.1M Stack 14.2M VM_ALLOCATE 17.3M __DATA 18.6M __IMAGE 528K __LINKEDIT 71.1M __TEXT 140.3M __UNICODE 552K mapped file 71.0M shared memory 4K =========== ======= TOTAL 498.3M Model: MacBookPro11,5, BootROM MBP114.0172.B10, 4 processors, Intel Core i7, 2.5 GHz, 16 GB, SMC 2.30f2 Graphics: AMD Radeon R9 M370X, AMD Radeon R9 M370X, PCIe, 2048 MB Graphics: Intel Iris Pro, Intel Iris Pro, Built-In Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533642465238412D50422020 Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533642465238412D50422020 AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x152), Broadcom BCM43xx 1.0 (7.15.166.24.3) Bluetooth: Version 4.3.6f4 17916, 3 services, 18 devices, 1 incoming serial ports Network Service: Thunderbolt Ethernet, Ethernet, en5 PCI Card: Apple 57762-A0, Ethernet Controller, Thunderbolt at 195,0,0 Serial ATA Device: APPLE SSD SM0512G, 500,28 GB USB Device: Internal Memory Card Reader USB Device: Porsche Mobile for Mac USB Device: Bluetooth USB Host Controller USB Device: Apple Internal Keyboard / Trackpad Thunderbolt Bus: MacBook Pro, Apple Inc., 27.1 Thunderbolt Device: Thunderbolt to Gigabit Ethernet Adapter, Apple Inc., 1, 5.5 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 11:53:41 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 11:53:41 -0000 Subject: [MacPorts] #53135: Chicken of VNC crash after ports upgrade Message-ID: <045.905c50621d79f659268e0b5d7b8c5b13@macports.org> #53135: Chicken of VNC crash after ports upgrade ----------------------+------------------------------ Reporter: emiglior | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: cotvnc @2.2b2_0 ----------------------+------------------------------ Dear experts, I am using a MB with osx 10.10.5 After running a port upgrade (yesterday) I have crash when launching ChickenOfVNC. I attach the dump I get after the crash. Is there any mismatched/missing library? Thanks in advance for the assistance. Regards Ernesto -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 11:54:50 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 11:54:50 -0000 Subject: [MacPorts] #53135: Chicken of VNC crash after ports upgrade In-Reply-To: <045.905c50621d79f659268e0b5d7b8c5b13@macports.org> References: <045.905c50621d79f659268e0b5d7b8c5b13@macports.org> Message-ID: <060.320b0ba9aecc223a10a18fad12e1e85c@macports.org> #53135: Chicken of VNC crash after ports upgrade -------------------------------+----------------- Reporter: emiglior | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cotvnc @2.2b2_0 | -------------------------------+----------------- Changes (by emiglior): * Attachment "cvnc.log" added. log file from Chicken of VNC crash -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 11:57:24 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 11:57:24 -0000 Subject: [MacPorts] #53134: Chicken of VNC crash after ports upgrade In-Reply-To: <045.0d1b05e5b977c70d45dc263cce6eb207@macports.org> References: <045.0d1b05e5b977c70d45dc263cce6eb207@macports.org> Message-ID: <060.eab96c083e05f2991776c0ffade83edd@macports.org> #53134: Chicken of VNC crash after ports upgrade -------------------------------+----------------- Reporter: emiglior | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cotvnc @2.2b2_0 | -------------------------------+----------------- Comment (by emiglior): supersedes by ticket #53134 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 11:58:41 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 11:58:41 -0000 Subject: [MacPorts] #53134: Chicken of VNC crash after ports upgrade In-Reply-To: <045.0d1b05e5b977c70d45dc263cce6eb207@macports.org> References: <045.0d1b05e5b977c70d45dc263cce6eb207@macports.org> Message-ID: <060.b9ddb06d1e12dbfb75d3f1a12edf13a0@macports.org> #53134: Chicken of VNC crash after ports upgrade -------------------------------+----------------- Reporter: emiglior | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cotvnc @2.2b2_0 | -------------------------------+----------------- Comment (by emiglior): superseded by ticket #53135 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 12:06:28 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 12:06:28 -0000 Subject: [MacPorts] #53134: cotvnc @2.2b2_0: Chicken of VNC crash after ports upgrade (was: Chicken of VNC crash after ports upgrade) In-Reply-To: <045.0d1b05e5b977c70d45dc263cce6eb207@macports.org> References: <045.0d1b05e5b977c70d45dc263cce6eb207@macports.org> Message-ID: <060.309015b2402866913302e219534430e0@macports.org> #53134: cotvnc @2.2b2_0: Chicken of VNC crash after ports upgrade ------------------------+-------------------- Reporter: emiglior | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: duplicate | Keywords: Port: cotvnc | ------------------------+-------------------- Changes (by ryandesign): * status: new => closed * resolution: => duplicate * port: cotvnc @2.2b2_0 => cotvnc Old description: > Dear experts, > I am using a MB with osx 10.10.5 > After running a port upgrade (yesterday) I have crash when launching > ChickenOfVNC. > Below you can find the dump I get after the crash. Is there any > mismatched/missing library? > Thanks in advance for the assistance. > Regards > Ernesto > > ---- > Process: Chicken [310] > Path: > /Applications/MacPorts/Chicken.app/Contents/MacOS/Chicken > Identifier: net.sourceforge.chicken > Version: 2.2b2 (2.2b2) > Code Type: X86-64 (Native) > Parent Process: ??? [1] > Responsible: Chicken [310] > User ID: 501 > > Date/Time: 2016-12-22 12:35:38.961 +0100 > OS Version: Mac OS X 10.10.5 (14F2109) > Report Version: 11 > Anonymous UUID: E3896221-6692-E1BE-7C31-A9B65EC7063F > > Time Awake Since Boot: 66 seconds > > Crashed Thread: 0 Dispatch queue: com.apple.main-thread > > Exception Type: EXC_BAD_ACCESS (SIGSEGV) > Exception Codes: KERN_INVALID_ADDRESS at 0x00007f9d00000018 > > VM Regions Near 0x7f9d00000018: > CG backing stores 000000010ec21000-000000010eef6000 [ 2900K] > rw-/rw- SM=SHM > --> > MALLOC_TINY 00007f9dd9400000-00007f9dd9500000 [ 1024K] > rw-/rwx SM=PRV > > Thread 0 Crashed:: Dispatch queue: com.apple.main-thread > 0 net.sourceforge.chicken 0x0000000106db4cac 0x106da0000 + > 85164 > 1 com.apple.AppKit 0x00007fff91d7f689 -[NSView > _drawRect:clip:] + 4238 > 2 com.apple.AppKit 0x00007fff91d7dcfa -[NSView > _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1875 > 3 com.apple.AppKit 0x00007fff91d7e0fe -[NSView > _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2903 > 4 com.apple.AppKit 0x00007fff91d7e0fe -[NSView > _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2903 > 5 com.apple.AppKit 0x00007fff91d7e0fe -[NSView > _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2903 > 6 com.apple.AppKit 0x00007fff91d7e0fe -[NSView > _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2903 > 7 com.apple.AppKit 0x00007fff91d7bb96 -[NSView > _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] > + 913 > 8 com.apple.AppKit 0x00007fff91d7b2f3 -[NSThemeFrame > _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] > + 333 > 9 com.apple.AppKit 0x00007fff91d7768b -[NSView > _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + > 2761 > 10 com.apple.AppKit 0x00007fff91d2f1ae -[NSView > displayIfNeeded] + 1876 > 11 com.apple.AppKit 0x00007fff91d2ea09 -[NSWindow > displayIfNeeded] + 236 > 12 com.apple.AppKit 0x00007fff91d2e672 > _handleWindowNeedsDisplayOrLayoutOrUpdateConstraints + 936 > 13 com.apple.AppKit 0x00007fff92464171 __83-[NSWindow > _postWindowNeedsDisplayOrLayoutOrUpdateConstraintsUnlessPostingDisabled]_block_invoke1540 > + 46 > 14 com.apple.CoreFoundation 0x00007fff8fe5b127 > __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 > 15 com.apple.CoreFoundation 0x00007fff8fe5b080 > __CFRunLoopDoObservers + 368 > 16 com.apple.CoreFoundation 0x00007fff8fe4d188 __CFRunLoopRun > + 872 > 17 com.apple.CoreFoundation 0x00007fff8fe4cbd8 > CFRunLoopRunSpecific + 296 > 18 com.apple.HIToolbox 0x00007fff9071156f > RunCurrentEventLoopInMode + 235 > 19 com.apple.HIToolbox 0x00007fff907112ea > ReceiveNextEventCommon + 431 > 20 com.apple.HIToolbox 0x00007fff9071112b > _BlockUntilNextEventMatchingListInModeWithFilter + 71 > 21 com.apple.AppKit 0x00007fff91d2b8ab _DPSNextEvent > + 978 > 22 com.apple.AppKit 0x00007fff91d2ae58 > -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346 > 23 com.apple.AppKit 0x00007fff91d20af3 > -[NSApplication run] + 594 > 24 com.apple.AppKit 0x00007fff91c9d244 > NSApplicationMain + 1832 > 25 libdyld.dylib 0x00007fff9761d5c9 start + 1 > > Thread 1:: Dispatch queue: com.apple.libdispatch-manager > 0 libsystem_kernel.dylib 0x00007fff8ae10232 kevent64 + 10 > 1 libdispatch.dylib 0x00007fff9594a26e > _dispatch_mgr_thread + 52 > > Thread 2: > 0 libsystem_kernel.dylib 0x00007fff8ae0f94a > __workq_kernreturn + 10 > 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread > + 13 > > Thread 3: > 0 libsystem_kernel.dylib 0x00007fff8ae0f94a > __workq_kernreturn + 10 > 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread > + 13 > > Thread 4:: Dispatch queue: NSUIHeartBeatOperationQueue :: NSOperation > 0x7f9dd9513dd0 (QOS: USER_INITIATED) > 0 libsystem_kernel.dylib 0x00007fff8ae0f166 > __psynch_mutexwait + 10 > 1 com.apple.Foundation 0x00007fff95c9f817 -[NSLock lock] > + 145 > 2 com.apple.AppKit 0x00007fff91fadbcf > __37-[NSUIHeartBeat updateHeartBeatState]_block_invoke142 + 60 > 3 com.apple.Foundation 0x00007fff95cf68b8 > __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 7 > 4 com.apple.Foundation 0x00007fff95cf6685 > -[NSBlockOperation main] + 97 > 5 com.apple.Foundation 0x00007fff95cf5b3c > -[__NSOperationInternal _start:] + 653 > 6 com.apple.Foundation 0x00007fff95cf5613 > __NSOQSchedule_f + 184 > 7 libdispatch.dylib 0x00007fff95945e73 > _dispatch_client_callout + 8 > 8 libdispatch.dylib 0x00007fff959495cd > _dispatch_queue_drain + 1100 > 9 libdispatch.dylib 0x00007fff95949030 > _dispatch_queue_invoke + 202 > 10 libdispatch.dylib 0x00007fff95948bef > _dispatch_root_queue_drain + 463 > 11 libdispatch.dylib 0x00007fff95948a1c > _dispatch_worker_thread3 + 91 > 12 libsystem_pthread.dylib 0x00007fff8efd5a9d > _pthread_wqthread + 729 > 13 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread > + 13 > > Thread 5: > 0 libsystem_kernel.dylib 0x00007fff8ae0f94a > __workq_kernreturn + 10 > 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread > + 13 > > Thread 6:: com.apple.CFSocket.private > 0 libsystem_kernel.dylib 0x00007fff8ae0f3fa __select + 10 > 1 libsystem_pthread.dylib 0x00007fff8efd605a _pthread_body > + 131 > 2 libsystem_pthread.dylib 0x00007fff8efd5fd7 _pthread_start > + 176 > 3 libsystem_pthread.dylib 0x00007fff8efd33ed thread_start + > 13 > > Thread 7: > 0 libsystem_kernel.dylib 0x00007fff8ae0a4de mach_msg_trap > + 10 > 1 libsystem_kernel.dylib 0x00007fff8ae0964f mach_msg + 55 > 2 com.apple.CoreFoundation 0x00007fff8fe4deb4 > __CFRunLoopServiceMachPort + 212 > 3 com.apple.CoreFoundation 0x00007fff8fe4d37b __CFRunLoopRun > + 1371 > 4 com.apple.CoreFoundation 0x00007fff8fe4cbd8 > CFRunLoopRunSpecific + 296 > 5 com.apple.AppKit 0x00007fff91df356b _NSEventThread > + 137 > 6 libsystem_pthread.dylib 0x00007fff8efd605a _pthread_body > + 131 > 7 libsystem_pthread.dylib 0x00007fff8efd5fd7 _pthread_start > + 176 > 8 libsystem_pthread.dylib 0x00007fff8efd33ed thread_start + > 13 > > Thread 8: > 0 libsystem_kernel.dylib 0x00007fff8ae0f94a > __workq_kernreturn + 10 > 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread > + 13 > > Thread 9: > 0 libsystem_kernel.dylib 0x00007fff8ae0f94a > __workq_kernreturn + 10 > 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread > + 13 > > Thread 10: > 0 libsystem_kernel.dylib 0x00007fff8ae0f94a > __workq_kernreturn + 10 > 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread > + 13 > > Thread 11: > 0 libsystem_kernel.dylib 0x00007fff8ae0f94a > __workq_kernreturn + 10 > 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread > + 13 > > Thread 12: > 0 libsystem_kernel.dylib 0x00007fff8ae0f94a > __workq_kernreturn + 10 > 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread > + 13 > > Thread 13:: com.apple.appkit-heartbeat > 0 libsystem_kernel.dylib 0x00007fff8ae0f48a > __semwait_signal + 10 > 1 libsystem_c.dylib 0x00007fff939f6e34 usleep + 54 > 2 com.apple.AppKit 0x00007fff91fa1e43 > -[NSUIHeartBeat _heartBeatThread:] + 2376 > 3 com.apple.Foundation 0x00007fff95cdae92 > __NSThread__main__ + 1345 > 4 libsystem_pthread.dylib 0x00007fff8efd605a _pthread_body > + 131 > 5 libsystem_pthread.dylib 0x00007fff8efd5fd7 _pthread_start > + 176 > 6 libsystem_pthread.dylib 0x00007fff8efd33ed thread_start + > 13 > > Thread 0 crashed with X86 Thread State (64-bit): > rax: 0x00007f9d00000000 rbx: 0x0000000000000000 rcx: > 0x00007f9dda009188 rdx: 0x00007fff58e5c788 > rdi: 0x00007f9dd9476680 rsi: 0x00007fff96cd0fff rbp: > 0x00007fff58e5c920 rsp: 0x00007fff58e5c880 > r8: 0x000000000000007f r9: 0x00007f9dd9476680 r10: > 0x00007f9dd97cf460 r11: 0x00007fff79a3dc60 > r12: 0x00000000000000c8 r13: 0x00007f9dd95a7e20 r14: > 0x0000000106de41bf r15: 0x0000000000000000 > rip: 0x0000000106db4cac rfl: 0x0000000000010246 cr2: > 0x00007f9d00000018 > > Logical CPU: 0 > Error Code: 0x00000004 > Trap Number: 14 > > Binary Images: > 0x106da0000 - 0x106df4fff +net.sourceforge.chicken (2.2b2 - > 2.2b2) <6D2FD694-6FB8-3F28-B85A-F38E2772A27F> > /Applications/MacPorts/Chicken.app/Contents/MacOS/Chicken > 0x106e16000 - 0x106e2dfff +org.andymatuschak.Sparkle (1.5 > Beta 6 - 313) <9253F8F7-250B-1114-7AE9-A10A54EB2298> > /Applications/MacPorts/Chicken.app/Contents/Frameworks/Sparkle.framework/Versions/A/Sparkle > 0x10b285000 - 0x10b28cff7 libCGCMS.A.dylib (788.3.6) > <09FA0C10-FAF1-362E-B0D7-2FC0BB19D386> > /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGCMS.A.dylib > 0x10c098000 - 0x10c09bffb libCGXType.A.dylib (788.3.6) > <2E327789-01E0-34C4-B387-A984A8DA7189> > /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGXType.A.dylib > 0x10c5c9000 - 0x10c5f1fff libRIP.A.dylib (788.3.6) > <903F88F3-DA15-3A95-AD1C-F0EA0AFC57C9> > /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib > 0x10e3fe000 - 0x10e3fefef +cl_kernels (???) > cl_kernels > 0x10e40c000 - 0x10e40cff5 +cl_kernels (???) > <145CB753-4111-446D-9269-DE8B92FB9A15> cl_kernels > 0x10e40e000 - 0x10e4f4fef unorm8_bgra.dylib (2.4.5) > <9980365E-FADF-36CB-97CC-2530BB70BA8A> > /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/ImageFormats/unorm8_bgra.dylib > 0x7fff6d6db000 - 0x7fff6d71192f dyld (353.2.4) <708E385E- > 50C6-32A3-983C-42E97BEE4346> /usr/lib/dyld > 0x7fff88121000 - 0x7fff8816bfff com.apple.HIServices (1.22 - > 523) <99ADA325-53C8-368E-A5FA-3F913CD2245A> > /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices > 0x7fff881cc000 - 0x7fff881d9ff7 libbz2.1.0.dylib (36) <2DF83FBC- > 5C08-39E1-94F5-C28653791B5F> /usr/lib/libbz2.1.0.dylib > 0x7fff8829b000 - 0x7fff8829ffff com.apple.TCC (1.0 - 1) > > /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC > 0x7fff882a0000 - 0x7fff882acff7 com.apple.OpenDirectory (10.10 - > 187) <22FF4721-03D8-381B-AA83-2B07D690C777> > /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory > 0x7fff882ad000 - 0x7fff882adfff com.apple.ApplicationServices > (48 - 48) <5BF7910B-C328-3BF8-BA4F-CE52B574CE01> > /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices > 0x7fff8855a000 - 0x7fff8859aff7 libGLImage.dylib (11.1.6) > > /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib > 0x7fff885ab000 - 0x7fff885b0fff com.apple.DiskArbitration (2.6 - > 2.6) <0DFF4D9B-2AC3-3B82-B5C5-30F4EFBD2DB9> > /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration > 0x7fff88684000 - 0x7fff8869eff7 com.apple.Kerberos (3.0 - 1) > <7760E0C2-A222-3709-B2A6-B692D900CEB1> > /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos > 0x7fff8869f000 - 0x7fff886aaff7 libkxld.dylib (2782.50.9) > /usr/lib/system/libkxld.dylib > 0x7fff886ab000 - 0x7fff88767ff7 libcrypto.0.9.7.dylib (106) > /usr/lib/libcrypto.0.9.7.dylib > 0x7fff88768000 - 0x7fff88775ff3 com.apple.ProtocolBuffer (1 - > 228.0.1) <3429EB06-9F0E-355F-B9AB-F72879177398> > /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer > 0x7fff88776000 - 0x7fff887a6ff3 com.apple.GSS (4.0 - 2.0) > <97F2A028-44CF-3188-B863-F4EEB39CBDBD> > /System/Library/Frameworks/GSS.framework/Versions/A/GSS > 0x7fff887a7000 - 0x7fff887a7ff7 libunc.dylib (29) <5676F7EA- > C1DF-329F-B006-D2C3022B7D70> /usr/lib/system/libunc.dylib > 0x7fff887be000 - 0x7fff887d0ff7 libsasl2.2.dylib (194.1) > <35371406-75EF-304A-A073-956C40373555> /usr/lib/libsasl2.2.dylib > 0x7fff8885c000 - 0x7fff88861fff libsystem_stats.dylib (163.30.2) > > /usr/lib/system/libsystem_stats.dylib > 0x7fff88862000 - 0x7fff88862fff com.apple.Accelerate (1.10 - > Accelerate 1.10) <2C8AF258-4F11-3BEC-A826-22D7199B3975> > /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate > 0x7fff88904000 - 0x7fff8892dff3 libxslt.1.dylib (13.12) > <19B2D915-DC29-3F79-9756-D7EB9051FEFF> /usr/lib/libxslt.1.dylib > 0x7fff8892e000 - 0x7fff88934fff > com.apple.speech.recognition.framework (5.0.9 - 5.0.9) -379F-A2BA-3C454EDCB111> > /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition > 0x7fff88935000 - 0x7fff88c68ff7 libmecabra.dylib (666.7) > <0ED8AE5E-7A5B-34A6-A2EE-2B852E60E1E2> /usr/lib/libmecabra.dylib > 0x7fff88c69000 - 0x7fff88cb5fff com.apple.corelocation (1486.17 > - 1615.24) <8825B3E2-E053-3E01-AE31-793443962D06> > /System/Library/Frameworks/CoreLocation.framework/Versions/A/CoreLocation > 0x7fff88cbc000 - 0x7fff88cc1ffb libheimdal-asn1.dylib (398.40.1) > <7D2BE3DE-60F7-3A6E-A92E-DA0EF9D3417E> /usr/lib/libheimdal-asn1.dylib > 0x7fff88cc2000 - 0x7fff88e0aff7 com.apple.WebKitLegacy (10600 - > 10600.8.9) > /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebKitLegacy.framework/Versions/A/WebKitLegacy > 0x7fff88e0b000 - 0x7fff88e0ffff libcache.dylib (69) > <45E9A2E7-99C4-36B2-BEE3-0C4E11614AD1> /usr/lib/system/libcache.dylib > 0x7fff88e10000 - 0x7fff88e11ff7 com.apple.print.framework.Print > (10.0 - 265) <3BC4FE7F-78A0-3E57-8F4C-520E7EFD36FA> > /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print > 0x7fff88e15000 - 0x7fff88f39ff7 com.apple.LaunchServices (644.56 > - 644.56) <20AABB1C-9319-3E4D-A024-51B0DD5FCD3B> > /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices > 0x7fff89931000 - 0x7fff8993cfff libGL.dylib (11.1.6) > <38B3FF9A-5660-3080-9DB8-1CAE0E8CD739> > /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib > 0x7fff89945000 - 0x7fff89969ff7 com.apple.Sharing (328.17 - > 328.17) > /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing > 0x7fff8996a000 - 0x7fff8a1aeff7 com.apple.CoreGraphics (1.600.0 > - 788.3.6) <3C5D7B35-2EB7-3907-A6B1-9186BDEA2CC8> > /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics > 0x7fff8a1af000 - 0x7fff8a1b0ff3 libSystem.B.dylib (1213) > <4B24B5BE-45F2-355A-9A35-D438A516D140> /usr/lib/libSystem.B.dylib > 0x7fff8a1b1000 - 0x7fff8a396ff7 libicucore.A.dylib (531.50) > /usr/lib/libicucore.A.dylib > 0x7fff8a58a000 - 0x7fff8a592ff7 com.apple.AppleSRP (5.0 - 1) > <68F0C577-ED96-34F2-B701-CE3023367D4D> > /System/Library/PrivateFrameworks/AppleSRP.framework/Versions/A/AppleSRP > 0x7fff8a598000 - 0x7fff8a637e27 com.apple.AppleJPEG (1.0 - 1) > <6627DDD9-A8FE-3968-B23A-B6A29AA3919A> > /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG > 0x7fff8a638000 - 0x7fff8a6c9ff7 libCoreStorage.dylib (471.30.1) > <9D95399F-1AC5-325F-8337-6E13AD99E44B> /usr/lib/libCoreStorage.dylib > 0x7fff8a759000 - 0x7fff8a7c7ff3 com.apple.Heimdal (4.0 - 2.0) > <8D1667CF-D454-3E07-A58E-E15591B5A95E> > /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal > 0x7fff8a7c8000 - 0x7fff8abf8fff com.apple.vision.FaceCore (3.1.6 > - 3.1.6) > /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore > 0x7fff8abfe000 - 0x7fff8ac87ff7 com.apple.CoreSymbolication (3.1 > - 57020.2) > /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication > 0x7fff8ac88000 - 0x7fff8ada1ffb com.apple.CoreText (454.11 - > 454.11) <7E5228C8-8657-3B6C-B3A4-98B79A3041EA> > /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText > 0x7fff8adf9000 - 0x7fff8ae16fff libsystem_kernel.dylib > (2782.50.9) > /usr/lib/system/libsystem_kernel.dylib > 0x7fff8b0f7000 - 0x7fff8b175fff > com.apple.CoreServices.OSServices (640.4 - 640.4) > <9D175CD9-B27F-3529-8269-66D8AA83582E> > /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices > 0x7fff8b179000 - 0x7fff8b1e5ff3 com.apple.MMCS (1.3 - 327.5) > > /System/Library/PrivateFrameworks/MMCS.framework/Versions/A/MMCS > 0x7fff8b279000 - 0x7fff8b281fff libsystem_dnssd.dylib (576.50.2) > <9EC5AF92-D0D2-3BDE-92B6-D3730D3865C8> > /usr/lib/system/libsystem_dnssd.dylib > 0x7fff8b34b000 - 0x7fff8b3c3ff7 com.apple.SystemConfiguration > (1.14.4 - 1.14) <3DFFD7F7-BD23-3F4C-A209-C4A0D99F6573> > /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration > 0x7fff8b3dc000 - 0x7fff8b4cdfff libJP2.dylib (1247) -C27E-3D7C-89D0-BE999596E2B1> > /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib > 0x7fff8b4dd000 - 0x7fff8b598ff7 com.apple.DiscRecording (9.0 - > 9000.4.2) <4655B4B8-523D-3AE6-92A0-8486A2258B3B> > /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording > 0x7fff8b599000 - 0x7fff8b5d4fff com.apple.QD (301 - 301) > > /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD > 0x7fff8b627000 - 0x7fff8b693fff com.apple.framework.CoreWLAN > (5.0 - 500.35.2) <03697149-1CDD-32FF-B564-1C1EF5E9E5C3> > /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN > 0x7fff8b694000 - 0x7fff8b6affff com.apple.AppleVPAFramework > (1.4.5 - 1.4.5) > /System/Library/PrivateFrameworks/AppleVPA.framework/Versions/A/AppleVPA > 0x7fff8b6f4000 - 0x7fff8b6ffff7 com.apple.CrashReporterSupport > (10.10 - 631) > /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport > 0x7fff8b700000 - 0x7fff8b730fff libsystem_m.dylib (3086.1) > <1E12AB45-6D96-36D0-A226-F24D9FB0D9D6> /usr/lib/system/libsystem_m.dylib > 0x7fff8b7e9000 - 0x7fff8b7ecfff com.apple.xpc.ServiceManagement > (1.0 - 1) > /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement > 0x7fff8b7ed000 - 0x7fff8b88ffff com.apple.Bluetooth (4.3.6 - > 4.3.6f4) > /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth > 0x7fff8bbbd000 - 0x7fff8bbd4ff7 libLinearAlgebra.dylib (1128) > > /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib > 0x7fff8bbd5000 - 0x7fff8bc02fff com.apple.CoreVideo (1.8 - > 145.1) <18DB07E0-B927-3260-A234-636F298D1917> > /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo > 0x7fff8bc2e000 - 0x7fff8bc52fef libJPEG.dylib (1247) <78AA0479 > -176D-3C69-ADFB-4609A4A676FF> > /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib > 0x7fff8bc57000 - 0x7fff8bc57ff7 libkeymgr.dylib (28) > <77845842-DE70-3CC5-BD01-C3D14227CED5> /usr/lib/system/libkeymgr.dylib > 0x7fff8bc81000 - 0x7fff8bca9fff libsystem_info.dylib (459.40.1) > <2E16C4B3-A327-3957-9C41-143911979A1E> > /usr/lib/system/libsystem_info.dylib > 0x7fff8bcaa000 - 0x7fff8bcb2ffb libcopyfile.dylib (118.1.2) > <0C68D3A6-ACDD-3EF3-991A-CC82C32AB836> /usr/lib/system/libcopyfile.dylib > 0x7fff8be1e000 - 0x7fff8be20fff libsystem_configuration.dylib > (699.40.2) <56F94DCE-DBDE-3615-8F07-DE6270D9F8BE> > /usr/lib/system/libsystem_configuration.dylib > 0x7fff8be30000 - 0x7fff8be38fff libsystem_platform.dylib (63) > <64E34079-D712-3D66-9CE2-418624A5C040> > /usr/lib/system/libsystem_platform.dylib > 0x7fff8be39000 - 0x7fff8be3cfff com.apple.IOSurface (97.4 - > 97.4) > /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface > 0x7fff8be3d000 - 0x7fff8ce00ff3 com.apple.WebCore (10600 - > 10600.8.9) > /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/WebCore > 0x7fff8ce01000 - 0x7fff8ce68ff7 com.apple.framework.CoreWiFi > (3.0 - 300.4) <19269C1D-EB29-384A-83F3-7DDDEB7D9DAD> > /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi > 0x7fff8ce69000 - 0x7fff8cec8fff com.apple.AE (681.5 - 681.7) > <2BF39455-1CDD-392C-824A-9972C6B1FB57> > /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE > 0x7fff8cec9000 - 0x7fff8cee4ff7 libCRFSuite.dylib (34) > /usr/lib/libCRFSuite.dylib > 0x7fff8d14e000 - 0x7fff8d2dcfff libBLAS.dylib (1128) > <497912C1-A98E-3281-BED7-E9C751552F61> > /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib > 0x7fff8d2dd000 - 0x7fff8d2e5fe7 libcldcpuengine.dylib (2.4.5) > > /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib > 0x7fff8d2f1000 - 0x7fff8d2f3fff com.apple.loginsupport (1.0 - 1) > > /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport > 0x7fff8daa9000 - 0x7fff8db9dff7 libFontParser.dylib (134.10) > <6CF434A2-91CA-3477-BDE2-124508EDA05D> > /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib > 0x7fff8dbc5000 - 0x7fff8dfd2ff7 libLAPACK.dylib (1128) > > /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib > 0x7fff8e054000 - 0x7fff8e087fff com.apple.MediaKit (16 - 757.2) > <2912E5C2-085F-3FE2-8531-23B6E894B0F0> > /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit > 0x7fff8e12d000 - 0x7fff8e146ff7 com.apple.CFOpenDirectory (10.10 > - 187) > /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory > 0x7fff8e297000 - 0x7fff8e298ff7 libsystem_blocks.dylib (65) > <9615D10A-FCA7-3BE4-AA1A-1B195DACE1A1> > /usr/lib/system/libsystem_blocks.dylib > 0x7fff8e2e8000 - 0x7fff8e34fffb com.apple.datadetectorscore (6.0 > - 396.1.2) > /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore > 0x7fff8e350000 - 0x7fff8e350fff com.apple.audio.units.AudioUnit > (1.12 - 1.12) > /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit > 0x7fff8e351000 - 0x7fff8e356ff7 libunwind.dylib (35.3) -B6EA-3A54-9CCA-9D88F683A6D6> /usr/lib/system/libunwind.dylib > 0x7fff8e357000 - 0x7fff8e378fff com.apple.framework.Apple80211 > (10.3 - 1030.71.6) > /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211 > 0x7fff8e379000 - 0x7fff8e37bfff libsystem_sandbox.dylib > (358.20.5) <3F5E973F-C702-31AC-97BC-05F5C195683C> > /usr/lib/system/libsystem_sandbox.dylib > 0x7fff8e37c000 - 0x7fff8e38eff7 com.apple.ImageCapture (9.0 - > 9.0) <7FB65DD4-56B5-35C4-862C-7A2DED991D1F> > /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture > 0x7fff8e4aa000 - 0x7fff8e4c4ff7 liblzma.5.dylib (7) > <1D03E875-A7C0-3028-814C-3C27F7B7C079> /usr/lib/liblzma.5.dylib > 0x7fff8e4f5000 - 0x7fff8e630fff com.apple.ImageIO.framework > (3.3.0 - 1247) > /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO > 0x7fff8e631000 - 0x7fff8e640fff com.apple.LangAnalysis (1.7.0 - > 1.7.0) > /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis > 0x7fff8efac000 - 0x7fff8efd1fff libPng.dylib (1247) <1E8B06AA- > 1DC5-3845-88D9-B2F8E6E1E540> > /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib > 0x7fff8efd2000 - 0x7fff8efdbfff libsystem_pthread.dylib > (105.40.1) > /usr/lib/system/libsystem_pthread.dylib > 0x7fff8efdc000 - 0x7fff8efecff7 libbsm.0.dylib (34) 2B65-37C7-B43A-A1F926E1A0BB> /usr/lib/libbsm.0.dylib > 0x7fff8f0b1000 - 0x7fff8f327fff com.apple.security (7.0 - > 57031.40.8) > /System/Library/Frameworks/Security.framework/Versions/A/Security > 0x7fff8f328000 - 0x7fff8f32bfff com.apple.help (1.3.3 - 46) > > /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help > 0x7fff8f387000 - 0x7fff8f89cfff com.apple.JavaScriptCore (10600 > - 10600.8.7.1) <4C48FD32-ACA3-358F-95D9-05DBB56A1DED> > /System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore > 0x7fff8f89d000 - 0x7fff8f8f1fff libc++.1.dylib (120) <1B9530FD- > 989B-3174-BB1C-BDC159501710> /usr/lib/libc++.1.dylib > 0x7fff8f8f2000 - 0x7fff8f9a1fe7 libvMisc.dylib (516) > <6739E390-46E7-3BFA-9B69-B278562326E6> > /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib > 0x7fff8f9a2000 - 0x7fff8f9edff7 com.apple.CloudDocs (1.0 - > 321.10) > /System/Library/PrivateFrameworks/CloudDocs.framework/Versions/A/CloudDocs > 0x7fff8f9ee000 - 0x7fff8fa3dff7 libcurl.4.dylib (83.40.2) > /usr/lib/libcurl.4.dylib > 0x7fff8fd2b000 - 0x7fff8fd9cffb > com.apple.ApplicationServices.ATS (360 - 375.4) <888FE0B1-835C-30B1-80AD- > 5066CADB0364> > /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS > 0x7fff8fddb000 - 0x7fff90173ff7 com.apple.CoreFoundation (6.9 - > 1153.18) <5C0892B8-9691-341F-9279-CA3A74D59AA0> > /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation > 0x7fff90174000 - 0x7fff90186ff7 com.apple.CoreDuetDaemonProtocol > (1.0 - 1) > /System/Library/PrivateFrameworks/CoreDuetDaemonProtocol.framework/Versions/A/CoreDuetDaemonProtocol > 0x7fff9018a000 - 0x7fff90409ff7 com.apple.CoreData (111 - 526.3) > <5A27E0D8-5E5A-335B-B3F6-2601C7B976FA> > /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData > 0x7fff9040a000 - 0x7fff906cdff7 com.apple.WebKit (10600 - > 10600.8.9) <8EE5A9F9-DE98-3202-92C0-23F6E6E5E274> > /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit > 0x7fff906ce000 - 0x7fff906dbfff libxar.1.dylib (255) > <7CD69BB5-97BA-3858-8A8B-2F33F129E6E7> /usr/lib/libxar.1.dylib > 0x7fff906dc000 - 0x7fff906deff7 libsystem_coreservices.dylib (9) > <41B7C578-5A53-31C8-A96F-C73E030B0938> > /usr/lib/system/libsystem_coreservices.dylib > 0x7fff906df000 - 0x7fff909e4ff3 com.apple.HIToolbox (2.1.1 - > 758.7) > /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox > 0x7fff909ee000 - 0x7fff90a5dfff com.apple.SearchKit (1.4.0 - > 1.4.0) <80883BD1-C9BA-3794-A20E-476F94DD89A9> > /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit > 0x7fff90a5e000 - 0x7fff90b50ff7 libiconv.2.dylib (42) <2A06D02F- > 8B76-3864-8D96-64EF5B40BC6C> /usr/lib/libiconv.2.dylib > 0x7fff90b92000 - 0x7fff90bacff7 libextension.dylib (55.2) > <3BB019CA-199A-36AC-AA22-14B562138545> /usr/lib/libextension.dylib > 0x7fff90bad000 - 0x7fff90bb3ff7 libsystem_networkextension.dylib > (167.40.3) > /usr/lib/system/libsystem_networkextension.dylib > 0x7fff90bb4000 - 0x7fff90c49ff7 com.apple.ColorSync (4.9.0 - > 4.9.0) <9150C2B7-2E6E-3509-96EA-7B3F959F049E> > /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync > 0x7fff90cde000 - 0x7fff90fadff3 com.apple.CoreImage (10.3.5) > <0224F5A6-636A-374B-B46C-13E066596725> > /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/CoreImage.framework/Versions/A/CoreImage > 0x7fff914f7000 - 0x7fff916a7ff3 com.apple.QuartzCore (1.10 - > 361.19) > /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore > 0x7fff916cb000 - 0x7fff91761ff7 com.apple.cloudkit.CloudKit > (283.67.4 - 283.67.4) > /System/Library/Frameworks/CloudKit.framework/Versions/A/CloudKit > 0x7fff91793000 - 0x7fff9179cff7 libsystem_notify.dylib (133.1.1) > <61147800-F320-3DAA-850C-BADF33855F29> > /usr/lib/system/libsystem_notify.dylib > 0x7fff918d2000 - 0x7fff91918ff7 libFontRegistry.dylib (134.1) > > /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib > 0x7fff91919000 - 0x7fff91926ff7 com.apple.SpeechRecognitionCore > (2.1.2 - 2.1.2) <551322E2-C1E4-3378-A218-F362985E3E3C> > /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore > 0x7fff91927000 - 0x7fff91ba5ff7 com.apple.RawCamera.bundle > (6.04.1 - 798) <7988A25F-2A69-311E-929E-B70D164739F4> > /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera > 0x7fff91ba6000 - 0x7fff91bc5fff com.apple.CoreDuet (1.0 - 1) > <36AA9FD5-2685-314D-B364-3FA4688D86BD> > /System/Library/PrivateFrameworks/CoreDuet.framework/Versions/A/CoreDuet > 0x7fff91bc6000 - 0x7fff91c20ff7 com.apple.LanguageModeling (1.0 > - 1) > /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling > 0x7fff91c4f000 - 0x7fff91c60ff7 libz.1.dylib (55) <88C7C7DE-04B8 > -316F-8B74-ACD9F3DE1AA1> /usr/lib/libz.1.dylib > 0x7fff91c61000 - 0x7fff91c99fff com.apple.RemoteViewServices > (2.0 - 99) > /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices > 0x7fff91c9a000 - 0x7fff9281bff7 com.apple.AppKit (6.9 - 1348.17) > > /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit > 0x7fff9281c000 - 0x7fff9294cfff com.apple.UIFoundation (1.0 - 1) > <466BDFA8-0B9F-3AB0-989D-F9779422926A> > /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation > 0x7fff9294d000 - 0x7fff92966ff3 com.apple.openscripting (1.6.4 - > 162.2) > /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting > 0x7fff92967000 - 0x7fff92998ff7 com.apple.ProtectedCloudStorage > (1.0 - 1) <9D76F2E0-C28A-3DBC-A91F-E87888D46BF0> > /System/Library/PrivateFrameworks/ProtectedCloudStorage.framework/Versions/A/ProtectedCloudStorage > 0x7fff9323e000 - 0x7fff93269fff libc++abi.dylib (125) <88A22A0F- > 87C6-3002-BFBA-AC0F2808B8B9> /usr/lib/libc++abi.dylib > 0x7fff9326a000 - 0x7fff9326afff com.apple.Carbon (154 - 157) > <9BF51672-1684-3FDE-A561-FC59A2864EF8> > /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon > 0x7fff93278000 - 0x7fff93281fff libGFXShared.dylib (11.1.6) > > /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib > 0x7fff93282000 - 0x7fff93342ff7 com.apple.backup.framework > (1.6.5 - 1.6.5) <86396038-33EA-3046-9F70-093A3D6407D4> > /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup > 0x7fff93347000 - 0x7fff93358ff3 libsystem_coretls.dylib > (35.40.1) <155DA0A9-2046-332E-BFA3-D7974A51F731> > /usr/lib/system/libsystem_coretls.dylib > 0x7fff93359000 - 0x7fff93640ffb > com.apple.CoreServices.CarbonCore (1108.6 - 1108.6) > <8953580E-7857-33B2-AA64-98296830D3A8> > /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore > 0x7fff936bf000 - 0x7fff93753fff com.apple.ink.framework (10.9 - > 213) <8E029630-1530-3734-A446-13353F0E7AC5> > /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink > 0x7fff93855000 - 0x7fff938c9ffb com.apple.securityfoundation > (6.0 - 55126) <344401F5-4016-3AEB-BFDC-CE8E5546D39F> > /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation > 0x7fff938ca000 - 0x7fff93904ffb com.apple.DebugSymbols (115 - > 115) <6F03761D-7C3A-3C80-8031-AA1C1AD7C706> > /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols > 0x7fff93905000 - 0x7fff93960fe7 libTIFF.dylib (1247) <43CB4BDE- > 84FD-3CCE-96C0-FB33BA2753BD> > /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib > 0x7fff93961000 - 0x7fff93977ff7 libsystem_asl.dylib (267) > > /usr/lib/system/libsystem_asl.dylib > 0x7fff93978000 - 0x7fff93a04fef libsystem_c.dylib (1044.40.3) > <2E673D96-E334-37D2-833A-E57383BBA377> /usr/lib/system/libsystem_c.dylib > 0x7fff93a1b000 - 0x7fff93a68ff7 > com.apple.print.framework.PrintCore (10.3 - 451.1) > > /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore > 0x7fff93ebf000 - 0x7fff93f5dfff com.apple.Metadata (10.7.0 - > 917.36) <00C4CB5D-E723-3612-84E0-439098392CDD> > /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata > 0x7fff93f5e000 - 0x7fff93fd0fff com.apple.framework.IOKit (2.0.2 > - 1050.20.2) <09C0518C-90DF-3FC3-96D6-34D35F72C8EF> > /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit > 0x7fff93fd1000 - 0x7fff93fedff7 libsystem_malloc.dylib (53.30.1) > > /usr/lib/system/libsystem_malloc.dylib > 0x7fff93ffe000 - 0x7fff9403ffff libGLU.dylib (11.1.6) <4BC6579D- > A6D0-3A19-880E-E29FAEA698E7> > /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib > 0x7fff94040000 - 0x7fff940c4fff com.apple.PerformanceAnalysis > (1.0 - 1) <095E6B1C-DC20-38DC-8931-16041B0489C7> > /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis > 0x7fff94130000 - 0x7fff94135ff7 libmacho.dylib (862) <126CA2ED- > DE91-308F-8881-B9DAEC3C63B6> /usr/lib/system/libmacho.dylib > 0x7fff9413a000 - 0x7fff94171ffb com.apple.LDAPFramework (2.4.28 > - 194.5) > /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP > 0x7fff94172000 - 0x7fff94183fff libcmph.dylib (1) <46EC3997 > -DB5E-38AE-BBBB-A035A54AD3C0> /usr/lib/libcmph.dylib > 0x7fff941da000 - 0x7fff9420cff3 com.apple.frameworks.CoreDaemon > (1.3 - 1.3) > /System/Library/PrivateFrameworks/CoreDaemon.framework/Versions/B/CoreDaemon > 0x7fff9439b000 - 0x7fff943affeb libCGInterfaces.dylib (294.1) > <390D4B3F-B738-3D33-BEDB-07E3F0F6B42C> > /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib > 0x7fff943b5000 - 0x7fff94401ff7 libcups.2.dylib (408.2) > /usr/lib/libcups.2.dylib > 0x7fff9444f000 - 0x7fff9446cffb libresolv.9.dylib (57) <26B38E61 > -298A-3C3A-82C1-3B5E98AD5E29> /usr/lib/libresolv.9.dylib > 0x7fff945fd000 - 0x7fff9470fff7 libvDSP.dylib (516) <151B3CCB- > 77D3-3715-A3D0-7C74CD5C7FFC> > /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib > 0x7fff94795000 - 0x7fff948dbfef libsqlite3.dylib (168.2) > <53F6A294-15D7-3804-9ABF-47D35E15CDFB> /usr/lib/libsqlite3.dylib > 0x7fff948dc000 - 0x7fff94907ff7 com.apple.DictionaryServices > (1.2 - 229.1) <62EC3E1B-5A28-3252-90FF-C2E9999C2A2A> > /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices > 0x7fff94908000 - 0x7fff94914fff > com.apple.speech.synthesis.framework (5.3.11 - 5.3.11) > > /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis > 0x7fff94d01000 - 0x7fff94d27fff com.apple.ChunkingLibrary (2.1 - > 163.6) <29D4CB95-42EF-34C6-8182-BDB6F7BB1E79> > /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary > 0x7fff94d28000 - 0x7fff95043fcf com.apple.vImage (8.0 - 8.0) > <1183FE6A-FDB6-3B3B-928D-50C7909F2308> > /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage > 0x7fff95049000 - 0x7fff95074ffb libarchive.2.dylib (30.50.1) > /usr/lib/libarchive.2.dylib > 0x7fff950b0000 - 0x7fff950b0fff libOpenScriptingUtil.dylib > (162.2) > /usr/lib/libOpenScriptingUtil.dylib > 0x7fff951b1000 - 0x7fff951b3fff libquarantine.dylib (76.20.1) > <7AF90041-2768-378A-925A-D83161863642> > /usr/lib/system/libquarantine.dylib > 0x7fff951b4000 - 0x7fff951b6fff libRadiance.dylib (1247) > <0028A2E3-7928-3479-9BF7-CB64234F85AF> > /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib > 0x7fff951ba000 - 0x7fff951bcfff libCVMSPluginSupport.dylib > (11.1.6) > /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib > 0x7fff95243000 - 0x7fff95244fff libsystem_secinit.dylib (18) > <581DAD0F-6B63-3A48-B63B-917AF799ABAA> > /usr/lib/system/libsystem_secinit.dylib > 0x7fff95245000 - 0x7fff95246ffb libremovefile.dylib (35) > <3485B5F4-6CE8-3C62-8DFD-8736ED6E8531> > /usr/lib/system/libremovefile.dylib > 0x7fff952f2000 - 0x7fff9531afff libxpc.dylib (559.40.1) > <5C829202-962E-3744-8B50-00D38CC88E84> /usr/lib/system/libxpc.dylib > 0x7fff9531b000 - 0x7fff953fffff libcrypto.0.9.8.dylib (52.40.1) > /usr/lib/libcrypto.0.9.8.dylib > 0x7fff95400000 - 0x7fff95401fff > libDiagnosticMessagesClient.dylib (100) <2EE8E436-5CDC- > 34C5-9959-5BA218D507FB> /usr/lib/libDiagnosticMessagesClient.dylib > 0x7fff95402000 - 0x7fff954f4ff7 libxml2.2.dylib (26.12) > <769FD755-D24A-3A7C-ABEE-9A82BB1196D0> /usr/lib/libxml2.2.dylib > 0x7fff954f5000 - 0x7fff954fcff7 libcompiler_rt.dylib (35) > > /usr/lib/system/libcompiler_rt.dylib > 0x7fff954fd000 - 0x7fff95501ff7 libGIF.dylib (1247) > <5EA6D19A-9922-39F6-82DB-DE7A5B8860CF> > /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib > 0x7fff95817000 - 0x7fff95817fff com.apple.Cocoa (6.8 - 21) > > /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa > 0x7fff95821000 - 0x7fff95930ff3 com.apple.desktopservices (1.9.3 > - 1.9.3) > /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv > 0x7fff95944000 - 0x7fff9596eff7 libdispatch.dylib (442.50.1) > /usr/lib/system/libdispatch.dylib > 0x7fff9596f000 - 0x7fff95b7fff7 com.apple.CFNetwork (720.5.7 - > 720.5.7) > /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork > 0x7fff95c13000 - 0x7fff95c8cfe7 libcorecrypto.dylib (233.30.1) > <5779FFA0-4D9A-3AD4-B7F2-618227621DC8> > /usr/lib/system/libcorecrypto.dylib > 0x7fff95c8d000 - 0x7fff95c8ffff com.apple.EFILogin (2.0 - 2) > <3BA837D8-94F5-3240-9CF7-E40DC2808446> > /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/EFILogin > 0x7fff95c90000 - 0x7fff95c9bfff libcommonCrypto.dylib > (60061.30.1) > /usr/lib/system/libcommonCrypto.dylib > 0x7fff95c9c000 - 0x7fff95fcdfff com.apple.Foundation (6.9 - > 1154) <49EE64E1-9F53-35D1-A481-2EFE2789B254> > /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation > 0x7fff9607b000 - 0x7fff96095ff3 com.apple.Ubiquity (1.3 - 313) > > /System/Library/PrivateFrameworks/Ubiquity.framework/Versions/A/Ubiquity > 0x7fff9618e000 - 0x7fff96264ff3 com.apple.DiskImagesFramework > (10.10.5 - 398) <37291661-BCB2-3F95-B446-5E5DB1D1E472> > /System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/DiskImages > 0x7fff96265000 - 0x7fff96266fff com.apple.TrustEvaluationAgent > (2.0 - 25) <2D61A2C3-C83E-3A3F-8EC1-736DBEC250AB> > /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent > 0x7fff96274000 - 0x7fff96274fff com.apple.Accelerate.vecLib > (3.10 - vecLib 3.10) <9D749502-A228-3BF1-B52F-A182DEEB2C4D> > /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib > 0x7fff965a1000 - 0x7fff965a9ff7 com.apple.icloud.FindMyDevice > (1.0 - 1) <9CE67F85-2BA8-3093-97BA-07BF5C04A5D6> > /System/Library/PrivateFrameworks/FindMyDevice.framework/Versions/A/FindMyDevice > 0x7fff965aa000 - 0x7fff965b8ff7 com.apple.opengl (11.1.6 - > 11.1.6) > /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL > 0x7fff965d2000 - 0x7fff967cc46f libobjc.A.dylib (647) <759E155D- > BC42-3D4E-869B-6F57D477177C> /usr/lib/libobjc.A.dylib > 0x7fff967cd000 - 0x7fff967d6ff3 com.apple.CommonAuth (4.0 - 2.0) > <9A484EE6-0003-3AB1-AE4F-AA543BBBF53F> > /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth > 0x7fff967d7000 - 0x7fff967e1ff7 com.apple.NetAuth (5.2 - 5.2) > <2BBD749A-8E18-35B8-8E48-A90347C1CCA7> > /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth > 0x7fff967e2000 - 0x7fff967e6fff libpam.2.dylib (20) 9A92-31F8-8005-8DC188BD8B6E> /usr/lib/libpam.2.dylib > 0x7fff96cd8000 - 0x7fff96d10fff libsystem_network.dylib > (412.20.3) <6105C134-6722-3C0A-A4CE-5E1261E2E1CC> > /usr/lib/system/libsystem_network.dylib > 0x7fff96d11000 - 0x7fff96e39ff7 com.apple.coreui (2.1 - 308.6) > <9E0E9C6A-68F5-34C1-A17C-96226D401D4D> > /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI > 0x7fff96e3a000 - 0x7fff96e5afff com.apple.IconServices (47.1 - > 47.1) > /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices > 0x7fff96ee0000 - 0x7fff96f2fff7 com.apple.opencl (2.4.2 - 2.4.2) > <590504FA-E5D2-37C2-91A7-09F5F039F971> > /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL > 0x7fff96f30000 - 0x7fff96f4cfff com.apple.GenerationalStorage > (2.0 - 209.11) <9FF8DD11-25FB-3047-A5BF-9415339B3EEC> > /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage > 0x7fff96f4d000 - 0x7fff9724fffb com.apple.GeoServices (1.0 - > 1077.0.18) <2BBF8B44-DD46-3432-8C84-6D6AA004C233> > /System/Library/PrivateFrameworks/GeoServices.framework/Versions/A/GeoServices > 0x7fff972db000 - 0x7fff972e2fff com.apple.NetFS (6.0 - 4.0) > > /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS > 0x7fff9737d000 - 0x7fff97385ff3 com.apple.CoreServices.FSEvents > (1210.20.1 - 1210.20.1) <84F79D3E-7B5E-3C93-8479-35794A3F125E> > /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents > 0x7fff97387000 - 0x7fff97387ff7 liblaunch.dylib (559.40.1) > <4F81CA3A-D2CE-3030-A89D-42F3DAD7BA8F> /usr/lib/system/liblaunch.dylib > 0x7fff97472000 - 0x7fff97476fff com.apple.CommonPanels (1.2.6 - > 96) > /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels > 0x7fff97477000 - 0x7fff974c8fff com.apple.audio.CoreAudio (4.3.0 > - 4.3.0) <8E6AE326-9F3E-3182-BD9E-FDF561211E2E> > /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio > 0x7fff974c9000 - 0x7fff974dcff7 com.apple.CoreBluetooth (1.0 - > 1) <8D7BA9BA-EB36-307A-9119-0B3D9732C953> > /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth > 0x7fff974e5000 - 0x7fff9752bff7 libauto.dylib (186) D4D8-316A-9490-254767B8A5F1> /usr/lib/libauto.dylib > 0x7fff9752c000 - 0x7fff9752eff7 libutil.dylib (38) <471AD65E- > B86E-3C4A-8ABD-B8665A2BCE3F> /usr/lib/libutil.dylib > 0x7fff9752f000 - 0x7fff97530fff liblangid.dylib (117) > /usr/lib/liblangid.dylib > 0x7fff97549000 - 0x7fff97549fff com.apple.CoreServices (62 - 62) > > /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices > 0x7fff9756e000 - 0x7fff97574fff libsystem_trace.dylib (72.20.1) > <840F5301-B55A-3078-90B9-FEFFD6CD741A> > /usr/lib/system/libsystem_trace.dylib > 0x7fff975d9000 - 0x7fff975e4ff7 libcsfde.dylib (471.30.1) > /usr/lib/libcsfde.dylib > 0x7fff975e5000 - 0x7fff975e9fff libCoreVMClient.dylib (79.1) > <201EF6DF-5074-3CB7-A361-398CF957A264> > /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib > 0x7fff975ea000 - 0x7fff97619ff7 com.apple.CoreServicesInternal > (221.7.2 - 221.7.2) > /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal > 0x7fff9761a000 - 0x7fff9761dff7 libdyld.dylib (353.2.4) > <224F35C5-6E35-3EC4-A97C-80949CE444E7> /usr/lib/system/libdyld.dylib > 0x7fff9763d000 - 0x7fff9763fff7 com.apple.securityhi (9.0 - > 55006) <15D38919-9697-3E3A-BCB9-4E3271BC2C7E> > /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI > 0x7fff978e5000 - 0x7fff97905ff7 > com.apple.MultitouchSupport.framework (264.6 - 264.6) > <1539F1F6-6334-37F3-9C52-02EFFBF4835D> > /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport > 0x7fff97906000 - 0x7fff97a6dffb > com.apple.audio.toolbox.AudioToolbox (1.12 - 1.12) <5678FC94-456A-3F5F- > BA9A-10EB6E462997> > /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox > 0x7fff97a6e000 - 0x7fff97a70fff com.apple.CoreDuetDebugLogging > (1.0 - 1) <9A6E5710-EA99-366E-BF40-9A65EC1B46A1> > /System/Library/PrivateFrameworks/CoreDuetDebugLogging.framework/Versions/A/CoreDuetDebugLogging > 0x7fff97a8b000 - 0x7fff97ac6fff com.apple.Symbolication (1.4 - > 56045) > /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication > > External Modification Summary: > Calls made by other processes targeting this process: > task_for_pid: 1 > thread_create: 0 > thread_set_state: 0 > Calls made by this process: > task_for_pid: 0 > thread_create: 0 > thread_set_state: 0 > Calls made by all processes on this machine: > task_for_pid: 297 > thread_create: 0 > thread_set_state: 0 > > VM Region Summary: > ReadOnly portion of Libraries: Total=211.4M resident=108.2M(51%) > swapped_out_or_unallocated=103.2M(49%) > Writable regions: Total=139.9M written=7136K(5%) resident=22.7M(16%) > swapped_out=0K(0%) unallocated=117.2M(84%) > > REGION TYPE VIRTUAL > =========== ======= > Activity Tracing 2048K > CG backing stores 7792K > CG image 796K > CG shared images 368K > CoreAnimation 3200K > CoreImage 16K > CoreUI image data 440K > Dispatch continuations 16.0M > Foundation 4K > Image IO 464K > Kernel Alloc Once 8K > MALLOC 77.9M > MALLOC (admin) 48K > Memory Tag 242 12K > Memory Tag 251 8K > OpenCL 16K > STACK GUARD 56.1M > Stack 14.2M > VM_ALLOCATE 17.3M > __DATA 18.6M > __IMAGE 528K > __LINKEDIT 71.1M > __TEXT 140.3M > __UNICODE 552K > mapped file 71.0M > shared memory 4K > =========== ======= > TOTAL 498.3M > > Model: MacBookPro11,5, BootROM MBP114.0172.B10, 4 processors, Intel Core > i7, 2.5 GHz, 16 GB, SMC 2.30f2 > Graphics: AMD Radeon R9 M370X, AMD Radeon R9 M370X, PCIe, 2048 MB > Graphics: Intel Iris Pro, Intel Iris Pro, Built-In > Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, > 0x484D54343147533642465238412D50422020 > Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, > 0x484D54343147533642465238412D50422020 > AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x152), > Broadcom BCM43xx 1.0 (7.15.166.24.3) > Bluetooth: Version 4.3.6f4 17916, 3 services, 18 devices, 1 incoming > serial ports > Network Service: Thunderbolt Ethernet, Ethernet, en5 > PCI Card: Apple 57762-A0, Ethernet Controller, Thunderbolt at 195,0,0 > Serial ATA Device: APPLE SSD SM0512G, 500,28 GB > USB Device: Internal Memory Card Reader > USB Device: Porsche Mobile for Mac > USB Device: Bluetooth USB Host Controller > USB Device: Apple Internal Keyboard / Trackpad > Thunderbolt Bus: MacBook Pro, Apple Inc., 27.1 > Thunderbolt Device: Thunderbolt to Gigabit Ethernet Adapter, Apple Inc., > 1, 5.5 New description: Dear experts, \\ I am using a MB with osx 10.10.5 \\ After running a port upgrade (yesterday) I have crash when launching ChickenOfVNC. \\ Below you can find the dump I get after the crash. Is there any mismatched/missing library? \\ Thanks in advance for the assistance. \\ Regards \\ Ernesto {{{ Process: Chicken [310] Path: /Applications/MacPorts/Chicken.app/Contents/MacOS/Chicken Identifier: net.sourceforge.chicken Version: 2.2b2 (2.2b2) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: Chicken [310] User ID: 501 Date/Time: 2016-12-22 12:35:38.961 +0100 OS Version: Mac OS X 10.10.5 (14F2109) Report Version: 11 Anonymous UUID: E3896221-6692-E1BE-7C31-A9B65EC7063F Time Awake Since Boot: 66 seconds Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00007f9d00000018 VM Regions Near 0x7f9d00000018: CG backing stores 000000010ec21000-000000010eef6000 [ 2900K] rw-/rw- SM=SHM --> MALLOC_TINY 00007f9dd9400000-00007f9dd9500000 [ 1024K] rw-/rwx SM=PRV Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 net.sourceforge.chicken 0x0000000106db4cac 0x106da0000 + 85164 1 com.apple.AppKit 0x00007fff91d7f689 -[NSView _drawRect:clip:] + 4238 2 com.apple.AppKit 0x00007fff91d7dcfa -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1875 3 com.apple.AppKit 0x00007fff91d7e0fe -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2903 4 com.apple.AppKit 0x00007fff91d7e0fe -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2903 5 com.apple.AppKit 0x00007fff91d7e0fe -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2903 6 com.apple.AppKit 0x00007fff91d7e0fe -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2903 7 com.apple.AppKit 0x00007fff91d7bb96 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 913 8 com.apple.AppKit 0x00007fff91d7b2f3 -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 333 9 com.apple.AppKit 0x00007fff91d7768b -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 2761 10 com.apple.AppKit 0x00007fff91d2f1ae -[NSView displayIfNeeded] + 1876 11 com.apple.AppKit 0x00007fff91d2ea09 -[NSWindow displayIfNeeded] + 236 12 com.apple.AppKit 0x00007fff91d2e672 _handleWindowNeedsDisplayOrLayoutOrUpdateConstraints + 936 13 com.apple.AppKit 0x00007fff92464171 __83-[NSWindow _postWindowNeedsDisplayOrLayoutOrUpdateConstraintsUnlessPostingDisabled]_block_invoke1540 + 46 14 com.apple.CoreFoundation 0x00007fff8fe5b127 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 15 com.apple.CoreFoundation 0x00007fff8fe5b080 __CFRunLoopDoObservers + 368 16 com.apple.CoreFoundation 0x00007fff8fe4d188 __CFRunLoopRun + 872 17 com.apple.CoreFoundation 0x00007fff8fe4cbd8 CFRunLoopRunSpecific + 296 18 com.apple.HIToolbox 0x00007fff9071156f RunCurrentEventLoopInMode + 235 19 com.apple.HIToolbox 0x00007fff907112ea ReceiveNextEventCommon + 431 20 com.apple.HIToolbox 0x00007fff9071112b _BlockUntilNextEventMatchingListInModeWithFilter + 71 21 com.apple.AppKit 0x00007fff91d2b8ab _DPSNextEvent + 978 22 com.apple.AppKit 0x00007fff91d2ae58 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346 23 com.apple.AppKit 0x00007fff91d20af3 -[NSApplication run] + 594 24 com.apple.AppKit 0x00007fff91c9d244 NSApplicationMain + 1832 25 libdyld.dylib 0x00007fff9761d5c9 start + 1 Thread 1:: Dispatch queue: com.apple.libdispatch-manager 0 libsystem_kernel.dylib 0x00007fff8ae10232 kevent64 + 10 1 libdispatch.dylib 0x00007fff9594a26e _dispatch_mgr_thread + 52 Thread 2: 0 libsystem_kernel.dylib 0x00007fff8ae0f94a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread + 13 Thread 3: 0 libsystem_kernel.dylib 0x00007fff8ae0f94a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread + 13 Thread 4:: Dispatch queue: NSUIHeartBeatOperationQueue :: NSOperation 0x7f9dd9513dd0 (QOS: USER_INITIATED) 0 libsystem_kernel.dylib 0x00007fff8ae0f166 __psynch_mutexwait + 10 1 com.apple.Foundation 0x00007fff95c9f817 -[NSLock lock] + 145 2 com.apple.AppKit 0x00007fff91fadbcf __37-[NSUIHeartBeat updateHeartBeatState]_block_invoke142 + 60 3 com.apple.Foundation 0x00007fff95cf68b8 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 7 4 com.apple.Foundation 0x00007fff95cf6685 -[NSBlockOperation main] + 97 5 com.apple.Foundation 0x00007fff95cf5b3c -[__NSOperationInternal _start:] + 653 6 com.apple.Foundation 0x00007fff95cf5613 __NSOQSchedule_f + 184 7 libdispatch.dylib 0x00007fff95945e73 _dispatch_client_callout + 8 8 libdispatch.dylib 0x00007fff959495cd _dispatch_queue_drain + 1100 9 libdispatch.dylib 0x00007fff95949030 _dispatch_queue_invoke + 202 10 libdispatch.dylib 0x00007fff95948bef _dispatch_root_queue_drain + 463 11 libdispatch.dylib 0x00007fff95948a1c _dispatch_worker_thread3 + 91 12 libsystem_pthread.dylib 0x00007fff8efd5a9d _pthread_wqthread + 729 13 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread + 13 Thread 5: 0 libsystem_kernel.dylib 0x00007fff8ae0f94a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread + 13 Thread 6:: com.apple.CFSocket.private 0 libsystem_kernel.dylib 0x00007fff8ae0f3fa __select + 10 1 libsystem_pthread.dylib 0x00007fff8efd605a _pthread_body + 131 2 libsystem_pthread.dylib 0x00007fff8efd5fd7 _pthread_start + 176 3 libsystem_pthread.dylib 0x00007fff8efd33ed thread_start + 13 Thread 7: 0 libsystem_kernel.dylib 0x00007fff8ae0a4de mach_msg_trap + 10 1 libsystem_kernel.dylib 0x00007fff8ae0964f mach_msg + 55 2 com.apple.CoreFoundation 0x00007fff8fe4deb4 __CFRunLoopServiceMachPort + 212 3 com.apple.CoreFoundation 0x00007fff8fe4d37b __CFRunLoopRun + 1371 4 com.apple.CoreFoundation 0x00007fff8fe4cbd8 CFRunLoopRunSpecific + 296 5 com.apple.AppKit 0x00007fff91df356b _NSEventThread + 137 6 libsystem_pthread.dylib 0x00007fff8efd605a _pthread_body + 131 7 libsystem_pthread.dylib 0x00007fff8efd5fd7 _pthread_start + 176 8 libsystem_pthread.dylib 0x00007fff8efd33ed thread_start + 13 Thread 8: 0 libsystem_kernel.dylib 0x00007fff8ae0f94a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread + 13 Thread 9: 0 libsystem_kernel.dylib 0x00007fff8ae0f94a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread + 13 Thread 10: 0 libsystem_kernel.dylib 0x00007fff8ae0f94a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread + 13 Thread 11: 0 libsystem_kernel.dylib 0x00007fff8ae0f94a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread + 13 Thread 12: 0 libsystem_kernel.dylib 0x00007fff8ae0f94a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff8efd33dd start_wqthread + 13 Thread 13:: com.apple.appkit-heartbeat 0 libsystem_kernel.dylib 0x00007fff8ae0f48a __semwait_signal + 10 1 libsystem_c.dylib 0x00007fff939f6e34 usleep + 54 2 com.apple.AppKit 0x00007fff91fa1e43 -[NSUIHeartBeat _heartBeatThread:] + 2376 3 com.apple.Foundation 0x00007fff95cdae92 __NSThread__main__ + 1345 4 libsystem_pthread.dylib 0x00007fff8efd605a _pthread_body + 131 5 libsystem_pthread.dylib 0x00007fff8efd5fd7 _pthread_start + 176 6 libsystem_pthread.dylib 0x00007fff8efd33ed thread_start + 13 Thread 0 crashed with X86 Thread State (64-bit): rax: 0x00007f9d00000000 rbx: 0x0000000000000000 rcx: 0x00007f9dda009188 rdx: 0x00007fff58e5c788 rdi: 0x00007f9dd9476680 rsi: 0x00007fff96cd0fff rbp: 0x00007fff58e5c920 rsp: 0x00007fff58e5c880 r8: 0x000000000000007f r9: 0x00007f9dd9476680 r10: 0x00007f9dd97cf460 r11: 0x00007fff79a3dc60 r12: 0x00000000000000c8 r13: 0x00007f9dd95a7e20 r14: 0x0000000106de41bf r15: 0x0000000000000000 rip: 0x0000000106db4cac rfl: 0x0000000000010246 cr2: 0x00007f9d00000018 Logical CPU: 0 Error Code: 0x00000004 Trap Number: 14 Binary Images: 0x106da0000 - 0x106df4fff +net.sourceforge.chicken (2.2b2 - 2.2b2) <6D2FD694-6FB8-3F28-B85A-F38E2772A27F> /Applications/MacPorts/Chicken.app/Contents/MacOS/Chicken 0x106e16000 - 0x106e2dfff +org.andymatuschak.Sparkle (1.5 Beta 6 - 313) <9253F8F7-250B-1114-7AE9-A10A54EB2298> /Applications/MacPorts/Chicken.app/Contents/Frameworks/Sparkle.framework/Versions/A/Sparkle 0x10b285000 - 0x10b28cff7 libCGCMS.A.dylib (788.3.6) <09FA0C10-FAF1-362E-B0D7-2FC0BB19D386> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGCMS.A.dylib 0x10c098000 - 0x10c09bffb libCGXType.A.dylib (788.3.6) <2E327789-01E0-34C4-B387-A984A8DA7189> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGXType.A.dylib 0x10c5c9000 - 0x10c5f1fff libRIP.A.dylib (788.3.6) <903F88F3-DA15-3A95-AD1C-F0EA0AFC57C9> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib 0x10e3fe000 - 0x10e3fefef +cl_kernels (???) cl_kernels 0x10e40c000 - 0x10e40cff5 +cl_kernels (???) <145CB753-4111-446D-9269-DE8B92FB9A15> cl_kernels 0x10e40e000 - 0x10e4f4fef unorm8_bgra.dylib (2.4.5) <9980365E-FADF-36CB-97CC-2530BB70BA8A> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/ImageFormats/unorm8_bgra.dylib 0x7fff6d6db000 - 0x7fff6d71192f dyld (353.2.4) <708E385E- 50C6-32A3-983C-42E97BEE4346> /usr/lib/dyld 0x7fff88121000 - 0x7fff8816bfff com.apple.HIServices (1.22 - 523) <99ADA325-53C8-368E-A5FA-3F913CD2245A> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices 0x7fff881cc000 - 0x7fff881d9ff7 libbz2.1.0.dylib (36) <2DF83FBC- 5C08-39E1-94F5-C28653791B5F> /usr/lib/libbz2.1.0.dylib 0x7fff8829b000 - 0x7fff8829ffff com.apple.TCC (1.0 - 1) /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC 0x7fff882a0000 - 0x7fff882acff7 com.apple.OpenDirectory (10.10 - 187) <22FF4721-03D8-381B-AA83-2B07D690C777> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory 0x7fff882ad000 - 0x7fff882adfff com.apple.ApplicationServices (48 - 48) <5BF7910B-C328-3BF8-BA4F-CE52B574CE01> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices 0x7fff8855a000 - 0x7fff8859aff7 libGLImage.dylib (11.1.6) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib 0x7fff885ab000 - 0x7fff885b0fff com.apple.DiskArbitration (2.6 - 2.6) <0DFF4D9B-2AC3-3B82-B5C5-30F4EFBD2DB9> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration 0x7fff88684000 - 0x7fff8869eff7 com.apple.Kerberos (3.0 - 1) <7760E0C2-A222-3709-B2A6-B692D900CEB1> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos 0x7fff8869f000 - 0x7fff886aaff7 libkxld.dylib (2782.50.9) /usr/lib/system/libkxld.dylib 0x7fff886ab000 - 0x7fff88767ff7 libcrypto.0.9.7.dylib (106) /usr/lib/libcrypto.0.9.7.dylib 0x7fff88768000 - 0x7fff88775ff3 com.apple.ProtocolBuffer (1 - 228.0.1) <3429EB06-9F0E-355F-B9AB-F72879177398> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer 0x7fff88776000 - 0x7fff887a6ff3 com.apple.GSS (4.0 - 2.0) <97F2A028-44CF-3188-B863-F4EEB39CBDBD> /System/Library/Frameworks/GSS.framework/Versions/A/GSS 0x7fff887a7000 - 0x7fff887a7ff7 libunc.dylib (29) <5676F7EA-C1DF- 329F-B006-D2C3022B7D70> /usr/lib/system/libunc.dylib 0x7fff887be000 - 0x7fff887d0ff7 libsasl2.2.dylib (194.1) <35371406-75EF-304A-A073-956C40373555> /usr/lib/libsasl2.2.dylib 0x7fff8885c000 - 0x7fff88861fff libsystem_stats.dylib (163.30.2) /usr/lib/system/libsystem_stats.dylib 0x7fff88862000 - 0x7fff88862fff com.apple.Accelerate (1.10 - Accelerate 1.10) <2C8AF258-4F11-3BEC-A826-22D7199B3975> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate 0x7fff88904000 - 0x7fff8892dff3 libxslt.1.dylib (13.12) <19B2D915-DC29-3F79-9756-D7EB9051FEFF> /usr/lib/libxslt.1.dylib 0x7fff8892e000 - 0x7fff88934fff com.apple.speech.recognition.framework (5.0.9 - 5.0.9) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition 0x7fff88935000 - 0x7fff88c68ff7 libmecabra.dylib (666.7) <0ED8AE5E-7A5B-34A6-A2EE-2B852E60E1E2> /usr/lib/libmecabra.dylib 0x7fff88c69000 - 0x7fff88cb5fff com.apple.corelocation (1486.17 - 1615.24) <8825B3E2-E053-3E01-AE31-793443962D06> /System/Library/Frameworks/CoreLocation.framework/Versions/A/CoreLocation 0x7fff88cbc000 - 0x7fff88cc1ffb libheimdal-asn1.dylib (398.40.1) <7D2BE3DE-60F7-3A6E-A92E-DA0EF9D3417E> /usr/lib/libheimdal-asn1.dylib 0x7fff88cc2000 - 0x7fff88e0aff7 com.apple.WebKitLegacy (10600 - 10600.8.9) /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebKitLegacy.framework/Versions/A/WebKitLegacy 0x7fff88e0b000 - 0x7fff88e0ffff libcache.dylib (69) <45E9A2E7-99C4-36B2-BEE3-0C4E11614AD1> /usr/lib/system/libcache.dylib 0x7fff88e10000 - 0x7fff88e11ff7 com.apple.print.framework.Print (10.0 - 265) <3BC4FE7F-78A0-3E57-8F4C-520E7EFD36FA> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print 0x7fff88e15000 - 0x7fff88f39ff7 com.apple.LaunchServices (644.56 - 644.56) <20AABB1C-9319-3E4D-A024-51B0DD5FCD3B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices 0x7fff89931000 - 0x7fff8993cfff libGL.dylib (11.1.6) <38B3FF9A-5660-3080-9DB8-1CAE0E8CD739> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib 0x7fff89945000 - 0x7fff89969ff7 com.apple.Sharing (328.17 - 328.17) /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing 0x7fff8996a000 - 0x7fff8a1aeff7 com.apple.CoreGraphics (1.600.0 - 788.3.6) <3C5D7B35-2EB7-3907-A6B1-9186BDEA2CC8> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics 0x7fff8a1af000 - 0x7fff8a1b0ff3 libSystem.B.dylib (1213) <4B24B5BE-45F2-355A-9A35-D438A516D140> /usr/lib/libSystem.B.dylib 0x7fff8a1b1000 - 0x7fff8a396ff7 libicucore.A.dylib (531.50) /usr/lib/libicucore.A.dylib 0x7fff8a58a000 - 0x7fff8a592ff7 com.apple.AppleSRP (5.0 - 1) <68F0C577-ED96-34F2-B701-CE3023367D4D> /System/Library/PrivateFrameworks/AppleSRP.framework/Versions/A/AppleSRP 0x7fff8a598000 - 0x7fff8a637e27 com.apple.AppleJPEG (1.0 - 1) <6627DDD9-A8FE-3968-B23A-B6A29AA3919A> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG 0x7fff8a638000 - 0x7fff8a6c9ff7 libCoreStorage.dylib (471.30.1) <9D95399F-1AC5-325F-8337-6E13AD99E44B> /usr/lib/libCoreStorage.dylib 0x7fff8a759000 - 0x7fff8a7c7ff3 com.apple.Heimdal (4.0 - 2.0) <8D1667CF-D454-3E07-A58E-E15591B5A95E> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal 0x7fff8a7c8000 - 0x7fff8abf8fff com.apple.vision.FaceCore (3.1.6 - 3.1.6) /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore 0x7fff8abfe000 - 0x7fff8ac87ff7 com.apple.CoreSymbolication (3.1 - 57020.2) /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication 0x7fff8ac88000 - 0x7fff8ada1ffb com.apple.CoreText (454.11 - 454.11) <7E5228C8-8657-3B6C-B3A4-98B79A3041EA> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText 0x7fff8adf9000 - 0x7fff8ae16fff libsystem_kernel.dylib (2782.50.9) /usr/lib/system/libsystem_kernel.dylib 0x7fff8b0f7000 - 0x7fff8b175fff com.apple.CoreServices.OSServices (640.4 - 640.4) <9D175CD9-B27F-3529-8269-66D8AA83582E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices 0x7fff8b179000 - 0x7fff8b1e5ff3 com.apple.MMCS (1.3 - 327.5) /System/Library/PrivateFrameworks/MMCS.framework/Versions/A/MMCS 0x7fff8b279000 - 0x7fff8b281fff libsystem_dnssd.dylib (576.50.2) <9EC5AF92-D0D2-3BDE-92B6-D3730D3865C8> /usr/lib/system/libsystem_dnssd.dylib 0x7fff8b34b000 - 0x7fff8b3c3ff7 com.apple.SystemConfiguration (1.14.4 - 1.14) <3DFFD7F7-BD23-3F4C-A209-C4A0D99F6573> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration 0x7fff8b3dc000 - 0x7fff8b4cdfff libJP2.dylib (1247) /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib 0x7fff8b4dd000 - 0x7fff8b598ff7 com.apple.DiscRecording (9.0 - 9000.4.2) <4655B4B8-523D-3AE6-92A0-8486A2258B3B> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording 0x7fff8b599000 - 0x7fff8b5d4fff com.apple.QD (301 - 301) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD 0x7fff8b627000 - 0x7fff8b693fff com.apple.framework.CoreWLAN (5.0 - 500.35.2) <03697149-1CDD-32FF-B564-1C1EF5E9E5C3> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN 0x7fff8b694000 - 0x7fff8b6affff com.apple.AppleVPAFramework (1.4.5 - 1.4.5) /System/Library/PrivateFrameworks/AppleVPA.framework/Versions/A/AppleVPA 0x7fff8b6f4000 - 0x7fff8b6ffff7 com.apple.CrashReporterSupport (10.10 - 631) /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport 0x7fff8b700000 - 0x7fff8b730fff libsystem_m.dylib (3086.1) <1E12AB45-6D96-36D0-A226-F24D9FB0D9D6> /usr/lib/system/libsystem_m.dylib 0x7fff8b7e9000 - 0x7fff8b7ecfff com.apple.xpc.ServiceManagement (1.0 - 1) /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement 0x7fff8b7ed000 - 0x7fff8b88ffff com.apple.Bluetooth (4.3.6 - 4.3.6f4) /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth 0x7fff8bbbd000 - 0x7fff8bbd4ff7 libLinearAlgebra.dylib (1128) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib 0x7fff8bbd5000 - 0x7fff8bc02fff com.apple.CoreVideo (1.8 - 145.1) <18DB07E0-B927-3260-A234-636F298D1917> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo 0x7fff8bc2e000 - 0x7fff8bc52fef libJPEG.dylib (1247) <78AA0479 -176D-3C69-ADFB-4609A4A676FF> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib 0x7fff8bc57000 - 0x7fff8bc57ff7 libkeymgr.dylib (28) <77845842-DE70-3CC5-BD01-C3D14227CED5> /usr/lib/system/libkeymgr.dylib 0x7fff8bc81000 - 0x7fff8bca9fff libsystem_info.dylib (459.40.1) <2E16C4B3-A327-3957-9C41-143911979A1E> /usr/lib/system/libsystem_info.dylib 0x7fff8bcaa000 - 0x7fff8bcb2ffb libcopyfile.dylib (118.1.2) <0C68D3A6-ACDD-3EF3-991A-CC82C32AB836> /usr/lib/system/libcopyfile.dylib 0x7fff8be1e000 - 0x7fff8be20fff libsystem_configuration.dylib (699.40.2) <56F94DCE-DBDE-3615-8F07-DE6270D9F8BE> /usr/lib/system/libsystem_configuration.dylib 0x7fff8be30000 - 0x7fff8be38fff libsystem_platform.dylib (63) <64E34079-D712-3D66-9CE2-418624A5C040> /usr/lib/system/libsystem_platform.dylib 0x7fff8be39000 - 0x7fff8be3cfff com.apple.IOSurface (97.4 - 97.4) /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface 0x7fff8be3d000 - 0x7fff8ce00ff3 com.apple.WebCore (10600 - 10600.8.9) /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/WebCore 0x7fff8ce01000 - 0x7fff8ce68ff7 com.apple.framework.CoreWiFi (3.0 - 300.4) <19269C1D-EB29-384A-83F3-7DDDEB7D9DAD> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi 0x7fff8ce69000 - 0x7fff8cec8fff com.apple.AE (681.5 - 681.7) <2BF39455-1CDD-392C-824A-9972C6B1FB57> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE 0x7fff8cec9000 - 0x7fff8cee4ff7 libCRFSuite.dylib (34) /usr/lib/libCRFSuite.dylib 0x7fff8d14e000 - 0x7fff8d2dcfff libBLAS.dylib (1128) <497912C1-A98E-3281-BED7-E9C751552F61> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib 0x7fff8d2dd000 - 0x7fff8d2e5fe7 libcldcpuengine.dylib (2.4.5) /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib 0x7fff8d2f1000 - 0x7fff8d2f3fff com.apple.loginsupport (1.0 - 1) /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport 0x7fff8daa9000 - 0x7fff8db9dff7 libFontParser.dylib (134.10) <6CF434A2-91CA-3477-BDE2-124508EDA05D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib 0x7fff8dbc5000 - 0x7fff8dfd2ff7 libLAPACK.dylib (1128) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib 0x7fff8e054000 - 0x7fff8e087fff com.apple.MediaKit (16 - 757.2) <2912E5C2-085F-3FE2-8531-23B6E894B0F0> /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit 0x7fff8e12d000 - 0x7fff8e146ff7 com.apple.CFOpenDirectory (10.10 - 187) /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory 0x7fff8e297000 - 0x7fff8e298ff7 libsystem_blocks.dylib (65) <9615D10A-FCA7-3BE4-AA1A-1B195DACE1A1> /usr/lib/system/libsystem_blocks.dylib 0x7fff8e2e8000 - 0x7fff8e34fffb com.apple.datadetectorscore (6.0 - 396.1.2) /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore 0x7fff8e350000 - 0x7fff8e350fff com.apple.audio.units.AudioUnit (1.12 - 1.12) /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit 0x7fff8e351000 - 0x7fff8e356ff7 libunwind.dylib (35.3) /usr/lib/system/libunwind.dylib 0x7fff8e357000 - 0x7fff8e378fff com.apple.framework.Apple80211 (10.3 - 1030.71.6) /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211 0x7fff8e379000 - 0x7fff8e37bfff libsystem_sandbox.dylib (358.20.5) <3F5E973F-C702-31AC-97BC-05F5C195683C> /usr/lib/system/libsystem_sandbox.dylib 0x7fff8e37c000 - 0x7fff8e38eff7 com.apple.ImageCapture (9.0 - 9.0) <7FB65DD4-56B5-35C4-862C-7A2DED991D1F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture 0x7fff8e4aa000 - 0x7fff8e4c4ff7 liblzma.5.dylib (7) <1D03E875-A7C0-3028-814C-3C27F7B7C079> /usr/lib/liblzma.5.dylib 0x7fff8e4f5000 - 0x7fff8e630fff com.apple.ImageIO.framework (3.3.0 - 1247) /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO 0x7fff8e631000 - 0x7fff8e640fff com.apple.LangAnalysis (1.7.0 - 1.7.0) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis 0x7fff8efac000 - 0x7fff8efd1fff libPng.dylib (1247) <1E8B06AA- 1DC5-3845-88D9-B2F8E6E1E540> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib 0x7fff8efd2000 - 0x7fff8efdbfff libsystem_pthread.dylib (105.40.1) /usr/lib/system/libsystem_pthread.dylib 0x7fff8efdc000 - 0x7fff8efecff7 libbsm.0.dylib (34) /usr/lib/libbsm.0.dylib 0x7fff8f0b1000 - 0x7fff8f327fff com.apple.security (7.0 - 57031.40.8) /System/Library/Frameworks/Security.framework/Versions/A/Security 0x7fff8f328000 - 0x7fff8f32bfff com.apple.help (1.3.3 - 46) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help 0x7fff8f387000 - 0x7fff8f89cfff com.apple.JavaScriptCore (10600 - 10600.8.7.1) <4C48FD32-ACA3-358F-95D9-05DBB56A1DED> /System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore 0x7fff8f89d000 - 0x7fff8f8f1fff libc++.1.dylib (120) <1B9530FD- 989B-3174-BB1C-BDC159501710> /usr/lib/libc++.1.dylib 0x7fff8f8f2000 - 0x7fff8f9a1fe7 libvMisc.dylib (516) <6739E390-46E7-3BFA-9B69-B278562326E6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib 0x7fff8f9a2000 - 0x7fff8f9edff7 com.apple.CloudDocs (1.0 - 321.10) /System/Library/PrivateFrameworks/CloudDocs.framework/Versions/A/CloudDocs 0x7fff8f9ee000 - 0x7fff8fa3dff7 libcurl.4.dylib (83.40.2) /usr/lib/libcurl.4.dylib 0x7fff8fd2b000 - 0x7fff8fd9cffb com.apple.ApplicationServices.ATS (360 - 375.4) <888FE0B1-835C-30B1-80AD-5066CADB0364> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS 0x7fff8fddb000 - 0x7fff90173ff7 com.apple.CoreFoundation (6.9 - 1153.18) <5C0892B8-9691-341F-9279-CA3A74D59AA0> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 0x7fff90174000 - 0x7fff90186ff7 com.apple.CoreDuetDaemonProtocol (1.0 - 1) /System/Library/PrivateFrameworks/CoreDuetDaemonProtocol.framework/Versions/A/CoreDuetDaemonProtocol 0x7fff9018a000 - 0x7fff90409ff7 com.apple.CoreData (111 - 526.3) <5A27E0D8-5E5A-335B-B3F6-2601C7B976FA> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData 0x7fff9040a000 - 0x7fff906cdff7 com.apple.WebKit (10600 - 10600.8.9) <8EE5A9F9-DE98-3202-92C0-23F6E6E5E274> /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit 0x7fff906ce000 - 0x7fff906dbfff libxar.1.dylib (255) <7CD69BB5-97BA-3858-8A8B-2F33F129E6E7> /usr/lib/libxar.1.dylib 0x7fff906dc000 - 0x7fff906deff7 libsystem_coreservices.dylib (9) <41B7C578-5A53-31C8-A96F-C73E030B0938> /usr/lib/system/libsystem_coreservices.dylib 0x7fff906df000 - 0x7fff909e4ff3 com.apple.HIToolbox (2.1.1 - 758.7) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox 0x7fff909ee000 - 0x7fff90a5dfff com.apple.SearchKit (1.4.0 - 1.4.0) <80883BD1-C9BA-3794-A20E-476F94DD89A9> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit 0x7fff90a5e000 - 0x7fff90b50ff7 libiconv.2.dylib (42) <2A06D02F- 8B76-3864-8D96-64EF5B40BC6C> /usr/lib/libiconv.2.dylib 0x7fff90b92000 - 0x7fff90bacff7 libextension.dylib (55.2) <3BB019CA-199A-36AC-AA22-14B562138545> /usr/lib/libextension.dylib 0x7fff90bad000 - 0x7fff90bb3ff7 libsystem_networkextension.dylib (167.40.3) /usr/lib/system/libsystem_networkextension.dylib 0x7fff90bb4000 - 0x7fff90c49ff7 com.apple.ColorSync (4.9.0 - 4.9.0) <9150C2B7-2E6E-3509-96EA-7B3F959F049E> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync 0x7fff90cde000 - 0x7fff90fadff3 com.apple.CoreImage (10.3.5) <0224F5A6-636A-374B-B46C-13E066596725> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/CoreImage.framework/Versions/A/CoreImage 0x7fff914f7000 - 0x7fff916a7ff3 com.apple.QuartzCore (1.10 - 361.19) /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore 0x7fff916cb000 - 0x7fff91761ff7 com.apple.cloudkit.CloudKit (283.67.4 - 283.67.4) /System/Library/Frameworks/CloudKit.framework/Versions/A/CloudKit 0x7fff91793000 - 0x7fff9179cff7 libsystem_notify.dylib (133.1.1) <61147800-F320-3DAA-850C-BADF33855F29> /usr/lib/system/libsystem_notify.dylib 0x7fff918d2000 - 0x7fff91918ff7 libFontRegistry.dylib (134.1) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib 0x7fff91919000 - 0x7fff91926ff7 com.apple.SpeechRecognitionCore (2.1.2 - 2.1.2) <551322E2-C1E4-3378-A218-F362985E3E3C> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore 0x7fff91927000 - 0x7fff91ba5ff7 com.apple.RawCamera.bundle (6.04.1 - 798) <7988A25F-2A69-311E-929E-B70D164739F4> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera 0x7fff91ba6000 - 0x7fff91bc5fff com.apple.CoreDuet (1.0 - 1) <36AA9FD5-2685-314D-B364-3FA4688D86BD> /System/Library/PrivateFrameworks/CoreDuet.framework/Versions/A/CoreDuet 0x7fff91bc6000 - 0x7fff91c20ff7 com.apple.LanguageModeling (1.0 - 1) /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling 0x7fff91c4f000 - 0x7fff91c60ff7 libz.1.dylib (55) <88C7C7DE-04B8 -316F-8B74-ACD9F3DE1AA1> /usr/lib/libz.1.dylib 0x7fff91c61000 - 0x7fff91c99fff com.apple.RemoteViewServices (2.0 - 99) /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices 0x7fff91c9a000 - 0x7fff9281bff7 com.apple.AppKit (6.9 - 1348.17) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit 0x7fff9281c000 - 0x7fff9294cfff com.apple.UIFoundation (1.0 - 1) <466BDFA8-0B9F-3AB0-989D-F9779422926A> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation 0x7fff9294d000 - 0x7fff92966ff3 com.apple.openscripting (1.6.4 - 162.2) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting 0x7fff92967000 - 0x7fff92998ff7 com.apple.ProtectedCloudStorage (1.0 - 1) <9D76F2E0-C28A-3DBC-A91F-E87888D46BF0> /System/Library/PrivateFrameworks/ProtectedCloudStorage.framework/Versions/A/ProtectedCloudStorage 0x7fff9323e000 - 0x7fff93269fff libc++abi.dylib (125) <88A22A0F- 87C6-3002-BFBA-AC0F2808B8B9> /usr/lib/libc++abi.dylib 0x7fff9326a000 - 0x7fff9326afff com.apple.Carbon (154 - 157) <9BF51672-1684-3FDE-A561-FC59A2864EF8> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon 0x7fff93278000 - 0x7fff93281fff libGFXShared.dylib (11.1.6) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib 0x7fff93282000 - 0x7fff93342ff7 com.apple.backup.framework (1.6.5 - 1.6.5) <86396038-33EA-3046-9F70-093A3D6407D4> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup 0x7fff93347000 - 0x7fff93358ff3 libsystem_coretls.dylib (35.40.1) <155DA0A9-2046-332E-BFA3-D7974A51F731> /usr/lib/system/libsystem_coretls.dylib 0x7fff93359000 - 0x7fff93640ffb com.apple.CoreServices.CarbonCore (1108.6 - 1108.6) <8953580E-7857-33B2-AA64-98296830D3A8> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore 0x7fff936bf000 - 0x7fff93753fff com.apple.ink.framework (10.9 - 213) <8E029630-1530-3734-A446-13353F0E7AC5> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink 0x7fff93855000 - 0x7fff938c9ffb com.apple.securityfoundation (6.0 - 55126) <344401F5-4016-3AEB-BFDC-CE8E5546D39F> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation 0x7fff938ca000 - 0x7fff93904ffb com.apple.DebugSymbols (115 - 115) <6F03761D-7C3A-3C80-8031-AA1C1AD7C706> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols 0x7fff93905000 - 0x7fff93960fe7 libTIFF.dylib (1247) <43CB4BDE- 84FD-3CCE-96C0-FB33BA2753BD> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib 0x7fff93961000 - 0x7fff93977ff7 libsystem_asl.dylib (267) /usr/lib/system/libsystem_asl.dylib 0x7fff93978000 - 0x7fff93a04fef libsystem_c.dylib (1044.40.3) <2E673D96-E334-37D2-833A-E57383BBA377> /usr/lib/system/libsystem_c.dylib 0x7fff93a1b000 - 0x7fff93a68ff7 com.apple.print.framework.PrintCore (10.3 - 451.1) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore 0x7fff93ebf000 - 0x7fff93f5dfff com.apple.Metadata (10.7.0 - 917.36) <00C4CB5D-E723-3612-84E0-439098392CDD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata 0x7fff93f5e000 - 0x7fff93fd0fff com.apple.framework.IOKit (2.0.2 - 1050.20.2) <09C0518C-90DF-3FC3-96D6-34D35F72C8EF> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit 0x7fff93fd1000 - 0x7fff93fedff7 libsystem_malloc.dylib (53.30.1) /usr/lib/system/libsystem_malloc.dylib 0x7fff93ffe000 - 0x7fff9403ffff libGLU.dylib (11.1.6) <4BC6579D- A6D0-3A19-880E-E29FAEA698E7> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib 0x7fff94040000 - 0x7fff940c4fff com.apple.PerformanceAnalysis (1.0 - 1) <095E6B1C-DC20-38DC-8931-16041B0489C7> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis 0x7fff94130000 - 0x7fff94135ff7 libmacho.dylib (862) <126CA2ED- DE91-308F-8881-B9DAEC3C63B6> /usr/lib/system/libmacho.dylib 0x7fff9413a000 - 0x7fff94171ffb com.apple.LDAPFramework (2.4.28 - 194.5) /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP 0x7fff94172000 - 0x7fff94183fff libcmph.dylib (1) <46EC3997-DB5E- 38AE-BBBB-A035A54AD3C0> /usr/lib/libcmph.dylib 0x7fff941da000 - 0x7fff9420cff3 com.apple.frameworks.CoreDaemon (1.3 - 1.3) /System/Library/PrivateFrameworks/CoreDaemon.framework/Versions/B/CoreDaemon 0x7fff9439b000 - 0x7fff943affeb libCGInterfaces.dylib (294.1) <390D4B3F-B738-3D33-BEDB-07E3F0F6B42C> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib 0x7fff943b5000 - 0x7fff94401ff7 libcups.2.dylib (408.2) /usr/lib/libcups.2.dylib 0x7fff9444f000 - 0x7fff9446cffb libresolv.9.dylib (57) <26B38E61 -298A-3C3A-82C1-3B5E98AD5E29> /usr/lib/libresolv.9.dylib 0x7fff945fd000 - 0x7fff9470fff7 libvDSP.dylib (516) <151B3CCB- 77D3-3715-A3D0-7C74CD5C7FFC> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib 0x7fff94795000 - 0x7fff948dbfef libsqlite3.dylib (168.2) <53F6A294-15D7-3804-9ABF-47D35E15CDFB> /usr/lib/libsqlite3.dylib 0x7fff948dc000 - 0x7fff94907ff7 com.apple.DictionaryServices (1.2 - 229.1) <62EC3E1B-5A28-3252-90FF-C2E9999C2A2A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices 0x7fff94908000 - 0x7fff94914fff com.apple.speech.synthesis.framework (5.3.11 - 5.3.11) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis 0x7fff94d01000 - 0x7fff94d27fff com.apple.ChunkingLibrary (2.1 - 163.6) <29D4CB95-42EF-34C6-8182-BDB6F7BB1E79> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary 0x7fff94d28000 - 0x7fff95043fcf com.apple.vImage (8.0 - 8.0) <1183FE6A-FDB6-3B3B-928D-50C7909F2308> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage 0x7fff95049000 - 0x7fff95074ffb libarchive.2.dylib (30.50.1) /usr/lib/libarchive.2.dylib 0x7fff950b0000 - 0x7fff950b0fff libOpenScriptingUtil.dylib (162.2) /usr/lib/libOpenScriptingUtil.dylib 0x7fff951b1000 - 0x7fff951b3fff libquarantine.dylib (76.20.1) <7AF90041-2768-378A-925A-D83161863642> /usr/lib/system/libquarantine.dylib 0x7fff951b4000 - 0x7fff951b6fff libRadiance.dylib (1247) <0028A2E3-7928-3479-9BF7-CB64234F85AF> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib 0x7fff951ba000 - 0x7fff951bcfff libCVMSPluginSupport.dylib (11.1.6) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib 0x7fff95243000 - 0x7fff95244fff libsystem_secinit.dylib (18) <581DAD0F-6B63-3A48-B63B-917AF799ABAA> /usr/lib/system/libsystem_secinit.dylib 0x7fff95245000 - 0x7fff95246ffb libremovefile.dylib (35) <3485B5F4-6CE8-3C62-8DFD-8736ED6E8531> /usr/lib/system/libremovefile.dylib 0x7fff952f2000 - 0x7fff9531afff libxpc.dylib (559.40.1) <5C829202-962E-3744-8B50-00D38CC88E84> /usr/lib/system/libxpc.dylib 0x7fff9531b000 - 0x7fff953fffff libcrypto.0.9.8.dylib (52.40.1) /usr/lib/libcrypto.0.9.8.dylib 0x7fff95400000 - 0x7fff95401fff libDiagnosticMessagesClient.dylib (100) <2EE8E436-5CDC-34C5-9959-5BA218D507FB> /usr/lib/libDiagnosticMessagesClient.dylib 0x7fff95402000 - 0x7fff954f4ff7 libxml2.2.dylib (26.12) <769FD755 -D24A-3A7C-ABEE-9A82BB1196D0> /usr/lib/libxml2.2.dylib 0x7fff954f5000 - 0x7fff954fcff7 libcompiler_rt.dylib (35) /usr/lib/system/libcompiler_rt.dylib 0x7fff954fd000 - 0x7fff95501ff7 libGIF.dylib (1247) <5EA6D19A-9922-39F6-82DB-DE7A5B8860CF> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib 0x7fff95817000 - 0x7fff95817fff com.apple.Cocoa (6.8 - 21) /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa 0x7fff95821000 - 0x7fff95930ff3 com.apple.desktopservices (1.9.3 - 1.9.3) /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv 0x7fff95944000 - 0x7fff9596eff7 libdispatch.dylib (442.50.1) /usr/lib/system/libdispatch.dylib 0x7fff9596f000 - 0x7fff95b7fff7 com.apple.CFNetwork (720.5.7 - 720.5.7) /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork 0x7fff95c13000 - 0x7fff95c8cfe7 libcorecrypto.dylib (233.30.1) <5779FFA0-4D9A-3AD4-B7F2-618227621DC8> /usr/lib/system/libcorecrypto.dylib 0x7fff95c8d000 - 0x7fff95c8ffff com.apple.EFILogin (2.0 - 2) <3BA837D8-94F5-3240-9CF7-E40DC2808446> /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/EFILogin 0x7fff95c90000 - 0x7fff95c9bfff libcommonCrypto.dylib (60061.30.1) /usr/lib/system/libcommonCrypto.dylib 0x7fff95c9c000 - 0x7fff95fcdfff com.apple.Foundation (6.9 - 1154) <49EE64E1-9F53-35D1-A481-2EFE2789B254> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation 0x7fff9607b000 - 0x7fff96095ff3 com.apple.Ubiquity (1.3 - 313) /System/Library/PrivateFrameworks/Ubiquity.framework/Versions/A/Ubiquity 0x7fff9618e000 - 0x7fff96264ff3 com.apple.DiskImagesFramework (10.10.5 - 398) <37291661-BCB2-3F95-B446-5E5DB1D1E472> /System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/DiskImages 0x7fff96265000 - 0x7fff96266fff com.apple.TrustEvaluationAgent (2.0 - 25) <2D61A2C3-C83E-3A3F-8EC1-736DBEC250AB> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent 0x7fff96274000 - 0x7fff96274fff com.apple.Accelerate.vecLib (3.10 - vecLib 3.10) <9D749502-A228-3BF1-B52F-A182DEEB2C4D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib 0x7fff965a1000 - 0x7fff965a9ff7 com.apple.icloud.FindMyDevice (1.0 - 1) <9CE67F85-2BA8-3093-97BA-07BF5C04A5D6> /System/Library/PrivateFrameworks/FindMyDevice.framework/Versions/A/FindMyDevice 0x7fff965aa000 - 0x7fff965b8ff7 com.apple.opengl (11.1.6 - 11.1.6) /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL 0x7fff965d2000 - 0x7fff967cc46f libobjc.A.dylib (647) <759E155D- BC42-3D4E-869B-6F57D477177C> /usr/lib/libobjc.A.dylib 0x7fff967cd000 - 0x7fff967d6ff3 com.apple.CommonAuth (4.0 - 2.0) <9A484EE6-0003-3AB1-AE4F-AA543BBBF53F> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth 0x7fff967d7000 - 0x7fff967e1ff7 com.apple.NetAuth (5.2 - 5.2) <2BBD749A-8E18-35B8-8E48-A90347C1CCA7> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth 0x7fff967e2000 - 0x7fff967e6fff libpam.2.dylib (20) /usr/lib/libpam.2.dylib 0x7fff96cd8000 - 0x7fff96d10fff libsystem_network.dylib (412.20.3) <6105C134-6722-3C0A-A4CE-5E1261E2E1CC> /usr/lib/system/libsystem_network.dylib 0x7fff96d11000 - 0x7fff96e39ff7 com.apple.coreui (2.1 - 308.6) <9E0E9C6A-68F5-34C1-A17C-96226D401D4D> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI 0x7fff96e3a000 - 0x7fff96e5afff com.apple.IconServices (47.1 - 47.1) /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices 0x7fff96ee0000 - 0x7fff96f2fff7 com.apple.opencl (2.4.2 - 2.4.2) <590504FA-E5D2-37C2-91A7-09F5F039F971> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL 0x7fff96f30000 - 0x7fff96f4cfff com.apple.GenerationalStorage (2.0 - 209.11) <9FF8DD11-25FB-3047-A5BF-9415339B3EEC> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage 0x7fff96f4d000 - 0x7fff9724fffb com.apple.GeoServices (1.0 - 1077.0.18) <2BBF8B44-DD46-3432-8C84-6D6AA004C233> /System/Library/PrivateFrameworks/GeoServices.framework/Versions/A/GeoServices 0x7fff972db000 - 0x7fff972e2fff com.apple.NetFS (6.0 - 4.0) /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS 0x7fff9737d000 - 0x7fff97385ff3 com.apple.CoreServices.FSEvents (1210.20.1 - 1210.20.1) <84F79D3E-7B5E-3C93-8479-35794A3F125E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents 0x7fff97387000 - 0x7fff97387ff7 liblaunch.dylib (559.40.1) <4F81CA3A-D2CE-3030-A89D-42F3DAD7BA8F> /usr/lib/system/liblaunch.dylib 0x7fff97472000 - 0x7fff97476fff com.apple.CommonPanels (1.2.6 - 96) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels 0x7fff97477000 - 0x7fff974c8fff com.apple.audio.CoreAudio (4.3.0 - 4.3.0) <8E6AE326-9F3E-3182-BD9E-FDF561211E2E> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio 0x7fff974c9000 - 0x7fff974dcff7 com.apple.CoreBluetooth (1.0 - 1) <8D7BA9BA-EB36-307A-9119-0B3D9732C953> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth 0x7fff974e5000 - 0x7fff9752bff7 libauto.dylib (186) /usr/lib/libauto.dylib 0x7fff9752c000 - 0x7fff9752eff7 libutil.dylib (38) <471AD65E- B86E-3C4A-8ABD-B8665A2BCE3F> /usr/lib/libutil.dylib 0x7fff9752f000 - 0x7fff97530fff liblangid.dylib (117) /usr/lib/liblangid.dylib 0x7fff97549000 - 0x7fff97549fff com.apple.CoreServices (62 - 62) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices 0x7fff9756e000 - 0x7fff97574fff libsystem_trace.dylib (72.20.1) <840F5301-B55A-3078-90B9-FEFFD6CD741A> /usr/lib/system/libsystem_trace.dylib 0x7fff975d9000 - 0x7fff975e4ff7 libcsfde.dylib (471.30.1) /usr/lib/libcsfde.dylib 0x7fff975e5000 - 0x7fff975e9fff libCoreVMClient.dylib (79.1) <201EF6DF-5074-3CB7-A361-398CF957A264> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib 0x7fff975ea000 - 0x7fff97619ff7 com.apple.CoreServicesInternal (221.7.2 - 221.7.2) /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal 0x7fff9761a000 - 0x7fff9761dff7 libdyld.dylib (353.2.4) <224F35C5-6E35-3EC4-A97C-80949CE444E7> /usr/lib/system/libdyld.dylib 0x7fff9763d000 - 0x7fff9763fff7 com.apple.securityhi (9.0 - 55006) <15D38919-9697-3E3A-BCB9-4E3271BC2C7E> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI 0x7fff978e5000 - 0x7fff97905ff7 com.apple.MultitouchSupport.framework (264.6 - 264.6) <1539F1F6-6334-37F3-9C52-02EFFBF4835D> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport 0x7fff97906000 - 0x7fff97a6dffb com.apple.audio.toolbox.AudioToolbox (1.12 - 1.12) <5678FC94-456A-3F5F- BA9A-10EB6E462997> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox 0x7fff97a6e000 - 0x7fff97a70fff com.apple.CoreDuetDebugLogging (1.0 - 1) <9A6E5710-EA99-366E-BF40-9A65EC1B46A1> /System/Library/PrivateFrameworks/CoreDuetDebugLogging.framework/Versions/A/CoreDuetDebugLogging 0x7fff97a8b000 - 0x7fff97ac6fff com.apple.Symbolication (1.4 - 56045) /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication External Modification Summary: Calls made by other processes targeting this process: task_for_pid: 1 thread_create: 0 thread_set_state: 0 Calls made by this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by all processes on this machine: task_for_pid: 297 thread_create: 0 thread_set_state: 0 VM Region Summary: ReadOnly portion of Libraries: Total=211.4M resident=108.2M(51%) swapped_out_or_unallocated=103.2M(49%) Writable regions: Total=139.9M written=7136K(5%) resident=22.7M(16%) swapped_out=0K(0%) unallocated=117.2M(84%) REGION TYPE VIRTUAL =========== ======= Activity Tracing 2048K CG backing stores 7792K CG image 796K CG shared images 368K CoreAnimation 3200K CoreImage 16K CoreUI image data 440K Dispatch continuations 16.0M Foundation 4K Image IO 464K Kernel Alloc Once 8K MALLOC 77.9M MALLOC (admin) 48K Memory Tag 242 12K Memory Tag 251 8K OpenCL 16K STACK GUARD 56.1M Stack 14.2M VM_ALLOCATE 17.3M __DATA 18.6M __IMAGE 528K __LINKEDIT 71.1M __TEXT 140.3M __UNICODE 552K mapped file 71.0M shared memory 4K =========== ======= TOTAL 498.3M Model: MacBookPro11,5, BootROM MBP114.0172.B10, 4 processors, Intel Core i7, 2.5 GHz, 16 GB, SMC 2.30f2 Graphics: AMD Radeon R9 M370X, AMD Radeon R9 M370X, PCIe, 2048 MB Graphics: Intel Iris Pro, Intel Iris Pro, Built-In Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533642465238412D50422020 Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533642465238412D50422020 AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x152), Broadcom BCM43xx 1.0 (7.15.166.24.3) Bluetooth: Version 4.3.6f4 17916, 3 services, 18 devices, 1 incoming serial ports Network Service: Thunderbolt Ethernet, Ethernet, en5 PCI Card: Apple 57762-A0, Ethernet Controller, Thunderbolt at 195,0,0 Serial ATA Device: APPLE SSD SM0512G, 500,28 GB USB Device: Internal Memory Card Reader USB Device: Porsche Mobile for Mac USB Device: Bluetooth USB Host Controller USB Device: Apple Internal Keyboard / Trackpad Thunderbolt Bus: MacBook Pro, Apple Inc., 27.1 Thunderbolt Device: Thunderbolt to Gigabit Ethernet Adapter, Apple Inc., 1, 5.5 }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 12:08:32 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 12:08:32 -0000 Subject: [MacPorts] #53135: cotvnc @2.2b2_0: Chicken of VNC crash after ports upgrade (was: Chicken of VNC crash after ports upgrade) In-Reply-To: <045.905c50621d79f659268e0b5d7b8c5b13@macports.org> References: <045.905c50621d79f659268e0b5d7b8c5b13@macports.org> Message-ID: <060.26b64c8f848cc96f1963d7e7e5930ae3@macports.org> #53135: cotvnc @2.2b2_0: Chicken of VNC crash after ports upgrade -----------------------+----------------- Reporter: emiglior | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cotvnc | -----------------------+----------------- Changes (by ryandesign): * port: cotvnc @2.2b2_0 => cotvnc Old description: > Dear experts, > I am using a MB with osx 10.10.5 > After running a port upgrade (yesterday) I have crash when launching > ChickenOfVNC. > I attach the dump I get after the crash. Is there any mismatched/missing > library? > Thanks in advance for the assistance. > Regards > Ernesto New description: Dear experts, \\ I am using a MB with osx 10.10.5 \\ After running a port upgrade (yesterday) I have crash when launching ChickenOfVNC. \\ I attach the dump I get after the crash. Is there any mismatched/missing library? \\ Thanks in advance for the assistance. \\ Regards \\ Ernesto -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 12:09:42 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 12:09:42 -0000 Subject: [MacPorts] #53133: sbt @0.13.11: upgrade to 0.13.13 In-Reply-To: <048.c986743b9245fa762ef56417535fc28b@macports.org> References: <048.c986743b9245fa762ef56417535fc28b@macports.org> Message-ID: <063.bf5259365d338cd33082ca272dc15723@macports.org> #53133: sbt @0.13.11: upgrade to 0.13.13 --------------------------+---------------------- Reporter: nhojpatrick | Owner: blair Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: sbt | --------------------------+---------------------- Changes (by ryandesign): * cc: blair@… (removed) * owner: => blair * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 12:54:16 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 12:54:16 -0000 Subject: [MacPorts] #52992: fluid-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.77f83535e591c463efa2958e24db20d2@macports.org> #52992: fluid-soundfont: add new sound fonts -------------------------------------------------+------------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: fluid-soundfont-gm_gs fluid- | soundfont-gu_gs | -------------------------------------------------+------------------------- Changes (by mojca): * status: new => closed * resolution: => fixed Comment: In [changeset:"576258835b3977f7573c20a84b2a746e63354b06/macports-ports" 57625883/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="576258835b3977f7573c20a84b2a746e63354b06" fluid-soundfont, generaluser-soundfont: new ports Closes: https://trac.macports.org/ticket/52992 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 12:56:41 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 12:56:41 -0000 Subject: [MacPorts] #52992: fluid-soundfont, generaluser-soundfont: add new sound fonts (was: fluid-soundfont: add new sound fonts) In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.f5fe74e7e61c9a42c3bfc66ac68fe41e@macports.org> #52992: fluid-soundfont, generaluser-soundfont: add new sound fonts ----------------------------------------------------+-------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: fluid-soundfont generaluser-soundfont | ----------------------------------------------------+-------------------- Changes (by mojca): * port: fluid-soundfont-gm_gs fluid-soundfont-gu_gs => fluid-soundfont generaluser-soundfont Old description: > I'm opening a new ticket for discussing new packages for fluidsynth sound > fonts. > > This was originally mentioned in #51842 as a potential dependency for > TiMidity++. > > Here's the code contributed by René: > * > [https://github.com/RJVB/macstrop/tree/2fb8aab3edbf8c0bd00604b87efa351c761d0cc5/multimedia/fluidsynth > multimedia/fluidsynth] (from > [https://github.com/RJVB/macstrop/tree/master/multimedia/fluidsynth > master]) New description: I'm opening a new ticket for discussing new packages for fluidsynth and GeneralUser sound fonts. This was originally mentioned in #51842 as a potential dependency for TiMidity++. Here's the code contributed by René: * [https://github.com/RJVB/macstrop/tree/2fb8aab3edbf8c0bd00604b87efa351c761d0cc5/multimedia/fluidsynth multimedia/fluidsynth] (from [https://github.com/RJVB/macstrop/tree/master/multimedia/fluidsynth master]) -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 14:34:41 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 14:34:41 -0000 Subject: [MacPorts] #53107: py-pygrib @2.0.2 update In-Reply-To: <044.366915d58c1d778030237b2c332b9007@macports.org> References: <044.366915d58c1d778030237b2c332b9007@macports.org> Message-ID: <059.7f50a03709bff3f8796c677f3ab92e53@macports.org> #53107: py-pygrib @2.0.2 update ------------------------+---------------------- Reporter: ForTozs | Owner: jswhit Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: py-pygrib | ------------------------+---------------------- Comment (by basmac): Still fails with most recent port selfupdate (Dec 22) as its still trying to build 2.0.1 ? [mac27:/opt/local/lib] root# port install py27-pygrib ---> Computing dependencies for py27-pygrib ---> Fetching archive for py27-pygrib ---> Attempting to fetch py27-pygrib-2.0.1_1.darwin_16.x86_64.tbz2 from https://packages.macports.org/py27-pygrib ---> Attempting to fetch py27-pygrib-2.0.1_1.darwin_16.x86_64.tbz2 from http://sea.us.packages.macports.org/macports/packages/py27-pygrib ---> Attempting to fetch py27-pygrib-2.0.1_1.darwin_16.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/py27-pygrib ---> Fetching distfiles for py27-pygrib ---> Verifying checksums for py27-pygrib ---> Extracting py27-pygrib ---> Configuring py27-pygrib ---> Building py27-pygrib Error: org.macports.build for port py27-pygrib returned: command execution failed Please see the log file for port py27-pygrib for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_python_py-pygrib/py27-pygrib/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port py27-pygrib failed [mac27:/opt/local/lib] -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 14:59:50 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 14:59:50 -0000 Subject: [MacPorts] #53136: emacs 25.1: add modules variant to build with loadable module support Message-ID: <049.6de3ca7b24f01201d0bf164ed39c7f7c@macports.org> #53136: emacs 25.1: add modules variant to build with loadable module support --------------------------+------------------- Reporter: little-big-h | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: modules | Port: emacs --------------------------+------------------- Emacs allows loadable modules with version 25.1. However, this functionality needs to be enabled at build-time. This variant enables loadable module support and installs the header necessary for building modules. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 15:00:03 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 15:00:03 -0000 Subject: [MacPorts] #53136: emacs 25.1: add modules variant to build with loadable module support In-Reply-To: <049.6de3ca7b24f01201d0bf164ed39c7f7c@macports.org> References: <049.6de3ca7b24f01201d0bf164ed39c7f7c@macports.org> Message-ID: <064.bcad8224e16e5cd86c4d2dbd16192850@macports.org> #53136: emacs 25.1: add modules variant to build with loadable module support ---------------------------+--------------------- Reporter: little-big-h | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: modules Port: emacs | ---------------------------+--------------------- Changes (by little-big-h): * Attachment "Portfile-emacs.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 15:26:18 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 15:26:18 -0000 Subject: [MacPorts] #53136: emacs 25.1: add modules variant to build with loadable module support In-Reply-To: <049.6de3ca7b24f01201d0bf164ed39c7f7c@macports.org> References: <049.6de3ca7b24f01201d0bf164ed39c7f7c@macports.org> Message-ID: <064.8ab413a0b0a15453a6aa9a410b7843e2@macports.org> #53136: emacs 25.1: add modules variant to build with loadable module support ---------------------------+---------------------- Reporter: little-big-h | Owner: drkp Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: emacs | ---------------------------+---------------------- Changes (by mf2k): * cc: drkp (removed) * owner: => drkp * status: new => assigned * keywords: modules => haspatch -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 15:27:02 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 15:27:02 -0000 Subject: [MacPorts] #53116: arc @5.21o_1: update to 5.21p In-Reply-To: <041.707e6f126be59a447916450f879d60bb@macports.org> References: <041.707e6f126be59a447916450f879d60bb@macports.org> Message-ID: <056.826709558c52217f36b072c848e138a1@macports.org> #53116: arc @5.21o_1: update to 5.21p ---------------------+---------------------- Reporter: l2dy | Owner: jc@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: arc | ---------------------+---------------------- Changes (by mf2k): * owner: => jc@… * cc: jc@… (removed) * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 15:37:09 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 15:37:09 -0000 Subject: [MacPorts] #53117: Braeburn POST requests (Trac, Mailman) are unreliable In-Reply-To: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> References: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> Message-ID: <056.899bcdee0ae7a64cc839af37b5844150@macports.org> #53117: Braeburn POST requests (Trac, Mailman) are unreliable -----------------------------+--------------------- Reporter: mf2k | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+--------------------- Comment (by neverpanic): On the trac side, we see errors such as {{{ [Tue Dec 20 15:16:42.208829 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] mod_wsgi (pid=24819): Exception occurred processing WSGI script '/var/www/trac/cgi-bin/trac.wsgi'. [Tue Dec 20 15:16:42.208961 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] Traceback (most recent call last): [Tue Dec 20 15:16:42.208980 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] File "/var/www/trac/cgi-bin/trac.wsgi", line 31, in application [Tue Dec 20 15:16:42.209005 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] return dispatch_request(environ, start_request) [Tue Dec 20 15:16:42.209014 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] File "/var/www/trac/virtualenv/lib/python2.7/site- packages/trac/web/main.py", line 530, in dispatch_request [Tue Dec 20 15:16:42.209028 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] return _dispatch_request(req, env, env_error) [Tue Dec 20 15:16:42.209035 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] File "/var/www/trac/virtualenv/lib/python2.7/site- packages/trac/web/main.py", line 569, in _dispatch_request [Tue Dec 20 15:16:42.209045 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] send_internal_error(env, req, sys.exc_info()) [Tue Dec 20 15:16:42.209052 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] File "/var/www/trac/virtualenv/lib/python2.7/site- packages/trac/web/main.py", line 688, in send_internal_error [Tue Dec 20 15:16:42.209062 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] req.send_error(exc_info, status=500, env=env, data=data) [Tue Dec 20 15:16:42.209069 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] File "/var/www/trac/virtualenv/lib/python2.7/site- packages/trac/web/api.py", line 597, in send_error [Tue Dec 20 15:16:42.209080 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] exc_info) [Tue Dec 20 15:16:42.209086 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] File "/var/www/trac/virtualenv/lib/python2.7/site- packages/trac/web/main.py", line 562, in _dispatch_request [Tue Dec 20 15:16:42.209096 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] dispatcher.dispatch(req) [Tue Dec 20 15:16:42.209103 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] File "/var/www/trac/virtualenv/lib/python2.7/site- packages/trac/web/main.py", line 249, in dispatch [Tue Dec 20 15:16:42.209113 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] resp = chosen_handler.process_request(req) [Tue Dec 20 15:16:42.209120 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] File "/var/www/trac/virtualenv/lib/python2.7/site- packages/trac/versioncontrol/web_ui/browser.py", line 404, in process_request [Tue Dec 20 15:16:42.209131 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] self._render_zip(req, context, repos, node, rev) [Tue Dec 20 15:16:42.209205 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] File "/var/www/trac/virtualenv/lib/python2.7/site- packages/trac/versioncontrol/web_ui/browser.py", line 661, in _render_zip [Tue Dec 20 15:16:42.209231 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] render_zip(req, filename, repos, root_node, self._iter_nodes) [Tue Dec 20 15:16:42.209243 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] File "/var/www/trac/virtualenv/lib/python2.7/site- packages/trac/versioncontrol/web_ui/util.py", line 231, in render_zip [Tue Dec 20 15:16:42.209368 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] req.write(zip_str) [Tue Dec 20 15:16:42.209375 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] File "/var/www/trac/virtualenv/lib/python2.7/site- packages/trac/web/api.py", line 698, in write [Tue Dec 20 15:16:42.209394 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] self._write(''.join(buf)) [Tue Dec 20 15:16:42.209410 2016] [wsgi:error] [pid 24819] [remote x.y.z.a:64119] IOError: Apache/mod_wsgi failed to write response data: Broken pipe }}} Unfortunately that's not very helpful in telling us why the pipe was broken (i.e. the connection was closed) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 15:49:39 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 15:49:39 -0000 Subject: [MacPorts] #53117: Braeburn POST requests (Trac, Mailman) are unreliable In-Reply-To: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> References: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> Message-ID: <056.60ae1ee4143d8a75b0114e7cd442b6ae@macports.org> #53117: Braeburn POST requests (Trac, Mailman) are unreliable -----------------------------+--------------------- Reporter: mf2k | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+--------------------- Comment (by neverpanic): I can also see the requests sent to the ticket you were trying to update, but unfortunately no entry in `access.log` with a 500 error code for this ticket (weird, that should have been there). As to the claim that this affects only post requests, that's an interesting observation. I've run some statistics on our logs to check which requests fail more often. We had 664993 GET requests on 2016-12-20, out of which 9973 failed with error 500, which is about 1,5 %. In the same time, we had 970 POST requests, 6 of which failed, i.e. 0.62 %. Ryan: Do you happen to have a specific request to mailman that you saw fail? That would be interesting to analyze to find out whether the problem is on Apache-side or in mod_wsgi. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 15:50:45 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 15:50:45 -0000 Subject: [MacPorts] #53137: Poppler 0.50.0 Undeclared Identifier Message-ID: <042.49cecea225fec8a1f7eb28737b564858@macports.org> #53137: Poppler 0.50.0 Undeclared Identifier ---------------------+--------------------- Reporter: lefte | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: poppler | Port: poppler ---------------------+--------------------- I'm receiving an error when attempting to upgrade poppler from 0.49.0_0 < 0.50.0_1 using `port upgrade outdated`. From the output: {{{ $ sudo port clean poppler ---> Cleaning poppler $ sudo port upgrade outdated ---> Computing dependencies for poppler ---> Fetching archive for poppler ---> Attempting to fetch poppler-0.50.0_1.darwin_16.x86_64.tbz2 from https://packages.macports.org/poppler ---> Attempting to fetch poppler-0.50.0_1.darwin_16.x86_64.tbz2 from http://sea.us.packages.macports.org/macports/packages/poppler ---> Attempting to fetch poppler-0.50.0_1.darwin_16.x86_64.tbz2 from http://lil.fr.packages.macports.org/poppler ---> Fetching distfiles for poppler ---> Verifying checksums for poppler ---> Extracting poppler ---> Configuring poppler ---> Building poppler Error: org.macports.build for port poppler returned: command execution failed Please see the log file for port poppler for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_poppler/poppler/main.log Error: Unable to upgrade port: 1 }}} And the first apparent lines from the log: {{{ 695 :info:build JPEG2000Stream.cc:169:37: error: use of undeclared identifier 'OPJ_CLRSPC_SRGB'; did you mean 'CLRSPC_SRGB'? 696 :info:build if (priv->image->color_space == OPJ_CLRSPC_SRGB && numComps == 4) { numComps = 3; } 697 :info:build ^~~~~~~~~~~~~~~ 698 :info:build CLRSPC_SRGB 699 :info:build /opt/local/include/openjpeg.h:133:2: note: 'CLRSPC_SRGB' declared here 700 :info:build CLRSPC_SRGB = 1, /**< sRGB */ 701 :info:build ^ }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 15:53:44 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 15:53:44 -0000 Subject: [MacPorts] #53137: Poppler 0.50.0 Undeclared Identifier In-Reply-To: <042.49cecea225fec8a1f7eb28737b564858@macports.org> References: <042.49cecea225fec8a1f7eb28737b564858@macports.org> Message-ID: <057.770ba67c5ee757ba2340bcc88c40e5a5@macports.org> #53137: Poppler 0.50.0 Undeclared Identifier ----------------------+--------------------- Reporter: lefte | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: poppler Port: poppler | ----------------------+--------------------- Changes (by lefte): * Attachment "poppler-0-50-0-1-error.log" added. Poppler 0.50.0_1 Error Log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 15:54:15 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 15:54:15 -0000 Subject: [MacPorts] #53137: Poppler 0.50.0 Undeclared Identifier In-Reply-To: <042.49cecea225fec8a1f7eb28737b564858@macports.org> References: <042.49cecea225fec8a1f7eb28737b564858@macports.org> Message-ID: <057.27b7b782a2e89e38b4de1585443d4422@macports.org> #53137: Poppler 0.50.0 Undeclared Identifier ----------------------+---------------------- Reporter: lefte | Owner: dbevans Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: poppler | ----------------------+---------------------- Changes (by mf2k): * keywords: poppler => * status: new => assigned * owner: => dbevans Comment: In the future, please Cc the port maintainers ({{{port info --maintainers poppler}}}), if any. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 15:55:48 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 15:55:48 -0000 Subject: [MacPorts] #53137: Poppler 0.50.0 Undeclared Identifier In-Reply-To: <042.49cecea225fec8a1f7eb28737b564858@macports.org> References: <042.49cecea225fec8a1f7eb28737b564858@macports.org> Message-ID: <057.bd0462f0167564f3530ff125a0308237@macports.org> #53137: Poppler 0.50.0 Undeclared Identifier ----------------------+---------------------- Reporter: lefte | Owner: dbevans Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: poppler | ----------------------+---------------------- Comment (by lefte): Forgot to mention, I'm using OSX Sierra 10.12.2 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 16:09:13 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 16:09:13 -0000 Subject: [MacPorts] #51842: Timidity: request for a new port In-Reply-To: <042.0dbd8a1776b3b4d627b5a128a2c7cbc7@macports.org> References: <042.0dbd8a1776b3b4d627b5a128a2c7cbc7@macports.org> Message-ID: <057.0f55e38b760a4f9bd59493dee3805e1f@macports.org> #51842: Timidity: request for a new port -------------------------+------------------- Reporter: mojca | Owner: mojca Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: timidity | -------------------------+------------------- Comment (by mojca): I committed the sound fonts without implementing any support for `port select` or whatever. Let's do that once it becomes clear what we need in the first place (`port select` doesn't guarantee that anything is selected at all). As far as TiMidity++ goes, I'm thinking of creating a subport, something like `timidity-soundfonts` with the sole purpose of setting up the right configuration files for fonts. It looks like an overkill to me to have to rebuild the binary just for the sake of switching the default sound font (a single line in a text file). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 16:21:00 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 16:21:00 -0000 Subject: [MacPorts] #53117: Braeburn POST requests (Trac, Mailman) are unreliable In-Reply-To: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> References: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> Message-ID: <056.cda17e23e7b9115c9fe26286c4eab6e3@macports.org> #53117: Braeburn POST requests (Trac, Mailman) are unreliable -----------------------------+--------------------- Reporter: mf2k | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+--------------------- Comment (by ryandesign): I don't recall specific mailman failures, just that I experienced the problem several times when submitting forms on the mailman web interface on the day when we moved the lists from macosforge to Braeburn. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 16:33:32 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 16:33:32 -0000 Subject: [MacPorts] #51842: Timidity: request for a new port In-Reply-To: <042.0dbd8a1776b3b4d627b5a128a2c7cbc7@macports.org> References: <042.0dbd8a1776b3b4d627b5a128a2c7cbc7@macports.org> Message-ID: <057.bbfa915cec5418cf4f350a803f36b28d@macports.org> #51842: Timidity: request for a new port -------------------------+------------------- Reporter: mojca | Owner: mojca Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: timidity | -------------------------+------------------- Comment (by RJVB): Agreed for `port select`. I think the proper way to address the timidity.cfg configuration file question is to install both out-of-the-box-supported versions under special names or in a special location (or even keep them in `filespath`), and install one of the two in the post-activate phase if the file doesn't already exist. Which of the two is installed can be under control of a variant. I don't know if this is the official way to handle such a situation, but with an approach like this the file won't be overwritten each time we update timidity. That will most likely not be necessary, and remember that the user ought to be able to change the file to use a sound .cfg file that doesn't come from MacPorts. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 17:57:01 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 17:57:01 -0000 Subject: [MacPorts] #53137: Poppler 0.50.0 Undeclared Identifier In-Reply-To: <042.49cecea225fec8a1f7eb28737b564858@macports.org> References: <042.49cecea225fec8a1f7eb28737b564858@macports.org> Message-ID: <057.ac269c149d593559679e3d955a70b5cb@macports.org> #53137: Poppler 0.50.0 Undeclared Identifier ----------------------+---------------------- Reporter: lefte | Owner: dbevans Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: poppler | ----------------------+---------------------- Changes (by dbevans): * status: assigned => accepted -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 18:18:06 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 18:18:06 -0000 Subject: [MacPorts] #53117: Braeburn POST requests (Trac, Mailman) are unreliable In-Reply-To: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> References: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> Message-ID: <056.b3e18e7399ede7ccec1c463f590b7a01@macports.org> #53117: Braeburn POST requests (Trac, Mailman) are unreliable -----------------------------+--------------------- Reporter: mf2k | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+--------------------- Comment (by neverpanic): I have updated mod_wsgi to the latest version to see if that helps fix the issue. For the record, the resources to build a newer version are - https://github.com/neverpanic/mod_wsgi_debian or Debian's upstream packaging and - https://github.com/neverpanic/mod_wsgi_docker_build -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 20:44:41 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 20:44:41 -0000 Subject: [MacPorts] #53021: octave @4.2.0_1 +gcc6 +openblas: build failure In-Reply-To: <041.a9100f410b771f7245060d742521900f@macports.org> References: <041.a9100f410b771f7245060d742521900f@macports.org> Message-ID: <056.442d6f39e9d77fab5187072da6e42562@macports.org> #53021: octave @4.2.0_1 +gcc6 +openblas: build failure ---------------------+--------------------------------- Reporter: mf2k | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: octave | ---------------------+--------------------------------- Comment (by mf2k): Yes, it builds for me now. Thank you! {{{ $ port installed octave The following ports are currently installed: octave @4.2.0_1+app+docs+fltk+gcc6+openblas+qt4+sound (active) }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 20:45:26 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 20:45:26 -0000 Subject: [MacPorts] #53021: octave @4.2.0_1 +gcc6 +openblas: build failure In-Reply-To: <041.a9100f410b771f7245060d742521900f@macports.org> References: <041.a9100f410b771f7245060d742521900f@macports.org> Message-ID: <056.12cd4e7607330dc2db86688208f49c1e@macports.org> #53021: octave @4.2.0_1 +gcc6 +openblas: build failure ---------------------+--------------------------------- Reporter: mf2k | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: octave | ---------------------+--------------------------------- Changes (by mf2k): * status: new => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 20:51:11 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 20:51:11 -0000 Subject: [MacPorts] #52992: fluid-soundfont, generaluser-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.caee62a8a39a0d4f1f9370a4d7c2ef00@macports.org> #52992: fluid-soundfont, generaluser-soundfont: add new sound fonts ----------------------------------------------------+-------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: fluid-soundfont generaluser-soundfont | ----------------------------------------------------+-------------------- Comment (by mojca): We have some problems. The installed package seems to contain some backup files that I didn't notice earlier, but I don't understand where they come from: {{{ x ./opt/local/share/sounds/sf2/._GeneralUser_GS_v1.47.sf2 x ./opt/local/share/sounds/sf2/GeneralUser_GS_v1.47.sf2 x ./opt/local/share/examples/generaluser-soundfont/ x ./opt/local/share/examples/generaluser-soundfont/._All Night Long.mid x ./opt/local/share/examples/generaluser-soundfont/All Night Long.mid x ./opt/local/share/examples/generaluser-soundfont/._GUTest.mid x ./opt/local/share/examples/generaluser-soundfont/GUTest.mid x ./opt/local/share/examples/generaluser-soundfont/._Take 5 - by Paul Desmond.mid x ./opt/local/share/examples/generaluser-soundfont/Take 5 - by Paul Desmond.mid x ./opt/local/share/examples/generaluser-soundfont/._The Christmas Song.mid x ./opt/local/share/examples/generaluser-soundfont/The Christmas Song.mid x ./opt/local/share/examples/generaluser-soundfont/._To Make the End of Battle.mid x ./opt/local/share/examples/generaluser-soundfont/To Make the End of Battle.mid x ./opt/local/share/examples/generaluser-soundfont/._earthday.mid x ./opt/local/share/examples/generaluser-soundfont/earthday.mid x ./opt/local/share/examples/generaluser-soundfont/._majicalljarr.mid x ./opt/local/share/examples/generaluser-soundfont/majicalljarr.mid x ./opt/local/share/doc/generaluser-soundfont/ x ./opt/local/share/doc/generaluser-soundfont/._CHANGELOG.txt x ./opt/local/share/doc/generaluser-soundfont/CHANGELOG.txt x ./opt/local/share/doc/generaluser-soundfont/._GU1.43 Percussion Map.pdf x ./opt/local/share/doc/generaluser-soundfont/GU1.43 Percussion Map.pdf x ./opt/local/share/doc/generaluser-soundfont/._LICENSE.txt x ./opt/local/share/doc/generaluser-soundfont/LICENSE.txt x ./opt/local/share/doc/generaluser-soundfont/._README.txt x ./opt/local/share/doc/generaluser-soundfont/README.txt }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 22:08:00 2016 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2016 22:08:00 -0000 Subject: [MacPorts] #52992: fluid-soundfont, generaluser-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.196bb65c5c3a4124835f0a7c591d6caa@macports.org> #52992: fluid-soundfont, generaluser-soundfont: add new sound fonts ----------------------------------------------------+-------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: fluid-soundfont generaluser-soundfont | ----------------------------------------------------+-------------------- Comment (by RJVB): Ah! I do *not* get those. Did you install a binary package from the build bots or one created locally? I think those ._ files might come from unzipping the original archive but what I don't understand is how the end up in the destroot. This is what's done during destroot: {{{ xinstall -m 644 "${worksrcpath}/GeneralUser GS v${version}.sf2" ${dir}/GeneralUser_GS_v${version}.sf2 set dir ${destroot}${prefix}/share/doc/${name} xinstall -m 755 -d ${dir} foreach f {CHANGELOG.txt LICENSE.txt README.txt "instrument lists/GU1.43 Percussion Map.pdf"} { xinstall -m 644 "${worksrcpath}/${f}" ${dir} } set dir ${destroot}${prefix}/share/examples/${name} xinstall -m 755 -d ${dir} xinstall -m 644 "${worksrcpath}/GUTest.mid" ${dir} foreach f [glob -nocomplain "${worksrcpath}/demo MIDIs/*"] { xinstall -m 644 "${f}" ${dir} } }}} Even if unzipping the archive creates those ._ files we shouldn't be copying them into the destroot. Mojca, is your ${workpath} on an HFS filesystem? You'd be seeing this kind of behaviour if you're using a FAT32 system, for instance. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 00:16:31 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 00:16:31 -0000 Subject: [MacPorts] #52985: buildbot: dependency calculation sometimes prohibitively expensive In-Reply-To: <042.82c02616dc3faf0568ebc12b946c1b94@macports.org> References: <042.82c02616dc3faf0568ebc12b946c1b94@macports.org> Message-ID: <057.b28b8fababc07c2c1ff4949eeda6bd3a@macports.org> #52985: buildbot: dependency calculation sometimes prohibitively expensive -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: 2.3.5 Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Comment (by jmroot): The problem is NP-complete in the general case (hence the use of a SAT solver in the GSOC work), so quadratic ain't bad? ;) Dependency calculation performance for mpbb should be a fair bit better after [changeset:af8a1e0e531d7026bd5f2578a47652be1c476a00/mpbb af8a1e0] at least. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 00:34:16 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 00:34:16 -0000 Subject: [MacPorts] #52985: buildbot: dependency calculation sometimes prohibitively expensive In-Reply-To: <042.82c02616dc3faf0568ebc12b946c1b94@macports.org> References: <042.82c02616dc3faf0568ebc12b946c1b94@macports.org> Message-ID: <057.cd8a542a36fc62eeaea9de89d657afe4@macports.org> #52985: buildbot: dependency calculation sometimes prohibitively expensive -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: 2.3.5 Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Comment (by mojca): Still [https://build.macports.org/builders/ports-10.5_ppc_legacy- builder/builds/12980 too long] though. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 00:47:44 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 00:47:44 -0000 Subject: [MacPorts] #52992: fluid-soundfont, generaluser-soundfont: add new sound fonts In-Reply-To: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> References: <042.b28fe838429df3ee53f9b071ce414e9f@macports.org> Message-ID: <057.49d044f3d59d0147a1012d8ace406e05@macports.org> #52992: fluid-soundfont, generaluser-soundfont: add new sound fonts ----------------------------------------------------+-------------------- Reporter: mojca | Owner: RJVB Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: fluid-soundfont generaluser-soundfont | ----------------------------------------------------+-------------------- Comment (by mojca): No, I'm not using any FAT32 system. I'm not sure if it came from a local build or from a server because that depends on whether the package was already built on the server at the time when I experienced this problem. But I'm currently unable to reproduce it, so let's forget about it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 01:01:11 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 01:01:11 -0000 Subject: [MacPorts] #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies Message-ID: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies -------------------------+------------------------------------------------- Reporter: | Owner: maxkalashnikov- | macports | Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: clang-3.3 clang-3.4 clang-3.5 | clang-3.6 clang-3.7 clang-3.8 clang-3.9 -------------------------+------------------------------------------------- This seems similar to #52091 du to the common error output for any of the clang ports: {{{ Error: The following dependencies were not installed: cctools llvm-3.9 clang-3.8 clang-3.7 ld64 ld64-latest llvm-3.8 }}} I believe this worked in version 2.3.4, and I haven't installed a differen Xcode, which is 5.1.1. Full otuput of `port -d install clang-3.3` attached. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 01:01:43 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 01:01:43 -0000 Subject: [MacPorts] #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies In-Reply-To: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> References: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> Message-ID: <075.2077abaaa5b31cf5b81e379c6ec2be56@macports.org> #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies -------------------------------------------------+------------------------- Reporter: maxkalashnikov-macports | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: clang-3.3 clang-3.4 clang-3.5 | clang-3.6 clang-3.7 clang-3.8 clang-3.9 | -------------------------------------------------+------------------------- Changes (by maxkalashnikov-macports): * Attachment "mp-debug" added. port -d install clang-3.3 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 01:05:29 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 01:05:29 -0000 Subject: [MacPorts] #52985: buildbot: dependency calculation sometimes prohibitively expensive In-Reply-To: <042.82c02616dc3faf0568ebc12b946c1b94@macports.org> References: <042.82c02616dc3faf0568ebc12b946c1b94@macports.org> Message-ID: <057.d1d984afd8cbeb32042a7ec42302cb8c@macports.org> #52985: buildbot: dependency calculation sometimes prohibitively expensive -----------------------------+---------------------- Reporter: mojca | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: 2.3.5 Resolution: | Keywords: buildbot Port: | -----------------------------+---------------------- Comment (by jmroot): It doesn't look like the dependency calculation is what took the majority of the time there, but rather that it got stuck querying the fail cache. We could print a timestamp after each step to find out. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 01:36:10 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 01:36:10 -0000 Subject: [MacPorts] #53139: gcc7 update Message-ID: <043.ee044657c3df4809f8316644719c337e@macports.org> #53139: gcc7 update --------------------+----------------- Reporter: rouson | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: --------------------+----------------- Please update the gcc7 port. The current gcc7 port is dated 20161204. I'm hoping to access features that hit the GCC trunk more recently. Damian -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 04:13:55 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 04:13:55 -0000 Subject: [MacPorts] #53133: sbt @0.13.11: upgrade to 0.13.13 In-Reply-To: <048.c986743b9245fa762ef56417535fc28b@macports.org> References: <048.c986743b9245fa762ef56417535fc28b@macports.org> Message-ID: <063.2a6d83d48a1af126ddce0151cc66a27b@macports.org> #53133: sbt @0.13.11: upgrade to 0.13.13 --------------------------+---------------------- Reporter: nhojpatrick | Owner: blair Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: sbt | --------------------------+---------------------- Changes (by nhojpatrick): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"ec5d09bdda50f6142d15897c9e771565f48cf9c9/macports-ports" ec5d09bd/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="ec5d09bdda50f6142d15897c9e771565f48cf9c9" trac-53133 sbt upgrade to v0.13.13 Closes #108 Fixes https://trac.macports.org/ticket/53133 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 04:59:11 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 04:59:11 -0000 Subject: [MacPorts] #53136: emacs 25.1: add modules variant to build with loadable module support In-Reply-To: <049.6de3ca7b24f01201d0bf164ed39c7f7c@macports.org> References: <049.6de3ca7b24f01201d0bf164ed39c7f7c@macports.org> Message-ID: <064.d3f5179236f0540d7861e16f23ee85e8@macports.org> #53136: emacs 25.1: add modules variant to build with loadable module support ---------------------------+---------------------- Reporter: little-big-h | Owner: drkp Type: enhancement | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: emacs | ---------------------------+---------------------- Changes (by drkp): * status: assigned => accepted Comment: Thanks for the patch! Any downsides to just having this enabled all the time, instead of making it a variant? We might as well cut down on the number of variants. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 05:11:45 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 05:11:45 -0000 Subject: [MacPorts] #53136: emacs 25.1: add modules variant to build with loadable module support In-Reply-To: <049.6de3ca7b24f01201d0bf164ed39c7f7c@macports.org> References: <049.6de3ca7b24f01201d0bf164ed39c7f7c@macports.org> Message-ID: <064.8b689266e5439d6d7727685a27a8bf68@macports.org> #53136: emacs 25.1: add modules variant to build with loadable module support ---------------------------+---------------------- Reporter: little-big-h | Owner: drkp Type: enhancement | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: emacs | ---------------------------+---------------------- Comment (by little-big-h): Excellent question. I've been thinking about this myself: The emacs-folks chose to disable dynamic modules by default and I just went along. I couldn't find any discussion or justification online but my gut tells me rms is somehow behind this :-) - I think he's not happy about having modules in there in the first place. I guess you could just enable it by default. I suspect it will become the default eventually and the patch will be unnecessary. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 08:24:04 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 08:24:04 -0000 Subject: [MacPorts] #52739: perl5 @5.22.2: build_arch and universal not fully respected In-Reply-To: <056.4e6ca570aea71d217bf9e4d745049e68@macports.org> References: <056.4e6ca570aea71d217bf9e4d745049e68@macports.org> Message-ID: <071.1c5ef738b9f15b2e51c8a72078447d10@macports.org> #52739: perl5 @5.22.2: build_arch and universal not fully respected ----------------------------------+---------------------- Reporter: MarcusCalhoun-Lopez | Owner: mojca@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: perl5 | ----------------------------------+---------------------- Comment (by mojca): * I was trying to address both this ticket and #52290 or at least try to understand whether any of these patches addresses the other bug or not (but the one who reported the problem didn't respond). * I still have no clue how to test the `.bundle` files. To start with, it would help if I knew which port to test. * It's not clear to me if we still have issues with `MACOSX_DEPLOYMENT_TARGET`. If the first patch woks satisfactory, I would go with the first one (adding lddflags). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 08:25:46 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 08:25:46 -0000 Subject: [MacPorts] #52290: perl5: cannot be built as ppc/i386 universal on x86_64 In-Reply-To: <060.f85f2e1baee9d53bb0ad2bd078190a1b@macports.org> References: <060.f85f2e1baee9d53bb0ad2bd078190a1b@macports.org> Message-ID: <075.8c68f0277392354feecffcc86f19fe23@macports.org> #52290: perl5: cannot be built as ppc/i386 universal on x86_64 ------------------------------+------------------- Reporter: ridethecliche@… | Owner: mojca Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: perl5.22 | ------------------------------+------------------- Comment (by mojca): PING. Can you please test the patches from #52739 and report if any of them solves the problem for you? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 08:35:35 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 08:35:35 -0000 Subject: [MacPorts] #42161: grass: compatibility with wxWidgets 3.0 In-Reply-To: <042.fc1a367dcdd70301a8ba57b6d19e02f2@macports.org> References: <042.fc1a367dcdd70301a8ba57b6d19e02f2@macports.org> Message-ID: <057.a88e30835374459f1ba48390953efa55@macports.org> #42161: grass: compatibility with wxWidgets 3.0 ---------------------+-------------------------------- Reporter: mojca | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: grass | ---------------------+-------------------------------- Changes (by mojca): * cc: Veence (added) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 08:44:05 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 08:44:05 -0000 Subject: [MacPorts] #44056: grass: upgrade to 7.0.0 In-Reply-To: <042.e79e3c1085ee1bd6ec8cdea687817110@macports.org> References: <042.e79e3c1085ee1bd6ec8cdea687817110@macports.org> Message-ID: <057.64de79b6fb2dd964c3c0d4b9bcfa6bd9@macports.org> #44056: grass: upgrade to 7.0.0 ---------------------+---------------------- Reporter: mojca | Owner: Veence Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: grass | ---------------------+---------------------- Changes (by mojca): * owner: macports-tickets@… => Veence * status: new => assigned * cc: Veence (removed) Comment: I'm assigning this ticket to Vincent who already created a port `grass7` in r142757 and kept updating it. Perhaps this ticket could be closed already? Perhaps we should rename `grass` to `grass6` (or perhaps better: remove grass6)? At some point I would like to get rid of `py-wxpython-2.8` (see ticket #46351) and grass 6 is one of two ports that still keep using it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 09:38:08 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 09:38:08 -0000 Subject: [MacPorts] #51668: texlive-texdist: new port In-Reply-To: <044.23afc3670fb54ae1779114e944c5da6a@macports.org> References: <044.23afc3670fb54ae1779114e944c5da6a@macports.org> Message-ID: <059.99ac190f14e14de1919bf06c07f19214@macports.org> #51668: texlive-texdist: new port ------------------------------+-------------------------------- Reporter: dliessi | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: texlive-texdist | ------------------------------+-------------------------------- Comment (by mojca): I didn't see this ticket earlier. Thanks a lot. Why do you make symlinks to `powerpc` rather than making a symlink to the actual architecture being used? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 09:47:18 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 09:47:18 -0000 Subject: [MacPorts] #51668: texlive-texdist: new port In-Reply-To: <044.23afc3670fb54ae1779114e944c5da6a@macports.org> References: <044.23afc3670fb54ae1779114e944c5da6a@macports.org> Message-ID: <059.3211f435c9c57b7856d4c8e8eea72fe2@macports.org> #51668: texlive-texdist: new port ------------------------------+-------------------------------- Reporter: dliessi | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: texlive-texdist | ------------------------------+-------------------------------- Comment (by mojca): I'm very happy that you sent this patch. But in my opinion this should be part of `texlive-common`. Otherwise people will either forget to install `texlive-texmfdist` or keep it installed long after they remove `texlive` form MacPorts. Then again, in case Dan would not be comfortable putting the code there, it's still better to have a functional package than not having anything at all. Dan? Would you be willing to accept the contents to one of your existing texlive packages? I imagine `texlive-common` would be the best place, but it's up to you. (I wonder if we really need all the zillion symlinks though. I thought the original author had a neat idea to use them somehow, but I imagine that nowadays almost the only useful bit is the bin dir.) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 09:54:14 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 09:54:14 -0000 Subject: [MacPorts] #53140: cctools @895_3 do not build on PPC Tiger, Mac OS X 10.4.11, because OFILE_LLVM_BITCODE macro is used in misc/strings.c Message-ID: <046.826b272879a9dece0fde20ec935cab75@macports.org> #53140: cctools @895_3 do not build on PPC Tiger, Mac OS X 10.4.11, because OFILE_LLVM_BITCODE macro is used in misc/strings.c -----------------------+--------------------- Reporter: ballapete | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: cctools -----------------------+--------------------- misc/strings.c contains: {{{ if(ofile->object_addr == NULL || ofile->member_type == OFILE_LLVM_BITCODE){ }}} In include/stuff/ofile.c stands: {{{ enum ofile_type { OFILE_UNKNOWN, OFILE_FAT, OFILE_ARCHIVE, OFILE_Mach_O #ifdef LTO_SUPPORT , OFILE_LLVM_BITCODE #endif /* LTO_SUPPORT */ }; }}} which is pre-processed to: {{{ enum ofile_type { OFILE_UNKNOWN, OFILE_FAT, OFILE_ARCHIVE, OFILE_Mach_O }; }}} so that GCC has to state: {{{ :info:build /opt/local/bin/gcc-apple-4.2 -Os -std=gnu99 -Os -DTRIE_SUPPORT -g -Wall -I. -I./../include -I. -I/opt/local/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_lil.fr.rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-895/../ld64-274.1/src/abstraction -I/opt/local/var/macports/build/_opt_local_var_macports_sources_lil.fr.rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-895/../ld64-274.1/src/other -I/opt/local/var/macports/build/_opt_local_var_macports_sources_lil.fr.rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-895/include -I/opt/local/include -arch ppc -c -o ./strings.o strings.c :info:build In file included from ./../include/stuff/bytesex.h:53, :info:build from ./../include/stuff/ofile.h:39, :info:build from strings.c:80: :info:build ./../include/mach/arm/thread_status.h:29:1: warning: "THREAD_STATE_NONE" redefined :info:build In file included from ./../include/stuff/bytesex.h:50, :info:build from ./../include/stuff/ofile.h:39, :info:build from strings.c:80: :info:build ./../include/mach/i386/thread_status.h:112:1: warning: this is the location of the previous definition :info:build In file included from ./../include/stuff/bytesex.h:53, :info:build from ./../include/stuff/ofile.h:39, :info:build from strings.c:80: :info:build ./../include/mach/arm/thread_status.h:50:1: warning: "VALID_THREAD_STATE_FLAVOR" redefined :info:build In file included from ./../include/stuff/bytesex.h:50, :info:build from ./../include/stuff/ofile.h:39, :info:build from strings.c:80: :info:build ./../include/mach/i386/thread_status.h:130:1: warning: this is the location of the previous definition :info:build In file included from ./../include/stuff/bytesex.h:53, :info:build from ./../include/stuff/ofile.h:39, :info:build from strings.c:80: :info:build ./../include/mach/arm/thread_status.h:105:1: warning: "MACHINE_THREAD_STATE" redefined :info:build In file included from ./../include/stuff/bytesex.h:50, :info:build from ./../include/stuff/ofile.h:39, :info:build from strings.c:80: :info:build ./../include/mach/i386/thread_status.h:286:1: warning: this is the location of the previous definition :info:build In file included from ./../include/stuff/bytesex.h:53, :info:build from ./../include/stuff/ofile.h:39, :info:build from strings.c:80: :info:build ./../include/mach/arm/thread_status.h:106:1: warning: "MACHINE_THREAD_STATE_COUNT" redefined :info:build In file included from ./../include/stuff/bytesex.h:50, :info:build from ./../include/stuff/ofile.h:39, :info:build from strings.c:80: :info:build ./../include/mach/i386/thread_status.h:287:1: warning: this is the location of the previous definition :info:build In file included from ./../include/stuff/ofile.h:39, :info:build from strings.c:80: :info:build ./../include/stuff/bytesex.h:244: warning: 'struct __darwin_i386_float_state' declared inside parameter list :info:build ./../include/stuff/bytesex.h:244: warning: its scope is only this definition or declaration, which is probably not what you want :info:build strings.c: In function 'ofile_processor': :info:build strings.c:338: error: 'OFILE_LLVM_BITCODE' undeclared (first use in this function) :info:build strings.c:338: error: (Each undeclared identifier is reported only once :info:build strings.c:338: error: for each function it appears in.) :info:build make[1]: *** [strings.o] Error 1 :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_lil.fr.rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-895/misc' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 09:54:47 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 09:54:47 -0000 Subject: [MacPorts] #53140: cctools @895_3 do not build on PPC Tiger, Mac OS X 10.4.11, because OFILE_LLVM_BITCODE macro is used in misc/strings.c In-Reply-To: <046.826b272879a9dece0fde20ec935cab75@macports.org> References: <046.826b272879a9dece0fde20ec935cab75@macports.org> Message-ID: <061.4aa136e0c37174b3592d86c52e0f5462@macports.org> #53140: cctools @895_3 do not build on PPC Tiger, Mac OS X 10.4.11, because OFILE_LLVM_BITCODE macro is used in misc/strings.c ------------------------+----------------- Reporter: ballapete | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cctools | ------------------------+----------------- Changes (by ballapete): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 09:57:02 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 09:57:02 -0000 Subject: [MacPorts] #53140: cctools @895_3 do not build on PPC Tiger, Mac OS X 10.4.11, because OFILE_LLVM_BITCODE macro is used in misc/strings.c In-Reply-To: <046.826b272879a9dece0fde20ec935cab75@macports.org> References: <046.826b272879a9dece0fde20ec935cab75@macports.org> Message-ID: <061.07d5df22d9c352c659a498297b458d7e@macports.org> #53140: cctools @895_3 do not build on PPC Tiger, Mac OS X 10.4.11, because OFILE_LLVM_BITCODE macro is used in misc/strings.c ------------------------+----------------- Reporter: ballapete | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cctools | ------------------------+----------------- Comment (by ballapete): The following patch fixes the problem: {{{ +++ misc/strings.c 2016-12-23 10:35:34.000000000 +0100 @@ -335,8 +335,13 @@ * If the ofile is not an object file then process it without reguard * to sections. */ - if(ofile->object_addr == NULL || ofile->member_type == OFILE_LLVM_BITCODE){ - if(ofile->file_type == OFILE_FAT && ofile->arch_flag.cputype != 0){ + if(ofile->object_addr == NULL +#ifdef LTO_SUPPORT + || ofile->member_type == OFILE_LLVM_BITCODE){ +#else + ){ +#endif /* LTO_SUPPORT */ + if(ofile->file_type == OFILE_FAT && ofile->arch_flag.cputype != 0){ if(ofile->fat_header->magic == FAT_MAGIC_64){ addr = ofile->file_addr + ofile->fat_archs64[ofile->narch].offset; }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 09:57:30 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 09:57:30 -0000 Subject: [MacPorts] #53140: cctools @895_3 do not build on PPC Tiger, Mac OS X 10.4.11, because OFILE_LLVM_BITCODE macro is used in misc/strings.c In-Reply-To: <046.826b272879a9dece0fde20ec935cab75@macports.org> References: <046.826b272879a9dece0fde20ec935cab75@macports.org> Message-ID: <061.83c19e6edd8e3f3781041c2ce14acf0c@macports.org> #53140: cctools @895_3 do not build on PPC Tiger, Mac OS X 10.4.11, because OFILE_LLVM_BITCODE macro is used in misc/strings.c ------------------------+----------------- Reporter: ballapete | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cctools | ------------------------+----------------- Changes (by ballapete): * Attachment "cctools-895-OFILE_LLVM_BITCODE.patch" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 09:59:27 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 09:59:27 -0000 Subject: [MacPorts] #53139: gcc7 update In-Reply-To: <043.ee044657c3df4809f8316644719c337e@macports.org> References: <043.ee044657c3df4809f8316644719c337e@macports.org> Message-ID: <058.f9e093edbe1ce38c52e376f9686d1045@macports.org> #53139: gcc7 update ---------------------+----------------- Reporter: rouson | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gcc7 | ---------------------+----------------- Changes (by raimue): * port: => gcc7 Comment: The fastest way to get a newer version would be to provide a patch to update the Portfile, see [wiki:howto/Upgrade]. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 11:39:11 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 11:39:11 -0000 Subject: [MacPorts] #53141: python36 @3.6.0rc2: update to 3.6.0 Message-ID: <041.cb4ea61559968984e1e3ce111be272eb@macports.org> #53141: python36 @3.6.0rc2: update to 3.6.0 --------------------+---------------------- Reporter: l2dy | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: python36 --------------------+---------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 11:53:49 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 11:53:49 -0000 Subject: [MacPorts] #51668: texlive-texdist: new port In-Reply-To: <044.23afc3670fb54ae1779114e944c5da6a@macports.org> References: <044.23afc3670fb54ae1779114e944c5da6a@macports.org> Message-ID: <059.ae612a07ceb5d265921350c76bb9a913@macports.org> #51668: texlive-texdist: new port ------------------------------+-------------------------------- Reporter: dliessi | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: texlive-texdist | ------------------------------+-------------------------------- Comment (by dliessi): Replying to [comment:2 mojca]: > Why do you make symlinks to `powerpc` rather than making a symlink to the actual architecture being used? That is what also MacTeX does for its symlinks: e.g., MacTeX 2013 links `ppc`, `powerpc`, `i386` to `bin/universal-darwin`, `x86_64` to `bin/x86_64-darwin` and `texbin` to `x86_64`. I don't recall the exact reason, but there might be some programs that check for a specific architecture instead of texbin. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 12:01:02 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 12:01:02 -0000 Subject: [MacPorts] #51668: texlive-texdist: new port In-Reply-To: <044.23afc3670fb54ae1779114e944c5da6a@macports.org> References: <044.23afc3670fb54ae1779114e944c5da6a@macports.org> Message-ID: <059.a41cc1fd3e21d4071294f54b42e4c88f@macports.org> #51668: texlive-texdist: new port ------------------------------+-------------------------------- Reporter: dliessi | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: texlive-texdist | ------------------------------+-------------------------------- Comment (by dliessi): Replying to [comment:3 mojca]: > I'm very happy that you sent this patch. But in my opinion this should be part of `texlive-common`. Otherwise people will either forget to install `texlive-texmfdist` or keep it installed long after they remove `texlive` form MacPorts. I would not oppose including this in one of the texlive ports. I would even be willing to maintain the relevant part of that Portfile. The reason for having a separate port is that I believe most MacTeX users will not install TeX Live through MacPorts and most MacPorts TeX Live users will not install MacTeX, so this package is probably useless for most TeX users on Mac. (One of the entries in my to-do list is to ask the author(s) of the `texdist` script to put it somewhere online and provide also that script via this package, which would motivate a separate package. The script is currently available only inside the MacTeX bundles, as far as I know.) > (I wonder if we really need all the zillion symlinks though. I thought the original author had a neat idea to use them somehow, but I imagine that nowadays almost the only useful bit is the bin dir.) (Indeed, the original author had great plans, and you are probably right, but I decided to provide the full directory structure to adhere to the informal specification and for consistency with the ones provided by MacTeX.) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 12:05:40 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 12:05:40 -0000 Subject: [MacPorts] #51668: texlive-texdist: new port In-Reply-To: <044.23afc3670fb54ae1779114e944c5da6a@macports.org> References: <044.23afc3670fb54ae1779114e944c5da6a@macports.org> Message-ID: <059.648d88251bc16fb25d8f2317a232ada6@macports.org> #51668: texlive-texdist: new port ------------------------------+-------------------------------- Reporter: dliessi | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: texlive-texdist | ------------------------------+-------------------------------- Comment (by mojca): No, `ppc` is there because MacTeX provides binaries for several architectures and it is in principle possible to switch between them (nowadays you could switch between `x86_64` and `universal` (=`i386`+`ppc`)). MacTeX installs it "just in case", but you wouldn't want to use PPC on 10.12 anyway. Providing symlinks for anything but the exact architecture(s) that MacPorts builds on that particular machine is useless. If you start working on texdist itself, please keep me in the loop. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 12:19:16 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 12:19:16 -0000 Subject: [MacPorts] #51668: texlive-texdist: new port In-Reply-To: <044.23afc3670fb54ae1779114e944c5da6a@macports.org> References: <044.23afc3670fb54ae1779114e944c5da6a@macports.org> Message-ID: <059.061314daae5a37752b36670e43f317c5@macports.org> #51668: texlive-texdist: new port ------------------------------+-------------------------------- Reporter: dliessi | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: texlive-texdist | ------------------------------+-------------------------------- Comment (by dliessi): Replying to [comment:6 mojca]: > No, `ppc` is there because MacTeX provides binaries for several architectures and it is in principle possible to switch between them (nowadays you could switch between `x86_64` and `universal` (=`i386`+`ppc`)). MacTeX installs it "just in case", but you wouldn't want to use PPC on 10.12 anyway. Providing symlinks for anything but the exact architecture(s) that MacPorts builds on that particular machine is useless. OK, maybe I misunderstood what was going on. I'll try removing "false" symlinks and test switching between distributions and see how programs behave. > If you start working on texdist itself, please keep me in the loop. I will. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 13:36:31 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 13:36:31 -0000 Subject: [MacPorts] #53142: py-poppler-qt5 @0.24.2_0: new port Message-ID: <044.775e8b80dd329fb47e07e1295012ac85@macports.org> #53142: py-poppler-qt5 @0.24.2_0: new port ------------------------+---------------------------- Reporter: dliessi | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: py-poppler-qt5 ------------------------+---------------------------- Analogous to py-poppler-qt4, it will be a dependency of new versions of Frescobaldi. See [https://github.com/macports/macports-ports/pull/120 pull request]. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 14:19:44 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 14:19:44 -0000 Subject: [MacPorts] #53139: gcc7 update In-Reply-To: <043.ee044657c3df4809f8316644719c337e@macports.org> References: <043.ee044657c3df4809f8316644719c337e@macports.org> Message-ID: <058.e263f8f407ef58cf1c0aa63f8592aa35@macports.org> #53139: gcc7 update ---------------------+------------------------ Reporter: rouson | Owner: ryandesign Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gcc7 | ---------------------+------------------------ Changes (by ryandesign): * owner: => ryandesign * status: new => accepted -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 14:21:25 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 14:21:25 -0000 Subject: [MacPorts] #53139: gcc7 update In-Reply-To: <043.ee044657c3df4809f8316644719c337e@macports.org> References: <043.ee044657c3df4809f8316644719c337e@macports.org> Message-ID: <058.cab118e465831ca54b1a11b5e47669b4@macports.org> #53139: gcc7 update ---------------------+------------------------ Reporter: rouson | Owner: ryandesign Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gcc7 | ---------------------+------------------------ Comment (by ryandesign): We need more than just a simple update here. The library version of one of the gcc libraries changed in the last version (or I noticed it in the last version), and as a result, we need to add a libgcc6 subport to the gcc6 port to provide the previous library version and make gcc6 and all previous versions use it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 14:35:10 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 14:35:10 -0000 Subject: [MacPorts] #52500: py-pyqt5 @5.6: conflict between Python versions In-Reply-To: <044.d13f04b961b76931b075833a7608276a@macports.org> References: <044.d13f04b961b76931b075833a7608276a@macports.org> Message-ID: <059.84eeea679a5facb49c094f3be9d38270@macports.org> #52500: py-pyqt5 @5.6: conflict between Python versions -----------------------+--------------------------------- Reporter: dliessi | Owner: mamoll Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch maintainer Port: py-pyqt5 | -----------------------+--------------------------------- Comment (by dliessi): Indeed I've been able to install both py27-pyqt5 and py35-pyqt5. Thanks for fixing. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 14:35:54 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 14:35:54 -0000 Subject: [MacPorts] #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies In-Reply-To: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> References: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> Message-ID: <075.132bdcd13b58a0bb6f0e50b2b3bae874@macports.org> #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies -------------------------------------------------+------------------------- Reporter: maxkalashnikov-macports | Owner: jeremyhu Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: clang-3.3 clang-3.4 clang-3.5 | clang-3.6 clang-3.7 clang-3.8 clang-3.9 | -------------------------------------------------+------------------------- Changes (by mf2k): * status: new => assigned * cc: larryv (added) * owner: => jeremyhu Comment: In the future, please Cc the port maintainers ({{{port info --maintainers clang-3.3 clang-3.4 clang-3.5 clang-3.6 clang-3.7 clang-3.8 clang-3.9}}}), if any. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 14:47:20 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 14:47:20 -0000 Subject: [MacPorts] #53140: cctools @895_3 do not build on PPC Tiger, Mac OS X 10.4.11, because OFILE_LLVM_BITCODE macro is used in misc/strings.c In-Reply-To: <046.826b272879a9dece0fde20ec935cab75@macports.org> References: <046.826b272879a9dece0fde20ec935cab75@macports.org> Message-ID: <061.97ceb52c1ababc54232824a655a91cc3@macports.org> #53140: cctools @895_3 do not build on PPC Tiger, Mac OS X 10.4.11, because OFILE_LLVM_BITCODE macro is used in misc/strings.c ------------------------+--------------------------- Reporter: ballapete | Owner: jeremyhu Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: tiger powerpc Port: cctools | ------------------------+--------------------------- Changes (by mf2k): * cc: jeremyhu@… (removed) * keywords: => tiger powerpc * status: new => assigned * owner: => jeremyhu -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 14:49:59 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 14:49:59 -0000 Subject: [MacPorts] #53141: python36 @3.6.0rc2: update to 3.6.0 In-Reply-To: <041.cb4ea61559968984e1e3ce111be272eb@macports.org> References: <041.cb4ea61559968984e1e3ce111be272eb@macports.org> Message-ID: <056.54a6c559323362bdb7924637c0dcca28@macports.org> #53141: python36 @3.6.0rc2: update to 3.6.0 -----------------------+---------------------------- Reporter: l2dy | Owner: jyrkiwahlstedt Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: python36 | -----------------------+---------------------------- Changes (by mf2k): * cc: jyrkiwahlstedt (removed) * owner: => jyrkiwahlstedt * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 15:00:45 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 15:00:45 -0000 Subject: [MacPorts] #53115: argtable armadillo libpointing : Remove maintainer In-Reply-To: <053.42672d0e8653539f8a48a55963b730b3@macports.org> References: <053.42672d0e8653539f8a48a55963b730b3@macports.org> Message-ID: <068.1518ea666ce6e02af6e6c42a482752c4@macports.org> #53115: argtable armadillo libpointing : Remove maintainer ---------------------------------------------+---------------------------- Reporter: ChristianFrisson | Owner: kurthindenburg Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: argtable armadillo libpointing | ---------------------------------------------+---------------------------- Changes (by kurthindenburg): * status: new => closed * owner: => kurthindenburg * resolution: => fixed Comment: In [changeset:"bbcc0c26419eda061bcbe6a4edb17b81fa07c7a0/macports-ports" bbcc0c26/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="bbcc0c26419eda061bcbe6a4edb17b81fa07c7a0" argtable/libpointing/armadillo: remove frisson maintainer per request of frisson closes https://trac.macports.org/ticket/53115 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 15:56:42 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 15:56:42 -0000 Subject: [MacPorts] #53115: argtable armadillo libpointing : Remove maintainer In-Reply-To: <053.42672d0e8653539f8a48a55963b730b3@macports.org> References: <053.42672d0e8653539f8a48a55963b730b3@macports.org> Message-ID: <068.d86dc555f9a252b5ae8d72df662b6a5e@macports.org> #53115: argtable armadillo libpointing : Remove maintainer ---------------------------------------------+---------------------------- Reporter: ChristianFrisson | Owner: kurthindenburg Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: argtable armadillo libpointing | ---------------------------------------------+---------------------------- Comment (by ChristianFrisson): Thanks! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 18:01:39 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 18:01:39 -0000 Subject: [MacPorts] #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X Message-ID: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X ---------------------------+------------------- Reporter: ballapete | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: tiger powerpc | Port: libuv ---------------------------+------------------- `src/unix/fs.c` uses unknown struct members, dst->st_birthtim.tv_sec and dst->st_birthtim.tv_nsec, and `src/unix/tty.c` uses an unknown macro TIOCPTYGNAME. These and can easily be fixed with the provided patch files. `src/unix/fsevents.c` is a bit harder to fix. It includes /System/Library/Frameworks/CoreServices.framework/Frameworks/OSServices.framework/Headers/OpenTransportProviders.h, which has {{{ /* TCP Level Options*/ enum { TCP_NODELAY = 0x01, TCP_MAXSEG = 0x02, TCP_NOTIFY_THRESHOLD = 0x10, /** not a real XTI option */ TCP_ABORT_THRESHOLD = 0x11, /** not a real XTI option */ TCP_CONN_NOTIFY_THRESHOLD = 0x12, /** not a real XTI option */ TCP_CONN_ABORT_THRESHOLD = 0x13, /** not a real XTI option */ TCP_OOBINLINE = 0x14, /** not a real XTI option */ TCP_URGENT_PTR_TYPE = 0x15, /** not a real XTI option */ TCP_KEEPALIVE = 0x0008 /* keepalive defined in OpenTransport.h */ }; }}} The C pre-processor generates {{{ enum { 0x01 = 0x01, 0x02 = 0x02, TCP_NOTIFY_THRESHOLD = 0x10, TCP_ABORT_THRESHOLD = 0x11, TCP_CONN_NOTIFY_THRESHOLD = 0x12, TCP_CONN_ABORT_THRESHOLD = 0x13, TCP_OOBINLINE = 0x14, TCP_URGENT_PTR_TYPE = 0x15, 0x10 = 0x0008 }; }}} which of course leads to an error: {{{ In /System/Library/Frameworks/CoreServices.framework/Frameworks/OSServices.framework/Headers/OpenTransportProviders.h:108: error: expected identifier before numeric constant }}} The reason for is presumingly /usr/include/netinet/tcp.h: {{{ #ifndef _NETINET_TCP_H_ #define _NETINET_TCP_H_ . . . /* * User-settable options (used with setsockopt). */ #define TCP_NODELAY 0x01 /* don't delay send to coalesce packets */ #ifndef _POSIX_C_SOURCE #define TCP_MAXSEG 0x02 /* set maximum segment size */ #define TCP_NOPUSH 0x04 /* don't push last block of write */ #define TCP_NOOPT 0x08 /* don't use TCP options */ #define TCP_KEEPALIVE 0x10 /* idle time used when SO_KEEPALIVE is enabled */ #endif /* _POSIX_C_SOURCE */ #endif }}} For this I cannot imagine a fix… -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 18:02:41 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 18:02:41 -0000 Subject: [MacPorts] #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X In-Reply-To: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> References: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> Message-ID: <061.0a9db79923736b471069d5f91893116d@macports.org> #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X ------------------------+--------------------------- Reporter: ballapete | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: tiger powerpc Port: libuv | ------------------------+--------------------------- Changes (by ballapete): * Attachment "main1.log" added. main.log with st_birthtim.tv error -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 18:04:09 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 18:04:09 -0000 Subject: [MacPorts] #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X In-Reply-To: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> References: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> Message-ID: <061.436f9165f502aac26225c45cb6818d9b@macports.org> #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X ------------------------+--------------------------- Reporter: ballapete | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: tiger powerpc Port: libuv | ------------------------+--------------------------- Changes (by ballapete): * Attachment "main3.log" added. main.log with the enum bug -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 18:05:22 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 18:05:22 -0000 Subject: [MacPorts] #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X In-Reply-To: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> References: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> Message-ID: <061.4f1ea2a89e6c39c1565062330a3ab731@macports.org> #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X ------------------------+--------------------------- Reporter: ballapete | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: tiger powerpc Port: libuv | ------------------------+--------------------------- Changes (by ballapete): * Attachment "st_birthtim.tv.patch" added. Patch to delete st_birthtim.tv_* -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 18:05:57 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 18:05:57 -0000 Subject: [MacPorts] #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X In-Reply-To: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> References: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> Message-ID: <061.cf2d143cacede9a9bd84450327c7480b@macports.org> #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X ------------------------+--------------------------- Reporter: ballapete | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: tiger powerpc Port: libuv | ------------------------+--------------------------- Changes (by ballapete): * Attachment "tty_TIOCGPTN.patch" added. Patch to delete TIOCPTYGNAME -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 18:46:45 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 18:46:45 -0000 Subject: [MacPorts] #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X In-Reply-To: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> References: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> Message-ID: <061.cda9e7419dd3ef3f19d7fb40fc4501b4@macports.org> #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X ------------------------+--------------------------- Reporter: ballapete | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: tiger powerpc Port: libuv | ------------------------+--------------------------- Changes (by mf2k): * owner: => raimue * cc: michaelld (added) * status: new => assigned Comment: In the future, please Cc the port maintainers ({{{port info --maintainers libuv}}}), if any. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 18:47:59 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 18:47:59 -0000 Subject: [MacPorts] #53141: python36 @3.6.0rc2: update to 3.6.0 In-Reply-To: <041.cb4ea61559968984e1e3ce111be272eb@macports.org> References: <041.cb4ea61559968984e1e3ce111be272eb@macports.org> Message-ID: <056.f0019317a06b53c62e9cbd94ea406195@macports.org> #53141: python36 @3.6.0rc2: update to 3.6.0 -----------------------+---------------------------- Reporter: l2dy | Owner: jyrkiwahlstedt Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: python36 | -----------------------+---------------------------- Changes (by jyrkiwahlstedt): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"b900cd5d5ff8393cf32f854939535eea310b2184/macports-ports" b900cd5d/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="b900cd5d5ff8393cf32f854939535eea310b2184" python36: version bump to 3.6.0, first release Closes: https://trac.macports.org/ticket/53141 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 19:10:28 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 19:10:28 -0000 Subject: [MacPorts] #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X In-Reply-To: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> References: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> Message-ID: <061.88f15a28a448be31b9d2c3683ea75bab@macports.org> #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X ------------------------+--------------------------- Reporter: ballapete | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: tiger powerpc Port: libuv | ------------------------+--------------------------- Comment (by ballapete): Replying to [comment:1 mf2k]: > In the future, please Cc the port maintainers ({{{port info --maintainers libuv}}}), if any. This was my first try *not* to add the maintainer(s), since I've seen so often that my additions were removed later. And the look, which is not available in Tiger, does not have a maintainer field, just a watcher (?) field. And I learned that I have to my own name there when I want to receive eMails about thing that happen to my report. OK, I'll continue adding watchers! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 21:16:56 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 21:16:56 -0000 Subject: [MacPorts] #52078: iTerm2 @3.0.5_0: pasting with the mouse between tabs does not work (anymore) In-Reply-To: <062.7038fee47b689585c64a9af194d6eab3@macports.org> References: <062.7038fee47b689585c64a9af194d6eab3@macports.org> Message-ID: <077.015bf99ba19dafaee776452ec78165df@macports.org> #52078: iTerm2 @3.0.5_0: pasting with the mouse between tabs does not work (anymore) --------------------------------+---------------------- Reporter: graziosi.angelo@… | Owner: markemer Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: iTerm2 | --------------------------------+---------------------- Comment (by markemer): After discussion I think this should be closed as an upstream bug. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 21:23:54 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 21:23:54 -0000 Subject: [MacPorts] #53144: libmacho @895 fails to build because GCC is not universal variant Message-ID: <046.367079c58979ee177ea68524b2ea0c15@macports.org> #53144: libmacho @895 fails to build because GCC is not universal variant ------------------------------+---------------------- Reporter: ballapete | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: tiger, universal | Port: libmacho ------------------------------+---------------------- That's my assumption… Installed are {{{ apple-gcc42 @5666.3_15+gpl3 (active) libmacho @886_0 (active) }}} Their variants are {{{ apple-gcc42 has the variants: bootstrap: Variant to break a dependency cycle on Tiger by first building an apple-gcc42 using host ld and cctools gpl3: Merge in changes from gcc-4.2.4 universal: Build for multiple architectures libmacho has the variants: [+]universal: Build for multiple architectures }}} The error is: {{{ :info:build gcc-apple-4.2: error trying to exec '/opt/local/bin/i686 -apple-darwin8-gcc-apple-4.2.4': execvp: No such file or directory }}} `opt/local/bin/i686-apple-darwin8-gcc-apple-4.2.4` exists on my Leopard system… -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 04:48:49 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 04:48:49 -0000 Subject: [MacPorts] #53145: zsh @5.2: update to 5.3.1 Message-ID: <041.fb42acc760d9cef456621d827ce5a041@macports.org> #53145: zsh @5.2: update to 5.3.1 --------------------+----------------- Reporter: l2dy | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: zsh --------------------+----------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 04:48:51 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 04:48:51 -0000 Subject: [MacPorts] #53146: GQRX Install with Mac Ports No Toolbar Icons Message-ID: <046.617d24fd37f5fe18495547f3f928a744@macports.org> #53146: GQRX Install with Mac Ports No Toolbar Icons -----------------------+------------------- Reporter: DANAVE3DS | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: GQXR | Port: GQRX -----------------------+------------------- during install, this package qt5-qtsvg package is NOT installed leading to missing icons. This dependency should be implemented for the Sierra and El Capitan versions of GQRX for 2.5 and 2.6 and all later. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 08:18:00 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 08:18:00 -0000 Subject: [MacPorts] #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X In-Reply-To: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> References: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> Message-ID: <061.e636091d93810347923f4140c4ade0bc@macports.org> #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X ------------------------+--------------------------- Reporter: ballapete | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: tiger powerpc Port: libuv | ------------------------+--------------------------- Comment (by kencu): Although you are completely correct in pointing out the libuv @1.10.1 does not build on Tiger (at least at this moment -- these things usually have a way of working out in the end), I might guess that the reason you now need libuv is because of the change in cmake-3.7.1; the portfile now specifies the system-library versions of most libraries, one of which is libuv. Cmake also includes it's own versions of the needed system libraries, however, and these internal versions still build on Tiger (go figure). So one way around your libuv issue is to edit the cmake portflle, remove the requirement for libuv by commenting it out like this: {{{ #depends_lib-append path:lib/pkgconfig/libuv.pc:libuv }}} and change the following configure arguments from this: {{{ --init=${worksrcpath}/macports.cmake \ --system-libs \ --no-system-jsoncpp }}} to this {{{ --init=${worksrcpath}/macports.cmake }}} then, when upgrading cmake, the system libuv is not required, and cmake 3.7.1 builds through to completion on Tiger without trouble. {{{ $ port -v installed | grep cmake cmake @3.6.3_0 platform='darwin 8' archs='ppc' cmake @3.7.1_0 (active) platform='darwin 8' archs='ppc' }}} if you actually needed libuv for some other reason besides cmake - well, obviously this won't help you. K. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 08:53:40 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 08:53:40 -0000 Subject: [MacPorts] #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X In-Reply-To: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> References: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> Message-ID: <061.cc0d1ab8bbc450d617c61fae6b2bc6e3@macports.org> #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X ------------------------+--------------------------- Reporter: ballapete | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: tiger powerpc Port: libuv | ------------------------+--------------------------- Comment (by ballapete): Replying to [comment:3 kencu]: > So one way around your libuv issue is to edit the cmake portflle, remove the requirement for libuv by commenting it out like this: Presumingly next week I can try… Now GCC6 is building – for days! > if you actually needed libuv for some other reason besides cmake - well, obviously this won't help you. K. For decades (1¼?) I could live on Tiger without libuv. I am willing to continue… Thanks for the information! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 09:21:45 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 09:21:45 -0000 Subject: [MacPorts] #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies In-Reply-To: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> References: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> Message-ID: <075.a8eb8e52ecfdcb3fd10a7ce6648ab8a6@macports.org> #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies -------------------------------------------------+------------------------- Reporter: maxkalashnikov-macports | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: duplicate | Keywords: Port: clang-3.3 clang-3.4 clang-3.5 | clang-3.6 clang-3.7 clang-3.8 clang-3.9 | -------------------------------------------------+------------------------- Changes (by jeremyhu): * status: assigned => closed * resolution: => duplicate Comment: Why do you need clang-3.3 on Montain Lion. It basically exists for Leopard. As for the circular dependencies, that's fixed already. See #53110 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 09:31:00 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 09:31:00 -0000 Subject: [MacPorts] #53144: libmacho @895 fails to build because GCC is not universal variant In-Reply-To: <046.367079c58979ee177ea68524b2ea0c15@macports.org> References: <046.367079c58979ee177ea68524b2ea0c15@macports.org> Message-ID: <061.72226a25df8cf0f634ea358339ffffbd@macports.org> #53144: libmacho @895 fails to build because GCC is not universal variant ------------------------+------------------------------ Reporter: ballapete | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: tiger, universal Port: libmacho | ------------------------+------------------------------ Changes (by jeremyhu): * owner: => jeremyhu * status: new => closed * resolution: => fixed Comment: In [changeset:"41e0ae1cf32e0a3d86283818c27e83e06fc8a853/macports-ports" 41e0ae1c/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="41e0ae1cf32e0a3d86283818c27e83e06fc8a853" {apple,llvm}-gcc42: Default to +universal The build system basically conflates CHOST and CTARGET. This is the simplest fix, and given the very deprecated nature of these ports, it's not worth a deeper fix. Fixes https://trac.macports.org/ticket/53144 Signed-off-by: Jeremy Huddleston Sequoia }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 09:45:27 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 09:45:27 -0000 Subject: [MacPorts] #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies In-Reply-To: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> References: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> Message-ID: <075.480b64eb07cd88f38fb03c2377d17e54@macports.org> #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies -------------------------------------------------+------------------------- Reporter: maxkalashnikov-macports | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: duplicate | Keywords: Port: clang-3.3 clang-3.4 clang-3.5 | clang-3.6 clang-3.7 clang-3.8 clang-3.9 | -------------------------------------------------+------------------------- Comment (by maxkalashnikov-macports): I don't need any particular version. I used its debug output because it had the fewest lines of the 7. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 10:29:14 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 10:29:14 -0000 Subject: [MacPorts] #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies In-Reply-To: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> References: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> Message-ID: <075.f8ba8b8941d8c5dacff4c3cf0042b792@macports.org> #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies -------------------------------------------------+------------------------- Reporter: maxkalashnikov-macports | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: duplicate | Keywords: Port: clang-3.3 clang-3.4 clang-3.5 | clang-3.6 clang-3.7 clang-3.8 clang-3.9 | -------------------------------------------------+------------------------- Comment (by maxkalashnikov-macports): Replying to [comment:2 jeremyhu]: > Why do you need clang-3.3 on Montain Lion. It basically exists for Leopard. I don't need any particular version. I used its debug output because it had the fewest lines of the 7. > As for the circular dependencies, that's fixed already. See #53110 I don't see how that would fix this issue, since that appears to be a change to the `libomp` port, of which I already have the latest version installed, not any of the `clang` (or `llvm`) ports nor `cctools` or `ld64`, which are what appear in the error message I receive. Trying to install `cctools`, I get: {{{ Error: The following dependencies were not installed: llvm-3.9 clang-3.8 cctools clang-3.7 ld64 ld64-latest llvm-3.8 }}} So maybe that's the port with circular dependency, since it seems to depend on itself. Should I open another ticket against it, instead? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 10:29:25 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 10:29:25 -0000 Subject: [MacPorts] #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies In-Reply-To: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> References: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> Message-ID: <075.48f77843af7fd4ded4e06579dbe86feb@macports.org> #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies -------------------------------------------------+------------------------- Reporter: maxkalashnikov-macports | Owner: jeremyhu Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: clang-3.3 clang-3.4 clang-3.5 | clang-3.6 clang-3.7 clang-3.8 clang-3.9 | -------------------------------------------------+------------------------- Changes (by maxkalashnikov-macports): * status: closed => reopened * resolution: duplicate => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 10:32:24 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 10:32:24 -0000 Subject: [MacPorts] #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies In-Reply-To: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> References: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> Message-ID: <075.1da9286ec22bff3a052f7dd68513b812@macports.org> #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies -------------------------------------------------+------------------------- Reporter: maxkalashnikov-macports | Owner: jeremyhu Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: clang-3.3 clang-3.4 clang-3.5 | clang-3.6 clang-3.7 clang-3.8 clang-3.9 | -------------------------------------------------+------------------------- Changes (by maxkalashnikov-macports): * Attachment "mp-cctools-debug" added. port -d install cctools -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 14:12:33 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 14:12:33 -0000 Subject: [MacPorts] #53122: gpgme : upgrade to 1.8.0 and +qt5 variant In-Reply-To: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> References: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> Message-ID: <056.496a73a978421c3bf89052e8d633fb1d@macports.org> #53122: gpgme : upgrade to 1.8.0 and +qt5 variant ---------------------+------------------------------- Reporter: RJVB | Owner: dbevans Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch upstream Port: gpgme | ---------------------+------------------------------- Changes (by dbevans): * status: new => closed * owner: => dbevans * resolution: => fixed Comment: In [changeset:"175d12d1e54d68bed4c93855dfeb3b0099e12797/macports-ports" 175d12d/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="175d12d1e54d68bed4c93855dfeb3b0099e12797" gpgme: update to version 1.8.0 Fix C, C++ build issues. Qt bindings to be handled in a separate port. Remove outdated Id tag line. Closes: https://trac.macports.org/ticket/53122 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 14:28:56 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 14:28:56 -0000 Subject: [MacPorts] #51668: texlive-texdist: new port In-Reply-To: <044.23afc3670fb54ae1779114e944c5da6a@macports.org> References: <044.23afc3670fb54ae1779114e944c5da6a@macports.org> Message-ID: <059.551a625c93ebb0ae59f5867102ffdedf@macports.org> #51668: texlive-texdist: new port ------------------------------+-------------------------------- Reporter: dliessi | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: texlive-texdist | ------------------------------+-------------------------------- Comment (by dliessi): The `texdist` script determines if a TeX distribution is usable by checking if `Contents/Programs/$arch/tex` exists, where `$arch` is the output of `uname -p`. So at least that symlink is needed, besides the `texbin` one. I could cheat and provide only the `$arch` and `texbin` symlinks: this would not provide the complete picture in the universal case, and it would provide wrong symlinks where `uname -p` does not correspond to the actual architecture (e.g. on my machine it outputs `i386`, while `texlive-bin` installs `x86_64`), but at least existing symlinks would not point to a different architecture family (PowerPC vs Intel). The ideal situation would be to provide the following symlinks, besides `texbin`: - 32-bit Intel: `i386` - 64-bit Intel: `i386`, `x86_64` - 32-bit or PowerPC: `ppc`, `powerpc` - universal: the correct combination of the above I can determine the installed architecture, if not universal, from the directory name in `${texlive_mactex_texdistdir}` and manually fix the 64-bit Intel case, but this does not work for the universal case. Is there a simple way to determine which architectures were installed in the universal case? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 08:58:52 2016 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2016 08:58:52 -0000 Subject: [MacPorts] #46351: py-wxpython-2.8: track the progress of transition to 3.0 and try to remove the port In-Reply-To: <042.f0ed2e26f5d209831f6dd20cfb9dec9f@macports.org> References: <042.f0ed2e26f5d209831f6dd20cfb9dec9f@macports.org> Message-ID: <057.ea0372da080604c8fca58254a6a15cc6@macports.org> #46351: py-wxpython-2.8: track the progress of transition to 3.0 and try to remove the port -------------------------------------------------+------------------------- Reporter: mojca | Owner: macports- | tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: grass, py-dsv, py-pyface, py- | robotframework-ride, py-wxpython-2.8 | -------------------------------------------------+------------------------- Changes (by mojca): * cc: Veence (added) Comment: Vincent, I'm adding you to CC, hoping that you could help us get rid of wxPython 2.8 in grass (removal of grass 6 is also a valid option :). I guess I'll simply remove DSV and keep hoping that a new release of robotframework-ride comes out soonish. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 15:44:43 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 15:44:43 -0000 Subject: [MacPorts] #53122: gpgme : upgrade to 1.8.0 and +qt5 variant In-Reply-To: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> References: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> Message-ID: <056.0c3c0f78947a34cdc3db4ca1bbf501b9@macports.org> #53122: gpgme : upgrade to 1.8.0 and +qt5 variant ---------------------+------------------------------- Reporter: RJVB | Owner: dbevans Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch upstream Port: gpgme | ---------------------+------------------------------- Comment (by RJVB): One remark w.r.t. one of the comments: gpgme only supports Qt5 from what I can see. So the question of co-existence of support for different Qt versions is moot. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 16:39:32 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 16:39:32 -0000 Subject: [MacPorts] #53147: python27 @2.7.13 fetch failed on osx 10.5 Message-ID: <046.aad5174b29074eccba1dcb7a3fe1ccba@macports.org> #53147: python27 @2.7.13 fetch failed on osx 10.5 -----------------------+---------------------- Reporter: pkoshevoy | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: leopard | Port: python27 -----------------------+---------------------- running `sudo port selfupdate && sudo port upgrade outdated` eventually fails on osx 10.5 (both intel and ppc): {{{ ---> Computing dependencies for python27 ---> Fetching distfiles for python27 ---> Attempting to fetch Python-2.7.13.tar.xz from http://www.python.org/ftp/python/2.7.13/ ---> Attempting to fetch Python-2.7.13.tar.xz from http://distfiles.macports.org/python27 ---> Attempting to fetch Python-2.7.13.tar.xz from http://sea.us.distfiles.macports.org/macports/distfiles/python27 ---> Attempting to fetch Python-2.7.13.tar.xz from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/python27 ---> Attempting to fetch Python-2.7.13.tar.xz from http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/python27 ---> Attempting to fetch Python-2.7.13.tar.xz from http://lil.fr.distfiles.macports.org/python27 ---> Attempting to fetch Python-2.7.13.tar.xz from http://cjj.kr.distfiles.macports.org/python27 ---> Attempting to fetch Python-2.7.13.tar.xz from http://nue.de.distfiles.macports.org/python27 ---> Attempting to fetch Python-2.7.13.tar.xz from http://osl.no.distfiles.macports.org/python27 ---> Attempting to fetch Python-2.7.13.tar.xz from http://pek.cn.distfiles.macports.org/macports/distfiles/python27 ---> Attempting to fetch Python-2.7.13.tar.xz from http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/python27 ---> Attempting to fetch Python-2.7.13.tar.xz from http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/python27 ---> Attempting to fetch Python-2.7.13.tar.xz from http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/python27 ---> Attempting to fetch Python-2.7.13.tar.xz from http://jog.id.distfiles.macports.org/macports/distfiles/python27 ---> Attempting to fetch Python-2.7.13.tar.xz from http://jnb.za.distfiles.macports.org/distfiles/python27 ---> Attempting to fetch Python-2.7.13.tar.xz from http://her.gr.distfiles.macports.org/python27 Error: org.macports.fetch for port python27 returned: fetch failed }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 16:54:07 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 16:54:07 -0000 Subject: [MacPorts] #53147: python27 @2.7.13 fetch failed on osx 10.5 In-Reply-To: <046.aad5174b29074eccba1dcb7a3fe1ccba@macports.org> References: <046.aad5174b29074eccba1dcb7a3fe1ccba@macports.org> Message-ID: <061.aaaa4df3750557771ac77354e95591eb@macports.org> #53147: python27 @2.7.13 fetch failed on osx 10.5 ------------------------+--------------------- Reporter: pkoshevoy | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: duplicate | Keywords: leopard Port: python27 | ------------------------+--------------------- Changes (by ryandesign): * status: new => closed * resolution: => duplicate Comment: Fetch failures due to https on 10.5 are well-known and will be resolved once we are properly mirroring distfiles on our own http server again. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 16:55:53 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 16:55:53 -0000 Subject: [MacPorts] #53127: (10.5.8PPC) Osxfuse - Fetch failed In-Reply-To: <044.50bcf03fed00657f19e635ea522c0cae@macports.org> References: <044.50bcf03fed00657f19e635ea522c0cae@macports.org> Message-ID: <059.c13e36986f7f22115d77e89cb88f6e9f@macports.org> #53127: (10.5.8PPC) Osxfuse - Fetch failed ------------------------+--------------------- Reporter: mrkapqa | Owner: drkp Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: duplicate | Keywords: leopard Port: osxfuse | ------------------------+--------------------- Changes (by ryandesign): * status: assigned => closed * resolution: => duplicate Comment: Fetch failures due to https on 10.5 are well-known and will be resolved once we are properly mirroring distfiles on our own http server again. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 16:57:09 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 16:57:09 -0000 Subject: [MacPorts] #53148: cairo @1.14.8+quartz: fetch failed on osx 10.5 Message-ID: <046.eb604c0535526e9a0475896323d07291@macports.org> #53148: cairo @1.14.8+quartz: fetch failed on osx 10.5 -----------------------+------------------- Reporter: pkoshevoy | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: leopard | Port: cairo -----------------------+------------------- Running `sudo port upgrade harfbuzz` on osx 10.5 ppc eventually fails due to failure to fetch cairo: {{{ ---> Computing dependencies for cairo ---> Fetching distfiles for cairo ---> Attempting to fetch cairo-1.14.8.tar.xz from http://distfiles.macports.org/cairo ---> Attempting to fetch cairo-1.14.8.tar.xz from http://cairographics.org/releases/ ---> Attempting to fetch cairo-1.14.8.tar.xz from http://sea.us.distfiles.macports.org/macports/distfiles/cairo ---> Attempting to fetch cairo-1.14.8.tar.xz from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/cairo ---> Attempting to fetch cairo-1.14.8.tar.xz from http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/cairo ---> Attempting to fetch cairo-1.14.8.tar.xz from http://lil.fr.distfiles.macports.org/cairo ---> Attempting to fetch cairo-1.14.8.tar.xz from http://cjj.kr.distfiles.macports.org/cairo ---> Attempting to fetch cairo-1.14.8.tar.xz from http://nue.de.distfiles.macports.org/cairo ---> Attempting to fetch cairo-1.14.8.tar.xz from http://osl.no.distfiles.macports.org/cairo ---> Attempting to fetch cairo-1.14.8.tar.xz from http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/cairo ---> Attempting to fetch cairo-1.14.8.tar.xz from http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/cairo ---> Attempting to fetch cairo-1.14.8.tar.xz from http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/cairo ---> Attempting to fetch cairo-1.14.8.tar.xz from http://jog.id.distfiles.macports.org/macports/distfiles/cairo ---> Attempting to fetch cairo-1.14.8.tar.xz from http://pek.cn.distfiles.macports.org/macports/distfiles/cairo ---> Attempting to fetch cairo-1.14.8.tar.xz from http://jnb.za.distfiles.macports.org/distfiles/cairo ---> Attempting to fetch cairo-1.14.8.tar.xz from http://her.gr.distfiles.macports.org/cairo Error: org.macports.fetch for port cairo returned: fetch failed }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 16:57:47 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 16:57:47 -0000 Subject: [MacPorts] #53148: cairo @1.14.8+quartz: fetch failed on osx 10.5 In-Reply-To: <046.eb604c0535526e9a0475896323d07291@macports.org> References: <046.eb604c0535526e9a0475896323d07291@macports.org> Message-ID: <061.e41216882748526e5d765753d355e299@macports.org> #53148: cairo @1.14.8+quartz: fetch failed on osx 10.5 ------------------------+--------------------- Reporter: pkoshevoy | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: duplicate | Keywords: leopard Port: cairo | ------------------------+--------------------- Changes (by ryandesign): * status: new => closed * resolution: => duplicate Comment: Fetch failures due to https on 10.5 are well-known and will be resolved once we are properly mirroring distfiles on our own http server again. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 16:58:17 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 16:58:17 -0000 Subject: [MacPorts] #53129: (10.5.8PPC) CCTools - Fetch Failes In-Reply-To: <044.ba00bff09faf7c49f492b9618c3bcc1f@macports.org> References: <044.ba00bff09faf7c49f492b9618c3bcc1f@macports.org> Message-ID: <059.127c1edfc357962bac7cec163f91d75a@macports.org> #53129: (10.5.8PPC) CCTools - Fetch Failes -------------------------+---------------------- Reporter: mrkapqa | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: worksforme | Keywords: leopard Port: cctools | -------------------------+---------------------- Comment (by ryandesign): Fetch failures due to https on 10.5 are well-known and will be resolved once we are properly mirroring distfiles on our own http server again. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 17:01:07 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 17:01:07 -0000 Subject: [MacPorts] #53149: wine-crossover: update to 16.0.0 Message-ID: <047.f24374f560f43ababd9417a5cfe6c90d@macports.org> #53149: wine-crossover: update to 16.0.0 ------------------------+---------------------------- Reporter: ryandesign | Owner: jeremyhu Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: wine-crossover ------------------------+---------------------------- Here is a patch to update wine-crossover to 16.0.0 and backport relevant changes from wine-devel. It should not be committed yet because it does not build: {{{ Undefined symbols for architecture i386: "_MIN", referenced from: _bitmap_info_size in clipboard.o }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 17:01:29 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 17:01:29 -0000 Subject: [MacPorts] #53149: wine-crossover: update to 16.0.0 In-Reply-To: <047.f24374f560f43ababd9417a5cfe6c90d@macports.org> References: <047.f24374f560f43ababd9417a5cfe6c90d@macports.org> Message-ID: <062.36d7b278893b0bba8da1ccd9c6dcf7ae@macports.org> #53149: wine-crossover: update to 16.0.0 -----------------------------+---------------------- Reporter: ryandesign | Owner: jeremyhu Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: wine-crossover | -----------------------------+---------------------- Changes (by ryandesign): * Attachment "wine-crossover-16.0.0.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 17:03:13 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 17:03:13 -0000 Subject: [MacPorts] #53146: GQRX Install with Mac Ports No Toolbar Icons In-Reply-To: <046.617d24fd37f5fe18495547f3f928a744@macports.org> References: <046.617d24fd37f5fe18495547f3f928a744@macports.org> Message-ID: <061.50cd7316ee851dbfc950b8ef2bb79451@macports.org> #53146: GQRX Install with Mac Ports No Toolbar Icons ------------------------+----------------------- Reporter: DANAVE3DS | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: gqrx | ------------------------+----------------------- Changes (by ryandesign): * owner: => michaelld * status: new => assigned * port: GQRX => gqrx * keywords: GQXR => Comment: Why only on El Capitan and later? Why not on Yosemite and earlier? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 17:24:57 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 17:24:57 -0000 Subject: [MacPorts] #53150: llvm ld: unknown option: -export_dynamic Message-ID: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> #53150: llvm ld: unknown option: -export_dynamic ---------------------+----------------- Reporter: gbrtrac | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: ---------------------+----------------- There is an unknown linker flag being used in the building of llvm :info:build /opt/local/bin/clang++-mp-3.7 -pipe -Os -std=c++11 -stdlib=libc++ -fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused- parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wcovered-switch-default -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -std=c++11 -DNDEBUG -arch x86_64 -mmacosx- version-min=10.9 -Wl,-search_paths_first -Wl,-headerpad_max_install_names -L/opt/local/lib -Wl,-headerpad_max_install_names -rdynamic CMakeFiles/bugpoint.dir/BugDriver.cpp.o CMakeFiles/bugpoint.dir/CrashDebugger.cpp.o CMakeFiles/bugpoint.dir/ExecutionDriver.cpp.o CMakeFiles/bugpoint.dir/ExtractFunction.cpp.o CMakeFiles/bugpoint.dir/FindBugs.cpp.o CMakeFiles/bugpoint.dir/Miscompilation.cpp.o CMakeFiles/bugpoint.dir/OptimizerDriver.cpp.o CMakeFiles/bugpoint.dir/ToolRunner.cpp.o CMakeFiles/bugpoint.dir/bugpoint.cpp.o -o ../../bin/bugpoint -Wl,-rpath,/opt/local/libexec/llvm-3.8/lib ../../lib/libLLVM.dylib :info:build ld: unknown option: -export_dynamic -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 17:38:13 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 17:38:13 -0000 Subject: [MacPorts] #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic (was: llvm ld: unknown option: -export_dynamic) In-Reply-To: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> References: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> Message-ID: <059.b2bcbaea5d0e603bfe425c062f4cf567@macports.org> #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic -----------------------+---------------------- Reporter: gbrtrac | Owner: jeremyhu Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: llvm-3.8 | -----------------------+---------------------- Changes (by ryandesign): * status: new => assigned * owner: => jeremyhu * port: => llvm-3.8 Old description: > There is an unknown linker flag being used in the building of llvm > > :info:build /opt/local/bin/clang++-mp-3.7 -pipe -Os -std=c++11 > -stdlib=libc++ -fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused- > parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers > -pedantic -Wno-long-long -Wcovered-switch-default -Wnon-virtual-dtor > -Wdelete-non-virtual-dtor -std=c++11 -DNDEBUG -arch x86_64 -mmacosx- > version-min=10.9 -Wl,-search_paths_first -Wl,-headerpad_max_install_names > -L/opt/local/lib -Wl,-headerpad_max_install_names -rdynamic > CMakeFiles/bugpoint.dir/BugDriver.cpp.o > CMakeFiles/bugpoint.dir/CrashDebugger.cpp.o > CMakeFiles/bugpoint.dir/ExecutionDriver.cpp.o > CMakeFiles/bugpoint.dir/ExtractFunction.cpp.o > CMakeFiles/bugpoint.dir/FindBugs.cpp.o > CMakeFiles/bugpoint.dir/Miscompilation.cpp.o > CMakeFiles/bugpoint.dir/OptimizerDriver.cpp.o > CMakeFiles/bugpoint.dir/ToolRunner.cpp.o > CMakeFiles/bugpoint.dir/bugpoint.cpp.o -o ../../bin/bugpoint > -Wl,-rpath,/opt/local/libexec/llvm-3.8/lib ../../lib/libLLVM.dylib > :info:build ld: unknown option: -export_dynamic New description: There is an unknown linker flag being used in the building of llvm {{{ :info:build /opt/local/bin/clang++-mp-3.7 -pipe -Os -std=c++11 -stdlib=libc++ -fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused- parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wcovered-switch-default -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -std=c++11 -DNDEBUG -arch x86_64 -mmacosx- version-min=10.9 -Wl,-search_paths_first -Wl,-headerpad_max_install_names -L/opt/local/lib -Wl,-headerpad_max_install_names -rdynamic CMakeFiles/bugpoint.dir/BugDriver.cpp.o CMakeFiles/bugpoint.dir/CrashDebugger.cpp.o CMakeFiles/bugpoint.dir/ExecutionDriver.cpp.o CMakeFiles/bugpoint.dir/ExtractFunction.cpp.o CMakeFiles/bugpoint.dir/FindBugs.cpp.o CMakeFiles/bugpoint.dir/Miscompilation.cpp.o CMakeFiles/bugpoint.dir/OptimizerDriver.cpp.o CMakeFiles/bugpoint.dir/ToolRunner.cpp.o CMakeFiles/bugpoint.dir/bugpoint.cpp.o -o ../../bin/bugpoint -Wl,-rpath,/opt/local/libexec/llvm-3.8/lib ../../lib/libLLVM.dylib :info:build ld: unknown option: -export_dynamic }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 17:43:56 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 17:43:56 -0000 Subject: [MacPorts] #53151: ld64-latest: handeling tbd files Message-ID: <056.29f019982176bcf6547cbdbe183768d5@macports.org> #53151: ld64-latest: handeling tbd files ---------------------------------+------------------------- Reporter: MarcusCalhoun-Lopez | Owner: jeremyhu@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: ld64-latest ---------------------------------+------------------------- I am currently trying to get Qt to use MacPorts clang instead of Xcode clang so as to hopefully support older OSs for longer..[[BR]] The linker, however, does not seem to be able to handle [http://stackoverflow.com/questions/31450690/why-xcode-7-shows-tbd- instead-of-dylib tbd] files.[[BR]] For example, the following code fails: {{{ clang++-mp-3.9 -Wl,-syslibroot,/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk main.cxx }}} with the error {{{ ld: unexpected token: !tapi-tbd-v2 file '/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/lib/libc++.tbd' for architecture x86_64 }}} I have been able to workaround the problem by removing {{{-syslibroot}}} from the linker. The more difficult problem is when the .tbd file and dylib file are in the same directory as in: {{{ clang++-mp-3.9 -F/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks -weak_framework XCTest main.cxx }}} which produces the error {{{ ld: unexpected token: !tapi-tbd-v2 file '/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks/XCTest.framework/XCTest.tbd' for architecture x86_64 }}} Any suggestions on a fix or workaround? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 18:32:16 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 18:32:16 -0000 Subject: [MacPorts] #52326: gmp @6.1.1: error: C++ compiler not available, see config.log for details In-Reply-To: <060.34c40255ad8e1bd7adef6f0c87d42e39@macports.org> References: <060.34c40255ad8e1bd7adef6f0c87d42e39@macports.org> Message-ID: <075.0f18093556b56c1a49bcb12b3edc44c8@macports.org> #52326: gmp @6.1.1: error: C++ compiler not available, see config.log for details ------------------------------+--------------------------------- Reporter: alexmartin715@… | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: invalid | Keywords: sierra Port: gmp | ------------------------------+--------------------------------- Changes (by MarcusCalhoun-Lopez): * status: new => closed * resolution: => invalid Comment: This error seems to be limited to specific machines, especially if reinstalling MacPorts fixed it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 18:33:29 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 18:33:29 -0000 Subject: [MacPorts] #51971: gmp stuck staging into Destroot In-Reply-To: <049.c2da29e61546029d544546781cdde2cd@macports.org> References: <049.c2da29e61546029d544546781cdde2cd@macports.org> Message-ID: <064.21d23e403340638fae17e30654da7e9e@macports.org> #51971: gmp stuck staging into Destroot -------------------------+--------------------------------- Reporter: rmahy@… | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: worksforme | Keywords: Port: gmp | -------------------------+--------------------------------- Changes (by MarcusCalhoun-Lopez): * status: new => closed * resolution: => worksforme Comment: I am sorry, but I have not been able to reproduce this error.[[BR]] The buildbots also seem to have no problem, so I do not see a way forward. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 18:50:08 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 18:50:08 -0000 Subject: [MacPorts] #53145: zsh @5.2: update to 5.3.1 In-Reply-To: <041.fb42acc760d9cef456621d827ce5a041@macports.org> References: <041.fb42acc760d9cef456621d827ce5a041@macports.org> Message-ID: <056.adde647c0b96da8e4d2ee8451fbb6fa1@macports.org> #53145: zsh @5.2: update to 5.3.1 ---------------------+---------------------- Reporter: l2dy | Owner: larryv Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: zsh | ---------------------+---------------------- Changes (by mf2k): * status: new => assigned * owner: => larryv * cc: larryv (removed) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 18:50:58 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 18:50:58 -0000 Subject: [MacPorts] #52078: iTerm2 @3.0.5_0: pasting with the mouse between tabs does not work (anymore) In-Reply-To: <062.7038fee47b689585c64a9af194d6eab3@macports.org> References: <062.7038fee47b689585c64a9af194d6eab3@macports.org> Message-ID: <077.6b6ee888406524e3a2b2eed17e9c53b9@macports.org> #52078: iTerm2 @3.0.5_0: pasting with the mouse between tabs does not work (anymore) --------------------------------+---------------------- Reporter: graziosi.angelo@… | Owner: markemer Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: wontfix | Keywords: Port: iTerm2 | --------------------------------+---------------------- Changes (by mf2k): * status: new => closed * resolution: => wontfix -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 18:53:30 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 18:53:30 -0000 Subject: [MacPorts] #52078: iTerm2 @3.0.5_0: pasting with the mouse between tabs does not work (anymore) In-Reply-To: <062.7038fee47b689585c64a9af194d6eab3@macports.org> References: <062.7038fee47b689585c64a9af194d6eab3@macports.org> Message-ID: <077.86ba091b0559a43904a3298da7d6d81d@macports.org> #52078: iTerm2 @3.0.5_0: pasting with the mouse between tabs does not work (anymore) --------------------------------+---------------------- Reporter: graziosi.angelo@… | Owner: markemer Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: wontfix | Keywords: Port: iTerm2 | --------------------------------+---------------------- Comment (by markemer): Turns out this was a configuration error, not a bug. Middle button single click needs to be set to "Paste from Selection" not "Paste from Clipboard" -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 19:06:34 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 19:06:34 -0000 Subject: [MacPorts] #53111: rsync: failed to connect to sea.us.rsync.macports.org: Operation timed out (60) In-Reply-To: <050.e95dfc8b93468f285f7e9c5c71f911fb@macports.org> References: <050.e95dfc8b93468f285f7e9c5c71f911fb@macports.org> Message-ID: <065.dd1685138011858ae91c00a6d2a9c255@macports.org> #53111: rsync: failed to connect to sea.us.rsync.macports.org: Operation timed out (60) ----------------------------+-------------------- Reporter: gaming-hacker | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.3.5 Resolution: worksforme | Keywords: Port: | ----------------------------+-------------------- Changes (by ryandesign): * status: new => closed * resolution: => worksforme -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 19:26:16 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 19:26:16 -0000 Subject: [MacPorts] #53146: GQRX Install with Mac Ports No Toolbar Icons In-Reply-To: <046.617d24fd37f5fe18495547f3f928a744@macports.org> References: <046.617d24fd37f5fe18495547f3f928a744@macports.org> Message-ID: <061.c16f9f68776ee447154d3642f98eb0dc@macports.org> #53146: GQRX Install with Mac Ports No Toolbar Icons ------------------------+----------------------- Reporter: DANAVE3DS | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: gqrx | ------------------------+----------------------- Comment (by michaelld): Are you saying that qt5-qtsvg should be a dependency for Gqrx (and gqrx- devel)? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 21:34:52 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 21:34:52 -0000 Subject: [MacPorts] #53122: gpgme : upgrade to 1.8.0 and +qt5 variant In-Reply-To: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> References: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> Message-ID: <056.11dc09da16b49dedacc897b4450e9753@macports.org> #53122: gpgme : upgrade to 1.8.0 and +qt5 variant ---------------------+------------------------------- Reporter: RJVB | Owner: dbevans Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch upstream Port: gpgme | ---------------------+------------------------------- Comment (by dbevans): Replying to [comment:14 RJVB]: > One remark w.r.t. one of the comments: gpgme only supports Qt5 from what I can see. So the question of co-existence of support for different Qt versions is moot. Yes, other than it dictates the installation paths. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 21:59:07 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 21:59:07 -0000 Subject: [MacPorts] #53122: gpgme : upgrade to 1.8.0 and +qt5 variant In-Reply-To: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> References: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> Message-ID: <056.8076228a406afa49b1194205273078ce@macports.org> #53122: gpgme : upgrade to 1.8.0 and +qt5 variant ---------------------+------------------------------- Reporter: RJVB | Owner: dbevans Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch upstream Port: gpgme | ---------------------+------------------------------- Comment (by RJVB): Doh, of course. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 23:28:05 2016 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2016 23:28:05 -0000 Subject: [MacPorts] #53144: libmacho @895 fails to build because GCC is not universal variant In-Reply-To: <046.367079c58979ee177ea68524b2ea0c15@macports.org> References: <046.367079c58979ee177ea68524b2ea0c15@macports.org> Message-ID: <061.d12962bc7bc7e36e73cf8ef466fd1917@macports.org> #53144: libmacho @895 fails to build because GCC is not universal variant ------------------------+------------------------------ Reporter: ballapete | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: tiger, universal Port: libmacho | ------------------------+------------------------------ Comment (by ballapete): Replying to [comment:1 jeremyhu]: > In [changeset:"41e0ae1cf32e0a3d86283818c27e83e06fc8a853/macports-ports" 41e0ae1c/macports-ports]: > {{{ > #!ConfigurableCommitTicketReference repository="macports-ports" revision="41e0ae1cf32e0a3d86283818c27e83e06fc8a853" > {apple,llvm}-gcc42: Default to +universal > > The build system basically conflates CHOST and CTARGET. This is > the simplest fix, and given the very deprecated nature of these > ports, it's not worth a deeper fix. What does that mean? I have no idea what a CHOST and a CTARGET could be… > > Fixes https://trac.macports.org/ticket/53144 > I seem to have a problem seeing the fix… -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 00:19:26 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 00:19:26 -0000 Subject: [MacPorts] #51668: texlive-texdist: new port In-Reply-To: <044.23afc3670fb54ae1779114e944c5da6a@macports.org> References: <044.23afc3670fb54ae1779114e944c5da6a@macports.org> Message-ID: <059.f3b12238ef1a4e12bb343c94ed136fca@macports.org> #51668: texlive-texdist: new port ------------------------------+-------------------------------- Reporter: dliessi | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: texlive-texdist | ------------------------------+-------------------------------- Comment (by mojca): Are you sure that the script checks for `uname -p`? That sounds stupid to me, but it's also true that it might not have seen any changes for years and nobody bothered. There might be one more thing. I'm almost sure that picking a different symlink won't have any effect if one builds universal binaries. This would probably only change the behaviour if we had a different set of, say, 32-bit binaries elsewhere. You may ask those who wrote the software or on one of the Mac-specific TUG mailing lists. For that reason it might be useless to set those other symlinks. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 00:42:45 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 00:42:45 -0000 Subject: [MacPorts] #53148: cairo @1.14.8+quartz: fetch failed on osx 10.5 In-Reply-To: <046.eb604c0535526e9a0475896323d07291@macports.org> References: <046.eb604c0535526e9a0475896323d07291@macports.org> Message-ID: <061.d954055ed9253759e2ba6a1d43db93bb@macports.org> #53148: cairo @1.14.8+quartz: fetch failed on osx 10.5 ------------------------+--------------------- Reporter: pkoshevoy | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: duplicate | Keywords: leopard Port: cairo | ------------------------+--------------------- Comment (by ryandesign): I added the cairo files to the distfiles mirror manually. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 01:28:49 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 01:28:49 -0000 Subject: [MacPorts] #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies In-Reply-To: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> References: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> Message-ID: <075.ce869f3728461bbe8a60253bf8eac4f3@macports.org> #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies -------------------------------------------------+------------------------- Reporter: maxkalashnikov-macports | Owner: jeremyhu Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: clang-3.3 clang-3.4 clang-3.5 | clang-3.6 clang-3.7 clang-3.8 clang-3.9 | -------------------------------------------------+------------------------- Comment (by jeremyhu): Ah. ld64-X depends on llvm39 (or llvm38), but your version of Xcode is too old to build llvm, so it tries to use the fallback (macports-clang-X.Y). That depends on ld64, and cycle. I suggest you install ld64 with the +ld64_xcode variant, then install clang-3.9, then deactivate and reinstall ld64 (with -ld64_xcode) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 01:46:30 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 01:46:30 -0000 Subject: [MacPorts] #53149: wine-crossover: update to 16.0.0 In-Reply-To: <047.f24374f560f43ababd9417a5cfe6c90d@macports.org> References: <047.f24374f560f43ababd9417a5cfe6c90d@macports.org> Message-ID: <062.5c73dee31bb882dcca52fe5a4c7b8239@macports.org> #53149: wine-crossover: update to 16.0.0 -----------------------------+---------------------- Reporter: ryandesign | Owner: jeremyhu Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: wine-crossover | -----------------------------+---------------------- Changes (by jeremyhu): * status: new => accepted -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 01:48:07 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 01:48:07 -0000 Subject: [MacPorts] #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic In-Reply-To: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> References: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> Message-ID: <059.16b64c95b88de0b8e63a0323fbb273a3@macports.org> #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic -----------------------+---------------------- Reporter: gbrtrac | Owner: jeremyhu Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: llvm-3.8 | -----------------------+---------------------- Comment (by jeremyhu): What is the output of: /opt/local/libexec/llvm-3.7/bin/ld -v -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 01:48:12 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 01:48:12 -0000 Subject: [MacPorts] #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic In-Reply-To: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> References: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> Message-ID: <059.00c310e021f9c7b384f7a6185bbbfb58@macports.org> #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic -----------------------+---------------------- Reporter: gbrtrac | Owner: jeremyhu Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: llvm-3.8 | -----------------------+---------------------- Changes (by jeremyhu): * status: assigned => accepted -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 01:49:16 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 01:49:16 -0000 Subject: [MacPorts] #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic In-Reply-To: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> References: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> Message-ID: <059.218a1274af04e5d53052912377116d13@macports.org> #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic -----------------------+---------------------- Reporter: gbrtrac | Owner: jeremyhu Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: llvm-3.8 | -----------------------+---------------------- Comment (by jeremyhu): Note that's just a warning from the linker. Are you seeing fallout from it? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 01:50:08 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 01:50:08 -0000 Subject: [MacPorts] #53151: ld64-latest: handeling tbd files In-Reply-To: <056.29f019982176bcf6547cbdbe183768d5@macports.org> References: <056.29f019982176bcf6547cbdbe183768d5@macports.org> Message-ID: <071.77c8a45a2406735e3abbf1c72261a49d@macports.org> #53151: ld64-latest: handeling tbd files ----------------------------------+------------------------ Reporter: MarcusCalhoun-Lopez | Owner: jeremyhu@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: invalid | Keywords: Port: ld64-latest | ----------------------------------+------------------------ Changes (by jeremyhu): * status: new => closed * resolution: => invalid Comment: File a radar at http://bugreport.apple.com -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 02:01:04 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 02:01:04 -0000 Subject: [MacPorts] #53151: ld64-latest: handeling tbd files In-Reply-To: <056.29f019982176bcf6547cbdbe183768d5@macports.org> References: <056.29f019982176bcf6547cbdbe183768d5@macports.org> Message-ID: <071.1e6a1d88f938786ca00aba32afe299a9@macports.org> #53151: ld64-latest: handeling tbd files ----------------------------------+------------------------ Reporter: MarcusCalhoun-Lopez | Owner: jeremyhu@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: invalid | Keywords: Port: ld64-latest | ----------------------------------+------------------------ Comment (by jeremyhu): (and indicate that it's a dupe of 29679726). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 02:07:56 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 02:07:56 -0000 Subject: [MacPorts] #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic In-Reply-To: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> References: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> Message-ID: <059.9e1ae53a70320b82c8032262f03b9b4b@macports.org> #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic -----------------------+---------------------- Reporter: gbrtrac | Owner: jeremyhu Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: llvm-3.8 | -----------------------+---------------------- Comment (by gbrtrac): The "warning" actually stops the build -- treated as an error /opt/local/libexec/llvm-3.7/bin/ld -v @(#)PROGRAM:ld PROJECT:ld64-136 configured to support archs: i386 x86_64 armv7 armv7s LTO support using: LLVM version 3.7.1 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 02:08:14 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 02:08:14 -0000 Subject: [MacPorts] #53144: libmacho @895 fails to build because GCC is not universal variant In-Reply-To: <046.367079c58979ee177ea68524b2ea0c15@macports.org> References: <046.367079c58979ee177ea68524b2ea0c15@macports.org> Message-ID: <061.07317b3d21bed756f72f9340da480dc8@macports.org> #53144: libmacho @895 fails to build because GCC is not universal variant ------------------------+------------------------------ Reporter: ballapete | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: tiger, universal Port: libmacho | ------------------------+------------------------------ Comment (by jeremyhu): Replying to [comment:2 ballapete]: > Replying to [comment:1 jeremyhu]: > > In [changeset:"41e0ae1cf32e0a3d86283818c27e83e06fc8a853/macports- ports" 41e0ae1c/macports-ports]: > > {{{ > > #!ConfigurableCommitTicketReference repository="macports-ports" revision="41e0ae1cf32e0a3d86283818c27e83e06fc8a853" > > {apple,llvm}-gcc42: Default to +universal > > > > The build system basically conflates CHOST and CTARGET. This is > > the simplest fix, and given the very deprecated nature of these > > ports, it's not worth a deeper fix. > > What does that mean? I have no idea what a CHOST and a CTARGET could be… That's the change log from the commit. It's not instructions for you. CBUILD is the architecture of the system that is building the executable CHOST is the architecture that the build executable will run on CTARGET is the architecture that the build executable will generate code for > > Fixes https://trac.macports.org/ticket/53144 > > > > I seem to have a problem seeing the fix… Just reinstall it +universal. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 02:09:40 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 02:09:40 -0000 Subject: [MacPorts] #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic In-Reply-To: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> References: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> Message-ID: <059.c97b0b860bda48cb0a6c8dc6a007a944@macports.org> #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic -----------------------+---------------------- Reporter: gbrtrac | Owner: jeremyhu Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: llvm-3.8 | -----------------------+---------------------- Comment (by jeremyhu): What port were you trying to build when you encountered this error? Please attach the full build log. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 02:14:43 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 02:14:43 -0000 Subject: [MacPorts] #53140: cctools @895_3 do not build on PPC Tiger, Mac OS X 10.4.11, because OFILE_LLVM_BITCODE macro is used in misc/strings.c In-Reply-To: <046.826b272879a9dece0fde20ec935cab75@macports.org> References: <046.826b272879a9dece0fde20ec935cab75@macports.org> Message-ID: <061.8457a4b38801124b242dd8422fd21e8e@macports.org> #53140: cctools @895_3 do not build on PPC Tiger, Mac OS X 10.4.11, because OFILE_LLVM_BITCODE macro is used in misc/strings.c ------------------------+--------------------------- Reporter: ballapete | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: tiger powerpc Port: cctools | ------------------------+--------------------------- Changes (by jeremyhu): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"fe6f70002ce2f81dbb00001553fa3724893c313b/macports-ports" fe6f7000/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="fe6f70002ce2f81dbb00001553fa3724893c313b" cctools: Fix biuld without LTO support Fixes https://trac.macports.org/ticket/53140 Signed-off-by: Jeremy Huddleston Sequoia }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 02:20:17 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 02:20:17 -0000 Subject: [MacPorts] #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic In-Reply-To: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> References: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> Message-ID: <059.e7cab1dbe92815511d547a92410fee99@macports.org> #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic -----------------------+---------------------- Reporter: gbrtrac | Owner: jeremyhu Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: llvm-3.8 | -----------------------+---------------------- Changes (by gbrtrac): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 02:21:26 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 02:21:26 -0000 Subject: [MacPorts] #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic In-Reply-To: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> References: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> Message-ID: <059.f622d75a7eccbef622a0dec1f26dbd79@macports.org> #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic -----------------------+---------------------- Reporter: gbrtrac | Owner: jeremyhu Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: llvm-3.8 | -----------------------+---------------------- Comment (by gbrtrac): The same thing happens if I clean and run the build -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 02:21:27 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 02:21:27 -0000 Subject: [MacPorts] #53152: ${prefix}/bin is not in PATH during build Message-ID: <045.7ecd78b417e4568b5ca942705e3aa5fc@macports.org> #53152: ${prefix}/bin is not in PATH during build ----------------------+----------------- Reporter: jeremyhu | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: Keywords: | Port: ----------------------+----------------- In the build phase, `ar` is resolving to /usr/bin/ar rather than ${prefix}/bin/ar as I'd expect because ${prefix}/bin seems to not be in $PATH any more. Am I misremembering? Was this change intentional? {{{ ---> Building serf1 DEBUG: Executing org.macports.build (serf1) DEBUG: Environment: CC_PRINT_OPTIONS='YES' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build /_Users_jeremy_src_macports_macports- ports_www_serf1/serf1/work/.CC_PRINT_OPTIONS' CPATH='/opt/local/include' LIBRARY_PATH='/opt/local/lib' MACOSX_DEPLOYMENT_TARGET='10.6' Executing: cd "/opt/local/var/macports/build /_Users_jeremy_src_macports_macports- ports_www_serf1/serf1/work/serf-1.3.8" && /opt/local/bin/scons -j6 APR=/opt/local APU=/opt/local OPENSSL=/opt/local PREFIX=/opt/local CC=/opt/local/bin/clang-mp-3.9 CPPFLAGS="-I/opt/local/include" CFLAGS="-Os -arch x86_64 -arch i386" LINKFLAGS="-L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 -arch i386" CC="MACOSX_DEPLOYMENT_TARGET=10.6 /opt/local/bin/clang-mp-3.9" DEBUG: system: cd "/opt/local/var/macports/build /_Users_jeremy_src_macports_macports- ports_www_serf1/serf1/work/serf-1.3.8" && /opt/local/bin/scons -j6 APR=/opt/local APU=/opt/local OPENSSL=/opt/local PREFIX=/opt/local CC=/opt/local/bin/clang-mp-3.9 CPPFLAGS="-I/opt/local/include" CFLAGS="-Os -arch x86_64 -arch i386" LINKFLAGS="-L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 -arch i386" CC="MACOSX_DEPLOYMENT_TARGET=10.6 /opt/local/bin/clang-mp-3.9" scons: Reading SConscript files ... scons: done reading SConscript files. scons: Building targets ... ar rc libserf-1.a context.o incoming.o outgoing.o ssltunnel.o buckets/aggregate_buckets.o buckets/allocator.o buckets/barrier_buckets.o buckets/buckets.o buckets/bwtp_buckets.o buckets/chunk_buckets.o buckets/dechunk_buckets.o buckets/deflate_buckets.o buckets/file_buckets.o buckets/headers_buckets.o buckets/iovec_buckets.o buckets/limit_buckets.o buckets/mmap_buckets.o buckets/request_buckets.o buckets/response_body_buckets.o buckets/response_buckets.o buckets/simple_buckets.o buckets/socket_buckets.o buckets/ssl_buckets.o auth/auth.o auth/auth_basic.o auth/auth_digest.o auth/auth_spnego.o auth/auth_spnego_gss.o auth/auth_spnego_sspi.o /usr/bin/ranlib: for object: libserf-1.a(x86_64) architecture context.o 1482632001 502 80 100644 16904 ` ¾ºþÊ malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(i386) architecture context.o 1482632001 502 80 100644 16904 ` ¾ºþÊ malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(x86_64) architecture buckets.o 1482632002 502 80 100644 17356 ` ¾ºþÊ malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(i386) architecture buckets.o 1482632002 502 80 100644 17356 ` ¾ºþÊ malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(x86_64) architecture dechunk_buckets.o malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(i386) architecture dechunk_buckets.o malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(x86_64) architecture deflate_buckets.o malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(i386) architecture deflate_buckets.o malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(x86_64) architecture headers_buckets.o malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(i386) architecture headers_buckets.o malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(x86_64) architecture response_buckets.o malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(i386) architecture response_buckets.o malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(x86_64) architecture ssl_buckets.o 1482632004 502 80 100644 62640 ` ¾ºþÊ malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(i386) architecture ssl_buckets.o 1482632004 502 80 100644 62640 ` ¾ºþÊ malformed object (unknown load command 2) /usr/bin/ranlib: library member: libserf-1.a(context.o) is not an object file (not allowed in a library with multiple architectures) /usr/bin/ranlib: library member: libserf-1.a(buckets.o) is not an object file (not allowed in a library with multiple architectures) /usr/bin/ranlib: library member: libserf-1.a(dechunk_buckets.o) is not an object file (not allowed in a library with multiple architectures) /usr/bin/ranlib: library member: libserf-1.a(deflate_buckets.o) is not an object file (not allowed in a library with multiple architectures) /usr/bin/ranlib: library member: libserf-1.a(headers_buckets.o) is not an object file (not allowed in a library with multiple architectures) /usr/bin/ranlib: library member: libserf-1.a(response_buckets.o) is not an object file (not allowed in a library with multiple architectures) /usr/bin/ranlib: library member: libserf-1.a(ssl_buckets.o) is not an object file (not allowed in a library with multiple architectures) ar: internal ranlib command failed MACOSX_DEPLOYMENT_TARGET=10.6 /opt/local/bin/clang-mp-3.9 -o auth/auth_spnego_gss.os -c -Os -arch x86_64 -arch i386 -std=c89 -Wdeclaration-after-statement -Wmissing-prototypes -Wall -O2 -fPIC -I/opt/local/include -DNDEBUG -DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK -DDARWIN_10 -I. -I/opt/local/include/apr-1 -I/opt/local/include -I/opt/local/include auth/auth_spnego_gss.c MACOSX_DEPLOYMENT_TARGET=10.6 /opt/local/bin/clang-mp-3.9 -o auth/auth_spnego_sspi.os -c -Os -arch x86_64 -arch i386 -std=c89 -Wdeclaration-after-statement -Wmissing-prototypes -Wall -O2 -fPIC -I/opt/local/include -DNDEBUG -DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK -DDARWIN_10 -I. -I/opt/local/include/apr-1 -I/opt/local/include -I/opt/local/include auth/auth_spnego_sspi.c scons: *** [libserf-1.a] Error 1 Creating 'serf-1.pc' scons: building terminated because of errors. Command failed: cd "/opt/local/var/macports/build /_Users_jeremy_src_macports_macports- ports_www_serf1/serf1/work/serf-1.3.8" && /opt/local/bin/scons -j6 APR=/opt/local APU=/opt/local OPENSSL=/opt/local PREFIX=/opt/local CC=/opt/local/bin/clang-mp-3.9 CPPFLAGS="-I/opt/local/include" CFLAGS="-Os -arch x86_64 -arch i386" LINKFLAGS="-L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 -arch i386" CC="MACOSX_DEPLOYMENT_TARGET=10.6 /opt/local/bin/clang-mp-3.9" Exit code: 2 Error: Failed to build serf1: command execution failed DEBUG: Error code: CHILDSTATUS 9404 2 DEBUG: Backtrace: command execution failed while executing "system {*}$notty {*}$nice $fullcmdstring" invoked from within "command_exec build" (procedure "portbuild::build_main" line 8) invoked from within "$procedure $targetname" Error: See /opt/local/var/macports/logs /_Users_jeremy_src_macports_macports-ports_www_serf1/serf1/main.log for details. Error: Follow https://guide.macports.org/#project.tickets to report a bug. Error: Processing of port serf1 failed }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 02:25:19 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 02:25:19 -0000 Subject: [MacPorts] #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies In-Reply-To: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> References: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> Message-ID: <075.6b6fb929bc881e6c1c3cefd54ce4b500@macports.org> #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies -------------------------------------------------+------------------------- Reporter: maxkalashnikov-macports | Owner: jeremyhu Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: clang-3.3 clang-3.4 clang-3.5 | clang-3.6 clang-3.7 clang-3.8 clang-3.9 | -------------------------------------------------+------------------------- Comment (by maxkalashnikov-macports): That doesn't seem to work, though having `ld64+ld64_xcode` installed eliminates `ld64` from the list of dependencies in the error message: {{{ ---> Computing dependencies for clang-3.9...... ---> Dependencies to be installed: cctools llvm-3.9 clang-3.8 clang-3.7 llvm-3.8 Error: The following dependencies were not installed: cctools llvm-3.9 clang-3.8 clang-3.7 llvm-3.8 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port clang-3.9 failed }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 03:21:18 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 03:21:18 -0000 Subject: [MacPorts] #53153: curl @7.51.0_1: update to 7.52.1 Message-ID: <041.976b8eead57598b628eda8efc5dc742b@macports.org> #53153: curl @7.51.0_1: update to 7.52.1 --------------------+------------------ Reporter: l2dy | Owner: Type: update | Status: new Priority: High | Milestone: Component: ports | Version: Keywords: | Port: curl --------------------+------------------ CVE-2016-9586 and CVE-2016-9594 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 03:55:10 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 03:55:10 -0000 Subject: [MacPorts] #53152: ${prefix}/bin is not in PATH during build In-Reply-To: <045.7ecd78b417e4568b5ca942705e3aa5fc@macports.org> References: <045.7ecd78b417e4568b5ca942705e3aa5fc@macports.org> Message-ID: <060.a5608d5ee52caffb7d548d41cb518501@macports.org> #53152: ${prefix}/bin is not in PATH during build -----------------------+----------------- Reporter: jeremyhu | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: scons | -----------------------+----------------- Changes (by jeremyhu): * component: base => ports * port: => scons Comment: Looks like a bug in scons. scons seems to not be honoring $PATH in the calling environment: {{{ $ which ar /opt/local/bin/ar $ /opt/local/bin/scons -j6 APR=/opt/local APU=/opt/local OPENSSL=/opt/local PREFIX=/opt/local CC=/opt/local/bin/clang-mp-3.9 CPPFLAGS="-I/opt/local/include" CFLAGS="-Os -arch x86_64 -arch i386" LINKFLAGS="-L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 -arch i386" CC="MACOSX_DEPLOYMENT_TARGET=10.6 /opt/local/bin/clang-mp-3.9" scons: Reading SConscript files ... scons: done reading SConscript files. scons: Building targets ... ar rc libserf-1.a context.o incoming.o outgoing.o ssltunnel.o buckets/aggregate_buckets.o buckets/allocator.o buckets/barrier_buckets.o buckets/buckets.o buckets/bwtp_buckets.o buckets/chunk_buckets.o buckets/dechunk_buckets.o buckets/deflate_buckets.o buckets/file_buckets.o buckets/headers_buckets.o buckets/iovec_buckets.o buckets/limit_buckets.o buckets/mmap_buckets.o buckets/request_buckets.o buckets/response_body_buckets.o buckets/response_buckets.o buckets/simple_buckets.o buckets/socket_buckets.o buckets/ssl_buckets.o auth/auth.o auth/auth_basic.o auth/auth_digest.o auth/auth_spnego.o auth/auth_spnego_gss.o auth/auth_spnego_sspi.o /usr/bin/ranlib: for object: libserf-1.a(x86_64) architecture context.o 1482632001 502 80 100644 16904 ` ???? malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(i386) architecture context.o 1482632001 502 80 100644 16904 ` ???? malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(x86_64) architecture buckets.o 1482632002 502 80 100644 17356 ` ???? malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(i386) architecture buckets.o 1482632002 502 80 100644 17356 ` ???? malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(x86_64) architecture dechunk_buckets.o malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(i386) architecture dechunk_buckets.o malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(x86_64) architecture deflate_buckets.o malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(i386) architecture deflate_buckets.o malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(x86_64) architecture headers_buckets.o malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(i386) architecture headers_buckets.o malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(x86_64) architecture response_buckets.o malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(i386) architecture response_buckets.o malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(x86_64) architecture ssl_buckets.o 1482632004 502 80 100644 62640 ` ???? malformed object (unknown load command 2) /usr/bin/ranlib: for object: libserf-1.a(i386) architecture ssl_buckets.o 1482632004 502 80 100644 62640 ` ???? malformed object (unknown load command 2) /usr/bin/ranlib: library member: libserf-1.a(context.o) is not an object file (not allowed in a library with multiple architectures) /usr/bin/ranlib: library member: libserf-1.a(buckets.o) is not an object file (not allowed in a library with multiple architectures) /usr/bin/ranlib: library member: libserf-1.a(dechunk_buckets.o) is not an object file (not allowed in a library with multiple architectures) /usr/bin/ranlib: library member: libserf-1.a(deflate_buckets.o) is not an object file (not allowed in a library with multiple architectures) /usr/bin/ranlib: library member: libserf-1.a(headers_buckets.o) is not an object file (not allowed in a library with multiple architectures) /usr/bin/ranlib: library member: libserf-1.a(response_buckets.o) is not an object file (not allowed in a library with multiple architectures) /usr/bin/ranlib: library member: libserf-1.a(ssl_buckets.o) is not an object file (not allowed in a library with multiple architectures) ar: internal ranlib command failed scons: `libserf-1.dylib' is up to date. scons: `serf-1.pc' is up to date. scons: *** [libserf-1.a] Error 1 scons: building terminated because of errors. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 03:55:22 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 03:55:22 -0000 Subject: [MacPorts] #53152: scons does not honor $PATH (was: ${prefix}/bin is not in PATH during build) In-Reply-To: <045.7ecd78b417e4568b5ca942705e3aa5fc@macports.org> References: <045.7ecd78b417e4568b5ca942705e3aa5fc@macports.org> Message-ID: <060.4b737730f27c84cd06061d779d903ec3@macports.org> #53152: scons does not honor $PATH -----------------------+----------------- Reporter: jeremyhu | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: scons | -----------------------+----------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 04:16:43 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 04:16:43 -0000 Subject: [MacPorts] #53152: scons does not honor $PATH In-Reply-To: <045.7ecd78b417e4568b5ca942705e3aa5fc@macports.org> References: <045.7ecd78b417e4568b5ca942705e3aa5fc@macports.org> Message-ID: <060.b721b2f0c6f14f85ee27066ccec568af@macports.org> #53152: scons does not honor $PATH -----------------------+----------------- Reporter: jeremyhu | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: scons | -----------------------+----------------- Comment (by jeremyhu): http://scons.org/doc/1.2.0/HTML/scons-user/x1673.html {{{ 7.3.1. Propagating PATH From the External Environment You may want to propagate the external PATH to the execution environment for commands. You do this by initializing the PATH variable with the PATH value from the os.environ dictionary, which is Python's way of letting you get at the external environment: import os env = Environment(ENV = {'PATH' : os.environ['PATH']}) Alternatively, you may find it easier to just propagate the entire external environment to the execution environment for commands. This is simpler to code than explicity selecting the PATH value: import os env = Environment(ENV = os.environ) Either of these will guarantee that SCons will be able to execute any command that you can execute from the command line. The drawback is that the build can behave differently if it's run by people with different PATH values in their environment--for example, if both the /bin and /usr/local/bin directories have different cc commands, then which one will be used to compile programs will depend on which directory is listed first in the user's PATH variable. }}} So... yet another completely braindead broken by design build system. It's up to each project to decide that it should honor the build environment?!? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 05:56:57 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 05:56:57 -0000 Subject: [MacPorts] #35972: inform @6.31.1 build fails with clang (missing verblibm.h and parserm.h) In-Reply-To: <058.4782e6a9bc25e78d05dcc23fc66a00ce@macports.org> References: <058.4782e6a9bc25e78d05dcc23fc66a00ce@macports.org> Message-ID: <073.2e309d48d61d96815a08c05b2963868e@macports.org> #35972: inform @6.31.1 build fails with clang (missing verblibm.h and parserm.h) -------------------------+-------------------- Reporter: macports@… | Owner: vim@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: fixed | Keywords: clang Port: inform | -------------------------+-------------------- Changes (by jeremyhu): * status: new => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 07:32:42 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 07:32:42 -0000 Subject: [MacPorts] #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic In-Reply-To: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> References: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> Message-ID: <059.8a898ee6119330497f6b2d8aef685e5d@macports.org> #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic -----------------------+---------------------- Reporter: gbrtrac | Owner: jeremyhu Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: llvm-3.8 | -----------------------+---------------------- Comment (by jeremyhu): Why did you decide to use the +ld64_variant? ld64-136 is really only useful for Leopard. If you use ld64-latest instead, I expect you can get past this. This was fixed in newer clang: commit bd77c59acc58e797756b0fcc6739319587e95d85 Author: Bob Wilson Date: Fri Aug 2 22:25:34 2013 +0000 Only use the Darwin linker's -export_dynamic option with supported versions. Related to . git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk at 187680 91177308-0d34-0410-b5e6-96231b3b80d8 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 07:41:02 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 07:41:02 -0000 Subject: [MacPorts] #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic In-Reply-To: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> References: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> Message-ID: <059.4a88a9a7730b425401856468aefa102a@macports.org> #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic -----------------------+---------------------- Reporter: gbrtrac | Owner: jeremyhu Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: llvm-3.8 | -----------------------+---------------------- Comment (by jeremyhu): Reduced: {{{ $ clang-mp-devel -c true.c && clang-mp-devel -rdynamic true.o -v clang version 4.0.0 (trunk 290074) Target: x86_64-apple-darwin13.4.0 Thread model: posix InstalledDir: /opt/local/libexec/llvm-devel/bin "/opt/local/libexec/llvm-devel/bin/ld" -demangle -export_dynamic -lto_library /opt/local/libexec/llvm-devel/lib/libLTO.dylib -dynamic -arch x86_64 -macosx_version_min 10.9.0 -o a.out true.o -lSystem /opt/local/libexec/llvm- devel/bin/../lib/clang/4.0.0/lib/darwin/libclang_rt.osx.a ld: unknown option: -export_dynamic clang: error: linker command failed with exit code 1 (use -v to see invocation) $ /opt/local/libexec/llvm-devel/bin/ld -v @(#)PROGRAM:ld PROJECT:ld64-136 configured to support archs: i386 x86_64 armv7 armv7s LTO support using: LLVM version 4.0.0svn }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 07:47:34 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 07:47:34 -0000 Subject: [MacPorts] #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic In-Reply-To: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> References: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> Message-ID: <059.90b354ed3aeab3f0e54f71f71f290351@macports.org> #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic -----------------------+---------------------- Reporter: gbrtrac | Owner: jeremyhu Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: llvm-3.8 | -----------------------+---------------------- Comment (by jeremyhu): Filed upstream bug https://llvm.org/bugs/show_bug.cgi?id=31465 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 08:02:41 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 08:02:41 -0000 Subject: [MacPorts] #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic In-Reply-To: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> References: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> Message-ID: <059.4e19e8b7feb07153ecc37ffaf5bccb9e@macports.org> #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic -----------------------+---------------------- Reporter: gbrtrac | Owner: jeremyhu Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: llvm-3.8 | -----------------------+---------------------- Comment (by jeremyhu): Do the following: {{{ sudo port -v -f deactivate ld64 sudo port -v install ld64 -ld64_136 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 08:13:05 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 08:13:05 -0000 Subject: [MacPorts] #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies In-Reply-To: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> References: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> Message-ID: <075.e975d0e9f6e638c35d8852b0052911fc@macports.org> #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies -------------------------------------------------+------------------------- Reporter: maxkalashnikov-macports | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: clang-3.3 clang-3.4 clang-3.5 | clang-3.6 clang-3.7 clang-3.8 clang-3.9 | -------------------------------------------------+------------------------- Changes (by jeremyhu): * status: reopened => closed * resolution: => fixed Comment: In [changeset:"ecaccfb3d8f4b7fd0861a26a55037bf45e0ae9fa/macports-ports" ecaccfb3/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="ecaccfb3d8f4b7fd0861a26a55037bf45e0ae9fa" llvm-{3.8,3.9,devel}: Drop dependency on cctools for building clang We don't need to use install_name_tool when building compiler_rt in the cmake based build system. Fixes https://trac.macports.org/ticket/53138 Signed-off-by: Jeremy Huddleston Sequoia }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 08:17:33 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 08:17:33 -0000 Subject: [MacPorts] #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies In-Reply-To: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> References: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> Message-ID: <075.7be3fbbf9a05615851b865644d480b0f@macports.org> #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies -------------------------------------------------+------------------------- Reporter: maxkalashnikov-macports | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: clang-3.3 clang-3.4 clang-3.5 | clang-3.6 clang-3.7 clang-3.8 clang-3.9 | -------------------------------------------------+------------------------- Comment (by jeremyhu): Although I'm not satisfied that's the last of them. We might need to re-add +llvm37 variants when building with older versions of Xcode to help with the bootstrapping problem. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 08:46:10 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 08:46:10 -0000 Subject: [MacPorts] #53142: py-poppler-qt5 @0.24.2_0: new port In-Reply-To: <044.775e8b80dd329fb47e07e1295012ac85@macports.org> References: <044.775e8b80dd329fb47e07e1295012ac85@macports.org> Message-ID: <059.40975bc0eee4f040c005da6b581db08d@macports.org> #53142: py-poppler-qt5 @0.24.2_0: new port -----------------------------+--------------------- Reporter: dliessi | Owner: dliessi Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: py-poppler-qt5 | -----------------------------+--------------------- Changes (by dliessi): * status: new => closed * owner: => dliessi * resolution: => fixed Comment: In [changeset:"d14b0e0942913fe0ef8f44f80dce57ea096a1743/macports-ports" d14b0e09/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="d14b0e0942913fe0ef8f44f80dce57ea096a1743" py-poppler-qt5: new port Closes: #120 Closes: https://trac.macports.org/ticket/53142 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 09:01:33 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 09:01:33 -0000 Subject: [MacPorts] #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies In-Reply-To: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> References: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> Message-ID: <075.9f8807ed6bd6bd6780b0176181ea2b66@macports.org> #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies -------------------------------------------------+------------------------- Reporter: maxkalashnikov-macports | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: clang-3.3 clang-3.4 clang-3.5 | clang-3.6 clang-3.7 clang-3.8 clang-3.9 | -------------------------------------------------+------------------------- Comment (by jeremyhu): In [changeset:"ceaae55eb40eb7075d5b52c39aa22833e85041dd/macports-ports" ceaae55e/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="ceaae55eb40eb7075d5b52c39aa22833e85041dd" cctools: Add a +llvm37 variant to help bootstrap Mountain Lion and Mavericks Fixes https://trac.macports.org/ticket/53138 Signed-off-by: Jeremy Huddleston Sequoia }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 09:01:33 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 09:01:33 -0000 Subject: [MacPorts] #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies In-Reply-To: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> References: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> Message-ID: <075.061a87eea27afb06b25cc26009962692@macports.org> #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies -------------------------------------------------+------------------------- Reporter: maxkalashnikov-macports | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: clang-3.3 clang-3.4 clang-3.5 | clang-3.6 clang-3.7 clang-3.8 clang-3.9 | -------------------------------------------------+------------------------- Comment (by jeremyhu): In [changeset:"e16e82613704613186e523d27b6b2e7bf87484d5/macports-ports" e16e8261/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="e16e82613704613186e523d27b6b2e7bf87484d5" ld64: Add a +llvm37 variant to help bootstrap Mountain Lion and Mavericks Fixes https://trac.macports.org/ticket/53138 Signed-off-by: Jeremy Huddleston Sequoia }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 09:33:21 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 09:33:21 -0000 Subject: [MacPorts] #53144: libmacho @895 fails to build because GCC is not universal variant In-Reply-To: <046.367079c58979ee177ea68524b2ea0c15@macports.org> References: <046.367079c58979ee177ea68524b2ea0c15@macports.org> Message-ID: <061.71e38880ff5759eadb825a9f6187cc13@macports.org> #53144: libmacho @895 fails to build because GCC is not universal variant ------------------------+------------------------------ Reporter: ballapete | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: tiger, universal Port: libmacho | ------------------------+------------------------------ Comment (by ballapete): {{{ Error: apple-gcc42 cannot be installed for the configured universal_archs 'i386 ppc' because it only supports the arch(s) 'ppc ppc64'. }}} That's the report from trying to install apple-gcc42 as universal. This variant is listed among the port's variants. New bug report on apple-gcc42? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 09:37:35 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 09:37:35 -0000 Subject: [MacPorts] #53152: scons does not honor $PATH In-Reply-To: <045.7ecd78b417e4568b5ca942705e3aa5fc@macports.org> References: <045.7ecd78b417e4568b5ca942705e3aa5fc@macports.org> Message-ID: <060.f5c20615dd996ad700e92f6d0cb3be8c@macports.org> #53152: scons does not honor $PATH -----------------------+----------------- Reporter: jeremyhu | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: scons | -----------------------+----------------- Comment (by jeremyhu): In [changeset:"c1f05c311796cda37b4ef774a04d0d90dcb3fcc7/macports-ports" c1f05c31/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="c1f05c311796cda37b4ef774a04d0d90dcb3fcc7" serf1: Honor $PATH when building See https://trac.macports.org/ticket/53152 Signed-off-by: Jeremy Huddleston Sequoia }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 09:39:01 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 09:39:01 -0000 Subject: [MacPorts] #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies In-Reply-To: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> References: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> Message-ID: <075.9e6863e03d392a92b3cf4ba0ba099ec7@macports.org> #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies -------------------------------------------------+------------------------- Reporter: maxkalashnikov-macports | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: clang-3.3 clang-3.4 clang-3.5 | clang-3.6 clang-3.7 clang-3.8 clang-3.9 | -------------------------------------------------+------------------------- Comment (by mojca): Other OS versions have {{{ #!tcl if {${os.major} == 10 || ${os.major} == 11} { default_variants +llvm34 } elseif {${os.major} == 9} { # Using llvm-3.3 to break dependency cycle (https://trac.macports.org/ticket/52091) default_variants +llvm33 } }}} Isn't the same needed on 10.8 & 10.9 as well? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 09:40:53 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 09:40:53 -0000 Subject: [MacPorts] #53144: libmacho @895 fails to build because GCC is not universal variant In-Reply-To: <046.367079c58979ee177ea68524b2ea0c15@macports.org> References: <046.367079c58979ee177ea68524b2ea0c15@macports.org> Message-ID: <061.673e500f03f8efa5f45085782715ef74@macports.org> #53144: libmacho @895 fails to build because GCC is not universal variant ------------------------+------------------------------ Reporter: ballapete | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: tiger, universal Port: libmacho | ------------------------+------------------------------ Comment (by jeremyhu): No, that's a limitation that won't be fixed. You want to set `universal_archs` to `i386 x86_64` when installing apple- gcc42. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 09:43:06 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 09:43:06 -0000 Subject: [MacPorts] #53144: libmacho @895 fails to build because GCC is not universal variant In-Reply-To: <046.367079c58979ee177ea68524b2ea0c15@macports.org> References: <046.367079c58979ee177ea68524b2ea0c15@macports.org> Message-ID: <061.0cbecd340e58d931bfba26cd9c81989c@macports.org> #53144: libmacho @895 fails to build because GCC is not universal variant ------------------------+------------------------------ Reporter: ballapete | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: tiger, universal Port: libmacho | ------------------------+------------------------------ Comment (by jeremyhu): Specifically, note this comment in the Portfile: {{{ # Building universal with a ppc slice doesn't work (Tried on Leopard) if {${build_arch} eq "i386" || ${build_arch} eq "x86_64"} { supported_archs i386 x86_64 } elseif {${build_arch} eq "ppc" || ${build_arch} eq "ppc64"} { supported_archs ppc ppc64 } }}} If you have a patch, we'll certainly take it, but it's not worth the time to invest in adding support to that old port. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 09:44:24 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 09:44:24 -0000 Subject: [MacPorts] #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies In-Reply-To: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> References: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> Message-ID: <075.b19658f043d4382bda727ee091938909@macports.org> #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies -------------------------------------------------+------------------------- Reporter: maxkalashnikov-macports | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: clang-3.3 clang-3.4 clang-3.5 | clang-3.6 clang-3.7 clang-3.8 clang-3.9 | -------------------------------------------------+------------------------- Comment (by jeremyhu): Doh. Yeah, I left that out. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 09:50:43 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 09:50:43 -0000 Subject: [MacPorts] #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies In-Reply-To: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> References: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> Message-ID: <075.0701ee96ca14466f5a62ae709f104606@macports.org> #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies -------------------------------------------------+------------------------- Reporter: maxkalashnikov-macports | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: clang-3.3 clang-3.4 clang-3.5 | clang-3.6 clang-3.7 clang-3.8 clang-3.9 | -------------------------------------------------+------------------------- Comment (by jeremyhu): In [changeset:"d322f154091d1b4a374bafcd9a6627029f0f03b5/macports-ports" d322f154/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="d322f154091d1b4a374bafcd9a6627029f0f03b5" ld64: Default to +llvm37 on Mountain Lion and Mavericks Fixes https://trac.macports.org/ticket/53138 Signed-off-by: Jeremy Huddleston Sequoia }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 09:50:44 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 09:50:44 -0000 Subject: [MacPorts] #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies In-Reply-To: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> References: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> Message-ID: <075.9c63bba3234a84fbd6c0c22de35dc987@macports.org> #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies -------------------------------------------------+------------------------- Reporter: maxkalashnikov-macports | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: clang-3.3 clang-3.4 clang-3.5 | clang-3.6 clang-3.7 clang-3.8 clang-3.9 | -------------------------------------------------+------------------------- Comment (by jeremyhu): In [changeset:"4b49d9654d147bb0ba69f081b1c1c8b4de8b082f/macports-ports" 4b49d965/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="4b49d9654d147bb0ba69f081b1c1c8b4de8b082f" cctools: Default to +llvm37 on Mountain Lion and Mavericks Fixes https://trac.macports.org/ticket/53138 Signed-off-by: Jeremy Huddleston Sequoia }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 10:29:34 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 10:29:34 -0000 Subject: [MacPorts] #53154: qhull seems to fail systematically when called from octave Message-ID: <044.b2f66d585e240ba60d5800db45e93af9@macports.org> #53154: qhull seems to fail systematically when called from octave ---------------------+-------------------------- Reporter: pierard | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: octave qhull ---------------------+-------------------------- The following example is given on the octave page [https://www.gnu.org/software/octave/doc/v4.0.3/Convex-Hull.html]: {{{ x = -3:0.05:3; y = abs (sin (x)); k = convhull (x, y); }}} when I try it, I get an error: {{{ QH6164 qhull internal error (qh_qhull): temporary sets not empty(2) While executing: | qhull Qt Options selected for Qhull 2015.2 2016/01/18: run-id 1815947927 Qtriangulate _pre-merge _zero-centrum _max-width 6 Error-roundoff 2.5e-15 _one-merge 1.2e-14 _near-inside 6.2e-14 Visible-distance 4.9e-15 U-coplanar-distance 4.9e-15 Width-outside 9.8e-15 _wide-facet 3e-14 Last point added to hull was p1. At error exit: Convex hull of 121 points in 2-d: Number of vertices: 61 Number of facets: 61 Statistics for: | qhull Qt Number of points processed: 61 Number of hyperplanes created: 120 Number of distance tests for qhull: 1007 error: convhulln: qhull failed error: called from convhull at line 59 column 7 }}} I tried various inputs, and I always got similar errors, so it is not related to the particular choice of input for qhull. I don't find a lot of information on the web. But perhaps the one found on [http://octave-bug- tracker.gnu.narkive.com/qbqa1lLX/delauney3-fails] could be useful: "miscompiled qhull is not uncommon (it's sensitive to flags), so maybe that's the source of your problem." I hope a solution will be found soon, as this is a critical part for many scripts. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 11:58:48 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 11:58:48 -0000 Subject: [MacPorts] #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies In-Reply-To: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> References: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> Message-ID: <075.cd69527d9e8af0237ee0ae90ec382a01@macports.org> #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies -------------------------------------------------+------------------------- Reporter: maxkalashnikov-macports | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: clang-3.3 clang-3.4 clang-3.5 | clang-3.6 clang-3.7 clang-3.8 clang-3.9 | -------------------------------------------------+------------------------- Comment (by mojca): Thanks, it looks better on the buildbots now. Unrelated to this ticket, but where exactly does `x86_64h` come from? [https://build.macports.org/builders/ports-10.8_x86_64_legacy- builder/builds/13641 log]: {{{ cd /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_llvm-3.8/clang-3.8/work/build/projects /compiler-rt/lib/builtins && lipo -output /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_llvm-3.8/clang-3.8/work/build/./lib/clang/3.8.1/lib/darwin/libclang_rt.cc_kext.a -create -arch i386 /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_llvm-3.8/clang-3.8/work/build/lib/libclang_rt.cc_kext_i386_osx.a -arch x86_64 /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_llvm-3.8/clang-3.8/work/build/lib/libclang_rt.cc_kext_x86_64_osx.a -arch x86_64h /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_llvm-3.8/clang-3.8/work/build/lib/libclang_rt.cc_kext_x86_64h_osx.a lipo: unknown architecture specification flag: x86_64h in specifying input file -arch x86_64h /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_llvm-3.8/clang-3.8/work/build/lib/libclang_rt.cc_kext_x86_64h_osx.a lipo: known architecture flags are: any little big ppc64 x86_64 ppc970-64 ppc i386 m68k hppa sparc m88k i860 veo arm ppc601 ppc603 ppc603e ppc603ev ppc604 ppc604e ppc750 ppc7400 ppc7450 ppc970 i486 i486SX pentium i586 pentpro i686 pentIIm3 pentIIm5 pentium4 m68030 m68040 hppa7100LC veo1 veo2 veo3 veo4 armv4t armv5 xscale armv6 armv7 armv7f armv7k lipo: Usage: lipo [input_file] ... [-arch input_file] ... [-info] [-detailed_info] [-output output_file] [-create] [-arch_blank ] [-thin ] [-remove ] ... [-extract ] ... [-extract_family ] ... [-verify_arch ...] [-replace ] ... make[2]: *** [lib/clang/3.8.1/lib/darwin/libclang_rt.cc_kext.a] Error 1 make[2]: Leaving directory `/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_llvm-3.8/clang-3.8/work/build' make[1]: *** [projects/compiler- rt/lib/builtins/CMakeFiles/clang_rt.cc_kext.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs.... }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 12:37:48 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 12:37:48 -0000 Subject: [MacPorts] #53122: gpgme : upgrade to 1.8.0 and +qt5 variant In-Reply-To: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> References: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> Message-ID: <056.6eb8a271f23a831732fa5c8d0914259b@macports.org> #53122: gpgme : upgrade to 1.8.0 and +qt5 variant ---------------------+------------------------------- Reporter: RJVB | Owner: dbevans Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch upstream Port: gpgme | ---------------------+------------------------------- Comment (by RJVB): ABCDEFGHIJKMNOPQRSTUVWXYZ O:-) I think you also missed this: {{{ reinplace "s|@libsuffix@|.dylib|g" ${destroot}${prefix}/lib/cmake/Gpgmepp/GpgmeppConfig.cmake reinplace "s|.so|.dylib|g" ${destroot}${prefix}/lib/cmake/Gpgmepp/GpgmeppConfig.cmake }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 13:03:40 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 13:03:40 -0000 Subject: [MacPorts] #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X In-Reply-To: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> References: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> Message-ID: <061.79814fe86daf97f77380c3d0fee6a06b@macports.org> #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X ------------------------+--------------------------- Reporter: ballapete | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: tiger powerpc Port: libuv | ------------------------+--------------------------- Comment (by raimue): As Mac OS X 10.4 Tiger is a legacy platform and over 10 years old, I will not investigate myself or take action to fix this. Patches are welcome, but please also include the necessary changes to the Portfile. I do not know and cannot test whether this affects specifically only Mac OS X 10.4 Tiger and no later version, or only PPC, etc. You could also get help with this by contacting [https://github.com/libuv/libuv upstream] and maybe even incorporate the patches there directly. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 13:54:48 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 13:54:48 -0000 Subject: [MacPorts] #53108: openssh 7.4p1 release In-Reply-To: <047.1e7e14f0247ff7de5f469ecdc5024132@macports.org> References: <047.1e7e14f0247ff7de5f469ecdc5024132@macports.org> Message-ID: <062.7071eb46bba51fff6e431514a17d6af2@macports.org> #53108: openssh 7.4p1 release -------------------------+---------------------- Reporter: danielluke | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: openssh | -------------------------+---------------------- Comment (by myrkraverk): There are at least two relevant CVEs so I'd like to bump up the priority. https://bugs.chromium.org/p/project-zero/issues/detail?id=1010 https://bugs.chromium.org/p/project-zero/issues/detail?id=1009 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 14:51:32 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 14:51:32 -0000 Subject: [MacPorts] #53108: openssh 7.4p1 release In-Reply-To: <047.1e7e14f0247ff7de5f469ecdc5024132@macports.org> References: <047.1e7e14f0247ff7de5f469ecdc5024132@macports.org> Message-ID: <062.2d1d637e4f82f7078c611cb4abb9aa70@macports.org> #53108: openssh 7.4p1 release -------------------------+---------------------- Reporter: danielluke | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: openssh | -------------------------+---------------------- Comment (by raimue): Replying to [comment:3 myrkraverk]: > There are at least two relevant CVEs so I'd like to bump up the priority. > > https://bugs.chromium.org/p/project-zero/issues/detail?id=1010 Bug against sshd. > https://bugs.chromium.org/p/project-zero/issues/detail?id=1009 Bug against ssh-agent. Both of these binaries are usually the version provided by Apple, unless you explicitly exposed the MacPorts version by changing your system configuration. Upgrading MacPorts will not remove the attack vector. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 14:54:31 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 14:54:31 -0000 Subject: [MacPorts] #53151: ld64-latest: handeling tbd files In-Reply-To: <056.29f019982176bcf6547cbdbe183768d5@macports.org> References: <056.29f019982176bcf6547cbdbe183768d5@macports.org> Message-ID: <071.8d8a0b194b48b86fa7bdff7299b9fac1@macports.org> #53151: ld64-latest: handeling tbd files ----------------------------------+------------------------ Reporter: MarcusCalhoun-Lopez | Owner: jeremyhu@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: invalid | Keywords: Port: ld64-latest | ----------------------------------+------------------------ Comment (by MarcusCalhoun-Lopez): Thank you for the suggestion.[[BR]] I opened bug number 29804935 with Apple. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 15:12:52 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 15:12:52 -0000 Subject: [MacPorts] #53108: openssh 7.4p1 release In-Reply-To: <047.1e7e14f0247ff7de5f469ecdc5024132@macports.org> References: <047.1e7e14f0247ff7de5f469ecdc5024132@macports.org> Message-ID: <062.06811ef1153260ef6085af7d98cd2a50@macports.org> #53108: openssh 7.4p1 release -------------------------+---------------------- Reporter: danielluke | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: openssh | -------------------------+---------------------- Comment (by myrkraverk): Replying to [comment:5 raimue]: > Both of these binaries are usually the version provided by Apple, unless you explicitly exposed the MacPorts version by changing your system configuration. Upgrading MacPorts will not remove the attack vector. Ok, so purely installing MacPorts is not sufficient, but can I still use the provided ssh-agent by changing my system config to use it? Or is it incompatible somehow? Right now I'm less concerned about the SSH daemon than the agent. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 16:33:31 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 16:33:31 -0000 Subject: [MacPorts] #53147: python27 @2.7.13 fetch failed on osx 10.5 In-Reply-To: <046.aad5174b29074eccba1dcb7a3fe1ccba@macports.org> References: <046.aad5174b29074eccba1dcb7a3fe1ccba@macports.org> Message-ID: <061.8012eec8664f1dcdaa10f5b480c0a86b@macports.org> #53147: python27 @2.7.13 fetch failed on osx 10.5 ------------------------+--------------------- Reporter: pkoshevoy | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: duplicate | Keywords: leopard Port: python27 | ------------------------+--------------------- Comment (by pkoshevoy): unfortunately this broken python27 dependency is not allowing me to install git or update boost will the mirroring issue be resolved in 2016 or some time next year? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 16:33:35 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 16:33:35 -0000 Subject: [MacPorts] #47671: update exim to 4.85, deprecate mysql5 for mysql51, add mysql56, mariadb as of #43431 In-Reply-To: <050.7450907a95d15d37f4ef79dba0557f69@macports.org> References: <050.7450907a95d15d37f4ef79dba0557f69@macports.org> Message-ID: <065.9412e2a06c1808918f03a131f4588a92@macports.org> #47671: update exim to 4.85, deprecate mysql5 for mysql51, add mysql56, mariadb as of #43431 ----------------------+-------------------------------- Reporter: pokui@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: haspatch Port: exim | ----------------------+-------------------------------- Comment (by l2dy): https://exim.org/static/doc/CVE-2016-9963.txt -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 16:35:02 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 16:35:02 -0000 Subject: [MacPorts] #53122: gpgme : upgrade to 1.8.0 and +qt5 variant In-Reply-To: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> References: <041.23d102e16741b0b96b3ef3666ddf612d@macports.org> Message-ID: <056.cf3568d6630e0d783d33b87842653b25@macports.org> #53122: gpgme : upgrade to 1.8.0 and +qt5 variant ---------------------+------------------------------- Reporter: RJVB | Owner: dbevans Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch upstream Port: gpgme | ---------------------+------------------------------- Comment (by dbevans): In [changeset:"690ac3a3b526502d2f7b2f176b75e6c0bc99a209/macports-ports" 690ac3a3/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="690ac3a3b526502d2f7b2f176b75e6c0bc99a209" gpgme: fixup library suffix in installed GpgmeppConfig.cmake See: https://trac.macports.org/ticket/53122 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 16:55:59 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 16:55:59 -0000 Subject: [MacPorts] #48807: python messes with terminal state on exit In-Reply-To: <057.6bd5937ec1e3acdeef099f04c549c3bb@macports.org> References: <057.6bd5937ec1e3acdeef099f04c549c3bb@macports.org> Message-ID: <072.b251452e3639e26f44c3c071e5697d07@macports.org> #48807: python messes with terminal state on exit -------------------------------------------------+------------------------- Reporter: yselivanov@… | Owner: | jyrkiwahlstedt Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: haspatch Port: python26 python27 python python34 | python35 libedit | -------------------------------------------------+------------------------- Comment (by cdeil): With {{{sudo port install python36}}} I now see {{{ ############################################################## # IF YOU ARE USING PYTHON FROM THE TERMINAL, PLEASE INSTALL: # py36-readline # TO AVOID A LIBEDIT / PYTHON INTERACTION ISSUE. # REF: https://trac.macports.org/ticket/48807 ############################################################## }}} but {{{py36-readline}}} doesn't exist (yet?). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 17:42:12 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 17:42:12 -0000 Subject: [MacPorts] #53155: Handbrake needs updating Message-ID: <046.00005e5f8650914257b2edbc68373dd3@macports.org> #53155: Handbrake needs updating -----------------------+----------------------- Reporter: keybounce | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: handbrake -----------------------+----------------------- Handbrake got an official release yesterday. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 17:43:20 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 17:43:20 -0000 Subject: [MacPorts] #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies In-Reply-To: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> References: <060.ddd757d8bcc7ad38845ece5e8e7f7d1c@macports.org> Message-ID: <075.a4c69cb51194eea2bd73a8ea66a43603@macports.org> #53138: clang-3.x: fails to build on Mountain Lion, possible circular dependencies -------------------------------------------------+------------------------- Reporter: maxkalashnikov-macports | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: Port: clang-3.3 clang-3.4 clang-3.5 | clang-3.6 clang-3.7 clang-3.8 clang-3.9 | -------------------------------------------------+------------------------- Comment (by jeremyhu): x86_64h is for CPU_SUBTYPE_X86_64_H. It requires Haswell or newer. One solution there is to pick up newer cctools if Xcode's is too old. Or we can just drop that slice. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 18:13:20 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 18:13:20 -0000 Subject: [MacPorts] #53156: upgrade: port:Vc Message-ID: <041.3dc6daddf4253f7a98698f2f7d4f54ae@macports.org> #53156: upgrade: port:Vc ----------------------+----------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: Vc ----------------------+----------------- port:Vc has been upgraded; the attached patch brings it to 1.3.0.14 to get as much support as possible for the latest CPU models. It also uses the Ninja generator from the cmake-1.1 PortGroup, to reduce build resource requires a bit. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 18:15:33 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 18:15:33 -0000 Subject: [MacPorts] #53156: upgrade: port:Vc In-Reply-To: <041.3dc6daddf4253f7a98698f2f7d4f54ae@macports.org> References: <041.3dc6daddf4253f7a98698f2f7d4f54ae@macports.org> Message-ID: <056.100e5ae4f6e0e1b21f0df0e366c9515a@macports.org> #53156: upgrade: port:Vc ---------------------+---------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: Vc | ---------------------+---------------------- Changes (by RJVB): * Attachment "Vc.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 18:21:18 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 18:21:18 -0000 Subject: [MacPorts] #53156: upgrade: port:Vc In-Reply-To: <041.3dc6daddf4253f7a98698f2f7d4f54ae@macports.org> References: <041.3dc6daddf4253f7a98698f2f7d4f54ae@macports.org> Message-ID: <056.169d04e24c7bf403875923b553fd12f6@macports.org> #53156: upgrade: port:Vc ---------------------+---------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: Vc | ---------------------+---------------------- Changes (by mkae): * cc: RJVB (removed) * cc: mkae (added) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 19:14:34 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 19:14:34 -0000 Subject: [MacPorts] #53146: GQRX Install with Mac Ports No Toolbar Icons In-Reply-To: <046.617d24fd37f5fe18495547f3f928a744@macports.org> References: <046.617d24fd37f5fe18495547f3f928a744@macports.org> Message-ID: <061.574c6b858db4aa469beb00453444108c@macports.org> #53146: GQRX Install with Mac Ports No Toolbar Icons ------------------------+----------------------- Reporter: DANAVE3DS | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: gqrx | ------------------------+----------------------- Comment (by DANAVE3DS): I spoke to Alexandru Csete the author who suggested that the dependency was missing and after installing it the icons were there. This was in OSX El Cap and Sierra for V 2.6 of GQRX, I am unsure of earlier versions or earlier OS's... The dependency is needed to properly install the icons, not sure when this changed, as earlier versions of GQRX were fine here on El Cap and earlier OS's, unfortunately I don't have the older installed versions handy to test. Regards Dana -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 19:59:48 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 19:59:48 -0000 Subject: [MacPorts] #48807: python messes with terminal state on exit In-Reply-To: <057.6bd5937ec1e3acdeef099f04c549c3bb@macports.org> References: <057.6bd5937ec1e3acdeef099f04c549c3bb@macports.org> Message-ID: <072.d9d7a54d78e1a1680241d37459a16f44@macports.org> #48807: python messes with terminal state on exit -------------------------------------------------+------------------------- Reporter: yselivanov@… | Owner: | jyrkiwahlstedt Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: haspatch Port: python26 python27 python python34 | python35 libedit | -------------------------------------------------+------------------------- Comment (by fhgwright): Replying to [comment:94 cdeil]: > With {{{sudo port install python36}}} I now see > {{{ > ############################################################## > # IF YOU ARE USING PYTHON FROM THE TERMINAL, PLEASE INSTALL: > # py36-readline > # TO AVOID A LIBEDIT / PYTHON INTERACTION ISSUE. > # REF: https://trac.macports.org/ticket/48807 > ############################################################## > }}} > but {{{py36-readline}}} doesn't exist (yet?). Note that Python 3.6 was only officially released two days ago :-) And unfortunately it's not just a matter of adding the version to the py- readline port. With a (locally generated) py36-readline installed: {{{ MacPro:~ fw$ python3.6 Python 3.6.0 (default, Dec 23 2016, 12:59:30) [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> 1+1 Python(59962,0x7fff7a4d0310) malloc: *** error for object 0x103e7f640: pointer being freed was not allocated *** set a breakpoint in malloc_error_break to debug Abort trap: 6 }}} Without it: {{{ MacPro:~ fw$ python3.6 Python 3.6.0 (default, Dec 23 2016, 12:59:30) [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> 1+1 >>> 2 ^D>>> MacPro:~ fw$ MacPro:~ fw$ MacPro:~ fw$ }}} The latter shows the usual trouble until "stty sane" (unechoed). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 20:08:11 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 20:08:11 -0000 Subject: [MacPorts] #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic In-Reply-To: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> References: <044.379d09e541b4d4aa57a3db1eabbed592@macports.org> Message-ID: <059.1d41831e504530e61105a683782b8410@macports.org> #53150: llvm-3.8: llvm ld: unknown option: -export_dynamic -----------------------+---------------------- Reporter: gbrtrac | Owner: jeremyhu Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: llvm-3.8 | -----------------------+---------------------- Comment (by gbrtrac): That resolved it -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 20:55:52 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 20:55:52 -0000 Subject: [MacPorts] #48807: python messes with terminal state on exit In-Reply-To: <057.6bd5937ec1e3acdeef099f04c549c3bb@macports.org> References: <057.6bd5937ec1e3acdeef099f04c549c3bb@macports.org> Message-ID: <072.cea46b6832021e313598c1934c5b32e2@macports.org> #48807: python messes with terminal state on exit -------------------------------------------------+------------------------- Reporter: yselivanov@… | Owner: | jyrkiwahlstedt Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: haspatch Port: python26 python27 python python34 | python35 libedit | -------------------------------------------------+------------------------- Comment (by eborisch): You can install {{{python36 +readline}}} (python36 with the readline variant). I just tried it and it "worked for me." -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 21:49:23 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 21:49:23 -0000 Subject: [MacPorts] #48807: python messes with terminal state on exit In-Reply-To: <057.6bd5937ec1e3acdeef099f04c549c3bb@macports.org> References: <057.6bd5937ec1e3acdeef099f04c549c3bb@macports.org> Message-ID: <072.b115cb11c6d65395eb5cfea04d54a11c@macports.org> #48807: python messes with terminal state on exit -------------------------------------------------+------------------------- Reporter: yselivanov@… | Owner: | jyrkiwahlstedt Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: haspatch Port: python26 python27 python python34 | python35 libedit | -------------------------------------------------+------------------------- Comment (by fhgwright): Replying to [comment:96 eborisch]: > You can install {{{python36 +readline}}} (python36 with the readline variant). I just tried it and it "worked for me." Yeah, that works. I'd moved away from that approach once py-readline appeared, since it avoids the need to rebuild Python from source due to the non-default variant. What's weird about this (aside from how long libedit's been broken) is that upstream Python uses readline and has to be patched to use libedit, so apparently having a less restrictive license was prioritized over consistency with upstream. It might be nice if the readline variant didn't suggest installing pyXX- readline. :-) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 23:47:45 2016 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2016 23:47:45 -0000 Subject: [MacPorts] #53157: recent base master cannot set configure.compiler from the command line Message-ID: <045.9945ea166069be4ca49084911a24bf4c@macports.org> #53157: recent base master cannot set configure.compiler from the command line ----------------------+----------------- Reporter: jeremyhu | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: Keywords: | Port: ----------------------+----------------- I'm unable to set configure.compiler from the command line like I used to be able to: {{{ ~ $ sudo port -v -s build gnutls configure.compiler=macports-clang-3.7 ---> Computing dependencies for gnutls. ---> Fetching distfiles for gnutls ---> Verifying checksums for gnutls ---> Checksumming gnutls-3.4.17.tar.xz ---> Extracting gnutls ---> Extracting gnutls-3.4.17.tar.xz Executing: cd "/opt/local/var/macports/build /_Users_jeremy_src_macports_macports-ports_devel_gnutls/gnutls/work" && /opt/local/bin/xz -dc '/opt/local/var/macports/distfiles/gnutls/gnutls-3.4.17.tar.xz' | /usr/bin/gnutar --no-same-owner -xf - ---> Applying patches to gnutls ---> Applying patch-tests-pkcs11-pkcs11-mock.c.diff Executing: cd "/opt/local/var/macports/build /_Users_jeremy_src_macports_macports- ports_devel_gnutls/gnutls/work/gnutls-3.4.17" && /usr/bin/patch -p0 < '/Users/jeremy/src/macports/macports-ports/devel/gnutls/files/patch-tests- pkcs11-pkcs11-mock.c.diff' patching file tests/pkcs11/pkcs11-mock.c ---> Patching aes-ssse3-x86.s: /^#/d ---> Patching aes-ssse3-x86_64.s: /^#/d ---> Patching aesni-x86.s: /^#/d ---> Patching aesni-x86_64.s: /^#/d ---> Patching cpuid-x86.s: /^#/d ---> Patching cpuid-x86_64.s: /^#/d ---> Patching e_padlock-x86.s: /^#/d ---> Patching e_padlock-x86_64.s: /^#/d ---> Patching ghash-x86_64.s: /^#/d ---> Patching sha1-ssse3-x86.s: /^#/d ---> Patching sha1-ssse3-x86_64.s: /^#/d ---> Patching sha256-ssse3-x86.s: /^#/d ---> Patching sha512-ssse3-x86.s: /^#/d ---> Patching sha512-ssse3-x86_64.s: /^#/d ---> Configuring gnutls Error: Failed to configure gnutls: Invalid value for configure.compiler: "macports-clang-3.7" Error: See /opt/local/var/macports/logs /_Users_jeremy_src_macports_macports-ports_devel_gnutls/gnutls/main.log for details. Error: Follow https://guide.macports.org/#project.tickets to report a bug. Error: Processing of port gnutls failed }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 01:09:37 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 01:09:37 -0000 Subject: [MacPorts] #53137: Poppler 0.50.0 Undeclared Identifier In-Reply-To: <042.49cecea225fec8a1f7eb28737b564858@macports.org> References: <042.49cecea225fec8a1f7eb28737b564858@macports.org> Message-ID: <057.4f2de0fc22b9a16e0538bce1e875748d@macports.org> #53137: Poppler 0.50.0 Undeclared Identifier ----------------------+---------------------- Reporter: lefte | Owner: dbevans Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: poppler | ----------------------+---------------------- Comment (by mkae): It worked for me on Sierra 10.12.2: {{{ $ sudo port install poppler ---> Computing dependencies for poppler ---> Fetching distfiles for poppler ---> Attempting to fetch poppler-0.50.0.tar.xz from https://poppler.freedesktop.org/ ---> Verifying checksums for poppler ---> Extracting poppler ---> Configuring poppler ---> Building poppler ---> Staging poppler into destroot ---> Installing poppler @0.50.0_1 ---> Activating poppler @0.50.0_1 ---> Cleaning poppler ---> Updating database of binaries ---> Scanning binaries for linking errors ---> No broken files found. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 01:43:54 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 01:43:54 -0000 Subject: [MacPorts] #53153: curl @7.51.0_1: update to 7.52.1 In-Reply-To: <041.976b8eead57598b628eda8efc5dc742b@macports.org> References: <041.976b8eead57598b628eda8efc5dc742b@macports.org> Message-ID: <056.7cd659405d6f6b9ad84b55529676f2d0@macports.org> #53153: curl @7.51.0_1: update to 7.52.1 ---------------------+------------------------ Reporter: l2dy | Owner: ryandesign Type: update | Status: accepted Priority: High | Milestone: Component: ports | Version: Resolution: | Keywords: Port: curl | ---------------------+------------------------ Changes (by ryandesign): * owner: => ryandesign * status: new => accepted * cc: ryandesign (removed) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 01:45:22 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 01:45:22 -0000 Subject: [MacPorts] #53158: qt4-mac-mariadb-plugin causes trouble during upgrade of KDE4 ports Message-ID: <041.d299450d3e6623b4ed6200b2379e070a@macports.org> #53158: qt4-mac-mariadb-plugin causes trouble during upgrade of KDE4 ports --------------------+--------------------- Reporter: mkae | Owner: pixilla Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: --------------------+--------------------- Recently I ran into this oddity with KDE4 ports: {{{ ---> Updating database of binaries ---> Scanning binaries for linking errors ---> Found 5 broken file(s), matching files to ports ---> Found 3 broken port(s), determining rebuild order ---> Rebuilding in order kdepimlibs4 @4.14.3 kde4-runtime @4.14.4.20150225 +samba kmymoney4-devel @4.8-20161022 Warning: No port py27-gtk found in the index. ---> Computing dependencies for qt4-mac-mysql5-plugin Error: Unable to exec port: Can't install qt4-mac-mysql5-plugin because conflicting ports are active: qt4-mac-mariadb-plugin Error rebuilding kdepimlibs4 }}} Why is it that those KDE4 ports suddenly want the {{{mysql5}}} plugin and are not happy with the installed {{{mariadb}}} plugins anymore? I have already uninstalled {{{konversation}}}, but as shown above there are more troubling ports... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 01:47:28 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 01:47:28 -0000 Subject: [MacPorts] #53157: recent base master cannot set configure.compiler from the command line In-Reply-To: <045.9945ea166069be4ca49084911a24bf4c@macports.org> References: <045.9945ea166069be4ca49084911a24bf4c@macports.org> Message-ID: <060.94ebdaea6de518c5e5081b848a72fb6e@macports.org> #53157: recent base master cannot set configure.compiler from the command line -----------------------+----------------- Reporter: jeremyhu | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: Resolution: | Keywords: Port: | -----------------------+----------------- Changes (by ryandesign): * cc: ryandesign (added) Comment: I assume this is the same issue as #53113. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 01:48:00 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 01:48:00 -0000 Subject: [MacPorts] #53113: expected boolean value but got ""no"" In-Reply-To: <047.4dfc9c6163c3085f1a025bdeeb3958e5@macports.org> References: <047.4dfc9c6163c3085f1a025bdeeb3958e5@macports.org> Message-ID: <062.0dde282587620bd9c0c2447be73b6bc4@macports.org> #53113: expected boolean value but got ""no"" -------------------------+-------------------- Reporter: ryandesign | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: | Keywords: Port: | -------------------------+-------------------- Comment (by ryandesign): Similar problem reported for inability to set `configure.compiler` on the command line in #53157. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 01:49:04 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 01:49:04 -0000 Subject: [MacPorts] #53153: curl @7.51.0_1: update to 7.52.1 In-Reply-To: <041.976b8eead57598b628eda8efc5dc742b@macports.org> References: <041.976b8eead57598b628eda8efc5dc742b@macports.org> Message-ID: <056.4eefb328ee8fd3ff3bc843185fcd2078@macports.org> #53153: curl @7.51.0_1: update to 7.52.1 ---------------------+------------------------ Reporter: l2dy | Owner: ryandesign Type: update | Status: closed Priority: High | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: curl | ---------------------+------------------------ Changes (by ryandesign): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"a154b1af4c5387df8666bb82bf42178ef831dc06/macports-ports" a154b1af/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="a154b1af4c5387df8666bb82bf42178ef831dc06" curl: Update to 7.52.1 Closes: https://trac.macports.org/ticket/53153 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 02:06:47 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 02:06:47 -0000 Subject: [MacPorts] #53156: upgrade: port:Vc In-Reply-To: <041.3dc6daddf4253f7a98698f2f7d4f54ae@macports.org> References: <041.3dc6daddf4253f7a98698f2f7d4f54ae@macports.org> Message-ID: <056.0ab88648a78a71457132d86bcee198b0@macports.org> #53156: upgrade: port:Vc ---------------------+---------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: Vc | ---------------------+---------------------- Comment (by ryandesign): A static library is still a library, isn't it? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 02:42:49 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 02:42:49 -0000 Subject: [MacPorts] #53151: ld64-latest: handeling tbd files In-Reply-To: <056.29f019982176bcf6547cbdbe183768d5@macports.org> References: <056.29f019982176bcf6547cbdbe183768d5@macports.org> Message-ID: <071.9226346d4bdc268297132b8411c70cb0@macports.org> #53151: ld64-latest: handeling tbd files ----------------------------------+------------------------ Reporter: MarcusCalhoun-Lopez | Owner: jeremyhu@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: invalid | Keywords: Port: ld64-latest | ----------------------------------+------------------------ Comment (by jeremyhu): Thanks. Every dupe helps. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 06:15:57 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 06:15:57 -0000 Subject: [MacPorts] #53139: gcc7 update In-Reply-To: <043.ee044657c3df4809f8316644719c337e@macports.org> References: <043.ee044657c3df4809f8316644719c337e@macports.org> Message-ID: <058.43518c0d288aeca24165b22ce19baac0@macports.org> #53139: gcc7 update ---------------------+------------------------ Reporter: rouson | Owner: ryandesign Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: gcc7 | ---------------------+------------------------ Changes (by ryandesign): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"c11df6b3e4867171fff9438ba499e20f31b449e8/macports-ports" c11df6b3/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="c11df6b3e4867171fff9438ba499e20f31b449e8" gcc7: Update to 7-20161225 Closes: https://trac.macports.org/ticket/53139 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 08:23:27 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 08:23:27 -0000 Subject: [MacPorts] #53156: upgrade: port:Vc In-Reply-To: <041.3dc6daddf4253f7a98698f2f7d4f54ae@macports.org> References: <041.3dc6daddf4253f7a98698f2f7d4f54ae@macports.org> Message-ID: <056.a55c9c88221983dd48db0e8f195847b4@macports.org> #53156: upgrade: port:Vc ---------------------+---------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: Vc | ---------------------+---------------------- Comment (by RJVB): True, so since you raise the point: what exactly is the variable used for? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 08:35:24 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 08:35:24 -0000 Subject: [MacPorts] #53158: qt4-mac-mariadb-plugin causes trouble during upgrade of KDE4 ports In-Reply-To: <041.d299450d3e6623b4ed6200b2379e070a@macports.org> References: <041.d299450d3e6623b4ed6200b2379e070a@macports.org> Message-ID: <056.5312f2bf71243d656f5746adf097123e@macports.org> #53158: qt4-mac-mariadb-plugin causes trouble during upgrade of KDE4 ports ---------------------+--------------------- Reporter: mkae | Owner: pixilla Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | ---------------------+--------------------- Comment (by RJVB): I haven't traced this to see who depends on the mysql plugin but it would seem that a path:-style depspec has been replaced with an explicit depspec, or an update to a shared dependency introduced this new depspec. I'd also raise the question why there have to individual mysql5 and mariadb plugins. AFAIK the whole idea after MariaDB is that it's a drop-in replacement for the regular MySql. The corresponding Qt5 plugin uses variants, but it would certainly be possible to use only path:-style depspecs (if port:mysql5x and port:mariadb were mutually exclusive alternatives). Whe -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 08:49:37 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 08:49:37 -0000 Subject: [MacPorts] #53159: clang-3.8 fails to build on Mountain Lion unless cctools is installed Message-ID: <045.103b098a0785242a9a27a134ff820829@macports.org> #53159: clang-3.8 fails to build on Mountain Lion unless cctools is installed ----------------------+----------------- Reporter: jeremyhu | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: ----------------------+----------------- https://build.macports.org/builders/ports-10.8_x86_64_legacy- builder/builds/13642 {{{ -- Got ld supported ARCHES: i386 x86_64 x86_64h armv6 armv7 armv7s armv7m armv7k arm64 (tvOS) -- Toolchain supported arches: i386;x86_64;x86_64h;armv6;armv7;armv7s;armv7m;armv7k;arm64;(tvOS) -- Finding valid architectures for osx... -- OSX supported arches: i386;x86_64;x86_64h -- Finding valid architectures for 10.4... -- OSX 10.4 supported arches: i386;x86_64;x86_64h -- Compiler-RT supported architectures: i386;x86_64;x86_64h --- [ 60%] Generating ../../../../lib/clang/3.8.1/lib/darwin/libclang_rt.cc_kext.a cd /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_llvm-3.8/clang-3.8/work/build/projects /compiler-rt/lib/builtins && /opt/local/bin/cmake -E make_directory /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_llvm-3.8/clang-3.8/work/build/./lib/clang/3.8.1/lib/darwin cd /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_llvm-3.8/clang-3.8/work/build/projects /compiler-rt/lib/builtins && lipo -output /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_llvm-3.8/clang-3.8/work/build/./lib/clang/3.8.1/lib/darwin/libclang_rt.cc_kext.a -create -arch i386 /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_llvm-3.8/clang-3.8/work/build/lib/libclang_rt.cc_kext_i386_osx.a -arch x86_64 /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_llvm-3.8/clang-3.8/work/build/lib/libclang_rt.cc_kext_x86_64_osx.a -arch x86_64h /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_llvm-3.8/clang-3.8/work/build/lib/libclang_rt.cc_kext_x86_64h_osx.a lipo: unknown architecture specification flag: x86_64h in specifying input file -arch x86_64h /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_llvm-3.8/clang-3.8/work/build/lib/libclang_rt.cc_kext_x86_64h_osx.a lipo: known architecture flags are: any little big ppc64 x86_64 ppc970-64 ppc i386 m68k hppa sparc m88k i860 veo arm ppc601 ppc603 ppc603e ppc603ev ppc604 ppc604e ppc750 ppc7400 ppc7450 ppc970 i486 i486SX pentium i586 pentpro i686 pentIIm3 pentIIm5 pentium4 m68030 m68040 hppa7100LC veo1 veo2 veo3 veo4 armv4t armv5 xscale armv6 armv7 armv7f armv7k lipo: Usage: lipo [input_file] ... [-arch input_file] ... [-info] [-detailed_info] [-output output_file] [-create] [-arch_blank ] [-thin ] [-remove ] ... [-extract ] ... [-extract_family ] ... [-verify_arch ...] [-replace ] ... make[2]: *** [lib/clang/3.8.1/lib/darwin/libclang_rt.cc_kext.a] Error 1 make[2]: Leaving directory `/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_llvm-3.8/clang-3.8/work/build' make[1]: *** [projects/compiler- rt/lib/builtins/CMakeFiles/clang_rt.cc_kext.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs.... }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 09:05:37 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 09:05:37 -0000 Subject: [MacPorts] #53159: clang-3.8 fails to build on Mountain Lion unless cctools is installed In-Reply-To: <045.103b098a0785242a9a27a134ff820829@macports.org> References: <045.103b098a0785242a9a27a134ff820829@macports.org> Message-ID: <060.a64306512accfcfcafd83af78ce82023@macports.org> #53159: clang-3.8 fails to build on Mountain Lion unless cctools is installed -----------------------+---------------------- Reporter: jeremyhu | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: | -----------------------+---------------------- Changes (by jeremyhu): * status: new => closed * owner: => jeremyhu * resolution: => fixed Comment: In [changeset:"d27b8091bef84bc219d4ed2c29037e8937cce536/macports-ports" d27b8091/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="d27b8091bef84bc219d4ed2c29037e8937cce536" clang-{3.8,3.9,devel}: Add a build dependency on cctools when Xcode's lipo doesn't support x86_64h Fixes https://trac.macports.org/ticket/53159 Signed-off-by: Jeremy Huddleston Sequoia }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 10:08:03 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 10:08:03 -0000 Subject: [MacPorts] #53154: qhull seems to fail systematically when called from octave In-Reply-To: <044.b2f66d585e240ba60d5800db45e93af9@macports.org> References: <044.b2f66d585e240ba60d5800db45e93af9@macports.org> Message-ID: <059.c91f5e417316bffaeda7f6591c745769@macports.org> #53154: qhull seems to fail systematically when called from octave ---------------------------+--------------------------------- Reporter: pierard | Owner: MarcusCalhoun-Lopez Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: octave qhull | ---------------------------+--------------------------------- Changes (by MarcusCalhoun-Lopez): * status: new => accepted * owner: => MarcusCalhoun-Lopez Comment: I can not reproduce this error.[[BR]] Would you please post the results of {{{octave --version}}}. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 10:39:34 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 10:39:34 -0000 Subject: [MacPorts] #53154: qhull seems to fail systematically when called from octave In-Reply-To: <044.b2f66d585e240ba60d5800db45e93af9@macports.org> References: <044.b2f66d585e240ba60d5800db45e93af9@macports.org> Message-ID: <059.ae84965101d7d58842f13c8ad2f6a7cf@macports.org> #53154: qhull seems to fail systematically when called from octave ---------------------------+--------------------------------- Reporter: pierard | Owner: MarcusCalhoun-Lopez Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: octave qhull | ---------------------------+--------------------------------- Comment (by pierard): Here are all informations about the installed versions. {{{ port installed qhull The following ports are currently installed: qhull @2015.2_1 (active) }}} {{{ port installed octave The following ports are currently installed: octave @4.2.0_1+accelerate+app+docs+fltk+gfortran+graphicsmagick+qt4+sound (active) }}} {{{ octave --version GNU Octave, version 4.2.0 Copyright (C) 2016 John W. Eaton and others. This is free software; see the source code for copying conditions. There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Octave was configured for "x86_64-apple-darwin15.x.x". Additional information about Octave is available at http://www.octave.org. Please contribute if you find this software useful. For more information, visit http://www.octave.org/get-involved.html }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 10:57:39 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 10:57:39 -0000 Subject: [MacPorts] #53154: qhull seems to fail systematically when called from octave In-Reply-To: <044.b2f66d585e240ba60d5800db45e93af9@macports.org> References: <044.b2f66d585e240ba60d5800db45e93af9@macports.org> Message-ID: <059.fdd777f1a2121578a0cf2be23c2a2532@macports.org> #53154: qhull seems to fail systematically when called from octave ---------------------------+--------------------------------- Reporter: pierard | Owner: MarcusCalhoun-Lopez Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: octave qhull | ---------------------------+--------------------------------- Comment (by pierard): And, as qhull needs to parse stdin, I think the current locale might also be relevant: {{{ defaults read -g AppleLocale fr_BE }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 13:25:19 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 13:25:19 -0000 Subject: [MacPorts] #53137: Poppler 0.50.0 Undeclared Identifier In-Reply-To: <042.49cecea225fec8a1f7eb28737b564858@macports.org> References: <042.49cecea225fec8a1f7eb28737b564858@macports.org> Message-ID: <057.1ef74bc0b0700b02656029346c040d0d@macports.org> #53137: Poppler 0.50.0 Undeclared Identifier ----------------------+---------------------- Reporter: lefte | Owner: dbevans Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: poppler | ----------------------+---------------------- Comment (by dbevans): The build works for me as well on Sierra and earlier systems and on the buildbots so there seems to be an issue specific to your installation. I suggest updating your ports and trying a clean install of poppler. {{{ sudo port selfupdate sudo port clean poppler sudo port install poppler }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 14:21:30 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 14:21:30 -0000 Subject: [MacPorts] #52247: rust 1.11.0 build hangs indefinitely on macos 10.12 (Sierra) In-Reply-To: <054.ea23676a7329d7d0cee044ab1a242f30@macports.org> References: <054.ea23676a7329d7d0cee044ab1a242f30@macports.org> Message-ID: <069.877939c06db1157d74b8491ceed21825@macports.org> #52247: rust 1.11.0 build hangs indefinitely on macos 10.12 (Sierra) ------------------------+-------------------- Reporter: r.keoni@… | Owner: g5pw Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: sierra Port: rust | ------------------------+-------------------- Comment (by mohd-akram): Rust is at 1.14.0 now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 14:53:26 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 14:53:26 -0000 Subject: [MacPorts] #53113: expected boolean value but got ""no"" In-Reply-To: <047.4dfc9c6163c3085f1a025bdeeb3958e5@macports.org> References: <047.4dfc9c6163c3085f1a025bdeeb3958e5@macports.org> Message-ID: <062.3c9378faf370c766f17f6e3be2b57222@macports.org> #53113: expected boolean value but got ""no"" -------------------------+-------------------- Reporter: ryandesign | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: | Keywords: Port: | -------------------------+-------------------- Changes (by kurthindenburg): * cc: khindenburg, jmroot (added) Comment: From what I gather using git bisect, this was the commit {{{ commit 59bceb47a4eb7ce3e354069220fbbaeba7544cf3 Author: Joshua Root Date: Wed Nov 30 08:59:01 2016 +1100 improve quoting of 'interp eval' args Having a single argument, preferably braced to guarantee that no substitution will happen, reduces the amount of string processing and may enable byte compilation in some cases. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 18:40:34 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 18:40:34 -0000 Subject: [MacPorts] #53155: HandBrake: update to 1.0.0 (was: Handbrake needs updating) In-Reply-To: <046.00005e5f8650914257b2edbc68373dd3@macports.org> References: <046.00005e5f8650914257b2edbc68373dd3@macports.org> Message-ID: <061.5aef6a4e8cb61ffb03022a1d9a85872c@macports.org> #53155: HandBrake: update to 1.0.0 ------------------------+---------------------- Reporter: keybounce | Owner: larryv Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: HandBrake | ------------------------+---------------------- Changes (by ryandesign): * status: new => assigned * cc: larryv@… (removed) * port: handbrake => HandBrake * owner: => larryv -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 19:49:20 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 19:49:20 -0000 Subject: [MacPorts] #52582: ghc @7.8.3_4: RTS incompatibility with Sierra In-Reply-To: <047.31ef8be7dd7559a12bcd7c2b768f2d94@macports.org> References: <047.31ef8be7dd7559a12bcd7c2b768f2d94@macports.org> Message-ID: <062.0fc6bc631cb666862cc8169370aacd91@macports.org> #52582: ghc @7.8.3_4: RTS incompatibility with Sierra -------------------------+----------------------------- Reporter: shanemikel | Owner: neverpanic Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: sierra haspatch Port: ghc | -------------------------+----------------------------- Comment (by rbq): Could someone™ please provide noob-proof instructions on how to apply the patch? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 20:17:49 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 20:17:49 -0000 Subject: [MacPorts] #52852: libgcc-devel does not provide libgforgran In-Reply-To: <046.c9ca08fa59e173470e1aa2f3d84dd572@macports.org> References: <046.c9ca08fa59e173470e1aa2f3d84dd572@macports.org> Message-ID: <061.10859f34a95b8a560a4502ee8b390823@macports.org> #52852: libgcc-devel does not provide libgforgran ---------------------------+-------------------- Reporter: michaelld | Owner: mww@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: libgcc-devel | ---------------------------+-------------------- Changes (by michaelld): * status: new => closed * resolution: => fixed Comment: libgcc-devel @7-20161225_0 fixes this issue, providing "libgfortran.4.dylib" ... which is different than the prior "libgfortran.3.dylib" so I'd guess many Fortran dependent ports will require a rev-bump. I'm going to close this ticket as fixed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 23:45:59 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 23:45:59 -0000 Subject: [MacPorts] #53157: recent base master cannot set configure.compiler from the command line In-Reply-To: <045.9945ea166069be4ca49084911a24bf4c@macports.org> References: <045.9945ea166069be4ca49084911a24bf4c@macports.org> Message-ID: <060.92cb30cc6f9dedd8b9e9fb9fe8af1e52@macports.org> #53157: recent base master cannot set configure.compiler from the command line ------------------------+-------------------- Reporter: jeremyhu | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: Resolution: duplicate | Keywords: Port: | ------------------------+-------------------- Changes (by jmroot): * status: new => closed * resolution: => duplicate -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 23:46:50 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 23:46:50 -0000 Subject: [MacPorts] #53113: options set from the command line have incorrect extra quotes added (was: expected boolean value but got ""no"") In-Reply-To: <047.4dfc9c6163c3085f1a025bdeeb3958e5@macports.org> References: <047.4dfc9c6163c3085f1a025bdeeb3958e5@macports.org> Message-ID: <062.045a588026b7d3d33587ec0e3013dd9d@macports.org> #53113: options set from the command line have incorrect extra quotes added -------------------------+-------------------- Reporter: ryandesign | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: | Keywords: Port: | -------------------------+-------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 23:47:30 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 23:47:30 -0000 Subject: [MacPorts] #53113: options set from the command line have incorrect extra quotes added In-Reply-To: <047.4dfc9c6163c3085f1a025bdeeb3958e5@macports.org> References: <047.4dfc9c6163c3085f1a025bdeeb3958e5@macports.org> Message-ID: <062.e732422d73c79d90d478203edfa5332a@macports.org> #53113: options set from the command line have incorrect extra quotes added -------------------------+-------------------- Reporter: ryandesign | Owner: jmroot Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: fixed | Keywords: Port: | -------------------------+-------------------- Changes (by jmroot): * status: new => closed * owner: => jmroot * resolution: => fixed Comment: In [changeset:"06daa26f0e53e9bd01c0a6bc69b2a3fa30edfe33/macports-base" 06daa26/macports-base]: {{{ #!ConfigurableCommitTicketReference repository="macports-base" revision="06daa26f0e53e9bd01c0a6bc69b2a3fa30edfe33" Don't overquote values of command line options This was previously needed because they were not correctly quoted when used elsewhere, but that was fixed. Fixes: https://trac.macports.org/ticket/53113 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 23:49:18 2016 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2016 23:49:18 -0000 Subject: [MacPorts] #53113: options set from the command line have incorrect extra quotes added In-Reply-To: <047.4dfc9c6163c3085f1a025bdeeb3958e5@macports.org> References: <047.4dfc9c6163c3085f1a025bdeeb3958e5@macports.org> Message-ID: <062.c4ae87ed6338ffc386931b2cc0f2b295@macports.org> #53113: options set from the command line have incorrect extra quotes added -------------------------+-------------------- Reporter: ryandesign | Owner: jmroot Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: fixed | Keywords: Port: | -------------------------+-------------------- Changes (by jmroot): * cc: khindenburg (removed) * cc: kurthindenburg (added) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 06:20:29 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 06:20:29 -0000 Subject: [MacPorts] #52582: ghc @7.8.3_4: RTS incompatibility with Sierra In-Reply-To: <047.31ef8be7dd7559a12bcd7c2b768f2d94@macports.org> References: <047.31ef8be7dd7559a12bcd7c2b768f2d94@macports.org> Message-ID: <062.4e2b928c3e11193309b5da92bf3b248d@macports.org> #52582: ghc @7.8.3_4: RTS incompatibility with Sierra -------------------------+----------------------------- Reporter: shanemikel | Owner: neverpanic Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: sierra haspatch Port: ghc | -------------------------+----------------------------- Comment (by sunoterra): Replying to [comment:24 rbq]: > Could someone™ please provide noob-proof instructions on how to apply the patch? https://trac.macports.org/wiki/howto/PatchLocal it's pretty much that process, replace `arb` with `ghc` obviously, and do not use the "-devel" suffix in your naming. instead manually updating source, like in the example, just add this file: https://trac.macports.org/raw-attachment/ticket/52582/patch-Fix-GetTime.c -on-Darwin-with-clock_gettime.diff to your patches (i.e. `cp ~/Dowloads/patch-Fix-GetTime.c-on-Darwin-with- clock_gettime.diff $(port dir ghc)/files/` after the indexing of the local ports repo is done). and patch your Portfile with: https://trac.macports.org/raw-attachment/ticket/52582/Portfile.diff (`cd $(port dir ghc)` and `patch -p0 < ~/Downloads/Portfile.diff`) clean and build to verify. NB: if your are installing this as a dependency to pandoc, as i am, just re-run your command to install that and let it finish installing ghc; otherwise, `sudo port unsetrequested ghc` after you install it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 11:28:52 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 11:28:52 -0000 Subject: [MacPorts] #52613: Guile-2.0.13 fails to build on Sierra In-Reply-To: <047.ac972e8ff213b95746deb5f6352988fa@macports.org> References: <047.ac972e8ff213b95746deb5f6352988fa@macports.org> Message-ID: <062.089f74998e991f7097663e26a482f397@macports.org> #52613: Guile-2.0.13 fails to build on Sierra -------------------------+-------------------------------- Reporter: mouse07410 | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: sierra Port: guile | -------------------------+-------------------------------- Comment (by eddieh): Replying to [comment:10 ken-cunningham-webuse]: > You can do this for any port you like, whenever you like. > > wiki:howto/InstallingOlderPort > > first find it > {{{ > > $ port info guile > guile @2.0.13 (lang) > }}} > > then go to the svn repo > > browser:trunk/dports/lang/guile > > click on 'revision log' (top right ) > > select any revision you want ( goes back 14 years) > > note the revision number, e.g. 151758 > > and check it out > > {{{ > $ svn checkout -r 151758 https://svn.macports.org/repository/macports/trunk/dports/lang/guile > }}} > > go into the directory where you downloaded that info > > and build it > > {{{ > sudo port install > }}} > > you are done. > > add it to your own local rep and it'll never ask to be updated again. > Unfortunately, this failed to build as well. On 10.12.1 (16B2657). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 14:59:19 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 14:59:19 -0000 Subject: [MacPorts] #53160: Update to Portfile -- WW Message-ID: <044.f37e52c7cb7a6c26585fb132fec29e37@macports.org> #53160: Update to Portfile -- WW --------------------------+----------------- Reporter: tazzben | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: update ports | Port: WW --------------------------+----------------- This is a small update to the port WW. The only change to the port file is the checksums and the version on github referenced. I've uploaded both a diff and the entire port file. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 14:59:38 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 14:59:38 -0000 Subject: [MacPorts] #53160: Update to Portfile -- WW In-Reply-To: <044.f37e52c7cb7a6c26585fb132fec29e37@macports.org> References: <044.f37e52c7cb7a6c26585fb132fec29e37@macports.org> Message-ID: <059.1d8857451db82610aee1e6a0cc9c05ae@macports.org> #53160: Update to Portfile -- WW ----------------------+-------------------------- Reporter: tazzben | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: update ports Port: WW | ----------------------+-------------------------- Changes (by tazzben): * Attachment "Portfile-WW.diff" added. Portfile Diff -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 14:59:55 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 14:59:55 -0000 Subject: [MacPorts] #53160: Update to Portfile -- WW In-Reply-To: <044.f37e52c7cb7a6c26585fb132fec29e37@macports.org> References: <044.f37e52c7cb7a6c26585fb132fec29e37@macports.org> Message-ID: <059.96a7a73a1f690cc848e1822afa6b9df7@macports.org> #53160: Update to Portfile -- WW ----------------------+-------------------------- Reporter: tazzben | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: update ports Port: WW | ----------------------+-------------------------- Changes (by tazzben): * Attachment "Portfile" added. WW Portfile -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 15:13:37 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 15:13:37 -0000 Subject: [MacPorts] #50671: boost: Update to 1.62.0 In-Reply-To: <045.068f49dfc49c577073cb3ffe59aec898@macports.org> References: <045.068f49dfc49c577073cb3ffe59aec898@macports.org> Message-ID: <060.9129b759492fc2d985101bc4d7827132@macports.org> #50671: boost: Update to 1.62.0 -----------------------+------------------------ Reporter: eborisch | Owner: ryandesign Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch Port: boost | -----------------------+------------------------ Comment (by michaelld): Boost 1.63.0 has been released. I'll be updating this branch & testing with my boost ports shortly. I'll also attach a patch to this ticket for folks interested in trying out this new boost version. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 15:17:07 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 15:17:07 -0000 Subject: [MacPorts] #50671: boost: Update to 1.63.0 (was: boost: Update to 1.62.0) In-Reply-To: <045.068f49dfc49c577073cb3ffe59aec898@macports.org> References: <045.068f49dfc49c577073cb3ffe59aec898@macports.org> Message-ID: <060.960577fc85e0b0c5368318dcdf300163@macports.org> #50671: boost: Update to 1.63.0 -----------------------+------------------------ Reporter: eborisch | Owner: ryandesign Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch Port: boost | -----------------------+------------------------ -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 15:55:49 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 15:55:49 -0000 Subject: [MacPorts] #47327: tuntaposx: Please update to 20150118 In-Reply-To: <055.ac7bc8c29504d7df76885e715888e6d0@macports.org> References: <055.ac7bc8c29504d7df76885e715888e6d0@macports.org> Message-ID: <070.9f7bb37f0dc082db9e694fda17a74f0a@macports.org> #47327: tuntaposx: Please update to 20150118 ------------------------+-------------------------------- Reporter: william@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: tuntaposx | ------------------------+-------------------------------- Comment (by mojca): In [changeset:"c9defaa7d163c3f77c7fd7b34d7a35630ba6a801/macports-ports" c9defaa7/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="c9defaa7d163c3f77c7fd7b34d7a35630ba6a801" tuntaposx: update to 20150118 See: https://trac.macports.org/ticket/47327 See: https://github.com/macports/macports-ports/pull/119 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 16:08:05 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 16:08:05 -0000 Subject: [MacPorts] #40327: tuntaposx @20111101 - Building failure In-Reply-To: <056.ed2c583d47a0e4b609ab76796da7c6d2@macports.org> References: <056.ed2c583d47a0e4b609ab76796da7c6d2@macports.org> Message-ID: <071.9769844bafb86cdccf8823ef38b39a6d@macports.org> #40327: tuntaposx @20111101 - Building failure --------------------------+-------------------------------- Reporter: interflap@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: tuntaposx | --------------------------+-------------------------------- Comment (by mojca): I updated the port (see #47327), but I didn't do any testing under 10.5 (or 10.4). The least we could do is blacklist a compiler, but that's tricky to do if we don't have any Tiger installation where we could test (or a Tiger user to do that for us). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 16:11:22 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 16:11:22 -0000 Subject: [MacPorts] #53161: tuntaposx: kernel extensions have to be signed Message-ID: <042.dbbacad56cde2bf4f27403f06b8719a1@macports.org> #53161: tuntaposx: kernel extensions have to be signed ---------------------------------------+----------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: yosemite elcapitan sierra | Port: tuntaposx ---------------------------------------+----------------------- See #47327: Citing: > ... there be dragons on Yosemite, since unless a a flag in nvram is altered, kernel extensions are required to be signed ![1]. > > Updating the version to current is a first step towards achieving something useful on Yosemite, in any case! Perhaps until some way of allowing the kexts to be signed (when a user has sufficient apple developer credentials) is developed an addition to this port's notes would be appropriate, indicating the nvram workaround required on yosemite. > > Aside: I have successfully installed the binary version from sourceforge, which is working fine on Yosemite. > > ![1] http://sourceforge.net/p/tuntaposx/mailman/message/32950567/ -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 16:12:32 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 16:12:32 -0000 Subject: [MacPorts] #47327: tuntaposx: Please update to 20150118 In-Reply-To: <055.ac7bc8c29504d7df76885e715888e6d0@macports.org> References: <055.ac7bc8c29504d7df76885e715888e6d0@macports.org> Message-ID: <070.957bd915299dd825a503b7b4d79694c2@macports.org> #47327: tuntaposx: Please update to 20150118 ------------------------+-------------------------------- Reporter: william@… | Owner: macports-tickets@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: tuntaposx | ------------------------+-------------------------------- Changes (by mojca): * status: new => closed * resolution: => fixed Comment: I updated the port (like it was mentioned in the PR above), but didn't do any testing of the functionality beyond making sure that it installs cleanly and I didn't test whether it still compiles on Leopard. A build failure on Tiger is listed in #40327. In particular I didn't do anything at all to address the problem with signing extensions. I blindly opened a new ticket under #53161 and want to leave it up to others to figure out what to do with that. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 16:27:23 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 16:27:23 -0000 Subject: [MacPorts] #52827: yarn @0.16.1 In-Reply-To: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> References: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> Message-ID: <061.b256cb79bbe6ab679c086ef2541db038@macports.org> #52827: yarn @0.16.1 -------------------------+-------------------------------- Reporter: isomarcte | Owner: macports-tickets@… Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: duplicate | Keywords: Port: yarn | -------------------------+-------------------------------- Changes (by mojca): * status: new => closed * version: 2.3.4 => * resolution: => duplicate -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 17:07:32 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 17:07:32 -0000 Subject: [MacPorts] #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X In-Reply-To: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> References: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> Message-ID: <061.18193627fdde8a56288807c590c00867@macports.org> #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X ------------------------+--------------------------- Reporter: ballapete | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: tiger powerpc Port: libuv | ------------------------+--------------------------- Comment (by kencu): This port does build on both 10.5 PPC and 10.5 Leopard, and up. The issues with it building on 10.4 PPC are probably something that could be overcome (usually these things are POSIX define mixups on 10.4 -- this didn't really get straightened out until 10.5). As there is no real need for libuv at the moment other than Cmake (which has a good workaround as above) I don't imagine I'll be spending any time on this to fix it. So as far as I'm personally concerned, this could be closed as 'wontfix'. I'll pass along the cmake tiger fix to michael and see what he thinks about incorporating it into macports. For the moment, it sits in my custom TigerPorts repo at for anyone who might want it (along with lots of other Tiger fixes). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 17:23:16 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 17:23:16 -0000 Subject: [MacPorts] #53123: botan links against libstdc++ on 10.6 with libcxx, preventing qca from building. And workaround. In-Reply-To: <042.c6ed3875ce93ad7a203783ef4a68231d@macports.org> References: <042.c6ed3875ce93ad7a203783ef4a68231d@macports.org> Message-ID: <057.8324fcb63578b6fa989d3b7207ac548d@macports.org> #53123: botan links against libstdc++ on 10.6 with libcxx, preventing qca from building. And workaround. ---------------------+------------------------- Reporter: kencu | Owner: mww@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: botan | ---------------------+------------------------- Comment (by kencu): The slightly patched versions of clang-3.7, clang-3.8, and clang-3.9 have indeed solved this problem for me (and the other listed problems in comment 2 above). Jeremy quite correctly points out that changing the default behaviour of a compiler can have unforeseen troubles, so he doesn't recommend this approach for general use at present. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 17:35:12 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 17:35:12 -0000 Subject: [MacPorts] #53160: Update to Portfile -- WW In-Reply-To: <044.f37e52c7cb7a6c26585fb132fec29e37@macports.org> References: <044.f37e52c7cb7a6c26585fb132fec29e37@macports.org> Message-ID: <059.d3414197e78cd4c7b7af3afef513939c@macports.org> #53160: Update to Portfile -- WW ----------------------+--------------------------------- Reporter: tazzben | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: WW | ----------------------+--------------------------------- Changes (by mf2k): * keywords: update ports => haspatch maintainer * type: defect => update Comment: Thank you! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 19:21:45 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 19:21:45 -0000 Subject: [MacPorts] #50671: boost: Update to 1.63.0 In-Reply-To: <045.068f49dfc49c577073cb3ffe59aec898@macports.org> References: <045.068f49dfc49c577073cb3ffe59aec898@macports.org> Message-ID: <060.1e8f787bd00377aa3245c17fc341d3be@macports.org> #50671: boost: Update to 1.63.0 -----------------------+------------------------ Reporter: eborisch | Owner: ryandesign Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch Port: boost | -----------------------+------------------------ Comment (by michaelld): Update is in place in the same branch (https://github.com/macports /macports-ports/tree/boost_update), which is refreshed to the current MP GIT master. I'll attach a patch as well, which folks can test using something like (assuming "~/Downloads/boost_update_to_1.63.0.diff" is where the patch is downloaded to): {{{ cd $(port dir boost) sudo chmod -R a+rw . patch -p0 < ~/Downloads/boost_update_to_1.63.0.diff sudo port selfupdate }}} and, then the new boost should be built and installed. For my Boost using ports, this update works after rebuilding them; these libraries are not drop-in ABI replacements for either 1.59.0 or 1.62.0. Please submit feedback on this ticket. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 19:22:11 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 19:22:11 -0000 Subject: [MacPorts] #50671: boost: Update to 1.63.0 In-Reply-To: <045.068f49dfc49c577073cb3ffe59aec898@macports.org> References: <045.068f49dfc49c577073cb3ffe59aec898@macports.org> Message-ID: <060.8ce3e6a2a64cd2cbbde23b6d44aea267@macports.org> #50671: boost: Update to 1.63.0 -----------------------+------------------------ Reporter: eborisch | Owner: ryandesign Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch Port: boost | -----------------------+------------------------ Changes (by michaelld): * Attachment "boost_update_to_1.63.0.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 19:26:56 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 19:26:56 -0000 Subject: [MacPorts] #53162: py-astropy: update to 1.3 Message-ID: <045.9398f0ce5ffacd90395e2651f8305f8c@macports.org> #53162: py-astropy: update to 1.3 ----------------------+------------------------ Reporter: lpsinger | Owner: robitaille Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: py-astropy ----------------------+------------------------ Astropy 1.3 is available: http://docs.astropy.org/en/stable/whatsnew/1.3.html -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 19:55:27 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 19:55:27 -0000 Subject: [MacPorts] #50671: boost: Update to 1.63.0 In-Reply-To: <045.068f49dfc49c577073cb3ffe59aec898@macports.org> References: <045.068f49dfc49c577073cb3ffe59aec898@macports.org> Message-ID: <060.631b634b7d25fcaab0cbf7729cc24bb4@macports.org> #50671: boost: Update to 1.63.0 -----------------------+------------------------ Reporter: eborisch | Owner: ryandesign Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch Port: boost | -----------------------+------------------------ Comment (by michaelld): Here's the command I use (approximately) to update boost dependent ports: {{{ sudo -s for tf in ${port dependents boost | awk '{ print $1 }'}; do \ port -n upgrade --force ${tf} \ done }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 20:24:36 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 20:24:36 -0000 Subject: [MacPorts] #53152: scons does not honor $PATH In-Reply-To: <045.7ecd78b417e4568b5ca942705e3aa5fc@macports.org> References: <045.7ecd78b417e4568b5ca942705e3aa5fc@macports.org> Message-ID: <060.bc620832c1437256e683c72e13678e82@macports.org> #53152: scons does not honor $PATH -----------------------+----------------- Reporter: jeremyhu | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: scons | -----------------------+----------------- Comment (by ryandesign): Replying to [comment:3 jeremyhu]: > So... yet another completely braindead broken by design build system. It's up to each project to decide that it should honor the build environment?!? Pretty much. scons is awful. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 20:32:30 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 20:32:30 -0000 Subject: [MacPorts] #53163: New dependencies for volk-gnss-sdr-next Message-ID: <052.ce59c2a6fb3e41a741b77c66033b5295@macports.org> #53163: New dependencies for volk-gnss-sdr-next -----------------------------+--------------------------- Reporter: carlesfernandez | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: volk-gnss-sdr -----------------------------+--------------------------- The attached diff adds py27-mako and py27-six to the list of dependencies for volk-gnss-sdr-next -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 20:33:48 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 20:33:48 -0000 Subject: [MacPorts] #53163: New dependencies for volk-gnss-sdr-next In-Reply-To: <052.ce59c2a6fb3e41a741b77c66033b5295@macports.org> References: <052.ce59c2a6fb3e41a741b77c66033b5295@macports.org> Message-ID: <067.29c63a103ca3362acc7e0ec683f3dadc@macports.org> #53163: New dependencies for volk-gnss-sdr-next ------------------------------+----------------- Reporter: carlesfernandez | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: volk-gnss-sdr | ------------------------------+----------------- Changes (by carlesfernandez): * Attachment "Portfile-volk-gnss-sdr.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 20:36:24 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 20:36:24 -0000 Subject: [MacPorts] #52827: yarn @0.16.1 In-Reply-To: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> References: <046.bf4244028e17b155e75b2ee12cceb252@macports.org> Message-ID: <061.8aa5541309050717f43f0e39a41c21f1@macports.org> #52827: yarn @0.16.1 -------------------------+-------------------------------- Reporter: isomarcte | Owner: macports-tickets@… Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: duplicate | Keywords: Port: yarn | -------------------------+-------------------------------- Comment (by jambonrose): In [changeset:"cbc8554047c2a8e08056a80d0ea6fc6249daa5f3/macports-ports" cbc85540/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="cbc8554047c2a8e08056a80d0ea6fc6249daa5f3" yarn: new port, version 0.18.1 JavaScript dependency manager * Closes: #48 * See: https://trac.macports.org/ticket/52827 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 21:22:52 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 21:22:52 -0000 Subject: [MacPorts] #53076: gcc47 @4.7.4_6 fails to build In-Reply-To: <043.7f4cb9cd057864586874ffa3345eb065@macports.org> References: <043.7f4cb9cd057864586874ffa3345eb065@macports.org> Message-ID: <058.a901d05df3a05af669226b366e4c639d@macports.org> #53076: gcc47 @4.7.4_6 fails to build ---------------------+---------------------- Reporter: posita | Owner: mww@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gcc47 | ---------------------+---------------------- Comment (by mpressman): I was able to fix it by adding a '@' on line 89 and 91 so that @end tex becomes @@end tex -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 22:18:36 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 22:18:36 -0000 Subject: [MacPorts] #53164: tk port does not install Message-ID: <044.1a3a8d2070079a2f937e0123a1577a9a@macports.org> #53164: tk port does not install ---------------------+----------------- Reporter: spidey3 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: tk ---------------------+----------------- I just tried installing tk on an older Mac (MacPro1,1 OS X 10.9.5), and see the following errors: {{{ arcturus[~] $ sudo port -vs install tk +quartz Password: ---> Computing dependencies for tk. ---> Building tk make: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_tk/tk/work/tk8.6.6/unix' rm -f libtk8.6.dylib /usr/bin/clang -dynamiclib -Os -pipe -Os -arch x86_64 -pipe -arch x86_64 -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_tk/tk/work/tcl8.6.6/generic -L/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_tk/tk/work/tk8.6.6/unix -L/opt/local/lib -arch x86_64 -headerpad_max_install_names -Wl,-search_paths_first -Wl,-single_module -o libtk8.6.dylib tk3d.o tkArgv.o tkAtom.o tkBind.o tkBitmap.o tkBusy.o tkClipboard.o tkCmds.o tkColor.o tkConfig.o tkConsole.o tkCursor.o tkError.o tkEvent.o tkFocus.o tkFont.o tkGet.o tkGC.o tkGeometry.o tkGrab.o tkGrid.o tkMain.o tkObj.o tkOldConfig.o tkOption.o tkPack.o tkPlace.o tkSelect.o tkStyle.o tkUndo.o tkUtil.o tkVisual.o tkWindow.o tkButton.o tkEntry.o tkFrame.o tkListbox.o tkMenu.o tkMenubutton.o tkMenuDraw.o tkMessage.o tkPanedWindow.o tkScale.o tkScrollbar.o tkCanvas.o tkCanvArc.o tkCanvBmap.o tkCanvImg.o tkCanvLine.o tkCanvPoly.o tkCanvPs.o tkCanvText.o tkCanvUtil.o tkCanvWind.o tkRectOval.o tkTrig.o tkImage.o tkImgBmap.o tkImgGIF.o tkImgPNG.o tkImgPPM.o tkImgPhoto.o tkImgPhInstance.o tkText.o tkTextBTree.o tkTextDisp.o tkTextImage.o tkTextIndex.o tkTextMark.o tkTextTag.o tkTextWind.o tkStubInit.o ttkBlink.o ttkButton.o ttkCache.o ttkClamTheme.o ttkClassicTheme.o ttkDefaultTheme.o ttkElements.o ttkEntry.o ttkFrame.o ttkImage.o ttkInit.o ttkLabel.o ttkLayout.o ttkManager.o ttkNotebook.o ttkPanedwindow.o ttkProgress.o ttkScale.o ttkScrollbar.o ttkScroll.o ttkSeparator.o ttkSquare.o ttkState.o ttkTagSet.o ttkTheme.o ttkTrace.o ttkTrack.o ttkTreeview.o ttkWidget.o ttkStubInit.o tkMacOSXBitmap.o tkMacOSXButton.o tkMacOSXClipboard.o tkMacOSXColor.o tkMacOSXConfig.o tkMacOSXCursor.o tkMacOSXDebug.o tkMacOSXDialog.o tkMacOSXDraw.o tkMacOSXEmbed.o tkMacOSXEntry.o tkMacOSXEvent.o tkMacOSXFont.o tkMacOSXHLEvents.o tkMacOSXInit.o tkMacOSXKeyboard.o tkMacOSXKeyEvent.o tkMacOSXMenu.o tkMacOSXMenubutton.o tkMacOSXMenus.o tkMacOSXMouseEvent.o tkMacOSXNotify.o tkMacOSXRegion.o tkMacOSXScrlbr.o tkMacOSXSend.o tkMacOSXSubwindows.o tkMacOSXWindowEvent.o tkMacOSXWm.o tkMacOSXXStubs.o tkFileFilter.o tkMacWinMenu.o tkPointer.o tkUnix3d.o tkUnixScale.o xcolors.o xdraw.o xgc.o ximage.o xutil.o ttkMacOSXTheme.o -lpthread -framework CoreFoundation -framework Cocoa -framework Carbon -framework IOKit -lz -lpthread -framework CoreFoundation -L/opt/local/lib -ltclstub8.6 -compatibility_version 8.6 -current_version 8.6.6 -install_name "/opt/local/lib/libtk8.6.dylib" -unexported_symbols_list $(f=libtk8.6.dylib.E && nm -gp tkMacOSX*.o 2>/dev/null | awk "/^[0-9a-f]+ . \.objc/ {print \$3}" > $f && nm -gjp "/opt/local/lib"/libtclstub8.6.a | grep ^_[^_] >> $f && echo $f) -sectcreate __TEXT __info_plist Tk- Info.plist llvm-nm: Unknown command line argument '-gjp'. Try: '/opt/local/libexec/llvm-3.7/bin/llvm-nm -help' llvm-nm: Did you mean '-g'? clang: error: no such file or directory: '__TEXT' clang: error: no such file or directory: '__info_plist' make: *** [libtk8.6.dylib] Error 1 make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_tk/tk/work/tk8.6.6/unix' Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_tk/tk/work/tk8.6.6/unix" && /usr/bin/make -j4 -w all Exit code: 2 Error: org.macports.build for port tk returned: command execution failed Warning: targets not executed for tk: org.macports.activate org.macports.build org.macports.destroot org.macports.install Please see the log file for port tk for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_tk/tk/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port tk failed arcturus[~] $ }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 22:36:04 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 22:36:04 -0000 Subject: [MacPorts] #51983: iTerm2 upgrade fails In-Reply-To: <044.c50edffe9a69eae3123be2bf8201f50c@macports.org> References: <044.c50edffe9a69eae3123be2bf8201f50c@macports.org> Message-ID: <059.6580db4b89b92ca7f82122211f6df27b@macports.org> #51983: iTerm2 upgrade fails ----------------------+--------------------------------------------- Reporter: watsodw | Owner: markemer Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: mountainlion mavericks yosemite Port: iTerm2 | ----------------------+--------------------------------------------- Comment (by myint): By the way, iTerm2 now (3.0.13) requires 10.12 to build. On 10.11, I get: {{{ CompileC build/iTerm2.build/Default/iTerm2Shared.build/Objects- normal/x86_64/PTYWindow.o sources/PTYWindow.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler cd /tmp/iTerm2 export LANG=en_US.US-ASCII /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x objective-c -arch x86_64 -fmessage-length=156 -fdiagnostics-show-note- include-stack -fmacro-backtrace-limit=0 -fcolor-diagnostics -std=gnu99 -fmodules -fmodules-prune-interval=86400 -fmodules-prune-after=345600 -fbuild-session- file=/var/folders/np/bmcfccrd3996nvvrxrht818r0000gn/C/org.llvm.clang/ModuleCache/Session.modulevalidation -fmodules-validate-once-per-build-session -Wnon-modular-include-in- framework-module -Werror=non-modular-include-in-framework-module -Wno- trigraphs -fpascal-strings -Os -fno-common -Wno-missing-field-initializers -Wno-missing-prototypes -Werror=return-type -Wunreachable-code -Wno- implicit-atomic-properties -Werror=deprecated-objc-isa-usage -Werror=objc- root-class -Wno-arc-repeated-use-of-weak -Wduplicate-method-match -Wno- missing-braces -Wparentheses -Wswitch -Wunused-function -Wno-unused-label -Wno-unused-parameter -Wunused-variable -Wunused-value -Wempty-body -Wconditional-uninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four- char-constants -Wno-conversion -Wconstant-conversion -Wint-conversion -Wbool-conversion -Wenum-conversion -Wno-shorten-64-to-32 -Wpointer-sign -Wno-newline-eof -Wno-selector -Wno-strict-selector-match -Wundeclared- selector -Wno-deprecated-implementations -DNS_BLOCK_ASSERTIONS=1 -DOBJC_OLD_DISPATCH_PROTOTYPES=0 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk -fasm-blocks -fstrict-aliasing -Wprotocol -Wdeprecated-declarations -mmacosx-version-min=10.9 -g -Wno-sign-conversion -iquote /tmp/iTerm2/build/iTerm2.build/Default/iTerm2Shared.build/iTerm2Shared- generated-files.hmap -I/tmp/iTerm2/build/iTerm2.build/Default/iTerm2Shared.build/iTerm2Shared- own-target-headers.hmap -I/tmp/iTerm2/build/iTerm2.build/Default/iTerm2Shared.build/iTerm2Shared- all-target-headers.hmap -iquote /tmp/iTerm2/build/iTerm2.build/Default/iTerm2Shared.build/iTerm2Shared- project-headers.hmap -I/tmp/iTerm2/build/Default/include -I/tmp/iTerm2/build/iTerm2.build/Default/iTerm2Shared.build/DerivedSources/x86_64 -I/tmp/iTerm2/build/iTerm2.build/Default/iTerm2Shared.build/DerivedSources -Wall -F/tmp/iTerm2/build/Default -F/tmp/iTerm2 -F/tmp/iTerm2/ColorPicker -F/tmp/iTerm2/ThirdParty -include /var/folders/np/bmcfccrd3996nvvrxrht818r0000gn/C/com.apple.DeveloperTools/7.3.1-7D1014/Xcode/SharedPrecompiledHeaders/iTerm2-cdsvnqusejvsafdgqekplpsmulwc/iTerm2.pch -MMD -MT dependencies -MF /tmp/iTerm2/build/iTerm2.build/Default/iTerm2Shared.build/Objects- normal/x86_64/PTYWindow.d --serialize-diagnostics /tmp/iTerm2/build/iTerm2.build/Default/iTerm2Shared.build/Objects- normal/x86_64/PTYWindow.dia -c /tmp/iTerm2/sources/PTYWindow.m -o /tmp/iTerm2/build/iTerm2.build/Default/iTerm2Shared.build/Objects- normal/x86_64/PTYWindow.o In file included from /tmp/iTerm2/sources/PTYWindow.m:43: /tmp/iTerm2/sources/iTermWindowImpl.m:30:38: error: expected a type styleMask:(NSWindowStyleMask)aStyle ^ /tmp/iTerm2/sources/iTermWindowImpl.m:35:39: warning: incompatible pointer to integer conversion sending 'id' to parameter of type 'NSUInteger' (aka 'unsigned long') [-Wint-conversion] styleMask:aStyle ^~~~~~ }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 22:47:38 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 22:47:38 -0000 Subject: [MacPorts] #53149: wine-crossover: update to 16.0.0 In-Reply-To: <047.f24374f560f43ababd9417a5cfe6c90d@macports.org> References: <047.f24374f560f43ababd9417a5cfe6c90d@macports.org> Message-ID: <062.c3fb28c11f4f4b4a9e38df3e84ebd0c8@macports.org> #53149: wine-crossover: update to 16.0.0 -----------------------------+---------------------- Reporter: ryandesign | Owner: jeremyhu Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: wine-crossover | -----------------------------+---------------------- Changes (by ryandesign): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"2ee16ad80f0635feb4725624717935ef14aa169a/macports-ports" 2ee16ad8/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="2ee16ad80f0635feb4725624717935ef14aa169a" wine-crossover: Update to 16.0.0 Closes: https://trac.macports.org/ticket/53149 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 23:05:15 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 23:05:15 -0000 Subject: [MacPorts] #53164: tk port does not install In-Reply-To: <044.1a3a8d2070079a2f937e0123a1577a9a@macports.org> References: <044.1a3a8d2070079a2f937e0123a1577a9a@macports.org> Message-ID: <059.f00113f972654060bb2a90d3567d0843@macports.org> #53164: tk port does not install ----------------------+----------------- Reporter: spidey3 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: tk | ----------------------+----------------- Comment (by ryandesign): This was not a [https://guide.macports.org/chunked/project.html#project.tickets clean build attempt]. Please `sudo port clean tk`, then try again. If it fails again, please attach the main.log file. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 23:21:37 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 23:21:37 -0000 Subject: [MacPorts] #53164: tk port does not install In-Reply-To: <044.1a3a8d2070079a2f937e0123a1577a9a@macports.org> References: <044.1a3a8d2070079a2f937e0123a1577a9a@macports.org> Message-ID: <059.ecd063fa9394cf80022382051d7aef04@macports.org> #53164: tk port does not install ----------------------+----------------- Reporter: spidey3 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: tk | ----------------------+----------------- Changes (by spidey3): * Attachment "main.log" added. Log file of failed port install tk -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 23:22:05 2016 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2016 23:22:05 -0000 Subject: [MacPorts] #53164: tk port does not install In-Reply-To: <044.1a3a8d2070079a2f937e0123a1577a9a@macports.org> References: <044.1a3a8d2070079a2f937e0123a1577a9a@macports.org> Message-ID: <059.4855bd5937733ab490a68008154632d0@macports.org> #53164: tk port does not install ----------------------+----------------- Reporter: spidey3 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: tk | ----------------------+----------------- Comment (by spidey3): See the new attachment. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 01:09:34 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 01:09:34 -0000 Subject: [MacPorts] #53164: tk port does not install In-Reply-To: <044.1a3a8d2070079a2f937e0123a1577a9a@macports.org> References: <044.1a3a8d2070079a2f937e0123a1577a9a@macports.org> Message-ID: <059.04db05dfbe6b6836a307d9137858792a@macports.org> #53164: tk port does not install ----------------------+----------------- Reporter: spidey3 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: tk | ----------------------+----------------- Comment (by ryandesign): Your issue looks the same as #51893, but that was resolved 5 months ago. Are your ports up to date? `sudo port selfupdate && sudo port upgrade outdated`? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 02:41:01 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 02:41:01 -0000 Subject: [MacPorts] #53163: New dependencies for volk-gnss-sdr-next In-Reply-To: <052.ce59c2a6fb3e41a741b77c66033b5295@macports.org> References: <052.ce59c2a6fb3e41a741b77c66033b5295@macports.org> Message-ID: <067.e65cb7ca2bb58434fd5798d580d0055c@macports.org> #53163: New dependencies for volk-gnss-sdr-next ------------------------------+----------------- Reporter: carlesfernandez | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: volk-gnss-sdr | ------------------------------+----------------- Comment (by michaelld): In [changeset:"170f5518bbeaf4b43374971148d8d331b1930632/macports-ports" 170f5518/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="170f5518bbeaf4b43374971148d8d331b1930632" volk-gnss-sdr: update to 878d2973 (20161227); add py27 mako and six as dependencies, to match those for updated Volk; addresses ticket https://trac.macports.org/ticket/53163 . }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 02:41:24 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 02:41:24 -0000 Subject: [MacPorts] #53163: New dependencies for volk-gnss-sdr-next In-Reply-To: <052.ce59c2a6fb3e41a741b77c66033b5295@macports.org> References: <052.ce59c2a6fb3e41a741b77c66033b5295@macports.org> Message-ID: <067.7ce54f93d613d7d3e031d970573eab53@macports.org> #53163: New dependencies for volk-gnss-sdr-next ------------------------------+-------------------- Reporter: carlesfernandez | Owner: Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: volk-gnss-sdr | ------------------------------+-------------------- Changes (by michaelld): * status: new => closed * resolution: => fixed Comment: Thanks! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 03:34:53 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 03:34:53 -0000 Subject: [MacPorts] #51983: iTerm2 upgrade fails In-Reply-To: <044.c50edffe9a69eae3123be2bf8201f50c@macports.org> References: <044.c50edffe9a69eae3123be2bf8201f50c@macports.org> Message-ID: <059.3b95c50024b5e27f41b7a66295f7ba63@macports.org> #51983: iTerm2 upgrade fails ----------------------+--------------------------------------------- Reporter: watsodw | Owner: markemer Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: mountainlion mavericks yosemite Port: iTerm2 | ----------------------+--------------------------------------------- Comment (by markemer): Unless we can build binaries for 10.8-10.11, I think I might have to mark this as 10.12 only. Which sucks. Anyone have any ideas? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 03:44:56 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 03:44:56 -0000 Subject: [MacPorts] #51983: iTerm2 upgrade fails In-Reply-To: <044.c50edffe9a69eae3123be2bf8201f50c@macports.org> References: <044.c50edffe9a69eae3123be2bf8201f50c@macports.org> Message-ID: <059.de2ec043fc65ce412e003a0d0ef61da8@macports.org> #51983: iTerm2 upgrade fails ----------------------+--------------------------------------------- Reporter: watsodw | Owner: markemer Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: mountainlion mavericks yosemite Port: iTerm2 | ----------------------+--------------------------------------------- Comment (by EJFielding): Seems like it would be better to mark the new version as 10.12 only to avoid the rest of us having the frustration of having MacPorts downloading the upgrade and having it fail to build on our machines. I don't mind sticking with the @3.0.5 until I do the full OS upgrade. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 04:39:44 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 04:39:44 -0000 Subject: [MacPorts] #52922: qt5 @5.6.2_0: build errors on 10.7 In-Reply-To: <042.4fe4267df0921e65219025cb7afc453e@macports.org> References: <042.4fe4267df0921e65219025cb7afc453e@macports.org> Message-ID: <057.061d27951c5e66ea46b3648b27066f4c@macports.org> #52922: qt5 @5.6.2_0: build errors on 10.7 -------------------------------------------------+------------------------- Reporter: mojca | Owner: | MarcusCalhoun-Lopez Type: defect | Status: accepted Priority: Low | Milestone: Component: ports | Version: Resolution: | Keywords: lion Port: qt5 qt5-qtdoc ​qt5-qtmultimedia | qt5-qtserialbus qt5-qtwebengine qt5 | -qtwebengine-docs qt5-qtwebkit qt5-qtwebkit- | docs qt5-qtwebview qt5-qtwebview-docs | -------------------------------------------------+------------------------- Comment (by MarcusCalhoun-Lopez): In [changeset:"77ec1368e330ec3d24f85c5543cd0c5304137fdf/macports-ports" 77ec1368/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="77ec1368e330ec3d24f85c5543cd0c5304137fdf" qmake5-1.0.tcl: avoid mixing libc++ and libstdc++ see https://trac.macports.org/ticket/52922 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 06:58:43 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 06:58:43 -0000 Subject: [MacPorts] #50671: boost: Update to 1.63.0 In-Reply-To: <045.068f49dfc49c577073cb3ffe59aec898@macports.org> References: <045.068f49dfc49c577073cb3ffe59aec898@macports.org> Message-ID: <060.7f88436bfebb26cc5badbce1dcb91f28@macports.org> #50671: boost: Update to 1.63.0 -----------------------+------------------------ Reporter: eborisch | Owner: ryandesign Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch Port: boost | -----------------------+------------------------ Comment (by akimd): Thanks for this. But I'm quite puzzled by the number of local patches that you still have to apply. Upstream does not want to apply them all? I can see that some have been, or became useless, but not all. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 06:59:55 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 06:59:55 -0000 Subject: [MacPorts] #53165: nodejs6: error: ... MemoryChunkVisitor::job_' is not a member of class Message-ID: <042.67a6f0ac4aa73253bf66c914a9ed3e17@macports.org> #53165: nodejs6: error: ... MemoryChunkVisitor::job_' is not a member of class --------------------+--------------------- Reporter: mojca | Owner: ci42 Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: lion | Port: nodejs6 --------------------+--------------------- nodejs6 fails to build on 10.7: {{{ ../deps/v8/src/heap/mark-compact.cc:3506:7: error: 'v8::internal::UpdatePointersInParallel(v8::internal::Heap *, base::Semaphore *)::MemoryChunkVisitor::operator()(v8::internal::MemoryChunk *)::MemoryChunkVisitor::job_' is not a member of class 'v8::internal::MemoryChunkVisitor' job_.AddPage(chunk, 0); ^ }}} Full logs are [https://build.macports.org/builders/ports-10 .7_x86_64_legacy-builder/builds/15328 here]. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 07:11:29 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 07:11:29 -0000 Subject: [MacPorts] #53166: yarn: default to an older nodejs on < 10.8 Message-ID: <042.50c072555c3b8cd5f320c0f07a2b878d@macports.org> #53166: yarn: default to an older nodejs on < 10.8 ------------------------------+------------------------ Reporter: mojca | Owner: jambonrose Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: snowleopard lion | Port: yarn ------------------------------+------------------------ nodejs6 only seems to work on 10.8 and later (see #53165 and many other tickets). Based on comments in the portfiles it seems that nodejs4 and 5 require at least 10.6 and nodejs requires at least 10.7. I suspect that the build failure on 10.7 might be only a matter using a too old compiler on 10.7 though and the following blacklist might not be sufficient: {{{ compiler.blacklist *gcc* {clang < 300} }}} It would be nice to fallback to an older version of nodejs (perhaps version 5) on < 10.8 (or on < 10.7 once the issue of building nodejs6 gets resolved on Lion). Btw: is the isomarcte's email in Yarn misspelled? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 08:17:20 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 08:17:20 -0000 Subject: [MacPorts] #53165: nodejs6: error: ... MemoryChunkVisitor::job_' is not a member of class In-Reply-To: <042.67a6f0ac4aa73253bf66c914a9ed3e17@macports.org> References: <042.67a6f0ac4aa73253bf66c914a9ed3e17@macports.org> Message-ID: <057.763bc568cab8fd935bd5b077dd412572@macports.org> #53165: nodejs6: error: ... MemoryChunkVisitor::job_' is not a member of class ----------------------+-------------------- Reporter: mojca | Owner: ci42 Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: lion Port: nodejs6 | ----------------------+-------------------- Changes (by mojca): * status: new => closed * resolution: => fixed Comment: In [changeset:"41fad2d2414cdfff00d98816d12c0dcd3bc568b4/macports-ports" 41fad2d2/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="41fad2d2414cdfff00d98816d12c0dcd3bc568b4" nodejs[67]: blacklist clang < 500 Closes: https://trac.macports.org/ticket/53165 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 08:23:19 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 08:23:19 -0000 Subject: [MacPorts] #53167: libupnp @1.6.20: update to 1.6.21 Message-ID: <041.9d57f6599dc01dd0a6a8c3168bfa73a2@macports.org> #53167: libupnp @1.6.20: update to 1.6.21 --------------------+--------------------- Reporter: l2dy | Owner: Type: update | Status: new Priority: High | Milestone: Component: ports | Version: Keywords: | Port: libupnp --------------------+--------------------- CVE-2016-6255 and CVE-2016-8863. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 08:43:05 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 08:43:05 -0000 Subject: [MacPorts] #53168: Python Frameworks not codesigned in MacOS Sierra Message-ID: <042.6587e7fd0ae44bc9b26de5421befffb9@macports.org> #53168: Python Frameworks not codesigned in MacOS Sierra ----------------------------------------------------+-------------------- Reporter: tcwan | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: codesign incoming connections firewall | Port: python ----------------------------------------------------+-------------------- I am using a python app which opens a listening socket for network connections, which is intercepted by the MacOS Firewall with the permission dialog "XXX accept incoming connections?" each time the app is executed. The reason for this behavior is due to the Python Frameworks not having a valid signature {{{ $ codesign -vvv /opt/local/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app /opt/local/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app: code object is not signed at all In architecture: x86_64 }}} To overcome this, the python framework(s) should be codesigned after installation. {{{ $sudo codesign -f -s - /opt/local/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app }}} Note the '-' after -s is needed to force codesign to use an ad hoc signature. After codesigning, the following output is seen: {{{ $ codesign -vvv /opt/local/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app /opt/local/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app: valid on disk /opt/local/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app: satisfies its Designated Requirement }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 09:28:26 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 09:28:26 -0000 Subject: [MacPorts] #53169: PortIndex contains expanded prefix Message-ID: <043.c2f960f04c1b7e8f6d401c4b06c1f5a5@macports.org> #53169: PortIndex contains expanded prefix --------------------+------------------- Reporter: jmroot | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.5 Keywords: | Port: --------------------+------------------- Somewhere along the way, portindex lost its code for replacing the prefix with the static string `{${prefix}}`. That means you end up with this sort of thing: {{{ % port -v deps --index BiggerSQL Full Name: BiggerSQL @1.3.9_0 Library Dependencies: path:/var/tmp/mprsyncup/opt/local/lib/postgresql84:postgresql84 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 09:44:13 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 09:44:13 -0000 Subject: [MacPorts] #53169: PortIndex contains expanded prefix In-Reply-To: <043.c2f960f04c1b7e8f6d401c4b06c1f5a5@macports.org> References: <043.c2f960f04c1b7e8f6d401c4b06c1f5a5@macports.org> Message-ID: <058.24a1819c604ebbfc5e524492ab94f531@macports.org> #53169: PortIndex contains expanded prefix ---------------------+------------------- Reporter: jmroot | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.5 Resolution: | Keywords: Port: | ---------------------+------------------- Comment (by jmroot): Cf. #17182 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 11:35:46 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 11:35:46 -0000 Subject: [MacPorts] #53170: py-mitmproxy @0.17.1: update to 1.0.1 Message-ID: <041.e8ce91fc13b3930d86b86a43dd0d084a@macports.org> #53170: py-mitmproxy @0.17.1: update to 1.0.1 --------------------+-------------------------- Reporter: l2dy | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: py-mitmproxy --------------------+-------------------------- All mitmproxy tools are now Python 3 only! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 11:54:28 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 11:54:28 -0000 Subject: [MacPorts] #53165: nodejs6: error: ... MemoryChunkVisitor::job_' is not a member of class In-Reply-To: <042.67a6f0ac4aa73253bf66c914a9ed3e17@macports.org> References: <042.67a6f0ac4aa73253bf66c914a9ed3e17@macports.org> Message-ID: <057.deca40c21af453959b2e7f0eebb5e768@macports.org> #53165: nodejs6: error: ... MemoryChunkVisitor::job_' is not a member of class ----------------------+-------------------- Reporter: mojca | Owner: ci42 Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: lion Port: nodejs6 | ----------------------+-------------------- Comment (by mojca): Both nodejs6 and nodejs7 seem to have been built successfully. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 11:56:04 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 11:56:04 -0000 Subject: [MacPorts] #53166: yarn: default to an older nodejs on 10.6 (was: yarn: default to an older nodejs on < 10.8) In-Reply-To: <042.50c072555c3b8cd5f320c0f07a2b878d@macports.org> References: <042.50c072555c3b8cd5f320c0f07a2b878d@macports.org> Message-ID: <057.820cd61e76f1a1158c39027b03544550@macports.org> #53166: yarn: default to an older nodejs on 10.6 ---------------------+------------------------- Reporter: mojca | Owner: jambonrose Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: yarn | ---------------------+------------------------- Changes (by mojca): * keywords: snowleopard lion => snowleopard Old description: > nodejs6 only seems to work on 10.8 and later (see #53165 and many other > tickets). > > Based on comments in the portfiles it seems that nodejs4 and 5 require at > least 10.6 and nodejs requires at least 10.7. I suspect that the build > failure on 10.7 might be only a matter using a too old compiler on 10.7 > though and the following blacklist might not be sufficient: > > {{{ > compiler.blacklist *gcc* {clang < 300} > }}} > > It would be nice to fallback to an older version of nodejs (perhaps > version 5) on < 10.8 (or on < 10.7 once the issue of building nodejs6 > gets resolved on Lion). > > Btw: is the isomarcte's email in Yarn misspelled? New description: nodejs6 only seems to work on 10.7 and later (see also #53165 and many other tickets). Based on comments in the portfiles it seems that nodejs4 and 5 require at least 10.6 and nodejs requires at least 10.7. It would be nice to fallback to an older version of nodejs (perhaps version 5) on < 10.7. Btw: is the isomarcte's email in Yarn misspelled? -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 12:02:52 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 12:02:52 -0000 Subject: [MacPorts] #51835: nodejs6 @6.3.0 Fails to build: filename too long In-Reply-To: <060.b9cb7a9b660870b042e218162fc135e6@macports.org> References: <060.b9cb7a9b660870b042e218162fc135e6@macports.org> Message-ID: <075.6ead2492929399de864c83b683af31af@macports.org> #51835: nodejs6 @6.3.0 Fails to build: filename too long -----------------------+------------------- Reporter: marcel@… | Owner: ci42 Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: nodejs6 | -----------------------+------------------- Comment (by mojca): Version 6.9.1 seems to build just fine on 10.7 after blacklisting the system compiler and using macports-clang-3.4. Is this still a problem for you? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 12:08:02 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 12:08:02 -0000 Subject: [MacPorts] #51949: nodejs6 @6.3.1 Fails to build In-Reply-To: <060.2c2043817012cd570ab233510095dae1@macports.org> References: <060.2c2043817012cd570ab233510095dae1@macports.org> Message-ID: <075.aee173f8817e9223b41540ba4fbfa139@macports.org> #51949: nodejs6 @6.3.1 Fails to build -----------------------+------------------- Reporter: marcel@… | Owner: ci42 Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: nodejs6 | -----------------------+------------------- Comment (by mojca): This looks like the same issue to me. I wasn't able to reproduce the problem with 6.9.1 after switching to macports-clang-3.4 though. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 12:56:40 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 12:56:40 -0000 Subject: [MacPorts] #50153: MoarVM: upgrade and fix some issues In-Reply-To: <042.f19be3e22e83ceac3c02825a637f4e24@macports.org> References: <042.f19be3e22e83ceac3c02825a637f4e24@macports.org> Message-ID: <057.a0f5e9758b6373422dce7ede966877f7@macports.org> #50153: MoarVM: upgrade and fix some issues ---------------------+-------------------- Reporter: mojca | Owner: will@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: MoarVM | ---------------------+-------------------- Comment (by mojca): Relevant lines from `./Configure.pl` where we might need a change: {{{ #!perl if ($args{'has-libtommath'}) { $defaults{-thirdparty}->{tom} = undef; unshift @{$config{usrlibs}}, 'tommath'; } else { $config{cincludes} .= ' ' . $defaults{ccinc} . '3rdparty/libtommath'; $config{install} .= "\t\$(MKPATH) \$(DESTDIR)\$(PREFIX)/include/libtommath\n" . "\t\$(CP) 3rdparty/libtommath/*.h \$(DESTDIR)\$(PREFIX)/include/libtommath\n"; } }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 13:21:34 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 13:21:34 -0000 Subject: [MacPorts] #53171: MoarVM: failure to compile with the built-in libatomic_ops on 10.7 Message-ID: <042.8bf81b1ca2ff1a67d11cf63b0831e565@macports.org> #53171: MoarVM: failure to compile with the built-in libatomic_ops on 10.7 --------------------+---------------------------------- Reporter: mojca | Owner: mojca Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: lion | Port: MoarVM libatomic_ops --------------------+---------------------------------- MoarVM compiles everywhere except on Lion. On Lion it only compiles if libatomic_ops from MacPorts (version 7.4.4) has already been installed, else one gets [https://build.macports.org/builders/ports-10 .7_x86_64_legacy-builder/builds/19237/steps/install- dependencies/logs/stdio this]: {{{ compiling src/core/callsite.o In file included from src/main.c:4: In file included from src/moar.h:28: 3rdparty/libatomic_ops/src/atomic_ops.h:376:5: error: Cannot implement AO_compare_and_swap_full on this architecture. # error Cannot implement AO_compare_and_swap_full on this architecture. ^ In file included from src/core/callsite.c:1: In file included from src/moar.h:28: 3rdparty/libatomic_ops/src/atomic_ops.h:376:5: error: Cannot implement AO_compare_and_swap_full on this architecture. # error Cannot implement AO_compare_and_swap_full on this architecture. ^ 1 error generated. }}} The version of libatomic_ops from MoarVM presents itself as 7.5.0. See also #50153. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 13:40:13 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 13:40:13 -0000 Subject: [MacPorts] #50153: MoarVM: upgrade and fix some issues In-Reply-To: <042.f19be3e22e83ceac3c02825a637f4e24@macports.org> References: <042.f19be3e22e83ceac3c02825a637f4e24@macports.org> Message-ID: <057.b34b1ca46b456b63db032864be7775f3@macports.org> #50153: MoarVM: upgrade and fix some issues ---------------------+-------------------- Reporter: mojca | Owner: will@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: MoarVM | ---------------------+-------------------- Comment (by mojca): In [changeset:"edda46853ad2bb87b89e42d5dcc033449efd7aae/macports-ports" edda4685/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="edda46853ad2bb87b89e42d5dcc033449efd7aae" MoarVM: add dependencies for 3rd party modules * Add `libuv` as a dependency rather than conflicting with it. It is now a dependency of CMake, so people probably have it installed. * Add a dependency on `libatomic_ops` due to a build failure on 10.7. Closes: https://trac.macports.org/ticket/53171 * Add a dependency on `dyncall` to further reduce the number of conflicts. * The `libtommath` package doesn't seem to be compatible. See: https://trac.macports.org/ticket/50153 See: https://github.com/MoarVM/MoarVM/issues/321 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 13:40:14 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 13:40:14 -0000 Subject: [MacPorts] #53171: MoarVM: failure to compile with the built-in libatomic_ops on 10.7 In-Reply-To: <042.8bf81b1ca2ff1a67d11cf63b0831e565@macports.org> References: <042.8bf81b1ca2ff1a67d11cf63b0831e565@macports.org> Message-ID: <057.7dd48dd60b38cca6fbcb7a1dc8a1f470@macports.org> #53171: MoarVM: failure to compile with the built-in libatomic_ops on 10.7 -----------------------------------+-------------------- Reporter: mojca | Owner: mojca Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: lion Port: MoarVM libatomic_ops | -----------------------------------+-------------------- Changes (by mojca): * status: new => closed * resolution: => fixed Comment: In [changeset:"edda46853ad2bb87b89e42d5dcc033449efd7aae/macports-ports" edda4685/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="edda46853ad2bb87b89e42d5dcc033449efd7aae" MoarVM: add dependencies for 3rd party modules * Add `libuv` as a dependency rather than conflicting with it. It is now a dependency of CMake, so people probably have it installed. * Add a dependency on `libatomic_ops` due to a build failure on 10.7. Closes: https://trac.macports.org/ticket/53171 * Add a dependency on `dyncall` to further reduce the number of conflicts. * The `libtommath` package doesn't seem to be compatible. See: https://trac.macports.org/ticket/50153 See: https://github.com/MoarVM/MoarVM/issues/321 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 14:00:39 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 14:00:39 -0000 Subject: [MacPorts] #53171: MoarVM: failure to compile with the built-in libatomic_ops on 10.7 In-Reply-To: <042.8bf81b1ca2ff1a67d11cf63b0831e565@macports.org> References: <042.8bf81b1ca2ff1a67d11cf63b0831e565@macports.org> Message-ID: <057.dee92506b40b1ddfebf713d7d44bca69@macports.org> #53171: MoarVM: failure to compile with the built-in libatomic_ops on 10.7 -----------------------------------+-------------------- Reporter: mojca | Owner: mojca Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: lion Port: MoarVM libatomic_ops | -----------------------------------+-------------------- Comment (by mojca): I opened an upstream ticket at https://github.com/ivmai/libatomic_ops/issues/23. Using {{{ #!tcl PortGroup compiler_blacklist_versions 1.0 compiler.blacklist {clang < 500} *gcc* }}} seems to help. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 14:38:13 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 14:38:13 -0000 Subject: [MacPorts] #53171: MoarVM: failure to compile with the built-in libatomic_ops on 10.7 In-Reply-To: <042.8bf81b1ca2ff1a67d11cf63b0831e565@macports.org> References: <042.8bf81b1ca2ff1a67d11cf63b0831e565@macports.org> Message-ID: <057.9dfdf1f588fd6e2ea177f1eecbc9b6d6@macports.org> #53171: MoarVM: failure to compile with the built-in libatomic_ops on 10.7 -----------------------------------+-------------------- Reporter: mojca | Owner: mojca Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: lion Port: MoarVM libatomic_ops | -----------------------------------+-------------------- Comment (by mojca): Arghhhh. After the change the build on 10.6 now fails with inability to link against `dyncall`. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 14:56:38 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 14:56:38 -0000 Subject: [MacPorts] #53172: nsf @2.0.0_0: upgrade due to upstream release Message-ID: <044.41f3496125ae0abc1289019bbc79eac8@macports.org> #53172: nsf @2.0.0_0: upgrade due to upstream release ---------------------------------+------------------- Reporter: gustafn | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: maintainer haspatch | Port: nsf ---------------------------------+------------------- Attached you find an updated port file for the most recent release of NSF. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 14:58:12 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 14:58:12 -0000 Subject: [MacPorts] #53172: nsf @2.0.0_0: upgrade due to upstream release In-Reply-To: <044.41f3496125ae0abc1289019bbc79eac8@macports.org> References: <044.41f3496125ae0abc1289019bbc79eac8@macports.org> Message-ID: <059.37f093a231aec5ad7dcaa12ebaef9f53@macports.org> #53172: nsf @2.0.0_0: upgrade due to upstream release ----------------------+--------------------------------- Reporter: gustafn | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: maintainer haspatch Port: nsf | ----------------------+--------------------------------- Changes (by gustafn): * Attachment "nsf-portfile.patch" added. patch for Portfile -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 15:33:34 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 15:33:34 -0000 Subject: [MacPorts] #53167: libupnp @1.6.20: update to 1.6.21 In-Reply-To: <041.9d57f6599dc01dd0a6a8c3168bfa73a2@macports.org> References: <041.9d57f6599dc01dd0a6a8c3168bfa73a2@macports.org> Message-ID: <056.a5ebf287fea9123fe14faa19df0e19e1@macports.org> #53167: libupnp @1.6.20: update to 1.6.21 ----------------------+------------------------ Reporter: l2dy | Owner: ctreleaven Type: update | Status: assigned Priority: High | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libupnp | ----------------------+------------------------ Changes (by ctreleaven): * owner: => ctreleaven * status: new => assigned * cc: ctreleaven@… (removed) Comment: I'm still not up and running with git. Hopefully in the next couple of weeks. If anyone else wants to handle this in the meantime, please do. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 16:02:32 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 16:02:32 -0000 Subject: [MacPorts] #53169: PortIndex contains expanded prefix In-Reply-To: <043.c2f960f04c1b7e8f6d401c4b06c1f5a5@macports.org> References: <043.c2f960f04c1b7e8f6d401c4b06c1f5a5@macports.org> Message-ID: <058.102cc4f67960de9c75b5b0b6e7bbdb08@macports.org> #53169: PortIndex contains expanded prefix ---------------------+------------------- Reporter: jmroot | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.5 Resolution: | Keywords: Port: | ---------------------+------------------- Comment (by neverpanic): Yep, that was probably me in [0e21180e3d1b197d077fde37a394ef67d8e486d1 /macports-base], since I didn't understand the purpose of `set prefix {\${prefix}}` and it didn't have a comment explaining it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 16:11:22 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 16:11:22 -0000 Subject: [MacPorts] #53169: PortIndex contains expanded prefix In-Reply-To: <043.c2f960f04c1b7e8f6d401c4b06c1f5a5@macports.org> References: <043.c2f960f04c1b7e8f6d401c4b06c1f5a5@macports.org> Message-ID: <058.9b2b7490c6b8b5d617023571dd7b91d7@macports.org> #53169: PortIndex contains expanded prefix ---------------------+------------------- Reporter: jmroot | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.5 Resolution: | Keywords: Port: | ---------------------+------------------- Comment (by neverpanic): Change available for review at https://github.com/macports/macports- base/pull/13. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 17:10:34 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 17:10:34 -0000 Subject: [MacPorts] #52922: qt5 @5.6.2_0: build errors on 10.7 In-Reply-To: <042.4fe4267df0921e65219025cb7afc453e@macports.org> References: <042.4fe4267df0921e65219025cb7afc453e@macports.org> Message-ID: <057.13c01770035d32e1c6cae936b8155572@macports.org> #52922: qt5 @5.6.2_0: build errors on 10.7 -------------------------------------------------+------------------------- Reporter: mojca | Owner: | MarcusCalhoun-Lopez Type: defect | Status: accepted Priority: Low | Milestone: Component: ports | Version: Resolution: | Keywords: lion Port: qt5 qt5-qtdoc ​qt5-qtmultimedia | qt5-qtserialbus qt5-qtwebengine qt5 | -qtwebengine-docs qt5-qtwebkit qt5-qtwebkit- | docs qt5-qtwebview qt5-qtwebview-docs | -------------------------------------------------+------------------------- Comment (by MarcusCalhoun-Lopez): In [changeset:"ec39a5a3336f1aea6aa0755286c202c3814fe72b/macports-ports" ec39a5a3/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="ec39a5a3336f1aea6aa0755286c202c3814fe72b" qt5-qtmultimedia: build on Mac OS X 10.7 see https://trac.macports.org/ticket/52922 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 17:20:41 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 17:20:41 -0000 Subject: [MacPorts] #52321: coccinelle : Configure failure (ac_nonexistent.h) In-Reply-To: <055.e60ca9dc8b9d90508ccd31bd1ea040c7@macports.org> References: <055.e60ca9dc8b9d90508ccd31bd1ea040c7@macports.org> Message-ID: <070.e3fa10b5d2e0fe681a1023f3039da7ec@macports.org> #52321: coccinelle : Configure failure (ac_nonexistent.h) -------------------------+------------------- Reporter: skycrawl@… | Owner: g5pw Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: coccinelle | -------------------------+------------------- Comment (by g5pw): Is this still happening with coccinelle 1.0.6? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 17:26:15 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 17:26:15 -0000 Subject: [MacPorts] #52922: qt5 @5.6.2_0: build errors on 10.7 In-Reply-To: <042.4fe4267df0921e65219025cb7afc453e@macports.org> References: <042.4fe4267df0921e65219025cb7afc453e@macports.org> Message-ID: <057.141328f329ef516b7623b8a4758c21b2@macports.org> #52922: qt5 @5.6.2_0: build errors on 10.7 -------------------------------------------------+------------------------- Reporter: mojca | Owner: | MarcusCalhoun-Lopez Type: defect | Status: accepted Priority: Low | Milestone: Component: ports | Version: Resolution: | Keywords: lion Port: qt5 qt5-qtdoc ​qt5-qtmultimedia | qt5-qtserialbus qt5-qtwebengine qt5 | -qtwebengine-docs qt5-qtwebkit qt5-qtwebkit- | docs qt5-qtwebview qt5-qtwebview-docs | -------------------------------------------------+------------------------- Comment (by mojca): What's the proper way for ports to add dependencies on Qt5 after you introduced the qt55 ports? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 17:29:31 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 17:29:31 -0000 Subject: [MacPorts] #52922: qt5 @5.6.2_0: build errors on 10.7 In-Reply-To: <042.4fe4267df0921e65219025cb7afc453e@macports.org> References: <042.4fe4267df0921e65219025cb7afc453e@macports.org> Message-ID: <057.a2dc1b0ea0cd005f07155813b7077b44@macports.org> #52922: qt5 @5.6.2_0: build errors on 10.7 -------------------------------------------------+------------------------- Reporter: mojca | Owner: | MarcusCalhoun-Lopez Type: defect | Status: accepted Priority: Low | Milestone: Component: ports | Version: Resolution: | Keywords: lion Port: qt5 qt5-qtdoc ​qt5-qtmultimedia | qt5-qtserialbus qt5-qtwebengine qt5 | -qtwebengine-docs qt5-qtwebkit qt5-qtwebkit- | docs qt5-qtwebview qt5-qtwebview-docs | -------------------------------------------------+------------------------- Comment (by MarcusCalhoun-Lopez): Replying to [comment:11 mojca]: > What's the proper way for ports to add dependencies on Qt5 after you introduced the qt55 ports? https://trac.macports.org/ticket/51619 is currently being tested. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 17:34:03 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 17:34:03 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.be0719cdb12c6d75a1dcb0ef81efa897@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by mojca): One warning. If ports can declare dependency on different versions of Qt (Qt 5.5 or 5.6 or dev or KDE or whatever ...) then the PortGroup needs to provide a way to automatically generate variants as well, otherwise there will be troubles with ABI compatilibility when users decide to switch to a different version of Qt. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 17:44:41 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 17:44:41 -0000 Subject: [MacPorts] #52574: cargo: update to version 0.13.0 In-Reply-To: <043.b2e705aabe9d18bb6c0f0f27fa6a8c0e@macports.org> References: <043.b2e705aabe9d18bb6c0f0f27fa6a8c0e@macports.org> Message-ID: <058.d813c00d0df8a64fbcc53512bca93afa@macports.org> #52574: cargo: update to version 0.13.0 ---------------------+------------------------ Reporter: raimue | Owner: seanfarley Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: haspatch Port: cargo | ---------------------+------------------------ Changes (by g5pw): * status: new => closed * resolution: => fixed Comment: Updated to 1.14 in e8a836cbfc. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 17:45:26 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 17:45:26 -0000 Subject: [MacPorts] #52247: rust 1.11.0 build hangs indefinitely on macos 10.12 (Sierra) In-Reply-To: <054.ea23676a7329d7d0cee044ab1a242f30@macports.org> References: <054.ea23676a7329d7d0cee044ab1a242f30@macports.org> Message-ID: <069.e57f82640a2c451dad797c2c4c44eec2@macports.org> #52247: rust 1.11.0 build hangs indefinitely on macos 10.12 (Sierra) ------------------------+-------------------- Reporter: r.keoni@… | Owner: g5pw Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: sierra Port: rust | ------------------------+-------------------- Changes (by g5pw): * status: new => closed * resolution: => fixed Comment: updated to 1.14 in 1e793e4776. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 18:02:34 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 18:02:34 -0000 Subject: [MacPorts] #53169: PortIndex contains expanded prefix In-Reply-To: <043.c2f960f04c1b7e8f6d401c4b06c1f5a5@macports.org> References: <043.c2f960f04c1b7e8f6d401c4b06c1f5a5@macports.org> Message-ID: <058.a9db1538f289f51b06763f65ba84c62d@macports.org> #53169: PortIndex contains expanded prefix ---------------------+-------------------- Reporter: jmroot | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: | Keywords: Port: | ---------------------+-------------------- Changes (by raimue): * version: 2.3.5 => 2.3.99 Comment: I checked and this bug does not exist in 2.3.5, but only on 2.3.99 master. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 18:04:37 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 18:04:37 -0000 Subject: [MacPorts] #52469: Rust update to 1.13 In-Reply-To: <043.1de7d6f358f111ea6f5c25b676fe6212@macports.org> References: <043.1de7d6f358f111ea6f5c25b676fe6212@macports.org> Message-ID: <058.d1ea8a94c4554549ea220e1bfe650b88@macports.org> #52469: Rust update to 1.13 ---------------------+---------------------- Reporter: jboone | Owner: g5pw Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: haspatch Port: rust | ---------------------+---------------------- Changes (by g5pw): * status: new => closed * resolution: => fixed Comment: updated to 1.14 in [1e793e4776/macports-ports] -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 18:05:33 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 18:05:33 -0000 Subject: [MacPorts] #47668: coccinelle @1.0.0-rc21 can't find camlp4 In-Reply-To: <048.0c816752f06bf8080e3b2426dedac367@macports.org> References: <048.0c816752f06bf8080e3b2426dedac367@macports.org> Message-ID: <063.b4b4778b83feac0ff5421e2894439088@macports.org> #47668: coccinelle @1.0.0-rc21 can't find camlp4 --------------------------+------------------- Reporter: Schamschula | Owner: g5pw Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: coccinelle | --------------------------+------------------- Comment (by g5pw): Is this still an issue with the 1.0.6? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 18:31:44 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 18:31:44 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.19bcda7234e33d9c7b7d55e339b209db@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by RJVB): A more important warning: when testing this procedure, please make sure to use the latest version from https://github.com/RJVB/macstrop/blob/master/_resources/port1.0/group/qt5-1.0.tcl {{{ # a procedure for declaring dependencies on Qt5 components, which will expand them # into the appropriate subports for the Qt5 flavour installed # e.g. qt5.depends_component qtbase qtsvg qtdeclarative proc qt5.depends_component {first args} { global qt5_component_lib qt5.using_kde os.major # join ${first} and (the optional) ${args} set args [linsert $args[set list {}] 0 ${first}] # select the Qt5 port prefix, depending on which Qt5 port is installed set is_qt5kde [expr [info exists qt5.using_kde] && ${qt5.using_kde}] if {${is_qt5kde} == 1 || ${os.major} == 10} { # We have port:qt5-kde or we're on OS X 10.6 which only gets Qt 5.3.2 from that port set qt5pprefix "qt5-kde" } elseif {${os.major} == 11} { set qt5pprefix "qt55" } else { set qt5pprefix "qt5" } foreach comp ${args} { set done true switch ${comp} { "qt5" { if {${is_qt5kde} == 1} { global qt5_dependency # qt5-kde-1.0.tcl exports the exact dependency expression in a variable depends_lib-append ${qt5_dependency} } else { depends_lib-append port:${qt5pprefix} } } "qtwebkit" - "qtwebengine" - "qtwebview" { # these components are never stub subports set done false } default { # these components are included port:qt5-kde (and provided as additional stub subports) if {${is_qt5kde} == 0} { set done false } } } if {!${done}} { set portname "${qt5pprefix}-${comp}" if {[info exists qt5_component_lib] && [info exists qt5_component_lib(${comp})]} { # an explicit dependency pattern was given, e.g. path:foo depends_lib-append "$qt5_component_lib(${comp}):${portname}" } else { depends_lib-append port:${portname} } } } } }}} @mojca: the goal here is not that ports can declare dependencies on different Qt versions. Even port:qt55 is supposed to be used only on earlier OS X version(s) (10.7 +?). How exactly that is supposed to work I don't know nor what kind of protection there is against installing that port on later OS versions; the procedure above assumes that this port is to be used on 10.7 only. port:qt5 and port:qt5-kde aren't supposed to have different Qt versions. Just as with -devel ports, it is largely up to the user to decide which Qt port s/he installs, and ports have to work with either of the available alternatives. But in line with your remark: using port:qt5-kde has always led to setting a variant. Not that variants can protect against ABI differences when a dependency is changed ... The risk is mitigated a bit by Qt's guaranteed backwards compatibility, so everything should be fine as long as no one tries to use port:qt55 after having used a later Qt version. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 18:38:30 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 18:38:30 -0000 Subject: [MacPorts] #53166: yarn: default to an older nodejs on 10.6 In-Reply-To: <042.50c072555c3b8cd5f320c0f07a2b878d@macports.org> References: <042.50c072555c3b8cd5f320c0f07a2b878d@macports.org> Message-ID: <057.85fbc11b474d1a230b00e2b0367900c3@macports.org> #53166: yarn: default to an older nodejs on 10.6 ---------------------+------------------------- Reporter: mojca | Owner: jambonrose Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: yarn | ---------------------+------------------------- Comment (by jambonrose): I've opened a PR on Github that attempts to fix this issue: https://github.com/macports/macports-ports/pull/127 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 18:40:43 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 18:40:43 -0000 Subject: [MacPorts] #53173: py-pyobjc: fails to build on 10.6, uses 10.7 SDK; stdarg.h: No such file or directory Message-ID: <042.9eb7c4eb8fe75c6aa2720d9712f5c2b9@macports.org> #53173: py-pyobjc: fails to build on 10.6, uses 10.7 SDK; stdarg.h: No such file or directory -------------------------+----------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: snowleopard | Port: py-pyobjc -------------------------+----------------------- It looks suspicious that the build is trying to use the 10.7 SDK: {{{ /usr/bin/gcc-4.2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -arch i386 -I/opt/local/Library/Frameworks/Python.framework/Versions/3.6/include/python3.6m -c Modules/objc/OC_NSBundleHack.m -o build/temp.macosx-10.6-i386-3.6/Modules/objc/OC_NSBundleHack.o -DPyObjC_STRICT_DEBUGGING -DMACOSX -DPyObjC_BUILD_RELEASE=1006 -DMACOSX -g -fexceptions -Wall -Wstrict-prototypes -Wmissing-prototypes -Wformat=2 -W -Wpointer-arith -Wmissing-declarations -Wnested-externs -W -Wno-import -Wno-unknown-pragmas -Wshorten-64-to-32 -Ilibffi-src/include -Ilibffi- src/powerpc -isysroot /Developer/SDKs/MacOSX10.7.sdk In file included from /opt/local/Library/Frameworks/Python.framework/Versions/3.6/include/python3.6m/Python.h:75, from Modules/objc/pyobjc.h:11, from Modules/objc/OC_NSBundleHack.m:1: /opt/local/Library/Frameworks/Python.framework/Versions/3.6/include/python3.6m/bytearrayobject.h:9:20: error: stdarg.h: No such file or directory }}} Here's the [https://build.macports.org/builders/ports-10.6_i386_legacy- builder/builds/13135 full log]. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 19:51:28 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 19:51:28 -0000 Subject: [MacPorts] #53173: py-pyobjc: fails to build on 10.6, uses 10.7 SDK; stdarg.h: No such file or directory In-Reply-To: <042.9eb7c4eb8fe75c6aa2720d9712f5c2b9@macports.org> References: <042.9eb7c4eb8fe75c6aa2720d9712f5c2b9@macports.org> Message-ID: <057.9a71ef4d643b3f719bdb653c379aee50@macports.org> #53173: py-pyobjc: fails to build on 10.6, uses 10.7 SDK; stdarg.h: No such file or directory ------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: py-pyobjc | ------------------------+------------------------- Comment (by ryandesign): You are right that it is unexpected that the pyobjc build is trying to use the 10.7 SDK. I don't know if that's the cause of the problem, however. The 10.6 buildbot machines do have the 10.7 SDK installed, because that was the only way to build libsdl2. The pyobjc setup.py file runs `/usr/bin/xcodebuild -version -sdk macosx Path` to determine what SDK to use. On the 10.6 buildbot machines, this returns `/Developer/SDKs/MacOSX10.7.sdk`, presumably because it is the newest installed SDK. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 20:26:34 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 20:26:34 -0000 Subject: [MacPorts] #53158: qt4-mac-mariadb-plugin causes trouble during upgrade of KDE4 ports In-Reply-To: <041.d299450d3e6623b4ed6200b2379e070a@macports.org> References: <041.d299450d3e6623b4ed6200b2379e070a@macports.org> Message-ID: <056.45ce07453596d2a80f4b99be908b20ee@macports.org> #53158: qt4-mac-mariadb-plugin causes trouble during upgrade of KDE4 ports -------------------------+--------------------- Reporter: mkae | Owner: pixilla Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: worksforme | Keywords: Port: | -------------------------+--------------------- Changes (by mkae): * status: new => closed * resolution: => worksforme Comment: I've realised that I still had an older MacPorts ports tree on my host system. That somehow interfered with the more up-to-date rsynced data from MacPorts' central server. I have no idea what caused this collision, but after rebuilding the 3 ports above all is back to normal now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 20:46:47 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 20:46:47 -0000 Subject: [MacPorts] #53168: python27: Python Frameworks not codesigned in MacOS Sierra (was: Python Frameworks not codesigned in MacOS Sierra) In-Reply-To: <042.6587e7fd0ae44bc9b26de5421befffb9@macports.org> References: <042.6587e7fd0ae44bc9b26de5421befffb9@macports.org> Message-ID: <057.40b31eefe581bbe413e44f2b749d72fc@macports.org> #53168: python27: Python Frameworks not codesigned in MacOS Sierra -----------------------+---------------------------- Reporter: tcwan | Owner: jyrkiwahlstedt Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: python27 | -----------------------+---------------------------- Changes (by ryandesign): * status: new => assigned * owner: => jyrkiwahlstedt * port: python => python27 * keywords: codesign incoming connections firewall => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 20:52:22 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 20:52:22 -0000 Subject: [MacPorts] #52468: gtk3 3.22.0_0 build fails on 10.5 ppc In-Reply-To: <055.10664af5583ed7c907561b6fd2498e1a@macports.org> References: <055.10664af5583ed7c907561b6fd2498e1a@macports.org> Message-ID: <070.c1e79793c497b89c1aab6cd22889c220@macports.org> #52468: gtk3 3.22.0_0 build fails on 10.5 ppc -------------------------+----------------------------- Reporter: dgonyier@… | Owner: dbevans Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: leopard powerpc Port: gtk3 | -------------------------+----------------------------- Comment (by ballapete): With `gtk33.22.5_0` I get on PPC Leopard a differrnt error: {{{ ld: illegal text-relocation to cstring in .libs/libgdk_3_la-gdkcolor.o from _gdk_color_copy in .libs/libgdk_3_la-gdkcolor.o for architecture ppc }}} There seems to exist a cure, http://stackoverflow.com/questions/6650178 /illegal-text-reloc-to-non-lazy-ptr-error-while-building-in-xcode-4-with- libav-l, but setting in Portfile {{{ if {[variant_isset universal]} { foreach arch ${configure.universal_archs} { lappend merger_build_args(${arch}) CC='${configure.cc} -arch ${arch}' lappend merger_build_args(${arch}) CC_FOR_BUILD='${configure.cc} -arch ${arch} -Wl,-read_only_relocs suppress' lappend merger_build_args(${arch}) LDFLAGS='${configure.ldflags} -arch ${arch} -read_only_relocs suppress' lappend merger_destroot_args(${arch}) CC='${configure.cc} -arch ${arch}' lappend merger_destroot_args(${arch}) CC_FOR_BUILD='${configure.cc} -arch ${arch} -Wl,-read_only_relocs suppress' lappend merger_destroot_args(${arch}) LDFLAGS='${configure.ldflags} -arch ${arch} -read_only_relocs suppress' } } else { build.args-append CC="${configure.cc} ${configure.cc_archflags}" \ CC_FOR_BUILD="${configure.cc} ${configure.cc_archflags} -Wl,-read_only_relocs suppress" \ LDFLAGS="${configure.ldflags} -read_only_relocs suppress" destroot.args-append CC="${configure.cc} ${configure.cc_archflags}" \ CC_FOR_BUILD="${configure.cc} ${configure.cc_archflags} -Wl,-read_only_relocs suppress" \ LDFLAGS="${configure.ldflags} -read_only_relocs suppress" } }}} leads to only a few uses of `-read_only_relocs suppress` … At least the error is consistent. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 21:02:49 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 21:02:49 -0000 Subject: [MacPorts] #53158: qt4-mac-mariadb-plugin causes trouble during upgrade of KDE4 ports In-Reply-To: <041.d299450d3e6623b4ed6200b2379e070a@macports.org> References: <041.d299450d3e6623b4ed6200b2379e070a@macports.org> Message-ID: <056.84bb950bb614d0d8884d5c6837752742@macports.org> #53158: qt4-mac-mariadb-plugin causes trouble during upgrade of KDE4 ports -------------------------+--------------------- Reporter: mkae | Owner: pixilla Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: worksforme | Keywords: Port: | -------------------------+--------------------- Comment (by RJVB): I've run into issues with supposedly unused port trees too. Removing a source from sources.conf wasn't enough, I also had to delete the PortIndex files in the ports directory. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 21:02:50 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 21:02:50 -0000 Subject: [MacPorts] #53164: tk port does not install In-Reply-To: <044.1a3a8d2070079a2f937e0123a1577a9a@macports.org> References: <044.1a3a8d2070079a2f937e0123a1577a9a@macports.org> Message-ID: <059.f074c422d2deda6732de798cd59cfea5@macports.org> #53164: tk port does not install ----------------------+----------------- Reporter: spidey3 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: tk | ----------------------+----------------- Comment (by spidey3): Ports are definitely up-to-date: {{{ $ sudo port selfupdate && sudo port upgrade outdated Password: ---> Updating MacPorts base sources using rsync MacPorts base version 2.3.5 installed, MacPorts base version 2.3.5 downloaded. ---> Updating the ports tree ---> MacPorts base is already the latest version The ports tree has been updated. To upgrade your installed ports, you should run port upgrade outdated Nothing to upgrade. arcturus[~] $ }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 21:02:52 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 21:02:52 -0000 Subject: [MacPorts] #53173: py-pyobjc: fails to build on 10.6, uses 10.7 SDK; stdarg.h: No such file or directory In-Reply-To: <042.9eb7c4eb8fe75c6aa2720d9712f5c2b9@macports.org> References: <042.9eb7c4eb8fe75c6aa2720d9712f5c2b9@macports.org> Message-ID: <057.94d3f94b3eddaa40e69b6b3f34adbc38@macports.org> #53173: py-pyobjc: fails to build on 10.6, uses 10.7 SDK; stdarg.h: No such file or directory ------------------------+------------------------- Reporter: mojca | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: py-pyobjc | ------------------------+------------------------- Comment (by mojca): Ah, that explains why I constantly get `10.(n+1)` on my computer as well. {{{ /usr/bin/xcodebuild -version -sdk macosx Path }}} returns the newer SDK for me as well. I was looking at some links like http://stackoverflow.com/a/10330744/585897 which tend to suggest a broken installation of the toolchain. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 21:12:59 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 21:12:59 -0000 Subject: [MacPorts] #53174: buildbot: better handle removal of ports in mpbb Message-ID: <042.5f3ed67bedd7140f0746acbba20ab61d@macports.org> #53174: buildbot: better handle removal of ports in mpbb ----------------------------+--------------------- Reporter: mojca | Owner: admin@… Type: defect | Status: new Priority: Low | Milestone: Component: server/hosting | Version: Keywords: buildbot | Port: ----------------------------+--------------------- Here's an [https://build.macports.org/builders/ports-10.7_x86_64_legacy- watcher/builds/3863 example] of removal of a port that resulted in an unexpected error: {{{ ./mpbb/mpbb: error: None of the specified ports were found in the port index. ./mpbb/mpbb: error: `list-subports' failed to run successfully }}} Our handling of removal of ports should probably be improved. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 21:59:30 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 21:59:30 -0000 Subject: [MacPorts] #52468: gtk3 3.22.0_0 build fails on 10.5 ppc In-Reply-To: <055.10664af5583ed7c907561b6fd2498e1a@macports.org> References: <055.10664af5583ed7c907561b6fd2498e1a@macports.org> Message-ID: <070.532d95acc76380ac7f8b1a03719a6f07@macports.org> #52468: gtk3 3.22.0_0 build fails on 10.5 ppc -------------------------+----------------------------- Reporter: dgonyier@… | Owner: dbevans Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: leopard powerpc Port: gtk3 | -------------------------+----------------------------- Comment (by ballapete): Trying to build gtk3 with Quartz leads to other errors: {{{ gdkevents-quartz.c:356:10: error: use of undeclared identifier 'NSEventTypeMagnify' case NSEventTypeMagnify: ^ gdkevents-quartz.c:357:10: error: use of undeclared identifier 'NSEventTypeRotate' case NSEventTypeRotate: ^ }}} and {{{ gdkevents-quartz.c:835:10: error: use of undeclared identifier 'NSEventTypeMagnify' case NSEventTypeMagnify: ^ gdkevents-quartz.c:836:10: error: use of undeclared identifier 'NSEventTypeRotate' case NSEventTypeRotate: ^ }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 22:01:07 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 22:01:07 -0000 Subject: [MacPorts] #52468: gtk3 3.22.0_0 build fails on 10.5 ppc In-Reply-To: <055.10664af5583ed7c907561b6fd2498e1a@macports.org> References: <055.10664af5583ed7c907561b6fd2498e1a@macports.org> Message-ID: <070.743566f12b426b9707eb0d5372b6d79f@macports.org> #52468: gtk3 3.22.0_0 build fails on 10.5 ppc -------------------------+----------------------------- Reporter: dgonyier@… | Owner: dbevans Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: leopard powerpc Port: gtk3 | -------------------------+----------------------------- Changes (by ballapete): * Attachment "main.4.log" added. main.log from gtk3 3.22.5, trying to build +quartz -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 22:28:57 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 22:28:57 -0000 Subject: [MacPorts] #53175: fdupes now v1.6.1 Message-ID: <043.b50c023176f31b6728142bf9ec50c485@macports.org> #53175: fdupes now v1.6.1 --------------------+-------------------- Reporter: bunk3m | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: fdupes --------------------+-------------------- Could the maintainer update the version of fdupes to the current v1.6.1 from 1.5.1? I believe the maintainer in v2.3.5 is wrong. I put the maintainer from v2.3.5 but I believe this is now Nerdling? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 22:54:31 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 22:54:31 -0000 Subject: [MacPorts] #52468: gtk3 3.22.0_0 build fails on 10.5 ppc In-Reply-To: <055.10664af5583ed7c907561b6fd2498e1a@macports.org> References: <055.10664af5583ed7c907561b6fd2498e1a@macports.org> Message-ID: <070.942dd9086d459b3d143c4f1d557d0265@macports.org> #52468: gtk3 3.22.0_0 build fails on 10.5 ppc -------------------------+----------------------------- Reporter: dgonyier@… | Owner: dbevans Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: leopard powerpc Port: gtk3 | -------------------------+----------------------------- Comment (by ballapete): Replying to [comment:49 ballapete]: > Trying to build gtk3 with Quartz leads to other errors: These can be fixed with the patch – but in the end the same text- relocation error breaks the build. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 22:59:53 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 22:59:53 -0000 Subject: [MacPorts] #52468: gtk3 3.22.0_0 build fails on 10.5 ppc In-Reply-To: <055.10664af5583ed7c907561b6fd2498e1a@macports.org> References: <055.10664af5583ed7c907561b6fd2498e1a@macports.org> Message-ID: <070.0012c4f2f97a1f9b1a8fe8eb1fdcb722@macports.org> #52468: gtk3 3.22.0_0 build fails on 10.5 ppc -------------------------+----------------------------- Reporter: dgonyier@… | Owner: dbevans Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: leopard powerpc Port: gtk3 | -------------------------+----------------------------- Changes (by ballapete): * Attachment "patch-gdkevents-quartz_NSTypes-10_5_compat.diff" added. Fixes in Leopard unknown NS Event Types -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 23:58:00 2016 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2016 23:58:00 -0000 Subject: [MacPorts] #53136: emacs 25.1: add modules variant to build with loadable module support In-Reply-To: <049.6de3ca7b24f01201d0bf164ed39c7f7c@macports.org> References: <049.6de3ca7b24f01201d0bf164ed39c7f7c@macports.org> Message-ID: <064.3e70a2acced6f984aec1f22c5c660c81@macports.org> #53136: emacs 25.1: add modules variant to build with loadable module support ---------------------------+---------------------- Reporter: little-big-h | Owner: drkp Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: emacs | ---------------------------+---------------------- Changes (by drkp): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"ddf3624c6d89ebd2ad830eb08bee05c9633ea023/macports-ports" ddf3624c/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="ddf3624c6d89ebd2ad830eb08bee05c9633ea023" emacs: enable module support Closes: https://trac.macports.org/ticket/53136 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 00:01:39 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 00:01:39 -0000 Subject: [MacPorts] #53136: emacs 25.1: add modules variant to build with loadable module support In-Reply-To: <049.6de3ca7b24f01201d0bf164ed39c7f7c@macports.org> References: <049.6de3ca7b24f01201d0bf164ed39c7f7c@macports.org> Message-ID: <064.8f3583332c3e78a660117e8f5cf8935d@macports.org> #53136: emacs 25.1: add modules variant to build with loadable module support ---------------------------+---------------------- Reporter: little-big-h | Owner: drkp Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: emacs | ---------------------------+---------------------- Comment (by drkp): If rms is unhappy about it, that's good enough for me. :-) Enabled it by default. Note that only the emacs ports (not emacs-app) install the header file. This is to keep them from conflicting with each other. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 00:08:16 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 00:08:16 -0000 Subject: [MacPorts] #53171: MoarVM: failure to compile with the built-in libatomic_ops on 10.7 In-Reply-To: <042.8bf81b1ca2ff1a67d11cf63b0831e565@macports.org> References: <042.8bf81b1ca2ff1a67d11cf63b0831e565@macports.org> Message-ID: <057.fe973780fd0f9dff58d35d25a32532a7@macports.org> #53171: MoarVM: failure to compile with the built-in libatomic_ops on 10.7 -----------------------------------+-------------------- Reporter: mojca | Owner: mojca Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: lion Port: MoarVM libatomic_ops | -----------------------------------+-------------------- Comment (by mojca): In [changeset:"6a01e722d9441c1e77bbd9f1a55c586115fa3cca/macports-ports" 6a01e722/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="6a01e722d9441c1e77bbd9f1a55c586115fa3cca" libatomic_ops[-devel]: merge into subports libatomic_ops: * add tests * disable universal build * unify description with the -devel port libatomic_ops-devel: * upgrade to version from master * homepage no longer valid See: https://trac.macports.org/ticket/53171 See: https://github.com/ivmai/libatomic_ops/issues/23 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 00:23:18 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 00:23:18 -0000 Subject: [MacPorts] #40904: tesseract @3.02.02: some language subports conflict In-Reply-To: <047.d0ac243462a4a66a1ad76872e44f85be@macports.org> References: <047.d0ac243462a4a66a1ad76872e44f85be@macports.org> Message-ID: <062.6bfe3cb3106c2fcd16f20acb961fae7e@macports.org> #40904: tesseract @3.02.02: some language subports conflict -------------------------+---------------------- Reporter: ryandesign | Owner: markemer Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: tesseract | -------------------------+---------------------- Comment (by markemer): This was fixed by #51128. The 3.04 languages no longer conflict like the 3.02 ones do. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 00:25:35 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 00:25:35 -0000 Subject: [MacPorts] #53124: julia: Update to version 0.5 In-Reply-To: <045.fc17f67b995cc13ab11a9440273f871f@macports.org> References: <045.fc17f67b995cc13ab11a9440273f871f@macports.org> Message-ID: <060.25809c6dd36090ca2d2dae869ba403c3@macports.org> #53124: julia: Update to version 0.5 -----------------------+------------------------ Reporter: manuSrep | Owner: seanfarley Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: julia | -----------------------+------------------------ Comment (by markemer): I tried the naive fix, bumping the versions and the hashes, but i set segfaults during the portion of the build when it begins to build julia code. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 00:28:10 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 00:28:10 -0000 Subject: [MacPorts] #46015: Cannot install gnu prolog (gprolog) on Yosemite In-Reply-To: <055.fe48083941c3dd4fca657057952a3fe6@macports.org> References: <055.fe48083941c3dd4fca657057952a3fe6@macports.org> Message-ID: <070.31d5bf7e60152954baf7ab12d5df9fe1@macports.org> #46015: Cannot install gnu prolog (gprolog) on Yosemite -------------------------+-------------------- Reporter: benshimo@… | Owner: pmoura Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: gprolog | -------------------------+-------------------- Comment (by markemer): This is still happening on Sierra. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 00:33:47 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 00:33:47 -0000 Subject: [MacPorts] #51983: iTerm2 upgrade fails In-Reply-To: <044.c50edffe9a69eae3123be2bf8201f50c@macports.org> References: <044.c50edffe9a69eae3123be2bf8201f50c@macports.org> Message-ID: <059.a8acd1604ada96d537c6a8c9da91348e@macports.org> #51983: iTerm2 upgrade fails ----------------------+--------------------------------------------- Reporter: watsodw | Owner: markemer Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: mountainlion mavericks yosemite Port: iTerm2 | ----------------------+--------------------------------------------- Comment (by mojca): If the port requires a newer SDK, then the "best" you can do is probably to install and older version of iTerm2 on older OSes. You can keep the same Portfile and only change the version and checksums based on OS version in some if-else statements. It requires more maintenance effort, but for some port it might be worth it. Depends. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 00:38:40 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 00:38:40 -0000 Subject: [MacPorts] #53026: nodejs6/7 and npm3/4 need update (was: nodejs6 and npm4 needs update) In-Reply-To: <050.c534650540f9311476383ef1b7981727@macports.org> References: <050.c534650540f9311476383ef1b7981727@macports.org> Message-ID: <065.46d3eb6a1fb0e90c29d4a0864133abfa@macports.org> #53026: nodejs6/7 and npm3/4 need update ----------------------------------------+---------------------- Reporter: luc-j-bourhis | Owner: ci42 Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: nodejs6 nodejs7 npm3 npm4 | ----------------------------------------+---------------------- Changes (by mojca): * port: nodejs => nodejs6 nodejs7 npm3 npm4 Comment: I opened https://github.com/macports/macports-ports/pull/128 for part of the updates. Waiting for maintainer to provide feedback and finish the rest. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 00:39:44 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 00:39:44 -0000 Subject: [MacPorts] #53026: nodejs4/6/7 and npm3/4 need update (was: nodejs6/7 and npm3/4 need update) In-Reply-To: <050.c534650540f9311476383ef1b7981727@macports.org> References: <050.c534650540f9311476383ef1b7981727@macports.org> Message-ID: <065.589252b6deb2302746ed43db36f89d6d@macports.org> #53026: nodejs4/6/7 and npm3/4 need update ------------------------------------------------+---------------------- Reporter: luc-j-bourhis | Owner: ci42 Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: nodejs4 nodejs6 nodejs7 npm3 npm4 | ------------------------------------------------+---------------------- Changes (by mojca): * port: nodejs6 nodejs7 npm3 npm4 => nodejs4 nodejs6 nodejs7 npm3 npm4 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 00:47:52 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 00:47:52 -0000 Subject: [MacPorts] #53026: nodejs4/6/7 and npm3/4 need update In-Reply-To: <050.c534650540f9311476383ef1b7981727@macports.org> References: <050.c534650540f9311476383ef1b7981727@macports.org> Message-ID: <065.349fff7f7d728fef921dee745d7f5c3e@macports.org> #53026: nodejs4/6/7 and npm3/4 need update ------------------------------------------------+---------------------- Reporter: luc-j-bourhis | Owner: ci42 Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: nodejs4 nodejs6 nodejs7 npm3 npm4 | ------------------------------------------------+---------------------- Changes (by mojca): * cc: l2dy (added) Old description: > {{{ > % port livecheck npm4 > npm4 seems to have been updated (port version: 4.0.2, new version: 4.0.5) > % port livecheck nodejs6 > nodejs6 seems to have been updated (port version: 6.9.1, new version: > 6.9.2) > }}} New description: `npm` and `nodejs` ports need an update and some fixing of livechecks (+ fixed dependencies on < 10.7 to account for inability to compile `nodejs6` there). {{{ % port livecheck npm3 npm3 seems to have been updated (port version: 3.10.9, new version: 4.0.5) # 3.10.10 % port livecheck npm4 npm4 seems to have been updated (port version: 4.0.2, new version: 4.1.1) # 4.0.5 }}} {{{ % port livecheck nodejs4 nodejs4 seems to have been updated (port version: 4.6.1, new version: 4.7.0) % port livecheck nodejs6 nodejs6 seems to have been updated (port version: 6.9.1, new version: 6.9.2) % port livecheck nodejs7 nodejs7 seems to have been updated (port version: 7.0.0, new version: 7.3.0) }}} -- Comment: Ticket #52976 is asking for updating one of them without a patch, so I'll treat it as a duplicate. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 00:48:41 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 00:48:41 -0000 Subject: [MacPorts] #52976: nodejs4 @4.6.1: update to 4.6.2 In-Reply-To: <041.2031761f858c785bb228d0481bf8da32@macports.org> References: <041.2031761f858c785bb228d0481bf8da32@macports.org> Message-ID: <056.ccf9ff460eb68004ed27000b28bc2225@macports.org> #52976: nodejs4 @4.6.1: update to 4.6.2 ------------------------+-------------------- Reporter: l2dy | Owner: ci42 Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: duplicate | Keywords: Port: nodejs4 | ------------------------+-------------------- Changes (by mojca): * status: assigned => closed * resolution: => duplicate Comment: Even if it's technically not, let's call this one a duplicate of #53026. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 00:51:22 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 00:51:22 -0000 Subject: [MacPorts] #51949: nodejs6 @6.3.1 Fails to build In-Reply-To: <060.2c2043817012cd570ab233510095dae1@macports.org> References: <060.2c2043817012cd570ab233510095dae1@macports.org> Message-ID: <075.92e8d948ba7c7ca86aa44e08b223d9a6@macports.org> #51949: nodejs6 @6.3.1 Fails to build ------------------------+-------------------- Reporter: marcel@… | Owner: ci42 Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: duplicate | Keywords: Port: nodejs6 | ------------------------+-------------------- Changes (by mojca): * status: new => closed * version: 2.3.4 => * resolution: => duplicate Old description: > With the ticket:51835 still not resolved, here comes another build- > breaking issue. Please see the attached log file. > > I feel this port needs better quality control. New description: With the ticket #51835 still not resolved, here comes another build- breaking issue. Please see the attached log file. I feel this port needs better quality control. -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 00:54:02 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 00:54:02 -0000 Subject: [MacPorts] #51835: nodejs6 @6.3.0 Fails to build: filename too long In-Reply-To: <060.b9cb7a9b660870b042e218162fc135e6@macports.org> References: <060.b9cb7a9b660870b042e218162fc135e6@macports.org> Message-ID: <075.c9b45fdd93aa52be36ca27a9ba4574ef@macports.org> #51835: nodejs6 @6.3.0 Fails to build: filename too long -----------------------+------------------- Reporter: marcel@… | Owner: ci42 Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: nodejs6 | -----------------------+------------------- Comment (by mojca): I marked #51949 as a duplicate of this one, I don't see any major difference between the two. In any case the port seems to build on all the build slaves now (from 10.7 on), so I would close this issue unless someone can confirm that this is still a problem with version 6.9.x. Ticket #53026 is about updating `nodejs6`. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 00:58:06 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 00:58:06 -0000 Subject: [MacPorts] #52634: nodejs4 @4.6.0: build does not respect CXXFLAGS In-Reply-To: <055.f0d61e741abb87d78dc99f884bb46db9@macports.org> References: <055.f0d61e741abb87d78dc99f884bb46db9@macports.org> Message-ID: <070.3eefcf9c8451806b9b2c47199f3a085a@macports.org> #52634: nodejs4 @4.6.0: build does not respect CXXFLAGS ------------------------+------------------- Reporter: william@… | Owner: ci42 Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: nodejs4 | ------------------------+------------------- Comment (by mojca): Isn't that the same problem for all `nodejs` version rather than just `nodejs4`? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 01:11:03 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 01:11:03 -0000 Subject: [MacPorts] #53168: python27: Python Frameworks not codesigned in MacOS Sierra In-Reply-To: <042.6587e7fd0ae44bc9b26de5421befffb9@macports.org> References: <042.6587e7fd0ae44bc9b26de5421befffb9@macports.org> Message-ID: <057.deec3ff76cc9cae3f7ada349bbb25046@macports.org> #53168: python27: Python Frameworks not codesigned in MacOS Sierra -----------------------+---------------------------- Reporter: tcwan | Owner: jyrkiwahlstedt Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: python27 | -----------------------+---------------------------- Comment (by mojca): See also #39349. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 01:16:53 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 01:16:53 -0000 Subject: [MacPorts] #53168: python27: Python Frameworks not codesigned in MacOS Sierra In-Reply-To: <042.6587e7fd0ae44bc9b26de5421befffb9@macports.org> References: <042.6587e7fd0ae44bc9b26de5421befffb9@macports.org> Message-ID: <057.5a47584a8498b050df5250120a411e27@macports.org> #53168: python27: Python Frameworks not codesigned in MacOS Sierra -----------------------+---------------------------- Reporter: tcwan | Owner: jyrkiwahlstedt Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: python27 | -----------------------+---------------------------- Comment (by tcwan): I think the codesigning requirement is true for all versions of Python, not just Python 2.7 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 01:19:55 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 01:19:55 -0000 Subject: [MacPorts] #53167: libupnp @1.6.20: update to 1.6.21 In-Reply-To: <041.9d57f6599dc01dd0a6a8c3168bfa73a2@macports.org> References: <041.9d57f6599dc01dd0a6a8c3168bfa73a2@macports.org> Message-ID: <056.8916813569f8c7cf15e2dc942d24f1b8@macports.org> #53167: libupnp @1.6.20: update to 1.6.21 ----------------------+------------------------ Reporter: l2dy | Owner: ctreleaven Type: update | Status: closed Priority: High | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: libupnp | ----------------------+------------------------ Changes (by mojca): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"f914cd798842497e04088c8ac585ce5f85913bd7/macports-ports" f914cd79/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="f914cd798842497e04088c8ac585ce5f85913bd7" libupnp: upgrade to 1.6.21 Closes: https://trac.macports.org/ticket/53167 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 01:24:23 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 01:24:23 -0000 Subject: [MacPorts] #53144: libmacho @895 fails to build because GCC is not universal variant In-Reply-To: <046.367079c58979ee177ea68524b2ea0c15@macports.org> References: <046.367079c58979ee177ea68524b2ea0c15@macports.org> Message-ID: <061.255335bb74285bb9cc920f29a06c4c49@macports.org> #53144: libmacho @895 fails to build because GCC is not universal variant ------------------------+------------------------------ Reporter: ballapete | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: tiger, universal Port: libmacho | ------------------------+------------------------------ Comment (by kencu): I installed libmacho on Tiger by disabling the default universal variant in the libmacho Portfile. {{{ $ port -v installed | grep libmacho libmacho @886_0 platform='darwin 8' archs='ppc' libmacho @895_0 (active) platform='darwin 8' archs='ppc' libmacho-headers @877.5_0 platform='darwin 8' archs='noarch' libmacho-headers @886_0 platform='darwin 8' archs='noarch' libmacho-headers @895_0 (active) platform='darwin 8' archs='noarch' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 01:30:14 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 01:30:14 -0000 Subject: [MacPorts] #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X In-Reply-To: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> References: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> Message-ID: <061.2a40492ebe83754ff8c0966d9d29cdb2@macports.org> #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X ------------------------+--------------------------- Reporter: ballapete | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: tiger powerpc Port: libuv | ------------------------+--------------------------- Comment (by mojca): I wouldn't necessarily bother fixing `libuv`, but it would make sense to fix `cmake` in a way that it would use the internal library rather than the external one if that helps. That should be easy enough to do and it affects a lot of ports (the system without `cmake` is nearly useless). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 01:37:35 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 01:37:35 -0000 Subject: [MacPorts] #53076: gcc47 @4.7.4_6 fails to build In-Reply-To: <043.7f4cb9cd057864586874ffa3345eb065@macports.org> References: <043.7f4cb9cd057864586874ffa3345eb065@macports.org> Message-ID: <058.a085c159d7d407a74166c53ac200cbef@macports.org> #53076: gcc47 @4.7.4_6 fails to build ---------------------+---------------------- Reporter: posita | Owner: mww@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gcc47 | ---------------------+---------------------- Comment (by mojca): Is this opportunistic usage of texinfo? I would be curious if deactivating texinfo and then rebuilding gcc47 from source (`sudo port -v -s destroot gcc47`) helps because the packages have been built successfully on the build slaves. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 02:49:12 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 02:49:12 -0000 Subject: [MacPorts] #53124: julia: Update to version 0.5 In-Reply-To: <045.fc17f67b995cc13ab11a9440273f871f@macports.org> References: <045.fc17f67b995cc13ab11a9440273f871f@macports.org> Message-ID: <060.50901008e8c061ebfc6c4587e7a73fd8@macports.org> #53124: julia: Update to version 0.5 -----------------------+------------------------ Reporter: manuSrep | Owner: seanfarley Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: julia | -----------------------+------------------------ Comment (by seanfarley): I'll try to take a look at this later this week. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 04:02:02 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 04:02:02 -0000 Subject: [MacPorts] #53175: fdupes now v1.6.1 In-Reply-To: <043.b50c023176f31b6728142bf9ec50c485@macports.org> References: <043.b50c023176f31b6728142bf9ec50c485@macports.org> Message-ID: <058.9f4a9ae7d37e6ea1ea8e41957cdd9731@macports.org> #53175: fdupes now v1.6.1 ---------------------+------------------- Reporter: bunk3m | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: fdupes | ---------------------+------------------- Comment (by grimreaper): > I believe the maintainer in v2.3.5 is wrong. Not sure what you mean here. Either way, I'll take a look at updating this. Thanks for the reminder! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 04:16:04 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 04:16:04 -0000 Subject: [MacPorts] #53169: PortIndex contains expanded prefix In-Reply-To: <043.c2f960f04c1b7e8f6d401c4b06c1f5a5@macports.org> References: <043.c2f960f04c1b7e8f6d401c4b06c1f5a5@macports.org> Message-ID: <058.adaeff8e9dbce5471c6bacc8c35df6a7@macports.org> #53169: PortIndex contains expanded prefix ---------------------+-------------------- Reporter: jmroot | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: | Keywords: Port: | ---------------------+-------------------- Comment (by jmroot): How come it's in the PortIndex on the rsync server then? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 04:17:55 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 04:17:55 -0000 Subject: [MacPorts] #53175: fdupes now v1.6.1 In-Reply-To: <043.b50c023176f31b6728142bf9ec50c485@macports.org> References: <043.b50c023176f31b6728142bf9ec50c485@macports.org> Message-ID: <058.e9abdd6413d34b7017835749e7dc255e@macports.org> #53175: fdupes now v1.6.1 ---------------------+------------------- Reporter: bunk3m | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: fdupes | ---------------------+------------------- Changes (by grimreaper): * Attachment "bump.patch" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 04:20:40 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 04:20:40 -0000 Subject: [MacPorts] #53175: fdupes now v1.6.1 In-Reply-To: <043.b50c023176f31b6728142bf9ec50c485@macports.org> References: <043.b50c023176f31b6728142bf9ec50c485@macports.org> Message-ID: <058.76dff0a02aca02aa886a86b37c5ed882@macports.org> #53175: fdupes now v1.6.1 ---------------------+------------------- Reporter: bunk3m | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: fdupes | ---------------------+------------------- Comment (by grimreaper): actually, due to an old bug this patch will resolve in > fdupes 1.6.1_0 < 1.51_0 How do I bump the 'port epoch' ? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 06:01:15 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 06:01:15 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.2103a32c6260bbcf02a10d9db004a5ae@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by MarcusCalhoun-Lopez): Attached is a proposal for {{{qt5-1.0.tcl}}}. To address some further questions: * {{{qt5-qtbase}}}, {{{qt56-qtbase}}}, and {{{qt5-kde}}} all conflict with one-another * {{{qt5X-component}}} depends on {{{qt5X-qtbase}}} (**not** a path dependency) * this way, there can be only **one** Qt installed at a time * qt5.depends_component uses a path dependency * this way, a user can install {{{qt5-kde}}} and then install {{{octave +qt5}}} * this assumes that all the Qts are API compatible * when {{{qt5}}} (or {{{qt5-kde}}}) is upgraded and some systems are left behind, it is the responsibility of {{{qt5}}} to include, e.g., {{{replaced_by qt56}}} for those systems With this setup, I do not believe automatic generation of variants is necessary. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 06:01:53 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 06:01:53 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.9fd917842fa08a818b1bb6a52dc7bc4c@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Changes (by MarcusCalhoun-Lopez): * Attachment "qt5-1.0.tcl" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 06:02:29 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 06:02:29 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.0c07ffcb4c4a9e1ef7b742baa2904d6f@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Changes (by MarcusCalhoun-Lopez): * Attachment "qt5-1.0.tcl.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 07:20:06 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 07:20:06 -0000 Subject: [MacPorts] #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X In-Reply-To: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> References: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> Message-ID: <061.8cc7bd6a075b56065de012c178e8aa2a@macports.org> #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X ------------------------+--------------------------- Reporter: ballapete | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: tiger powerpc Port: libuv | ------------------------+--------------------------- Comment (by kencu): something like this should work {{{ platform darwin 8 { configure.args-delete --system-libs \ --no-system-jsoncpp # is this the right way to delete the path / port dep? #depends_lib-append path:lib/pkgconfig/libuv.pc:libuv depends_lib-delete port:libuv } }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 07:52:49 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 07:52:49 -0000 Subject: [MacPorts] #53176: py36-gnureadline @6.3.3_1: python3.6 crashes with malloc: pointer being freed was not allocated Message-ID: <047.6d5d604bea32c01385c321b1bde3dd00@macports.org> #53176: py36-gnureadline @6.3.3_1: python3.6 crashes with malloc: pointer being freed was not allocated ------------------------+---------------------------- Reporter: mndavidoff | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: py-gnureadline ------------------------+---------------------------- Installing py36-gnureadline causes python3.6 to crash. Without py36-gnureadline: {{{ $ port installed py36-gnureadline None of the specified ports are installed. $ python3.6 Python 3.6.0 (default, Dec 28 2016, 22:59:42) [GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.42.1)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> 1+2 3 >>> ^D }}} With py36-gnureadline: {{{ $ port installed py36-gnureadline The following ports are currently installed: py36-gnureadline @6.3.3_1 (active) $ python3.6 Python 3.6.0 (default, Dec 28 2016, 22:59:42) [GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.42.1)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> 1+2 Python(53168,0x7fffd7e0f3c0) malloc: *** error for object 0x109b63698: pointer being freed was not allocated *** set a breakpoint in malloc_error_break to debug Abort trap: 6 }}} Curiously, this problem does not affect ipython: {{{ $ ipython3-3.6 Python 3.6.0 (default, Dec 28 2016, 22:59:42) Type "copyright", "credits" or "license" for more information. IPython 5.1.0 -- An enhanced Interactive Python. ? -> Introduction and overview of IPython's features. %quickref -> Quick reference. help -> Python's own help system. object? -> Details about 'object', use 'object??' for extra details. In [1]: 1+2 Out[1]: 3 In [2]: exit }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 08:07:04 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 08:07:04 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.8f45a20521c20bde6aa2a3bd33cbad17@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by mojca): This doesn't make the variants unnecessary. If the buildbot built `octave` against `qt5-qtbase` and the user decided to install `qt5-kde`, then unless the two ports are fully ABI-compatible, this will still lead to problems. There's one more thing. There is a very small number of ports from Qt 5.6 that breaks on 10.7, but even then most of them only break because they need C++11 and would probably work fine under `libc++` default. So a pretty large population of 10.7 users might be OK with 5.6, while some users with particular needs might opt for 5.5 on the same OS version to be able to support some specific ports. I can imagine the same situation on other OS versions and a different set of Qt versions. On the other hand I wouldn't even create a variant for Qt 5.7 on 10.6-10.7 and I wouldn't create a variant for Qt 5.5 on 10.9 for example. Yes, variants are ugly, but probably the only way to make things work properly. (Just don't ask me how the user is supposed to switch between the variants. Actually having `qt55-*` co-installable with `qt56-*` at a different location would make things much easier and then users could even have both installed at the same time and pick a different variant for different ports if they would need that for some reason. We could perhaps one day install `qt55` with `stdlibc++` and `qt56` with `libc++` and then users of 10.7-10.8 could pick `qt56` for C++11 projects and `qt55` for everything else. Just brainstorming.) In `wxWidgets` I used: {{{ #!tcl wxWidgets.setup wxWidgets-3.0 # or wxGTK-2.8 or anything else depends-lib ${wxWidgets.port} }}} but {{{ #!tcl qt5.depends_component qt5 qtwebengine }}} sounds OK to me. The components would then be selected based on the variant being used. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 09:48:33 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 09:48:33 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.20051243f3f7e0bbd07eb728ec386fa0@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by RJVB): Replying to [comment:12 MarcusCalhoun-Lopez]: > Attached is a proposal for {{{qt5-1.0.tcl}}}. That has become a huge function! A couple of points, I hope I'm concise enough: - port:qt5 currently installs the pkg-config files to `${qt_libs_dir}/pkgconfig`. Is that to be changed? - I don't really like the "-append" suffix, if not only because it suggests there are also "-prepend", "-replace" etc. modifiers. - qt5.using_kde isn't always defined, I don't know if `[tbool qt5.using_kde]` catches all possible situations(?) Evidently the variable could be defined by the shared PortGroup. I am VERY much in favour of maintaining the PortGroup approach implemented in https://github.com/RJVB/macstrop/blob/master/_resources/port1.0/group/qt5-1.0.tcl which allows us to keep separated the things that are best kept separated, like install locations and possibly variants. In that approach, `qt5-1.0.tcl` only contains the logic that decides which Qt5 port is (or is to be) installed and thus which dedicated PortGroup to load, as well as common functions like `qt5.depends_component`. This file could be called qt5-1.1.tcl as far as I'm concerned, but in that case we will have to do a forced upgrade of all PortGroup expressions in all dependent ports. Either way, with dedicated portgroups containing the port-specific logic the big switch in Marcus's proposal could be replaced with a lookup in a table that's defined in the dedicated portgroup. My own proposal already carries a prototype implementation of that. The advantage is that it keeps the shared PortGroup as lean as possible, AND let's each of us handle the depspecs details as best fits the port's main purpose. - My own function above uses the `is_qt5kde` local variable to avoid adding dependencies on stub ports. The qt5-kde stub ports are mostly there to be able to satisfy dependency requirements when someone moves from port:qt5 to port:qt5-kde . A user who installs port:qt5-kde from the start shouldn't be obliged to need them. The attached new proposal has a different effect: from what I can see it will add another (and different!) depspec on `qt5-kde` for each required component which is provided by `port:qt5kde`. That isn't very elegant and I don't know how "base" will handle the different path-style dependencies on a single port. A priori I think that this can be avoided by returning early from the default case (line 305 in the attachment); the qt5-kde PortGroup already adds a dependency. > qt5X-component depends on qt5X-qtbase (not a path dependency) I suppose that's something that is handled in `port:qt5` and `port:qt55`? The qt5-kde stubports evidently have a dependency on the `port:qt5-kde`. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 10:53:49 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 10:53:49 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.0074f536ec3c3673c5dc7a2a5dac352b@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by RJVB): Replying to [comment:13 mojca]: > This doesn't make the variants unnecessary. If the buildbot built `octave` against `qt5-qtbase` and the user decided to install `qt5-kde`, then unless the two ports are fully ABI-compatible, this will still lead to problems. Variant or not, if you replace a dependency with a non-ABI compatible alternative you will have problems. I'm not aware of anything in MacPorts that provides a 100% protection there. In my experience `rev-upgrade` isn't run systematically when you install a port (rather than upgrade), and never when you use de/activation. But even if it were it doesn't check the full ABI, just library presence, dependencies and compatibility version. You can move from port:qt5 to port:qt5-kde, at least that's what my tests until now have shown. The KDE patches do introduce some ABI changes which may make moving back less evident, but this can be documented. I am also in the process of upgrading the port to Qt 5.7 because some KDE software already requires that Qt version. Qt's own ABI compatibility rules ensure that you can still move from port:qt5 (5.6) to port:qt5-kde (5.7), potentially breaking only ports that use private APIs. NB: I think Qt Creator uses a few private APIs, but it does so in a way that still allows you to run it after upgrading Qt to a new major version. This is the reason my qt5-kde PortGroup declares and sets the `+qt5kde` variant when `port:qt5-kde` is used. That variant isn't intended to be manipulated by the user, it is just there as a label, and to allow the build-bots to provide binaries that are built against the ports' preferred Qt5 "flavour". Make no mistake: the most important of my Qt5 KDE patches requires code to be built against port:qt5-kde because the preprocessor is involved and, yes, a subtle, behind-the-scenes change to an API. Ports built against `port:qt55` could be labelled the same way, with a `+qt55` variant. > So a pretty large population of 10.7 users might be OK with 5.6, while some users with particular needs might opt for 5.5 on the same OS version to be able to support some specific ports. I can imagine the same situation on other OS versions and a different set of Qt versions. Yes. The same question will arise with Qt 5.6 vs. 5.7 or 5.8 or higher. In fact, it almost arose for QtWebEngine already (5.7.0 didn't build on 10.9, 5.7.1 does but not with the preferred 10.9 SDK). I don't intend to provide a qt5-kde 5.5 version because a majority of KDE software now require Qt 5.6.2 as the minimal version. I try to keep the port set up so that it can be built on 10.7, either with libc++ or else using gcc, but I cannot test that myself so it is "officially unsupported". > On the other hand I wouldn't even create a variant for Qt 5.7 on 10.6-10.7 and I wouldn't create a variant for Qt 5.5 on 10.9 for example. No. Qt 5.5 might have an interest on recent OS X versions for user developing for 10.7, but I don't think we have to cater to that particular niche. > Yes, variants are ugly, but probably the only way to make things work properly. I agree, to the extent outlined above. I.e. variant(s) that label builds but nothing else. As you say, how should it work when a user has `port:qt5` installed and then requests, say `port install kf5-kwallet +qt5kde`? Using path-style dependencies to allow different Qt5 ports to provide the necessary dependencies means there is no implicit conflict information in the depspecs, so all we can do is test for presence of the requested Qt5 port and raise an error if that fails. I'm not sure if there's much point in that. For one, the KF5 PortGroup already checks which Qt5 is installed, and raises a big warning if it's not qt5-kde. I also have checks against `variant_exists qt5kde` and `!variant_isset qt5kde`; that's an error. I would have to think more (and hard) to see if there would be a point in defining the qt5kde variant for all qt5 dependents. But I'm pretty sure that is nothing much if anything to gain from allowing users to use `+qt5kde` as a way to impose `port:qt5-kde`. It's up to ports to indicate which Qt5 flavour works best for them (currently with `set qt5.prefer_kde 1` before loading the portgroup). For the rest the choice should be made at the level of installing a Qt5 port and be as transparent as possible. > Actually having `qt55-*` co-installable with `qt56-*` at a different location would make things much easier and then users could even have both installed at the same time and pick a different variant for different ports if they would need that for some reason. I have a hunch that concurrent installation will prove to be a Pandora's box and maintenance nightmare. With 2 monolithic ports (aka qt4-mac which just installs all of Qt4) this might still be doable, but with `port:qt5` broken up into a growing number of subports the chances that things go wrong through unintended mix-and-match at build-time or even runtime are too high. There's only 1 reason why one might want to have different "medior" Qt5 versions installed, and that's for development purposes. I think that goes beyond the intended scope of MacPorts. Qt already caters to that kind of need through its own installers, and I can tell from experience that it works fine to have a single Qt4,Qt5 pair installed through MacPorts and any number of other Qt versions in a different prefix and maintained through Qt's own installer (or via a Linux distribution's package manager). With a properly set-up QtChooser you can then even invoke QMake from the commandline and point it to whichever of your Qt versions you have installed and configured. Side-note: there's an old submission ticket on Trac for QtChooser ... > We could perhaps one day install `qt55` with `stdlibc++` and `qt56` with `libc++` and then users of 10.7-10.8 could pick `qt56` for C++11 projects and `qt55` for everything else. Just brainstorming.) Brain fart (O:-)): wouldn't those OS versions be really old and obsolete by the time we get around to considering how to achieve such a loft goal? ;) > In `wxWidgets` I used: > {{{ > #!tcl > wxWidgets.setup wxWidgets-3.0 # or wxGTK-2.8 or anything else > depends-lib ${wxWidgets.port} > }}} Here we're talking about dependencies that aren't ABI compatible AT ALL, even use different backends that cannot be determined at runtime. The analogy here would be +qt4 and +qt5 variants, and indeed we *could* have a generic Qt portgroup that defines such variants which include the expected PortGroup. That could have made sense back in the day when Qt5 was still new and Qt4 still supported; I don't think there's much reason anymore to do this now. > {{{ > #!tcl > qt5.depends_component qt5 qtwebengine > }}} > sounds OK to me. > The components would then be selected based on the variant being used. No, not that please! That would defeat the whole effort to make the Qt5 ports drop-in alternatives so that users can decide what kind of experience they want simply be installing Qt5 one way or another. - Want KF5 applications that work properly? Install `port:qt5-kde`, or just install any KF5 port from scratch. Other dependents on Qt5 will work fine but will be built from source (but there aren't many that are as complex and expensive to build as KF5). - Don't care about KF5 applications but more about a stock Qt5 and getting binary installs from the build bots? Install `port:qt5` or any non KF5 port that needs Qt5. If at some point a regular Qt5 dependent declares a dependency on a KF5 framework (say, KWallet support in QupZilla) you'll end up building the required KF5 frameworks from source and they'll work to an unknown degree. But you can always decide to migrate to `port:qt5-kde`, and the way things are done now this should not expose you to rebuilding or reinstalling everything. To add to what I said above: I think that as soon as we do this, and start allowing users to set or unset `+qt5kde` to control what Qt5 flavour is to be used, we get hard dependencies on either `port:qt5` or `port:qt5-kde`. That means we also have to start handling conflicts. There are over 60 KF5 Frameworks, a large part of which have intradependencies, and those frameworks are intended to be usable in code that has otherwise nothing to do with KDE. Handling this properly and not with a crude check will be a combinatorial nightmare. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 11:06:29 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 11:06:29 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.ba60af24fca67db4c4df7d8a8e709229@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by RJVB): And one last thing: that main KDE patch which introduces an ABI enrichment is designed to be submitted upstream. I've been in on-and-off contact with Qt devs about this for a long time, but upstreaming patches into Qt is a complex and difficult procedure, which in this case will need real-life proof of the value of a change that could have important implications for Qt's commercial customers. Either way, the point is that there is some hope that this particular patch will be included upstream at some point (we're probably talking 5.9 by now ...). If so, it'll become available through `port:qt5` too. That will not remove all justification for `port:qt5-kde`, but it will mean that I can start offering more support for building KF5 code against a stock Qt5, and the ABI differences between `port:qt5-kde` and `port:qt5` should disappear completely. It would be a pity to have to impose more or less crude conflicts and installation impossibilities and then to undo them. Evidently, nothing stops Marcus from testing the patch in question on his end, and including it. It should be mature enough and not change significantly anymore (... soon ...). Just saying; that decision is his as much as the patch is mine :) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 13:25:30 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 13:25:30 -0000 Subject: [MacPorts] #53177: activator @1.3.12 : new port Message-ID: <048.c53ca43819289286db81094705cf6daf@macports.org> #53177: activator @1.3.12 : new port -------------------------+----------------------- Reporter: nhojpatrick | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: activator -------------------------+----------------------- New port submission for activator used by the play framework. I've put it down as nomaintainer as not sure what to put? Is that me or only macport developers? The worksrcdir and destroot sections I believe are correct as looked at a few other Portfile(s) for inspiration. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 13:29:03 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 13:29:03 -0000 Subject: [MacPorts] #53177: activator @1.3.12 : new port In-Reply-To: <048.c53ca43819289286db81094705cf6daf@macports.org> References: <048.c53ca43819289286db81094705cf6daf@macports.org> Message-ID: <063.bce4e88e4b23fd514f5773745000e9ee@macports.org> #53177: activator @1.3.12 : new port --------------------------+---------------------- Reporter: nhojpatrick | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: activator | --------------------------+---------------------- Comment (by nhojpatrick): Pull Request https://github.com/macports/macports-ports/pull/130 fyi it might be useful to have haspullrequest alongside haspatch. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 13:43:15 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 13:43:15 -0000 Subject: [MacPorts] #53178: php55 @5.5.36: update to 5.5.38 Message-ID: <041.2b3adeb402165ddee783bab38bd49f92@macports.org> #53178: php55 @5.5.36: update to 5.5.38 --------------------+------------------- Reporter: l2dy | Owner: Type: update | Status: new Priority: High | Milestone: Component: ports | Version: Keywords: | Port: php55 --------------------+------------------- Multiple CVEs, see http://php.net/ChangeLog-5.php#5.5.38. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 14:05:10 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 14:05:10 -0000 Subject: [MacPorts] #53179: exim @4.82.1_2: update to 4.88 Message-ID: <041.e5aeac40016423985e94535da8f2da94@macports.org> #53179: exim @4.82.1_2: update to 4.88 --------------------+------------------ Reporter: l2dy | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: exim --------------------+------------------ CVE-2016-9963 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 14:09:49 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 14:09:49 -0000 Subject: [MacPorts] #50671: boost: Update to 1.63.0 In-Reply-To: <045.068f49dfc49c577073cb3ffe59aec898@macports.org> References: <045.068f49dfc49c577073cb3ffe59aec898@macports.org> Message-ID: <060.d1db950873f4605c9c0ac753c9de1c0a@macports.org> #50671: boost: Update to 1.63.0 -----------------------+------------------------ Reporter: eborisch | Owner: ryandesign Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch Port: boost | -----------------------+------------------------ Comment (by michaelld): I know little about why Boost patches are in place. I can see from the Portfile comments that at last some portion of the patches were integrated into Boost a while back, but clearly not all of them. In my belief, if the patches can still be applied then they should continue to be used, that there's a reason they are there in the first place & are highly likely to continue to be needed. That said, if folks want to do testing by commenting out any specific patch then I'd welcome feedback as to if/how that worked. I don't have time to do this just right now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 14:58:05 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 14:58:05 -0000 Subject: [MacPorts] #53170: py-mitmproxy @0.17.1: update to 1.0.1 In-Reply-To: <041.e8ce91fc13b3930d86b86a43dd0d084a@macports.org> References: <041.e8ce91fc13b3930d86b86a43dd0d084a@macports.org> Message-ID: <056.1dc22ce25d5d76a5ddcae9ba167ea78a@macports.org> #53170: py-mitmproxy @0.17.1: update to 1.0.1 ---------------------------+------------------------ Reporter: l2dy | Owner: mdeaudelin Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-mitmproxy | ---------------------------+------------------------ Changes (by mf2k): * status: new => assigned * owner: => mdeaudelin * cc: mdeaudelin (removed) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 15:12:53 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 15:12:53 -0000 Subject: [MacPorts] #53117: Braeburn POST requests (Trac, Mailman) are unreliable In-Reply-To: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> References: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> Message-ID: <056.79ec2a39f32e8916adcf071ba180cb25@macports.org> #53117: Braeburn POST requests (Trac, Mailman) are unreliable -----------------------------+--------------------- Reporter: mf2k | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+--------------------- Comment (by mf2k): The problem happened again to me today. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 15:20:40 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 15:20:40 -0000 Subject: [MacPorts] #40904: tesseract @3.02.02: some language subports conflict In-Reply-To: <047.d0ac243462a4a66a1ad76872e44f85be@macports.org> References: <047.d0ac243462a4a66a1ad76872e44f85be@macports.org> Message-ID: <062.fb97d3281325c1a2ff48a4947de4cf64@macports.org> #40904: tesseract @3.02.02: some language subports conflict -------------------------+---------------------- Reporter: ryandesign | Owner: markemer Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: fixed | Keywords: Port: tesseract | -------------------------+---------------------- Changes (by mf2k): * status: new => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 15:20:42 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 15:20:42 -0000 Subject: [MacPorts] #53180: Processing of port arb failed Message-ID: <045.02177858dbd15b1e9c09234e4adb755f@macports.org> #53180: Processing of port arb failed ----------------------+------------------- Reporter: walker92 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: arb | Port: arb ----------------------+------------------- Trying to install Arb using the easy method of This is what was in the terminal: Last login: Thu Dec 29 09:45:35 on ttys001 Ryan-Walkers-iMac:~ walker92$ sudo port install arb Password: ---> Computing dependencies for arb ---> Dependencies to be installed: coreutils gettext expat libiconv ncurses gmp glew glib2 libffi pcre bzip2 libedit zlib glw autoconf automake libpng libtool mesa xorg-dri2proto xorg-glproto xorg-libX11 xorg- kbproto xorg-libXau xorg-xproto xorg-libXdmcp xorg-libxcb python27 db48 openssl python2_select python_select sqlite3 xorg-libpthread-stubs xorg- xcb-proto libxml2 xz xorg-libXdamage xorg-damageproto xorg-libXfixes xorg- fixesproto xorg-xextproto xorg-libXext xorg-libXi xorg-inputproto xorg- libXmu xorg-libXt xorg-libsm xorg-libice xorg-libXxf86vm xorg- xf86vidmodeproto openmotif Xft2 fontconfig freetype xrender xorg- renderproto bison bison-runtime m4 flex jpeg pkgconfig xbitmaps xorg-libXp xorg-printproto gsed gtime gv Xaw3d xpm ghostscript jbig2dec lcms2 tiff libidn libpaper perl5 perl5.24 gdbm xorg-libXinerama xorg-xineramaproto lynx makedepend sablotron spidermonkey nspr readline xfig transfig netpbm jasper jbigkit libnetpbm xorg-libXaw ---> Fetching archive for expat ---> Attempting to fetch expat-2.2.0_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/expat ---> Attempting to fetch expat-2.2.0_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/expat ---> Installing expat @2.2.0_0 ---> Activating expat @2.2.0_0 ---> Cleaning expat ---> Fetching archive for libiconv ---> Attempting to fetch libiconv-1.14_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/libiconv ---> Attempting to fetch libiconv-1.14_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/libiconv ---> Installing libiconv @1.14_0 ---> Activating libiconv @1.14_0 ---> Cleaning libiconv ---> Fetching archive for ncurses ---> Attempting to fetch ncurses-6.0_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/ncurses ---> Attempting to fetch ncurses-6.0_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/ncurses ---> Installing ncurses @6.0_0 ---> Activating ncurses @6.0_0 ---> Cleaning ncurses ---> Fetching archive for gettext ---> Attempting to fetch gettext-0.19.8.1_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/gettext ---> Attempting to fetch gettext-0.19.8.1_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/gettext ---> Installing gettext @0.19.8.1_0 ---> Activating gettext @0.19.8.1_0 ---> Cleaning gettext ---> Fetching distfiles for gmp ---> Verifying checksums for gmp ---> Extracting gmp ---> Applying patches to gmp ---> Configuring gmp ---> Building gmp ---> Staging gmp into destroot ---> Installing gmp @6.1.2_0 ---> Activating gmp @6.1.2_0 ---> Cleaning gmp ---> Fetching archive for coreutils ---> Attempting to fetch coreutils-8.26_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/coreutils ---> Attempting to fetch coreutils-8.26_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/coreutils ---> Installing coreutils @8.26_0 ---> Activating coreutils @8.26_0 The tools provided by GNU coreutils are prefixed with the character 'g' by default to distinguish them from the BSD commands. For example, cp becomes gcp and ls becomes gls. If you want to use the GNU tools by default, add this directory to the front of your PATH environment variable: /opt/local/libexec/gnubin/ ---> Cleaning coreutils ---> Fetching archive for glew ---> Attempting to fetch glew-2.0.0_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/glew ---> Attempting to fetch glew-2.0.0_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/glew ---> Installing glew @2.0.0_0 ---> Activating glew @2.0.0_0 ---> Cleaning glew ---> Fetching archive for libffi ---> Attempting to fetch libffi-3.2.1_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/libffi ---> Attempting to fetch libffi-3.2.1_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/libffi ---> Installing libffi @3.2.1_0 ---> Activating libffi @3.2.1_0 ---> Cleaning libffi ---> Fetching archive for bzip2 ---> Attempting to fetch bzip2-1.0.6_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/bzip2 ---> Attempting to fetch bzip2-1.0.6_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/bzip2 ---> Installing bzip2 @1.0.6_0 ---> Activating bzip2 @1.0.6_0 ---> Cleaning bzip2 ---> Fetching archive for libedit ---> Attempting to fetch libedit-20160903-3.1_1.darwin_15.x86_64.tbz2 from https://packages.macports.org/libedit ---> Attempting to fetch libedit-20160903-3.1_1.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/libedit ---> Installing libedit @20160903-3.1_1 ---> Activating libedit @20160903-3.1_1 ---> Cleaning libedit ---> Fetching archive for zlib ---> Attempting to fetch zlib-1.2.8_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/zlib ---> Attempting to fetch zlib-1.2.8_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/zlib ---> Installing zlib @1.2.8_0 ---> Activating zlib @1.2.8_0 ---> Cleaning zlib ---> Fetching archive for pcre ---> Attempting to fetch pcre-8.39_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/pcre ---> Attempting to fetch pcre-8.39_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/pcre ---> Installing pcre @8.39_0 ---> Activating pcre @8.39_0 ---> Cleaning pcre ---> Fetching archive for glib2 ---> Attempting to fetch glib2-2.50.2_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/glib2 ---> Attempting to fetch glib2-2.50.2_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/glib2 ---> Installing glib2 @2.50.2_0 ---> Activating glib2 @2.50.2_0 ---> Cleaning glib2 ---> Fetching archive for autoconf ---> Attempting to fetch autoconf-2.69_5.darwin_15.noarch.tbz2 from https://packages.macports.org/autoconf ---> Attempting to fetch autoconf-2.69_5.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/autoconf ---> Installing autoconf @2.69_5 ---> Activating autoconf @2.69_5 ---> Cleaning autoconf ---> Fetching archive for automake ---> Attempting to fetch automake-1.15_1.darwin_15.noarch.tbz2 from https://packages.macports.org/automake ---> Attempting to fetch automake-1.15_1.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/automake ---> Installing automake @1.15_1 ---> Activating automake @1.15_1 ---> Cleaning automake ---> Fetching archive for libpng ---> Attempting to fetch libpng-1.6.26_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/libpng ---> Attempting to fetch libpng-1.6.26_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/libpng ---> Installing libpng @1.6.26_0 ---> Activating libpng @1.6.26_0 ---> Cleaning libpng ---> Fetching archive for libtool ---> Attempting to fetch libtool-2.4.6_2.darwin_15.x86_64.tbz2 from https://packages.macports.org/libtool ---> Attempting to fetch libtool-2.4.6_2.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/libtool ---> Installing libtool @2.4.6_2 ---> Activating libtool @2.4.6_2 ---> Cleaning libtool ---> Fetching archive for xorg-dri2proto ---> Attempting to fetch xorg-dri2proto-2.8_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-dri2proto ---> Attempting to fetch xorg- dri2proto-2.8_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-dri2proto ---> Installing xorg-dri2proto @2.8_0 ---> Activating xorg-dri2proto @2.8_0 ---> Cleaning xorg-dri2proto ---> Fetching archive for xorg-glproto ---> Attempting to fetch xorg-glproto-1.4.17_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-glproto ---> Attempting to fetch xorg- glproto-1.4.17_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-glproto ---> Installing xorg-glproto @1.4.17_0 ---> Activating xorg-glproto @1.4.17_0 ---> Cleaning xorg-glproto ---> Fetching archive for xorg-kbproto ---> Attempting to fetch xorg-kbproto-1.0.7_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-kbproto ---> Attempting to fetch xorg- kbproto-1.0.7_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-kbproto ---> Installing xorg-kbproto @1.0.7_0 ---> Activating xorg-kbproto @1.0.7_0 ---> Cleaning xorg-kbproto ---> Fetching archive for xorg-xproto ---> Attempting to fetch xorg-xproto-7.0.31_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-xproto ---> Attempting to fetch xorg- xproto-7.0.31_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-xproto ---> Installing xorg-xproto @7.0.31_0 ---> Activating xorg-xproto @7.0.31_0 ---> Cleaning xorg-xproto ---> Fetching archive for xorg-libXau ---> Attempting to fetch xorg-libXau-1.0.8_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libXau ---> Attempting to fetch xorg-libXau-1.0.8_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libXau ---> Installing xorg-libXau @1.0.8_0 ---> Activating xorg-libXau @1.0.8_0 ---> Cleaning xorg-libXau ---> Fetching archive for xorg-libXdmcp ---> Attempting to fetch xorg-libXdmcp-1.1.2_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libXdmcp ---> Attempting to fetch xorg- libXdmcp-1.1.2_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libXdmcp ---> Installing xorg-libXdmcp @1.1.2_0 ---> Activating xorg-libXdmcp @1.1.2_0 ---> Cleaning xorg-libXdmcp ---> Fetching archive for db48 ---> Attempting to fetch db48-4.8.30_4.darwin_15.x86_64.tbz2 from https://packages.macports.org/db48 ---> Attempting to fetch db48-4.8.30_4.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/db48 ---> Installing db48 @4.8.30_4 ---> Activating db48 @4.8.30_4 ---> Cleaning db48 ---> Fetching archive for openssl ---> Attempting to fetch openssl-1.0.2j_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/openssl ---> Attempting to fetch openssl-1.0.2j_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/openssl ---> Installing openssl @1.0.2j_0 ---> Activating openssl @1.0.2j_0 ---> Cleaning openssl ---> Fetching archive for python2_select ---> Attempting to fetch python2_select-0.0_2.darwin_15.noarch.tbz2 from https://packages.macports.org/python2_select ---> Attempting to fetch python2_select-0.0_2.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/python2_select ---> Installing python2_select @0.0_2 ---> Activating python2_select @0.0_2 ---> Cleaning python2_select ---> Fetching archive for python_select ---> Attempting to fetch python_select-0.3_7.darwin_15.noarch.tbz2 from https://packages.macports.org/python_select ---> Attempting to fetch python_select-0.3_7.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/python_select ---> Installing python_select @0.3_7 ---> Activating python_select @0.3_7 ---> Cleaning python_select ---> Fetching archive for sqlite3 ---> Attempting to fetch sqlite3-3.15.2_2.darwin_15.x86_64.tbz2 from https://packages.macports.org/sqlite3 ---> Attempting to fetch sqlite3-3.15.2_2.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/sqlite3 ---> Installing sqlite3 @3.15.2_2 ---> Activating sqlite3 @3.15.2_2 ---> Cleaning sqlite3 ---> Fetching archive for python27 ---> Attempting to fetch python27-2.7.13_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/python27 ---> Attempting to fetch python27-2.7.13_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/python27 ---> Installing python27 @2.7.13_0 ---> Activating python27 @2.7.13_0 To make this the default Python or Python 2 (i.e., the version run by the 'python' or 'python2' commands), run one or both of: sudo port select --set python python27 sudo port select --set python2 python27 ############################################################## # IF YOU ARE USING PYTHON FROM THE TERMINAL, PLEASE INSTALL: # py27-readline # TO AVOID A LIBEDIT / PYTHON INTERACTION ISSUE. # REF: https://trac.macports.org/ticket/48807 ############################################################## ---> Cleaning python27 ---> Fetching archive for xorg-libpthread-stubs ---> Attempting to fetch xorg-libpthread- stubs-0.3_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg- libpthread-stubs ---> Attempting to fetch xorg-libpthread- stubs-0.3_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-libpthread-stubs ---> Installing xorg-libpthread-stubs @0.3_0 ---> Activating xorg-libpthread-stubs @0.3_0 ---> Cleaning xorg-libpthread-stubs ---> Fetching archive for xz ---> Attempting to fetch xz-5.2.2_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xz ---> Attempting to fetch xz-5.2.2_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xz ---> Installing xz @5.2.2_0 ---> Activating xz @5.2.2_0 ---> Cleaning xz ---> Fetching archive for libxml2 ---> Attempting to fetch libxml2-2.9.4_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/libxml2 ---> Attempting to fetch libxml2-2.9.4_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/libxml2 ---> Installing libxml2 @2.9.4_0 ---> Activating libxml2 @2.9.4_0 ---> Cleaning libxml2 ---> Fetching archive for xorg-xcb-proto ---> Attempting to fetch xorg-xcb- proto-1.12_1+python27.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-xcb-proto ---> Attempting to fetch xorg-xcb- proto-1.12_1+python27.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-xcb-proto ---> Installing xorg-xcb-proto @1.12_1+python27 ---> Activating xorg-xcb-proto @1.12_1+python27 ---> Cleaning xorg-xcb-proto ---> Fetching archive for xorg-libxcb ---> Attempting to fetch xorg- libxcb-1.12_2+python27.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libxcb ---> Attempting to fetch xorg- libxcb-1.12_2+python27.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libxcb ---> Installing xorg-libxcb @1.12_2+python27 ---> Activating xorg-libxcb @1.12_2+python27 ---> Cleaning xorg-libxcb ---> Fetching archive for xorg-libX11 ---> Attempting to fetch xorg-libX11-1.6.4_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libX11 ---> Attempting to fetch xorg-libX11-1.6.4_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libX11 ---> Installing xorg-libX11 @1.6.4_0 ---> Activating xorg-libX11 @1.6.4_0 ---> Cleaning xorg-libX11 ---> Fetching archive for xorg-damageproto ---> Attempting to fetch xorg-damageproto-1.2.1_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-damageproto ---> Attempting to fetch xorg- damageproto-1.2.1_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-damageproto ---> Installing xorg-damageproto @1.2.1_0 ---> Activating xorg-damageproto @1.2.1_0 ---> Cleaning xorg-damageproto ---> Fetching archive for xorg-xextproto ---> Attempting to fetch xorg-xextproto-7.3.0_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-xextproto ---> Attempting to fetch xorg- xextproto-7.3.0_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-xextproto ---> Installing xorg-xextproto @7.3.0_0 ---> Activating xorg-xextproto @7.3.0_0 ---> Cleaning xorg-xextproto ---> Fetching archive for xorg-fixesproto ---> Attempting to fetch xorg-fixesproto-5.0_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-fixesproto ---> Attempting to fetch xorg- fixesproto-5.0_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-fixesproto ---> Installing xorg-fixesproto @5.0_0 ---> Activating xorg-fixesproto @5.0_0 ---> Cleaning xorg-fixesproto ---> Fetching archive for xorg-libXfixes ---> Attempting to fetch xorg-libXfixes-5.0.3_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libXfixes ---> Attempting to fetch xorg- libXfixes-5.0.3_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libXfixes ---> Installing xorg-libXfixes @5.0.3_0 ---> Activating xorg-libXfixes @5.0.3_0 ---> Cleaning xorg-libXfixes ---> Fetching archive for xorg-libXdamage ---> Attempting to fetch xorg-libXdamage-1.1.4_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libXdamage ---> Attempting to fetch xorg- libXdamage-1.1.4_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libXdamage ---> Installing xorg-libXdamage @1.1.4_0 ---> Activating xorg-libXdamage @1.1.4_0 ---> Cleaning xorg-libXdamage ---> Fetching archive for xorg-libXext ---> Attempting to fetch xorg-libXext-1.3.3_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libXext ---> Attempting to fetch xorg- libXext-1.3.3_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libXext ---> Installing xorg-libXext @1.3.3_0 ---> Activating xorg-libXext @1.3.3_0 ---> Cleaning xorg-libXext ---> Fetching archive for xorg-inputproto ---> Attempting to fetch xorg-inputproto-2.3.2_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-inputproto ---> Attempting to fetch xorg- inputproto-2.3.2_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-inputproto ---> Installing xorg-inputproto @2.3.2_0 ---> Activating xorg-inputproto @2.3.2_0 ---> Cleaning xorg-inputproto ---> Fetching archive for xorg-libXi ---> Attempting to fetch xorg-libXi-1.7.8_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libXi ---> Attempting to fetch xorg-libXi-1.7.8_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libXi ---> Installing xorg-libXi @1.7.8_0 ---> Activating xorg-libXi @1.7.8_0 ---> Cleaning xorg-libXi ---> Fetching archive for xorg-libice ---> Attempting to fetch xorg-libice-1.0.9_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libice ---> Attempting to fetch xorg-libice-1.0.9_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libice ---> Installing xorg-libice @1.0.9_0 ---> Activating xorg-libice @1.0.9_0 ---> Cleaning xorg-libice ---> Fetching archive for xorg-libsm ---> Attempting to fetch xorg-libsm-1.2.1_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libsm ---> Attempting to fetch xorg-libsm-1.2.1_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libsm ---> Installing xorg-libsm @1.2.1_0 ---> Activating xorg-libsm @1.2.1_0 ---> Cleaning xorg-libsm ---> Fetching archive for xorg-libXt ---> Attempting to fetch xorg-libXt-1.1.5_1.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libXt ---> Attempting to fetch xorg-libXt-1.1.5_1.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libXt ---> Installing xorg-libXt @1.1.5_1 ---> Activating xorg-libXt @1.1.5_1 ---> Cleaning xorg-libXt ---> Fetching archive for xorg-libXmu ---> Attempting to fetch xorg-libXmu-1.1.2_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libXmu ---> Attempting to fetch xorg-libXmu-1.1.2_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libXmu ---> Installing xorg-libXmu @1.1.2_0 ---> Activating xorg-libXmu @1.1.2_0 ---> Cleaning xorg-libXmu ---> Fetching archive for xorg-xf86vidmodeproto ---> Attempting to fetch xorg- xf86vidmodeproto-2.3.1_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-xf86vidmodeproto ---> Attempting to fetch xorg- xf86vidmodeproto-2.3.1_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-xf86vidmodeproto ---> Installing xorg-xf86vidmodeproto @2.3.1_0 ---> Activating xorg-xf86vidmodeproto @2.3.1_0 ---> Cleaning xorg-xf86vidmodeproto ---> Fetching archive for xorg-libXxf86vm ---> Attempting to fetch xorg-libXxf86vm-1.1.4_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libXxf86vm ---> Attempting to fetch xorg- libXxf86vm-1.1.4_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libXxf86vm ---> Installing xorg-libXxf86vm @1.1.4_0 ---> Activating xorg-libXxf86vm @1.1.4_0 ---> Cleaning xorg-libXxf86vm ---> Fetching archive for mesa ---> Attempting to fetch mesa-12.0.1_2+osmesa+python27.darwin_15.x86_64.tbz2 from https://packages.macports.org/mesa ---> Attempting to fetch mesa-12.0.1_2+osmesa+python27.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/mesa ---> Installing mesa @12.0.1_2+osmesa+python27 ---> Activating mesa @12.0.1_2+osmesa+python27 ---> Cleaning mesa ---> Fetching archive for freetype ---> Attempting to fetch freetype-2.7_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/freetype ---> Attempting to fetch freetype-2.7_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/freetype ---> Installing freetype @2.7_0 ---> Activating freetype @2.7_0 ---> Cleaning freetype ---> Fetching archive for fontconfig ---> Attempting to fetch fontconfig-2.12.1_1.darwin_15.x86_64.tbz2 from https://packages.macports.org/fontconfig ---> Attempting to fetch fontconfig-2.12.1_1.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/fontconfig ---> Installing fontconfig @2.12.1_1 ---> Activating fontconfig @2.12.1_1 ---> Cleaning fontconfig ---> Fetching archive for xorg-renderproto ---> Attempting to fetch xorg-renderproto-0.11.1_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-renderproto ---> Attempting to fetch xorg- renderproto-0.11.1_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-renderproto ---> Installing xorg-renderproto @0.11.1_0 ---> Activating xorg-renderproto @0.11.1_0 ---> Cleaning xorg-renderproto ---> Fetching archive for xrender ---> Attempting to fetch xrender-0.9.10_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xrender ---> Attempting to fetch xrender-0.9.10_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xrender ---> Installing xrender @0.9.10_0 ---> Activating xrender @0.9.10_0 ---> Cleaning xrender ---> Fetching archive for Xft2 ---> Attempting to fetch Xft2-2.3.2_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/Xft2 ---> Attempting to fetch Xft2-2.3.2_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/Xft2 ---> Installing Xft2 @2.3.2_0 ---> Activating Xft2 @2.3.2_0 ---> Cleaning Xft2 ---> Fetching archive for bison-runtime ---> Attempting to fetch bison-runtime-3.0.4_0.darwin_15.noarch.tbz2 from https://packages.macports.org/bison-runtime ---> Attempting to fetch bison- runtime-3.0.4_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/bison-runtime ---> Installing bison-runtime @3.0.4_0 ---> Activating bison-runtime @3.0.4_0 ---> Cleaning bison-runtime ---> Fetching archive for m4 ---> Attempting to fetch m4-1.4.17_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/m4 [ ] 95.1 % speed: 3.6 KiB/s ---> Attempting to fetch m4-1.4.17_0.darwin_15.x86_64.tbz2 from http://sea.us.packages.macports.org/macports/packages/m4 ---> Attempting to fetch m4-1.4.17_0.darwin_15.x86_64.tbz2.rmd160 from http://sea.us.packages.macports.org/macports/packages/m4 ---> Installing m4 @1.4.17_0 ---> Activating m4 @1.4.17_0 ---> Cleaning m4 ---> Fetching archive for bison ---> Attempting to fetch bison-3.0.4_1.darwin_15.x86_64.tbz2 from https://packages.macports.org/bison ---> Attempting to fetch bison-3.0.4_1.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/bison ---> Installing bison @3.0.4_1 ---> Activating bison @3.0.4_1 ---> Cleaning bison ---> Fetching archive for flex ---> Attempting to fetch flex-2.6.0_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/flex ---> Attempting to fetch flex-2.6.0_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/flex ---> Installing flex @2.6.0_0 ---> Activating flex @2.6.0_0 ---> Cleaning flex ---> Fetching archive for jpeg ---> Attempting to fetch jpeg-9b_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/jpeg ---> Attempting to fetch jpeg-9b_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/jpeg ---> Installing jpeg @9b_0 ---> Activating jpeg @9b_0 ---> Cleaning jpeg ---> Fetching archive for pkgconfig ---> Attempting to fetch pkgconfig-0.29.1_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/pkgconfig ---> Attempting to fetch pkgconfig-0.29.1_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/pkgconfig ---> Installing pkgconfig @0.29.1_0 ---> Activating pkgconfig @0.29.1_0 ---> Cleaning pkgconfig ---> Fetching archive for xbitmaps ---> Attempting to fetch xbitmaps-1.1.1_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xbitmaps ---> Attempting to fetch xbitmaps-1.1.1_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xbitmaps ---> Installing xbitmaps @1.1.1_0 ---> Activating xbitmaps @1.1.1_0 ---> Cleaning xbitmaps ---> Fetching archive for xorg-printproto ---> Attempting to fetch xorg-printproto-1.0.5_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-printproto ---> Attempting to fetch xorg- printproto-1.0.5_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-printproto ---> Installing xorg-printproto @1.0.5_0 ---> Activating xorg-printproto @1.0.5_0 ---> Cleaning xorg-printproto ---> Fetching archive for xorg-libXp ---> Attempting to fetch xorg-libXp-1.0.3_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libXp ---> Attempting to fetch xorg-libXp-1.0.3_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libXp ---> Installing xorg-libXp @1.0.3_0 ---> Activating xorg-libXp @1.0.3_0 ---> Cleaning xorg-libXp ---> Fetching archive for openmotif Error: org.macports.archivefetch for port openmotif returned: xorg-libXt must be installed with +flat_namespace. Error: Failed to install openmotif Please see the log file for port openmotif for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_openmotif/openmotif/main.log Error: The following dependencies were not installed: glw openmotif gsed gtime gv Xaw3d xpm ghostscript jbig2dec lcms2 tiff libidn libpaper perl5 perl5.24 gdbm xorg-libXinerama xorg-xineramaproto lynx makedepend sablotron spidermonkey nspr readline xfig transfig netpbm jasper jbigkit libnetpbm xorg-libXaw To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port arb failed Ryan-Walkers-iMac:~ walker92$ -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 15:35:51 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 15:35:51 -0000 Subject: [MacPorts] #53175: fdupes now v1.6.1 In-Reply-To: <043.b50c023176f31b6728142bf9ec50c485@macports.org> References: <043.b50c023176f31b6728142bf9ec50c485@macports.org> Message-ID: <058.59c2321c080566868ef8c9b2cba5687d@macports.org> #53175: fdupes now v1.6.1 ---------------------+------------------------ Reporter: bunk3m | Owner: grimreaper Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: fdupes | ---------------------+------------------------ Changes (by mf2k): * cc: lists@… (removed) * keywords: => haspatch * version: 2.3.5 => * status: new => assigned * owner: => grimreaper Comment: Thanks. You have to add the {{{epoch}}} line. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 15:36:16 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 15:36:16 -0000 Subject: [MacPorts] #53175: fdupes now v1.6.1 In-Reply-To: <043.b50c023176f31b6728142bf9ec50c485@macports.org> References: <043.b50c023176f31b6728142bf9ec50c485@macports.org> Message-ID: <058.a8c38d89e883a41c76a491119be87af6@macports.org> #53175: fdupes now v1.6.1 ---------------------+--------------------------------- Reporter: bunk3m | Owner: grimreaper Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: fdupes | ---------------------+--------------------------------- Changes (by mf2k): * keywords: haspatch => haspatch maintainer -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 15:40:10 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 15:40:10 -0000 Subject: [MacPorts] #53176: py36-gnureadline @6.3.3_1: python3.6 crashes with malloc: pointer being freed was not allocated In-Reply-To: <047.6d5d604bea32c01385c321b1bde3dd00@macports.org> References: <047.6d5d604bea32c01385c321b1bde3dd00@macports.org> Message-ID: <062.236733f4fc54f16ce5cf316d53e0fdc3@macports.org> #53176: py36-gnureadline @6.3.3_1: python3.6 crashes with malloc: pointer being freed was not allocated -----------------------------+---------------------- Reporter: mndavidoff | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-gnureadline | -----------------------------+---------------------- Changes (by mf2k): * cc: stromnov@… (removed) * status: new => assigned * owner: => stromnov -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 15:43:51 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 15:43:51 -0000 Subject: [MacPorts] #53177: activator @1.3.12 : new port In-Reply-To: <048.c53ca43819289286db81094705cf6daf@macports.org> References: <048.c53ca43819289286db81094705cf6daf@macports.org> Message-ID: <063.ad9e6ea1864bfad8578fc8dd5ac38c19@macports.org> #53177: activator @1.3.12 : new port --------------------------+----------------- Reporter: nhojpatrick | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: activator | --------------------------+----------------- Changes (by mf2k): * keywords: haspatch => Comment: {{{nomaintainer}}} means no maintainer. If you could maintain it, that is much preferred. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 15:46:08 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 15:46:08 -0000 Subject: [MacPorts] #53178: php55 @5.5.36: update to 5.5.38 In-Reply-To: <041.2b3adeb402165ddee783bab38bd49f92@macports.org> References: <041.2b3adeb402165ddee783bab38bd49f92@macports.org> Message-ID: <056.23ce9ec775598318153efaecdd1aed92@macports.org> #53178: php55 @5.5.36: update to 5.5.38 ---------------------+------------------------ Reporter: l2dy | Owner: ryandesign Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: php55 | ---------------------+------------------------ Changes (by mf2k): * owner: => ryandesign * status: new => assigned * cc: ryandesign (removed) * priority: High => Normal Comment: The Priority field is for use by Macports team members only. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 15:50:07 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 15:50:07 -0000 Subject: [MacPorts] #53180: Processing of port arb failed In-Reply-To: <045.02177858dbd15b1e9c09234e4adb755f@macports.org> References: <045.02177858dbd15b1e9c09234e4adb755f@macports.org> Message-ID: <060.d7bd62513afd8ae2630b5dd5cd522d7d@macports.org> #53180: Processing of port arb failed -----------------------+------------------- Reporter: walker92 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: arb Port: arb | -----------------------+------------------- Comment (by mf2k): In the future, please use WikiFormatting, fill in the Port field with the port that actually fails to build and Cc the port maintainers ({{{port info --maintainers xorg-libXt}}}), if any. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 15:50:28 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 15:50:28 -0000 Subject: [MacPorts] #53180: Processing of port arb failed In-Reply-To: <045.02177858dbd15b1e9c09234e4adb755f@macports.org> References: <045.02177858dbd15b1e9c09234e4adb755f@macports.org> Message-ID: <060.fd3190ebfe6438faec6df516726de087@macports.org> #53180: Processing of port arb failed -----------------------+------------------- Reporter: walker92 | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: arb | -----------------------+------------------- Changes (by mf2k): * keywords: arb => Old description: > Trying to install Arb using the easy method of > > This is what was in the terminal: > > Last login: Thu Dec 29 09:45:35 on ttys001 > Ryan-Walkers-iMac:~ walker92$ sudo port install arb > Password: > ---> Computing dependencies for arb > ---> Dependencies to be installed: coreutils gettext expat libiconv > ncurses gmp glew glib2 libffi pcre bzip2 libedit zlib glw autoconf > automake libpng libtool mesa xorg-dri2proto xorg-glproto xorg-libX11 > xorg-kbproto xorg-libXau xorg-xproto xorg-libXdmcp xorg-libxcb python27 > db48 openssl python2_select python_select sqlite3 xorg-libpthread-stubs > xorg-xcb-proto libxml2 xz xorg-libXdamage xorg-damageproto xorg-libXfixes > xorg-fixesproto xorg-xextproto xorg-libXext xorg-libXi xorg-inputproto > xorg-libXmu xorg-libXt xorg-libsm xorg-libice xorg-libXxf86vm xorg- > xf86vidmodeproto openmotif Xft2 fontconfig freetype xrender xorg- > renderproto bison bison-runtime m4 flex jpeg pkgconfig xbitmaps xorg- > libXp xorg-printproto gsed gtime gv Xaw3d xpm ghostscript jbig2dec lcms2 > tiff libidn libpaper perl5 perl5.24 gdbm xorg-libXinerama xorg- > xineramaproto lynx makedepend sablotron spidermonkey nspr readline xfig > transfig netpbm jasper jbigkit libnetpbm xorg-libXaw > ---> Fetching archive for expat > ---> Attempting to fetch expat-2.2.0_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/expat > ---> Attempting to fetch expat-2.2.0_0.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/expat > ---> Installing expat @2.2.0_0 > ---> Activating expat @2.2.0_0 > ---> Cleaning expat > ---> Fetching archive for libiconv > ---> Attempting to fetch libiconv-1.14_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/libiconv > ---> Attempting to fetch libiconv-1.14_0.darwin_15.x86_64.tbz2.rmd160 > from https://packages.macports.org/libiconv > ---> Installing libiconv @1.14_0 > ---> Activating libiconv @1.14_0 > ---> Cleaning libiconv > ---> Fetching archive for ncurses > ---> Attempting to fetch ncurses-6.0_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/ncurses > ---> Attempting to fetch ncurses-6.0_0.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/ncurses > ---> Installing ncurses @6.0_0 > ---> Activating ncurses @6.0_0 > ---> Cleaning ncurses > ---> Fetching archive for gettext > ---> Attempting to fetch gettext-0.19.8.1_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/gettext > ---> Attempting to fetch gettext-0.19.8.1_0.darwin_15.x86_64.tbz2.rmd160 > from https://packages.macports.org/gettext > ---> Installing gettext @0.19.8.1_0 > ---> Activating gettext @0.19.8.1_0 > ---> Cleaning gettext > ---> Fetching distfiles for gmp > ---> Verifying checksums for gmp > ---> Extracting gmp > ---> Applying patches to gmp > ---> Configuring gmp > ---> Building gmp > ---> Staging gmp into destroot > ---> Installing gmp @6.1.2_0 > ---> Activating gmp @6.1.2_0 > ---> Cleaning gmp > ---> Fetching archive for coreutils > ---> Attempting to fetch coreutils-8.26_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/coreutils > ---> Attempting to fetch coreutils-8.26_0.darwin_15.x86_64.tbz2.rmd160 > from https://packages.macports.org/coreutils > ---> Installing coreutils @8.26_0 > ---> Activating coreutils @8.26_0 > > The tools provided by GNU coreutils are prefixed with the character 'g' > by > default to distinguish them from the BSD commands. > For example, cp becomes gcp and ls becomes gls. > > If you want to use the GNU tools by default, add this directory to the > front of > your PATH environment variable: > /opt/local/libexec/gnubin/ > > ---> Cleaning coreutils > ---> Fetching archive for glew > ---> Attempting to fetch glew-2.0.0_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/glew > ---> Attempting to fetch glew-2.0.0_0.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/glew > ---> Installing glew @2.0.0_0 > ---> Activating glew @2.0.0_0 > ---> Cleaning glew > ---> Fetching archive for libffi > ---> Attempting to fetch libffi-3.2.1_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/libffi > ---> Attempting to fetch libffi-3.2.1_0.darwin_15.x86_64.tbz2.rmd160 > from https://packages.macports.org/libffi > ---> Installing libffi @3.2.1_0 > ---> Activating libffi @3.2.1_0 > ---> Cleaning libffi > ---> Fetching archive for bzip2 > ---> Attempting to fetch bzip2-1.0.6_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/bzip2 > ---> Attempting to fetch bzip2-1.0.6_0.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/bzip2 > ---> Installing bzip2 @1.0.6_0 > ---> Activating bzip2 @1.0.6_0 > ---> Cleaning bzip2 > ---> Fetching archive for libedit > ---> Attempting to fetch libedit-20160903-3.1_1.darwin_15.x86_64.tbz2 > from https://packages.macports.org/libedit > ---> Attempting to fetch > libedit-20160903-3.1_1.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/libedit > ---> Installing libedit @20160903-3.1_1 > ---> Activating libedit @20160903-3.1_1 > ---> Cleaning libedit > ---> Fetching archive for zlib > ---> Attempting to fetch zlib-1.2.8_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/zlib > ---> Attempting to fetch zlib-1.2.8_0.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/zlib > ---> Installing zlib @1.2.8_0 > ---> Activating zlib @1.2.8_0 > ---> Cleaning zlib > ---> Fetching archive for pcre > ---> Attempting to fetch pcre-8.39_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/pcre > ---> Attempting to fetch pcre-8.39_0.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/pcre > ---> Installing pcre @8.39_0 > ---> Activating pcre @8.39_0 > ---> Cleaning pcre > ---> Fetching archive for glib2 > ---> Attempting to fetch glib2-2.50.2_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/glib2 > ---> Attempting to fetch glib2-2.50.2_0.darwin_15.x86_64.tbz2.rmd160 > from https://packages.macports.org/glib2 > ---> Installing glib2 @2.50.2_0 > ---> Activating glib2 @2.50.2_0 > ---> Cleaning glib2 > ---> Fetching archive for autoconf > ---> Attempting to fetch autoconf-2.69_5.darwin_15.noarch.tbz2 from > https://packages.macports.org/autoconf > ---> Attempting to fetch autoconf-2.69_5.darwin_15.noarch.tbz2.rmd160 > from https://packages.macports.org/autoconf > ---> Installing autoconf @2.69_5 > ---> Activating autoconf @2.69_5 > ---> Cleaning autoconf > ---> Fetching archive for automake > ---> Attempting to fetch automake-1.15_1.darwin_15.noarch.tbz2 from > https://packages.macports.org/automake > ---> Attempting to fetch automake-1.15_1.darwin_15.noarch.tbz2.rmd160 > from https://packages.macports.org/automake > ---> Installing automake @1.15_1 > ---> Activating automake @1.15_1 > ---> Cleaning automake > ---> Fetching archive for libpng > ---> Attempting to fetch libpng-1.6.26_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/libpng > ---> Attempting to fetch libpng-1.6.26_0.darwin_15.x86_64.tbz2.rmd160 > from https://packages.macports.org/libpng > ---> Installing libpng @1.6.26_0 > ---> Activating libpng @1.6.26_0 > ---> Cleaning libpng > ---> Fetching archive for libtool > ---> Attempting to fetch libtool-2.4.6_2.darwin_15.x86_64.tbz2 from > https://packages.macports.org/libtool > ---> Attempting to fetch libtool-2.4.6_2.darwin_15.x86_64.tbz2.rmd160 > from https://packages.macports.org/libtool > ---> Installing libtool @2.4.6_2 > ---> Activating libtool @2.4.6_2 > ---> Cleaning libtool > ---> Fetching archive for xorg-dri2proto > ---> Attempting to fetch xorg-dri2proto-2.8_0.darwin_15.noarch.tbz2 from > https://packages.macports.org/xorg-dri2proto > ---> Attempting to fetch xorg- > dri2proto-2.8_0.darwin_15.noarch.tbz2.rmd160 from > https://packages.macports.org/xorg-dri2proto > ---> Installing xorg-dri2proto @2.8_0 > ---> Activating xorg-dri2proto @2.8_0 > ---> Cleaning xorg-dri2proto > ---> Fetching archive for xorg-glproto > ---> Attempting to fetch xorg-glproto-1.4.17_0.darwin_15.noarch.tbz2 > from https://packages.macports.org/xorg-glproto > ---> Attempting to fetch xorg- > glproto-1.4.17_0.darwin_15.noarch.tbz2.rmd160 from > https://packages.macports.org/xorg-glproto > ---> Installing xorg-glproto @1.4.17_0 > ---> Activating xorg-glproto @1.4.17_0 > ---> Cleaning xorg-glproto > ---> Fetching archive for xorg-kbproto > ---> Attempting to fetch xorg-kbproto-1.0.7_0.darwin_15.noarch.tbz2 from > https://packages.macports.org/xorg-kbproto > ---> Attempting to fetch xorg- > kbproto-1.0.7_0.darwin_15.noarch.tbz2.rmd160 from > https://packages.macports.org/xorg-kbproto > ---> Installing xorg-kbproto @1.0.7_0 > ---> Activating xorg-kbproto @1.0.7_0 > ---> Cleaning xorg-kbproto > ---> Fetching archive for xorg-xproto > ---> Attempting to fetch xorg-xproto-7.0.31_0.darwin_15.noarch.tbz2 from > https://packages.macports.org/xorg-xproto > ---> Attempting to fetch xorg- > xproto-7.0.31_0.darwin_15.noarch.tbz2.rmd160 from > https://packages.macports.org/xorg-xproto > ---> Installing xorg-xproto @7.0.31_0 > ---> Activating xorg-xproto @7.0.31_0 > ---> Cleaning xorg-xproto > ---> Fetching archive for xorg-libXau > ---> Attempting to fetch xorg-libXau-1.0.8_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/xorg-libXau > ---> Attempting to fetch xorg- > libXau-1.0.8_0.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/xorg-libXau > ---> Installing xorg-libXau @1.0.8_0 > ---> Activating xorg-libXau @1.0.8_0 > ---> Cleaning xorg-libXau > ---> Fetching archive for xorg-libXdmcp > ---> Attempting to fetch xorg-libXdmcp-1.1.2_0.darwin_15.x86_64.tbz2 > from https://packages.macports.org/xorg-libXdmcp > ---> Attempting to fetch xorg- > libXdmcp-1.1.2_0.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/xorg-libXdmcp > ---> Installing xorg-libXdmcp @1.1.2_0 > ---> Activating xorg-libXdmcp @1.1.2_0 > ---> Cleaning xorg-libXdmcp > ---> Fetching archive for db48 > ---> Attempting to fetch db48-4.8.30_4.darwin_15.x86_64.tbz2 from > https://packages.macports.org/db48 > ---> Attempting to fetch db48-4.8.30_4.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/db48 > ---> Installing db48 @4.8.30_4 > ---> Activating db48 @4.8.30_4 > ---> Cleaning db48 > ---> Fetching archive for openssl > ---> Attempting to fetch openssl-1.0.2j_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/openssl > ---> Attempting to fetch openssl-1.0.2j_0.darwin_15.x86_64.tbz2.rmd160 > from https://packages.macports.org/openssl > ---> Installing openssl @1.0.2j_0 > ---> Activating openssl @1.0.2j_0 > ---> Cleaning openssl > ---> Fetching archive for python2_select > ---> Attempting to fetch python2_select-0.0_2.darwin_15.noarch.tbz2 from > https://packages.macports.org/python2_select > ---> Attempting to fetch > python2_select-0.0_2.darwin_15.noarch.tbz2.rmd160 from > https://packages.macports.org/python2_select > ---> Installing python2_select @0.0_2 > ---> Activating python2_select @0.0_2 > ---> Cleaning python2_select > ---> Fetching archive for python_select > ---> Attempting to fetch python_select-0.3_7.darwin_15.noarch.tbz2 from > https://packages.macports.org/python_select > ---> Attempting to fetch > python_select-0.3_7.darwin_15.noarch.tbz2.rmd160 from > https://packages.macports.org/python_select > ---> Installing python_select @0.3_7 > ---> Activating python_select @0.3_7 > ---> Cleaning python_select > ---> Fetching archive for sqlite3 > ---> Attempting to fetch sqlite3-3.15.2_2.darwin_15.x86_64.tbz2 from > https://packages.macports.org/sqlite3 > ---> Attempting to fetch sqlite3-3.15.2_2.darwin_15.x86_64.tbz2.rmd160 > from https://packages.macports.org/sqlite3 > ---> Installing sqlite3 @3.15.2_2 > ---> Activating sqlite3 @3.15.2_2 > ---> Cleaning sqlite3 > ---> Fetching archive for python27 > ---> Attempting to fetch python27-2.7.13_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/python27 > ---> Attempting to fetch python27-2.7.13_0.darwin_15.x86_64.tbz2.rmd160 > from https://packages.macports.org/python27 > ---> Installing python27 @2.7.13_0 > ---> Activating python27 @2.7.13_0 > > To make this the default Python or Python 2 (i.e., the version run by the > 'python' or 'python2' commands), run one or both of: > > sudo port select --set python python27 > sudo port select --set python2 python27 > > ############################################################## > # IF YOU ARE USING PYTHON FROM THE TERMINAL, PLEASE INSTALL: > # py27-readline > # TO AVOID A LIBEDIT / PYTHON INTERACTION ISSUE. > # REF: https://trac.macports.org/ticket/48807 > ############################################################## > > ---> Cleaning python27 > ---> Fetching archive for xorg-libpthread-stubs > ---> Attempting to fetch xorg-libpthread- > stubs-0.3_0.darwin_15.noarch.tbz2 from https://packages.macports.org > /xorg-libpthread-stubs > ---> Attempting to fetch xorg-libpthread- > stubs-0.3_0.darwin_15.noarch.tbz2.rmd160 from > https://packages.macports.org/xorg-libpthread-stubs > ---> Installing xorg-libpthread-stubs @0.3_0 > ---> Activating xorg-libpthread-stubs @0.3_0 > ---> Cleaning xorg-libpthread-stubs > ---> Fetching archive for xz > ---> Attempting to fetch xz-5.2.2_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/xz > ---> Attempting to fetch xz-5.2.2_0.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/xz > ---> Installing xz @5.2.2_0 > ---> Activating xz @5.2.2_0 > ---> Cleaning xz > ---> Fetching archive for libxml2 > ---> Attempting to fetch libxml2-2.9.4_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/libxml2 > ---> Attempting to fetch libxml2-2.9.4_0.darwin_15.x86_64.tbz2.rmd160 > from https://packages.macports.org/libxml2 > ---> Installing libxml2 @2.9.4_0 > ---> Activating libxml2 @2.9.4_0 > ---> Cleaning libxml2 > ---> Fetching archive for xorg-xcb-proto > ---> Attempting to fetch xorg-xcb- > proto-1.12_1+python27.darwin_15.noarch.tbz2 from > https://packages.macports.org/xorg-xcb-proto > ---> Attempting to fetch xorg-xcb- > proto-1.12_1+python27.darwin_15.noarch.tbz2.rmd160 from > https://packages.macports.org/xorg-xcb-proto > ---> Installing xorg-xcb-proto @1.12_1+python27 > ---> Activating xorg-xcb-proto @1.12_1+python27 > ---> Cleaning xorg-xcb-proto > ---> Fetching archive for xorg-libxcb > ---> Attempting to fetch xorg- > libxcb-1.12_2+python27.darwin_15.x86_64.tbz2 from > https://packages.macports.org/xorg-libxcb > ---> Attempting to fetch xorg- > libxcb-1.12_2+python27.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/xorg-libxcb > ---> Installing xorg-libxcb @1.12_2+python27 > ---> Activating xorg-libxcb @1.12_2+python27 > ---> Cleaning xorg-libxcb > ---> Fetching archive for xorg-libX11 > ---> Attempting to fetch xorg-libX11-1.6.4_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/xorg-libX11 > ---> Attempting to fetch xorg- > libX11-1.6.4_0.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/xorg-libX11 > ---> Installing xorg-libX11 @1.6.4_0 > ---> Activating xorg-libX11 @1.6.4_0 > ---> Cleaning xorg-libX11 > ---> Fetching archive for xorg-damageproto > ---> Attempting to fetch xorg-damageproto-1.2.1_0.darwin_15.noarch.tbz2 > from https://packages.macports.org/xorg-damageproto > ---> Attempting to fetch xorg- > damageproto-1.2.1_0.darwin_15.noarch.tbz2.rmd160 from > https://packages.macports.org/xorg-damageproto > ---> Installing xorg-damageproto @1.2.1_0 > ---> Activating xorg-damageproto @1.2.1_0 > ---> Cleaning xorg-damageproto > ---> Fetching archive for xorg-xextproto > ---> Attempting to fetch xorg-xextproto-7.3.0_0.darwin_15.noarch.tbz2 > from https://packages.macports.org/xorg-xextproto > ---> Attempting to fetch xorg- > xextproto-7.3.0_0.darwin_15.noarch.tbz2.rmd160 from > https://packages.macports.org/xorg-xextproto > ---> Installing xorg-xextproto @7.3.0_0 > ---> Activating xorg-xextproto @7.3.0_0 > ---> Cleaning xorg-xextproto > ---> Fetching archive for xorg-fixesproto > ---> Attempting to fetch xorg-fixesproto-5.0_0.darwin_15.noarch.tbz2 > from https://packages.macports.org/xorg-fixesproto > ---> Attempting to fetch xorg- > fixesproto-5.0_0.darwin_15.noarch.tbz2.rmd160 from > https://packages.macports.org/xorg-fixesproto > ---> Installing xorg-fixesproto @5.0_0 > ---> Activating xorg-fixesproto @5.0_0 > ---> Cleaning xorg-fixesproto > ---> Fetching archive for xorg-libXfixes > ---> Attempting to fetch xorg-libXfixes-5.0.3_0.darwin_15.x86_64.tbz2 > from https://packages.macports.org/xorg-libXfixes > ---> Attempting to fetch xorg- > libXfixes-5.0.3_0.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/xorg-libXfixes > ---> Installing xorg-libXfixes @5.0.3_0 > ---> Activating xorg-libXfixes @5.0.3_0 > ---> Cleaning xorg-libXfixes > ---> Fetching archive for xorg-libXdamage > ---> Attempting to fetch xorg-libXdamage-1.1.4_0.darwin_15.x86_64.tbz2 > from https://packages.macports.org/xorg-libXdamage > ---> Attempting to fetch xorg- > libXdamage-1.1.4_0.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/xorg-libXdamage > ---> Installing xorg-libXdamage @1.1.4_0 > ---> Activating xorg-libXdamage @1.1.4_0 > ---> Cleaning xorg-libXdamage > ---> Fetching archive for xorg-libXext > ---> Attempting to fetch xorg-libXext-1.3.3_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/xorg-libXext > ---> Attempting to fetch xorg- > libXext-1.3.3_0.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/xorg-libXext > ---> Installing xorg-libXext @1.3.3_0 > ---> Activating xorg-libXext @1.3.3_0 > ---> Cleaning xorg-libXext > ---> Fetching archive for xorg-inputproto > ---> Attempting to fetch xorg-inputproto-2.3.2_0.darwin_15.noarch.tbz2 > from https://packages.macports.org/xorg-inputproto > ---> Attempting to fetch xorg- > inputproto-2.3.2_0.darwin_15.noarch.tbz2.rmd160 from > https://packages.macports.org/xorg-inputproto > ---> Installing xorg-inputproto @2.3.2_0 > ---> Activating xorg-inputproto @2.3.2_0 > ---> Cleaning xorg-inputproto > ---> Fetching archive for xorg-libXi > ---> Attempting to fetch xorg-libXi-1.7.8_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/xorg-libXi > ---> Attempting to fetch xorg-libXi-1.7.8_0.darwin_15.x86_64.tbz2.rmd160 > from https://packages.macports.org/xorg-libXi > ---> Installing xorg-libXi @1.7.8_0 > ---> Activating xorg-libXi @1.7.8_0 > ---> Cleaning xorg-libXi > ---> Fetching archive for xorg-libice > ---> Attempting to fetch xorg-libice-1.0.9_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/xorg-libice > ---> Attempting to fetch xorg- > libice-1.0.9_0.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/xorg-libice > ---> Installing xorg-libice @1.0.9_0 > ---> Activating xorg-libice @1.0.9_0 > ---> Cleaning xorg-libice > ---> Fetching archive for xorg-libsm > ---> Attempting to fetch xorg-libsm-1.2.1_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/xorg-libsm > ---> Attempting to fetch xorg-libsm-1.2.1_0.darwin_15.x86_64.tbz2.rmd160 > from https://packages.macports.org/xorg-libsm > ---> Installing xorg-libsm @1.2.1_0 > ---> Activating xorg-libsm @1.2.1_0 > ---> Cleaning xorg-libsm > ---> Fetching archive for xorg-libXt > ---> Attempting to fetch xorg-libXt-1.1.5_1.darwin_15.x86_64.tbz2 from > https://packages.macports.org/xorg-libXt > ---> Attempting to fetch xorg-libXt-1.1.5_1.darwin_15.x86_64.tbz2.rmd160 > from https://packages.macports.org/xorg-libXt > ---> Installing xorg-libXt @1.1.5_1 > ---> Activating xorg-libXt @1.1.5_1 > ---> Cleaning xorg-libXt > ---> Fetching archive for xorg-libXmu > ---> Attempting to fetch xorg-libXmu-1.1.2_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/xorg-libXmu > ---> Attempting to fetch xorg- > libXmu-1.1.2_0.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/xorg-libXmu > ---> Installing xorg-libXmu @1.1.2_0 > ---> Activating xorg-libXmu @1.1.2_0 > ---> Cleaning xorg-libXmu > ---> Fetching archive for xorg-xf86vidmodeproto > ---> Attempting to fetch xorg- > xf86vidmodeproto-2.3.1_0.darwin_15.noarch.tbz2 from > https://packages.macports.org/xorg-xf86vidmodeproto > ---> Attempting to fetch xorg- > xf86vidmodeproto-2.3.1_0.darwin_15.noarch.tbz2.rmd160 from > https://packages.macports.org/xorg-xf86vidmodeproto > ---> Installing xorg-xf86vidmodeproto @2.3.1_0 > ---> Activating xorg-xf86vidmodeproto @2.3.1_0 > ---> Cleaning xorg-xf86vidmodeproto > ---> Fetching archive for xorg-libXxf86vm > ---> Attempting to fetch xorg-libXxf86vm-1.1.4_0.darwin_15.x86_64.tbz2 > from https://packages.macports.org/xorg-libXxf86vm > ---> Attempting to fetch xorg- > libXxf86vm-1.1.4_0.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/xorg-libXxf86vm > ---> Installing xorg-libXxf86vm @1.1.4_0 > ---> Activating xorg-libXxf86vm @1.1.4_0 > ---> Cleaning xorg-libXxf86vm > ---> Fetching archive for mesa > ---> Attempting to fetch > mesa-12.0.1_2+osmesa+python27.darwin_15.x86_64.tbz2 from > https://packages.macports.org/mesa > ---> Attempting to fetch > mesa-12.0.1_2+osmesa+python27.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/mesa > ---> Installing mesa @12.0.1_2+osmesa+python27 > ---> Activating mesa @12.0.1_2+osmesa+python27 > ---> Cleaning mesa > ---> Fetching archive for freetype > ---> Attempting to fetch freetype-2.7_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/freetype > ---> Attempting to fetch freetype-2.7_0.darwin_15.x86_64.tbz2.rmd160 > from https://packages.macports.org/freetype > ---> Installing freetype @2.7_0 > ---> Activating freetype @2.7_0 > ---> Cleaning freetype > ---> Fetching archive for fontconfig > ---> Attempting to fetch fontconfig-2.12.1_1.darwin_15.x86_64.tbz2 from > https://packages.macports.org/fontconfig > ---> Attempting to fetch > fontconfig-2.12.1_1.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/fontconfig > ---> Installing fontconfig @2.12.1_1 > ---> Activating fontconfig @2.12.1_1 > ---> Cleaning fontconfig > ---> Fetching archive for xorg-renderproto > ---> Attempting to fetch xorg-renderproto-0.11.1_0.darwin_15.noarch.tbz2 > from https://packages.macports.org/xorg-renderproto > ---> Attempting to fetch xorg- > renderproto-0.11.1_0.darwin_15.noarch.tbz2.rmd160 from > https://packages.macports.org/xorg-renderproto > ---> Installing xorg-renderproto @0.11.1_0 > ---> Activating xorg-renderproto @0.11.1_0 > ---> Cleaning xorg-renderproto > ---> Fetching archive for xrender > ---> Attempting to fetch xrender-0.9.10_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/xrender > ---> Attempting to fetch xrender-0.9.10_0.darwin_15.x86_64.tbz2.rmd160 > from https://packages.macports.org/xrender > ---> Installing xrender @0.9.10_0 > ---> Activating xrender @0.9.10_0 > ---> Cleaning xrender > ---> Fetching archive for Xft2 > ---> Attempting to fetch Xft2-2.3.2_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/Xft2 > ---> Attempting to fetch Xft2-2.3.2_0.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/Xft2 > ---> Installing Xft2 @2.3.2_0 > ---> Activating Xft2 @2.3.2_0 > ---> Cleaning Xft2 > ---> Fetching archive for bison-runtime > ---> Attempting to fetch bison-runtime-3.0.4_0.darwin_15.noarch.tbz2 > from https://packages.macports.org/bison-runtime > ---> Attempting to fetch bison- > runtime-3.0.4_0.darwin_15.noarch.tbz2.rmd160 from > https://packages.macports.org/bison-runtime > ---> Installing bison-runtime @3.0.4_0 > ---> Activating bison-runtime @3.0.4_0 > ---> Cleaning bison-runtime > ---> Fetching archive for m4 > ---> Attempting to fetch m4-1.4.17_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/m4 > [ ] 95.1 % speed: 3.6 > KiB/s ---> Attempting to fetch m4-1.4.17_0.darwin_15.x86_64.tbz2 from > http://sea.us.packages.macports.org/macports/packages/m4 > ---> Attempting to fetch m4-1.4.17_0.darwin_15.x86_64.tbz2.rmd160 from > http://sea.us.packages.macports.org/macports/packages/m4 > ---> Installing m4 @1.4.17_0 > ---> Activating m4 @1.4.17_0 > ---> Cleaning m4 > ---> Fetching archive for bison > ---> Attempting to fetch bison-3.0.4_1.darwin_15.x86_64.tbz2 from > https://packages.macports.org/bison > ---> Attempting to fetch bison-3.0.4_1.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/bison > ---> Installing bison @3.0.4_1 > ---> Activating bison @3.0.4_1 > ---> Cleaning bison > ---> Fetching archive for flex > ---> Attempting to fetch flex-2.6.0_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/flex > ---> Attempting to fetch flex-2.6.0_0.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/flex > ---> Installing flex @2.6.0_0 > ---> Activating flex @2.6.0_0 > ---> Cleaning flex > ---> Fetching archive for jpeg > ---> Attempting to fetch jpeg-9b_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/jpeg > ---> Attempting to fetch jpeg-9b_0.darwin_15.x86_64.tbz2.rmd160 from > https://packages.macports.org/jpeg > ---> Installing jpeg @9b_0 > ---> Activating jpeg @9b_0 > ---> Cleaning jpeg > ---> Fetching archive for pkgconfig > ---> Attempting to fetch pkgconfig-0.29.1_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/pkgconfig > ---> Attempting to fetch pkgconfig-0.29.1_0.darwin_15.x86_64.tbz2.rmd160 > from https://packages.macports.org/pkgconfig > ---> Installing pkgconfig @0.29.1_0 > ---> Activating pkgconfig @0.29.1_0 > ---> Cleaning pkgconfig > ---> Fetching archive for xbitmaps > ---> Attempting to fetch xbitmaps-1.1.1_0.darwin_15.noarch.tbz2 from > https://packages.macports.org/xbitmaps > ---> Attempting to fetch xbitmaps-1.1.1_0.darwin_15.noarch.tbz2.rmd160 > from https://packages.macports.org/xbitmaps > ---> Installing xbitmaps @1.1.1_0 > ---> Activating xbitmaps @1.1.1_0 > ---> Cleaning xbitmaps > ---> Fetching archive for xorg-printproto > ---> Attempting to fetch xorg-printproto-1.0.5_0.darwin_15.noarch.tbz2 > from https://packages.macports.org/xorg-printproto > ---> Attempting to fetch xorg- > printproto-1.0.5_0.darwin_15.noarch.tbz2.rmd160 from > https://packages.macports.org/xorg-printproto > ---> Installing xorg-printproto @1.0.5_0 > ---> Activating xorg-printproto @1.0.5_0 > ---> Cleaning xorg-printproto > ---> Fetching archive for xorg-libXp > ---> Attempting to fetch xorg-libXp-1.0.3_0.darwin_15.x86_64.tbz2 from > https://packages.macports.org/xorg-libXp > ---> Attempting to fetch xorg-libXp-1.0.3_0.darwin_15.x86_64.tbz2.rmd160 > from https://packages.macports.org/xorg-libXp > ---> Installing xorg-libXp @1.0.3_0 > ---> Activating xorg-libXp @1.0.3_0 > ---> Cleaning xorg-libXp > ---> Fetching archive for openmotif > Error: org.macports.archivefetch for port openmotif returned: xorg-libXt > must be installed with +flat_namespace. > Error: Failed to install openmotif > Please see the log file for port openmotif for details: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_openmotif/openmotif/main.log > Error: The following dependencies were not installed: glw openmotif gsed > gtime gv Xaw3d xpm ghostscript jbig2dec lcms2 tiff libidn libpaper perl5 > perl5.24 gdbm xorg-libXinerama xorg-xineramaproto lynx makedepend > sablotron spidermonkey nspr readline xfig transfig netpbm jasper jbigkit > libnetpbm xorg-libXaw > To report a bug, follow the instructions in the guide: > http://guide.macports.org/#project.tickets > Error: Processing of port arb failed > Ryan-Walkers-iMac:~ walker92$ New description: Trying to install Arb using the easy method of This is what was in the terminal: {{{ Last login: Thu Dec 29 09:45:35 on ttys001 Ryan-Walkers-iMac:~ walker92$ sudo port install arb Password: ---> Computing dependencies for arb ---> Dependencies to be installed: coreutils gettext expat libiconv ncurses gmp glew glib2 libffi pcre bzip2 libedit zlib glw autoconf automake libpng libtool mesa xorg-dri2proto xorg-glproto xorg-libX11 xorg- kbproto xorg-libXau xorg-xproto xorg-libXdmcp xorg-libxcb python27 db48 openssl python2_select python_select sqlite3 xorg-libpthread-stubs xorg- xcb-proto libxml2 xz xorg-libXdamage xorg-damageproto xorg-libXfixes xorg- fixesproto xorg-xextproto xorg-libXext xorg-libXi xorg-inputproto xorg- libXmu xorg-libXt xorg-libsm xorg-libice xorg-libXxf86vm xorg- xf86vidmodeproto openmotif Xft2 fontconfig freetype xrender xorg- renderproto bison bison-runtime m4 flex jpeg pkgconfig xbitmaps xorg-libXp xorg-printproto gsed gtime gv Xaw3d xpm ghostscript jbig2dec lcms2 tiff libidn libpaper perl5 perl5.24 gdbm xorg-libXinerama xorg-xineramaproto lynx makedepend sablotron spidermonkey nspr readline xfig transfig netpbm jasper jbigkit libnetpbm xorg-libXaw ---> Fetching archive for expat ---> Attempting to fetch expat-2.2.0_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/expat ---> Attempting to fetch expat-2.2.0_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/expat ---> Installing expat @2.2.0_0 ---> Activating expat @2.2.0_0 ---> Cleaning expat ---> Fetching archive for libiconv ---> Attempting to fetch libiconv-1.14_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/libiconv ---> Attempting to fetch libiconv-1.14_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/libiconv ---> Installing libiconv @1.14_0 ---> Activating libiconv @1.14_0 ---> Cleaning libiconv ---> Fetching archive for ncurses ---> Attempting to fetch ncurses-6.0_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/ncurses ---> Attempting to fetch ncurses-6.0_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/ncurses ---> Installing ncurses @6.0_0 ---> Activating ncurses @6.0_0 ---> Cleaning ncurses ---> Fetching archive for gettext ---> Attempting to fetch gettext-0.19.8.1_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/gettext ---> Attempting to fetch gettext-0.19.8.1_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/gettext ---> Installing gettext @0.19.8.1_0 ---> Activating gettext @0.19.8.1_0 ---> Cleaning gettext ---> Fetching distfiles for gmp ---> Verifying checksums for gmp ---> Extracting gmp ---> Applying patches to gmp ---> Configuring gmp ---> Building gmp ---> Staging gmp into destroot ---> Installing gmp @6.1.2_0 ---> Activating gmp @6.1.2_0 ---> Cleaning gmp ---> Fetching archive for coreutils ---> Attempting to fetch coreutils-8.26_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/coreutils ---> Attempting to fetch coreutils-8.26_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/coreutils ---> Installing coreutils @8.26_0 ---> Activating coreutils @8.26_0 The tools provided by GNU coreutils are prefixed with the character 'g' by default to distinguish them from the BSD commands. For example, cp becomes gcp and ls becomes gls. If you want to use the GNU tools by default, add this directory to the front of your PATH environment variable: /opt/local/libexec/gnubin/ ---> Cleaning coreutils ---> Fetching archive for glew ---> Attempting to fetch glew-2.0.0_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/glew ---> Attempting to fetch glew-2.0.0_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/glew ---> Installing glew @2.0.0_0 ---> Activating glew @2.0.0_0 ---> Cleaning glew ---> Fetching archive for libffi ---> Attempting to fetch libffi-3.2.1_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/libffi ---> Attempting to fetch libffi-3.2.1_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/libffi ---> Installing libffi @3.2.1_0 ---> Activating libffi @3.2.1_0 ---> Cleaning libffi ---> Fetching archive for bzip2 ---> Attempting to fetch bzip2-1.0.6_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/bzip2 ---> Attempting to fetch bzip2-1.0.6_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/bzip2 ---> Installing bzip2 @1.0.6_0 ---> Activating bzip2 @1.0.6_0 ---> Cleaning bzip2 ---> Fetching archive for libedit ---> Attempting to fetch libedit-20160903-3.1_1.darwin_15.x86_64.tbz2 from https://packages.macports.org/libedit ---> Attempting to fetch libedit-20160903-3.1_1.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/libedit ---> Installing libedit @20160903-3.1_1 ---> Activating libedit @20160903-3.1_1 ---> Cleaning libedit ---> Fetching archive for zlib ---> Attempting to fetch zlib-1.2.8_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/zlib ---> Attempting to fetch zlib-1.2.8_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/zlib ---> Installing zlib @1.2.8_0 ---> Activating zlib @1.2.8_0 ---> Cleaning zlib ---> Fetching archive for pcre ---> Attempting to fetch pcre-8.39_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/pcre ---> Attempting to fetch pcre-8.39_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/pcre ---> Installing pcre @8.39_0 ---> Activating pcre @8.39_0 ---> Cleaning pcre ---> Fetching archive for glib2 ---> Attempting to fetch glib2-2.50.2_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/glib2 ---> Attempting to fetch glib2-2.50.2_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/glib2 ---> Installing glib2 @2.50.2_0 ---> Activating glib2 @2.50.2_0 ---> Cleaning glib2 ---> Fetching archive for autoconf ---> Attempting to fetch autoconf-2.69_5.darwin_15.noarch.tbz2 from https://packages.macports.org/autoconf ---> Attempting to fetch autoconf-2.69_5.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/autoconf ---> Installing autoconf @2.69_5 ---> Activating autoconf @2.69_5 ---> Cleaning autoconf ---> Fetching archive for automake ---> Attempting to fetch automake-1.15_1.darwin_15.noarch.tbz2 from https://packages.macports.org/automake ---> Attempting to fetch automake-1.15_1.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/automake ---> Installing automake @1.15_1 ---> Activating automake @1.15_1 ---> Cleaning automake ---> Fetching archive for libpng ---> Attempting to fetch libpng-1.6.26_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/libpng ---> Attempting to fetch libpng-1.6.26_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/libpng ---> Installing libpng @1.6.26_0 ---> Activating libpng @1.6.26_0 ---> Cleaning libpng ---> Fetching archive for libtool ---> Attempting to fetch libtool-2.4.6_2.darwin_15.x86_64.tbz2 from https://packages.macports.org/libtool ---> Attempting to fetch libtool-2.4.6_2.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/libtool ---> Installing libtool @2.4.6_2 ---> Activating libtool @2.4.6_2 ---> Cleaning libtool ---> Fetching archive for xorg-dri2proto ---> Attempting to fetch xorg-dri2proto-2.8_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-dri2proto ---> Attempting to fetch xorg- dri2proto-2.8_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-dri2proto ---> Installing xorg-dri2proto @2.8_0 ---> Activating xorg-dri2proto @2.8_0 ---> Cleaning xorg-dri2proto ---> Fetching archive for xorg-glproto ---> Attempting to fetch xorg-glproto-1.4.17_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-glproto ---> Attempting to fetch xorg- glproto-1.4.17_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-glproto ---> Installing xorg-glproto @1.4.17_0 ---> Activating xorg-glproto @1.4.17_0 ---> Cleaning xorg-glproto ---> Fetching archive for xorg-kbproto ---> Attempting to fetch xorg-kbproto-1.0.7_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-kbproto ---> Attempting to fetch xorg- kbproto-1.0.7_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-kbproto ---> Installing xorg-kbproto @1.0.7_0 ---> Activating xorg-kbproto @1.0.7_0 ---> Cleaning xorg-kbproto ---> Fetching archive for xorg-xproto ---> Attempting to fetch xorg-xproto-7.0.31_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-xproto ---> Attempting to fetch xorg- xproto-7.0.31_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-xproto ---> Installing xorg-xproto @7.0.31_0 ---> Activating xorg-xproto @7.0.31_0 ---> Cleaning xorg-xproto ---> Fetching archive for xorg-libXau ---> Attempting to fetch xorg-libXau-1.0.8_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libXau ---> Attempting to fetch xorg-libXau-1.0.8_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libXau ---> Installing xorg-libXau @1.0.8_0 ---> Activating xorg-libXau @1.0.8_0 ---> Cleaning xorg-libXau ---> Fetching archive for xorg-libXdmcp ---> Attempting to fetch xorg-libXdmcp-1.1.2_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libXdmcp ---> Attempting to fetch xorg- libXdmcp-1.1.2_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libXdmcp ---> Installing xorg-libXdmcp @1.1.2_0 ---> Activating xorg-libXdmcp @1.1.2_0 ---> Cleaning xorg-libXdmcp ---> Fetching archive for db48 ---> Attempting to fetch db48-4.8.30_4.darwin_15.x86_64.tbz2 from https://packages.macports.org/db48 ---> Attempting to fetch db48-4.8.30_4.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/db48 ---> Installing db48 @4.8.30_4 ---> Activating db48 @4.8.30_4 ---> Cleaning db48 ---> Fetching archive for openssl ---> Attempting to fetch openssl-1.0.2j_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/openssl ---> Attempting to fetch openssl-1.0.2j_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/openssl ---> Installing openssl @1.0.2j_0 ---> Activating openssl @1.0.2j_0 ---> Cleaning openssl ---> Fetching archive for python2_select ---> Attempting to fetch python2_select-0.0_2.darwin_15.noarch.tbz2 from https://packages.macports.org/python2_select ---> Attempting to fetch python2_select-0.0_2.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/python2_select ---> Installing python2_select @0.0_2 ---> Activating python2_select @0.0_2 ---> Cleaning python2_select ---> Fetching archive for python_select ---> Attempting to fetch python_select-0.3_7.darwin_15.noarch.tbz2 from https://packages.macports.org/python_select ---> Attempting to fetch python_select-0.3_7.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/python_select ---> Installing python_select @0.3_7 ---> Activating python_select @0.3_7 ---> Cleaning python_select ---> Fetching archive for sqlite3 ---> Attempting to fetch sqlite3-3.15.2_2.darwin_15.x86_64.tbz2 from https://packages.macports.org/sqlite3 ---> Attempting to fetch sqlite3-3.15.2_2.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/sqlite3 ---> Installing sqlite3 @3.15.2_2 ---> Activating sqlite3 @3.15.2_2 ---> Cleaning sqlite3 ---> Fetching archive for python27 ---> Attempting to fetch python27-2.7.13_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/python27 ---> Attempting to fetch python27-2.7.13_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/python27 ---> Installing python27 @2.7.13_0 ---> Activating python27 @2.7.13_0 To make this the default Python or Python 2 (i.e., the version run by the 'python' or 'python2' commands), run one or both of: sudo port select --set python python27 sudo port select --set python2 python27 ############################################################## # IF YOU ARE USING PYTHON FROM THE TERMINAL, PLEASE INSTALL: # py27-readline # TO AVOID A LIBEDIT / PYTHON INTERACTION ISSUE. # REF: https://trac.macports.org/ticket/48807 ############################################################## ---> Cleaning python27 ---> Fetching archive for xorg-libpthread-stubs ---> Attempting to fetch xorg-libpthread- stubs-0.3_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg- libpthread-stubs ---> Attempting to fetch xorg-libpthread- stubs-0.3_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-libpthread-stubs ---> Installing xorg-libpthread-stubs @0.3_0 ---> Activating xorg-libpthread-stubs @0.3_0 ---> Cleaning xorg-libpthread-stubs ---> Fetching archive for xz ---> Attempting to fetch xz-5.2.2_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xz ---> Attempting to fetch xz-5.2.2_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xz ---> Installing xz @5.2.2_0 ---> Activating xz @5.2.2_0 ---> Cleaning xz ---> Fetching archive for libxml2 ---> Attempting to fetch libxml2-2.9.4_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/libxml2 ---> Attempting to fetch libxml2-2.9.4_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/libxml2 ---> Installing libxml2 @2.9.4_0 ---> Activating libxml2 @2.9.4_0 ---> Cleaning libxml2 ---> Fetching archive for xorg-xcb-proto ---> Attempting to fetch xorg-xcb- proto-1.12_1+python27.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-xcb-proto ---> Attempting to fetch xorg-xcb- proto-1.12_1+python27.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-xcb-proto ---> Installing xorg-xcb-proto @1.12_1+python27 ---> Activating xorg-xcb-proto @1.12_1+python27 ---> Cleaning xorg-xcb-proto ---> Fetching archive for xorg-libxcb ---> Attempting to fetch xorg- libxcb-1.12_2+python27.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libxcb ---> Attempting to fetch xorg- libxcb-1.12_2+python27.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libxcb ---> Installing xorg-libxcb @1.12_2+python27 ---> Activating xorg-libxcb @1.12_2+python27 ---> Cleaning xorg-libxcb ---> Fetching archive for xorg-libX11 ---> Attempting to fetch xorg-libX11-1.6.4_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libX11 ---> Attempting to fetch xorg-libX11-1.6.4_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libX11 ---> Installing xorg-libX11 @1.6.4_0 ---> Activating xorg-libX11 @1.6.4_0 ---> Cleaning xorg-libX11 ---> Fetching archive for xorg-damageproto ---> Attempting to fetch xorg-damageproto-1.2.1_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-damageproto ---> Attempting to fetch xorg- damageproto-1.2.1_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-damageproto ---> Installing xorg-damageproto @1.2.1_0 ---> Activating xorg-damageproto @1.2.1_0 ---> Cleaning xorg-damageproto ---> Fetching archive for xorg-xextproto ---> Attempting to fetch xorg-xextproto-7.3.0_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-xextproto ---> Attempting to fetch xorg- xextproto-7.3.0_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-xextproto ---> Installing xorg-xextproto @7.3.0_0 ---> Activating xorg-xextproto @7.3.0_0 ---> Cleaning xorg-xextproto ---> Fetching archive for xorg-fixesproto ---> Attempting to fetch xorg-fixesproto-5.0_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-fixesproto ---> Attempting to fetch xorg- fixesproto-5.0_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-fixesproto ---> Installing xorg-fixesproto @5.0_0 ---> Activating xorg-fixesproto @5.0_0 ---> Cleaning xorg-fixesproto ---> Fetching archive for xorg-libXfixes ---> Attempting to fetch xorg-libXfixes-5.0.3_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libXfixes ---> Attempting to fetch xorg- libXfixes-5.0.3_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libXfixes ---> Installing xorg-libXfixes @5.0.3_0 ---> Activating xorg-libXfixes @5.0.3_0 ---> Cleaning xorg-libXfixes ---> Fetching archive for xorg-libXdamage ---> Attempting to fetch xorg-libXdamage-1.1.4_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libXdamage ---> Attempting to fetch xorg- libXdamage-1.1.4_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libXdamage ---> Installing xorg-libXdamage @1.1.4_0 ---> Activating xorg-libXdamage @1.1.4_0 ---> Cleaning xorg-libXdamage ---> Fetching archive for xorg-libXext ---> Attempting to fetch xorg-libXext-1.3.3_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libXext ---> Attempting to fetch xorg- libXext-1.3.3_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libXext ---> Installing xorg-libXext @1.3.3_0 ---> Activating xorg-libXext @1.3.3_0 ---> Cleaning xorg-libXext ---> Fetching archive for xorg-inputproto ---> Attempting to fetch xorg-inputproto-2.3.2_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-inputproto ---> Attempting to fetch xorg- inputproto-2.3.2_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-inputproto ---> Installing xorg-inputproto @2.3.2_0 ---> Activating xorg-inputproto @2.3.2_0 ---> Cleaning xorg-inputproto ---> Fetching archive for xorg-libXi ---> Attempting to fetch xorg-libXi-1.7.8_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libXi ---> Attempting to fetch xorg-libXi-1.7.8_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libXi ---> Installing xorg-libXi @1.7.8_0 ---> Activating xorg-libXi @1.7.8_0 ---> Cleaning xorg-libXi ---> Fetching archive for xorg-libice ---> Attempting to fetch xorg-libice-1.0.9_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libice ---> Attempting to fetch xorg-libice-1.0.9_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libice ---> Installing xorg-libice @1.0.9_0 ---> Activating xorg-libice @1.0.9_0 ---> Cleaning xorg-libice ---> Fetching archive for xorg-libsm ---> Attempting to fetch xorg-libsm-1.2.1_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libsm ---> Attempting to fetch xorg-libsm-1.2.1_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libsm ---> Installing xorg-libsm @1.2.1_0 ---> Activating xorg-libsm @1.2.1_0 ---> Cleaning xorg-libsm ---> Fetching archive for xorg-libXt ---> Attempting to fetch xorg-libXt-1.1.5_1.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libXt ---> Attempting to fetch xorg-libXt-1.1.5_1.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libXt ---> Installing xorg-libXt @1.1.5_1 ---> Activating xorg-libXt @1.1.5_1 ---> Cleaning xorg-libXt ---> Fetching archive for xorg-libXmu ---> Attempting to fetch xorg-libXmu-1.1.2_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libXmu ---> Attempting to fetch xorg-libXmu-1.1.2_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libXmu ---> Installing xorg-libXmu @1.1.2_0 ---> Activating xorg-libXmu @1.1.2_0 ---> Cleaning xorg-libXmu ---> Fetching archive for xorg-xf86vidmodeproto ---> Attempting to fetch xorg- xf86vidmodeproto-2.3.1_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-xf86vidmodeproto ---> Attempting to fetch xorg- xf86vidmodeproto-2.3.1_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-xf86vidmodeproto ---> Installing xorg-xf86vidmodeproto @2.3.1_0 ---> Activating xorg-xf86vidmodeproto @2.3.1_0 ---> Cleaning xorg-xf86vidmodeproto ---> Fetching archive for xorg-libXxf86vm ---> Attempting to fetch xorg-libXxf86vm-1.1.4_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libXxf86vm ---> Attempting to fetch xorg- libXxf86vm-1.1.4_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libXxf86vm ---> Installing xorg-libXxf86vm @1.1.4_0 ---> Activating xorg-libXxf86vm @1.1.4_0 ---> Cleaning xorg-libXxf86vm ---> Fetching archive for mesa ---> Attempting to fetch mesa-12.0.1_2+osmesa+python27.darwin_15.x86_64.tbz2 from https://packages.macports.org/mesa ---> Attempting to fetch mesa-12.0.1_2+osmesa+python27.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/mesa ---> Installing mesa @12.0.1_2+osmesa+python27 ---> Activating mesa @12.0.1_2+osmesa+python27 ---> Cleaning mesa ---> Fetching archive for freetype ---> Attempting to fetch freetype-2.7_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/freetype ---> Attempting to fetch freetype-2.7_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/freetype ---> Installing freetype @2.7_0 ---> Activating freetype @2.7_0 ---> Cleaning freetype ---> Fetching archive for fontconfig ---> Attempting to fetch fontconfig-2.12.1_1.darwin_15.x86_64.tbz2 from https://packages.macports.org/fontconfig ---> Attempting to fetch fontconfig-2.12.1_1.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/fontconfig ---> Installing fontconfig @2.12.1_1 ---> Activating fontconfig @2.12.1_1 ---> Cleaning fontconfig ---> Fetching archive for xorg-renderproto ---> Attempting to fetch xorg-renderproto-0.11.1_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-renderproto ---> Attempting to fetch xorg- renderproto-0.11.1_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-renderproto ---> Installing xorg-renderproto @0.11.1_0 ---> Activating xorg-renderproto @0.11.1_0 ---> Cleaning xorg-renderproto ---> Fetching archive for xrender ---> Attempting to fetch xrender-0.9.10_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xrender ---> Attempting to fetch xrender-0.9.10_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xrender ---> Installing xrender @0.9.10_0 ---> Activating xrender @0.9.10_0 ---> Cleaning xrender ---> Fetching archive for Xft2 ---> Attempting to fetch Xft2-2.3.2_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/Xft2 ---> Attempting to fetch Xft2-2.3.2_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/Xft2 ---> Installing Xft2 @2.3.2_0 ---> Activating Xft2 @2.3.2_0 ---> Cleaning Xft2 ---> Fetching archive for bison-runtime ---> Attempting to fetch bison-runtime-3.0.4_0.darwin_15.noarch.tbz2 from https://packages.macports.org/bison-runtime ---> Attempting to fetch bison- runtime-3.0.4_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/bison-runtime ---> Installing bison-runtime @3.0.4_0 ---> Activating bison-runtime @3.0.4_0 ---> Cleaning bison-runtime ---> Fetching archive for m4 ---> Attempting to fetch m4-1.4.17_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/m4 [ ] 95.1 % speed: 3.6 KiB/s ---> Attempting to fetch m4-1.4.17_0.darwin_15.x86_64.tbz2 from http://sea.us.packages.macports.org/macports/packages/m4 ---> Attempting to fetch m4-1.4.17_0.darwin_15.x86_64.tbz2.rmd160 from http://sea.us.packages.macports.org/macports/packages/m4 ---> Installing m4 @1.4.17_0 ---> Activating m4 @1.4.17_0 ---> Cleaning m4 ---> Fetching archive for bison ---> Attempting to fetch bison-3.0.4_1.darwin_15.x86_64.tbz2 from https://packages.macports.org/bison ---> Attempting to fetch bison-3.0.4_1.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/bison ---> Installing bison @3.0.4_1 ---> Activating bison @3.0.4_1 ---> Cleaning bison ---> Fetching archive for flex ---> Attempting to fetch flex-2.6.0_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/flex ---> Attempting to fetch flex-2.6.0_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/flex ---> Installing flex @2.6.0_0 ---> Activating flex @2.6.0_0 ---> Cleaning flex ---> Fetching archive for jpeg ---> Attempting to fetch jpeg-9b_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/jpeg ---> Attempting to fetch jpeg-9b_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/jpeg ---> Installing jpeg @9b_0 ---> Activating jpeg @9b_0 ---> Cleaning jpeg ---> Fetching archive for pkgconfig ---> Attempting to fetch pkgconfig-0.29.1_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/pkgconfig ---> Attempting to fetch pkgconfig-0.29.1_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/pkgconfig ---> Installing pkgconfig @0.29.1_0 ---> Activating pkgconfig @0.29.1_0 ---> Cleaning pkgconfig ---> Fetching archive for xbitmaps ---> Attempting to fetch xbitmaps-1.1.1_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xbitmaps ---> Attempting to fetch xbitmaps-1.1.1_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xbitmaps ---> Installing xbitmaps @1.1.1_0 ---> Activating xbitmaps @1.1.1_0 ---> Cleaning xbitmaps ---> Fetching archive for xorg-printproto ---> Attempting to fetch xorg-printproto-1.0.5_0.darwin_15.noarch.tbz2 from https://packages.macports.org/xorg-printproto ---> Attempting to fetch xorg- printproto-1.0.5_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/xorg-printproto ---> Installing xorg-printproto @1.0.5_0 ---> Activating xorg-printproto @1.0.5_0 ---> Cleaning xorg-printproto ---> Fetching archive for xorg-libXp ---> Attempting to fetch xorg-libXp-1.0.3_0.darwin_15.x86_64.tbz2 from https://packages.macports.org/xorg-libXp ---> Attempting to fetch xorg-libXp-1.0.3_0.darwin_15.x86_64.tbz2.rmd160 from https://packages.macports.org/xorg-libXp ---> Installing xorg-libXp @1.0.3_0 ---> Activating xorg-libXp @1.0.3_0 ---> Cleaning xorg-libXp ---> Fetching archive for openmotif Error: org.macports.archivefetch for port openmotif returned: xorg-libXt must be installed with +flat_namespace. Error: Failed to install openmotif Please see the log file for port openmotif for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_openmotif/openmotif/main.log Error: The following dependencies were not installed: glw openmotif gsed gtime gv Xaw3d xpm ghostscript jbig2dec lcms2 tiff libidn libpaper perl5 perl5.24 gdbm xorg-libXinerama xorg-xineramaproto lynx makedepend sablotron spidermonkey nspr readline xfig transfig netpbm jasper jbigkit libnetpbm xorg-libXaw To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port arb failed Ryan-Walkers-iMac:~ walker92$ }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 15:51:01 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 15:51:01 -0000 Subject: [MacPorts] #53180: Processing of port arb failed In-Reply-To: <045.02177858dbd15b1e9c09234e4adb755f@macports.org> References: <045.02177858dbd15b1e9c09234e4adb755f@macports.org> Message-ID: <060.638de80301ae5aa87bb354f59f2c600f@macports.org> #53180: Processing of port arb failed -----------------------+-------------------- Reporter: walker92 | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: invalid | Keywords: Port: arb | -----------------------+-------------------- Changes (by mf2k): * status: new => closed * resolution: => invalid Comment: The solution is in the output you provided. {{{ xorg-libXt must be installed with +flat_namespace }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 17:03:43 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 17:03:43 -0000 Subject: [MacPorts] #53181: git @2.11.0: fetch failed on OS X 10.5 ppc and intel Message-ID: <046.2a400e8d1ec1a965acc9aeb1e5d1ecb9@macports.org> #53181: git @2.11.0: fetch failed on OS X 10.5 ppc and intel -----------------------+------------------- Reporter: pkoshevoy | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: leopard | Port: git -----------------------+------------------- {{{ $ sudo port upgrade outdated Password: ---> Computing dependencies for git ---> Fetching distfiles for git ---> Attempting to fetch git-2.11.0.tar.gz from http://distfiles.macports.org/git ---> Attempting to fetch git-2.11.0.tar.gz from https://cdn.kernel.org/pub/software/scm/git/ ---> Attempting to fetch git-2.11.0.tar.gz from https://www.kernel.org/pub/software/scm/git/ ---> Attempting to fetch git-2.11.0.tar.gz from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/git ---> Attempting to fetch git-2.11.0.tar.gz from http://sea.us.distfiles.macports.org/macports/distfiles/git ---> Attempting to fetch git-2.11.0.tar.gz from http://lil.fr.distfiles.macports.org/git ---> Attempting to fetch git-2.11.0.tar.gz from http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/git ---> Attempting to fetch git-2.11.0.tar.gz from http://kmq.jp.distfiles.macports.org/git ---> Attempting to fetch git-2.11.0.tar.gz from http://nue.de.distfiles.macports.org/git ---> Attempting to fetch git-2.11.0.tar.gz from http://cjj.kr.distfiles.macports.org/git ---> Attempting to fetch git-2.11.0.tar.gz from http://osl.no.distfiles.macports.org/git ---> Attempting to fetch git-2.11.0.tar.gz from http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/git ---> Attempting to fetch git-2.11.0.tar.gz from http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/git ---> Attempting to fetch git-2.11.0.tar.gz from http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/git ---> Attempting to fetch git-2.11.0.tar.gz from http://jog.id.distfiles.macports.org/macports/distfiles/git ---> Attempting to fetch git-2.11.0.tar.gz from http://jnb.za.distfiles.macports.org/distfiles/git ---> Attempting to fetch git-2.11.0.tar.gz from http://her.gr.distfiles.macports.org/git ---> Attempting to fetch git-2.11.0.tar.gz from http://pek.cn.distfiles.macports.org/macports/distfiles/git Error: org.macports.fetch for port git returned: fetch failed Please see the log file for port git for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_git/git/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: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 17:11:56 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 17:11:56 -0000 Subject: [MacPorts] #53178: php55 @5.5.36: update to 5.5.38 In-Reply-To: <041.2b3adeb402165ddee783bab38bd49f92@macports.org> References: <041.2b3adeb402165ddee783bab38bd49f92@macports.org> Message-ID: <056.5fdd2471216aa2537e97a366001ddb90@macports.org> #53178: php55 @5.5.36: update to 5.5.38 ---------------------+------------------------ Reporter: l2dy | Owner: ryandesign Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: php55 | ---------------------+------------------------ Changes (by ryandesign): * status: assigned => accepted Comment: Thanks, I didn't realize livecheck had stopped checking php55. I'll fix that and update the port. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 17:26:12 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 17:26:12 -0000 Subject: [MacPorts] #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X In-Reply-To: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> References: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> Message-ID: <061.dde520ea57ce31b4529080ef45cc42ae@macports.org> #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X ------------------------+--------------------------- Reporter: ballapete | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: tiger powerpc Port: libuv | ------------------------+--------------------------- Changes (by kencu): * Attachment "patch-cmake-371-Portfile-Tigerfix.diff" added. a patch for cmake-371 for tiger to disable need for libuv -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 17:30:33 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 17:30:33 -0000 Subject: [MacPorts] #53182: cctools @895_3 fails to build on OS X 10.5 Message-ID: <046.7e4e93468781af56cae41826e3014764@macports.org> #53182: cctools @895_3 fails to build on OS X 10.5 -----------------------+--------------------- Reporter: pkoshevoy | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: leopard | Port: cctools -----------------------+--------------------- can't upgrade libvpx because cctools fails to build: {{{ :info:build /usr/bin/gcc-4.2 -Os -std=gnu99 -std=c99 -Os -DLTO_SUPPORT -g -I../../include -Wall -D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_ -D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_ -I/opt/local/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-895/../ld64-274.1/src/abstraction -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-895/../ld64-274.1/src/other -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-895/include -arch i386 -I/opt/local/libexec/llvm-3.3/include -DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -O3 -g -fno-common -c \ :info:build -I/opt/local/include \ :info:build -I/opt/local/include \ :info:build -o ./lto.o ../lto.c :info:build ../lto.c:21: error: expected declaration specifiers or ‘...’ before ‘*’ token :info:build ../lto.c:21: warning: type defaults to ‘int’ in declaration of ‘lto_bool_t’ :info:build ../lto.c:21: error: ‘lto_bool_t’ declared as function returning a function :info:build ../lto.c:21: error: function ‘lto_bool_t’ is initialized like a variable :info:build ../lto.c: In function ‘is_llvm_bitcode_from_memory’: :info:build ../lto.c:137: error: ‘lto_is_object’ undeclared (first use in this function) :info:build ../lto.c:137: error: (Each undeclared identifier is reported only once :info:build ../lto.c:137: error: for each function it appears in.) :info:build ../lto.c:164: warning: implicit declaration of function ‘lto_is_object’ :info:build make[2]: *** [lto.o] Error 1 :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-895/libstuff/dynamic_obj' :info:build make[1]: *** [dynamic] Error 2 :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-895/libstuff' :info:build make: *** [all] Error 1 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-895' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-895" && /usr/bin/make -w all RC_OS="macos" RC_ProjectSourceVersion=895 USE_DEPENDENCY_FILE=NO BUILD_DYLIBS=NO CC="/usr/bin/gcc-4.2 -Os -std=gnu99" CXX="/usr/bin/g++-4.2 -Os" CXXLIB="" TRIE=-DTRIE_SUPPORT RC_ARCHS="i386" SDK="-I/opt/local/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-895/../ld64-274.1/src/abstraction -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-895/../ld64-274.1/src/other -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/work/cctools-895/include" LTO=-DLTO_SUPPORT RC_CFLAGS="-arch i386 `llvm-config-mp-3.3 --cflags`" LLVM_MC="llvm-mc-mp-3.3" :info:build Exit code: 2 :error:build org.macports.build for port cctools returned: command execution failed :debug:build Error code: CHILDSTATUS 28743 2 :debug:build Backtrace: command execution failed while executing "system -nice 0 $fullcmdstring" ("eval" body line 1) invoked from within "eval system $notty $nice \$fullcmdstring" invoked from within "command_exec build" (procedure "portbuild::build_main" line 8) invoked from within "portbuild::build_main org.macports.build" ("eval" body line 1) invoked from within "eval $procedure $targetname" :info:build Warning: targets not executed for cctools: org.macports.activate org.macports.build org.macports.destroot org.macports.install :notice:build Please see the log file for port cctools for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cctools/cctools/main.log }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 17:31:29 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 17:31:29 -0000 Subject: [MacPorts] #53182: cctools @895_3 fails to build on OS X 10.5 In-Reply-To: <046.7e4e93468781af56cae41826e3014764@macports.org> References: <046.7e4e93468781af56cae41826e3014764@macports.org> Message-ID: <061.7f326bfd954f848509f17b62608dfb52@macports.org> #53182: cctools @895_3 fails to build on OS X 10.5 ------------------------+--------------------- Reporter: pkoshevoy | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: leopard Port: cctools | ------------------------+--------------------- Changes (by pkoshevoy): * Attachment "cctools-main.log" added. main.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 17:54:24 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 17:54:24 -0000 Subject: [MacPorts] #53182: cctools @895_3 fails to build on OS X 10.5 In-Reply-To: <046.7e4e93468781af56cae41826e3014764@macports.org> References: <046.7e4e93468781af56cae41826e3014764@macports.org> Message-ID: <061.fedfffc71690b7ff9614e845269abb04@macports.org> #53182: cctools @895_3 fails to build on OS X 10.5 ------------------------+---------------------- Reporter: pkoshevoy | Owner: jeremyhu Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: leopard Port: cctools | ------------------------+---------------------- Changes (by mf2k): * status: new => assigned * cc: jeremyhu (removed) * owner: => jeremyhu -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 18:13:14 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 18:13:14 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.d197228c7e2b7404fcead1d3e3e89b4d@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by MarcusCalhoun-Lopez): Replying to [comment:14 RJVB]: > - port:qt5 currently installs the pkg-config files to `${qt_libs_dir}/pkgconfig`. Is that to be changed? Links to the .pc files are currently put into `${prefix}/lib/pkgconfig` (see [https://trac.macports.org/changeset/142505/trunk/dports here]). > - I don't really like the "-append" suffix, if not only because it suggests there are also "-prepend", "-replace" etc. modifiers. You are right, the original name is probably best. > - qt5.using_kde isn't always defined, I don't know if `[tbool qt5.using_kde]` catches all possible situations(?) Evidently the variable could be defined by the shared PortGroup. `tbool` [https://github.com/macports/macports- base/blob/master/src/port1.0/portutil.tcl#L884 tests for existence] > I am VERY much in favour of maintaining the PortGroup approach implemented in > [https://github.com/RJVB/macstrop/blob/master/_resources/port1.0/group/qt5-1.0.tcl qt5-1.0.tcl] I believe there would be **strong** objections from the other developers to having dependencies influenced by {{{[file exists ${prefix}/include/qt5/QtCore/QtCore]}}}.[[BR]] At the very least, it would run contrary to ReproducibleBuilds.[[BR]] `port deps libQGLViewer` would give different answers from one day to the next depending on which Qt is installed. > The qt5-kde stub ports are mostly there to be able to satisfy dependency requirements when someone moves from port:qt5 to port:qt5-kde . A user who installs port:qt5-kde from the start shouldn't be obliged to need them. I may have misunderstood how qt5-kde stubports are used, but I humbly suggest this is resolved after consensus is reached on general strategy. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 18:13:48 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 18:13:48 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.83c7a5f0b7ee825b590d77ad2ba0a13c@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by MarcusCalhoun-Lopez): Please correct me if I am wrong, but we have three major design goals: 1. Allow the installation of older versions of Qt to accommodate older OSs. 1. Support a patched version of Qt which is necessary to be used with KDE. 1. Minimal disruption of ports that use Qt. Here are the options I can determine: 1. Let the user decide which Qt to install with reasonable defaults. * This seems to be the current path. * Runs contrary to ReproducibleBuilds and MacPorts philosophy in general. * There might be (and probably are) any number of ABI comparabilities that we don't know about. 1. Variants (`qt5`, `qt56`, `qt5-kde`) defined in `qt5-1.0.tcl` to conflicting Qts. * The various GTK ports had to jump through quite a few hoops with `+x11` vs `+quartz`. The various maintainers have done a wonderful job, but, from the outside, it looked like quite a bit of effort. I am not sure I want to have allot of `require_active_variants` in client ports. 1. Variants (`qt5`, `qt56`, `qt5-kde`) defined in `qt5-1.0.tcl` to non- conflicting Qts. * Each Qt would be installed in its own location (`${prefix}/libexec/qt5`, `${prefix}/libexec/qt5-kde`, etc.) * Potentially, lots of `require_active_variants` in client ports. 1. Completely separate `qt5` and `qt5-kde` * Each Qt would be installed in its own location (`${prefix}/libexec/qt5`, `${prefix}/libexec/qt5-kde`, etc.) * There would be a `qt5-1.0.tcl` and `qt5-kde-1.0.tcl` and each port would have decide which one to use. * Using `qt5-1.0.tcl`, the Qt version would be determined by the OS version and cxx_stdlib. 1. Attempt to merge `qt5` and `qt5-kde` * The necessary KDE patches would be added via a variant in `qt5`. * The Qt version would be determined by the OS and cxx_stdlib. * `require_active_variants`might still be necessary in client ports, but probably not many. If I understand correctly, Mojca has raised serious concerns about (1), and René has objected to (2) and (3).[[BR]] Personally, I am leaning toward (4) or (5).[[BR]] I must admit, however, that I do not understand the various [https://github.com/RJVB/macstrop/tree/master/aqua/qt5-kde KDE patches].[[BR]] René has [https://lists.macports.org/pipermail/macports- dev/2016-October/033944.html expressed reservations about (5)]. Based on the numerous discussions we have already had, I thinks it is fair to say that a perfect solution is unlikely to present itself.[[BR]] I am willing to work on any of the solution, but my order of preference is (5), (4), (1), (2), then (3). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 18:18:01 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 18:18:01 -0000 Subject: [MacPorts] #53177: activator @1.3.12 : new port In-Reply-To: <048.c53ca43819289286db81094705cf6daf@macports.org> References: <048.c53ca43819289286db81094705cf6daf@macports.org> Message-ID: <063.60abc67bf981965d023d0ba073389c80@macports.org> #53177: activator @1.3.12 : new port --------------------------+----------------- Reporter: nhojpatrick | Owner: Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: activator | --------------------------+----------------- Comment (by nhojpatrick): pull request updated -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 18:18:26 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 18:18:26 -0000 Subject: [MacPorts] #53117: Braeburn POST requests (Trac, Mailman) are unreliable In-Reply-To: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> References: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> Message-ID: <056.c3fb5e32323a9b51f2f1713fa3426b5c@macports.org> #53117: Braeburn POST requests (Trac, Mailman) are unreliable -----------------------------+--------------------- Reporter: mf2k | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+--------------------- Comment (by neverpanic): Do you have IPv6 connectivity when this happens? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 18:31:55 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 18:31:55 -0000 Subject: [MacPorts] #53117: Braeburn POST requests (Trac, Mailman) are unreliable In-Reply-To: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> References: <041.c6b9e1c59e9844cc34a136b97d18db64@macports.org> Message-ID: <056.655f96170159b10dd46cc809027c7b66@macports.org> #53117: Braeburn POST requests (Trac, Mailman) are unreliable -----------------------------+--------------------- Reporter: mf2k | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+--------------------- Comment (by mf2k): I do not believe so. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 18:31:59 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 18:31:59 -0000 Subject: [MacPorts] #52321: coccinelle : Configure failure (ac_nonexistent.h) In-Reply-To: <055.e60ca9dc8b9d90508ccd31bd1ea040c7@macports.org> References: <055.e60ca9dc8b9d90508ccd31bd1ea040c7@macports.org> Message-ID: <070.0d57e66c18d6748d5c3304cc55e93219@macports.org> #52321: coccinelle : Configure failure (ac_nonexistent.h) -------------------------+------------------- Reporter: skycrawl@… | Owner: g5pw Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: coccinelle | -------------------------+------------------- Comment (by SkyCrawl): No configuration error anymore but there's a build error instead (MacPorts v2.3.5!): {{{ :info:build /opt/local/bin/ocamlopt.opt -unsafe -I ../commons -I ../commons/ocamlextra -I ../globals -I -c ast_cocci.ml :info:build ld: warning: directory not found for option '-L-c' :info:build ld: warning: directory not found for option '-L-c' :info:build File "dpll.ml", line 1: :info:build Error: No implementations provided for the following modules: :info:build Common referenced from dpll.cmx :info:build make[6]: *** [dpll.cmx] Error 2 :info:build make[6]: *** Waiting for unfinished jobs.... :info:build File "parse_printf.ml", line 1: :info:build Error: No implementations provided for the following modules: :info:build Flag referenced from parse_printf.cmx :info:build Str referenced from parse_printf.cmx :info:build File "git_grep.ml", line 1: :info:build Error: No implementations provided for the following modules: :info:build Common referenced from git_grep.cmx :info:build make[6]: *** [parse_printf.cmx] Error 2 :info:build make[6]: *** [git_grep.cmx] Error 2 :info:build File "cocci_grep.ml", line 1: :info:build Error: No implementations provided for the following modules: :info:build Flag referenced from cocci_grep.cmx :info:build Str referenced from cocci_grep.cmx :info:build Common referenced from cocci_grep.cmx :info:build make[6]: *** [cocci_grep.cmx] Error 2 :info:build ld: warning: directory not found for option '-L-c' :info:build File "ast_cocci.ml", line 1: :info:build Error: No implementations provided for the following modules: :info:build Common referenced from ast_cocci.cmx :info:build make[6]: *** [ast_cocci.cmx] Error 2 :info:build make[6]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_coccinelle/coccinelle/work/coccinelle-1.0.6/parsing_cocci' :info:build make[5]: *** [all.opt] Error 2 :info:build make[5]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_coccinelle/coccinelle/work/coccinelle-1.0.6/parsing_cocci' :info:build make[4]: *** [parsing_cocci.opt] Error 2 :info:build make[4]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_coccinelle/coccinelle/work/coccinelle-1.0.6' :info:build make[3]: *** [subdirs.opt] Error 1 :info:build make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_coccinelle/coccinelle/work/coccinelle-1.0.6' :info:build make[2]: *** [opt-compil] Error 2 :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_coccinelle/coccinelle/work/coccinelle-1.0.6' :info:build make[1]: *** [all-release] Error 2 :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_coccinelle/coccinelle/work/coccinelle-1.0.6' :info:build make: *** [all] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_coccinelle/coccinelle/work/coccinelle-1.0.6' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_coccinelle/coccinelle/work/coccinelle-1.0.6" && /usr/bin/make -j8 -w all :info:build Exit code: 2 :error:build org.macports.build for port coccinelle returned: command execution failed :debug:build Error code: CHILDSTATUS 4367 2 :debug:build Backtrace: command execution failed while executing "system -nice 0 $fullcmdstring" ("eval" body line 1) invoked from within "eval system $notty $nice \$fullcmdstring" invoked from within "command_exec build" (procedure "portbuild::build_main" line 8) invoked from within "portbuild::build_main org.macports.build" ("eval" body line 1) invoked from within "eval $procedure $targetname" :info:build Warning: targets not executed for coccinelle: org.macports.activate org.macports.build org.macports.destroot org.macports.install :notice:build Please see the log file for port coccinelle for details: }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 18:51:36 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 18:51:36 -0000 Subject: [MacPorts] #52321: coccinelle : Configure failure (ac_nonexistent.h) In-Reply-To: <055.e60ca9dc8b9d90508ccd31bd1ea040c7@macports.org> References: <055.e60ca9dc8b9d90508ccd31bd1ea040c7@macports.org> Message-ID: <070.5fe89bf822d351643237a3720fcc3689@macports.org> #52321: coccinelle : Configure failure (ac_nonexistent.h) -------------------------+------------------- Reporter: skycrawl@… | Owner: g5pw Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: coccinelle | -------------------------+------------------- Comment (by g5pw): That's a weird error. Could you clean, rebuild and attach the complete log? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 19:04:39 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 19:04:39 -0000 Subject: [MacPorts] #53154: qhull seems to fail systematically when called from octave In-Reply-To: <044.b2f66d585e240ba60d5800db45e93af9@macports.org> References: <044.b2f66d585e240ba60d5800db45e93af9@macports.org> Message-ID: <059.03852d71e46859c12cf4eb94454870c7@macports.org> #53154: qhull seems to fail systematically when called from octave ---------------------------+--------------------------------- Reporter: pierard | Owner: MarcusCalhoun-Lopez Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: octave qhull | ---------------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): Octave can now be [https://github.com/macports/macports- ports/commit/a099fb31427d00275534827896d84c934fe0af10#diff- ee42da86e52de9b0680a5402ffdb07a1 build on servers].[[BR]] Using this build of octave, I am unable to reproduce this problem.[[BR]] By chance, does the new build fix the problem for you? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 19:07:23 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 19:07:23 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.c101bad7d21397c9159b591ac18210fb@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by RJVB): Replying to [comment:17 MarcusCalhoun-Lopez]: > Replying to [comment:14 RJVB]: > > - port:qt5 currently installs the pkg-config files to `${qt_libs_dir}/pkgconfig`. Is that to be changed? > Links to the .pc files are currently put into `${prefix}/lib/pkgconfig` (see [https://trac.macports.org/changeset/142505/trunk/dports here]). OK. I put those files into lib/pkgconfig directly. > > I am VERY much in favour of maintaining the PortGroup approach implemented in > > [https://github.com/RJVB/macstrop/blob/master/_resources/port1.0/group/qt5-1.0.tcl qt5-1.0.tcl] > I believe there would be **strong** objections from the other developers to having dependencies influenced by {{{[file exists ${prefix}/include/qt5/QtCore/QtCore]}}}.[[BR]] > At the very least, it would run contrary to ReproducibleBuilds.[[BR]] No, because of the variant I include. Build with a different Qt5 port installed and your port will be labelled with a variant, which makes it officially different from what the build bots give. KF5 ports set `qt5.prefer_kde 1` before including the PortGroup. On the build bots and on virgin systems that means that `port:qt5-kde` will be installed, and the resulting build will have `+qt5kde` set. This will be exactly the same build on the bots, on a user system when installed from scratch, and on a user system where `port:qt5-kde` was already installed. > `port deps libQGLViewer` would give different answers from one day to the next depending on which Qt is installed. All this is not so different from what you get with regular vs. -devel ports. Yes, `port deps foo-qt5` will give a different answer depending on what Qt5 port is installed, but it's an answer that reflects the local context. I don't see a way around this if we want minimal disruption of ports that use Qt5. Once a choice for Qt5 ports has been made, all Qt5 dependencies should be taken from that same choice: you shouldn't end up mixing qt5-qtbase and qt55-qtdeclarative for instance, nor qt5-kde with qt5-qttools to name just 2 examples. We could probably make a more complex use variants and for the KF5 ports that could logic could be hidden (made automatic) in the KF5 PortGroup. But would we want to oblige users to specify a variant to "force" libQGLViewer or any other "pure Qt5" port to install when port:qt5-kde is installed? Or a variant to make it use port:qt55 on 10.7 if indeed that's the only way to get a proper Qt5 experience on that OS version? > I may have misunderstood how qt5-kde stubports are used, but I humbly suggest this is resolved after consensus is reached on general strategy. Possibly, but in this case the fix is easy; the early return I mentioned above (i.e. don't add any dependencies for a component provided by qt5-kde it it's known we're using qt5-kde). That doesn't really depend on the kind of consensus we can reach. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 19:17:00 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 19:17:00 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.d081aeba253d04070357bf5aa26976b6@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by ctreleaven): To state the obvious, variants suck. You all know why...only one variant can be the default. Thus the need for {{{require_active_variants}}. And the buildbots (at least for now) only build the default. Thus we only serve binaries for the default--which is pretty important for something as large as Qt. As an aside, the current implementation of {{{require_active_variants}}} isn't very friendly to novice users. The word "error" is repeated several time while masking the actual polite message to just reinstall port foo with variant +bar. My mythtv-* ports need {{{require_active_variants}}} and numerous times users have been convinced that the port is broken when they get this result. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 19:17:05 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 19:17:05 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.89bb28fb1b586a3c32250453f2a056cc@macports.org> #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): Replying to [comment:16 mojca]: > I don't understand how this was supposed to fix the problem. (And the builds on the buildbot still fail.) As I understand the situation, not only is `libc++` incompatible with with `libstdc++`, but `libstdc++` is incompatible with older versions.[[BR]] According to [https://gcc.gnu.org/onlinedocs/gcc-5.2.0/libstdc++/manual/manual/using_dual_abi.html this], `-D_GLIBCXX_USE_CXX11_ABI=0` allows the current `libstdc++` to be compatible with the (older) system `libstdc++`. From what I can tell, octave now builds [http://packages.macports.org/octave/?C=N;O=A back to Mac OS 10.7].[[BR]] Can this ticket be closed? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 19:21:14 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 19:21:14 -0000 Subject: [MacPorts] #45665: ilmbase destroot error In-Reply-To: <059.bf08a6d2123fffb12d1930a3f4bfe663@macports.org> References: <059.bf08a6d2123fffb12d1930a3f4bfe663@macports.org> Message-ID: <074.61ff30fa42b42be12e7996e539d5ef5b@macports.org> #45665: ilmbase destroot error ----------------------------+--------------------------------- Reporter: shuttle1978@… | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.2 Resolution: worksforme | Keywords: Port: ilmbase | ----------------------------+--------------------------------- Changes (by MarcusCalhoun-Lopez): * status: assigned => closed * resolution: => worksforme Comment: Without any response, hope that prior changes fixed the problem.[[BR]] Please feel free to reopen if problem crops up again. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 19:30:29 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 19:30:29 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.6d6549f76ba4d1541d2c510ee0cf4194@macports.org> #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Comment (by mojca): Replying to [comment:19 MarcusCalhoun-Lopez]: > As I understand the situation, not only is `libc++` incompatible with with `libstdc++`, but `libstdc++` is incompatible with older versions.[[BR]] Yes, I know. > According to [https://gcc.gnu.org/onlinedocs/gcc-5.2.0/libstdc++/manual/manual/using_dual_abi.html this], `-D_GLIBCXX_USE_CXX11_ABI=0` allows the current `libstdc++` to be compatible with the (older) system `libstdc++`. If one can indeed use gcc 5/6/7 to build C++11 and keep it linked against the system libstdc++, we need to start discussing that on the mailing list. I seriously mean that because that would solve most of our problems. > From what I can tell, octave now builds [http://packages.macports.org/octave/?C=N;O=A back to Mac OS 10.7].[[BR]] > Can this ticket be closed? Sure. I noticed that, but did not manage to figure out how you got it working. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 19:45:20 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 19:45:20 -0000 Subject: [MacPorts] #52321: coccinelle : Configure failure (ac_nonexistent.h) In-Reply-To: <055.e60ca9dc8b9d90508ccd31bd1ea040c7@macports.org> References: <055.e60ca9dc8b9d90508ccd31bd1ea040c7@macports.org> Message-ID: <070.7b8f4ac0d6c8b1d1d8f83c9849df5fb1@macports.org> #52321: coccinelle : Configure failure (ac_nonexistent.h) -------------------------+------------------- Reporter: skycrawl@… | Owner: g5pw Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: coccinelle | -------------------------+------------------- Comment (by SkyCrawl): Hopefully I did what you wanted me to: {{{ sudo port clean coccinelle sudo port install coccinelle }}} And the full log: https://www.dropbox.com/s/od0wlfg6n262gdp/main.log?dl=0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 19:54:07 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 19:54:07 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.7b4478beeabadb828e8bd2435d874775@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by RJVB): Replying to [comment:18 MarcusCalhoun-Lopez]: > Please correct me if I am wrong, but we have three major design goals: I would use this order: > 1. Minimal disruption of ports that use Qt. > 1. Support a patched version of Qt which is necessary to be used with KDE. > 1. Allow the installation of older versions of Qt to accommodate older OSs. > Here are the options I can determine: > 1. Let the user decide which Qt to install with reasonable defaults. > * This seems to be the current path. Indeed. > * Runs contrary to ReproducibleBuilds and MacPorts philosophy in general. Again, it doesn't have to violate the reproducible build approach as far as I understand it. It *is* somewhat of a novel approach for MacPorts, but then the situation is novel(ish) too. Though there are similarities with the libressl vs openssl situation (and I think I have prepared a more elegant implementation for port:qt5 vs port:qt5-kde!) > * There might be (and probably are) any number of ABI comparabilities that we don't know about. The whole discussion about ABI compatibility has probably distracted us from a rather important point. This is a problem that plays only when changing from one port to another. Once you install port:qt5-kde, the +qt5kde variant my portgroup introduces is going to protect against pulling possibly incompatible binary builds from the bots. This means that users who install `port:qt5-kde` will install standard Qt5 ports from source, and when they change back to port:qt5 they may have to reinstall those ports. The same thing happens with GTk X11 vs. XQuartz as far as I know, or LibreSSL vs OpenSSL. It's a choice they make, and we can document such implications. In practice I would expect that most users will decide once which Qt5 port they install and then stick to it. > 2. Variants (`qt5`, `qt56`, `qt5-kde`) defined in `qt5-1.0.tcl` to conflicting Qts. > * The various GTK ports had to jump through quite a few hoops with `+x11` vs `+quartz`. The various maintainers have done a wonderful job, but, from the outside, it looked like quite a bit of effort. I am not sure I want to have allot of `require_active_variants` in client ports. > 3. Variants (`qt5`, `qt56`, `qt5-kde`) defined in `qt5-1.0.tcl` to non- conflicting Qts. > 4. Completely separate `qt5` and `qt5-kde` I am sure I do not want to have to impose the use of the active_variants PortGroup, and also that I don't want to have to guess about the side- effects of potentially having a different Qt version installed somewhere in the same prefix. Those 3 options will more or less oblige me to declare conflicts with port:qt5 in port:qt5-kde, and that's going to cause a big problem with ports like qca-qt5, poppler-qt5 etc. which are dependencies for both regular Qt5 applications and Qt5-kde applications. > 5. Attempt to merge `qt5` and `qt5-kde` > * The necessary KDE patches would be added via a variant in `qt5`. > * The Qt version would be determined by the OS and cxx_stdlib. > * `require_active_variants`might still be necessary in client ports, but probably not many. Require_active_variants would be required in all KF5 ports because there would no longer be a way to indicate a preference. Either way, the Option 5 ship has sailed over a year ago. > If I understand correctly, Mojca has raised serious concerns about (1) Where? Mojca, is this true? I know you've been following my qt5-kde submission ticket from an early stage but cannot recall that you voiced any serious concerns there? > René has [https://lists.macports.org/pipermail/macports- dev/2016-October/033944.html expressed reservations about (5)]. > Based on the numerous discussions we have already had, I thinks it is fair to say that a perfect solution is unlikely to present itself.[[BR]] > I am willing to work on any of the solution, but my order of preference is (5), (4), (1), (2), then (3). My preference is evidently with the current approach, option 1). I've had a lot of time to think about this, and I think it's the only approach that allows to introduce KF5 in a way I can really stand behind. It's also the approach that puts the least additional maintenance effort on Marcus and maintainers of other ports depending on Qt5. I have already stated that I'm willing to carry the brunt of the maintenance of the shared PortGroup, but for the rest responsibility of everything related to the current port:qt5 will remain with Marcus, and I will keep in sync with any chances he makes that have implications for the compatibility between the ports. That's not just minimal disruption of ports that use Qt, it's also minimal disruption of all port maintainers except myself (but then guess who's proposing to introduce another Qt5 port :)). (There *is* the question of shared maintenance of the qmake5 PG of course but there too I have already re-organised the file to make it clear which parts are shared and which aren't). The only other option I see is to include the QStandardPaths patch into port:qt5, without using a variant (just including the patch doesn't change Qt's default behaviour). That is probably the only adaptation for KF5 that is really required, though I cannot fathom nor guarantee how well things will work with the installation layout used by port:qt5 . They may simply work, but maybe they won't; the different and very non-standard location of the CMake modules may be an issue, for instance. Actually, I do see another option, and that's to keep on proposing the KF5 ports as I do at the moment: as a custom ports tree with instructions on how to use it. But that would be somewhat of a pity. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 20:10:14 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 20:10:14 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.2809d1190d72a4a54f8949359aa03274@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by RJVB): Replying to [comment:20 ctreleaven]: > To state the obvious, variants suck. You all know why...only one variant can be the default. Among mutually conflicting variants, yes. More in general, only one set of variants can be the default. It would also suck if users would have to add a variant to all KF5 ports they might want to install (including all 60+ frameworks), or if they would have to use a variant to force non-KF5 ports to install against port:qt5-kde . BTW, what happens when you do `default_variants +foo` before variant foo has been defined? Will that still work, or does the statement have to come after the variant has been defined? > Thus the need for {{{require_active_variants}}} ... ... actually goes a bit beyond that. It can be used for any combination of variants required. `port:kf5-digikam` for instance requires `opencv +qt5+contrib`, and only +qt5 conflicts with one of the port's other variants. > Thus we only serve binaries for the default--which is pretty important for something as large as Qt. Those are actually the main arguments why Marko and I were almost relieved when it became clear that we'd better prepare a dedicated `port:qt5-kde`. It would make dependencies easier (and allow ports to express a preference rather than a hard requirement), but also allow the build bots to provide a binary build. > As an aside, the current implementation of {{{require_active_variants}}} isn't very friendly to novice users. The word "error" is repeated several time while masking the actual polite message to just reinstall port foo with variant +bar. My mythtv-* ports need {{{require_active_variants}}} and numerous times users have been convinced that the port is broken when they get this result. I suppose you're entitled to feel welcome to change the message based on the feedback you've gotten! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 20:32:29 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 20:32:29 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.7c5d0babc19ae4bea530d6184ecc037c@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by RJVB): A thought resulting from my reply to Craig: suppose we have a shared Qt5 PG that determines which actual Qt5 port and PortGroup are to be used and which also defines a `qt5kde` variant. Suppose also that ports can do {{{ default_variants +qt5kde PortGroup qt5 1.0 }}} instead of {{{ set qt5.prefer_kde 1 PortGroup qt5 1.0 }}} and be assured that `[variant_isset qt5kde]` is true in qt5-1.0.tcl . I *think* that in that case, setting `+qt5kde` in ${prefix}/etc/macports/variants.conf will be analogous to deciding to use `port:qt5-kde` simply by installing it. In that case `port deps` will change it's output in reaction to a variant and not simply to what's installed (something I don't see the problem with but which may be unacceptable for that very reason 8-) ). I'll have to sleep a few nights over this and see how well I get used to the idea, but it's a solution I might be able to live with. There's one big problem with this approach: how do we handle the situation where `port:qt5` is installed, and a KF5 port or the user sets +qt5kde? The logical thing to do in that case would be - if +qt5kde is the result of `default_variants`, unset the variant so that future tests `[variant_isset qt5kde]` will fail (but we can't) - if +qt5kde is the result of +qt5kde on the commandline or in variants.conf, raise an error Evidently the opposite situation is just as much a problem (though I'd hope there will never be a hard reason for ports to require the stock `port:qt5`). I see that variants set through variants.conf show up as `(+)foo` while those set with `default_variants` as `[+]foo`. So at some level the difference can be made, but I don't know if that's possible in the Portfile. PS: > `tbool` ​tests for existence With interpreted languages it can make a considerable difference to avoid calls to user-defined procedures for frequent operations; dependency calculations can take long enough as it is already. Better ensure that the variable to be tested always exists in that case. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 20:41:49 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 20:41:49 -0000 Subject: [MacPorts] #53181: git @2.11.0: fetch failed on OS X 10.5 ppc and intel In-Reply-To: <046.2a400e8d1ec1a965acc9aeb1e5d1ecb9@macports.org> References: <046.2a400e8d1ec1a965acc9aeb1e5d1ecb9@macports.org> Message-ID: <061.b7e89e580a57c8881613b234530306e7@macports.org> #53181: git @2.11.0: fetch failed on OS X 10.5 ppc and intel ------------------------+--------------------- Reporter: pkoshevoy | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: leopard Port: git | ------------------------+--------------------- Comment (by kencu): Although a more permanent fix for this is likely coming along eventually, for now the only practical and functional solution to this is to rebuild macports from source referencing a newer version of curl. There are a number of posts here on trac detailing the step-by-step instructions how to do that. One of the them is here . I've done it on every machine I have < 10.8. It works great at present, and solves the problem comprehensively. It comes with no warranty, though. Although you could install curl into `/opt/local` and self-reference it when rebuilding macports, I would suggest (and described how to) install a parallel version of macports into `/opt/bootstrap`, and use a curl installation in there to upgrade macports installed into `/opt/local` -- just in case one day, in a fit of confusion, you `sudo port deactivate` everything, and blow up your macports install. If this all seems a bit of a hassle, yeah - you're right - but hey, it's a 10+ year old machine and it's still usable after all these years, so what's a 10 minute fix in that context? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 20:54:56 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 20:54:56 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.5db8f2f4e84dbecbe4eafc6708fa2f0f@macports.org> #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Comment (by kencu): Replying to [comment:20 mojca]: > If one can indeed use gcc 5/6/7 to build C++11 and keep it linked against the system libstdc++, we need to start discussing that on the mailing list. I seriously mean that because that would solve most of our problems. As you know from our previous posts I've been doing this for months on 10.4 and 10.5 PPC with good success. Occasionally you need to build something with apple's compilers (due to complex ObjC or apple- specific flags), but usually things build and work well. A list of what I have currently installed on 10.4 PPC is here if you're curious . 10.5 builds more, but I don't have that list up right now. I have llvm-3.7, libc++, libc++abi, libunwind, libmacho, ld64, and cctools installed and apparently working on 10.5 PPC. Just can't quite get clang-3.7 to build through to completion at present -- some kind of out- of-memory error in the final link... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 21:08:03 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 21:08:03 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.da175116269471a56c25d600da2920dc@macports.org> #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Comment (by kencu): Replying to [comment:19 MarcusCalhoun-Lopez]: > From what I can tell, octave now builds [http://packages.macports.org/octave/?C=N;O=A back to Mac OS 10.7].[[BR]] > Can this ticket be closed? For a data point, just built and runs successfully on 10.6 as well (upgraded to LibcxxOnOlderSystems) Thanks! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 21:16:39 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 21:16:39 -0000 Subject: [MacPorts] #53181: git @2.11.0: fetch failed on OS X 10.5 ppc and intel In-Reply-To: <046.2a400e8d1ec1a965acc9aeb1e5d1ecb9@macports.org> References: <046.2a400e8d1ec1a965acc9aeb1e5d1ecb9@macports.org> Message-ID: <061.3353bcf7afa46ceb828bd2dd23e64f66@macports.org> #53181: git @2.11.0: fetch failed on OS X 10.5 ppc and intel ------------------------+--------------------- Reporter: pkoshevoy | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: duplicate | Keywords: leopard Port: git | ------------------------+--------------------- Changes (by mf2k): * status: new => closed * resolution: => duplicate Comment: Duplicate of #51516. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 21:17:37 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 21:17:37 -0000 Subject: [MacPorts] #51516: MacPorts should use a bundled copy of a newer libcurl and SSL library rather than the OS X version In-Reply-To: <047.77071f9662e9241a7e27fcde2de41507@macports.org> References: <047.77071f9662e9241a7e27fcde2de41507@macports.org> Message-ID: <062.194cb58ce252fd36c176f0f1a361d845@macports.org> #51516: MacPorts should use a bundled copy of a newer libcurl and SSL library rather than the OS X version --------------------------+-------------------------------- Reporter: ryandesign | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: MacPorts Future Component: base | Version: Resolution: | Keywords: Port: | --------------------------+-------------------------------- Changes (by mf2k): * cc: pkoshevoy (added) Comment: Has duplicate #53181. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 23:10:07 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 23:10:07 -0000 Subject: [MacPorts] #52558: python36 requests install of py36-readline In-Reply-To: <048.36c067b06bb3814e51eced50687cae1f@macports.org> References: <048.36c067b06bb3814e51eced50687cae1f@macports.org> Message-ID: <063.2b59af2a1c5b1868cd6c442a9cc59484@macports.org> #52558: python36 requests install of py36-readline -------------------------------------+-------------------------------- Reporter: nhojpatrick | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: python36 py36-readline | -------------------------------------+-------------------------------- Comment (by kundor): This is still the case now that Python 3.6.0 is released. python36 setup requests the installation of py36-readline, which doesn't exist. There '''is''' a port named py36-gnureadline. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 23:51:26 2016 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2016 23:51:26 -0000 Subject: [MacPorts] #53124: julia: Update to version 0.5 In-Reply-To: <045.fc17f67b995cc13ab11a9440273f871f@macports.org> References: <045.fc17f67b995cc13ab11a9440273f871f@macports.org> Message-ID: <060.a65c615a8f6acd75a5479a3a8236718e@macports.org> #53124: julia: Update to version 0.5 -----------------------+------------------------ Reporter: manuSrep | Owner: seanfarley Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: julia | -----------------------+------------------------ Comment (by seanfarley): I can reproduce, so that's good. Haven't figured out what's going on yet. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 00:38:18 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 00:38:18 -0000 Subject: [MacPorts] #53076: gcc47 @4.7.4_6 fails to build In-Reply-To: <043.7f4cb9cd057864586874ffa3345eb065@macports.org> References: <043.7f4cb9cd057864586874ffa3345eb065@macports.org> Message-ID: <058.7a5f1163b86a7e6affeac5c542360cb1@macports.org> #53076: gcc47 @4.7.4_6 fails to build ---------------------+---------------------- Reporter: posita | Owner: mww@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gcc47 | ---------------------+---------------------- Comment (by kencu): try downgrading to texinfo 6.1.0. Worked for me with gcc46. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 00:41:18 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 00:41:18 -0000 Subject: [MacPorts] #53183: onioncat @0.2.2.r569: binary gcat conflicts with coreutils Message-ID: <041.2a11f9e7c396c13fa3259fc5e42aebf7@macports.org> #53183: onioncat @0.2.2.r569: binary gcat conflicts with coreutils ------------------------+---------------------- Reporter: l2dy | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: maintainer | Port: onioncat ------------------------+---------------------- The onioncat port contains gcat which conflicts with gcat in coreutils. Which resolution is preferred? Citing mojca: > Yes. You should either: > 1. Add conflicts coreutils to onioncat and conflicts onioncat to coreutils and prevent users from having both installed at the same time. (This is already the case now, but it is better to make the conflict explicit.) > 2. Resolve the conflict by renaming the gcat binary. > And you should probably open a ticket. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 01:04:23 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 01:04:23 -0000 Subject: [MacPorts] #53169: PortIndex contains expanded prefix In-Reply-To: <043.c2f960f04c1b7e8f6d401c4b06c1f5a5@macports.org> References: <043.c2f960f04c1b7e8f6d401c4b06c1f5a5@macports.org> Message-ID: <058.247d06df722bd90de58263d46d72d8f9@macports.org> #53169: PortIndex contains expanded prefix ---------------------+------------------------ Reporter: jmroot | Owner: neverpanic Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: fixed | Keywords: Port: | ---------------------+------------------------ Changes (by neverpanic): * owner: => neverpanic * status: new => closed * resolution: => fixed Comment: In [changeset:"9a23db2fde81660ca42425ae0647a4f347571f45/macports-base" 9a23db2/macports-base]: {{{ #!ConfigurableCommitTicketReference repository="macports-base" revision="9a23db2fde81660ca42425ae0647a4f347571f45" portindex: Restore special $prefix handling This avoids expanded values for ${prefix} in the PortIndex. Closes: https://trac.macports.org/ticket/53169 See: https://trac.macports.org/ticket/17182 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 01:04:24 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 01:04:24 -0000 Subject: [MacPorts] #17182: Variables aren't expanded in path:-style dependencies In-Reply-To: <047.4b428150868604608f864c0965970402@macports.org> References: <047.4b428150868604608f864c0965970402@macports.org> Message-ID: <062.bfb9551c32b42d3b31562bc824d2d307@macports.org> #17182: Variables aren't expanded in path:-style dependencies -------------------------+-------------------------------- Reporter: ryandesign | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: MacPorts 1.8.0 Component: base | Version: 1.6.0 Resolution: fixed | Keywords: Port: | -------------------------+-------------------------------- Comment (by neverpanic): In [changeset:"9a23db2fde81660ca42425ae0647a4f347571f45/macports-base" 9a23db2/macports-base]: {{{ #!ConfigurableCommitTicketReference repository="macports-base" revision="9a23db2fde81660ca42425ae0647a4f347571f45" portindex: Restore special $prefix handling This avoids expanded values for ${prefix} in the PortIndex. Closes: https://trac.macports.org/ticket/53169 See: https://trac.macports.org/ticket/17182 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 01:08:38 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 01:08:38 -0000 Subject: [MacPorts] #53175: fdupes now v1.6.1 In-Reply-To: <043.b50c023176f31b6728142bf9ec50c485@macports.org> References: <043.b50c023176f31b6728142bf9ec50c485@macports.org> Message-ID: <058.86b5a8a156cfe30b791fd31099a946cd@macports.org> #53175: fdupes now v1.6.1 ---------------------+--------------------------------- Reporter: bunk3m | Owner: grimreaper Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: fdupes | ---------------------+--------------------------------- Changes (by grimreaper): * Attachment "bump.2.patch" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 02:38:13 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 02:38:13 -0000 Subject: [MacPorts] #53169: PortIndex contains expanded prefix In-Reply-To: <043.c2f960f04c1b7e8f6d401c4b06c1f5a5@macports.org> References: <043.c2f960f04c1b7e8f6d401c4b06c1f5a5@macports.org> Message-ID: <058.2dc4bdb43dac30f8fdfb07d73798b468@macports.org> #53169: PortIndex contains expanded prefix ---------------------+---------------------------- Reporter: jmroot | Owner: neverpanic Type: defect | Status: closed Priority: Normal | Milestone: MacPorts 2.4.0 Component: base | Version: 2.3.5 Resolution: fixed | Keywords: Port: | ---------------------+---------------------------- Changes (by jmroot): * version: 2.3.99 => 2.3.5 * milestone: => MacPorts 2.4.0 Comment: I've confirmed the problem exists in 2.3.5. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 02:40:13 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 02:40:13 -0000 Subject: [MacPorts] #53181: git @2.11.0: fetch failed on OS X 10.5 ppc and intel In-Reply-To: <046.2a400e8d1ec1a965acc9aeb1e5d1ecb9@macports.org> References: <046.2a400e8d1ec1a965acc9aeb1e5d1ecb9@macports.org> Message-ID: <061.9e6e209ce358c5fb62998090d6724a7a@macports.org> #53181: git @2.11.0: fetch failed on OS X 10.5 ppc and intel ------------------------+--------------------- Reporter: pkoshevoy | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: duplicate | Keywords: leopard Port: git | ------------------------+--------------------- Comment (by pkoshevoy): That helped, thank you! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 02:54:50 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 02:54:50 -0000 Subject: [MacPorts] #53169: PortIndex contains expanded prefix In-Reply-To: <043.c2f960f04c1b7e8f6d401c4b06c1f5a5@macports.org> References: <043.c2f960f04c1b7e8f6d401c4b06c1f5a5@macports.org> Message-ID: <058.a44f813c2b2bbeceb6563c138d22979d@macports.org> #53169: PortIndex contains expanded prefix ---------------------+---------------------------- Reporter: jmroot | Owner: neverpanic Type: defect | Status: closed Priority: Normal | Milestone: MacPorts 2.4.0 Component: base | Version: 2.3.5 Resolution: fixed | Keywords: Port: | ---------------------+---------------------------- Comment (by raimue): Sorry, that was misleading. The problem exists in 2.3.5, but the commit linked earlier was never merged to the release-2.3 branch. I tried to bisect it but the problem was definitely there back in 2.3.0, but earlier releases do not work on macOS 10.12 Sierra. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 05:51:22 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 05:51:22 -0000 Subject: [MacPorts] #53178: php55 @5.5.36: update to 5.5.38 In-Reply-To: <041.2b3adeb402165ddee783bab38bd49f92@macports.org> References: <041.2b3adeb402165ddee783bab38bd49f92@macports.org> Message-ID: <056.3a4f39d60be4f4d3cbfffe6bf33b2a7b@macports.org> #53178: php55 @5.5.36: update to 5.5.38 ---------------------+------------------------ Reporter: l2dy | Owner: ryandesign Type: update | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: php55 | ---------------------+------------------------ Comment (by ryandesign): In [changeset:"3b4aaf7e10b3bfe9b0241022bad0c0cc4588b3d6/macports-ports" 3b4aaf7/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="3b4aaf7e10b3bfe9b0241022bad0c0cc4588b3d6" php: Livecheck all stable versions See: https://trac.macports.org/ticket/53178 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 05:51:23 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 05:51:23 -0000 Subject: [MacPorts] #53178: php55 @5.5.36: update to 5.5.38 In-Reply-To: <041.2b3adeb402165ddee783bab38bd49f92@macports.org> References: <041.2b3adeb402165ddee783bab38bd49f92@macports.org> Message-ID: <056.921c31f6963601f1025e4df0df7e032a@macports.org> #53178: php55 @5.5.36: update to 5.5.38 ---------------------+------------------------ Reporter: l2dy | Owner: ryandesign Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: php55 | ---------------------+------------------------ Changes (by ryandesign): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"7b7707138e9578cdae256cc0aa32c2296694be4f/macports-ports" 7b77071/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="7b7707138e9578cdae256cc0aa32c2296694be4f" php: Update php55 to 5.5.38 Closes: https://trac.macports.org/ticket/53178 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 07:21:46 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 07:21:46 -0000 Subject: [MacPorts] #53182: cctools @895_3 fails to build on OS X 10.5 In-Reply-To: <046.7e4e93468781af56cae41826e3014764@macports.org> References: <046.7e4e93468781af56cae41826e3014764@macports.org> Message-ID: <061.fca46aa5f365638a3e27fb566b1948c2@macports.org> #53182: cctools @895_3 fails to build on OS X 10.5 ------------------------+---------------------- Reporter: pkoshevoy | Owner: jeremyhu Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: leopard Port: cctools | ------------------------+---------------------- Changes (by jeremyhu): * status: assigned => accepted Comment: {{{ $ ls -l /opt/local/var/macports/software/cctools/ total 3832 -rw-r--r-- 1 root admin 3922865 Dec 20 21:45 cctools- 895_3+llvm39+universal.darwin_9.i386-x86_64.tbz2 }}} I suspect the issue is for +llvm33 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 07:57:10 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 07:57:10 -0000 Subject: [MacPorts] #53182: cctools @895_3 fails to build on OS X 10.5 In-Reply-To: <046.7e4e93468781af56cae41826e3014764@macports.org> References: <046.7e4e93468781af56cae41826e3014764@macports.org> Message-ID: <061.4bcc692153e7cd03f6f7ad16dcac20ae@macports.org> #53182: cctools @895_3 fails to build on OS X 10.5 ------------------------+---------------------- Reporter: pkoshevoy | Owner: jeremyhu Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: leopard Port: cctools | ------------------------+---------------------- Comment (by kencu): for a data point {{{ $ port -v installed | grep cctools cctools @886_6+llvm33 platform='darwin 9' archs='i386' cctools @886_6+llvm38+universal-llvm33-llvm34 platform='darwin 9' archs='i386 x86_64' cctools @895_3+llvm39+universal-llvm33-llvm34 (active) platform='darwin 9' archs='i386 ppc x86_64' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 08:13:57 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 08:13:57 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.bebe1ff4e3a2895dcfba936fd50f97d4@macports.org> #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Comment (by mojca): Replying to [comment:21 kencu]: > As you know from our previous posts I've been doing this for months on 10.4 and 10.5 PPC with good success. Isn't that different? My understand has been that you are linking all binaries against libstdc++ shipped by the latest version of GCC rather than linking against the system libstdc++. On PPC it's a problem because clang doesn't quite work correctly yet due to a small number of remaining bugs that need to be fixed first. This is about 10.6-10.8 (10.5 would probably be too optimistic) where one would try to keep using the shipped libstdc++. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 08:22:33 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 08:22:33 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.f400004d1a02595a5e928b46ccc32917@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by mojca): It's easy to get lost in this discussion, I'll try to take more time to go through all of the points later. I hope that one day a special KDE port will no longer be needed. Do I understand correctly that qt5-kde is currently more or less qt5 + a bunch of modifications needed to run KDE apps and there would be no harm if everyone would use that patched version (or even better convince the upstream Qt 5 developers to include those patches and then there would be just a single version remaining anyway)? But we'll certainly need special versions of Qt 5 for different OS versions and this is where we absolutely have to ensure that: * Users don't end up with packages that were built with a different version of Qt (like having 5.5 installed and then installing a binary package that was built against 5.6). * Ports declare dependencies in a proper way, so that the same port will depend on qt55-something on one system and on qt56-something on another without every single port implementing "if this is 10.7, then use qt55-something, if this is 10.8-10.10, use qt56-something, if this is 10.11 or later, use qt57-something". -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 08:36:08 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 08:36:08 -0000 Subject: [MacPorts] #49408: ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590) In-Reply-To: <057.b7594a5a27ae0d95b3620434c8949e61@macports.org> References: <057.b7594a5a27ae0d95b3620434c8949e61@macports.org> Message-ID: <072.e678f83d5989486617ce94ff8b0d6d54@macports.org> #49408: ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590) -------------------------+---------------------------- Reporter: tessarek@… | Owner: jyrkiwahlstedt Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: invalid | Keywords: Port: python27 | -------------------------+---------------------------- Changes (by jyrkiwahlstedt): * status: new => closed * resolution: => invalid Comment: Closing ticket per request -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 09:31:28 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 09:31:28 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.dded8ea68b43999838e92b5944273474@macports.org> #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Comment (by kencu): I'm surprised anyone with 10.6+ would consider anything other than clang-3.7-8-9 and libc++ at this point -- Jeremy has fixed that up very nicely and 10.6 + seems to work great with libc++ for any software I have tried; I have no concerns about using that going forward for all software, and would suggest (IMHO) that macports just default to that forever and be done with it. But that's not up to me. A few last hiccups with some last few build systems like scons persist -- I have personally fixed all those, as you know, by patching clang, but sooner or later macports will get all the portfiles in line for that. 10.5 (and 10.4) are the only issue I have left with cxx11 -- although just tonight I have clang-3.6 installed and compiling c++ software on 10.5 PPC linking against libc++, so I still hold out hope there. In the meantime, tho, 10.5 and 10.4 are where I'm using gcc6. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 10:25:31 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 10:25:31 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.f071457bf1a7fcddc574ec0109cf926b@macports.org> #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Comment (by mojca): Replying to [comment:24 kencu]: > I'm surprised anyone with 10.6+ would consider anything other than clang-3.7-8-9 and libc++ at this point There's a single reason for that: #50448 that's blocking new build slaves from being started. Building everything from source is a bit annoying. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 10:34:29 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 10:34:29 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.095bf74d9e3da046e5af400e8b082d3f@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by RJVB): > Do I understand correctly that qt5-kde is currently more or less qt5 + a bunch of modifications needed to run KDE apps More or less, indeed. There is at least 1 crucial patch (for getting "Linuxy" locations), there are a few patches which improve the experience like by allowing a different platform theme to be loaded automatically. There are also patches being developed upstream that address issues which are more likely to occur in KDE apps (related to using DBus, for instance), plus a number of patches for general little things that either were already in the old qt5-mac port when I started working on it or that come from Debian, and which still apply. There is 1 other big difference, which may or may not be crucial: the installation layout. I've documented this extensively last year. In short, my approach follows Qt's implicit guidelines for installing different versions in parallel as system libraries in the same prefix. The old qtN- mac ports put the shared resources (plugins, mkspecs, etc) under a Linuxy location, /opt/local/share/qtN, and I remember running into issues with KDE4 when I tried to change that. So basically I kept all those old locations which never conflicted between the Qt4 and Qt5 ports, and that includes the CMake modules (as you already found out). I lack the resources to figure out if indeed this difference is crucial and to what extent. The point to keep in mind here is that KDE applications come from the FreeDesktop environment and are designed to interact with others from that same environment. That includes KDE4 and GTk/Gnome apps. Those all use /opt/local/share, so much hunch is that Qt5/KF5 applications best do the same in order to reach their full potential. It can of course be absorbed by using symlinks just as Marcus currently does with the pkgconfig files. As a side-note: that kind of solution to make files appear in the location where they should be just increases filesystem clutter. It's an approach that can make sense if you're installing stuff without registry and you want to keep track of who installs what so you can uninstall/deactivate it with a few simple commands. With a package manager that knows exactly who installs what you can just as well put the actual files in the required location. > and there would be no harm if everyone would use that patched version Indeed, I've always striven to ensure that the port can be used by everyone - I myself also use it for everything. That's one reason why the crucial ("QSP") patch is more complicated than it could be: just applying the patch itself changes nothing in Qt's behaviour. In its current version, software needs to be built with 1 or 2 tokens set in order to activate new feature the patch introduces. That's of course a sine-qua- none for upstreaming the patch, but just as much to me for acceptance into MacPorts. > (or even better convince the upstream Qt 5 developers to include those patches and then there would be just a single version remaining anyway)? Yes. But I am doubtful that we can achieve that. There was momentum and a more or less open mind for the special needs of projects like MacPorts at some point, but that's probably almost 2 years ago by now. That time span and the fact the likes of Fink and HomeBrew haven't waited don't actually support my arguments. Getting patches into Qt is so difficult that there is at least 1 company that lives off it. > * Users don't end up with packages that were built with a different version of Qt (like having 5.5 installed and then installing a binary package that was built against 5.6). Agreed. As discussed elsewhere this can be achieved by using a variant as a label. One or two things could be changed in "base" to streamline this, but it's already possible and this is actually the main thing that variants do in "base" (everything else depends on port-specific implementation). I think that a solution to this point will also address (prevent) potential violations of the reproducible build principle. > * Ports declare dependencies in a proper way, so that the same port will depend on qt55-something on one system and on qt56-something on another without every single port implementing "if this is 10.7, then use qt55-something, if this is 10.8-10.10, use qt56-something, if this is 10.11 or later, use qt57-something". OOPS, before the wrong idea gets in peoples' minds: Qt 5.7 still supports 10.9!! I'm working on upgrading to 5.7.1 as we speak! We'll see about 5.8, but even QtWebEngine 5.7.1 builds and runs fine (with 1 issue & patch I've reported upstream). I guess it will shock no one if `port deps foo-qt5` will return "qt55" on 10.7? But just how shocking is it if that return value depended not simply on OS but also (or instead) on the installed Qt version? I can think of nothing in MacPorts dogma that forbids this explicitly. I also think it's certainly not illogical ("if you have qt55-base installed you should also depend on qt55-whatever if you need the whatever component"). It's even going to be necessary if qt55-* and qt5-* declare mutual conflicts, as they should. Side-note: port:qt5-kde has had support for building Qt 5.3.2 on 10.6 for a long time now. This could and should maybe be moved to a dedicated port by now since KF5 has been requiring later Qt versions for a few iterations now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 14:59:50 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 14:59:50 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.2045ee6120c0a657ddf2eb7059d341a9@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by RJVB): A few more things, inspired by upgrading to 5.7.1 : - qtenginio was deprecated in 5.6 and is removed from 5.7 . I doubt it was ever used but I am keeping its stubport (which will now raise an obsoletion error) - A few new components were added in 5.7: QtCharts QtDatavis3D QtGamepad QtPurchasing QtScxml (no idea yet what the latter does). They're all small when built and only depend on other components in `qt5-kde`, so I am including it in the main port, with stubs. - QtScript is deprecated but still available. KF5 evolves rather quickly and is in a sense a development platform and showcase for new, "Kool" things. I think the only reason why it doesn't yet require Qt 5.7 across the board is because of Qt 5.6's LTS status. I know that many KDE devs are already using preview versions of Qt 5.8, and at least 1 port already requires 5.7. (Not to mention QtWebEngine which works better in 5.7+ than it does in 5.6 .) All this is in line with KDE's history of being a source of APIs that end up being integrated into Qt. This observation is actually an additional argument NOT to integrate the KDE patches with the main `port:qt5` but to keep a dedicated Qt5 port so it become easier for KF5 ports to depend on `port:qt5-kde`, and for me to keep up with the "recommended" minimal Qt version. It is also an argument for something I already hinted at before: the 2nd part of his `qt5.depends_component` proposal {{{ switch -exact ${comp} { qtquickcontrols2 { depends_lib-append path:lib/pkgconfig/Qt5QuickControls2.pc:${qt_port_name} } qtbase { depends_lib-append path:lib/pkgconfig/Qt5Core.pc:${qt_port_name} } # ... } }}} should go into the port-specific PortGroup files, OR do a lookup in tables provided by those PortGroups. Yes, I realise this degrades the ABI compatibility argument. But as explained above: 1 Qt guarantees that you can upgrade Qt from 5.x to 5.y without having to rebuild (except if certain private APIs are used) 2 the autodefault +qt5kde variant prevents getting mismatched binary builds from the bots. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 16:09:59 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 16:09:59 -0000 Subject: [MacPorts] #53118: add nccmp into macports ? In-Reply-To: <043.1244f8056d17c36ca50189d9d0741e3b@macports.org> References: <043.1244f8056d17c36ca50189d9d0741e3b@macports.org> Message-ID: <058.067359afa863529c15b20941917058d8@macports.org> #53118: add nccmp into macports ? ----------------------+----------------- Reporter: basmac | Owner: Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: nccmp | ----------------------+----------------- Comment (by mojca): It is straightforward to create a package for this, but given the current lack of manpower in MP it would be ideal if we would get at least a co- maintainer from the user base even if that user is not a computer programmer. While I can create a port for this, I don't want to spend time testing the functionality and have no idea about needs of real users. We need some volunteer who is willing to be responsible for testing, reporting when something is broken, checking for updates, ... Are you or someone else willing to volunteer for a (co-)maintainer? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 16:13:24 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 16:13:24 -0000 Subject: [MacPorts] #53118: add nccmp into macports ? In-Reply-To: <043.1244f8056d17c36ca50189d9d0741e3b@macports.org> References: <043.1244f8056d17c36ca50189d9d0741e3b@macports.org> Message-ID: <058.8615af84e52d49f33bdf1f26d638f79c@macports.org> #53118: add nccmp into macports ? ----------------------+----------------- Reporter: basmac | Owner: Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: nccmp | ----------------------+----------------- Changes (by mojca): * Attachment "nccmp.Portfile" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 16:14:20 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 16:14:20 -0000 Subject: [MacPorts] #53118: add nccmp into macports ? In-Reply-To: <043.1244f8056d17c36ca50189d9d0741e3b@macports.org> References: <043.1244f8056d17c36ca50189d9d0741e3b@macports.org> Message-ID: <058.49e8c07726ddfad5497518f3bc5ce4d6@macports.org> #53118: add nccmp into macports ? ----------------------+---------------------- Reporter: basmac | Owner: Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: nccmp | ----------------------+---------------------- Changes (by mojca): * keywords: => haspatch Comment: I added a Portfile that is still missing support for reading two header files from NetCDF. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 16:55:32 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 16:55:32 -0000 Subject: [MacPorts] #52568: libgcc build failure In-Reply-To: <064.c913da9da5263151e52d46b719d10ca2@macports.org> References: <064.c913da9da5263151e52d46b719d10ca2@macports.org> Message-ID: <079.119bf00b496f593be1f006dcc7e5e44a@macports.org> #52568: libgcc build failure -----------------------------------+-------------------------------- Reporter: michael.f.corcoran@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: libgcc | -----------------------------------+-------------------------------- Comment (by smithsp): I am going to attach my own main.log, since I am also getting a build error for bootstrap-lean. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 17:00:43 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 17:00:43 -0000 Subject: [MacPorts] #52568: libgcc build failure In-Reply-To: <064.c913da9da5263151e52d46b719d10ca2@macports.org> References: <064.c913da9da5263151e52d46b719d10ca2@macports.org> Message-ID: <079.b5a1c8ccfff4c99fe92c4548ed020226@macports.org> #52568: libgcc build failure -----------------------------------+-------------------------------- Reporter: michael.f.corcoran@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: libgcc | -----------------------------------+-------------------------------- Changes (by smithsp): * Attachment "libgcc_main.log" added. main.log (last 40k lines to not exceed size limit) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 17:04:40 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 17:04:40 -0000 Subject: [MacPorts] #53040: py27-wxpython-3.0 @3.0.2.0 fatal error: 'type_traits' file not found on systems upgraded to libc++ In-Reply-To: <042.60b960fe5a4bb70586997df006b20806@macports.org> References: <042.60b960fe5a4bb70586997df006b20806@macports.org> Message-ID: <057.08a94f4da815c288f176af8abbc709d0@macports.org> #53040: py27-wxpython-3.0 @3.0.2.0 fatal error: 'type_traits' file not found on systems upgraded to libc++ ------------------------------+---------------------- Reporter: kencu | Owner: mojca Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-wxpython-3.0 | ------------------------------+---------------------- Comment (by mojca): The official answer was that we should add `-stdlib=libc++` to `CC`, so that the full compiler name is something like `clang -stdlib=libc++`. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 17:36:24 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 17:36:24 -0000 Subject: [MacPorts] #53070: Update Version of port seqan-apps to 2.2.0 (was: Update Version of port sedan-apps to 2.2.0) In-Reply-To: <042.bb14e5fd4bccf9d3d78441222e2e613b@macports.org> References: <042.bb14e5fd4bccf9d3d78441222e2e613b@macports.org> Message-ID: <057.2d86469aa9e9964866aedf44294d5af8@macports.org> #53070: Update Version of port seqan-apps to 2.2.0 -------------------------+--------------------------------- Reporter: rrahn | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: seqan-apps | -------------------------+--------------------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 19:31:02 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 19:31:02 -0000 Subject: [MacPorts] #53066: Version Update to SeqAn 2.2.0 In-Reply-To: <042.15db684f9fdbe281bd57c709cb6b7b88@macports.org> References: <042.15db684f9fdbe281bd57c709cb6b7b88@macports.org> Message-ID: <057.d966a029de23495629833abf8eacb6fe@macports.org> #53066: Version Update to SeqAn 2.2.0 ---------------------+--------------------------------- Reporter: rrahn | Owner: mf2k Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch maintainer Port: seqan | ---------------------+--------------------------------- Changes (by mf2k): * status: new => closed * owner: => mf2k * resolution: => fixed Comment: In [changeset:"8aa9a0b2985896279689c2afccff648c8af46f0a/macports-ports" 8aa9a0b/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="8aa9a0b2985896279689c2afccff648c8af46f0a" Merge branch 'seqan_update' seqan: Update to version 2.2.0 seqan-apps: Update to version 2.2.0 Closes: https://trac.macports.org/ticket/53066 Closes: https://trac.macports.org/ticket/53070 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 19:31:02 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 19:31:02 -0000 Subject: [MacPorts] #53070: Update Version of port seqan-apps to 2.2.0 In-Reply-To: <042.bb14e5fd4bccf9d3d78441222e2e613b@macports.org> References: <042.bb14e5fd4bccf9d3d78441222e2e613b@macports.org> Message-ID: <057.ed6bc8d396242f03c922b56aa01c6d09@macports.org> #53070: Update Version of port seqan-apps to 2.2.0 -------------------------+--------------------------------- Reporter: rrahn | Owner: mf2k Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch maintainer Port: seqan-apps | -------------------------+--------------------------------- Changes (by mf2k): * status: new => closed * owner: => mf2k * resolution: => fixed Comment: In [changeset:"8aa9a0b2985896279689c2afccff648c8af46f0a/macports-ports" 8aa9a0b/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="8aa9a0b2985896279689c2afccff648c8af46f0a" Merge branch 'seqan_update' seqan: Update to version 2.2.0 seqan-apps: Update to version 2.2.0 Closes: https://trac.macports.org/ticket/53066 Closes: https://trac.macports.org/ticket/53070 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 20:40:14 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 20:40:14 -0000 Subject: [MacPorts] #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X In-Reply-To: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> References: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> Message-ID: <061.777875ad43325ae0a26503e1e6307da5@macports.org> #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X ------------------------+--------------------------- Reporter: ballapete | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: tiger powerpc Port: libuv | ------------------------+--------------------------- Comment (by michaelld): In [changeset:"1d68d187ac75a8013661d2a6489e5ff75b554fe4/macports-ports" 1d68d187/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="1d68d187ac75a8013661d2a6489e5ff75b554fe4" cmake: on Tiger (10.4), just use cmake internal system libraries, since those provided by the system and/or macPorts do not build or work as desired. Partly addresses ticket https://trac.macports.org/ticket/53143 . }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 20:41:15 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 20:41:15 -0000 Subject: [MacPorts] #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X In-Reply-To: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> References: <046.cb3f767d7e165e4fefb37dadaa852fe3@macports.org> Message-ID: <061.ca41fa67950cd834622079ada71698d6@macports.org> #53143: libuv @1.10.1 does not build on PPC Tiger, Mac OS X ------------------------+--------------------------- Reporter: ballapete | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: tiger powerpc Port: libuv | ------------------------+--------------------------- Comment (by michaelld): I've integrated Ken's patch. Does that fix this ticket? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 21:55:01 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 21:55:01 -0000 Subject: [MacPorts] #53184: A cxx11-compatible clang compiler on 10.5 PPC ?Some progress... Message-ID: <042.6019e737e4e7617d7289c2f8e9868bfa@macports.org> #53184: A cxx11-compatible clang compiler on 10.5 PPC ?Some progress... -------------------------+----------------- Reporter: kencu | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: leopard PPC | Port: -------------------------+----------------- We have been trying for a while now to get a current version of clang working on 10.5 - specifically PPC - and this ticket is keep a log of successes and failures in this regard. Jeremy's recent 10.5 fixes have enabled 10.5 Intel to have a working version of libc++ and clang-3.7 that can cross-compile simple PPC apps. I have had some success with clang-3.6 on 10.5 PPC, so I thought I would document how that worked in case anyone would like to try it, or alternatively has some ideas how to better test it and/or improve the situation. When I tried, I could not build libcxx on PPC with clang-3.4, but it does (as Jeremy documents) build with clang-3.4 on 10.5 Intel with PPC slices. I copied the following files built on the 10.5 Intel system {{{ libcxx-3.9.0_0+universal.darwin_9.i386-ppc-x86_64.tbz2 libcxxabi-3.9.0_0+universal.darwin_9.i386-ppc-x86_64.tbz2 libffi-3.2.1_0+universal.darwin_9.i386-ppc-x86_64.tbz2 libmacho-886_0+universal.darwin_9.i386-ppc-x86_64.tbz2 libedit-20160618-3.1_1+universal.darwin_9.i386-ppc-x86_64.tbz2 libunwind-3.9.0_3+universal.darwin_9.i386-ppc-x86_64.tbz2 libunwind-headers-3.9.0_0.darwin_9.noarch.tbz2 ncurses-6.0_0+universal.darwin_9.i386-ppc-x86_64.tbz2 }}} over to a 10.5 PPC machine, placing them into `/opt/local/var/macports/incoming/verified`, and then installed each one like this: {{{ sudo port -v install PORTNAME +universal universal_arches="i386 ppc x86_64" supported_arches="i386 ppc x86_64" }}} I believe that was the full list of cross-compiled files that I had to move over. Next, I tried to cross-compile clang-3.7 and clang-3.8 with ppc slices. LLVM-3.7 and 3.8 did build with ppc slices, but they segfault when moved to the 10.5 ppc machine with what appears to be an error in the address lookup for strlen(). Neither clang-3.7 nor clang-3.8 would cross-compile on 10.5 Intel, in each case delivering up `error 12` during the link phase. Whether or not that can be overcome is to be discovered. Back to the 10.5 PPC machine, clang-3.4 proved to be quite touchy compiling software, however with some modifications as below, it would compile llvm/clang-3.6 through to completion. adding this to the clang-3.6 portfile {{{ configure.cflags-append -fPIE configure.cxxflags-append -fPIE configure.ldflags-append -fPIE -nodefaultlibs -lc++ -lc++abi -lgcc_s.10.5 configure.ldflags-append -lSystem and editing this to include ppc supported_archs i386 x86_64 ppc }}} updating macports.conf as usual {{{ cxx_stdlib libc++ buildfromsurce always delete_la_files yes default_compilers macports-clang-3.4 gcc-4.2 }}} and installing clang-3.6 did go through to completion. {{{ clang-3.6 @3.6.2_5+analyzer (active) platform='darwin 9' archs='ppc' llvm-3.6 @3.6.2_4 (active) platform='darwin 9' archs='ppc' }}} clang-3.6 appears to work correctly {{{ $ clang --version clang version 3.6.2 (tags/RELEASE_362/final) Target: powerpc-apple-darwin9.8.0 Thread model: posix }}} and the llvm-binaries don't segfault (like the cross-compiled ones did) {{{ $ /opt/local/bin/llvm-tblgen-mp-3.6 --version LLVM (http://llvm.org/): LLVM version 3.6.2 Optimized build. Built Dec 29 2016 (18:30:54). Default target: powerpc-apple-darwin9.8.0 Host CPU: 970 }}} and so far simple apps build and link against libc++ {{{ $ helloworld Hello World! $ otool -L /opt/local/bin/helloworld /opt/local/bin/helloworld: /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 3.9.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.1.7) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 697.0.0) /usr/lib/libc++abi.dylib (compatibility version 1.0.0, current version 3.9.0) }}} and a few more complex apps also build and run {{{ $ otool -L /opt/local/bin/nzbget /opt/local/bin/nzbget: /opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.8) /opt/local/lib/libgnutls.30.dylib (compatibility version 37.0.0, current version 37.8.0) /opt/local/lib/libncurses.6.dylib (compatibility version 6.0.0, current version 6.0.0) /opt/local/lib/libxml2.2.dylib (compatibility version 12.0.0, current version 12.4.0) /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 3.9.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.1.7) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 697.0.0) /usr/lib/libc++abi.dylib (compatibility version 1.0.0, current version 3.9.0) $ nzbget --version nzbget version: 14.1 }}} at this time, clang-3.7 / llvm-3.7 will not build through on 10.5 PPC, and the cross-compiled llvm-3.7 segfaults on PPC. Hope this helps someone. K -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 23:16:28 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 23:16:28 -0000 Subject: [MacPorts] #53156: upgrade: port:Vc In-Reply-To: <041.3dc6daddf4253f7a98698f2f7d4f54ae@macports.org> References: <041.3dc6daddf4253f7a98698f2f7d4f54ae@macports.org> Message-ID: <056.dadd993740c6ac205f5315b2a1b5320b@macports.org> #53156: upgrade: port:Vc ---------------------+---------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: Vc | ---------------------+---------------------- Comment (by mkae): Is this about {{{ installs_libs no }}} ? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 23:22:16 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 23:22:16 -0000 Subject: [MacPorts] #53062: poppler fails to install In-Reply-To: <046.c8fa858c3409aff55975ac5519c0f676@macports.org> References: <046.c8fa858c3409aff55975ac5519c0f676@macports.org> Message-ID: <061.3f1a6b413552b8b5314745c9297373fe@macports.org> #53062: poppler fails to install -------------------------+--------------------- Reporter: william76 | Owner: dbevans Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: worksforme | Keywords: Port: poppler | -------------------------+--------------------- Comment (by mkae): Any update on this? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 23:32:11 2016 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2016 23:32:11 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.919fa240a7486fc1c39d03e4503842ec@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by mkae): Replying to [comment:24 mojca]: > It's easy to get lost in this discussion, Yes, I'm already lost in this and wonder which way we could and should go now... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 00:07:15 2016 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2016 00:07:15 -0000 Subject: [MacPorts] #53156: upgrade: port:Vc In-Reply-To: <041.3dc6daddf4253f7a98698f2f7d4f54ae@macports.org> References: <041.3dc6daddf4253f7a98698f2f7d4f54ae@macports.org> Message-ID: <056.3148a5ad802d4f6d58ad78691cabbcf1@macports.org> #53156: upgrade: port:Vc ---------------------+---------------------- Reporter: RJVB | Owner: Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: Vc | ---------------------+---------------------- Comment (by RJVB): yes -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 10:35:44 2016 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2016 10:35:44 -0000 Subject: [MacPorts] #52005: postgresql95-server should be marked noarch In-Reply-To: <047.75fb6908f279ae336cb051fdadafe961@macports.org> References: <047.75fb6908f279ae336cb051fdadafe961@macports.org> Message-ID: <062.2622f3f6821bcfe498ad6025507e61cb@macports.org> #52005: postgresql95-server should be marked noarch -------------------------------------------------+------------------------- Reporter: ryandesign | Owner: | jyrkiwahlstedt Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: postgresql80-server | postgresql81-server postgresql82-server | postgresql83-server postgresql84-server | postgresql90-server postgresql91-server | postgresql92-server postgresql93-server | postgresql94-server postgresql95-server | postgresql96-server | -------------------------------------------------+------------------------- Changes (by jyrkiwahlstedt): * status: new => closed * resolution: => fixed Comment: In [changeset:"254a189a5561f7ada73b83b91dc3936d0a4cb904/macports-ports" 254a189a/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="254a189a5561f7ada73b83b91dc3936d0a4cb904" postgresql9.-server: add noarch Closes: https://trac.macports.org/ticket/52005 (didn't modify EOL'd) }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 17:22:33 2016 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2016 17:22:33 -0000 Subject: [MacPorts] #51801: qt5: support older versions of OS X via different versions of Qt 5 In-Reply-To: <044.c67ff530149c88540d9051bfc53ecb16@macports.org> References: <044.c67ff530149c88540d9051bfc53ecb16@macports.org> Message-ID: <059.5a0d0f21430d025425860ae62b6b4026@macports.org> #51801: qt5: support older versions of OS X via different versions of Qt 5 --------------------------+--------------------------------- Reporter: dliessi | Owner: MarcusCalhoun-Lopez Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5 | --------------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): In [changeset:"777e827bebeb02b2d4c04e66295f0cf63921e807/macports-ports" 777e827b/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="777e827bebeb02b2d4c04e66295f0cf63921e807" qt5 PG: remove references to supported versions A better mechanism must be found for providing this information. see https://trac.macports.org/ticket/51801 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 17:27:26 2016 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2016 17:27:26 -0000 Subject: [MacPorts] #53185: ghc does not compile Message-ID: <042.43ef9f8aa8e2bf33a6d3f53ecfa13612@macports.org> #53185: ghc does not compile --------------------+------------------- Reporter: neilt | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Keywords: | Port: ghc --------------------+------------------- {{{ sudo port install ghc ---> Attempting to fetch ghc-7.8.3_4.darwin_16.x86_64.tbz2 from http://sea.us.packages.macports.org/macports/packages/ghc ---> Attempting to fetch ghc-7.8.3_4.darwin_16.x86_64.tbz2 from http://lil.fr.packages.macports.org/ghc ---> Fetching distfiles for ghc ---> Verifying checksums for ghc ---> Extracting ghc ---> Applying patches to ghc ---> Configuring ghc ---> Building ghc Error: org.macports.build for port ghc returned: command execution failed Please see the log file for port ghc for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_ghc/ghc/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port ghc failed }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 17:28:20 2016 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2016 17:28:20 -0000 Subject: [MacPorts] #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 In-Reply-To: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> References: <042.f778082097c12a41e9aed8e84edb51b8@macports.org> Message-ID: <057.d17c70215ee6b40a2664ab95ca590f40@macports.org> #53044: octave @4.2.0_1: requires C++11, does not build correctly on default setups on < 10.9 ---------------------+--------------------------------- Reporter: mojca | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: snowleopard lion Port: octave | ---------------------+--------------------------------- Changes (by MarcusCalhoun-Lopez): * status: new => closed * resolution: => fixed Comment: As far as I can tell, this is fixed.[[BR]] Please feel free to reopen if new problems crop up. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 17:29:14 2016 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2016 17:29:14 -0000 Subject: [MacPorts] #53185: ghc does not compile In-Reply-To: <042.43ef9f8aa8e2bf33a6d3f53ecfa13612@macports.org> References: <042.43ef9f8aa8e2bf33a6d3f53ecfa13612@macports.org> Message-ID: <057.a88115d9fc106de4c3aa18023c755b1d@macports.org> #53185: ghc does not compile ---------------------+------------------- Reporter: neilt | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: ghc | ---------------------+------------------- Changes (by neilt): * Attachment "main.log" added. Complile error log file. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 17:45:20 2016 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2016 17:45:20 -0000 Subject: [MacPorts] #53185: ghc does not compile In-Reply-To: <042.43ef9f8aa8e2bf33a6d3f53ecfa13612@macports.org> References: <042.43ef9f8aa8e2bf33a6d3f53ecfa13612@macports.org> Message-ID: <057.f755d4dac9f7ad680662926a19350723@macports.org> #53185: ghc does not compile ---------------------+------------------- Reporter: neilt | Owner: Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: | Keywords: Port: ghc | ---------------------+------------------- Comment (by neilt): Forgot {{{ Darwin MBP.localdomain 16.3.0 Darwin Kernel Version 16.3.0: Thu Nov 17 20:23:58 PST 2016; root:xnu-3789.31.2~1/RELEASE_X86_64 x86_64 ProductName: Mac OS X ProductVersion: 10.12.2 BuildVersion: 16C67 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 17:49:13 2016 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2016 17:49:13 -0000 Subject: [MacPorts] #53186: qmake5 should change destroot.destdir (qmake PG idem) Message-ID: <041.8dec9c7fe17895934be7037ceda0c266@macports.org> #53186: qmake5 should change destroot.destdir (qmake PG idem) -------------------------+--------------------- Reporter: RJVB | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: qt5 qt4 -------------------------+--------------------- I think the qmake portgroups should include a statement like {{{ destroot.destdir "INSTALL_ROOT=${destroot}" }}} I had already observed this but now got confirmation on a Qt ML that this is indeed the official way to do a destroot'ed install. Using the default (`DESTDIR=${destroot}`) mostly works, but can have undesirable side-effects: {{{ > ls -l `port work qt5-kde-devel-qtwebengine` drwxr-xr-x  8 bertin admin 612 Dec  2 12:18 qtwebengine-opensource- src-5.7.1 drwxr-xr-x 11 bertin admin 510 Dec 31 01:44 build drwxr-xr-x  3 bertin admin 136 Dec 31 11:59 destrootQtWebEngineCore.framework drwxr-xr-x  3 bertin admin 136 Dec 31 11:59 destrootQtWebEngine.framework drwxr-xr-x  3 bertin admin 136 Dec 31 11:59 destrootQtWebEngineWidgets.framework drwxr-xr-x  3 bertin admin 102 Dec 31 11:59 destroot }}} Same thing happens for me with QtWebKit. The end result seems to be fine, but there's no guarantee that this will continue to be the case. A number of Qt5-dependent ports make this change themselves, that shouldn't be necessary, ideally. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 18:30:47 2016 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2016 18:30:47 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.28f1304f8e02c45b3514c12df019389c@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by MarcusCalhoun-Lopez): Replying to [comment:27 mkae]: > Replying to [comment:24 mojca]: > > It's easy to get lost in this discussion, > > Yes, I'm already lost in this and wonder which way we could and should go now... I am sorry about losing people in this discussion.[[BR]] Hopefully, we can find our way forward.[[BR]] Attached is a patch that attempts to satisfy most concerns. * qt5 PG provides qt5kde variant (unless Portfile opts out). * if qt5kde is selected, qt5-kde is **required** * if qt5kde is not selected * path dependency on Qt component is used so qt5-kde could still satisfy dependency * default Qt port (qt55, q56, or qt5) is determined by values `os.major` and `cxx_stdlib` * if installed Qt is different than the default, a warning is given * Only one Qt installation is possible at a given time * qt5-qtbase, qt56-qtbase, and qt5-kde all conflict with each other. * every Qt component (e.g. qt5*-qtmultimedia) explicitly depends on qt5*-qtbase (**not** a path dependency) If there are no objections, I will commit the change, and we can proceed on other fronts. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 18:31:08 2016 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2016 18:31:08 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.89ac52d0561a3ea5d709669e464d956b@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Changes (by MarcusCalhoun-Lopez): * Attachment "qt5-1.0.tcl.2.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 18:35:47 2016 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2016 18:35:47 -0000 Subject: [MacPorts] #53186: qmake5 should change destroot.destdir (qmake PG idem) In-Reply-To: <041.8dec9c7fe17895934be7037ceda0c266@macports.org> References: <041.8dec9c7fe17895934be7037ceda0c266@macports.org> Message-ID: <056.6aa954e506c572113d95ff270a135894@macports.org> #53186: qmake5 should change destroot.destdir (qmake PG idem) --------------------------+----------------- Reporter: RJVB | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5 qt4 | --------------------------+----------------- Comment (by MarcusCalhoun-Lopez): The qt5 PortGroup has the code `destroot.env-append INSTALL_ROOT=${destroot}`.[[BR]] Is there any reason to think that this is insufficient? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 18:50:32 2016 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2016 18:50:32 -0000 Subject: [MacPorts] #53186: qmake5 should change destroot.destdir (qmake PG idem) In-Reply-To: <041.8dec9c7fe17895934be7037ceda0c266@macports.org> References: <041.8dec9c7fe17895934be7037ceda0c266@macports.org> Message-ID: <056.1507ea72565f8fae929ae4b4aa3898ff@macports.org> #53186: qmake5 should change destroot.destdir (qmake PG idem) --------------------------+----------------- Reporter: RJVB | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5 qt4 | --------------------------+----------------- Comment (by RJVB): The above observations and the instructions on the Qt interest ML ... I'm waiting for a QtWebKit build to finish to see if adding the variable on the commandline makes a difference. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 19:11:34 2016 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2016 19:11:34 -0000 Subject: [MacPorts] #52582: ghc @7.8.3_4: RTS incompatibility with Sierra In-Reply-To: <047.31ef8be7dd7559a12bcd7c2b768f2d94@macports.org> References: <047.31ef8be7dd7559a12bcd7c2b768f2d94@macports.org> Message-ID: <062.60a4c0b2faeae9bb2b1c1d9f55ca18cc@macports.org> #52582: ghc @7.8.3_4: RTS incompatibility with Sierra -------------------------+----------------------------- Reporter: shanemikel | Owner: neverpanic Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: sierra haspatch Port: ghc | -------------------------+----------------------------- Changes (by ryandesign): * cc: neilt (added) Comment: Has duplicate #53185. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 19:11:37 2016 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2016 19:11:37 -0000 Subject: [MacPorts] #53185: ghc does not compile In-Reply-To: <042.43ef9f8aa8e2bf33a6d3f53ecfa13612@macports.org> References: <042.43ef9f8aa8e2bf33a6d3f53ecfa13612@macports.org> Message-ID: <057.2f9fbab3ca4f5729b5d9373aba907a70@macports.org> #53185: ghc does not compile ------------------------+-------------------- Reporter: neilt | Owner: Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: duplicate | Keywords: sierra Port: ghc | ------------------------+-------------------- Changes (by ryandesign): * keywords: => sierra * status: new => closed * resolution: => duplicate Comment: Duplicate of #52582. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 19:12:32 2016 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2016 19:12:32 -0000 Subject: [MacPorts] #52991: Error upon installing the GHC In-Reply-To: <046.0310b609922306b86c4cc90415e2c8d2@macports.org> References: <046.0310b609922306b86c4cc90415e2c8d2@macports.org> Message-ID: <061.9294396df859548f6456440ff7334899@macports.org> #52991: Error upon installing the GHC ------------------------+------------------------ Reporter: DennyBeck | Owner: neverpanic Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ghc | ------------------------+------------------------ Comment (by ryandesign): DennyBeck, please attach the main.log. We cannot make progress on this issue without seeing the output recorded in the log. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 19:13:06 2016 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2016 19:13:06 -0000 Subject: [MacPorts] #51619: qt5.depends_component procedure In-Reply-To: <041.d00f8f306f54179195096ddec28d445f@macports.org> References: <041.d00f8f306f54179195096ddec28d445f@macports.org> Message-ID: <056.24d9f38318b784375fbf76e10c885c88@macports.org> #51619: qt5.depends_component procedure ---------------------------+---------------------- Reporter: RJVB | Owner: mkae Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5, qt5-kde | ---------------------------+---------------------- Comment (by RJVB): I wouldn't commit anything just yet, in any event I won't have an occasion to take a detailed look until Monday. OTOH, if this is just to introduce qt5.depends_component and you don't mind making adjustments later, then fine. There will be more commits on the PortGroup level anyway, including for instance a mechanism by which (KF5) ports can express a preference for qt5-kde . There is discussion going on on the devel ML ("Re: port:libressl vs port:openssl, path-style variants and prebuilt binaries") which evokes among other things the idea of adaptive depspecs. You should have seen it, and that Mojca is apparently rather on the same page as I am concerning the depspecs and (automatic) variant. > qt5 PG provides qt5kde variant (unless Portfile opts out). Doesn't that means you can no longer prevent installing with qt5-kde installed? No variant provided means you cannot NOT set it and that seems counterproductive (opting out seems of interest only as a way to say "I don't work with that port"). > if qt5kde is not selected > > path dependency on Qt component is used so qt5-kde could still satisfy dependency If that's not done with adaptive depspecs I will have to rectify that in the KF5 PG, idem with the preference mechanism. That'd be a shame, for functionality that should be provided at the Qt5 PG level. > every Qt component (e.g. qt5*-qtmultimedia) explicitly depends on qt5*-qtbase (not a path dependency) Not the qt5-kde-* ports; those evidently depend on qt5-kde (including the stub qt5-kde-qtbase port). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 20:14:40 2016 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2016 20:14:40 -0000 Subject: [MacPorts] #53062: poppler fails to install In-Reply-To: <046.c8fa858c3409aff55975ac5519c0f676@macports.org> References: <046.c8fa858c3409aff55975ac5519c0f676@macports.org> Message-ID: <061.4e92a954ff11b92a3da51ac7975addf5@macports.org> #53062: poppler fails to install -------------------------+--------------------- Reporter: william76 | Owner: dbevans Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: worksforme | Keywords: Port: poppler | -------------------------+--------------------- Comment (by dbevans): Current poppler distfile poppler-0.50.0.tar.xz is fetchible via the MacPorts distfile mirrors as well as the upstream download location. I don't know whether this means the distfile mirroring is working automatically now or whether this was done manually (as in some other tickets). At any rate, the issue should be moot now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 21:23:54 2016 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2016 21:23:54 -0000 Subject: [MacPorts] #53062: poppler fails to install In-Reply-To: <046.c8fa858c3409aff55975ac5519c0f676@macports.org> References: <046.c8fa858c3409aff55975ac5519c0f676@macports.org> Message-ID: <061.9c171c57ca7fdb51738992810fed6150@macports.org> #53062: poppler fails to install -------------------------+--------------------- Reporter: william76 | Owner: dbevans Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: worksforme | Keywords: Port: poppler | -------------------------+--------------------- Comment (by ryandesign): I added the poppler distfile manually. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 21:51:32 2016 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2016 21:51:32 -0000 Subject: [MacPorts] #53186: qmake5 should change destroot.destdir (qmake PG idem) In-Reply-To: <041.8dec9c7fe17895934be7037ceda0c266@macports.org> References: <041.8dec9c7fe17895934be7037ceda0c266@macports.org> Message-ID: <056.c5af8fe3c4ea3e40669d9a124e795f18@macports.org> #53186: qmake5 should change destroot.destdir (qmake PG idem) --------------------------+----------------- Reporter: RJVB | Owner: Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5 qt4 | --------------------------+----------------- Comment (by RJVB): Replying to [comment:2 RJVB]: > I'm waiting for a QtWebKit build to finish to see if adding the variable on the commandline makes a difference. That was a Linux build, and well, evidently I cannot reproduce the issue there with the 5.7.1 QtWebKit version. Either way, whether or not setting INSTALL_ROOT in the *environment* is enough to obtain the intended behaviour is one thing. Setting DESTDIR via the command line *in addition* is another thing, and in principle not a good idea since that variable *is* used in the Makefiles generated by QMake. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 22:16:59 2016 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2016 22:16:59 -0000 Subject: [MacPorts] #53182: cctools @895_3 fails to build on OS X 10.5 In-Reply-To: <046.7e4e93468781af56cae41826e3014764@macports.org> References: <046.7e4e93468781af56cae41826e3014764@macports.org> Message-ID: <061.1aad6a8e965aabb312e164fd642f1e56@macports.org> #53182: cctools @895_3 fails to build on OS X 10.5 ------------------------+---------------------- Reporter: pkoshevoy | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.5 Resolution: fixed | Keywords: leopard Port: cctools | ------------------------+---------------------- Changes (by jeremyhu): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"373d97e83fa33a2aff43914212dc2521667a6811/macports-ports" 373d97e8/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="373d97e83fa33a2aff43914212dc2521667a6811" cctools: Remove +llvm33 variant This removes support for LTO by default on Leopard. Leopard users can reinstall with +llvm34 (or higher) to get back LTO support. Fixes https://trac.macports.org/ticket/53182 Signed-off-by: Jeremy Huddleston Sequoia }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 22:19:38 2016 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2016 22:19:38 -0000 Subject: [MacPorts] #52091: cctools, ld64: Removing +llvm33 variant introduces circular dependencies on Leopard due to llvm-3.4 failing to build with Xcode 3.1's gcc In-Reply-To: <047.5a82f417920a2b6c34e18b2fcd0f544e@macports.org> References: <047.5a82f417920a2b6c34e18b2fcd0f544e@macports.org> Message-ID: <062.318c9fe5ff53b1ff66eb9580b8125858@macports.org> #52091: cctools, ld64: Removing +llvm33 variant introduces circular dependencies on Leopard due to llvm-3.4 failing to build with Xcode 3.1's gcc ----------------------------+---------------------- Reporter: ryandesign | Owner: jeremyhu Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: leopard Port: cctools, ld64 | ----------------------------+---------------------- Comment (by jeremyhu): cctools removed the +llvm33 variant in [changeset:"373d97e83fa33a2aff43914212dc2521667a6811/macports-ports" 373d97e8/macports-ports] in a way that should not make this be a problem (essentially dropping support for LTO on Leopard by default). -- Ticket URL: MacPorts Ports system for macOS