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

[BUG] latest published versions contain bogus LICENSE files #649

Open
decathorpe opened this issue Oct 7, 2024 · 9 comments
Open

[BUG] latest published versions contain bogus LICENSE files #649

decathorpe opened this issue Oct 7, 2024 · 9 comments
Labels
bug Something isn't working

Comments

@decathorpe
Copy link

Describe the bug

This is a followup for #392 and #477.

It looks like you cargo publish was run for v0.3.7 on a system that does not support symbolic links - the LICENSE files contain just the string ../LICENSE and not the actual license text.

If you are going to be publishing from Windows again, symbolic links will not be enough to include the license files, but actual copies of the files will be necessary to have cargo pick them up correctly.

To Reproduce

Download plotters-* crates from crates.io and inspect them. The LICENSE files contain just the string ../LICENSE instead of the license text.

Version Information

  • plotters v0.3.7
  • plotters-backend v0.3.7
  • plotters-bitmap v0.3.7
  • plotters-svg v0.3.7
@decathorpe decathorpe added the bug Something isn't working label Oct 7, 2024
@AaronErhardt
Copy link
Member

It looks like you cargo publish was run for v0.3.7 on a system that does not support symbolic links

Not sure if Fedora 40 counts as a system that does not support symbolic links. I rather think that Cargo does not resolve symbolic links in general.

@decathorpe
Copy link
Author

No, cargo definitely does support this ... I tested running cargo package on Fedora 41, and the resulting .crate file contains the correct LICENSE file, and not just a file that contains the string ../LICENSE.

Looks like something went wrong when the crates for v0.3.7 were published - either the local checkout of the git repo was corrupted, or you used a buggy version of cargo.

@AaronErhardt
Copy link
Member

Mhh, strange. Maybe you have to use cargo publish -p ... instead of cd ... && cargo publish because cargo does not load symlinks from outside of the current pwd?

@decathorpe
Copy link
Author

I don't think so. I just tried both, and both worked :(

@AaronErhardt
Copy link
Member

Then I'm out of ideas why it didn't work. I should have a regular Fedora setup with a recent Rust version via rustup and without notable configuration changes. I'll have a look at this tomorrow.

@AaronErhardt
Copy link
Member

I just tried both cargo package variants and both didn't work for me. Not sure why honestly. As I said earlier, I just have a regular Fedora setup...

@decathorpe
Copy link
Author

Did you try from a fresh git clone of this repo? Maybe your local checkout is corrupted somehow.

@AaronErhardt
Copy link
Member

Thanks for the good idea!
That actually worked. I guess the next release will fix the issue then automatically.

@decathorpe
Copy link
Author

Good to know. Thanks for checking!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants