Re: Payload ownership
Re: Payload ownership
- Subject: Re: Payload ownership
- From: Don Montalvo <email@hidden>
- Date: Fri, 5 Mar 2010 09:16:09 -0600
Hi Sakshi,
Just curious, is the username exactly the same on both computers? I mean the short name (not John Doe, but johndoe or jdoe). Also, what is the UID on the account (on each machine)? We deal with managed environments, so the UID is consistent across all Macs (longish AD string). Lastly, is there a reason the payload can't simply be owned by root:wheel (the standard we use)? :)
Don
On Mar 5, 2010, at 5:54 AM, sakshi wrote:
> Hi Don,
>
> The user:group do exist on the machine. In fact when I see the pmdoc on my machine, files are labeled root:admin and on the buggy machine (the staging area and) the pmdoc contents get set to the user's username:admin. I was under the impression that the staging area would define what does into the pmdoc and finally the pkg. This situation seems to differ from my opinion: the pmdoc gets set from the staging area but the pkg has a mind of its own.
> Does the fact that packagemaker is being invoked from the commandline and not the UI have any impact?
>
> Thanks,
> Sakshi
>
> On Fri, Mar 5, 2010 at 1:40 AM, Don Montalvo <email@hidden> wrote:
> 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