Re: 10.15 buildbot and nodejs17

On Jan 14, 2022, at 12:24, David Gilman wrote: > The buildbot for nodejs17 failed a few days ago: > > https://build.macports.org/builders/ports-10.15_x86_64-watcher/builds/24816 > > It looks like the other builders were OK with the job, so it isn't an > issue with the port. Digging into the log

Re: license_noconflict ignored on builders?

Yes, I went back and re-read that before I posted. The second example might qualify as having answered my question, but since "openssl" is both the name of a port and one of the licenses, maybe that's not the best example to be using? Especially considering that the keyword just above "license_noco

Re: license_noconflict ignored on builders?

On 2022-1-15 11:14 , Jason Liu wrote: Oh, was license_noconflict supposed to be used with the name of a port? Yes, exactly. It lists which of your dependencies you don't use in a way that creates a conflictingly-licensed binary, despite conflicting licenses being involved. - Josh

Re: license_noconflict ignored on builders?

On Jan 14, 2022, at 18:14, Jason Liu wrote: > Oh, was license_noconflict supposed to be used with the name of a port? I > thought it was supposed to specify a license that didn't conflict! See the documentation for license_noconflict at https://guide.macports.org/#reference.keywords

Re: license_noconflict ignored on builders?

Oh, was license_noconflict supposed to be used with the name of a port? I thought it was supposed to specify a license that didn't conflict! -- Jason Liu On Fri, Jan 14, 2022 at 6:35 PM Joshua Root wrote: > On 2022-1-15 03:58 , Jason Liu wrote: > > I added a license_noconflict > >

Re: license_noconflict ignored on builders?

On 2022-1-15 03:58 , Jason Liu wrote: I added a license_noconflict to one of my portfiles a couple of days ago, and it appears that the builders are still flagging it as not distributable: "warzone2100" is not distributable because its l

10.15 buildbot and nodejs17

The buildbot for nodejs17 failed a few days ago: https://build.macports.org/builders/ports-10.15_x86_64-watcher/builds/24816 It looks like the other builders were OK with the job, so it isn't an issue with the port. Digging into the log there it died trying to run xcodebuild -version. I am not s

license_noconflict ignored on builders?

I added a license_noconflict to one of my portfiles a couple of days ago, and it appears that the builders are still flagging it as not distributable: "warzone2100" is not distributable because its license "gpl" conflicts with license "OpenSS

Re: bazel build points to builder directory _opt_bblocal_var_buildworker_ports_build_ports_devel_bazel

Thanks. Please see https://trac.macports.org/ticket/64442. > On Jan 14, 2022, at 08:30, Christopher Jones wrote: > >  > > please open a trac ticket and we will discuss there. better than a mailing > list. > >> On 14 Jan 2022, at 11:55 am, Steven Smith wrote: >> >> Chris, Thanks, and concur

Re: bazel build points to builder directory _opt_bblocal_var_buildworker_ports_build_ports_devel_bazel

please open a trac ticket and we will discuss there. better than a mailing list. > On 14 Jan 2022, at 11:55 am, Steven Smith wrote: > > Chris, Thanks, and concur on the wonderfulness of bazel. > > To be clear, I am not building bazel-3.7 here. I am building > py38-tensorflow-metadata, which u

Re: bazel build points to builder directory _opt_bblocal_var_buildworker_ports_build_ports_devel_bazel

Chris, Thanks, and concur on the wonderfulness of bazel.To be clear, I am not building bazel-3.7 here. I am building py38-tensorflow-metadata, which uses bazel-3.7. I’ve attached the log file. It was produced with a build (please see attached Portfile) that adds `bazel.build_opts-append --sandbox_d