Re: [macports-ports] branch master updated: darktable: update to 2.2.3

2017-02-23 Thread Ryan Schmidt
> On Feb 23, 2017, at 10:48, Craig Treleaven wrote: > > Craig Treleaven (ctreleaven) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/4606c62b254f469098fe72805b99c13e81ec1839 > > The following

Re: [macports-ports] branch master updated: hackrf: move current to devel & add release.

2017-02-23 Thread Ryan Schmidt
> On Feb 23, 2017, at 07:25, Michael Dickens wrote: > > Michael Dickens (michaelld) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/b566db2c16035d568261b863c73b0fb795aa7eab > > The following

Re: Resolving pull request conflicts

2017-02-23 Thread Clemens Lang
Hi Ryan, - On 23 Feb, 2017, at 12:04, Ryan Schmidt ryandes...@macports.org wrote: > GitHub said the pull request had a conflict. (The PR is a version update, but > a > revbump was committed to the port in the meantime.) GitHub said I could > resolve > the conflict on the command line or in

Re: Resolving pull request conflicts

2017-02-23 Thread Mojca Miklavec
On 23 February 2017 at 12:04, Ryan Schmidt wrote: > > GitHub said the pull request had a conflict. (The PR is a version update, but > a revbump was committed to the port in the meantime.) GitHub said I could > resolve the conflict on the command line or in a web-based editor. There was > a

Re: Resolving pull request conflicts

2017-02-23 Thread Ryan Schmidt
On Feb 23, 2017, at 04:46, Mojca Miklavec wrote: > > Dear Ryan, > > On 23 February 2017 at 11:19, Ryan Schmidt wrote: >> Browsing pull requests, I found this one: >> >> https://github.com/macports/macports-ports/pull/305 >> >> Another commit had happened to that port in

Re: Resolving pull request conflicts

2017-02-23 Thread Mojca Miklavec
Dear Ryan, On 23 February 2017 at 11:19, Ryan Schmidt wrote: > Browsing pull requests, I found this one: > > https://github.com/macports/macports-ports/pull/305 > > Another commit had happened to that port in the mean time, so the PR now had > conflicts and could not be applied as-is. GitHub

cxx11-1.1 & gcc

2017-02-23 Thread Mojca Miklavec
Dear Marcus, After you did the changes in cmake 1.1 I discovered the following in your port: # see https://lists.gnu.org/archive/html/octave-maintainers/2016-05/msg00286.html #PortGroup cxx11 1.0 # Octave requires c++-11 but can not use cxx11 PortGroup because Octave also #

Re: [macports-ports] branch master updated: aqua/x2goclient: update to 4.1.0.0.

2017-02-23 Thread Ryan Schmidt
> On Feb 23, 2017, at 02:56, Mihai Moldovan wrote: > > Mihai Moldovan (Ionic) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/5ef7d72e34586081b904c15830ec70741f758566 > > The following commit(s) were

Resolving pull request conflicts

2017-02-23 Thread Ryan Schmidt
Browsing pull requests, I found this one: https://github.com/macports/macports-ports/pull/305 Another commit had happened to that port in the mean time, so the PR now had conflicts and could not be applied as-is. GitHub invited me to edit the file on the web to resolve the conflict, so I did.

Re: No email from the buildbot

2017-02-23 Thread Mojca Miklavec
Dear Joshua & Ryan, On 22 February 2017 at 13:00, Joshua Root wrote: > On 2017-2-22 20:41 , Mojca Miklavec wrote: >> >> Does anyone understand why there was no email sent from the buildbot >> for this failure? >> >> https://build.macports.org/builders/ports-10.12_x86_64-watcher/builds/3808 > > Is

Request to review rpcgen

2017-02-23 Thread Mojca Miklavec
Hi, I would like to ask for help with this: https://github.com/macports/macports-ports/pull/270 Apple already ships rpcgen, but it lacks an important flag to make the generated code thread-safe and I need that flag to package other software. The software seems "abandoned", but FreeBSD keeps