Can’t get InstaUp2Date to run at all

[dead2sin]

I got instadmg running well and I am extremely pleased, so I decided to try instaup2date.

No matter what I do, whenever I run the instaup2date.py script it spits an error message at me.

In the catalog file, I tried putting in the exact path of the files as well as putting them in the InstaUp2DatePackages folder.

Here is a copy of my vanilla.catalog:

# This is the catalog for the Plain Vanilla Leopard 10.5 Image with Updates

Output Volume Name = Macintosh HD
Output File Name = OS X 10.5 Updated

Base OS Disk:
# the first one should be disk 1 of an installer disk
# this is not yet implimented

OS Updates:
Mac OS X 10.5.6 Combo Update /Users/macadmin/Desktop/MasterPackages/OSUpdates/MacOSXUpdCombo10.5.6.dmg ?

QuickTime 7.6 /Users/macadmin/Desktop/MasterPackages/OSUpdates/QuickTime76_Leopard.dmg ?

Java for Mac OS X 10.5 Update 2 /Users/macadmin/Desktop/MasterPackages/OSUpdates/JavaForMacOSX10.5Update2.dmg ?

AirPort Utility /Users/macadmin/Desktop/MasterPackages/OSUpdates/AirPortUtility_Leopard.dmg ?

Apple Updates:

iLife Media Browser v2 /Users/macadmin/Desktop/MasterPackages/OSUpdates/iLifeMediaBrowser_v2.dmg ?

Safari 3.2.1 /Users/macadmin/Desktop/MasterPackages/OSUpdates/Safari321Leopard.dmg ?

RAW Camera Update /Users/macadmin/Desktop/MasterPackages/OSUpdates/RAWCameraUpdate.pkg sha1:110546789241d1f15c213bcd222c13e40076ecbe

All the spaces in it are correct tabs. Here is the error message I get:

udo ./instaUp2Date.py vanilla.catalog
Password:
Looking for MacOSXUpdCombo10.5.6.dmg in cache folder
Did not find MacOSXUpdCombo10.5.6.dmg in archive
Downloading /Users/macadmin/Desktop/MasterPackages/OSUpdates/MacOSXUpdCombo10.5.6.dmg
Traceback (most recent call last):
File “/Users/macadmin/Desktop/InstaDMG_1.4b4/AddOns/InstaUp2Date/instaUp2Date.py”, line 930, in
main()
File “/Users/macadmin/Desktop/InstaDMG_1.4b4/AddOns/InstaUp2Date/instaUp2Date.py”, line 921, in main
thisController.parseFile(inputFilePath, topLevel=True)
File “/Users/macadmin/Desktop/InstaDMG_1.4b4/AddOns/InstaUp2Date/instaUp2Date.py”, line 221, in parseFile
thisPackage = installerPackage( simpleLineMatch.group(“prettyName”), simpleLineMatch.group(“archiveLocation”), simpleLineMatch.group(“archiveChecksum”), simpleLineMatch.group(“packageLocation”), simpleLineMatch.group(“packageChecksum”) )
File “/Users/macadmin/Desktop/InstaDMG_1.4b4/AddOns/InstaUp2Date/instaUp2Date.py”, line 546, in __init__
if self.retrieveFromArchive():
File “/Users/macadmin/Desktop/InstaDMG_1.4b4/AddOns/InstaUp2Date/instaUp2Date.py”, line 813, in retrieveFromArchive
if REMOTEFILE != None:
UnboundLocalError: local variable ‘REMOTEFILE’ referenced before assignment

thanks in Advance

Nate

[dead2sin]

Ok, I played with it a little more.

If I jump dump the files into the InstaUp2DatePackages folder, it works fine, but if I try to specify a path, it spits that error message out. Should the path be in quotes in the catalog file? What is the best way to specify their location? I would like to try to stay away from dumping all the packges into one folder.

Thanks,

Nate

[dead2sin]

*edit*

Nevermind. Its not working. *sigh*

[larkost]

First off, you are using a slightly different version of InstaUp2Date than I have on my computer because the line numbers don’t match. But I am always using the latest development version (since I am the developer).

I think I have an idea of what is going on. For some reason it is unable to open a temporary file in /tmp. To prove this you could change (around line 775):
[code]OUTPUTFILE = os.fdopen(fileDescriptor, “w+b”)
if OUTPUTFILE == None:
raise Exception(); # TODO: better errors[/code]
to:
[code]OUTPUTFILE = os.fdopen(fileDescriptor, “w+b”)
if OUTPUTFILE == None:
print(‘Yep, this is the problem’)
raise Exception(); # TODO: better errors[/code]

Then when you run the code, if I am right, then you will get the message ‘Yep, this is the problem’.

[dead2sin]

Ironically, I added that debug message you suggested, but when I run it now I get a totally different error message. I think that the script hates me for some reason =)

Its now getting an error on line 66, which is the settings sanity check in the python script.

I need to see if I can get it to bug out like it was previously.

Thanks,

Nate

[Author]

Posts