New issue
Advanced search Search tips

Issue 592209 link

Starred by 8 users
Status: Duplicate
Merged: issue 591480
Owner: ----
Closed: Mar 2016
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

apt-get update results into error

Reported by vanantwe...@gmail.com, Mar 5 2016 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.11 Safari/537.36

Steps to reproduce the problem:
1. Try checking for updates on a debian based system (64 bit) via 'apt-get update'

What is the expected behavior?
No errors, normal update logic

What went wrong?
Got error:
W: 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)

Did this work before? Yes Before 49 was released

Chrome version: 49  Channel: stable
OS Version: Ubuntu 14.04
Flash Version: N/A

Expected an update of the configuration to no longer request the i386 packages

Comment 1 by justhink...@gmail.com, Mar 5 2016 

Looks like this is affecting 64-bit Ubuntu and Ubuntu based distributions as I've seen several reports and comments regarding this situation. When installing 64-bit Google Chrome (before Google discontinued the 32-bit version) the following line was added to the sources list for the distro:

deb http://dl.google.com/linux/chrome/deb/ stable main

This no longer works for 64-bit Ubuntu and Ubuntu based distros. Attempting to update the apt-cache in order to update the system throws this error:

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)

Again, this is on a 64-bit distro with 64-bit Google Chrome installed. When Google discounted the 32-bit version of Chrome something obviously went wrong when re-configuring the Chrome repository(s) so the sources list line for Google Chrome was no longer valid.

Hoping this can be fixed officially.

Comment 2 by richard....@gmail.com, Mar 5 2016 

The "deb" prefix needs to be changed to "deb [arch=amd64]".  64-bit ubuntu by default will try to scan for package manifests for both 32bit and 64bit unless you tell it NOT to.

Comment 3 by ilqk@google.com, Mar 6 2016 

This is a duplicate of  issue 591480 .

Comment 4 by brajkumar@chromium.org, Mar 7 2016

Mergedinto: 591480
Status: Duplicate (was: Unconfirmed)
As per comment #3 issue looks similar to  bug 591480 , Hence merging in to it. Feel free to undupe if it's a different issue.

Thanks!
►

Sign in to add a comment