Re: Error writing data to TLS socket: The specified session has been invalidated for some reason.

2019-01-27 Thread Kenneth F. Cunningham
On 2019-01-27, at 10:33 AM, Ryan Schmidt wrote: > On Jan 27, 2019, at 06:24, Marius Schamschula wrote: > >> On Jan 26, 2019, at 9:03 PM, Ken Cunningham wrote: >> >>> Running the test suite on gnutls on 10.6.8 shows one failure: >>> >>> FAIL: srp >> >> For gnutls 3.6.6 the test suite runs

Re: Q about a (new) portgroup file

2019-01-27 Thread Eric F (iEFdev)
On 1/27/19 19:39 , Rainer Müller wrote: > On 27.01.19 14:33, Eric F (iEFdev) wrote: >> Ok, here it is: https://github.com/macports/macports-ports/pull/3510 >> Hope that was ok. At least it passed the checks. :) > FYI, Travis CI will only test changed Portfiles, as you can see on this > build the

Re: Q about a (new) portgroup file

2019-01-27 Thread Rainer Müller
On 27.01.19 14:33, Eric F (iEFdev) wrote: > > On 1/27/19 14:21 , Christopher Jones wrote: >> If you don’t think it is quite ready, but you want to start to get >> feedback, then that is exactly with WIP PRs are for. Just remember to >> start the title with ‘WIP” and also add the wip label to the

Re: Error writing data to TLS socket: The specified session has been invalidated for some reason.

2019-01-27 Thread Ryan Schmidt
On Jan 27, 2019, at 06:24, Marius Schamschula wrote: > On Jan 26, 2019, at 9:03 PM, Ken Cunningham wrote: > >> Running the test suite on gnutls on 10.6.8 shows one failure: >> >> FAIL: srp > > For gnutls 3.6.6 the test suite runs clean under High Sierra: only a few > XFAIL, not a single FAIL.

Re: Can buildbots open a window?

2019-01-27 Thread Ryan Schmidt
On Jan 22, 2019, at 08:40, Joshua Root wrote: > On 2019-1-23 00:48 , Marcus Calhoun-Lopez wrote: >> In trying to fix one bug [1], I seem to have created another [2]. >> I have been unable to fix the second bug, so I am revisiting the first. >> >> When building, octave tries to open a window

Re: Q about a (new) portgroup file

2019-01-27 Thread Eric F (iEFdev)
On 1/27/19 14:21 , Christopher Jones wrote: > If you don’t think it is quite ready, but you want to start to get feedback, > then that is exactly with WIP PRs are for. Just remember to start the title > with ‘WIP” and also add the wip label to the PR. > > Chris Thanks! Ok, here it is:

Re: Q about a (new) portgroup file

2019-01-27 Thread Christopher Jones
> On 27 Jan 2019, at 12:17 pm, Eric F (iEFdev) wrote: > > Thanks Chris, > > > On 1/27/19 12:41 , Christopher Jones wrote: >>> So, I'd like to ask… Where to put it? >> >> The port group code lives in the same GitHub project as the ports. See >> >>

Re: Q about a (new) portgroup file

2019-01-27 Thread Eric F (iEFdev)
Thanks Chris, On 1/27/19 12:41 , Christopher Jones wrote: >> So, I'd like to ask… Where to put it? > > The port group code lives in the same GitHub project as the ports. See > > https://github.com/macports/macports-ports/tree/b7dbaee30cd63f197eb8d1b0db9090a5a5c948f4/_resources/port1.0/group > >

Re: Q about a (new) portgroup file

2019-01-27 Thread Joshua Root
On 2019-1-27 22:41 , Christopher Jones wrote: > > The port group code lives in the same GitHub project as the ports. See > > https://github.com/macports/macports-ports/tree/b7dbaee30cd63f197eb8d1b0db9090a5a5c948f4/_resources/port1.0/group > > New port groups should just be added there. > > I

Re: Q about a (new) portgroup file

2019-01-27 Thread Christopher Jones
> On 27 Jan 2019, at 11:35 am, Eric F (iEFdev) wrote: > > Hi, > > While waiting on a PR and a ticket, I spent the weekend looking at file I > once started with. > > // From an earlier convo (w Ryan): > … since github.setup sets it for you; > >>> An off-topic question about