• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Copying an app bundle on OS X 10.10 creates an invalid bundle?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Copying an app bundle on OS X 10.10 creates an invalid bundle?


  • Subject: Re: Copying an app bundle on OS X 10.10 creates an invalid bundle?
  • From: Dan McCombs <email@hidden>
  • Date: Thu, 21 Aug 2014 16:05:56 -0400

Thanks for the suggestions everyone. On Linux with GNU cp, -r and -R are equivalent so I never thought to check that.

cp -R works, so now I need to figure out what Python's distutils.file_util.copy_file is missing I suppose, as that's where my build is breaking - or just replace the call. Though I'm still wondering what changed between 10.9 and 10.10 in codesign to make it get tripped up by this.

-Dan



Dyn logo, Dyn.com           Dyn facebook account   Dyn LinkedIn account

Dan McCombs  / Senior Software Engineer 
 603 296 1568      @danmccombs 



On Thu, Aug 21, 2014 at 11:46 AM, Akis Kesoglou <email@hidden> wrote:
You most likely need “$ cp -pR”. The capital “R” is for recursive copy and the “p” flag is for preserving file dates, permissions, extended attributes and more (check "man cp").


On 21 Αυγ 2014, at 15:12, Dan McCombs <email@hidden> wrote:

Hi all,

On OS X 10.10 Preview 5, copying an app bundle on the command line (with something like cp -r) results in an app bundle copy that isn't recognized as an app bundle. This was not the case on previous OS versions.

Trying to codesign such a copy results in an errror stating:

"bundle format unrecognized, invalid, or unsuitable"

A diff shows no differences between the two app bundle directories, nor are there any extended attributes on any files in either app bundle that xattr can see. Moving a bundle with mv does not invalidate a bundle, nor does copying via Finder, so there seems to be some sort of magic going on with Finder that normal command line tools are not capable of.

Has anyone else ran into this? Any idea what needs to be done to the copy to make it a valid bundle? Is this a bug in Yosemite?

Take care,

-Dan

Dyn logo, Dyn.com           Dyn facebook account   Dyn LinkedIn account

Dan McCombs  / Senior Software Engineer 
 603 296 1568      @danmccombs 

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)

This email sent to email@hidden


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Copying an app bundle on OS X 10.10 creates an invalid bundle? (From: Dan McCombs <email@hidden>)
 >Re: Copying an app bundle on OS X 10.10 creates an invalid bundle? (From: Akis Kesoglou <email@hidden>)

  • Prev by Date: Re: Copying an app bundle on OS X 10.10 creates an invalid bundle?
  • Next by Date: Where are my simulators gone?
  • Previous by thread: Re: Copying an app bundle on OS X 10.10 creates an invalid bundle?
  • Next by thread: Where are my simulators gone?
  • Index(es):
    • Date
    • Thread