Moving from Local to Remote Development.This also includes 32-bit builds of Google Chrome OS and Google Chrome for ARM, in addition to Chroium derivatives like Opera. However, for those users who still use the 32-bit version of Google Chrome, the source code is still available to compile and run on their distro, or also to be able to download it from the repo of the distro in which they have to work. However, for those people who are still using Ubuntu 12.04 (Precise Pangolin) and Debian 7 (Wheezy) regardless of whether they are using the 32-bit and 64-bit versions, Google Chrome support has been completely terminated, so the only option what remains is to simply uninstall the browser and use nothing more and nothing less than the version of Chromium that is in said repositories, use another browser or simply update the respective distribution, in addition to removing the Google Chrome repository. Sudo sed -i -e 's/deb http/deb http/' "/etc/apt//google-chrome.list" Now, for those who are using the 64-bit versions of Ubuntu (exactly, from Trusty) and Debian Jessie, they should run the following command line (if you don't have SUDO configured, I suggest you run it under ROOT): W: Fallo al obtener No se pudo encontrar la entrada esperada «main/binary-i386/Packages» en el archivo «Release» (entrada incorrecta en «sources.list» o fichero mal formado) You have probably got a message like this: However, this measure became effective on Tuesday, March 3, which completely removed the repository for the 32-bit version of Google Chrome. Last Friday, I came across the unpleasant surprise in which when updating Google Chrome, the update system told me that it needed the 32-bit repository, which it had already been announced since December of last year.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |