Skip to main content
Answer

Composer flat package problem

  • May 10, 2012
  • 9 replies
  • 44 views
N
Forum|alt.badge.img+19

I'm having problems with composer's flat packages. I've always used regular pkg's in the past, but I'm converting to SMB shares for Casper, so I thought I'd start switching over to DMG and flat packages to simplify replication.
So, my first test flat package was very simple- Firefox 12. I have an existing source for a old-style pkg for Firefox 12 already in Composer, so I clicked the preference to enable building flat pkg's, and had composer generate a new package. Ran it, and the Firefox app installed to /ROOT/Applications instead of /Applications.
So, I created a new firefox package from scratch- dragged firefox from /Applications into the composer window, checked permissions, and built it again . . . same results- the file is installed to /ROOT/Applications.
So, just to make sure I'm not insane, I switched the Composer preference back to building old-school pkgs. Generated Firefox's pkg again with no other changes, and it installs to /Applications as it should.

I ask you, jamfnation- what's the deal with composer and flat pkgs? :)

Best answer by CasperSally

I saw issue myself today. I closed Composer and reopened and it seemed to go away but is a pain.

    9 replies

    T
    Forum|alt.badge.img+21
    • tkimpton
    • Honored Contributor
    • May 13, 2012

    I recently noticed the same problem. Please report it to Jamf so they can look into it. From the first few hours of Composer 8.52 and the problems I experienced I went back to 8.51

    M
    Forum|alt.badge.img+20
    • Matt11
    • Valued Contributor
    • May 31, 2012

    I am having the same issues right now with the /ROOT issue.

    C
    Forum|alt.badge.img+17
    • CasperSally
    • Honored Contributor
    • Answer
    • May 31, 2012

    I saw issue myself today. I closed Composer and reopened and it seemed to go away but is a pain.

    N
    Forum|alt.badge.img+19
    • nkalister
    • Author
    • Contributor
    • May 31, 2012

    yep, I'm having the same results as CasperSally- if I quit and re-launch composer after adding the source but before generating the package, then the generated package installs correctly.

    @tkimpton: I did report this to casper support, they're working on it.

    J
    Forum|alt.badge.img+11
    • jake11
    • Employee
    • May 31, 2012

    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!

    M
    Forum|alt.badge.img+9
    • myronjoffe
    • Valued Contributor
    • September 12, 2012

    Im having the same issue in 8.52 composer. The workaround CasperSally speaks about does work but what is the solution?

    J
    Forum|alt.badge.img+24
    • jarednichols
    • Valued Contributor
    • September 12, 2012

    Update to 8.6

    M
    Forum|alt.badge.img+9
    • myronjoffe
    • Valued Contributor
    • September 12, 2012

    Thanks Jared. No caveats when using 8.6 composer with 8.52 JSS?

    mm2270
    Forum|alt.badge.img+24
    • mm2270
    • Legendary Contributor
    • September 12, 2012

    There shouldn't be. Composer is essentially a standalone app that has no connection to your JSS. You can use any version that works for you to create your packages. 8.6 does resolve the issue outlined here so go for it. You can always keep the older 8.5.2 version around as well in case you're concerned.

    Terms & ConditionsCookie settingsAccessibility statement