Bug 17913 - Ownership of installed files isn't being set to root
Summary: Ownership of installed files isn't being set to root
Status: RESOLVED INVALID
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 7.0.7
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-02-20 14:13 UTC by bbender
Modified: 2017-03-22 16:57 UTC (History)
6 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED INVALID

Description bbender 2014-02-20 14:13:09 UTC
After installing the MonoTouch package, the files in /Developer/MonoTouch and /Applications/Xamarin.iOS\ Build\ Host.app are owned by uid 501 (which isn't even the uid of the account I'm using). They _should_ be owned by root.

Missing a postflight step?
Comment 1 Atin 2014-03-25 10:23:28 UTC
Today, we have checked this issue with:

ML 10.8.4
XS 4.2.4(build 32)
X.iOS 7.0.7.2

I have typed following command in terminal:
cd /Developer
ls -ln 

and observed that we are getting '501' for Monotouch. Here is the screencast for the same: http://screencast.com/t/ba2bkH4FPwzV
Comment 2 Manuel de la Peña [MSFT] 2017-03-22 16:57:35 UTC
This bug does not longer happen. Please if you consider this to be an error, reopen the bug.