PyPi Packages containing an Epoch can cause a 500 internal server error #21707
Labels
Milestone
Comments
|
Linking to this as well since the test case package can be made in the same way, just substitute |
lunny
pushed a commit
that referenced
this issue
Nov 8, 2022
…es (#21708) This addresses #21707 and adds a second package test case for a non-semver compatible version (this might be overkill though since you could also edit the old package version to have an epoch in front and see the error, this just seemed more flexible for the future). Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
|
closed by #21708 |
Racer159
added a commit
to Racer159/gitea
that referenced
this issue
Nov 9, 2022
…es (go-gitea#21708) Backport (go-gitea#21708) This addresses go-gitea#21707 and adds a second package test case for a non-semver compatible version (this might be overkill though since you could also edit the old package version to have an epoch in front and see the error, this just seemed more flexible for the future). Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
Racer159
added a commit
to Racer159/gitea
that referenced
this issue
Nov 9, 2022
…es (go-gitea#21708) Backport (go-gitea#21708) This addresses go-gitea#21707 and adds a second package test case for a non-semver compatible version (this might be overkill though since you could also edit the old package version to have an epoch in front and see the error, this just seemed more flexible for the future). Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
lunny
pushed a commit
that referenced
this issue
Nov 9, 2022
…es (#21708) (#21730) Backport (#21708) This addresses #21707 and adds a second package test case for a non-semver compatible version (this might be overkill though since you could also edit the old package version to have an epoch in front and see the error, this just seemed more flexible for the future). Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
lunny
pushed a commit
that referenced
this issue
Nov 9, 2022
…es (#21708) (#21729) Backport (#21708) This addresses #21707 and adds a second package test case for a non-semver compatible version (this might be overkill though since you could also edit the old package version to have an epoch in front and see the error, this just seemed more flexible for the future). Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Python does not fully follow semantic versioning and has an optional epoch segment (
([1-9][0-9]*!)?(note the!) in front of its versions. Providing a package with a version with an epoch results in a 500 error on upload and a 500 error on subsequent requests to/admin/packagesas well.Gitea Version
1.17.3
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
https://gist.github.com/Racer159/cbe5bfb6df438cee59400695ec6ce89b
Screenshots
Git Version
2.38.0
Operating System
popOS 22.04
How are you running Gitea?
For testing locally off of the
mainbranch, in production using the official chart version 6.0.3 (app version 1.17.3)Database
SQLite
The text was updated successfully, but these errors were encountered: