From: <stefan.naewe@atlas-elektronik.com>
To: <larsxschneider@gmail.com>, <git@vger.kernel.org>
Cc: <gitster@pobox.com>
Subject: Re: [PATCH v1] travis-ci: ask homebrew for the its path instead of hardcoding it
Date: Wed, 21 Sep 2016 09:31:38 +0000 [thread overview]
Message-ID: <83e3049c-34ea-4440-7b4d-061cb98ba2dd@atlas-elektronik.com> (raw)
In-Reply-To: <20160921084518.13091-1-larsxschneider@gmail.com>
In the Subject: s/the //
Am 21.09.2016 um 10:45 schrieb larsxschneider@gmail.com:
> From: Lars Schneider <larsxschneider@gmail.com>
>
> The TravisCI macOS build is broken because homebrew (a macOS depedency
s/depedency/dependency/
> manager) changed its internal directory structure [1]. This is a problem
> because we modify the Perforce dependencies in the homebrew repository
> before installing them.
>
> Fix it by asking homebrew for its path instead of hardcoding it.
>
> [1] https://github.com/Homebrew/brew/commit/0a09ae30f8b6117ad699b4a0439010738989c547
>
> Signed-off-by: Lars Schneider <larsxschneider@gmail.com>
> ---
>
> Hi Junio,
>
> the problem affects all branches (pu, next, master, maint):
> https://travis-ci.org/git/git/branches
>
> Is it possible for this fix to graduate more quickly?
>
> Thanks,
> Lars
>
> .travis.yml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/.travis.yml b/.travis.yml
> index 477c3d2..37a1e1f 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -78,7 +78,7 @@ before_install:
> FORMULA=$1
> SHA=$(brew fetch --force $FORMULA 2>&1 | grep ^SHA256: | cut -d ' ' -f 2)
> sed -E -i.bak "s/sha256 \"[0-9a-f]{64}\"/sha256 \"$SHA\"/g" \
> - /usr/local/Library/Taps/homebrew/homebrew-binary/$FORMULA.rb
> + "$(brew --repository homebrew/homebrew-binary)/$FORMULA.rb"
> }
> brew update --quiet
> brew tap homebrew/binary --quiet
> --
> 2.10.0
>
>
--
----------------------------------------------------------------
/dev/random says: If winning isn't important then why keep score?
python -c "print '73746566616e2e6e616577654061746c61732d656c656b74726f6e696b2e636f6d'.decode('hex')"
GPG Key fingerprint = 2DF5 E01B 09C3 7501 BCA9 9666 829B 49C5 9221 27AF
next prev parent reply other threads:[~2016-09-21 9:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 8:45 [PATCH v1] travis-ci: ask homebrew for the its path instead of hardcoding it larsxschneider
2016-09-21 9:31 ` stefan.naewe [this message]
2016-09-21 13:28 ` Lars Schneider
2016-09-21 16:42 ` Junio C Hamano
2016-09-22 9:03 ` Lars Schneider
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83e3049c-34ea-4440-7b4d-061cb98ba2dd@atlas-elektronik.com \
--to=stefan.naewe@atlas-elektronik.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=larsxschneider@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).