Issue metadata
Sign in to add a comment
|
Debian google-chrome-stable packages causes apt-get update to fail
Reported by
hyperba...@gmail.com,
Mar 3 2016
|
||||||||||||||||||||||
Issue descriptionChrome Version : 49.0.2623.75 URLs (if applicable) : Other browsers tested: N / A What steps will reproduce the problem? 1. Install google-chrome-stable 2. Run apt-get update 3. Error appears What is the expected result? Apt-get update should not give an error. What happens instead? This error is returned: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release Unable to find expected entry 'main/binary-i386/Packages' in Release file (Wrong sources.list entry or malformed file) The solution is to change the /etc/apt/sources.list.d/google-chrome.list file to the following: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main The only thing changed is the [arch=amd64]. It seems without this, apt is trying to retrieve i386 packages, which do not exist according to the Release file: Origin: Google, Inc. Label: Google Suite: stable Codename: stable Version: 1.0 Date: Wed, 02 Mar 2016 20:06:03 +0000 Architectures: amd64 Components: main Description: Google chrome-linux repository. MD5Sum: 89704f9af9e6ccd87c192de11ba4c511 145 main/binary-amd64/Release f6b564f73fe97e866a0a5d093cae6006 4162 main/binary-amd64/Packages 8e9eca702d86b5262e58558f18a43377 963 main/binary-amd64/Packages.gz 01e89d641ae66e265bbd28d0ae56b23e 1191 main/binary-amd64/Packages.bz2 SHA1: 153199d8f866350b7853365a4adc95ee687603dd 145 main/binary-amd64/Release 6958758454ad2d56383996b75e91a42f381ad0b7 4162 main/binary-amd64/Packages 05f149ee4d2573f77f3bedc5488da595ac96f42a 963 main/binary-amd64/Packages.gz ca925350845fc461954148f34730a1be2ee6f9be 1191 main/binary-amd64/Packages.bz2 Possibly, this problem is caused due to my 64-bit system being multi-arch. I cannot make it 64 bit only, as that would require me to uninstall all 32-bit packages. The way I see it, because only amd64 packages are delivered by the Google repository, it would be safe to edit the sources.list file with the fix provided. The issue right now is that this fix would have to be done after every google-chrome-stable update, because the google-chrome-stable package manages the sources.list file.
,
Mar 3 2016
,
Mar 4 2016
hyperbaton@Could you please check and confirm if this is duplicate of Issue 591480 or not, so that we can dupe this issue.
,
Mar 4 2016
I'd love to check, but I can't view the issue: You do not have permission to view the requested page. Reason: User is not allowed to view this issue
,
Mar 4 2016
every time Chrome updates, I run this: sudo sed -i -e 's/deb http/deb [arch=amd64] http/' "/etc/apt/sources.list.d/google-chrome.list"
,
Mar 7 2016
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ashej...@chromium.org
, Mar 3 2016