-
-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Symlinks not preserved #112
Comments
Sounds like a bug. I'll try to fix it asap. |
Ok, small update:
|
@chrispcampbell Please try pre-release https://github.com/blender/Rome/releases/tag/v0.14.0.36 I haven't tried to build but the contents of the archive seem to preserve symlinks |
@chrispcampbell any feedback on this? |
Thanks for the fix, I will try it out today and will let you know! |
@blender I tested with v0.14.0.36. The good news is that it appears to partially preserve symlinks when doing a However, when I clear out my
Then, testing the upload to an empty Rome cache:
Next, I moved the
It's worth noting that I see similar CRC-related messages when I try to unzip the thing from the command line:
|
I think I know why. Thanks for testing. Back on it. |
please try https://github.com/blender/Rome/releases/tag/v0.14.0.37 I have fixed CRC32 errros and I see no issue with the upload/download flow. Command line unzipping is clean too. |
@blender |
@blender I just tried again and can confirm that |
@blender Here's the output of the
And a listing of the unzipped content:
Looks like it could be a permissions issue? |
Strange. I'll investigate. |
@blender Have you had a chance to look into the permissions issue? |
Yes, I have addressed it in the zip library jgm/zip-archive#39. Will make a build asap.
|
@chrispcampbell here you go https://github.com/blender/Rome/releases/tag/v0.14.0.38 I have tested:
Let me know if it works for you as well and I will make a full release |
@blender I tried v0.14.0.38 and can confirm that everything appears to be working correctly now. |
Thank you for the patience! I'll make remove the draft tag from the release and update brew too. |
Issue
This issue sounds similar to #106, but that ticket seemed to cover a different scenario, so I figured I'd file this as a separate issue.
I just updated our macOS build to use Rome and found that the build would break in code signing, but only in the case where binaries are copied in from Rome's local cache. (The build was successful when using artifacts produced directly by Carthage.) I discovered that the frameworks produced by Carthage contain symlinks, for example:
After a
rome upload
step, if I unzip the relevant file from the Rome cache, I see that the symlinks are no longer present:So if later I use
rome download
, theCarthage/Build
directory will be populated with the framework(s) that don't contain symlinks.This causes
codesign
to fail later with a "bundle format is ambiguous" error, which is described here:https://developer.apple.com/library/content/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919-CH1-TNTAG313
"Perhaps a framework was copied incorrectly so the symlinks it contained were converted to normal files."
The relevant portion of our
Cartfile.resolved
:And our
Romefile
:Rome version: 0.13.1.35
OS and version: macOS 10.12.6
The text was updated successfully, but these errors were encountered: