search

amey-sam / Flask-MailGun

Flask MailGun extension
MIT License
14 stars 20 forks source link

issue with pypi deployment #28

Open Richard-Mathie opened 5 years ago

Richard-Mathie commented 5 years ago 
Writing Flask-MailGun3-0.1.6/setup.cfg
creating dist
Creating tar archive
removing 'Flask-MailGun3-0.1.6' (and everything under it)
/home/travis/virtualenv/pypy2.7-5.10/site-packages/cryptography/hazmat/bindings/openssl/binding.py:163: CryptographyDeprecationWarning: OpenSSL version 1.0.1 is no longer supported by the OpenSSL project, please upgrade. A future version of cryptography will drop support for it.
  utils.CryptographyDeprecationWarning
Uploading distributions to https://upload.pypi.org/legacy/
Uploading Flask-MailGun3-0.1.6.tar.gz
100%|##########| 17.9k/17.9k [00:00<00:00, 69.3kB/s]HTTPError: 403 Client Error: Invalid or non-existent authentication information. for url: https://upload.pypi.org/legacy/
NOTE: Try --verbose to see response content.
Flask_MailGun3.egg-info/PKG-INFO already exists, no checkout
Flask_MailGun3.egg-info/SOURCES.txt already exists, no checkout
Flask_MailGun3.egg-info/dependency_links.txt already exists, no checkout
Flask_MailGun3.egg-info/not-zip-safe already exists, no checkout
Flask_MailGun3.egg-info/requires.txt already exists, no checkout
Flask_MailGun3.egg-info/top_level.txt already exists, no checkout
Could not restore untracked files from stash entry
PyPI upload failed.
failed to deploy

https://github.com/FaradayRF/faradayio/issues/35 https://github.com/travis-ci/travis-ci/issues/10056

marshallmcdonnell commented 5 years ago

In googling to fix this for my own repository, I came across your issue.

I believe this is due to the build artifacts getting "cleaned" in the "Preparing deploy" step in Travis just before they are deployed to PyPi in the "Deploy Application" step directly after.

The remedy, I found is to add skip_cleanup: true in your .travis.yml

Below is from your build found here: https://travis-ci.org/amey-sam/Flask-MailGun/jobs/460912350

image

Also, since your Travis build has multiple version builds, each one will try to deploy your application. The first one to finish will succeed but all others after will fail on the PyPi side with "version already exists" type error. Thus, will also need the skip_existing: true statement as well