Finally needed to use a Pages document today. Double-clicked it as usual and was greeted by a message suggesting I "contact the developer to make sure the app was compatible with Lion."
I thought that's what the iWork Updater 6 was supposed to have provided!
Who would have thought I should have investigated the actual 'proof-of-concept!" No, I blithely accepted Apple's promise and 100% accuracy of their previous updates...
Checking the Apple Forums revealed that others had discovered the same behavior (from all three iWork apps). Software update claimed my versions were up-to-date (which was true). Unzipping my archived versions did get SU to decide those versions needed updating, but it did not create versions that would work in Lion.
Not even if I downloaded the updater from Apple directly.
The only solution that seemed to work, as stated in the Forums, was to completely
un-install the apps, re-install from whatever media they came on and
then do the updating. Fortunately, that also worked for me. I have no idea why, however.
Along the way, I discovered that there don't seem to be any ".bom" files in any Receipts directory. This may be part of the recent "buy-from-the-Mac-App-Store-and-we'll-keep-track-of-everything" philosophy at Apple. The directory is still there but the only ".bom" files are from non-Apple apps/developers. The actual app installations are now kept in a "InstallHistory.plist" file. One advantage might be to provide a list of all the files an installer creates, even though the locations aren't listed. The list also includes how the instal occurred; Software Update, the developer's installer, etc.
Aside/Rant:
I'm trying to be a 'security-conscious' user and forcing a password login. But, once again, I'm growing weary of constantly being asked for that password to make changes in the /Library. In fact, duplicating/archiving a 'System" file provides no request for a password. The OS acts like it is following my command and even beeps when it is 'complete.' However, nothing actually happens (unless the action is putting the file somewhere else on the drive!)! In order to do my standard 'archive-before-updating' method, I have to copy the system file to somewhere in my Home directory. That move then requests my password.
I'm not actually sure this is because I changed the way I log in or if it is the "Lion" way of operating.