@InakyMartinez commented on GitHub:
Hi, So sorry for my late response here, but we wrote an official recipe label, years ago and it's working for us. Let me know if you need any further…
@mjsanders commented on GitHub:
It really seems a temporary issue. (My guess a small difference in update repositories). I have removed Chrome, installed an old version (125.x) and ran the same…
@Theile commented on GitHub:
You are right.
At one time we decided to more the reading of arguments to be after the label definition in the script, and then lsagent broke.
Right now we are…
@datalone commented on GitHub:
Ok, good to know. Thanks for the quick response.
@mikecalbreeeezy commented on GitHub:
I'm having the same issue where it goes through the installomator script but doesn't update the browser so it gets stuck on the same version
@mjsanders commented on GitHub:
I see the same issue. I have used the appNewVersion from the labels online (4 months old) ` appNewVersion=$(getJSONValue "$(curl -fsL "https://versionhistory.googl…
@sslawter commented on GitHub:
Same issue trying to update from 131.0.6778.205 to 131.0.6778.265.
2025-01-08…
@AymenAbb commented on GitHub:
I couldn't replicate this issue on googlechromepkg. I had an older package installed (I didn't open it), then ran the installomator script using self service for…
@sjurlohne commented on GitHub:
2024-05-21 11:24:25 : REQ : carboncopycloner : ################## Start Installomator v. 10.5, date 2023-10-15 2024-05-21 11:24:25 : INFO : carboncopycloner :…
@jhawkinsgg commented on GitHub:
I've also created a PR for this #1956
@AymenAbb commented on GitHub:
Implement #1569 manually until a new version of installomator is out
@acodega commented on GitHub:
Dup of #1946 which is linked to a PR fix