Re: [macports-infrastructure] 02/02: buildbot: Update status on GitHub after each build

2018-03-13 Thread Mojca Miklavec
On 13 March 2018 at 05:07, Ryan Schmidt wrote: > On Mar 12, 2018, at 21:46, Mojca Miklavec wrote: > >>> Shall we backport these PRs to our buildbot 0.8.12 port? >>> >>> Add context field to GitHubStatus updates >>> https://github.com/buildbot/buildbot/pull/1721 >>> >>> Include 'context' in the log

Re: [macports-infrastructure] 02/02: buildbot: Update status on GitHub after each build

2018-03-13 Thread Rainer Müller
On 2018-03-13 05:07, Ryan Schmidt wrote: > > On Mar 12, 2018, at 21:46, Mojca Miklavec wrote: > >>> Shall we backport these PRs to our buildbot 0.8.12 port? >>> >>> Add context field to GitHubStatus updates >>> https://github.com/buildbot/buildbot/pull/1721 >>> >>> Include 'context' in the log

Re: [macports-infrastructure] 02/02: buildbot: Update status on GitHub after each build

2018-03-13 Thread Rainer Müller
On 2018-03-13 11:06, Rainer Müller wrote: > I am working on a filter by builder name. This should be covered with this commit: https://github.com/macports/macports-infrastructure/commit/830b9ff5b4f0af5d7d2598e01f48ff69074e7742 Rainer

Re: [macports-infrastructure] 02/02: buildbot: Update status on GitHub after each build

2018-03-13 Thread Ryan Schmidt
On Mar 13, 2018, at 02:43, Mojca Miklavec wrote: > On 13 March 2018 at 05:07, Ryan Schmidt wrote: >> On Mar 12, 2018, at 21:46, Mojca Miklavec wrote: >> Shall we backport these PRs to our buildbot 0.8.12 port? Add context field to GitHubStatus updates

Re: Changing default cxx_stdlib to libc++

2018-03-13 Thread db
On 12 Mar 2018, at 21:56, Ryan Schmidt wrote: > I'm not aware of any plan to notify users of the cxx_stdlib change, other > than the same way that users are notified of any other port update being > available: by the user running "sudo port selfupdate" and then

Re: Changing default cxx_stdlib to libc++

2018-03-13 Thread Ryan Schmidt
On Mar 13, 2018, at 08:47, db wrote: > On 12 Mar 2018, at 21:35, Ryan Schmidt wrote: >> On Mar 12, 2018, at 13:56, db wrote: >>> If not, shouldn't it, prior to accepting an updated port definition? >> The buildbot is only engaged after a commit is in the repository master >> branch. >> We have a

Re: [macports-infrastructure] 02/02: buildbot: Update status on GitHub after each build

2018-03-13 Thread Rainer Müller
On 2018-03-13 13:27, Ryan Schmidt wrote: > > On Mar 13, 2018, at 02:43, Mojca Miklavec wrote: > >> On 13 March 2018 at 05:07, Ryan Schmidt wrote: >>> On Mar 12, 2018, at 21:46, Mojca Miklavec wrote: >>> > Shall we backport these PRs to our buildbot 0.8.12 port? > > Add context field

Re: Changing default cxx_stdlib to libc++

2018-03-13 Thread db
On 12 Mar 2018, at 21:35, Ryan Schmidt wrote: > On Mar 12, 2018, at 13:56, db wrote: >> If not, shouldn't it, prior to accepting an updated port definition? > The buildbot is only engaged after a commit is in the repository master > branch. > We have a separate system,

Re: Changing default cxx_stdlib to libc++

2018-03-13 Thread Ryan Schmidt
On Mar 13, 2018, at 08:45, db wrote: > On 12 Mar 2018, at 21:56, Ryan Schmidt wrote: >> I'm not aware of any plan to notify users of the cxx_stdlib change, other >> than the same way that users are notified of any other port update being >> available: by the user running "sudo port selfupdate"

Re: Buildbot proposal: combine portwatcher and portbuilder

2018-03-13 Thread Mojca Miklavec
Dear Ryan, Please take a look at the discussion summary we just had at the meeting: https://trac.macports.org/wiki/Meetings/MacPortsMeeting2018/BuildbotRestructuring Regarding emails: we figured out that it makes no sense to make our design decisions based on how annoying it would be to write

Re: Changing default cxx_stdlib to libc++

2018-03-13 Thread db
On 13 Mar 2018, at 15:22, Ryan Schmidt wrote: > On Mar 13, 2018, at 08:47, db wrote: >> On 12 Mar 2018, at 21:35, Ryan Schmidt wrote: >>> On Mar 12, 2018, at 13:56, db wrote: If not, shouldn't it, prior to accepting an updated port definition? >>> The buildbot is

Re: [macports-infrastructure] 02/02: buildbot: Update status on GitHub after each build

2018-03-13 Thread Mojca Miklavec
On 13 March 2018 at 16:15, Ryan Schmidt wrote: > On Mar 13, 2018, at 07:50, Rainer Müller wrote: >> On 2018-03-13 13:27, Ryan Schmidt wrote: >>> On Mar 13, 2018, at 02:43, Mojca Miklavec wrote: On 13 March 2018 at 05:07, Ryan Schmidt wrote: > > Maybe we want to exclude some of them...

Re: [macports-infrastructure] 02/02: buildbot: Update status on GitHub after each build

2018-03-13 Thread Ryan Schmidt
On Mar 13, 2018, at 07:50, Rainer Müller wrote: > On 2018-03-13 13:27, Ryan Schmidt wrote: >> >> On Mar 13, 2018, at 02:43, Mojca Miklavec wrote: >> >>> On 13 March 2018 at 05:07, Ryan Schmidt wrote: On Mar 12, 2018, at 21:46, Mojca Miklavec wrote: >> Shall we backport these PRs

Re: Buildbot proposal: combine portwatcher and portbuilder

2018-03-13 Thread Ryan Schmidt
On Mar 13, 2018, at 09:50, Mojca Miklavec wrote: > Dear Ryan, > > Please take a look at the discussion summary we just had at the meeting: > > https://trac.macports.org/wiki/Meetings/MacPortsMeeting2018/BuildbotRestructuring So... > Ryan's proposal > > Ryan asked us to get rid of the

Re: Changing default cxx_stdlib to libc++

2018-03-13 Thread db
On 13 Mar 2018, at 17:10, Mojca Miklavec wrote: > The main problem is that Travis is *not* out main build system, we use > a different system for that. Travis has lots of limitations: Got it. Then why use it in the first place instead of an alternative CI?

Re: Changing default cxx_stdlib to libc++

2018-03-13 Thread Mojca Miklavec
On 14 March 2018 at 00:12, db wrote: > On 13 Mar 2018, at 17:10, Mojca Miklavec > wrote: >> The main problem is that Travis is *not* out main build system, we use >> a different system for that. Travis has lots of limitations: > > Got it. Then

Action Required: Clone Your MacPorts User Repository on GitHub

2018-03-13 Thread Clemens Lang
Hello, If you find yourself in the To list of this email, you still have a user repository in the MacPorts GitHub organization at https://github.com/macports/macports-user- We have created this repository from the users/ subfolder of the MacPorts Subversion repository when we moved to GitHub.

Re: CI system for PR builds (was: Re: Changing default cxx_stdlib to libc++)

2018-03-13 Thread Ryan Schmidt
On Mar 13, 2018, at 19:14, Rainer Müller wrote: > On 2018-03-14 00:42, db wrote: >> On 14 Mar 2018, at 00:22, Mojca Miklavec wrote: >>> Because someone would need to write the code for an alternative CI >> >> Wouldn't self-hosted GitLab CI be good enough? > > Are you going to sponsor a

Re: [macports-ports] branch master updated: Update Tesseract to 03.05.01

2018-03-13 Thread Ryan Schmidt
On Mar 13, 2018, at 21:32, Mark Anderson wrote: > Perry E. Metzger (pmetzger) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/1b655b8f6dae92268712ca6ff6900ab60008f53e > > The following commit(s) were added to

Re: [macports-infrastructure] branch master updated: GitHubStatus: allow to filter by builder name

2018-03-13 Thread Ryan Schmidt
On Mar 13, 2018, at 06:14, Rainer Müller wrote: > Rainer Müller (raimue) pushed a commit to branch master > in repository macports-infrastructure. > > > https://github.com/macports/macports-infrastructure/commit/830b9ff5b4f0af5d7d2598e01f48ff69074e7742 > > The following commit(s) were added

Re: Changing default cxx_stdlib to libc++

2018-03-13 Thread db
On 14 Mar 2018, at 00:22, Mojca Miklavec wrote: > Because someone would need to write the code for an alternative CI Wouldn't self-hosted GitLab CI be good enough? I get the impression that testing across the board is not a priority.

Re: Changing default cxx_stdlib to libc++

2018-03-13 Thread Rainer Müller
On 2018-03-14 00:42, db wrote: > On 14 Mar 2018, at 00:22, Mojca Miklavec wrote: >> Because someone would need to write the code for an alternative CI > > Wouldn't self-hosted GitLab CI be good enough? Are you going to sponsor a dedicated Mac server for GitLab CI? Travis CI