philr has joined #nix-darwin
periklis has joined #nix-darwin
periklis has quit [Ping timeout: 260 seconds]
peacememories has joined #nix-darwin
periklis has joined #nix-darwin
peacememories has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
periklis has quit [Ping timeout: 260 seconds]
periklis has joined #nix-darwin
periklis has quit [Ping timeout: 252 seconds]
philr has quit [Ping timeout: 272 seconds]
trcc has joined #nix-darwin
hamishmack has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<dhess> I'm getting build issues with libsecurity_utilities-osx-10.7.5 again on Mojave
<dhess> oh I see that johnw and acowley are also having problems
<dhess> does anyone know why this keeps happening?
<dhess> oh but looks like johnw and acowley are having problems with it on High Sierra
<dhess> I'm actually having problems building it on Mojave. It was fixed for awhile and then broke agai
<dhess> sometime between 6021a94062f9740591e858996984089317b51c13 (good) and d9423ee4464e02fd90eb2ca6192017a00a0805bf (bad)
hamishmack has joined #nix-darwin
<wildsebastian> Hi there! I have the same issue with Mojave (Latest update: 10.14.1)
<wildsebastian> dhess: Thank you for the mention of the git hashes, I just did a git bisect and might have found the first bad commit.
trcc has quit []
<wildsebastian> I don't have enough knowledge at this point to know what is wrong
<wildsebastian> But according to my git bisect the first bad commit is 0fcd2ca7b2e313f88687037a835555b31a0892b6
<wildsebastian> I will try to fix it, but maybe it also helps someone else with deeper knowledge
carlosdagos has joined #nix-darwin
<wildsebastian> I was able to fix it, by removing the copy in line 44 (pkgs/os-specific/darwin/cf-private/default.nix). What are the implications of this?
<dhess> wildsebastian: wow, nice work!
<dhess> LnL should see this soon and he can take a look (he made the commit)
<wildsebastian> dhess: Thank you for narrowing it down for me! :)
<dhess> wildsebastian: it's good to have you around :) I hope you stick around!
<wildsebastian> dhess: Thank you! I will definitely stick around! :)
<dhess> good ;)
<LnL> huh, that broke something?
<wildsebastian> LnL: Yes. It brought up all the libsecurity_utilities-osx build errors. After removing the copy it works again (on my machine - TM)
<wildsebastian> For me basically installing haskell based packages like cabal2nix broke
<LnL> well, my fix unblocked the channel updates
<LnL> btw y'all have been confusing me by talking about macos versions, this should be a problem everywhere
<dhess> it seems like it is. acowley and johnw reported it earlier in the chat and are running High Sierra
<dhess> wildsebastian and I are running Mojave
<wildsebastian> I just saw the underlying error is a 'Permission denied' when copying.
<wildsebastian> LnL: I think I pinned the issue down to the '-f' option flag of the 'cp'. I just removed it and it works now for me.
<dhess> nice
<LnL> I think the proper solution here is to get rid of cf-private in the framework dependencies and make it explicit everywhere it's actually needed
<LnL> oh, hmm
<wildsebastian> LnL: Sorry, never mind. It failed at a later point.
<LnL> LnL: where? what I added already uses -f
<wildsebastian> Since removing the copy from Line 44 of pkgs/os-specific/darwin/cf-private/default.nix, I experimented by removing only options from that copy statement. I thought removing -f works, but I was wrong. Sorry for the confusion.
<wildsebastian> This is the underlying error.
<wildsebastian> cp: cannot create regular file '/nix/store/4abf2ls22vfi8azzq881fiixkm1bh7q3-swift-corefoundation-private/Library/Frameworks/CoreFoundation.framework/Headers/CFFileDescriptor.h': Permission denied
<{^_^}> #49768 (by LnL7, 7 seconds ago, open): darwin: don't include cf-private in framework dependencies
<wildsebastian> LnL7: Cool! Thank you! :)
<wildsebastian> LnL: Thank you, that fixes it for me and I hope for others as well as far as I tested it. :) Sorry for the confusion I might have caused!
<dhess> thanks, LnL
<LnL> no problem, I didn't expect the original commit to cause any problems since we did basically the same before