SHA256 mismatch on fxfactory Cask 8.0.13,7767 #5155
-
Output of
|
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 2 replies
-
https://docs.brew.sh/Common-Issues#cask---checksum-does-not-match |
Beta Was this translation helpful? Give feedback.
-
I filed an PR of updating the checksum, Homebrew/homebrew-cask#168220 |
Beta Was this translation helpful? Give feedback.
-
All,
I have reached out to FXFactory support and asked for them to provide a revision to their product as this is throwing of SHA checks for us (their customers).
Thanks,
SS
… On Jun 27, 2024, at 1:24 PM, Patrick Linnane ***@***.***> wrote:
This isn't an issue with Homebrew. What's happening is that the upstream developer is releasing a version, and at some point afterward replacing the archive for some reason without changing the version number. This is a very poor practice, and should be discussed with upstream.
—
Reply to this email directly, view it on GitHub <#5155 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACLZ6UFZUUHACSIHG4UKDVLZJRRFFAVCNFSM6AAAAABDYC7QZKVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQOJXHA3DK>.
You are receiving this because you authored the thread.
|
Beta Was this translation helpful? Give feedback.
-
Here is the response from FXFactory Support. It does not sound as if they will be responsive to changing this immediately, so I would think this repo should be retired as it sounds that they will continue doing this for the time being.
Hi Steven,
I apologize for the inconvenience. We received a similar report a few months ago, where we explained that our software will receive numerous unscheduled updates, sometimes just to address concerns of a single customer. This is the nature of the video industry, where we know customers are on deadlines and they are our top priority. The side effect is that within the same release day we might end up with two or more versions of the same installer. We don't do this to disrupt management tools... and hopefully we can adopt some new naming conventions to avoid this type of problem on your end.
…--
Gabe
***@***.*** ***@***.***>
On Jun 27, 2024, at 4:43 PM, ***@***.*** wrote:
All,
I have reached out to FXFactory support and asked for them to provide a revision to their product as this is throwing of SHA checks for us (their customers).
Thanks,
SS
> On Jun 27, 2024, at 1:24 PM, Patrick Linnane ***@***.***> wrote:
>
>
> This isn't an issue with Homebrew. What's happening is that the upstream developer is releasing a version, and at some point afterward replacing the archive for some reason without changing the version number. This is a very poor practice, and should be discussed with upstream.
>
> —
> Reply to this email directly, view it on GitHub <#5155 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACLZ6UFZUUHACSIHG4UKDVLZJRRFFAVCNFSM6AAAAABDYC7QZKVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQOJXHA3DK>.
> You are receiving this because you authored the thread.
>
|
Beta Was this translation helpful? Give feedback.
-
Could FXFactory just be removed as they will not confirm to the standard? Or, perhaps the SHA256 value could be updated since they are acknowledging their behavior.
SS
… On Jun 28, 2024, at 8:28 AM, ***@***.*** wrote:
Here is the response from FXFactory Support. It does not sound as if they will be responsive to changing this immediately, so I would think this repo should be retired as it sounds that they will continue doing this for the time being.
Hi Steven,
I apologize for the inconvenience. We received a similar report a few months ago, where we explained that our software will receive numerous unscheduled updates, sometimes just to address concerns of a single customer. This is the nature of the video industry, where we know customers are on deadlines and they are our top priority. The side effect is that within the same release day we might end up with two or more versions of the same installer. We don't do this to disrupt management tools... and hopefully we can adopt some new naming conventions to avoid this type of problem on your end.
--
Gabe
***@***.*** ***@***.***>
> On Jun 27, 2024, at 4:43 PM, ***@***.*** wrote:
>
> All,
>
> I have reached out to FXFactory support and asked for them to provide a revision to their product as this is throwing of SHA checks for us (their customers).
>
> Thanks,
> SS
>
>> On Jun 27, 2024, at 1:24 PM, Patrick Linnane ***@***.***> wrote:
>>
>>
>> This isn't an issue with Homebrew. What's happening is that the upstream developer is releasing a version, and at some point afterward replacing the archive for some reason without changing the version number. This is a very poor practice, and should be discussed with upstream.
>>
>> —
>> Reply to this email directly, view it on GitHub <#5155 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACLZ6UFZUUHACSIHG4UKDVLZJRRFFAVCNFSM6AAAAABDYC7QZKVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQOJXHA3DK>.
>> You are receiving this because you authored the thread.
>>
>
|
Beta Was this translation helpful? Give feedback.
I filed an PR of updating the checksum, Homebrew/homebrew-cask#168220