-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Cargo whines about not finding README.md #2553
Comments
Which rust toolchain are you using? A similar issue was opened last year, but it was a regression in a cargo nightly #2231 |
Indeed, that might certainly be important for the discussion... To reiterate, the flaw is not in hyper(since the crate has the file that is pointed out by package.readme in its Cargo.toml. Which, of course, makes the issue opened in the wrong place. But, perhaps, this place is a good starting point... And, it is also NOT in cargo. The question is rather: Is it because of some misplaced optimization effort ? Ideas ? |
Yea I think the regression was fixed a few days later with rust-lang/cargo#8353 Either way, to help avoid issues like that, an option would be to remove the line that specifies Line 5 in 960a69a
Alternatively/ in addition, the readme file could be added to the include list Lines 15 to 20 in 960a69a
|
I got the following message from cargo recently:
error: failed to parse manifest at /build/hyper-0.13.8.crate/Cargo.toml
Caused by:
readme file with name 'README.md' was not found
It seems cargo enforces that a readme file exists if it is included in Cargo.toml.
Obviously, hyper has a README.md file.
It is just not included in the crate downloaded from crates.io.
Weirdly, of the crates I have checked, this only seems to apply the hyper crate.
Any idea ?
The text was updated successfully, but these errors were encountered: