A Glitch with the Chrome for Linux Package Repository

One of the software packages I have installed on the computer ‘Phoenix’ is “Google Chrome”, for Debian / Linux. And this package is eligible for upgrades via Package Manager because Google makes the binaries available. In order for the upgrades to take place, an ‘apt-get update’ command needs to succeed, with this file installed:


/etc/apt/sources.list.d/google-chrome.list

One problem I’ve encountered recently, is that because my computer is set up to pull both the 32-bit and the 64-bit repositories, I get an error message telling me that there is apparently no more 32-bit version on the Google servers. And so the line of code that is needed in this file requires


deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main

The only problem though with this, is that as soon as my Chrome package does update, the ‘[arch=amd64]‘ vanishes, because the package overwrites whatever modifications I made to this file.

It could be that this problem has delayed my getting updates through until now. But unless either the Chrome repository starts to include a 32-bit entry again, or until the same package replaces this file with the specification in-place, this problem will eventually recur.

Dirk

 

Print Friendly, PDF & Email

2 thoughts on “A Glitch with the Chrome for Linux Package Repository”

Leave a Reply

Your email address will not be published. Required fields are marked *

Please Prove You Are Not A Robot *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>