Unable to find expected entry 'main/binary-i386/Packages - Chrome [duplicate]

1

This question already has an answer here:

I recently noticed while installing some packages and using the command apt-get update that I ran into the following 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)

As mentioned in THIS recent question on Ask Ubuntu, Chrome will no longer be supported by 32 bit systems, however I am currently running 64 bit Ubuntu 14.04, with libc6:i386 libncurses5:i386 libstdc++6:i386 installed for 32 bit application support.

Am I seeing this error because dpkg is looking for the i386 packages as a result of the aforementioned install of libc6:i386 libncurses5:i386 libstdc++6:i386?

How do I resolve this error?

EDIT - (I was not able to resolve this question with simply updating Chrome as mentioned in the other thread, and not all the information in the other answer was...

0 0
2

I recently noticed while installing some packages and using the command apt-get update that I ran into the following 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)

As mentioned in THIS recent question on Ask Ubuntu, Chrome will no longer be supported by 32 bit systems, however I am currently running 64 bit Ubuntu 14.04, with libc6:i386 libncurses5:i386 libstdc++6:i386 installed for 32 bit application support.

Am I seeing this error because dpkg is looking for the i386 packages as a result of the aforementioned install of libc6:i386 libncurses5:i386 libstdc++6:i386?

How do I resolve this error?

EDIT - (I was not able to resolve this question with simply updating Chrome as mentioned in the other thread, and not all the information in the other answer was present at the time I posted this).

...

0 0
3

There are two causes but in your case is that you have configured multiarch to ask for i386 packages while that repository is amd64 exclusive. The same would be happened if you set arm64 or any other architecture as foreign architecture with dpkg.

There are three ways to go:

If the repository should have amd64 packages, contact the maintainer and let them know. If you actually don't want/need foreigns architectures installed on your system you can disable them with dpkg --remove-architecture.

You can set your sources.list to only ask for the architecture the repository is supposed to provide, so apt doesn't try to ask for them. Something like this:

deb [ arch=amd64 ] http://codezen.org/debian sid main

Other causes

This can also happen if components (main, contrib, security, etc.) or type of packages (sources vs binaries) aren't available in the repository. This can be identified by the string main/binary-i386/Packages. Here, main is the component, and...

0 0
4

The warning that you see is caused by Google's dropping of support for 32-bit Google Chrome for Linux. You can fix that by looking at http://askubuntu.com/questions/724093/no-more-updates-for-google-chrome-apt-get-update-error.

However, the aforementioned warning you see is entirely unrelated to your attempt to upgrade vlc. Looking at https://launchpad.net/~videolan/ archive/ubuntu/stable-daily, the PPA you added does not have an installation candidate for Ubuntu 14.04 (Trusty Tahr). If you want to use this PPA, you are going to have to upgrade to 15.10, 16.04 or 16.10. I would recommend 16.04 because 16.04 is an LTS while 15.10 will reach end-of-life in a couple of weeks and 16.10 is a developmental version that may be too unstable for you.

If you want to keep using 14.04, then you can simply remove the PPA and just install vlc from the Ubuntu repositories, but this version will be outdated relative to what is available to in the...

0 0
5

Recently, while updating your Ubuntu or Linux Mint system, you might have come across an update error that says:

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.

On Ubuntu the error looks like:

While on Linux Mint, the Software Updater throws the following error:

Don’t feel alone. This is a common issue faced by many after Google Chrome has ended support for 32 bit Linux system. We already know about it. This change was supposed to impact only 32 bit Linux systems but it seems that even users running Ubuntu 14.04 or higher on a 64 bit systems are also affected by this change.

While this error is tiny, trivial, it is highly annoying. Good news is that it is really easy to get rid of this...

0 0
6

Google Chrome 65 Released. It is a freeware web browser developed by Google Inc. It is most popular browser and used by millions of users. It provides a long list of development tools for web developers. Google Chrome is available for Linux, Windows and Mac OS. The Google Chrome 65 stable version has been released to download and install with various bug fixes and improvements. This tutorial will help you to install or upgrade Google Chrome to latest stable release on Ubuntu 18.04, 16.04 LTS, 14.04 LTS and LinuxMint 18/17.

Why use Google Chrome?

You have multiple web browsers as alternatives to chrome, but still, most of the users prefer to use Google Chrome. Below are few my point of views about Chrome.

First thing is that Google chrome is developed by Google, Every one trust on Google products.Google chrome is very light weight and fast web browserIt provides easy to access, We can browser web site and search with same box.Google chrome created individual...
0 0
7

Google Chrome has dropped 32bit Linux builds

Google announced plans to discontinue 32-bit Google Chrome for Linux this March, and, bang on cue, it has.

The search engine has pulled 32-bit Chrome builds from the official Chrome repo, which gets added to Ubuntu Software Sources when the app is first installed.

Some 64-bit Ubuntu systems caught in the cross-hairs of the deprecation are now throwing a small, yet very annoying, error when performing an apt update.

The ‘failed to fetch error that appears in the Terminal says:

“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)”

Alternatively you may see:

”Skipping acquire of configured file ‘main/binary-i386/Packages’ as repository ‘http://dl.google.com/linux/chrome/deb stable InRelease’ doesn’t support architecture ‘i386’”

If you do see one...

0 0
8

As

announced

back in December, Google stopped supporting Google Chrome on 32-bit Linux starting this month. Users running a 32bit Linux distribution are advised to stop using Google Chrome because, while it will continue to work, it will no longer receive any updates (including no security fixes).

The 32-bit build configurations for Chromium continues to be supported, so you can still use Chromium browser on 32-bit Linux distributions.


Because the official Google Chrome repository no longer provides 32-bit packages, 64-bit Ubuntu/Debian users will notice an error when updating the software sources, which looks as follows:

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) Some index files failed to download. They have been ignored, or old ones used instead.
To fix this error on Ubuntu/Debian 64-bit

, the...

0 0
9
Failed To Fetch Google Chrome Repository -

Why this happen? This caused Google dropped Google Chrome support for GNU/Linux 32bit distribution. As announced in December, Google plans to discontinue 32-bit Google Chrome for Linux this March.


However Chromium browser is goo choice to replace Google Chrome, because the 32bit build configurations for Chromium continues to be supported.

So this is the line that terminal printed when resynchronizes the local index of packages files (sudo apt-get update) :

"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)"

or alternatively you may see

"Skipping acquire of configured file ‘main/binary-i386/Packages’ as repository ‘http://dl.google.com/linux/chrome/deb stable InRelease’ doesn’t support architecture ‘i386’"

Why Google Dropping Support?

...

0 0
10

This is my first post here since I'm new user of Ubuntu Mate. I have been doing some distro hopping in recent times since I upgraded my computer to Haswell i7, and my previous OS has some issues with graphic drivers (FreeBSD).

So I'm learning "linux ways", and after some testing of other distros, I decided to stick with you guys. Experience is super slick, love how things just work. But here comes my first observation. I noticed some error logs while updating:

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.

Now, I'm pretty sure I did not messed with ppa entries at all, but if I try to open that url in error, it gives me back 404. Or did google change url and I just need to enter new path?

Best...

0 0
11

Hi, I'm trying to install openalpr on my Raspberry Pi (B+) and I'm running these commands based on installation manuals available here:

https://github.com/openalpr/openalpr/wi ... u-Linux%29

Code: Select all

echo "deb [arch=amd64] http://deb.openalpr.com/master/ openalpr main" | sudo tee /etc/apt/sources.list.d/openalpr.list sudo apt-get update sudo apt-get install openalpr

during the apt-get update I get errors like this:

Fetched 6908 kB in 1min 32s (74.7 kB/s)
W: Failed to fetch http://raspberrypi.collabora.com/dists/wheezy/Release Unable to find expected entry 'rpi/binary-i386/Packages' in Release file (Wrong sources.list entry or malformed file)

W: Failed to fetch http://repository.wolfram.com/raspbian/ ... le/Release Unable to find expected entry 'non-free/binary-i386/Packages' in Release file (Wrong sources.list entry or malformed file)

W: Failed to fetch http://mirrordirector.raspbian.org/rasp ... zy/Release Unable to find expected...

0 0
12

I added a third party repository and now I'm seeing this warning while updating my packages list:

W: Failed to fetch http://codezen.org/debian/dists/sid/Release Unable to find expected entry 'main/binary-i386/Packages' in Release file (Wrong sources.list entry or malformed file)

Why is that?

Answers

There are two causes but in your case is that you have configured multiarch to ask for i386 packages while that repository is amd64 exclusive. The same would be happened if you set arm64 or any other architecture as foreign architecture with dpkg.

There are three ways to go:

If the repository should have amd64 packages, contact the maintainer and let them know. If you actually don't want/need foreigns architectures installed on your system you can disable them with dpkg --remove-architecture. You can set your sources.list to only ask for the architecture the repository is supposed to provide, so apt doesn't try to ask for them. Something like this:...
0 0
13

Tagged as: apt google-chrome linux

Recently, Google deprecated the i386 build of Google Chrome, which means that apt not produces an error when you try to 'apt-get update'.

This is the error that you may have encountered:

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)

This is because Google has deprecated 32-bit Chrome installations. Luckily, it's easy to fix the error. Just run this command in your terminal:

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

Modify this line:

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

To read this instead:

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

Then you can update without the error occurring...

0 0
14

Hi

I am another one having a problem getting updates. I have tried running updates automatically and get the error, "Couldn't fetch the package cache information lists"

I have run

sudo apt-get update

in the terminal, it appears to work but the following text appears at the end;


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.

Does this mean most of the updates have installed, or did the update process fail, and of course how to fix it? :-)
...

0 0
15

After following the first two instructions on https://www.hipchat.com/downloads#linux I then run

sudo apt-get update

A lot of packages are updated but the operation ends with the warnings and errors:

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) W: Failed to fetch https://atlassian.artifactoryonline.com/atlassian/hipchat-apt-client/dists/rafaela/main/binary-amd64/Packages HttpError404 W: Failed to fetch https://atlassian.artifactoryonline.com/atlassian/hipchat-apt-client/dists/rafaela/main/binary-i386/Packages HttpError404 E: Some index files failed to download. They have been ignored, or old ones used instead.

Checking to see what's in the .list file:

$ cat /etc/apt/sources.list.d/atlassian-hipchat4.list deb https://atlassian.artifactoryonline.com/atlassian/hipchat-apt-client rafaela main

If I then try the install...

0 0
16
...
0 0
17

I tried searching first regarding this error.

I have a new Pi3 with Jessie (full version) installed. I already (successfully) completed apt-update, apt-upgrade, apt dist-upgrade. Done there. But when I get to installing OpenVPN using:

$ wget -O - https://swupdate.openvpn.net/repos/repo ... pg|apt-key add -
$ echo "deb http://build.openvpn.net/debian/openvpn/testing jessie main" > /etc/apt/sources.list.d/openvpn-aptrepo.list
$ apt-get update && apt-get install openvpn

I get this error at about 99% through the install.


W: Failed to fetch http://build.openvpn.net/debian/openvpn ... ie/Release Unable to find expected entry 'main/binary-armhf/Packages' in Release file (Wrong sources.list entry or malformed file)

I have been searching Google for hours regarding the following issue. It looks like something might be wrong with the installer. Both Testing Jessie main, Stable Jessie main, any of the Release Jessie main, throw this same...

0 0