Home Forums Software InstaDMG Rev 387

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #379654
    rtrouton
    Participant

    I checked out Rev 387 and it looks like my InstallerChoices.xml file for my 10.6.3 installer disk image is now being ignored when I run InstaUp2Date. Anyone else seeing this problem?

    #379669
    dead2sin
    Participant

    I checked the SVN and it looks like Karl added support for specifying an installer choice file.

    Here is an example of how to use this functionality:

    http://code.google.com/p/instadmg/source/browse/trunk/AddOns/InstaUp2Date/CatalogFiles/base-template.catalog?spec=svn387&r=387

    Nate

    #379674
    rtrouton
    Participant

    I like the idea, but I’m having a hard time figuring out how to make it work. I’ve got my catalog file set up like this:

    [code]# Template for user-supplied catalog files

    #
    # Settings
    #

    Installer Choices File: /Volumes/Builder_10_6/instadmg-read-only/InstallerFiles/BaseOS/InstallerChoices.xml sha1:2f8a9e057b09658c376908c3549ada9c014d394a
    #Supporting Disc: tab

    #ISO Language Code:
    #Output Volume Name:
    #Output File Name:

    #include-file:

    include-file: 10.6_vanilla.catalog
    include-file: xcode.catalog
    include-file: clear-reg.catalog

    #
    # Sections
    #
    # Takes lines in the form:
    # tab tab tab [tab ]

    Apple Updates:

    System Settings:

    Third Party Software:

    Software Settings:
    [/code]

    When I run InstaUp2Date, I’m getting the following errors:

    [code]Parsing the catalog files for master10_6
    Installer Choices File: /Volumes/Builder_10_6/instadmg-read-only/InstallerFiles/BaseOS/InstallerChoices.xml – checksummed (189 Bytes) in less than one second (1.3 Megabytes/sec)Traceback (most recent call last):
    File “./instadmg-read-only/AddOns/InstaUp2Date/instaUp2Date.py”, line 716, in
    main()
    File “./instadmg-read-only/AddOns/InstaUp2Date/instaUp2Date.py”, line 662, in main
    thisController.parseCatalogFile()
    File “./instadmg-read-only/AddOns/InstaUp2Date/instaUp2Date.py”, line 266, in parseCatalogFile
    raise commonExceptions.InstallerChoicesFileException(‘Unable to find %s: %s (checksum: %s)’ % (settingLineMatch.group(“variableName”), settingLineMatch.group(“variableValue”), settingLineMatch.group(“fileChecksum”)), choicesFile=fileLocation, lineNumber=lineNumber)
    Resources.commonExceptions.InstallerChoicesFileException: Unable to find Installer Choices File: /Volumes/Builder_10_6/instadmg-read-only/InstallerFiles/BaseOS/InstallerChoices.xml (checksum: sha1:2f8a9e057b09658c376908c3549ada9c014d394a)[/code]

    Once I comment out the “Installer Choices File:” line, everything runs fine.

    Here’s my current InstallerChoices.xml file:

    [code]
    All_PrinterDrivers
    AdditionalFonts
    LanguageTranslations
    Rosetta
    QuickTimePlayer7
    [/code]

    #379675
    Allister Banks
    Participant

    Hey Mr. Trouton,

    Were you just leaving the installerChoices.xml file in the same folder as the baseOS and having it work before 387? It worked for me, at least as of 383. I’m running a test now-ish
    *EDIT*
    My test only confirms a lack of functionality of instaUp2Date in general, filed as issue 66 on instadmg.googlecode.com

    Allister

    #379677
    rtrouton
    Participant

    Correct, InstallerChoices.xml was previously in the same folder as the BaseOS and it had worked prior to 387. I’ve also tried build 388 and have the same issue.

    #379678
    dead2sin
    Participant

    I kept my InstallerChoices file in BaseOS despite my OS Disc being in InstallerDiscs and I didn’t notice it reinstalling the OS (It seemed to use the cache as usual). I’m not sure what the right answer is on this one, perhaps Larkost can clear it up for it 🙂

    Nate

    #379679
    dead2sin
    Participant

    I just checked my logs and it is installing OS X every run instead of caching and it is not using the InstallerChoices file.

    I specified an Installerchoices file in my 10.6_vanilla catalog and I’m doing another 2 builds to make sure that #1 It uses the installer choices (which it said it found at the beginning of the build, so I am sure that will work) and #2 I want to make sure on second run, it uses the cached image.

    Nate

    #379680
    Allister Banks
    Participant

    Hey Nate,

    Thanks for pushing ahead on clarifying the issue while we wait to hear back from Larkost.

    Mr. Trouton, could you please file an issue on googlecode separate from mine – I don’t have as cleanly reproducible an issue. Thanks,

    Allister

    #379681
    dead2sin
    Participant

    Its using the cached image again. It is back to working exactly how it should.

    OP, double check your syntax for specifying the InstallerChoices. Make sure its exactly like this:

    [code]Installer Choices File: /Users/admin/Desktop/InstaDMG1.6b2/InstallerFiles/InstallerChoices/InstallerChoicesNoRosetta.xml sha1:92ebd7ebdc4dd077a562e79ac2d4502dd966da5e
    [/code]

    Thats: Installer Choices file: Location Hash

    If there are some other spaces in there at the end or the beginning, etc, it might get cranky 🙂

    Nate

    #379682
    rtrouton
    Participant

    I went back and re-checked everything, and found my D’oh! mistake. I had edited my InstallerChoices.xml file and hadn’t re-run checksum.py on the file again. Sure enough, I got a new checksum when I re-ran checksum.py. Once I edited my catalog file (thanks dead2sin) and plugged in the new checksum, the error went away. I got a successful build run and I’m re-runnning it now to make sure that wasn’t a fluke.

Viewing 10 posts - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.

Comments are closed