Re: Payload ownership
Re: Payload ownership
- Subject: Re: Payload ownership
- From: Don Montalvo <email@hidden>
- Date: Thu, 4 Mar 2010 12:10:40 -0800
sakshi <email@hidden> wrote:
> Hi,
>
> I am running into a very weird issue while building a pmdoc and need some
> help with my basics. I created a pmdoc using a staging folder on my machine.
> I shared it with the team to build and test on their machines. On one
> machine we are seeing weird behavior and some files end up getting created
> with an <unknown> owner. The pmdoc is being built through the commandline.
>
> All other files have a valid username associated with them, just these
> specific files are linked to <unknown>. I've verified the staging folder on
> that machine and it has the right permissions and owner. I opened that copy
> of the pmdoc in PackageMaker and it also has the expected owner. Somehow the
> final pkg differs. I used lsbom and verified that the pkg itself contains a
> 'corrupted' file.
>
> Any clues on where else I could look?
>
> Thanks!
> Sakshi
Hi Sakshi,
Sounds like the user:group defined in the pkg is not present on the target computer? For example, if you set user to "jdoe" who has UID of 504, but there is no UID 504 on the target computer, this can happen. It happened last week when I was testing a new pkg. Since it happened before, I recognized the problem. I changed the user:group to something that's on every computer. Then tested again and all went well.
Don _______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden