brew cask install little-snitch - "Filename has an unknown suffix" error #92674
Comments
|
As mentioned in #92692 (comment):
|
|
i can confirm this issue |
Ah lusciousness. I'm somewhat pleased it's not just me, although sorry to hear you're experiencing the same issue. I thought I'd mucked things up on my individual machine! 👍🏻 |
|
no need to be sorry i just installed it to confirm or deny the report to move things along here :) |
|
Comparing LittleSnitch-5.0.1.dmg to LittleSnitch-5.0.2.dmg with WhatsYourSign, I notice there's a difference in item type:
|
|
i guess this is the problem
should be using the DMG strategy |
|
Firstly, out of an abundance of caution, I checked the integrity of the DMG, and all looks good and valid, having followed Objective Development's advice on checking download integrity: Comparing the two DMGs with A quick
The 10.15 minimum requirement might also explain why @vitorgalvao found the DMG to be corrupt, as from this I speculate he may have been opening it from a 10.14 machine, perhaps? Given that LS5 requires a minimum of Big Sur (11.0) to operate, I suppose it makes sense that they switched to this new format for the disk image. As someone who knows very-little about this sort of thing, I suspect that something somewhere in brew is thinking these shiny new DMGs are XZ compressed and therefore not handling them appropriately? Certainly the previous tool I used to inspect them also alluded to XZ compression. A brief Google search brings up results that seem to indicate that XZ is based on the lzma algorithm. Edit: LS confirmed via Twitter that move to ULMO/lzma was intentional and it results in a significantly smaller download (there's around a 10MB difference between LittleSnitch-5.0.1.dmg and LittleSnitch-5.0.2.dmg!). |
Yep! |
|
Having now upgraded to Big Sur, I can confirm this error, and all my investigations this far to rectify this have been in vain. |
|
Ok. I'll prefix this with saying I know very-little about Ruby, but please do take a look at the following commit, which appears to fix the issue and allowed me to install No idea as to what else moving |
|
I guess we have no other comment preventing |
Sure thing! Draft PR in at Homebrew/brew#9161 - As I mentioned in the PR, I am not at all proficient in Ruby and have only tested this change on a single system running macOS Big Sur, so any and all advice/feedback would be appreciated! |
|
Fixed in Homebrew/brew#9161. |
|
I'm getting this exact error with 5.0.3. I checked the dmg and it's still XZ compressed data. Is anyone else seeing this problem now? |
|
@denkristoffer please post the output of |
|
|
Ok, most likely the fix will be included when they bump up the version of Homebrew to 2.5.12., which should happen soon(ish). |
|
2.5.12 is out now so |
and others
General troubleshooting steps
--force.brew update-reset && brew updateand retried my command.brew doctor, fixed as many issues as possible and retried my command.Description of issue
Okay, firstly apologies. This may be an inappropriate issue being raised, given that I'm now running Big Sur, but:
brew cask install little-snitch-edbrew cask uninstall little-snitch, intending to then do the next stepbrew cask install little-snitchI've tried, the following, to no avail:
brew update-reset && brew updatebrew cask uninstall --force little-snitchbrew cask zap --force little-snitchI've also tried manually editing the formula to the 4.X version so that I can proceed through the workflow I did before Ibrew cask uninstall little-snitchto no avail.There seems to be something left that it's trying to purge, to no avail. I'm understanding this to be the case from==> Purging files for version 5.0.2 of Cask little-snitchwhenlittle-snitchis not deemed to be installed.If I could please ask for someone's assistance on this, it would be tremendously appreciated! I totally appreciate that Big Sur is currently unsupported but this is doing my absolute nut and not sure it's Big Sur related specifically (I could be wrong). Have been attempted to resolve this specific issue for over three hours, now. Many thanks!
Command that failed
Output of command with
--verbose --debugHave shortened unique folder names to
xxxandyyyOutput of
brew doctor --verboseOutput of
brew tapThe text was updated successfully, but these errors were encountered: