Re: SL checking bundle versions incorrectly?
Re: SL checking bundle versions incorrectly?
- Subject: Re: SL checking bundle versions incorrectly?
- From: Kevin Brock <email@hidden>
- Date: Fri, 04 Sep 2009 16:21:12 -0700
Iceberg-Dev wrote:
On Sep 4, 2009, at 8:55 PM, Kevin Brock wrote:
I've seen a strange error with SL upgrade of a package.
Here's what's happening.
1) Install initial package -- bundle version 1.0.2
2) Run installer of new package, with bundle version 1.0.3
result: 'PackageKit: skipping component "com.thecompany.theapp"
(*-1.0.0-*-*) because the version *-1.0.2-*-* is already installed.'
I figured something was wrong with the 1.0.3 package, so I
uninstalled 1.0.2, installed 1.0.3 fresh. Worked. Now I tried to
upgrade to 1.0.4,
result: 'PackageKit: skipping component "com.mycompany.theapp"
(*-1.0.0-*-*) because the version *-1.0.3-*-* is already installed.'
so clearly is is able to see that 1.0.3 *is* 1.0.3. So, why didn't
it see this during the upgrade from 1.0.2? Is it looking at a
different plist entry in each case?
Any help would be appreciated.
I would tend to believe the problem would lie with the version
Installer.app thinks it's seeing in the package you're trying to
install. The par tI don't get is how it can guess the format of your
version number x.x.x.
It gets stranger. I'm using short version string for the 'version',
i.e., 1.0.2. I'm using the build # for the bundle version, e.g., 1, 2,
3. So the 'About' box shows 1.0.2 (19) for example.
- Install version 1.0.2 (19) --> works. Run it, yes it shows build 19 in
the about box.
- Upgrade to version 1.0.(20) --> works. Run it, yes it shows build 20
in the about box.
- Upgrade *that* to 1.0.2 (21) --> skipping component
"com.mycompany.theapp" (*-19.0.0-*-*) because the version
*-1.0.2-20.0.0-*-* is already installed.
Now I know that the version number 19 is nowhere in build 21. I
generated three builds, one right after the other, where the only change
was the CFBundleVersion in the plist file. Maybe SL is caching things
it's not supposed to?
Something's really screwy here, and I can't figure out whether it's
something I'm doing or something SL is doing. I can't do anything to
fix this in the preflight script because the installer is making the
decision not to install the package before it runs the script.
Kevin
_______________________________________________
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