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

brew update is destructive linking python3 to python #3859

Closed
PhDuck opened this Issue Mar 2, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@PhDuck
Copy link

PhDuck commented Mar 2, 2018

I just did "brew update" which did the following:

==> Migrating python3 to python
==> Unlinking python3
==> Unlinking python
==> Moving python3 children
==> Linking python

I'm sure that python3 makes sense to use and is the future, but why is this change made without
prompting the user for input? This is potentially a breaking change that can affect systems.
Furthermore the semantics of running brew update is now blurred; what am I to expect when running the command?

@ilovezfs

This comment has been minimized.

Copy link
Contributor

ilovezfs commented Mar 2, 2018

This changed was announced in January https://brew.sh/2018/01/19/homebrew-1.5.0/

If you need Python 2, brew install python@2

@ilovezfs ilovezfs closed this Mar 2, 2018

@MikeMcQuaid

This comment has been minimized.

Copy link
Member

MikeMcQuaid commented Mar 2, 2018

Also: please always, always read and fill out the issue template. It tells you to do so.

why is this change made without prompting the user for input?

No Homebrew change ever prompts the user for input.

@MikeMcQuaid

This comment has been minimized.

Copy link
Member

MikeMcQuaid commented Mar 2, 2018

How should a user guard against unexpected breaking changes?

In progressing levels of effort (the lowest level of which would have been sufficient in this case):

  1. read our blog posts through the RSS feed or our Twitter feed (or the front page of Hacker News where they normally end up)
  2. watch our repository and read pull requests that seem relevant to your organisation
  3. watch our repository and test pull requests that seem relevant to your organisation before they are merged
  4. create your own tap or fork of Homebrew/homebrew-core for formulae you wish to never be changed

how should users proceed and get back to getting work done?

That's on you to figure out. We're volunteers running a project that you're using to "get work done" i.e. make money. Our license clearly states we disclaim all warranties and the software is available as-is. Note, your organisation could consider donating money to our project which would provide more resources to make it easier for us to do additional automated testing.

@MikeMcQuaid

This comment has been minimized.

Copy link
Member

MikeMcQuaid commented Mar 2, 2018

And to be clear:

This is potentially a breaking change that can affect systems.

This is definitely a breaking change. That's why we gave you a month and a half's notice on our primary communication mechanisms (blog on our homepage, our Twitter) to adapt to this change. If you did not do so: that's on you, not us, sorry.

@Homebrew Homebrew deleted a comment from kevinwaddle Mar 2, 2018

@Homebrew Homebrew deleted a comment from kevwil Mar 2, 2018

@Homebrew Homebrew deleted a comment from kevwil Mar 2, 2018

@Homebrew Homebrew locked as too heated and limited conversation to collaborators Mar 2, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.