I can’t very well guess the
compressed size :)
It turns out this bug also happens if I
convert to UDRO and UDCO.
I don’t want to ship a writable
image, and not compressing it is an issue as we are downloading this client
over bandwidth constrained networks.
I guess I’ll just have to wait for a fix.
Oddly, this used to work fine. Then
at some point I got the “No welcome text in the installer”
bug. My fix at the time was to add a trailing newline to the file, and the
bug went away (I thought it was an installer bug). Now it is back, and
the file content and name don’t seem to make any difference (really, why
would they?).
Perhaps I’ll have to roll back my dev tools and OS version and see if I
can get it to work on an older tools configuration. Which would mean
building on one machine and packaging on another. How ugly is that…
David Litwin
BigFix, Inc.
From: Michael
Nickerson [mailto:email@hidden]
Sent: Tuesday, August 01, 2006
4:28 PM
To: David Litwin
Cc: email@hidden
Users
Subject: Re: Problems with hdiutil
On Aug 1, 2006, at 3:01 PM, David Litwin wrote:
Has anyone seen anything like this? It’s
completely baffling. If I can’t trust my disk image making tool,
how can I put my code out with any confidence?
David Litwin
BigFix, Inc.
Hey David, I tried out your script. It looks
like a bug with hdiutil. If you add -size with a value to the create
line, it'll work out correctly. I guess it's not correctly setting the
size and creating an invalid dmg file. I wasn't able to mount the
Writable.dmg file created by your script by double-clicking on it - it comes up
with an error dialog when I try.
If you're just using that script on the command line,
I suppose you could add in a portion to ask for the size. Otherwise, I'm
not entirely sure how you'd get the correct size value to use with it.