Re: "Could not update existing receipt" error
Re: "Could not update existing receipt" error
- Subject: Re: "Could not update existing receipt" error
- From: Rick Mann <email@hidden>
- Date: Wed, 8 Apr 2009 15:02:52 -0700
Thanks, Andrew. This is indeed what I needed. pkgutil shows our
installation, and I can remove it with pkgutil --forget.
Something else I didn't realize: the .pkg file that PackageMaker.app
creates is not a bundle, but a single file! I don't know what I did to
get that; I don't see a setting in the UI. But that's okay, I like it.
After removing the old DB receipt, and re-running my installer, I
still don't have a file in /Library/Receipts, but there is a new entry
in the receipts DB.
On Apr 7, 2009, at 00:37:32, Andrew Strotheide wrote:
Rick,
If you believe you need to modify the installdb, take a look at
pkgutil on 10.5+ (man pkgutil).
Andrew
On Tue, Apr 7, 2009 at 12:18 AM, Rick Mann <email@hidden>
wrote:
Well, I'm familiar enough with receipts to know to look in the /
Library/Receipts folder for my package's recept, and remove it.
Trouble is, there is no such receipt. I found a few files in /
Library/Receipts/boms, but nothing in /Library/Receipts. I even had
a colleague look to double-check. I also checked ~/Library/Receipts.
It seems to me that something is written in the installdb DB, and I
have no idea how to check that.
On Apr 6, 2009, at 23:11:28, Andrew Strotheide wrote:
Rick,
You will see this error any time you try to re-run your new
installer (with admin auth disabled). The UID used when the package
was installed before is 0 (root), but the current user has a
different uid, which means the receipt cannot be overwritten because
the new user does not have ownership.
It sounds like you're unfamiliar with receipts. Every time you
install a package, the "receipt" for that package is placed in /
Library/Receipts. If you go to that folder directly, I expect
you're going to find a file with the exact name of the package you
are developing. You may safely remove that file if you want your
installer to behave as if it has never executed before. Obviously
though, if you've released this package previously under the same
name, your users would have this problem also, so you would need to
take action to prevent that, perhaps by renaming the package.
Andrew
On Mon, Apr 6, 2009 at 6:36 PM, Rick Mann <email@hidden>
wrote:
We're trying alternatives to our ridiculous install requirements.
I'm trying to see if an admin user can install a sys prefs pane
without being prompted for a password.
When I unchecked the "Require admin authentication", and tried to
install our prefs pane, but since I've installed before, I get this:
4/6/09 17:11:22 installdb[43006] Error: Could not update existing
receipt using uid=501 as the prior owner is uid=0
Now, I can't find a receipt anywhere, so I don't know how to remove
this.
Is there a way?
--
Rick
_______________________________________________
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
_______________________________________________
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