<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr">A separate and likely insignificant issue with the same port. Nevertheless:</div><div dir="ltr"><br></div><div dir="ltr">Why don’t the buildbots automatically build the `*-proxy`and its dependent subports?</div><div dir="ltr"><br></div><div dir="ltr">Everything works locally, but half the Portfile isn’t being tested by the buildbots, including the main port ${name}:</div><div dir="ltr"><br></div><div dir="ltr"><blockquote type="cite"><span style="background-color: rgb(255, 255, 255);">Port macos-fortress-dshield success on xcode10.3. </span><a href="https://paste.macports.org/24874b625f02" rel="nofollow">Log</a><br><span style="background-color: rgb(255, 255, 255);">Port macos-fortress-emergingthreats success on xcode10.3. </span><a href="https://paste.macports.org/df1b57e12043" rel="nofollow">Log</a><br><span style="background-color: rgb(255, 255, 255);">Port macos-fortress-pf success on xcode10.3. </span><a href="https://paste.macports.org/52a890b02a7f" rel="nofollow">Log</a></blockquote></div><div dir="ltr"><br></div><div dir="ltr"><br><blockquote type="cite">On Nov 17, 2019, at 15:57, Steven Smith <steve.t.smith@gmail.com> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><span>Thank you! This is what gurus are for.</span><br><span></span><br><span>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.</span><br><span></span><br><span>I’ll just rename it hosts_orig.</span><br><span></span><br><blockquote type="cite"><span>On Nov 17, 2019, at 3:51 PM, Ryan Schmidt <ryandesign@macports.org> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>On Nov 17, 2019, at 14:37, Steven Smith wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>I have a weird error with the recently merged macos-fortress port.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>sudo port selfupdate</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>sudo port install macos-fortress</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>throws an error because the file ${filespath}/hosts.orig doesn’t exist.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>I see this file on GitHub: https://github.com/macports/macports-ports/blob/master/net/macos-fortress/files/hosts.orig</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>But it’s not in /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/net/macos-fortress/files</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>But all the other files are there. Weird that this one file is missing.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>How should this be fixed?</span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>By renaming the file, specifically its extension.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>mprsyncup (the script that keeps the rsync server updated) uses `rsync -aIC` to synchronize the files between the git clone and the rsync server directory. The -C part means "auto-ignore files in the same way CVS does". Files whose names end in .orig are among those that get excluded.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>https://github.com/macports/macports-infrastructure/blob/master/jobs/mprsyncup</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>If this is a sample file to be installed of which the user will edit a copy, then a suffix like .dist, .sample, .example would be what we usually use.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I don't think anybody's deliberately tried to use a .orig file in MacPorts before. :)</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><span></span><br></div></blockquote></body></html>