Re: [julia] App permissions issues on OS X (#9010)

12 views
Skip to first unread message

Stefan Karpinski

unread,
Nov 17, 2014, 4:54:32 PM11/17/14
to JuliaLang/julia, Julia Backports

This should be safe to backport. @JuliaBackports.


Reply to this email directly or view it on GitHub.

Elliot Saba

unread,
Nov 17, 2014, 5:13:53 PM11/17/14
to JuliaLang/julia, Julia Backports

@hansen-m We try to have stable releases once a month or so. We should have a new release in a week or so.

Elliot Saba

unread,
Nov 17, 2014, 5:36:27 PM11/17/14
to JuliaLang/julia, Julia Backports

Backported in cb6a5ee

Viral B. Shah

unread,
Nov 18, 2014, 2:02:53 PM11/18/14
to JuliaLang/julia, Julia Backports

Close this?

Elliot Saba

unread,
Nov 18, 2014, 5:58:16 PM11/18/14
to JuliaLang/julia, Julia Backports

Closed #9010.

Simon Byrne

unread,
Dec 25, 2015, 4:46:44 PM12/25/15
to JuliaLang/julia, Julia Backports

I'm trying to understand the exact problem here (for #14470): from what I can tell, this issue can only arise when the user has intentionally disabled the "ignore ownership of this volume" option. Does this arise often? What do other software libraries do?

Elliot Saba

unread,
Dec 25, 2015, 6:41:26 PM12/25/15
to JuliaLang/julia, Julia Backports

@simonbyrne The issue here is that the files copied into the dmg are (by default) owned by whatever user the buildbot software is running as. Example: on the OSX buildbots, the user is called osx, and is UID 501. However, when mounting a .dmg file, the files don't store the username, they only store the UID, and 501 essentially means the first user created on that system, so if you attempt to open the .dmg on a system with multiple users, the files will appear to be owned by the first user that was created on that system, which may or may not be the user actually wanting to use julia in the first place.

The solution to this is to standardize everything by chown'ing the whole directory tree as root:admin. This is apparently standard practice on OS X, and is what the changes in a910969 effected. One small side-effect of this is that we have to use sudo to do a lot of this stuff due to the fact that things are owned by root.

Simon Byrne

unread,
Dec 28, 2015, 9:17:27 AM12/28/15
to JuliaLang/julia, Julia Backports

thanks @staticfloat, I got that far, but from what I can tell this problem only arises when the user has intentionally disabled "ignore ownership of this volume" (as otherwise its just loaded as the current user/users group).

I've looked at a few other .dmg files, and haven't come across any that bother changing the owner. Most seem to keep the UID/GID as 501/20 (though aquamacs uses 505/20).

Even then, when I copy the files to /Applications, the owner/group gets set to me/admin (admin=group 80): I guess because the /Applications is in the admin group?

Elliot Saba

unread,
Dec 28, 2015, 2:12:10 PM12/28/15
to JuliaLang/julia, Julia Backports

I'm not certain when "ignore ownership of this volume" is not the default, but yes, in the case that it is checked, this is a non-issue.

Reply all
Reply to author
Forward
0 new messages