November 2004 - Installer-dev

Re: PackageMaker bug?
by Stéphane Sudre 24 Nov '04

24 Nov '04

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On mercredi, novembre 17, 2004, at 09:36 PM, Stéphane Sudre wrote: [...] I will try to see if I'm seeing the problem on a 10.3 system. After tests on OS X 10.3.5, I'm seeing this bug too. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… I had a look at this DiskManagementTool tool and it looks like it can does a bunch of things. A class-dump and a quick inspection of the Frameworks resources seem to indicate that it can be used to: - fix permissions: this was my first idea on what it's trying to do in the package building process. Yet a simple test with a wrong permissions on /Applications shows this is not the case. The Hints.plist file is really interesting from a security point of view. - deal with bom in a package - do something with a BOM enumerator. I'm wondering what's the real goal of calling DiskManagementTool (via a NSTask) and if it's really doing something. This email sent to site_archiver(a)lists.apple.com

1 0

Re: PackageMaker bug?
by Stéphane Sudre 17 Nov '04

17 Nov '04

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Are you sure it's PackageMaker which is launching it? Is there not a part of your script building a Disk Image? Side question: how do you build a meta-package from the commande line using PackageMaker? I will try to see if I'm seeing the problem on a 10.3 system. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… On mercredi, novembre 17, 2004, at 03:45 PM, Huyler, Christopher M wrote: The script does create a disk image but I added a few lines to count the number of running DiskManagementTool processes and print the value before and after each call to PackageMaker. The value printed increases after the call so I am positive that is where it is coming from. However, it inconsistent as to which call causes it. Sometimes its only one call, other times its all four calls. Here is a snippit of shell script that I use to create the meta-package: PACKAGEMAKER="/Developer/Applications/Utilities/PackageMaker.app/ Contents/MacOS/PackageMaker" PACKAGE_DEST="/Users/huych02/package_stage" PACKAGE_FILES="/Users/huych02/dev/Mac/package" mkdir -p "$PACKAGE_DEST" echo "Processes before : `ps -xalww | grep DiskMan | wc -l`" $PACKAGEMAKER -build \ -p "$PACKAGE_DEST/MetaPackage.mpkg" \ -f "$PACKAGE_FILES/MetaRoot" \ -r "$PACKAGE_FILES/MetaResources" \ -i "$PACKAGE_FILES/MetaPackageInfo.plist" \ -d "$PACKAGE_FILES/MetaPackageDescription.plist" echo "Processes after : `ps -xalww | grep DiskMan | wc -l`" The Info.plist files and Description.plist files were generated using the PackageMaker gui. The MetaRoot folder is empty since a meta-package has no files of its own (PackageMaker doesn't work unless a folder is specified). If I have time today, I will make a test script and package that duplicates the possible bug, zip it up, and send it to you. I tried creating both a package and a metapackage using this tool on Mac OS X 10.2.8 (I don't think it has changed in 10.3.x) and I didn't get the additional processes. BTW, using the command line to create a metapackage this way has a side effect from what I can see, this may require some additional work: The metapackage contains .bom, .pax[.gz] and .sizes files which are useless. This email sent to site_archiver(a)lists.apple.com

1 0

RE: PackageMaker bug?
by Huyler, Christopher M 17 Nov '04

17 Nov '04

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AcTMeOmLtdSEi+6fSNy1cZlqFk0LswAN/4TA Thread-topic: PackageMaker bug? > Are you sure it's PackageMaker which is launching it? Is there not a > part of your script building a Disk Image? The script does create a disk image but I added a few lines to count the number of running DiskManagementTool processes and print the value before and after each call to PackageMaker. The value printed increases after the call so I am positive that is where it is coming from. However, it inconsistent as to which call causes it. Sometimes its only one call, other times its all four calls. > Side question: how do you build a meta-package from the commande line > using PackageMaker? Here is a snippit of shell script that I use to create the meta-package: PACKAGEMAKER="/Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/PackageMaker" PACKAGE_DEST="/Users/huych02/package_stage" PACKAGE_FILES="/Users/huych02/dev/Mac/package" mkdir -p "$PACKAGE_DEST" echo "Processes before : `ps -xalww | grep DiskMan | wc -l`" $PACKAGEMAKER -build \ -p "$PACKAGE_DEST/MetaPackage.mpkg" \ -f "$PACKAGE_FILES/MetaRoot" \ -r "$PACKAGE_FILES/MetaResources" \ -i "$PACKAGE_FILES/MetaPackageInfo.plist" \ -d "$PACKAGE_FILES/MetaPackageDescription.plist" echo "Processes after : `ps -xalww | grep DiskMan | wc -l`" The Info.plist files and Description.plist files were generated using the PackageMaker gui. The MetaRoot folder is empty since a meta-package has no files of its own (PackageMaker doesn't work unless a folder is specified). If I have time today, I will make a test script and package that duplicates the possible bug, zip it up, and send it to you. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: PackageMaker bug?
by Stéphane Sudre 17 Nov '04

17 Nov '04

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On lundi, novembre 15, 2004, at 07:26 PM, Huyler, Christopher M wrote: I tested this on my desktop machine and the same behavior occurs. The server is running 10.3.5 and my desktop is running 10.3.6. Both machines have Xcode 1.5 installed. According to Macslash, it verifies and repairs disk permissions. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… Our build server was acting funky this morning so I did a ps to see what processes were running. To my surprise there were over 100 instances of "DiskManagementTool -uuid XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" running. I traced this to our build scripts which call PackageMaker from the command line. We build two packages and two meta-packages using the CLI to PackageMaker. 1-4 of these DiskManagementTool processes are left behind each time I run our build. After putting some debug statements in, it appears that there is no consistency to which calls to PackageMaker cause this behavior. Sometimes it happens, sometimes it doesn't. Can anyone shed some light on this? What does this tool do? Why is PackageMaker calling it? Are you sure it's PackageMaker which is launching it? Is there not a part of your script building a Disk Image? Side question: how do you build a meta-package from the commande line using PackageMaker? This email sent to site_archiver(a)lists.apple.com

1 0

PackageMaker bug?
by Huyler, Christopher M 15 Nov '04

15 Nov '04

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AcTLQJGC0+q15r/hQZCB6vpdM3437Q== Thread-topic: PackageMaker bug? Our build server was acting funky this morning so I did a ps to see what processes were running. To my surprise there were over 100 instances of "DiskManagementTool -uuid XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" running. I traced this to our build scripts which call PackageMaker from the command line. We build two packages and two meta-packages using the CLI to PackageMaker. 1-4 of these DiskManagementTool processes are left behind each time I run our build. After putting some debug statements in, it appears that there is no consistency to which calls to PackageMaker cause this behavior. Sometimes it happens, sometimes it doesn't. I tested this on my desktop machine and the same behavior occurs. The server is running 10.3.5 and my desktop is running 10.3.6. Both machines have Xcode 1.5 installed. Can anyone shed some light on this? What does this tool do? Why is PackageMaker calling it? Why is it locking up? Is this a bug? -- Christopher Huyler Computer Associates Intl. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

RE: Can't install package. More info.
by Pavel Golovko 11 Nov '04

11 Nov '04

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AcTHXsZtkP97MwnFQY+5vunTLcgZoQAnNO5w Thread-topic: Can't install package. More info. Thank you Stephane. It works fine! :) Best regards, Pavel. -----Original Message----- From: Stephane Sudre [mailto:ssudre2@wanadoo.fr] Sent: Wednesday, November 10, 2004 10:49 PM To: Pavel Golovko Cc: installer-dev(a)lists.apple.com Subject: Re: Can't install package. More info. On mercredi, novembre 10, 2004, at 10:05 AM, Pavel Golovko wrote: > Thank you Stephane. > It happens on the systems where there is only one partition and > doesn't happen on the system where more than one partition. > Apple guys, or anybody else, could you tell me please, what is it? Is > it bug of Installer.app or not? > Our tech support will have many problems if we don't fix this bug. Let's suppose it's a bug in Installer.app. Maybe it can be worked around. What I would try is to create a simple installer and see what happens when: a) the IFPkgFlagRootVolumeOnly is set to false b) the IFPkgFlagRootVolumeOnly is set to false and a VolumeCheck script is used. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Can't install package. More info.
by Stéphane Sudre 10 Nov '04

10 Nov '04

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On mercredi, novembre 10, 2004, at 10:05 AM, Pavel Golovko wrote: a) the IFPkgFlagRootVolumeOnly is set to false _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… Thank you Stephane. It happens on the systems where there is only one partition and doesn't happen on the system where more than one partition. Apple guys, or anybody else, could you tell me please, what is it? Is it bug of Installer.app or not? Our tech support will have many problems if we don't fix this bug. Let's suppose it's a bug in Installer.app. Maybe it can be worked around. What I would try is to create a simple installer and see what happens when: b) the IFPkgFlagRootVolumeOnly is set to false and a VolumeCheck script is used. This email sent to site_archiver(a)lists.apple.com

1 0

Can't install package. More info.
by Pavel Golovko 10 Nov '04

10 Nov '04

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AcTGnD/AA4uM27qDREmWa3QZNgBnkAAZcMaQ Thread-topic: Can't install package. Thank you Stephane. It happens on the systems where there is only one partition and doesn't happen on the system where more than one partition. Apple guys, or anybody else, could you tell me please, what is it? Is it bug of Installer.app or not? Our tech support will have many problems if we don't fix this bug. Thank you in advance. Regards. Pavel. -----Original Message----- From: Stephane Sudre [mailto:ssudre2@wanadoo.fr] Sent: Tuesday, November 09, 2004 11:36 PM To: Pavel Golovko Cc: installer-dev(a)lists.apple.com Subject: Re: Can't install package. On mardi, novembre 9, 2004, at 04:38 PM, Pavel Golovko wrote: > Hello everybody! > > I try to install my installation package on two computers (both under > MAC OS X 10.2.8). > On the one computer this complete successfully, but on the other i > have the following problem: First time I have to select a partition > for installing, I can't select it.My partition is disabled. If I go > one step back and then forward to the same step, then I can select the > partition. What is the problem? > > This is a part of my plist file > > <key>IFPkgFlagAllowBackRev</key> > <false/> > [...] I tend to believe it's a bug in Installer.app. I've seen it once on a PowerMac G4 1 GHz MP (with Mac OS X 10.2.6 or an earlier version) but I thought it got fixed in the latest releases of Mac OS X 10.2. I've never seen it on any other machine. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: PackageMaker command line/meta pkg/Panther
by John Rosasco 09 Nov '04

09 Nov '04

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com works great. thanks Stephane. On Nov 9, 2004, at 12:26 PM, Stéphane Sudre wrote: On lundi, novembre 8, 2004, at 11:27 PM, John Rosasco wrote: This is because it was just to give an idea ;) To go into details, a metapackage once built looks like this: MyMetapackage.mpkg -+- Contents -+- PkgInfo | +- Info.plist | +- Resources -+- Description.plist | +- [MyMetapackage.info] | +- [MyMetapackage.list] | + ... build -+- .containedPkgs -+- Your Packages | +- MyMetapackage.mpkg Now, if you want the solution involving a 3rd party tool: Hope it helps. -- Stephane _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… mkdir $HOME/build/ cp -R Meta/*.pkg $HOME/build/ mkdir $HOME/build/MyMetapackage.mpkg mkdir $HOME/build/MyMetapackage/Contents cp Info.plist $HOME/build/MyMetapackage/Contents/ ##echo pmkrpkg1 > $HOME/build/MyMetapackage/Contents/PkgInfo ## As this puts a 0, you need to copy a file instead cp -R resources $HOME/build/MyMetapackage/Contents/Resources cp Description.plist $HOME/build/MyMetapackage/Contents/Resources/ How is it that this can hide the packages ? Right now, given my Info.plist file as described above, it doesn't appear possible that these steps could produce a meta-package that would work with my Info.plist file or hide the packages. Items in [] are optional and used for Mac OS X < 10.1 compatibility ... represents .lproj folders, scripts, and additional resources (background picture), etc... So if you already have the Info.plist and the Description.plist file and you don't care about 10.1 compatibility (which you wouldn't get anyway using PackageMaker from the UI last time I checked), what you just have to do is build the file hierarchy yourself. Since you want to put the Packages in a .containedPkgs folder, your hierarchy would look like this ("build" is a temporary folder I think it's wise to create): As I'm not a king of shell scripts (but I think it can be done just via a shell script): 1) Create the build folder 2) Create the .containedPkgs within the build folder 3) Copy your Packages in the .containedPkgs folder 4) Create the MyMetapackage.mpkg folder 5) Create the Contents folder within the MyMetapackage.mpkg folder 6) Copy a PkgInfo file from a Metapackage you built manually in the Contents folder 7) Copy the Info.plist in the Contents folder 8) Copy the Resources folder in the Contents folder 9) Copy the Description.plist file in the Resources folder 1) Download Iceberg on VersionTracker 2) Create a new Metapackage project 3) Add your documents, settings and all (if you have a .pmsm file, you can import it to avoid steps 2 and 3). 4) Drag and Drop your built packages in the Components section 5) Save 6) Call from the command line: freeze /the_path/to/your/Iceberg/Project.packproj But I still think the shell solution is easier in your case if you don't care about 10.1 compatibility. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Can't install package.
by Stéphane Sudre 09 Nov '04

09 Nov '04

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On mardi, novembre 9, 2004, at 04:38 PM, Pavel Golovko wrote: Hello everybody! This is a part of my plist file <key>IFPkgFlagAllowBackRev</key> <false/> [...] I've never seen it on any other machine. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… I try to install my installation package on two computers (both under MAC OS X 10.2.8). On the one computer this complete successfully, but on the other i have the following problem: First time I have to select a partition for installing, I can't select it.My partition is disabled. If I go one step back and then forward to the same step, then I can select the partition. What is the problem? I tend to believe it's a bug in Installer.app. I've seen it once on a PowerMac G4 1 GHz MP (with Mac OS X 10.2.6 or an earlier version) but I thought it got fixed in the latest releases of Mac OS X 10.2. This email sent to site_archiver(a)lists.apple.com

1 0