Upgrade problem

[mikel]

Hi,

I read about V2 in Daring Fireball and launched Superduper to update itself, but the upgrade failed. Note that although in the transcript below it suggests that the upgrade was successful, the version in my Applications folder is still 1.5.5.

Here is a dump of the relevant Console info:

[***] Thursday, November 24, 2005 08:42:54 AM Canada/Eastern
|08:42:54 AM|Info| SuperDuper!, version 74, path: /Applications/SuperDuper!.app, OS: 10.4.3 (8F46)
|08:42:54 AM|Info| Copy Mode : Smart Update
|08:42:54 AM|Info| Copy Script : Backup - all files.dset
|08:42:54 AM|Info| Transcript : UpgradeTranscript.plist
|08:42:54 AM|Info| PHASE: Upgrade Application
|08:42:54 AM|Info| ...ACTION: Upgrade Application
|08:42:54 AM|Info| ......COMMAND => Downloading update package...
|08:43:11 AM|Info| ......COMMAND => Uncompressing upgrade package
|08:43:11 AM|Info| ......COMMAND => Installing upgrade package
|08:43:12 AM|Info| Package name is SuperDuper!
|08:43:12 AM|Info| Installing onto volume mounted at /.
|08:43:12 AM|Info| Preparing for installation
|08:43:13 AM|Info|
|08:43:14 AM|Info| The software was successfully installed
|08:43:14 AM|Info| The install was successful.
|08:43:14 AM|Info| ......COMMAND => Copying upgrade bundle to temporary location
|08:43:14 AM|Error| ditto: /Applications/Utilities/SuperDuper!.app: No such file or directory

[dnanian]

Hi, Mike -- rare problem that's happening to some. Just download the program from elsewhere on the site and manually install -- that'll resolve the issue.

Sorry for the trouble.

[mikel]

Hi, Mike -- rare problem that's happening to some. Just download the program from elsewhere on the site and manually install -- that'll resolve the issue.

Sorry for the trouble.
OK thanks. And no problem - it's still super-easy to upgrade.

[dnanian]

We can always make it easier... :)

[jcbeckman]

I had to recompile the Daily Backup.applescript, save it as an .app, and re-save my Daily Backup settings for the upgrade to work for me. I tried the auto upgrade and the manual install method.

[dnanian]

Well, you don't really need "Daily Backup" any more, jcbeckman... just use the built-in scheduler!

[jcbeckman]

When I tired the built-in scheduler, it made an entry in my cron tables that looked *exactly* like the entry I already had - right down to starting "Daily Backup.app". When I tried running it, it died - first, it tried to run v155 instead of v2. After I trashed v155 (which I had renamed, but the applescript found anyway), then it said all kinds of files were missing. That's when I recompiled the applescript.

It looks to me like the Scheduler just takes the place of manually creating a cron entry (which is certainly fine), but that I still *do* need the "Daily Backup" .app, applescript and settings.

[dnanian]

It certainly shouldn't have done that. It should create a rather different crontab entry.

Could you try removing any schedules in the scheduled copies window, clearing your crontab with "crontab -r" (as long as there's nothing else in there of importance), and then give it another try?

[jcbeckman]

That worked. I got a completely different cron job this time.

[dnanian]

Phew! Good.

Let me know how this one works!

[themphill]

My update failed similar to the original poster's update; here is part of the log:

|09:15:37 AM|Info| The software was successfully installed
|09:15:37 AM|Info| The install was successful.
|09:15:37 AM|Info| ......COMMAND => Copying upgrade bundle to temporary location
|09:15:37 AM|Error| ditto: /Applications/Utilities/SuperDuper!.app: No such file or directory

It is my understanding that a manual install is in order. My question is, if I go that route, do I need to worry about any deritus left over from the failed previous installation?

[dnanian]

Nope, no detritus, themphill. You could remove the receipt from /Library/Receipts, though, if you'd like.