Latest release 3.3.1 fails to deploy to pypi

[belugame]

see job log: https://travis-ci.org/James1345/django-rest-knox/jobs/409780228

HTTPError: 400 Client Error: User 'xxx.xxx' does not have a verified primary email address. Please add a verified primary email before attempting to upload to PyPI. See https://pypi.org/help/#verified-email for more information.for more information. for url: https://upload.pypi.org/legacy/

Original author was informed by me.

[belugame]

ping @James1345

[luk156]

ping :)

[rphlo]

Is there any sign of life from @James1345 ? Should we consider transfering the ownership of this repo and the pypi package to someone more active?

[belugame]

Feel free to drop him an email, you can find it here:
https://github.com/James1345/django-rest-knox/blob/master/setup.py#L28

[rphlo]

Thing is he should have already received multiple email regarding this issue and did not respond to any of those (Pypi email confirmation, Github notifications...)

[belugame]

he does reply to personal emails relatively quick. People tend to filter away auto-emails into folders. At least I do :)

[rphlo]

I sent an email.

[rphlo]

@James1345 replied

PyPi seem to have changed something and I can't get back into my old account. I don't know why yet, but it seems to have completely lost my email address as one that's registered to an account.

I'm contacting PyPi support to see if I can get back into the account

[James1345]

Okay, email address verified, the builds should succeed now hopefully

…

On Thu, 30 Aug 2018 at 12:56, Raphaël Stefanini ***@***.***> wrote: @James1345 <https://github.com/James1345> replied PyPi seem to have changed something and I can't get back into my old account. I don't know why yet, but it seems to have completely lost my email address as one that's registered to an account. I'm contacting PyPi support to see if I can get back into the account — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#107 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAkjesBjRF1EQFaaQM_zu7LxJkJMn3u_ks5uV9LhgaJpZM4VnxJj> .

[rphlo]

Travis build went through but show Skipping a deployment with the pypi provider because this is not a tagged commit

[James1345]

Good spot. Need to force it to try a pypi deployment somehow...

…

On Tue, 4 Sep 2018 at 12:37, Raphaël Stefanini ***@***.***> wrote: Travis build went through but show Skipping a deployment with the pypi provider because this is not a tagged commit — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#107 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAkjehun2Bc9OZlRzo4kVyGo-2j7rYx7ks5uXmYBgaJpZM4VnxJj> .

[belugame]

@James1345 any update on this?

[luk156]

ping

[James1345]

next release should force a deployment

[belugame]

just tagged master as 3.3.1, hopefully already on its way to pypi

[belugame]

Release failed :( @James1345

HTTPError: 403 Client Error: Invalid or non-existent authentication information. for url: https://upload.pypi.org/legacy/
django_rest_knox.egg-info/PKG-INFO already exists, no checkout
django_rest_knox.egg-info/SOURCES.txt already exists, no checkout
django_rest_knox.egg-info/dependency_links.txt already exists, no checkout
django_rest_knox.egg-info/requires.txt already exists, no checkout
django_rest_knox.egg-info/top_level.txt already exists, no checkout
Could not restore untracked files from stash entry
PyPI upload failed.
failed to deploy

https://travis-ci.org/James1345/django-rest-knox/jobs/434573815

[rphlo]

@James1345 did you forget to update your password in .travis.yml after you recovered your account?

[James1345]

That's not impossible

[johnraz]

Hey guys,

Would be nice to merge #109 with a successful pypi release 🎉

@James1345 would you have a bit of time to create a PR with the updated credentials?

Cheers 🤓

[belugame]

ping @James1345

[James1345]

I'll give it a poke this evening

…

On Tue, 9 Oct 2018, 07:42 belugame, ***@***.***> wrote: ping @James1345 <https://github.com/James1345> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#107 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAkjeukaaNfVb4vUX-KcPZv9JagOHVpIks5ujEU3gaJpZM4VnxJj> .

[johnraz]

@James1345 any chance we could see this moving forward or maybe you can delegate some permissions to @belugame ?

[belugame]

❗ We are unable to release since almost 3 months now, @James1345
At the moment the project sees a lot of valuable contributions from motivated coders new to the project, far more than in the past. It's a shame that we cannot thank them with regular releases to pypi. If you can't find the time for reestablishing the release workflow, I guess we have to republish it under a new name sadly. :-/

[James1345]

I did the thing. Is it still not working?

[belugame]

Oh I wasn't aware you did. Just made a new release. It failed sadly:

https://travis-ci.org/James1345/django-rest-knox/jobs/445302892

HTTPError: 403 Client Error: Invalid or non-existent authentication information. for url: https://upload.pypi.org/legacy/
django_rest_knox.egg-info/PKG-INFO already exists, no checkout
django_rest_knox.egg-info/SOURCES.txt already exists, no checkout
django_rest_knox.egg-info/dependency_links.txt already exists, no checkout
django_rest_knox.egg-info/requires.txt already exists, no checkout
django_rest_knox.egg-info/top_level.txt already exists, no checkout
Could not restore untracked files from stash entry
PyPI upload failed.
failed to deploy

[James1345]

On it right now, just reminding myself how travis works

[James1345]

Okay, I've re-reset the password. I'm doing a new release to try to make it deploy

[James1345]

@belugame it successfully deployed the first build, but then the others fail when it tries to deploy again with the other django versions... not sure of the solution yet

[James1345]

https://travis-ci.org/James1345/django-rest-knox/builds/445317311

[belugame]

might be related to us having added a Manifest file here ca26c90

but for a release, i dont even know why it should build all versions and try to publish them.. that sounds wrong anyway

[James1345]

Fixing it now with build stages

[James1345]

Going to leave it for tonight. It looks odd, but the deployment at least succeeds. I'll properly secure another new password some other day (leave this issue open so I remember)

[johnraz]

I don't believe it's related to the manifest.

The log says:

Uploading distributions to https://upload.pypi.org/legacy/
Uploading django_rest_knox-3.4.0-py3-none-any.whl
100%|██████████████████████████████████████| 19.0k/19.0k [00:01<00:00, 14.6kB/s]
Uploading django-rest-knox-3.4.0.tar.gz
100%|██████████████████████████████████████| 16.6k/16.6k [00:00<00:00, 44.1kB/s]
NOTE: Try --verbose to see response content.
HTTPError: 400 Client Error: File already exists. See https://pypi.org/help/#file-name-reuse for url: https://upload.pypi.org/legacy/

And then reading on https://pypi.org/help/#file-name-reuse, it seems that you cannot re-use the same filename twice - I guess to avoid replacing releases with new content and force you to bump your version instead.

And I believe it has been like that for a long time:
https://travis-ci.org/James1345/django-rest-knox/builds/346312886

Do you know if it ever worked without errors?

Anyway, I think everything is working as it should considering the release has been pushed to pypi.

We should close this and maybe re-open another issue if we really want to fix those kinda false positive failure.

Cheers

[James1345]

It worked for the 2.7 config. The issue is that each config in the test matrix is trying to deploy, which causes the file conflict. Because we build a universal package, it should be fine to install 3.4.0 from pypi, we're just going to get this error every time we try to deploy

…

On Wed, 24 Oct 2018, 12:23 Jonathan Liuti, ***@***.***> wrote: I don't believe it's related to the manifest. The log says: Uploading distributions to https://upload.pypi.org/legacy/ Uploading django_rest_knox-3.4.0-py3-none-any.whl 100%|██████████████████████████████████████| 19.0k/19.0k [00:01<00:00, 14.6kB/s] Uploading django-rest-knox-3.4.0.tar.gz 100%|██████████████████████████████████████| 16.6k/16.6k [00:00<00:00, 44.1kB/s] NOTE: Try --verbose to see response content. HTTPError: 400 Client Error: File already exists. See https://pypi.org/help/#file-name-reuse for url: https://upload.pypi.org/legacy/ And then reading on https://pypi.org/help/#file-name-reuse, it seems that you cannot re-use the same filename twice - I guess to avoid replacing releases with new content and force you to bump your version instead. And I believe it has been like that for a long time: https://travis-ci.org/James1345/django-rest-knox/builds/346312886 Do you know if it ever worked ? Cheers — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#107 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAkjerQT7kJTIp-xEAs5jvPQYPAnkEivks5uoE3HgaJpZM4VnxJj> .

[johnraz]

This is precisely what I'm stating, yes.

[johnraz]

Created #138 to follow up on this, that way we can close this as the main issue is fixed.

[belugame]

thank you @johnraz