-
Notifications
You must be signed in to change notification settings - Fork 144
Packages uploaded to private gitlab repos are not discoverable in pypi/simple #364
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
Comments
I am experiencing something similar (if not identical). If I upload using flit and try to install I get the following error:
when I upload using twine and install, all is the fine. What I find is that the download path is different:
It seems the SHA hash is used as a path maybe ? |
Has anyone made any progress on this? I just started testing with gitlab package registries and I'm running into this same issue. |
No progress. I settled with creating the package using flit and uploading using twine. It does the job. |
This is needed by GitLab to support uploads from flit (GitLab works fine with twine). Addresses pypa#364 of takluyver/flit Addresses #333964 of gitlab.com/gitlab-org/gitlab The most useful one-line of code I ever wrote I believe.
Hey, I provided a fix for this. Can you test again? |
(You'll need Flit from master for now to test this - I'll try to do a new release soon. It will be in version 3.3. |
And this is now released. Thanks @ChloeTigre for the fix! |
I am not sure if this is an issue on gitlab or flit, but I recently tried flit with private gitlab repos, and the package is shown in gitlab user interface, but it is not available to download in
pypi/simple
. This behavior does not happen when twine is used. This can also be an issue on gitlab's registry.install command for flit:
and twine:
The former shows
The text was updated successfully, but these errors were encountered: