Open Baplar opened 1 year ago
Apparently I just re-discovered an already known workaround mentioned in an existing issue: https://github.com/CircleCI-Public/browser-tools-orb/issues/90#issuecomment-1698052540
Had to switch to chrome v118 because of a bug found in v119 (released yesterday) and got
Google Chrome is not currently installed; installing it
Preparing Chrome installation for Debian-based systems
2023-11-01 19:25:09 URL:https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_118.0.5993.117-1_amd64.deb [104057764/104057764] -> "/tmp/chrome.deb" [1]
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'google-chrome-stable' instead of '/tmp/chrome.deb'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
google-chrome-stable : Depends: libu2f-udev but it is not installable
E: Unable to correct problems, you have held broken packages.
/bin/bash: line 129: google-chrome-stable: command not found
Google Chrome v118.0.5993.117 (stable) failed to install.
Exited with code exit status 1
Workaround helped.
Had to switch to chrome v118 because of a bug found in v119 (released yesterday) and got
@bondar is the bug you found in Chrome 119 documented somewhere? We are also having issues with it - see #99
Description
Fix script for installing specific Chrome version with APT
Checklist
Motivation, issues
When installing a specific version of Chrome on a Debian-based distro, the APT repositories were not refreshed by running
apt-get update
beforehand, leading to the install process failing due to unresolvable dependencies:Adding this update command before the install command fixes the issue.
Workaround
On an affected job, adding a step to run
apt-get update
before theinstall-chrome
step fixes the resolution issue, as we manually perform the repository update before the script is run.In other words, in the current version, this fails:
But this works: