Local Package Identifiers not currently supported in Gitea

[Racer159]

Description

When running Gitea as a private PyPi package registry there may be packages that do not match the canonical public version and instead use a local version identifier as outlined in PEP-0440. An example of this could be an internally forked version of certify https://pypi.org/project/certifi/#files that includes custom CAs specific to that organization.

When attempting to use these packages with Gitea it will return a 400 Bad Request with "invalid name or version"

Gitea Version

1.17.3

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

https://gist.github.com/Racer159/8aa895f1ffd62fb56d567d26e812c973

Screenshots

Git Version

2.38.0

Operating System

popOS 22.04

How are you running Gitea?

For this testing/log locally off of the main branch, but in production it is inside of the official Gitea chart, specifically version 6.0.3.

Database

SQLite

[Racer159]

Also as a note, to quickly make a version that matches you can do the following:

1. Download the latest Built version of certify from here: https://pypi.org/project/certifi/#files
2. Extract the .whl as a zip archive
3. Rename the .dist-info folder to include the +<local_id>
   
4. Inside of that folder, edit the METADATA file to include the +<local_id> on its version
   
5. Rezip the two folders into a .whl named with the new local id version. (these folders should be at the root of the archive)