Re: [macports-ports] branch master updated: jack: Fix upgrade path from jack1

On Apr 6, 2018, at 16:26, Clemens Lang wrote: > Clemens Lang (neverpanic) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/a4e16dbb046d89f9146dbc9408f2bfb96ec73a82 > > The following commit(s) were added to

Re: problem with font DejaVuSansMono

Hi, - On 7 Apr, 2018, at 01:34, macpo...@parvis.nl wrote: > --- > DEBUG: system: /opt/mpt/bin/fc-cache -fv /opt/mpt/share/fonts > --- > but fc-cache seems to hang now (not on initial 2nd macports install), without > taking any cpu. fc-cache may just be doing a lot of IO. Try running $>

Re: CI system for PR builds

On Apr 7, 2018, at 00:47, Mojca Miklavec wrote: > On 3 April 2018 at 21:45, db wrote: >> On 3 Apr 2018, at 18:04, Mojca Miklavec wrote: >>> Travis has lots of limitations, but it offers both (a) and (b) for free. >> >> Couldn't (b) be the current infrastructure? > > No, because that would make

Re: CI system for PR builds

On 7 Apr 2018, at 07:47, Mojca Miklavec wrote: > No, because that would make the infrastructure that distributes binaries to > all our users susceptible to malicious PRs. How is reviewing a PR, then letting it build and, if it succeeds, uploading the binary, if not,

Re: [macports-ports] branch master updated: py-clang: python bindings to libclang

On Apr 7, 2018, at 12:05, Eric A. Borisch wrote: > Eric A. Borisch (eborisch) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/885596f36cf2d5fa569b7e2e2335db6907770c02 > > The following commit(s) were added to

Re: [macports-ports] branch master updated: py-clang: python bindings to libclang

On 2018-4-8 03:44 , Ryan Schmidt wrote: > > On Apr 7, 2018, at 12:05, Eric A. Borisch wrote: > >> +eval [subst { > > This usage of "eval" was recently removed from other ports. Please look up > what changes were done, and make them here as well: > >

Re: [macports-ports] branch master updated: jack: Fix upgrade path from jack1

Hi, On Sat, Apr 07, 2018 at 07:16:37AM -0500, Ryan Schmidt wrote: > I still think jack should not handle this differently from other > ports. If we want automatic upgrades for ports that have build > conflicts with themselves, then we want that for all such ports, not > just for jack. Sure, but

Re: CI system for PR builds

On Apr 7, 2018, at 07:02, db wrote: > On 7 Apr 2018, at 07:47, Mojca Miklavec wrote: >> No, because that would make the infrastructure that distributes binaries to >> all our users susceptible to malicious PRs. > > How is reviewing a PR, then letting it build and, if it succeeds, uploading >

CI system for PR builds

On 2018-04-07 07:40, Mojca Miklavec wrote: >>> - with a bit of legal questionability >> >> From my understanding, it is legal to virtualize macOS, as long as the >> hypervisor is running on a Mac as well, which is possible. > > I'm aware that it's legal to virtualize macOS on mac hardware, it's >

Re: CI system for PR builds

On 2018-04-07 19:44, Clemens Lang wrote: > For these resons, we want to reset the machines to a clean state before > every build, which we could do with buildbot, but requires some python > magic that hasn't been written yet. I think this is mostly written. What is needed is only a little bit of