Replies: 3 comments 6 replies
-
That is not an official tap. You will need to reach out to the maintainer of the tap since we have no control over its contents. |
Beta Was this translation helpful? Give feedback.
-
Since we did not change anything regarding that tap for several years now, but it started to break only recently, I believe this is a bug in homebrew, not in the tap itself. |
Beta Was this translation helpful? Give feedback.
-
Upon investigation I found out that homebrew apparently caches the OLD tar archive downloaded in the last install/upgrade. When new metadata is available (having a new hash and new version number) it SAYS it's downloading the new tar archive, but somehow uses the old cached one --> the hashes of the OLD tar archive don't match the NEW metadata. I've just implemented a workaround: monal-im/homebrew-monal-alpha@da23a3e But I strongly believe that this should not be neccessary and homebrew should not somehow cache the old download in the first place. Edit: the output logged when trying to upgrade suggests the same (
|
Beta Was this translation helpful? Give feedback.
-
Output of
brew config
Output of
brew doctor
➜ ~ brew doctor Your system is ready to brew.
Description of issue
Running into trouble trying to upgrade monal-alpha.
Reproduce
Currently
This is tap + install:
Metadata for this version:
Expected hash is that of the previous version.
Metadata of new version
Expected
Upgrade. Workaround:
brew --cache
Is there something that can be done to allow for easier upgrades?
Relevant casks
monal-alpha
Beta Was this translation helpful? Give feedback.
All reactions