On Tue, Jan 24, 2017 at 6:53 PM, René J.V. Bertin
wrote:
> 0775 (0001:1101) turning into 0255 (000:10101101), there's no
> logical explanation (involving umask()) for that, is there?
That is what you'd get if the *umask* were 0255.
--
brandon s allbery kf8nh
> On Jan 24, 2017, at 01:32, Ryan Schmidt wrote:
>
>
>> On Jan 23, 2017, at 21:05, Jeremy Huddleston Sequoia
>> wrote:
>> commit b45c6c288b90421df0407b17a5885033bfb4efdd
>>
>> Author: Jeremy Huddleston Sequoia
>>
Ryan Schmidt writes:
>> On Jan 23, 2017, at 18:08, Sean Farley wrote:
>>
>> Sean Farley (seanfarley) pushed a commit to branch master
>> in repository macports-ports.
>>
>>
>>
Hello,
You know I use a very slightly adapted version of "base" to use MacPorts on
Linux. This is about an intermittent issue I see there that happens in code
which I think should be host/OS *independent*.
I have mentioned before that I sometimes get permissions errors during the
destroot
Hello,
Does anyone (Jeremy??) know if the Security.framework sources provided on
opensource.apple.com (latest version
https://opensource.apple.com/source/Security/Security-57740.31.2/) are
feature-complete and has anyone tried to build this framework with the goal of
providing recent security
> On Jan 23, 2017, at 18:08, Sean Farley wrote:
>
> Sean Farley (seanfarley) pushed a commit to branch master
> in repository macports-ports.
>
>
> https://github.com/macports/macports-ports/commit/ea02c6a2415087a43634f83653532c4aaf346a21
>
> commit
> On Jan 23, 2017, at 21:05, Jeremy Huddleston Sequoia
> wrote:
>
> Jeremy Huddleston Sequoia (jeremyhu) pushed a commit to branch master
> in repository macports-ports.
>
>
> https://github.com/macports/macports-ports/commit/b45c6c288b90421df0407b17a5885033bfb4efdd
>