you-get: migrate to [email protected]

[gaurdro]

• Have you followed the guidelines for contributing?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing brew install <formula>)?

---

[Rylan12]

Thanks for working on this, @gaurdro. We really appreciate it.

If you don't mind, can you hold off on opening these until the virtualenv fix gets merged? I just don't want to waste CI capacity on things that we expect to fail.

I've seen a few that have passed, though, and those are totally fine!

Edit: ooh, you get bonus points for adding the license! 😄

[gaurdro]

@Rylan12 of course! I've been trying to only make PRs for ones that don't use a virtualenv, this one I missed because it happened to work locally.

[fxcoudert]

I'm re-running CI, to check the virtualenv fix at Homebrew/brew#8873
Even if CI is green, this should not be merged before the next Brew tag ships, expected on Monday 2020-10-12.

[BrewTestBot]

🤖 A scheduled task has triggered a merge.