On Mar 11, 2018, at 11:07, Joshua Root wrote:
> Joshua Root (jmroot) pushed a commit to branch master
> in repository macports-ports.
>
>
> https://github.com/macports/macports-ports/commit/b215f4265eff84d045c20168dfc47b4f99d5c969
>
> commit b215f4265eff84d045c20168dfc47b4f99d5c969
>
> Author
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 refs/heads/m
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 dedicated
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 to
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 is available at no co
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.
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 why use it in the first place instead of an alternat
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?
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.
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 separa
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...
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
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 only engaged after a commit i
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 em
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" a
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
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, using Travis CI, for doing
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 examining the
> output of "port o
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 t
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
https://github.com/buil
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
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 me
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
23 matches
Mail list logo
