[jeffbearer]

That was my fear. And changing it on network config sounds like too many moving parts.

I guess I’ll consider using DNS views based on subnet to do the dns trickery if pretending to be apple, but not for VPN users.

[jeffbearer]

Apparently I needed a reboot it worked today where it wasn’t working last week.

[jeffbearer]

I’m having continued problems with r383. It’s in findInstallerDisk.py where it says it can’t find my base dmg file. I thought maybe it was because it was a legacy image, so I ripped a new one but i’m having very similar problem Here is where it’s getting lost.

[code] # find the item that matches the frontmost allowedBuilds item
for thisItem in innerSearchItems:
print(‘\n\n ‘ + thisItem + ‘ \n\n’)
baseImageCandidate = None

if hasattr(thisItem, ‘isContainerType’):
baseImageCandidate = thisItem
print “–a–”
else:
print “–b–”
try:
print “–c–”
baseImageCandidate = containerController.newContainerForPath(thisItem)
except:
print “–d–”
continue

if not baseImageCandidate.isContainerType(‘dmg’):
print “–e–”
continue
[/code]
And here is the output:
[code]
/Users/jeff/instadmg/InstallerFiles/InstallerDiscs/.svn
–b–
–c–
–e–
/Users/jeff/instadmg/InstallerFiles/InstallerDiscs/MacOS X Client 10.6 10A432.dmg
–b–
–c–
–e–
/Users/jeff/instadmg/InstallerFiles/BaseOS/.DS_Store
–b–
–c–
–e–
/Users/jeff/instadmg/InstallerFiles/BaseOS/.svn
–b–
–c–
–e–
/Users/jeff/instadmg/InstallerFiles/BaseOS/InstallerChoices.xml
–b–
–c–
–e–

[/code]
It looks like the: [code] if not baseImageCandidate.isContainerType(‘dmg’):[/code] is always evaluating true even when it hits the dmg file. However I’m stymied at trying to dig into isContainerType.

That installer disk was generated with importDisk.py -a

[jeffbearer]

Gotcha, The question I have is that the installer command that you fixed to point to the generic InstallerChoices.xml to be used by all packages.

[code]instadmg/InstallerFiles/InstaUp2DatePackages/InstallerChoices.xml[/code]

is the same functionality that instadmg used to have. In looking at the code I thought that perhaps the functionality was upgraded and looking inside the package directory for the InstallerChoices.xml was a new valid operation.

[code]instadmg/InstallerFiles/InstaUp2DatePackages/clearReg.pkg/InstallerChoices.xml[/code]

But after looking at r302 I guess that was just a mistake? Maybe what is the new code is the section above that does not require the InstallerChoices.xml at all. Thanks for the help.

[jeffbearer]

10.6.2 on the build machine and the image.

[jeffbearer]

Please forgive me, this is indeed a duplicate of the other recent code post. I didn’t grok what he was seeing till just now.

Here is the meat from my debug log:

[code]PHASE:Preparing Xcode…
IFPKInstallElement (18 packages)
An exception was thrown from the install queue while running IFPKInstallElement. IFPKInstallElementException. Package PKLeopardPackage cannot be installed at /tmp/InstaDMG_temp_folder.VisiwP/mount_point.B2QZKy/Developer using destination path /private/tmp/InstaDMG_temp_folder.VisiwP/mount_point.B2QZKy/Developer.
Install failed: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
The install failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)

Unmounted the Package DMG image from /private/tmp/InstaDMG_temp_folder.VisiwP/mount_point.ffXux2
[/code]

[Author]

Posts