package issues

[Janowski]

I have a package that was created in packagemaker that isn't installing via casper remote or policy in the JSS.
This is my first packagemaker project, so it's possible that I made a beginners mistake.

having said that, the package successfully installs via ARD or when run locally on the client computer.

The JSS reports the following when it tries to run it:

Copying Acrobat X Kohl's Installer.pkg...
sh: -c: line 0: unexpected EOF while looking for matching `''
sh: -c: line 1: syntax error: unexpected end of file Installing Acrobat X Kohl's Installer.pkg...
sh: -c: line 0: unexpected EOF while looking for matching `''
sh: -c: line 1: syntax error: unexpected end of file Installation failed. The installer reported: sh: -c: line 0: unexpected EOF while looking for matching `''
sh: -c: line 1: syntax error: unexpected end of file
sh: -c: line 0: unexpected EOF while looking for matching `''
sh: -c: line 1: syntax error: unexpected end of file

The package consists of 2 'payload' files and one script that runs after the files are copied to the machine.

I have tried fixing permissions on our JSS in the file sharing section of the JSS Setup Utility, Indexing this package in casper admin and forcing the policy to run over afp instead of http. Haven't been able to make any headway.

My other option is to deploy the 2 payload files via .dmg and then run the script through policy in the JSS. I wanted the files to be put in /private/tmp. I created a dmg in composer to that effect, but i can't get our JSS to push them there.

Anyone have any suggestions? Maybe I just need to deploy somewhere other than /private/tmp?

ben janowski
Senior Macintosh Support Technician
Kohl's Mac Support Team
262.703.1396 | benjamin.janowski at kohls.com

[jarednichols]

I don't know what you're doing that's so custom, but in our case, we didn't want to install the browser plugin for Acrobat X Pro. So we modified the distribution file inside of the pkg installer so that it wasn't active by default (see my post earlier today about Office 2011 packaging… Same process).

J
--
Jared F. Nichols
Desktop Engineer, Client Services
Information Services Department
MIT Lincoln Laboratory
244 Wood Street
Lexington, Massachusetts 02420
781.981.5436

[#3]

You have an apostrophe in your package's name. That trips up the way the
installer is called.

Best,

Brandt

--

J. Brandt Buckley
Systems Integration Engineer
CRBS

brandt at ucsd.edu http://crbs.ucsd.edu
P: +1 858 822 0743 F: +1 858 524 7497

Center for Research in Biological Systems
University of California, San Diego

9500 Gilman Drive
Basic Sciences Building #1000
La Jolla, Ca. 92093-0608

[Janowski]

ah, man. you are TOTALLY right.

thanks for the tip!

ben janowski
Senior Macintosh Support Technician
Kohl's Mac Support Team
262.703.1396 | benjamin.janowski at kohls.com

[tlarkin]

Yes, well I always abide by the old school Unix philosophy. No spaces,
no special characters. I name my packages like this...

packagename_version_date