This is a bug on Chrome's site mostly. We made the design choice to
request all architectures configured and warn about missing ones. You
can tell APT to ignore archs for some sources in your sources.list
entry.
** Changed in: apt (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1554223
Title:
apt-get update fails with "Unable to find expected entry
'main/binary-i386/Packages' in Release file" on pure x86_64 repos
Status in apt package in Ubuntu:
Opinion
Bug description:
(ubuntu-bug wouldn't let me report bugs against apt, go figure.)
I run my own apt repo for a third-party app, and I have to include a
dummy i386 package to avoid an error from apt-get.
Along comes Chrome's decision to desupport i386, and suddenly this problem
matters to a lot of people,
who are all seeing apt-get update fail with:
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)
E: Some index files failed to download. They have been ignored, or old ones
used instead.
While it would be easy for Google to include a dummy i386 package in
their repo, it would be even better if apt-get didn't barf like this
on pure 64 bit repos.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1554223/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
