Re: PRs

On May 19, 2019, at 18:14, Mark Anderson wrote: > > Using our own buildbot servers would be pretty cool, where are they hosted? > And they go pretty far back, don't they. The buildbot servers are at my house. I currently have 4 Xserves running VMware ESXi. One is the buildmaster and the othe

Re: PRs

I got the feeling Travis was on it's way out - maybe I'll dig into Azure Pipelines to see what can be done with them, I've been meaning to anyway for myself. Using our own buildbot servers would be pretty cool, where are they hosted? And they go pretty far back, don't they. I've been taking a lot

Re: PRs

On Mon, 20 May 2019 at 00:05, Mark Anderson wrote: > > Yeah. I don’t like that really. I’ll live with it. I think I can trigger from > Travis, if I want to. > > Are we looking to move over to azure pipelines permanently or do we want to > try and see what can be done on the Travis side. Personal

Re: PRs

Yeah. I don’t like that really. I’ll live with it. I think I can trigger from Travis, if I want to. Are we looking to move over to azure pipelines permanently or do we want to try and see what can be done on the Travis side. I’m hoping the first WWDC I’ve missed in 4 years will reveal some kind o

Re: PRs

If you have commit access to MacPorts and the pull request author allows it , you can rebase their fork's branch (for example, with git commit --amend --no-edit) and trigger a new CI build. I’d ask

Re: PRs

Ok, I thought it was already. But I’m not sure it’s working. Or my maintainer math is off. On Sun, May 19, 2019 at 5:32 PM Rainer Müller wrote: > On 19.05.19 20:40, Mark Anderson wrote: > > Who is currently working on out CI/CD stuff like Travis, etc? And where > > is it? There are some things

Re: PRs

On 19.05.19 20:40, Mark Anderson wrote: > Who is currently working on out CI/CD stuff like Travis, etc? And where > is it? There are some things I'd like to propose/do, like making the > maintainer timeout label automatic and making it possible to re-run CI > from GitHub commits. The bot is mainta

Re: PRs

On 19.05.19 20:45, Christopher Chavez wrote: > On 5/19/2019 1:40 PM, Mark Anderson wrote: >> making it possible to re-run CI from GitHub commits. > > As a PR submitter, one workaround I'm aware of is rebasing the PR > commit(s). I'm not sure that's something members can/should try though, > so a b

Re: virtualbox mojave fix

Yeah here too. Going to be super important once 10.15 comes out and 32-bit is verboten. On Sun, May 19, 2019 at 3:00 PM Ken Cunningham < ken.cunningham.web...@gmail.com> wrote: > Oh, it would be great if I read that backwards, as I use VBox mostly for > the 32bit guests. > > Thanks, > > Ken > >

Re: virtualbox mojave fix

Oh, it would be great if I read that backwards, as I use VBox mostly for the 32bit guests. Thanks, Ken > On May 19, 2019, at 10:01 AM, Joshua Root wrote: > > On 2019-5-19 16:20 , Ken Cunningham wrote: >> BTW, VB 5.x is the last that supports 32 bit OS client versions, so if >> you upgrade t

Re: PRs

Yeah, we can pull all sorts of dirty tricks to get things to fire, but typically the best choice is adding comment or something that will refire the builds. Maybe it'd have to check that it's a commiter or the author to avoid someone spaming our CI stack. I'm also wondering if we can plead with Tra

Re: PRs

On 5/19/2019 1:40 PM, Mark Anderson wrote: making it possible to re-run CI from GitHub commits. As a PR submitter, one workaround I'm aware of is rebasing the PR commit(s). I'm not sure that's something members can/should try though, so a better solution is probably still preferred…

PRs

So I just looked at our PRs, and we have 47 outstanding with the oldest being 245 days. I'd like to help out. I'm going to go make a bunch of comments, and merge uncontroversial ones. I don't know the standard when there is a bit of a thing going on in the PR, but has been quiet for a while. Should

Re: virtualbox mojave fix

On 2019-5-19 16:20 , Ken Cunningham wrote: > BTW, VB 5.x is the last that supports 32 bit OS client versions, so if > you upgrade to VB 6.x then you lose those VMs. To be clear, 32-bit *hosts* (the OS that you run on your actual hardware, which VirtualBox runs under) are no longer supported in 6.x

Advice for Boost CMake scripts

We're working on updating Boost to 1.70.0 < https://github.com/macports/macports-ports/pull/4243 > ... we'd value others participating, BTW! Thus far many ports work out of the box with it (current Boost in MacPorts is 1.66.0, so there are some significant bug fixes and API changes to deal with