git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: git@vger.kernel.org
Cc: "Lars Schneider" <larsxschneider@gmail.com>,
	"Junio C Hamano" <gitster@pobox.com>,
	"SZEDER Gábor" <szeder.dev@gmail.com>
Subject: [RFC PATCH] travis-ci: work around quarantine error during Perforce install on macOS
Date: Fri,  7 Sep 2018 05:20:02 +0200	[thread overview]
Message-ID: <20180907032002.23366-1-szeder.dev@gmail.com> (raw)

Homebrew recently enabled the quarantine feature, which breaks a lot
of things [1], including installing Perforce in our macOS build jobs
on Travis CI [2], breaking all those builds in the last couple of
days.

The suggested workaround is to install affected packages using the
'--no-quarantine' option, but adding it to the current command, i.e.
running:

  brew install --no-quarantine caskroom/cask/perforce

doesn't work, because apparently the '--no-quarantine' option is not
propagated when the command gets converted to:

  brew cask install perforce

(unlike other options, e.g. '--verbose', '--force', and '--debug',
which are propagated properly).

So work around the issue by installing Perforce with this command
instead:

  brew cask install --no-quarantine perforce

Note that one option homebrew/cask devs are considering is to roll
back quarantine altogether [3].  We might have to revisit this
workaround if they eventually end up doing that, as that might remove
the '--no-quarantine' options as well.  We'll see.

[1] https://github.com/Homebrew/homebrew-cask/issues/51554
[2] e.g. https://travis-ci.org/git/git/jobs/424552274#L1246
[3] https://github.com/Homebrew/homebrew-cask/issues/51554#issuecomment-418923763

Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com>
---

I'm not quite sure how to handle this issue.

First: I don't have a Mac, and this "cute" homebrew talk about pouring
bottles and tappping casks in the caskroom makes my brain hurt; so I
was just following instructions without fully understanding what I was
doing.  Nonetheless, this patch apparently makes the macOS build jobs
work again.

OTOH, this is only an auxillary part of Git, so fast-tracking it is
fairly low-risk, and by doing so we might have an all-green CI build
before the 2.19 release.

Finally, if we wait long enough, then this whole issue might just
solve itself, if the homebrew devs revert this quarantine stuff, and
our current 'brew install' command might suddenly work again.

 ci/install-dependencies.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/ci/install-dependencies.sh b/ci/install-dependencies.sh
index 75a9fd2475..ca99044b20 100755
--- a/ci/install-dependencies.sh
+++ b/ci/install-dependencies.sh
@@ -30,7 +30,7 @@ osx-clang|osx-gcc)
 	# brew install gnu-time
 	brew install git-lfs gettext
 	brew link --force gettext
-	brew install caskroom/cask/perforce
+	brew cask install --no-quarantine perforce
 	;;
 esac
 
-- 
2.19.0.rc2.140.g09cf9e37c9


             reply	other threads:[~2018-09-07  3:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-07  3:20 SZEDER Gábor [this message]
2018-09-27 22:56 ` [RFC PATCH] travis-ci: work around quarantine error during Perforce install on macOS SZEDER Gábor

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=20180907032002.23366-1-szeder.dev@gmail.com \
    --to=szeder.dev@gmail.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).