On 2019-11-18 08:53 , Steven Smith wrote:
> A separate and likely insignificant issue with the same port. Nevertheless:
>
> Why don’t the buildbots automatically build the `*-proxy`and its
> dependent subports?
>
> Everything works locally, but half the Portfile isn’t being tested by
> the buildb
A separate and likely insignificant issue with the same port. Nevertheless:
Why don’t the buildbots automatically build the `*-proxy`and its dependent
subports?
Everything works locally, but half the Portfile isn’t being tested by the
buildbots, including the main port ${name}:
> Port macos-fo
Thank you! This is what gurus are for.
For posterity, the adaptive hosts file is created from macOS’s original
/etc/hosts file, which I’ve saved as hosts.orig in case I or anyone else wants
a different hosts file baseline.
I’ll just rename it hosts_orig.
> On Nov 17, 2019, at 3:51 PM, Ryan Sch
On Nov 17, 2019, at 14:37, Steven Smith wrote:
> I have a weird error with the recently merged macos-fortress port.
>
> sudo port selfupdate
> sudo port install macos-fortress
>
> throws an error because the file ${filespath}/hosts.orig doesn’t exist.
>
> I see this file on GitHub:
> https:
I have a weird error with the recently merged macos-fortress port.
sudo port selfupdate
sudo port install macos-fortress
throws an error because the file ${filespath}/hosts.orig doesn’t exist.
I see this file on GitHub:
https://github.com/macports/macports-ports/blob/master/net/macos-fortress/f
