-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Error 500 if upload non SemVers Conan packages #21250
Comments
I expected conan to use SemVer but the upload did not enforce it. I don't use conan in production, are non-SemVer versions common and should the registry allow non-SemVer versions? The docs are not clear about that:
|
I am more an ops than a dev. Our dev team uses non-SemVer versions on Conan packages but I don't know if it's a good practise. Thanks for your interest on thi s issue. |
For instance, libbacktrace recipe on Conan-center index doesn't use SemVer : version is cci.20210118 and we encounter the problem with this dependency. not tested, but perhaps it's the same with : More generally, we cannot either manage an intermediate version in dev : "latest" or other string version currently with Gitea. |
Fixes go-gitea#21250 Related go-gitea#20414 Conan packages don't have to follow SemVer. The migration fixes the setting for all existing Conan and Generic (go-gitea#20414) packages.
Description
We are trying Gitea as repository.
We are experimenting the same issue that this case using Conan package:
#20603 (comment)
****
If we upload a conan package using nonSem version, we have error 500 on repo package pages.
To fix this issue, I update semver_compatible from true to false :
There is no command on conan upload cli to fix semvers to true or false.
Is this a bug in Gitea ?
Thanks,
Gitea Version
1.18-dev
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
Ubuntu 22
How are you running Gitea?
Install gitea on vmware virtual machine, ubuntu22 using the binary.
Database
PostgreSQL
The text was updated successfully, but these errors were encountered: