Skip to content
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

removal of 4.1 broke downstream gates #192

Closed
prometheanfire opened this issue Jun 29, 2018 · 6 comments
Closed

removal of 4.1 broke downstream gates #192

prometheanfire opened this issue Jun 29, 2018 · 6 comments

Comments

@prometheanfire
Copy link

prometheanfire commented Jun 29, 2018

http://logs.openstack.org/91/578291/2/check/requirements-tox-py27-check-uc/d6c84fe/job-output.txt.gz#_2018-06-29_05_13_33_345222

@prometheanfire
Copy link
Author

prometheanfire commented Jun 29, 2018

https://doughellmann.com/blog/2016/02/25/so-youve-released-a-broken-package-to-pypi-what-do-you-do-now/

@penguinolog
Copy link

penguinolog commented Jun 29, 2018

Removal of the package (and distribution files) is a really bad thing. As result, all instances with frozen requirements immediately became broken.

@edmorley
Copy link

edmorley commented Jun 29, 2018

@orsinium
Copy link

orsinium commented Jun 29, 2018

It's broke our locked production requirements too.

@adamcharnock
Copy link

adamcharnock commented Jun 29, 2018

Having the same problem here.

@ingydotnet
Copy link
Member

ingydotnet commented Jun 29, 2018

I apologize for the fallout on this decision. We were between a rock and a hard place, and we decided that removing a badly broken 4.1 would cause more trouble the longer we waited.

See #193 for details and the path forward to 4.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants