Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

brew cask outdated showing old versions of renamed casks as latest #46067

Closed
wickles opened this issue Apr 18, 2018 · 6 comments
Closed

brew cask outdated showing old versions of renamed casks as latest #46067

wickles opened this issue Apr 18, 2018 · 6 comments

Comments

@wickles
Copy link
Contributor

wickles commented Apr 18, 2018

Description of issue

After brew updateing today, Casks that have been renamed are showing old versions as newest version when running brew cask outdated.

I realize I can just delete the outdated casks, but this never happened before today and could be confusing to users not familiar with the issue detailed in #29716.

Command that failed

> % brew cask outdated --greedy
google-play-music-desktop-player (4.1.1, 4.2.0, 4.4.0, 4.4.1) != 4.3.0
gpgtools (2017.1) != 2016.10_v2
macupdate (6.1.9, latest) != latest
macupdate-desktop (6.1.2, 6.1.3, 6.1.5, 6.1.6, 6.1.7, 6.1.8, 6.1.9) != 6.1.4

(removed lines not relevant to issue)

Relevant cask renames:

google-play-music-desktop-player -> marshallofsound-google-play-music-player (not installed)
gpgtools -> gpg-suite (not installed)
macupdate-desktop -> macupdate
info results
> % brew cask info macupdate-desktop
macupdate-desktop: 6.1.9
https://www.macupdate.com/desktop
/usr/local/Caskroom/macupdate-desktop/6.1.2 (64B)
/usr/local/Caskroom/macupdate-desktop/6.1.3 (64B)
/usr/local/Caskroom/macupdate-desktop/6.1.4 (64B)
/usr/local/Caskroom/macupdate-desktop/6.1.5 (64B)
/usr/local/Caskroom/macupdate-desktop/6.1.6 (64B)
/usr/local/Caskroom/macupdate-desktop/6.1.7 (64B)
/usr/local/Caskroom/macupdate-desktop/6.1.8 (64B)
/usr/local/Caskroom/macupdate-desktop/6.1.9 (64B)
==> Name
MacUpdate Desktop
==> Artifacts
MacUpdate Desktop.app (App)
> % brew cask info google-play-music-desktop-player
google-play-music-desktop-player: 4.4.1
https://www.googleplaymusicdesktopplayer.com/
/usr/local/Caskroom/google-play-music-desktop-player/4.1.1 (64B)
/usr/local/Caskroom/google-play-music-desktop-player/4.2.0 (64B)
/usr/local/Caskroom/google-play-music-desktop-player/4.3.0 (64B)
/usr/local/Caskroom/google-play-music-desktop-player/4.4.0 (64B)
/usr/local/Caskroom/google-play-music-desktop-player/4.4.1 (64B)
==> Name
Google Play Music Desktop Player
==> Artifacts
Google Play Music Desktop Player.app (App)
> % brew cask info gpgtools
gpgtools: 2017.1
https://gpgtools.org/
/usr/local/Caskroom/gpgtools/2016.10_v2 (17 files, 21.6MB)
/usr/local/Caskroom/gpgtools/2017.1 (17 files, 28MB)
==> Name
GPG Suite
==> Artifacts
Install.pkg (Pkg)
==> Caveats
Cask gpgtools installs files under /usr/local. The presence of such
files can cause warnings when running "brew doctor", which is considered
to be a bug in Homebrew-Cask.

Output of brew cask doctor

brew cask doctor
> % brew cask doctor
==> Homebrew-Cask Version
Homebrew-Cask 1.6.1-18-g714bf51
caskroom/homebrew-cask (git revision bcad7; last commit 2018-04-18)
==> macOS
10.13.4
==> SIP
Enabled (custom configuration)

configuration:
apple internal: disabled
kext signing: enabled
filesystem protections: enabled
debugging restrictions: disabled
dtrace restrictions: enabled
nvram protections: enabled
basesystem verification: enabled
==> Java
10, 9.0.4, 9, 1.8.0_144, 1.8.0_131, 1.8.0_121, 1.8.0_112
==> Homebrew-Cask Install Location
<NONE>
==> Homebrew-Cask Staging Location
/usr/local/Caskroom
==> Homebrew-Cask Cached Downloads
~/Library/Caches/Homebrew/Cask (3 files, 164MB)
==> Homebrew-Cask Taps:
/usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask (3958 casks)
/usr/local/Homebrew/Library/Taps/caskroom/homebrew-drivers (143 casks)
/usr/local/Homebrew/Library/Taps/caskroom/homebrew-versions (176 casks)
==> Contents of $LOAD_PATH
/usr/local/Homebrew/Library/Homebrew/cask/lib
/usr/local/Homebrew/Library/Homebrew
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/gems/2.3.0/gems/did_you_mean-1.0.0/lib
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/site_ruby/2.3.0
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/site_ruby/2.3.0/x86_64-darwin9.0
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/site_ruby/2.3.0/universal-darwin9.0
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/site_ruby
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/vendor_ruby/2.3.0
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/vendor_ruby/2.3.0/x86_64-darwin9.0
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/vendor_ruby/2.3.0/universal-darwin9.0
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/vendor_ruby
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/2.3.0
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/2.3.0/x86_64-darwin9.0
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/2.3.0/universal-darwin9.0
==> Environment Variables
LC_ALL="en_US.UTF-8"
PATH="/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/Homebrew/Library/Homebrew/shims/scm"
SHELL="/bin/zsh"
@commitay
Copy link
Contributor

but this never happened before today

Might be related to Homebrew/brew#4072. @reitermarkus

Renames should be: ...

Not sure I understand what this means?

@wickles
Copy link
Contributor Author

wickles commented Apr 18, 2018

Not sure I understand what this means?

Just noting how the casks were renamed. Not especially important.

@commitay
Copy link
Contributor

This is only an issue because somehow there are multiple versions of each in /Caskroom/* when there shouldn't be. Not sure how would have happened.

Closing as this doesn't need to be fixed if it only impacts multiple copies in /Caskroom.

@wickles
Copy link
Contributor Author

wickles commented Apr 18, 2018

That is the expected behavior for Caskroom leftovers from before brew cask upgrade was implemented (see #9586), or for those of us avoiding brew cask upgrade for whatever reason (e.g. #42112, a followup or reopen there would be helpful btw).

@commitay
Copy link
Contributor

commitay commented Apr 18, 2018

a followup there would be helpful btw

#42112 (comment)

@commitay
Copy link
Contributor

That is the expected behavior for Caskroom leftovers from before

We aren't going to fix something that isn't a problem with the current implementation.

@Homebrew Homebrew locked and limited conversation to collaborators Aug 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants