New issue
Advanced search Search tips

Issue 592046 link

Starred by 3 users

Issue metadata

Status: Duplicate
Merged: issue 591480
Owner: ----
Closed: Mar 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Apt sources.list still refer to i386 packages

Reported by andrey.s...@gmail.com, Mar 4 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:44.0) Gecko/20100101 Firefox/44.0

Steps to reproduce the problem:
After Chrome 49 release the i386 packages are no longer available. Yet the repository, as is described in /etc/apt/sources.list.d/google-chrome.list, does not disable the i386 architecture. Ubuntu/Debian are multiarch systems and because of that apt-get attempts to download packages list for the i386 architecture, even when the host is x86_64. This results in errors in package managers.

Steps to reproduce:
1. On a system with Chrome installed, execute "sudo apt-get update".

What is the expected behavior?
The package lists should update successfully.

What went wrong?
The following error appears:

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 It worked before Chrome 49 release

Chrome version: 49.0.2623.75  Channel: stable
OS Version: Kubuntu 15.10
Flash Version: Shockwave Flash 20.0 r0

The architecture can be limited to x86_64 if the repo line is changed to:

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

Note the arch parameter. It does work when I change it locally, but only for a while because apparently Chrome packaging scripts change the line back and the error returns.
 

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

This is a duplicate of  issue 591480 .

Comment 2 by mmoss@chromium.org, Mar 7 2016

Mergedinto: 591480
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment