December 2006 - Installer-dev

Installer Marking Unrelated Files as Obsolete
by Matt Willmore 14 Dec '06

14 Dec '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=HT1rz1VhFk2IZWRNUk1vwL6s1/QdcvV4cfWALd+r0CUt1RnTFAjr0x3D86C2pTPmTZSD6b8IQqB+lTa42VtqgrGkVdHpUjTQLXMDk+gSquxnKFb/vG3ofJ4f+T7BPDD1V94/eRr6YOy95E22+d24AjK27XLBjdqRsmLKlmJjXz8= We deploy software to clients with single packages via ARD 3. All clients are running 10.4.8 on a mix of PPC and Intel Mac's. In the past week we have noticed that the Microsoft Office 2004 directory (in /Applications) is being marked as obsolete by installer when either our Adobe CS 2 package or our KeyServer 2 packaged is being pushed (we've seen either one package or the other trigger the obsoleted remarks in install.log). What's more interesting is that this is not happening to every computer receiving packages; right now the count is 5 Mac's (mix of PPC and Intel). Even though most of Office can not be deleted ("directory not empty") the Office directory is gone as are the applications, and we have to push the package again. I have looked at both the Adobe and KeyServer packages in PackageMaker and in Pacifist and neither show any reference to Office at all. Can anyone think of a reason why this might be happening? Thanks in advance! Matt Willmore Engineering Computer Network Purdue University _______________________________________________ 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

Different runtime Installer behavior for same package
by Alex Sheh 14 Dec '06

14 Dec '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AccfxHS1NPI1R1OsQpqgxWNrg/LHxw== Thread-topic: Different runtime Installer behavior for same package _______________________________________________ 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

MetaPackage project, Authorization setting?
by Alex Sheh 14 Dec '06

14 Dec '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AccfxBd1cxQTd7yQRdGZ1VmyOl5t2w== Thread-topic: MetaPackage project, Authorization setting? _______________________________________________ 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

Manual installl works, auto doesn't on 10.4.8
by Craig Landrum 14 Dec '06

14 Dec '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com I have a very strange problem with a very simple install. For many revisions now, I have used PackageMaker to create an installer for my ScanTango scanning application. This has worked perfectly up until 10.4.8. The exhibited problem does not occur until the first time the application is run after installlation. At that time, it loads/unloads a series of a half-dozen or so code bundles that attempt to detect and talk to various models of USB-attached scanners that we support. The exhibited problem is that the application sometimes hangs when attempting to do this. I cannot recreate this here in the lab - it has only occured out "in the wild" to about 8-10 of my users. The problem ONLY occurs when the installer installs the application. The problem can be fixed by having the user manually unpack the "Archive.pax.gz" file in the installer to their Desktop and then dragging the application into the /Appplications folder. My PackageMaker project is set up as follows. I am building using PackageMaker 2.1 (10.4.7): Default location : /Applications Package Requirements: none Authentication : Adminstrator Post-Install Action: None Flags: Root Volume Only, Follow Symbolic Links (I've also tried Overwrite Directory Permissions with my app root in the package set to "root:admin" with the same result) No Scripts File Permissions: root:admin rwxrwxr-x No Locator definitions Default file filters for CVS stuff Identifier: com.mindwrap.scantango Version is 2.3 and has been steadily bumped each release NOTES: I had a user do an auto install and a manual-unpack install, then fire up Terminal, go to /Applications and do an "ls -lR ScanTango.app" to see exactly what was installed and the permissions. The ONLY visible difference between the two installs was that on the auto install, the user:group was root:admin and on the manual install it was <username>:admin. All files and permissions identical on both and all file sizes identical on both. Only the manual install would run correctly for those users reporting the problem (some users had no problem with the auto install). The only think that caught my eye was that the application contains two private frameworks. However, the link path is expressed slightly differntly on the two: ScanTango.app/Contents/Frameworks/ScanUSB.framework: total 16 lrwxr-xr-x 1 root admin 28 Dec 14 14:02 Resources -> ./Versions/Current/Resources lrwxr-xr-x 1 root admin 26 Dec 14 14:02 ScanUSB -> ./Versions/Current/ScanUSB drwxrwxr-x 4 root admin 136 Dec 14 14:02 Versions ScanTango.app/Contents/Frameworks/SyscanDll.framework: total 16 lrwxr-xr-x 1 root admin 26 Dec 14 14:02 Resources -> Versions/Current/Resources lrwxr-xr-x 1 root admin 26 Dec 14 14:02 SyscanDll -> Versions/Current/SyscanDll drwxrwxr-x 4 root admin 136 Dec 14 14:02 Versions We don't feel that this could cause any problems. This really feels like a permissions problem, but we can't seem to recreate it in the lab. Anyone else have any similar experiences or have suggestions? Feel free to download the installer from our website and play with it. www.scantango.com -- Craig Landrum Chief Technical Officer mindwrap, inc. Phone: (540) 675-3015 x 229 Fax: (540) 675-3130 email: craigl(a)mindwrap.com _______________________________________________ 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: Am I using PackageMaker incorrectly?
by John Daniel 12 Dec '06

12 Dec '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Dec 12, 2006, at 3:01 PM, Stéphane Sudre wrote: On lundi, décembre 11, 2006, at 11:28 PM, John Daniel wrote: John _______________________________________________ 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.… installer-dev'ers, After only a few trails and errors, I have packagemaker working the way I want and I'm quite happy with the results. However, the PackageMaker help and some Internet postings are saying that I may be doing some things incorrectly. So, here are my > questions: Do I have to set permissions before creating the package? Currently, I just package up all my files and set ownership and permissions with the postinstall/postupgrade script. This package runs with AdminAuthorization and creates root/wheel files in / Library and works perfectly. It seems to me that Root is the only uid that is the same on all systems. If you want to ensure that ownership and permissions are set appropriately, these scripts seem to be the only place to do it. Setting permissions in the postinstall or postupgrade script is not the best solution in theory. The reason behind this is that if we imagine that one day Disk Utility will also use Receipts in / Library/Receipts to repair permissions on disk, your package will describe incorrect permissions. Additionally, doing it this way, you can't use the option to only set the permissions of folders that do not exist. So for instance, if you're setting the permissions for /Library, you may not set the right permissions depending on the OS version. Is there a difference depending on OS version? If so, I could easily handle that in the script. What we really need is a plist file that tells the installer what the permissions should be. It could be 1) a specific user (mysql or root) or 2) the current user. It should use symbolic names instead of uid/ gid, which is what is going on now. I'm pretty convinced that anything being installed as root needs to have its permissions set beforehand, in the "traditional" way. That doesn't bother me much as root/wheel aren't going to be changing uid/ gid. I'm still not happy with the situation for installing as "current user". I will continue to use scripts to try to set permissions to "current user" instead of my 501. If the permissions ever get repaired, it will get screwed up. But, had I not used said scripts, it would have been screwed up like that from day one. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Am I using PackageMaker incorrectly?
by John Daniel 12 Dec '06

12 Dec '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Dec 11, 2006, at 5:22 PM, Frederik Seiffert wrote: John, John _______________________________________________ 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.… Do I have to set permissions before creating the package? Currently, I just package up all my files and set ownership and permissions with the postinstall/postupgrade script. This package runs with AdminAuthorization and creates root/wheel files in / Library and works perfectly. It seems to me that Root is the only uid that is the same on all systems. If you want to ensure that ownership and permissions are set appropriately, these scripts seem to be the only place to do it. You can set the permissions right in PackageMaker. In PackageMaker 2.1 click the "File Permissions" button in the contents pane of your package project. Using "Apply Recommendations" should give you a good starting point. But that is just setting permissions before creating the package. If user jblow with uid 503 installs something, it should be owned by jblow 503, not jdaniel 501. I really don't use the PackageMaker GUI at all anymore. It is so much more powerful from the command line. I have one project where I do set the permissions (to root) before creating the installer. In this case, I copy all my install files to a temporary folder, set them to root, create the package, then get rid of those root files. Otherwise, it really screws up CVS. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Am I using PackageMaker incorrectly?
by Stéphane Sudre 12 Dec '06

12 Dec '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On lundi, décembre 11, 2006, at 11:28 PM, John Daniel wrote: _______________________________________________ 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.… installer-dev'ers, After only a few trails and errors, I have packagemaker working the way I want and I'm quite happy with the results. However, the PackageMaker help and some Internet postings are saying that I may be doing some things incorrectly. So, here are my > questions: Do I have to set permissions before creating the package? Currently, I just package up all my files and set ownership and permissions with the postinstall/postupgrade script. This package runs with AdminAuthorization and creates root/wheel files in /Library and works perfectly. It seems to me that Root is the only uid that is the same on all systems. If you want to ensure that ownership and permissions are set appropriately, these scripts seem to be the only place to do it. Setting permissions in the postinstall or postupgrade script is not the best solution in theory. The reason behind this is that if we imagine that one day Disk Utility will also use Receipts in /Library/Receipts to repair permissions on disk, your package will describe incorrect permissions. Additionally, doing it this way, you can't use the option to only set the permissions of folders that do not exist. So for instance, if you're setting the permissions for /Library, you may not set the right permissions depending on the OS version. That being said, postinstall or postupgrade (but you could use postflight) used to be the only solution to set owner and group to root:wheel for StartupItems in /Library/StartupItems on 10.1 (and maybe 10.2). This email sent to site_archiver(a)lists.apple.com

1 0

Re: Am I using PackageMaker incorrectly?
by Frederik Seiffert 11 Dec '06

11 Dec '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com John, With the latest security update, there isn't any. Frederik _______________________________________________ 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.… Do I have to set permissions before creating the package? Currently, I just package up all my files and set ownership and permissions with the postinstall/postupgrade script. This package runs with AdminAuthorization and creates root/wheel files in /Library and works perfectly. It seems to me that Root is the only uid that is the same on all systems. If you want to ensure that ownership and permissions are set appropriately, these scripts seem to be the only place to do it. You can set the permissions right in PackageMaker. In PackageMaker 2.1 click the "File Permissions" button in the contents pane of your package project. Using "Apply Recommendations" should give you a good starting point. What is the difference between Administrator and Root? I have one installer that runs as Administrator and is able to install software into /Library with no problem. I created a test installer and ran it under AdminAuthorization, RootAuthorization, and noAuthorization. I can find no difference between AdminAuthorization and RootAuthorization. This email sent to site_archiver(a)lists.apple.com

1 0

Am I using PackageMaker incorrectly?
by John Daniel 11 Dec '06

11 Dec '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thanks, John _______________________________________________ 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.… installer-dev'ers, After only a few trails and errors, I have packagemaker working the way I want and I'm quite happy with the results. However, the PackageMaker help and some Internet postings are saying that I may be doing some things incorrectly. So, here are my questions: Do I have to set permissions before creating the package? Currently, I just package up all my files and set ownership and permissions with the postinstall/postupgrade script. This package runs with AdminAuthorization and creates root/wheel files in /Library and works perfectly. It seems to me that Root is the only uid that is the same on all systems. If you want to ensure that ownership and permissions are set appropriately, these scripts seem to be the only place to do it. What is the difference between Administrator and Root? I have one installer that runs as Administrator and is able to install software into /Library with no problem. I created a test installer and ran it under AdminAuthorization, RootAuthorization, and noAuthorization. I can find no difference between AdminAuthorization and RootAuthorization. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Providing cancel button in installer package
by Bill Coderre 11 Dec '06

11 Dec '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com _______________________________________________ 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