For example, the latest version is called Focal Fossa. The releases are named according to the pattern Adjective Animal (both words must begin with the same first letter). These LTS versions reach their end of life after five years of being released. There are two versions released every year and an LTS ( Long Term Support) version once every two years. Ubuntu has a reasonably simple release cycle. While it should not be a problem on most of the devices, it is still important to know if you depend on new hardware technology often, or want the latest version of all software. On Debian 10 I had no need for the above fix.One prime difference between Ubuntu and Debian is the release cycle. In general this forced me to upgrade to Debian 10. Since the version is deprecated these repos needed to point to archive. ![]() In my case Debian 9 is an archived, unsupported, unmaintained version.Īlthough I could "fix" (bypass) the security repo, I had further issues with dependency repos for APT. Why are we having these problems with the security repo? The above is correct if you are just zooming in on the security repo issue. Instead of using the bullseye security repo you could use the stretch archive repo deb stretch main contrib non-free it would be better to stick to the security from the latest release from a security perspective.Running apt with -allow-releaseinfo-change flag - the flag pairing with apt-get update was not recognised.`deb bullseye-security main contrib non-free`Īdd this line in the Dockerfile RUN echo "deb bullseye-security main contrib non-free" > /etc/apt/sources.list The official Debian Security recommendation - To keep your Debian operating system up-to-date with security patches, please add the following line to your /etc/apt/sources.list file These repo definitions are used by apt to fetch update and they are defined in /etc/apt/sources.list This is related to the security repo in particular. They have been ignored, or old ones used instead. ![]() W: The repository ' stretch-updates Release' does not have a Release file.Į: Failed to fetch 404 Not Found Į: Some index files failed to download. W: The repository ' stretch Release' does not have a Release file. The below error came up when running apt-get update W: The repository ' stretch/updates Release' does not have a Release file. Issueįaced this issue on a Debian Stretch (9) Docker image. It feels relevant here too because I couldn't solve the issue with the accepted answer apt-get -allow-releaseinfo-change-suite update and the accepted answer has security implications and doesn't actually tackle the underlying issue of apt getting security updates from the wrong repo. Sudo apt-get -allow-releaseinfo-change update Therefore the answer was not to add the sudo apt-get -allow-releaseinfo-change update to the step executed commands, but substituting the sudo apt-get update command for it. Substituting it for sudo apt-get -allow-releaseinfo-change update resolved my problem. ![]() I observed afterwards that the problem was happening at the first command : sudo apt-get update (and I was adding the other command after.). Sudo Xvfb -ac :99 -screen 0 1280x1024x24 > /dev/null 2>&1 & # optionalĪs it seems to be related to Debian 10 (Buster) (?) I also tried to use another Ubuntu runner version as a runner ( ubuntu-18.04 instead of ubuntu-latest), but nothing changed, same error. uses: uses: Optional: do not specify to match Chrome's version I tried using this action setup-chromedriver but it returned the same error when following the documentation: steps: I read from here and here that adding sudo apt-get -allow-releaseinfo-change update or sudo apt-get dist-upgrade could resolve the problem, but even adding those to my workflow didn't resolve it. Sudo chmod 0755 /usr/local/bin/chromedriverĭocker Image Implementation: docker://guillaumefalourd/ritchiecli:py-3.8 What I tried ![]() Sudo chown root:root /usr/local/bin/chromedriver Sudo mv -f ~/chromedriver /usr/local/bin/chromedriver Sudo apt-get -y install google-chrome-stable Sudo echo "deb stable main" > /etc/apt//google-chrome.list Sudo apt-get install -y unzip xvfb libxi6 libgconf-2-4 gnupg2 Image: docker://guillaumefalourd/ritchiecli:py-3.8 Get:3 buster-updates InRelease Į: Repository ' buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'Į: Repository ' buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'Į: Repository ' buster-updates InRelease' changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'Įrror: Process completed with exit code 100. Some of my GitHub Actions workflows started recently to return this error when installing Chromedriver: Get:1 buster/updates InRelease
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |