on 14 Sep, iTerm was running and notified me that an update was available; i allowed iTerm to update itself, and there were no warnings in the process except for the perfunctory warning at that my shell session would be closed; i wasn't actually going to use it at that time so i missed the fact that when i clicked the button to install and relaunch iTerm, it failed to launch; i do have an item in my system.log from the 14th about that failure:
Sep 14 09:43:52 mirapod-2 relaunch: LSOpenFromURLSpec() returned -10661 for application (null) path /Applications/Utilities/_net/iTerm.app.
Sep 14 09:43:52 mirapod-2 [0x0-0x279279].com.googlecode.iterm2: 2011-09-14 09:43:52.048 relaunch[3578:10b] LSOpenFromURLSpec() returned -10661 for application (null) path /Applications/Utilities/_net/iTerm.app.
i hadn't tried to use it again until today, and have rebooted the machine in the interim; when i try to launch iTerm i get a notice
You can't open the application "iTerm.app" because it is not supported on this architecture.
nothing appears in my logs for this launch attempt
looking at the application in Finder, i found an application bundle with the "dead application" icon (white circle-slash atop generic gray icon); the plist in the bundle indicates 126.96.36.19910909
replacing the app with a fresh manual download today i can launch the app normally; i note the bundle's plist shows a different version number, 0.10, and compared to this bundle the unlaunchable version was missing iTerm.framework, the iTerm binary in the MacOS folder and the PkgInfo file, and some of the contents of the Resources folder; it appears that somehow a partial download was done without raising an error
iTerm has autu-updated successfully several times before; i have assumed that there is a checksum or some other verification involved in the auto-update process, and if so that seems to have failed in this case; in case it matters, i keep the app in a subfolder: /Applications/Utilities/_net
(Mac OS X 10.5.8, Core2Duo MacBook Pro)