Does dropping the --cask flag make a difference?

Also see Homebrew/homebrew-cask#87045 for more information.

Maybe - but I have to separate casks from regular updates as I use home-brew usually without admin rights.

So I run only cask updates in an admin-User (with the terrible permission update problems).

Pulling in @Homebrew/cask for thoughts/fixes.

but I have to separate casks from regular updates as I use home-brew usually without admin rights.

Using --cask or not won’t make an (installation) difference in this case. Even if you omit the flag, it will still install the cask (there’s no google-chrome formula).

So what happens if you brew reinstall --verbose --debug --no-quarantine google-chrome?

@vitorgalvao agreed. But in upgrade it will, right?

But in upgrade it will, right?

Not when you give it an argument of what to upgrade (which in this case you’re doing).

Think of the --casks and --formulae flags as restrictors (without which, both are included). When you give it a specific formula or cask as an argument, you’ve already restricted it to that and the flag doesn’t do much (or it shouldn’t, but in this case it might be introducing a bug).

@vitorgalvao I see,

My problem is: once I upgrade and only one cask that needs admin rights is in the outdated list, my scripts fail sometime in the list as I have no sudo right.

So I restrict it with —cask (no cask name, above was a sample to demonstrate the error) and run it in the Admin account.
After that I do a regular upgrade.

I did not know —formula. Good news.

But can you try the reinstall command as requested? We can’t proceed until we know what happens there.

@vitorgalvao sure.

> brew reinstall --force --no-quarantine --verbose --debug google-chrome
...
==> Checking quarantine support
/usr/bin/xattr
/usr/bin/swift /usr/local/Homebrew/Library/Homebrew/cask/utils/quarantine.swift
==> Quarantine is available.
==> Verifying Gatekeeper status of /Users/_admin/Library/Caches/Homebrew/downloads/9830ac8a5256756d2643fbdb6a47ba0eb019c3816fc4366049f2483999b2ee4f--googlechrome.dmg
/usr/bin/xattr -p com.apple.quarantine /Users/_admin/Library/Caches/Homebrew/downloads/9830ac8a5256756d2643fbdb6a47ba0eb019c3816fc4366049f2483999b2ee4f--googlechrome.dmg
==> /Users/_admin/Library/Caches/Homebrew/downloads/9830ac8a5256756d2643fbdb6a47ba0eb019c3816fc4366049f2483999b2ee4f--googlechrome.dmg is quarantined
==> Downloaded to -> /Users/_admin/Library/Caches/Homebrew/downloads/9830ac8a5256756d2643fbdb6a47ba0eb019c3816fc4366049f2483999b2ee4f--googlechrome.dmg
tar tf /Users/_admin/Library/Caches/Homebrew/downloads/9830ac8a5256756d2643fbdb6a47ba0eb019c3816fc4366049f2483999b2ee4f--googlechrome.dmg
hdiutil imageinfo -format /Users/_admin/Library/Caches/Homebrew/downloads/9830ac8a5256756d2643fbdb6a47ba0eb019c3816fc4366049f2483999b2ee4f--googlechrome.dmg
...
==> Verifying Gatekeeper status of /Users/_admin/Library/Caches/Homebrew/downloads/9830ac8a5256756d2643fbdb6a47ba0eb019c3816fc4366049f2483999b2ee4f--googlechrome.dmg
/usr/bin/xattr -p com.apple.quarantine /Users/_admin/Library/Caches/Homebrew/downloads/9830ac8a5256756d2643fbdb6a47ba0eb019c3816fc4366049f2483999b2ee4f--googlechrome.dmg
==> /Users/_admin/Library/Caches/Homebrew/downloads/9830ac8a5256756d2643fbdb6a47ba0eb019c3816fc4366049f2483999b2ee4f--googlechrome.dmg is quarantined
==> Propagating quarantine from /Users/_admin/Library/Caches/Homebrew/downloads/9830ac8a5256756d2643fbdb6a47ba0eb019c3816fc4366049f2483999b2ee4f--googlechrome.dmg to /usr/local/Caskroom/google-chrome/87.0.4280.67
/usr/bin/xattr -p com.apple.quarantine /Users/_admin/Library/Caches/Homebrew/downloads/9830ac8a5256756d2643fbdb6a47ba0eb019c3816fc4366049f2483999b2ee4f--googlechrome.dmg
/usr/bin/xargs -0 -- /bin/chmod -h u\+w
/usr/bin/xargs -0 -- /usr/bin/xattr -w com.apple.quarantine 0181\;5fb68e37\;Homebrew\\x20Cask\;10D60B01-B275-48A9-99F8-1C9C3B625214
...

Dialog is shown.

@logopk does running:

HOMEBREW_CASK_OPTS="--no-quarantine" brew reinstall --force --verbose --debug google-chrome

make a difference?

Seems so:

> HOMEBREW_CASK_OPTS="--no-quarantine" brew reinstall --force --verbose --debug google-chrome
...
==> Checking quarantine support
/usr/bin/xattr
/usr/bin/swift /usr/local/Homebrew/Library/Homebrew/cask/utils/quarantine.swift
==> Quarantine is available.
==> Verifying Gatekeeper status of /Users/_admin/Library/Caches/Homebrew/downloads/9830ac8a5256756d2643fbdb6a47ba0eb019c3816fc4366049f2483999b2ee4f--googlechrome.dmg
/usr/bin/xattr -p com.apple.quarantine /Users/_admin/Library/Caches/Homebrew/downloads/9830ac8a5256756d2643fbdb6a47ba0eb019c3816fc4366049f2483999b2ee4f--googlechrome.dmg
==> /Users/_admin/Library/Caches/Homebrew/downloads/9830ac8a5256756d2643fbdb6a47ba0eb019c3816fc4366049f2483999b2ee4f--googlechrome.dmg is quarantined
==> Releasing /Users/_admin/Library/Caches/Homebrew/downloads/9830ac8a5256756d2643fbdb6a47ba0eb019c3816fc4366049f2483999b2ee4f--googlechrome.dmg from quarantine
/usr/bin/xattr -d com.apple.quarantine /Users/_admin/Library/Caches/Homebrew/downloads/9830ac8a5256756d2643fbdb6a47ba0eb019c3816fc4366049f2483999b2ee4f--googlechrome.dmg
==> Downloaded to -> /Users/_admin/Library/Caches/Homebrew/downloads/9830ac8a5256756d2643fbdb6a47ba0eb019c3816fc4366049f2483999b2ee4f--googlechrome.dmg
tar tf /Users/_admin/Library/Caches/Homebrew/downloads/9830ac8a5256756d2643fbdb6a47ba0eb019c3816fc4366049f2483999b2ee4f--googlechrome.dmg
hdiutil imageinfo -format /Users/_admin/Library/Caches/Homebrew/downloads/9830ac8a5256756d2643fbdb6a47ba0eb019c3816fc4366049f2483999b2ee4f--googlechrome.dmg
...
==> Installing Cask google-chrome
Warning: macOS's Gatekeeper has been disabled for this Cask
...

Important to note, that this happens only if it was quarantined before
If it was not then it looks like this

==> Checking quarantine support
/usr/bin/xattr
/usr/bin/swift /usr/local/Homebrew/Library/Homebrew/cask/utils/quarantine.swift
==> Quarantine is available.
==> Verifying Gatekeeper status of /Users/_admin/Library/Caches/Homebrew/downloads/9830ac8a5256756d2643fbdb6a47ba0eb019c3816fc4366049f2483999b2ee4f--googlechrome.dmg
/usr/bin/xattr -p com.apple.quarantine /Users/_admin/Library/Caches/Homebrew/downloads/9830ac8a5256756d2643fbdb6a47ba0eb019c3816fc4366049f2483999b2ee4f--googlechrome.dmg
==> /Users/_admin/Library/Caches/Homebrew/downloads/9830ac8a5256756d2643fbdb6a47ba0eb019c3816fc4366049f2483999b2ee4f--googlechrome.dmg is not quarantined
==> Downloaded to -> /Users/_admin/Library/Caches/Homebrew/downloads/9830ac8a5256756d2643fbdb6a47ba0eb019c3816fc4366049f2483999b2ee4f--googlechrome.dmg
...

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

Hi,

I'm reproducibly running into this issue as well.

I have installed sapmachine11-ea-jdk from https://github.com/SAP/homebrew-SapMachine/. I need to update this every week. I used to do "brew cask upgrade --no-quarantine" which worked fine. Now, since brew cask upgrade is locked, I need to do "brew upgrade --cask --no-quarantine" which will install the updated cask without disablingthe gatekeeper. A "brew reinstall sapmachine11-ea-jdk --no-quarantine" will fix this. Or, alternatively, it seems to work when I set HOMEBREW_CASK_OPTS to "--no-quarantine".

I'd really love if this could be fixed.

Thanks
Christoph

which will install the updated cask without disablingthe gatekeeper.

We never disable Gatekeeper. --no-quarantine simply doesn’t set the quarantine attribute on the download.

A "brew reinstall sapmachine11-ea-jdk --no-quarantine" will fix this.

That directly contradicts the report in this issue. Are you sure that’s what you meant?

I'd really love if this could be fixed.

There’s a reason this is still open: it’s a valid bug report but we did not have the chance to get to it. We take pull requests, if you’re so inclined. Otherwise it’s uncertain when we’ll get to it; it’s low priority.

There’s no reason to think this bug doesn’t occur in all macOS versions. It’s not a macOS bug, it’s ours, so please comment if it doesn’t occur in a specific macOS version (which would be weird), not if it does (which would not).

which will install the updated cask without disablingthe gatekeeper.

We never disable Gatekeeper. --no-quarantine simply doesn’t set the quarantine attribute on the download.

Sorry, I probably used the wrong wording here. I said that because when I do a `brew install --cask --no-quarantine sapmachine11-ea-jre", I can see the warning "macOS's Gatekeeper has been disabled for this Cask". Having said that, I just tested this install command again and it installed my cask fine without quarantine. I can run java -version.

A "brew reinstall sapmachine11-ea-jdk --no-quarantine" will fix this.

That directly contradicts the report in this issue. Are you sure that’s what you meant?

I'm pretty sure it is. I'll test this later this week when there will be an update for sapmachine11-ea-jdk/jre and report here.

I'd really love if this could be fixed.

There’s a reason this is still open: it’s a valid bug report but we did not have the chance to get to it. We take pull requests, if you’re so inclined. Otherwise it’s uncertain when we’ll get to it; it’s low priority.

Sure. :) Unfortunately I'm not so much into the brew source code and ruby and my time also doesn't permit digging deeper. So, priority is all fine given that HOMEBREW_CASK_OPTS to "--no-quarantine" or "brew reinstall --no-quarantine" help. I was just worried since I had "brew cask upgrade --no-quarantine" working before and now this got locked out in favor of "brew upgrade --cask --no-quarantine" which obviously doesn't honor --no-quarantine correctly at the moment.

Thanks for your great efforts with brew :)

A "brew reinstall sapmachine11-ea-jdk --no-quarantine" will fix this.

That directly contradicts the report in this issue. Are you sure that’s what you meant?

I'm pretty sure it is. I'll test this later this week when there will be an update for sapmachine11-ea-jdk/jre and report here.

OK, I have to correct myself. "brew reinstall --no-quarantine" does not work (as reported). The current workaround is HOMEBREW_CASK_OPTS.

This bug is only partially resolved—for the reinstall case, not the upgrade case. Please reopen.

This bug is only partially resolved—for the reinstall case, not the upgrade case. Please reopen.

I can confirm that. reinstall --no-quarantine works now but ugrade --no-quarantine doesn't.