session-buddy: Update the hash to version 4.0.5#1484
session-buddy: Update the hash to version 4.0.5#1484brianmcgillion merged 1 commit intotiiuae:mainfrom
Conversation
|
Tested on Lenovo-X1 (
|
Use the hardcoded version for installPhase. Signed-off-by: Vunny Sodhi <vunny.sodhi@unikie.com>
5dc0b6a to
cc4e106
Compare
There was a problem hiding this comment.
Here, we fetch the crx from https://clients2.google.com, based on the extension id and chrome version, but we don't specify the extension version (and it appears chrome extensions api doesn't even support fetching a given extension version).
When google updates the extension version at https://clients2.google.com, doesn't it cause a hash mismatch since the crx contents changes, causing a mismatch with the FOD hash? Worse, such change would go unnoticed, if the old package is cached.
What will drive the update of these extensions?
There was a problem hiding this comment.
I don't have much idea about chrome extensions, I can check more on it.
There was a problem hiding this comment.
@kajusnau can share more insights, once he's back.
Description of Changes
Use the hardcoded version for installPhase.
Type of Change
Related Issues / Tickets
Checklist
make-checksand it passesTesting Instructions
Applicable Targets
aarch64aarch64x86_64x86_64x86_64Installation Method
nixos-rebuild ... switchTest Steps To Verify: