Skip to content
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

Dangling symlinks prevent cargo publish #271

Open
clehner opened this issue Mar 3, 2022 · 0 comments
Open

Dangling symlinks prevent cargo publish #271

clehner opened this issue Mar 3, 2022 · 0 comments
Labels
developer experience Make nicer and easier to use for developers

Comments

@clehner
Copy link
Contributor

clehner commented Mar 3, 2022

The following files in this repo are symlinks to build artifacts:

  • lib/android/didkit/src/main/jniLibs/arm64-v8a/libdidkit.so
  • lib/android/didkit/src/main/jniLibs/armeabi-v7a/libdidkit.so
  • lib/android/didkit/src/main/jniLibs/x86/libdidkit.so
  • lib/android/didkit/src/main/jniLibs/x86_64/libdidkit.so
  • lib/flutter/android/src/main/jniLibs/arm64-v8a/libdidkit.so
  • lib/flutter/android/src/main/jniLibs/armeabi-v7a/libdidkit.so
  • lib/flutter/android/src/main/jniLibs/x86_64/libdidkit.so
  • lib/flutter/ios/libdidkit.a
  • lib/flutter/libdidkit.dylib
  • lib/flutter/libdidkit.so
  • lib/ios/libdidkit.a

If the targets of these symlinks are not present, publishing fails, e.g.:

$ cargo publish --dry-run --manifest-path lib/Cargo.toml
    Updating crates.io index
   Packaging didkit v0.4.0 (/home/cel/src/didkit-release/lib)
error: failed to prepare local package for uploading

Caused by:
  failed to open for archiving: `/home/cel/src/didkit-release/lib/android/didkit/libs/didkit.jar`
Caused by:
  No such file or directory (os error 2)

This looks like a possible bug in cargo, since lib/Cargo.toml uses include to only include "/src", "/README.md", and "/LICENSE"; so these files should not be looked at. For now, the files can be deleted before publishing.

@clehner clehner added the developer experience Make nicer and easier to use for developers label Apr 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
developer experience Make nicer and easier to use for developers
Projects
None yet
Development

No branches or pull requests

1 participant