error: could not learn metadata for

[Thomblin]

Problem

I try to run cargo publish --dry-run using WSL 2 with Debian on Windows 10

The command gives me two different errors whenever I try to execute it (without changing something in between)

me@home:/mnt/c/Users/me/development/rust/convert_string$ cargo publish --dry-run
Updating crates.io index
Packaging convert_string v0.1.0 (/mnt/c/Users/me/development/rust/convert_string)
Verifying convert_string v0.1.0 (/mnt/c/Users/me/development/rust/convert_string)
error: failed to verify package tarball

Caused by:
Permission denied (os error 13)

me@home:/mnt/c/Users/me/development/rust/convert_string$ cargo publish --dry-run
Updating crates.io index
Packaging convert_string v0.1.0 (/mnt/c/Users/me/development/rust/convert_string)
Verifying convert_string v0.1.0 (/mnt/c/Users/me/development/rust/convert_string)
Compiling convert_string v0.1.0 (/mnt/c/Users/me/development/rust/convert_string/target/package/convert_string-0.1.0)
Finished dev [unoptimized + debuginfo] target(s) in 1.38s
error: could not learn metadata for: /mnt/c/Users/me/development/rust/convert_string/target/package/convert_string-0.1.0.crate

Caused by:
No such file or directory (os error 2)

the mentioned file exists and is readable by the current user

I tried cargo clean as well as installing additional tools (build-essentials, clang, cmake)

Steps

1. cargo publish --dry-run

Possible Solution(s)

No response

Notes

No response

Version

cargo 1.71.0 (cfd3bbd8f 2023-06-08)
release: 1.71.0
commit-hash: cfd3bbd8fe4fd92074dfad04b7eb9a923646839f
commit-date: 2023-06-08
host: x86_64-unknown-linux-gnu
libgit2: 1.6.4 (sys:0.17.1 vendored)
libcurl: 8.0.1-DEV (sys:0.4.61+curl-8.0.1 vendored ssl:OpenSSL/1.1.1t)
ssl: OpenSSL 1.1.1t  7 Feb 2023
os: Debian 11.0.0 [64-bit]

[Thomblin]

Update: It works when I move the project into the WSL home directory, so far it was located at a mounted windows directory

[weihanglo]

Probably attributed to the same root cause of #11677?

[Thomblin]

@weihanglo That topic sounds related, however I had no issues with cargo build run or test so far

[weihanglo]

underlying they share the same code path. I'll close this in favor of that. Thank you :)