Composer installing in /root/applications

bazcurtis
New Contributor III

Hi,

I have made a Firefox package via Composer 8.5.2. I have tried pkg and dmg. I have used the drag and drop method and the built in diffs. Every time I try and install the package it installs it in /root/applications and not /applications. What have I missed?

Cheers

Michael

9 REPLIES 9

mrowell
Contributor

Michael,

I've seen this in Composer 8.5.2. I haven't tested it definitively yet, but I think it occurs when I rename the package before building.

Are you renaming the packages before building them?
Once you rename the package, try quiting Composer and re-opening it before building the package.

Marcus

natkins
New Contributor III

I can confirm this with Composer 8.52 and Firefox 10.0.4esr.

Package created by dragging /Applications/Firefox.app into Composer.

If I rename the Package before hitting "Build as DMG", the DMG has the folders: ROOT, Scripts, Settings, Snapshots.

If I do NOT rename the Package before hitting "Build as DMG", the DMG has the folder: /Applications only.

nkalister
Valued Contributor

i'm having this as well if I build as a flat package. If I switch the preference in Composer to turn off flat packages, the same source creates a package that installs to the correct path.
I'm not renaming anything.

bazcurtis
New Contributor III

I also am deleting the users folder and the library folder. I am renaming the package firefox_12

Cheers

Michael

nkalister
Valued Contributor

and today I'm unable to repro the issue for casper support. strange.

tkimpton
Valued Contributor II

Same with me Nick. I had the same thing but now can't reproduce. I'm sticking on 8.51 for now

rlandgraf
Contributor

I have also noticed this problem I was using the Adobe CS4 experimental pre-installed software in composer. When I tried to rename it to call it Adobe CS4 design premium, it all installed to ROOT/Applications. I am currently trying it with out renaming in to see what happens.

Update: After further testing it appears to just happen when you rename the package in Composer. If you rename it on the Desktop or wherever it is saved before copying it to casper admin it seems to work fine.

Hope they fix this in the next rev.

jake
Contributor II
Contributor II

Hi Everyone -

Thank you for the feedback. This issue has been addressed in an upcoming release. The defect number to reference in the release notes is D-002856.

Thanks!

donmontalvo
Esteemed Contributor III

Any ETA when this issue will be resolved? :)

UPDATE: Our JAMF Buddy hooked us up with Composer 8.51 to tie us over until 8.53 is released.

--
https://donmontalvo.com