-
-
Notifications
You must be signed in to change notification settings - Fork 5.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 registry - Renamed dependencies does not get renamed #31500
Comments
Thanks @usbalbin, has this been working previously, or has it always been like this? (If you haven’t tried this before and don’t know that’s ok) |
I first tried the same thing with 1.21. |
@techknowlogick That's not implemented. I didn't know that was possible. I will send a PR when I got time for it. |
I have found another issue. Not sure if it is gitea or cargo. In case it is related https://forum.gitea.com/t/published-cargo-crate-version-not-available/9365 |
rust allows renaming dependencies such as when depending on multiple versions of the same package. This is not supported by gitea as discovered in #31500 . This PR tries to address that. --------- Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
rust allows renaming dependencies such as when depending on multiple versions of the same package. This is not supported by gitea as discovered in go-gitea#31500 . This PR tries to address that. --------- Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
This should be solved in #32430 |
Description
When publishing a crate with a renamed dependency
The registry does not reflect the fact that the dependency is renamed
https://my-gitea-domain/api/packages/SomeOwner/cargo/re/na/rename_deps
:Same thing formatted:
I posted the same issue in rust-lang/cargo#14148 leading me here. I have not tried this on demo.gitea.com
Gitea Version
1.22.0
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
Whatever is in the docker image
Operating System
Debian 12
How are you running Gitea?
Database
MySQL/MariaDB
The text was updated successfully, but these errors were encountered: