File Doesn't Appear in Release tarball, but is in GitHub master
Steven Smith
steve.t.smith at gmail.com
Sun Nov 17 21:53:54 UTC 2019
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-fortress-dshield success on xcode10.3. Log
> Port macos-fortress-emergingthreats success on xcode10.3. Log
> Port macos-fortress-pf success on xcode10.3. Log
> On Nov 17, 2019, at 15:57, Steven Smith <steve.t.smith at gmail.com> wrote:
>
> 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 Schmidt <ryandesign at macports.org> wrote:
>>
>>
>>
>>> 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://github.com/macports/macports-ports/blob/master/net/macos-fortress/files/hosts.orig
>>>
>>> But it’s not in /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/net/macos-fortress/files
>>>
>>> But all the other files are there. Weird that this one file is missing.
>>>
>>> How should this be fixed?
>>
>> By renaming the file, specifically its extension.
>>
>> 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.
>>
>> https://github.com/macports/macports-infrastructure/blob/master/jobs/mprsyncup
>>
>> 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.
>>
>> I don't think anybody's deliberately tried to use a .orig file in MacPorts before. :)
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20191117/af763f66/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3898 bytes
Desc: not available
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20191117/af763f66/attachment-0001.bin>
More information about the macports-dev
mailing list