{"thread":{"id":"49295","subject":"[RFC PATCH] travis-ci: work around quarantine error during Perforce install on macOS","startedAt":"2018-09-07T03:20:18Z","lastAt":"2018-09-27T22:56:18Z","messageCount":2,"participants":["SZEDER Gábor"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"357598","messageId":"20180907032002.23366-1-szeder.dev@gmail.com","threadId":"49295","inReplyTo":null,"subject":"[RFC PATCH] travis-ci: work around quarantine error during Perforce install on macOS","fromName":"SZEDER Gábor","fromEmail":"szeder.dev@gmail.com","sentAt":"2018-09-07T03:20:02Z","receivedAt":"2018-09-07T03:20:18Z","isPatch":true,"sender":{"key":"szeder.dev@gmail.com","avatar":"https://avatars.githubusercontent.com/u/116324?v=4"},"body":"Homebrew recently enabled the quarantine feature, which breaks a lot\nof things [1], including installing Perforce in our macOS build jobs\non Travis CI [2], breaking all those builds in the last couple of\ndays.\n\nThe suggested workaround is to install affected packages using the\n'--no-quarantine' option, but adding it to the current command, i.e.\nrunning:\n\n  brew install --no-quarantine caskroom/cask/perforce\n\ndoesn't work, because apparently the '--no-quarantine' option is not\npropagated when the command gets converted to:\n\n  brew cask install perforce\n\n(unlike other options, e.g. '--verbose', '--force', and '--debug',\nwhich are propagated properly).\n\nSo work around the issue by installing Perforce with this command\ninstead:\n\n  brew cask install --no-quarantine perforce\n\nNote that one option homebrew/cask devs are considering is to roll\nback quarantine altogether [3].  We might have to revisit this\nworkaround if they eventually end up doing that, as that might remove\nthe '--no-quarantine' options as well.  We'll see.\n\n[1] https://github.com/Homebrew/homebrew-cask/issues/51554\n[2] e.g. https://travis-ci.org/git/git/jobs/424552274#L1246\n[3] https://github.com/Homebrew/homebrew-cask/issues/51554#issuecomment-418923763\n\nSigned-off-by: SZEDER Gábor <szeder.dev@gmail.com>\n---\n\nI'm not quite sure how to handle this issue.\n\nFirst: I don't have a Mac, and this \"cute\" homebrew talk about pouring\nbottles and tappping casks in the caskroom makes my brain hurt; so I\nwas just following instructions without fully understanding what I was\ndoing.  Nonetheless, this patch apparently makes the macOS build jobs\nwork again.\n\nOTOH, this is only an auxillary part of Git, so fast-tracking it is\nfairly low-risk, and by doing so we might have an all-green CI build\nbefore the 2.19 release.\n\nFinally, if we wait long enough, then this whole issue might just\nsolve itself, if the homebrew devs revert this quarantine stuff, and\nour current 'brew install' command might suddenly work again.\n\n ci/install-dependencies.sh | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/ci/install-dependencies.sh b/ci/install-dependencies.sh\nindex 75a9fd2475..ca99044b20 100755\n--- a/ci/install-dependencies.sh\n+++ b/ci/install-dependencies.sh\n@@ -30,7 +30,7 @@ osx-clang|osx-gcc)\n \t# brew install gnu-time\n \tbrew install git-lfs gettext\n \tbrew link --force gettext\n-\tbrew install caskroom/cask/perforce\n+\tbrew cask install --no-quarantine perforce\n \t;;\n esac\n \n-- \n2.19.0.rc2.140.g09cf9e37c9\n\n"},{"id":"359159","messageId":"20180927225611.GM27036@localhost","threadId":"49295","inReplyTo":"20180907032002.23366-1-szeder.dev@gmail.com","subject":"Re: [RFC PATCH] travis-ci: work around quarantine error during Perforce install on macOS","fromName":"SZEDER Gábor","fromEmail":"szeder.dev@gmail.com","sentAt":"2018-09-27T22:56:11Z","receivedAt":"2018-09-27T22:56:18Z","isPatch":true,"sender":{"key":"szeder.dev@gmail.com","avatar":"https://avatars.githubusercontent.com/u/116324?v=4"},"body":"On Fri, Sep 07, 2018 at 05:20:02AM +0200, SZEDER Gábor wrote:\n> Homebrew recently enabled the quarantine feature, which breaks a lot\n> of things [1], including installing Perforce in our macOS build jobs\n> on Travis CI [2], breaking all those builds in the last couple of\n> days.\n \n> Note that one option homebrew/cask devs are considering is to roll\n> back quarantine altogether [3].\n\n> Finally, if we wait long enough, then this whole issue might just\n> solve itself, if the homebrew devs revert this quarantine stuff, and\n> our current 'brew install' command might suddenly work again.\n\nGood, we waited long enough, and this issue apparently did indeed just\nsolve itself :)\n\n"}]}