search

keeleysam / instadmg

Automatically exported from code.google.com/p/instadmg
0 stars 0 forks source link

InstaUp2Date, rev 295, HTTP DMG work, local pkg files do not #38

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What is the expected output? What do you see instead?

dmg based files work just fine it seems (at least http created dmg files or 
cached dmg files) but 
pkg / mpkg files fail.  

What version of InstaDMG are you running? What revision number (this should
be the second line of your package log)?
rev295

What OS are you running on (booted from)?
10.6.3

What OS are you installing?
10.6.3

Please provide any additional information below.

Original issue reported on code.google.com by hkim...@gmail.com on 11 May 2010 at 9:20

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I can confirm that this issue has been happening since rev 277, ever since the
symlinks for the folders have replaced the true folders, at around the same 
time, it
appears to have been creating all these files and folders(symlinks) in a /tmp.  
 So I
am not sure what is happening to and in the /tmp area, because it is gone when 
the
script is done.
     However, I have also placed the folders as aliases and tried to run instadmg by
itself (no instaUp2Date) and had the same problems.   If I run InstaUp2Date (no
--process) and then replace the folder symlinks with real folders, and real 
files
inside, and then run InstaDMG it runs just fine.

Thanks,
Steven Stuart

Original comment by sgstu...@pacbell.net on 14 May 2010 at 8:27

GoogleCodeExporter commented 9 years ago 
should be fixed as of rev300 - tested pkg's, DMG's, a mpkg bundled with an 
installerchoices.xml file, all work in the two default 
locations(Caches/instaup2date and InstallerFiles/instaup2datePackages)

Original comment by allister...@gtempaccount.com on 8 Jun 2010 at 11:34