Re: el capitan

Here is a list of messages I have observed while installing ports: 1/27/16 8:07:05.232 PM sandboxd[116]: ([327]) xcodebuild(327) deny file-write-data /opt/local/var/macports/home/Library/Preferences/com.apple.dt.xcodebuild.plist 1/27/16 7:54:01.522 PM sandboxd[116]: ([95150]) mdworker(95150)

Re: el capitan

This is obviously "one of those important things" that Apple won't tell us about - or Fix - or tell "us" how to fix it. If you scan the forums, it has been around for a while. It is clearly related to Apple's security, nominally to the new "rootless" (or whatever its name is) environment, and

Re: el capitan

Not in this case. Macports makes use of the sandbox feature of Mac OS X to make it a little less likely that a poorly written Portfile (or upstream software build system) can cause unintended changes to your system. The original poster is setting the error because 'javac' is trying to update

Re: el capitan

I'm migrating from Yosemite to a clean install of El Capitan. I'm seeing several of these "deny" messages for various reasons besides Java. This is affecting both file and directory creation. Should I post the list here? Sent from my iPhone > On Jan 27, 2016, at 11:49 AM, Daniel J. Luke

Re: el capitan

On Wed, Jan 27, 2016 at 2:32 PM, Mark Brethen wrote: > I'm migrating from Yosemite to a clean install of El Capitan. I'm seeing > several of these "deny" messages for various reasons besides Java. This is > affecting both file and directory creation. Should I post the

Re: el capitan

thanks it does take a while to install took like 30 min but it got it done. thanks again. On Sun, Oct 25, 2015 at 3:36 AM, Stanton Sanderson wrote: > It is hard to resist the temptation to “pull the plug” when there is no > apparent movement, but the process worked

Re: el capitan

On Oct 24, 2015, at 7:49 PM, Brandon Allbery wrote: > At that point it is doing a "port sync", and depending on the state of the > servers, your local network conditions, etc. it may take a long time to > update itself. Some amount of time will be spent fetching the ports tree, yes, but the

Re: el capitan

Hi Alexander, I have it installed without any problems, how long are you waiting when it reaches 70%?. For me it took a while at this point, I think I waited more than 15 minutes but if completed ok. Kind Regards, Horst Simon > On 25 Oct 2015, at 11:20, Alexander Garcia Castro

Re: el capitan

On Sat, Oct 24, 2015 at 8:20 PM, Alexander Garcia Castro < alexgarc...@gmail.com> wrote: > Hi, I am using el capitan and I have downloaded mac ports several times. > it just does not work. the installation reaches close to 70% and then it > just does not move any more. does it work in el capitan

Re: el capitan

It is hard to resist the temptation to “pull the plug” when there is no apparent movement, but the process worked for me as described on the migration page. Have you looked at the Activity Monitor and Console apps? They can offer some reassurance as to whether things are moving. Using the

Re: El Capitan build errors...

Ok, got past the ones I caused. Here's what's left before I get stuck (filed tickets for the last three that didn't have them, found the tickets for the others): PortTkt# Description wireshark 49065 wireshark 1.12.17 +quartz crashes when opening a network device on ElCap

Re: El Capitan changes for Mac Ports ?

On Oct 4, 2015, at 3:22 AM, Sven Kolja Heinemann wrote: > Maybe the installer should just call xcodebuild -license. The User will still > have to press Y. An interesting idea, but I don't think we can do that. First, admin privileges are required ("sudo xcodebuild -license"). That might be

Re: El Capitan build errors...

That's ok, a couple were my bad anyway (built ok now). > On Oct 4, 2015, at 14:54, Rainer Müller wrote: > > On 2015-10-04 20:16, Richard L. Hamilton wrote: >> Here's my latest set of errors with log excerpts, now that I got >> further by applying the qt4-mac patch described

Re: El Capitan changes for Mac Ports ?

Maybe the installer should just call xcodebuild -license. The User will still have to press Y. > Am 04.10.2015 um 09:28 schrieb Ryan Schmidt : > > You're right, it looks like after Apple changed Xcode to require users to > accept a license agreement, the guide was not

Re: El Capitan changes for Mac Ports ?

On Oct 3, 2015, at 10:09 AM, William H. Magill wrote: > While doing the migration thing I noticed two items: > > 1- This might not be new, but with Apple Mail, “Reply” goes to the author of > the comment, not to the list. > “Reply All” puts the Author on the To: line and the mailing list

Re: El Capitan build errors...

On 2015-10-04 20:16, Richard L. Hamilton wrote: > Here's my latest set of errors with log excerpts, now that I got > further by applying the qt4-mac patch described in the ticket. > They're in order by number of other ports dependent on them, i.e. of > those I ran into, clucene had the most.