-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Package: Could not validate one or more reference fields #20405
Comments
Looking at the full logs, it seems to me that both of them fail because the package version is not SemVer compatible, while the conan repository seems to require the version to be SemVer. Other packages going through likely have a version that adheres to SemVer. I suspect that this semver restriction should be lifted. |
they both come from the main repository without changes... so...don't know. |
zeripath
pushed a commit
that referenced
this issue
Jul 22, 2022
A lot of existing packages do not conform to SemVer, yet, they should be allowed in the Conan package registry as-is. To achieve this, remove the SemVer check from `NewRecipeReference`, and replace it with a simple empty string check. A unit test with a non-semver version is also included. Fixes #20405. Signed-off-by: Gergely Nagy <[email protected]> Co-authored-by: KN4CK3R <[email protected]>
6543
pushed a commit
to 6543-forks/gitea
that referenced
this issue
Jul 28, 2022
A lot of existing packages do not conform to SemVer, yet, they should be allowed in the Conan package registry as-is. To achieve this, remove the SemVer check from `NewRecipeReference`, and replace it with a simple empty string check. A unit test with a non-semver version is also included. Fixes go-gitea#20405. Signed-off-by: Gergely Nagy <[email protected]> Co-authored-by: KN4CK3R <[email protected]>
zeripath
pushed a commit
that referenced
this issue
Jul 28, 2022
) Backport #20412 A lot of existing packages do not conform to SemVer, yet, they should be allowed in the Conan package registry as-is. To achieve this, remove the SemVer check from `NewRecipeReference`, and replace it with a simple empty string check. A unit test with a non-semver version is also included. Fixes #20405. Signed-off-by: Gergely Nagy <[email protected]> Co-authored-by: KN4CK3R <[email protected]> Co-authored-by: Gergely Nagy <[email protected]>
vsysoev
pushed a commit
to IntegraSDL/gitea
that referenced
this issue
Aug 10, 2022
A lot of existing packages do not conform to SemVer, yet, they should be allowed in the Conan package registry as-is. To achieve this, remove the SemVer check from `NewRecipeReference`, and replace it with a simple empty string check. A unit test with a non-semver version is also included. Fixes go-gitea#20405. Signed-off-by: Gergely Nagy <[email protected]> Co-authored-by: KN4CK3R <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Using conan package manager with gitea 1.17.0 when uploading some of the packages gitea return this error:
The log on gitea side is:
Is there a reason to why this package failed to be uploaded to gitea? most of them are uploaded with success this one no...it seems a name check?? openssl also fails for example:
full log
https://gist.github.com/nesc1/562b1e25d6132b4f091aa009b3f011ab
Gitea Version
1.17.0+rc1-33-g780b198997
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
https://gist.github.com/nesc1/562b1e25d6132b4f091aa009b3f011ab
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
dowloaded from your serves and running on a raspberry pi.
Database
MySQL
The text was updated successfully, but these errors were encountered: