Re: binary-i386 packages missing in Release file

[Gene Heskett]

On Tuesday 08 March 2016 10:07:35 Haines Brown wrote:

> On Tue, Mar 08, 2016 at 12:46:14PM +, Lisi Reisz wrote:
> > > > > It sounds as though your Jessie is being identified as Wheezy.
> > > > > You get that warning with Wheezy, even if it is 64bit Wheezy
> > > > > with 64bit Google-Chrome. Presumably because Google hasn't
> > > > > written a string of different error messages for the various
> > > > > different things it has just stopped supporting.
> > > > >
> > > > > Why Jessie is being identified as Wheezy is another question.
> > > > > Is there any reason why you might get identified as Ubuntu
> > > > > 12.04?  Another of the things that has just dropped off
> > > > > Google's cliff.
> > > > >
> > > > > Lisi
> > > >
> > > > Lisi, I have to make a confession. The machine is actually
> > > > running devuan Jessie. That is probably the reason.
> > >
> > > Glad we have solved the mystery - though sadly not your problem.
> > > :-(
> >
> > A potential solution to the problem would be Jessie proper, but
> > without systemd.  It seems to work rather well, in fact, from what
> > people doing so say.  I am about to cross my fingers and try it
> > myself.
> > Lisi
>
> In thinking about it, I'm not sure now if I installed the devuan ISO
> or debian Jessie and then removed systemd. As I tell my wife, I always
> am thinking about higher things! How would I know at this point which
> I did?
>
> Haines

Whether you can get away with that depends on the age of the wet ram, I 
have reached that age (81) where I can recall stuff I did in the '60's, 
but not what, if anything, I had for breakfast for breakfast this 
morning, it takes 2 to 3 cups of caffiene before I can claim to even be 
awake.  That means 2 more before I'm safe around machinery. :)

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: binary-i386 packages missing in Release file

[Lisi Reisz]

On Tuesday 08 March 2016 15:07:35 Haines Brown wrote:
> On Tue, Mar 08, 2016 at 12:46:14PM +, Lisi Reisz wrote:
> > > > > It sounds as though your Jessie is being identified as Wheezy.
> > > > > You get that warning with Wheezy, even if it is 64bit Wheezy
> > > > > with 64bit Google-Chrome. Presumably because Google hasn't
> > > > > written a string of different error messages for the various
> > > > > different things it has just stopped supporting.
> > > > >
> > > > > Why Jessie is being identified as Wheezy is another question.
> > > > > Is there any reason why you might get identified as Ubuntu
> > > > > 12.04?  Another of the things that has just dropped off Google's
> > > > > cliff.
> > > > >
> > > > > Lisi
> > > >
> > > > Lisi, I have to make a confession. The machine is actually running
> > > > devuan Jessie. That is probably the reason.
> > >
> > > Glad we have solved the mystery - though sadly not your problem. :-(
> >
> > A potential solution to the problem would be Jessie proper, but without
> > systemd.  It seems to work rather well, in fact, from what people doing
> > so say.  I am about to cross my fingers and try it myself.
> > Lisi
>
> In thinking about it, I'm not sure now if I installed the devuan ISO or
> debian Jessie and then removed systemd. As I tell my wife, I always am
> thinking about higher things! How would I know at this point which I
> did?

:-))

But if you installed Jessie proper without systemd you shouldn't be having the 
Google-Chrome problems - and we are back to square one!!

Lisi

Re: binary-i386 packages missing in Release file

[Haines Brown]

On Tue, Mar 08, 2016 at 12:46:14PM +, Lisi Reisz wrote:

> > > > It sounds as though your Jessie is being identified as Wheezy.
> > > > You get that warning with Wheezy, even if it is 64bit Wheezy
> > > > with 64bit Google-Chrome. Presumably because Google hasn't
> > > > written a string of different error messages for the various
> > > > different things it has just stopped supporting.
> > > >
> > > > Why Jessie is being identified as Wheezy is another question.
> > > > Is there any reason why you might get identified as Ubuntu
> > > > 12.04?  Another of the things that has just dropped off Google's
> > > > cliff.
> > > >
> > > > Lisi
> > >
> > > Lisi, I have to make a confession. The machine is actually running
> > > devuan Jessie. That is probably the reason.
> >
> > Glad we have solved the mystery - though sadly not your problem. :-(
> 
> A potential solution to the problem would be Jessie proper, but without 
> systemd.  It seems to work rather well, in fact, from what people doing so 
> say.  I am about to cross my fingers and try it myself.
> Lisi

In thinking about it, I'm not sure now if I installed the devuan ISO or
debian Jessie and then removed systemd. As I tell my wife, I always am
thinking about higher things! How would I know at this point which I
did?

Haines

Re: binary-i386 packages missing in Release file

[Lisi Reisz]

On Monday 07 March 2016 18:29:50 Lisi Reisz wrote:
> On Monday 07 March 2016 17:14:40 Haines Brown wrote:
> > On Mon, Mar 07, 2016 at 02:54:22PM +, Lisi Reisz wrote:
> > > On Monday 07 March 2016 00:30:44 Haines Brown wrote:
> > > > On Sun, Mar 06, 2016 at 08:43:56PM -0300, Martinx - ジェームズ wrote:
> > > > > Correct syntax is:
> > > > >
> > > > > --
> > > > > deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
> > > > > --
> > > > >
> > > > > On 6 March 2016 at 20:10, Haines Brown  wrote:
> > > > >
> > > > > On Sun, Mar 06, 2016 at 10:47:26PM +0300, Reco wrote:
> > > > > >       Hi.
> > > > > >
> > > > > > On Sun, 6 Mar 2016 14:34:25 -0500
> > > > > >
> > > > > > Haines Brown  wrote:
> > > > > > > I have jessie installed on an AMD64 machine, which lacks
> > > > > > > any desktop environment.
> > > > > > >
> > > > > > > I downloaded google-chrome AMD64 deb from the Chrome
> > > > > > > website and installed by running dpkg -i on it. It works
> > > > > > > OK. But now I want to add flashplugin-nonfree for it or, if
> > > > > > > that fails to use it for my iceweasel. In order to install
> > > > > > > flashplugin-nonfree I added contrib to the sources.list.
> > > > > > >
> > > > > > > When I do aptitude update, the contrib it hit, but the
> > > > > > > update fails
> >
> > ...
> >
> > > > Progress, but not there yet. In sources.list I have the line:
> > > >
> > > >   deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
> > > >
> > > > When I do # aptitude update, it starts with a warning:
> > > >
> > > >  W: Duplicate sources.list entry
> > > >  http://dl.google.com/linus/chrome/deb stable/main amd64 Packages
> > > >  (/var/lib/apt/lists/dl.google.com_linux_chrome_deb_dists_stable_
> > > > \ main_binary-amd64_packages)
> > > >
> > > >  W: You may want to update the packages lists to correct these
> > > >  missing files
> > > >
> > > > then there are hits and gets and then 100% [working]. However, this
> > > > is followed by a warning 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)
> > > >
> > > >  E: Some index files failed to download. They have been ignored,
> > > > or old ones used instead
> > > >
> > > >  E: Couldn't rebuild package cache.
> > > >
> > > > This didn't stop me from installing the flashplugin-nonfree, but with
> > > > aptitude update I still get more or less the same warnings and
> > > > errors.
> > > >
> > > > Haines
> > >
> > > It sounds as though your Jessie is being identified as Wheezy.  You get
> > > that warning with Wheezy, even if it is 64bit Wheezy with 64bit
> > > Google-Chrome. Presumably because Google hasn't written a string of
> > > different error messages for the various different things it has just
> > > stopped supporting.
> > >
> > > Why Jessie is being identified as Wheezy is another question.  Is there
> > > any reason why you might get identified as Ubuntu 12.04?  Another of
> > > the things that has just dropped off Google's cliff.
> > >
> > > Lisi
> >
> > Lisi, I have to make a confession. The machine is actually running
> > devuan Jessie. That is probably the reason.
>
> Glad we have solved the mystery - though sadly not your problem. :-(

A potential solution to the problem would be Jessie proper, but without 
systemd.  It seems to work rather well, in fact, from what people doing so 
say.  I am about to cross my fingers and try it myself.

Lisi

Re: binary-i386 packages missing in Release file

[Lisi Reisz]

On Monday 07 March 2016 17:14:40 Haines Brown wrote:
> On Mon, Mar 07, 2016 at 02:54:22PM +, Lisi Reisz wrote:
> > On Monday 07 March 2016 00:30:44 Haines Brown wrote:
> > > On Sun, Mar 06, 2016 at 08:43:56PM -0300, Martinx - ジェームズ wrote:
> > > > Correct syntax is:
> > > >
> > > > --
> > > > deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
> > > > --
> > > >
> > > > On 6 March 2016 at 20:10, Haines Brown  wrote:
> > > >
> > > > On Sun, Mar 06, 2016 at 10:47:26PM +0300, Reco wrote:
> > > > >       Hi.
> > > > >
> > > > > On Sun, 6 Mar 2016 14:34:25 -0500
> > > > >
> > > > > Haines Brown  wrote:
> > > > > > I have jessie installed on an AMD64 machine, which lacks any
> > > > > > desktop environment.
> > > > > >
> > > > > > I downloaded google-chrome AMD64 deb from the Chrome website
> > > > > > and installed by running dpkg -i on it. It works OK. But now
> > > > > > I want to add flashplugin-nonfree for it or, if that fails to
> > > > > > use it for my iceweasel. In order to install
> > > > > > flashplugin-nonfree I added contrib to the sources.list.
> > > > > >
> > > > > > When I do aptitude update, the contrib it hit, but the update
> > > > > > fails
>
> ...
>
> > > Progress, but not there yet. In sources.list I have the line:
> > >
> > >   deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
> > >
> > > When I do # aptitude update, it starts with a warning:
> > >
> > >  W: Duplicate sources.list entry
> > >  http://dl.google.com/linus/chrome/deb stable/main amd64 Packages
> > >  (/var/lib/apt/lists/dl.google.com_linux_chrome_deb_dists_stable_ \
> > >  main_binary-amd64_packages)
> > >
> > >  W: You may want to update the packages lists to correct these
> > >  missing files
> > >
> > > then there are hits and gets and then 100% [working]. However, this
> > > is followed by a warning 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)
> > >
> > >  E: Some index files failed to download. They have been ignored, or
> > >  old ones used instead
> > >
> > >  E: Couldn't rebuild package cache.
> > >
> > > This didn't stop me from installing the flashplugin-nonfree, but with
> > > aptitude update I still get more or less the same warnings and errors.
> > >
> > > Haines
> >
> > It sounds as though your Jessie is being identified as Wheezy.  You get
> > that warning with Wheezy, even if it is 64bit Wheezy with 64bit
> > Google-Chrome. Presumably because Google hasn't written a string of
> > different error messages for the various different things it has just
> > stopped supporting.
> >
> > Why Jessie is being identified as Wheezy is another question.  Is there
> > any reason why you might get identified as Ubuntu 12.04?  Another of the
> > things that has just dropped off Google's cliff.
> >
> > Lisi
>
> Lisi, I have to make a confession. The machine is actually running
> devuan Jessie. That is probably the reason.

Glad we have solved the mystery - though sadly not your problem. :-(

Lisi

Re: binary-i386 packages missing in Release file

[Haines Brown]

On Mon, Mar 07, 2016 at 02:54:22PM +, Lisi Reisz wrote:
> On Monday 07 March 2016 00:30:44 Haines Brown wrote:
> > On Sun, Mar 06, 2016 at 08:43:56PM -0300, Martinx - ジェームズ wrote:
> > > Correct syntax is:
> > >
> > > --
> > > deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
> > > --
> > >
> > > On 6 March 2016 at 20:10, Haines Brown  wrote:
> > >
> > > On Sun, Mar 06, 2016 at 10:47:26PM +0300, Reco wrote:
> > > >       Hi.
> > > >
> > > > On Sun, 6 Mar 2016 14:34:25 -0500
> > > >
> > > > Haines Brown  wrote:
> > > > > I have jessie installed on an AMD64 machine, which lacks any
> > > > > desktop environment.
> > > > >
> > > > > I downloaded google-chrome AMD64 deb from the Chrome website and
> > > > > installed by running dpkg -i on it. It works OK. But now I want
> > > > > to add flashplugin-nonfree for it or, if that fails to use it for
> > > > > my iceweasel. In order to install flashplugin-nonfree I added
> > > > > contrib to the sources.list.
> > > > >
> > > > > When I do aptitude update, the contrib it hit, but the update
> > > > > fails

...

> > Progress, but not there yet. In sources.list I have the line:
> >
> >   deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
> >
> > When I do # aptitude update, it starts with a warning:
> >
> >  W: Duplicate sources.list entry
> >  http://dl.google.com/linus/chrome/deb stable/main amd64 Packages
> >  (/var/lib/apt/lists/dl.google.com_linux_chrome_deb_dists_stable_ \
> >  main_binary-amd64_packages)
> >
> >  W: You may want to update the packages lists to correct these
> >  missing files
> >
> > then there are hits and gets and then 100% [working]. However, this
> > is followed by a warning 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)
> >
> >  E: Some index files failed to download. They have been ignored, or
> >  old ones used instead
> >
> >  E: Couldn't rebuild package cache.
> >
> > This didn't stop me from installing the flashplugin-nonfree, but with
> > aptitude update I still get more or less the same warnings and errors.
> >
> > Haines
> 
> It sounds as though your Jessie is being identified as Wheezy.  You get that 
> warning with Wheezy, even if it is 64bit Wheezy with 64bit Google-Chrome. 
> Presumably because Google hasn't written a string of different error messages 
> for the various different things it has just stopped supporting.
> 
> Why Jessie is being identified as Wheezy is another question.  Is there any 
> reason why you might get identified as Ubuntu 12.04?  Another of the things 
> that has just dropped off Google's cliff.
> 
> Lisi

Lisi, I have to make a confession. The machine is actually running
devuan Jessie. That is probably the reason.

Haines

Re: binary-i386 packages missing in Release file

[Lisi Reisz]

On Monday 07 March 2016 00:30:44 Haines Brown wrote:
> On Sun, Mar 06, 2016 at 08:43:56PM -0300, Martinx - ジェームズ wrote:
> > Correct syntax is:
> >
> > --
> > deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
> > --
> >
> > On 6 March 2016 at 20:10, Haines Brown  wrote:
> >
> > On Sun, Mar 06, 2016 at 10:47:26PM +0300, Reco wrote:
> > >       Hi.
> > >
> > > On Sun, 6 Mar 2016 14:34:25 -0500
> > >
> > > Haines Brown  wrote:
> > > > I have jessie installed on an AMD64 machine, which lacks any
> > > > desktop environment.
> > > >
> > > > I downloaded google-chrome AMD64 deb from the Chrome website and
> > > > installed by running dpkg -i on it. It works OK. But now I want
> > > > to add flashplugin-nonfree for it or, if that fails to use it for
> > > > my iceweasel. In order to install flashplugin-nonfree I added
> > > > contrib to the sources.list.
> > > >
> > > > When I do aptitude update, the contrib it hit, but the update
> > > > fails
> > > >
> > > > because:
> > > > > W: Failed to fetch
> > > > > http://dl.google.com/linux/chrome/deb/dists/stable/Release:
> > > > > Unable to find expected entry 'main/binary-i386/Packages' in
> > > > > file
> > >
> > > 1) Locate the line like this in a file inside
> > > /etc/apt/sources.list.d:
> > >
> > > deb http://dl.google.com/linux/chrome/deb/
> > >
> > > 2) Change it to:
> > >
> > > deb [amd64] http://dl.google.com/linux/chrome/deb/
> > >
> > > This warning should go away.
> > >
> > > Reco
> >
> > Reco, your suggestion didn't work. When I do an update I get
> >
> > > E: Malformed line 14 in source list /etc/apt/sources.list ([amd64]
> > > is not an assignment)
> >
> > I did not have the dl.google.com line to start with. When I removed
> > the amd, and the line still malformed. When I comment the line
> > altogether, I get failed to fetch because there no
> > 'main/binary-i386/Pakages in release file. Why does it look for
> > dl.google.com? The line is not in sources.list.
> >
> > Haines
>
> Progress, but not there yet. In sources.list I have the line:
>
>   deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
>
> When I do # aptitude update, it starts with a warning:
>
>  W: Duplicate sources.list entry
>  http://dl.google.com/linus/chrome/deb stable/main amd64 Packages
>  (/var/lib/apt/lists/dl.google.com_linux_chrome_deb_dists_stable_ \
>  main_binary-amd64_packages)
>
>  W: You may want to update the packages lists to correct these
>  missing files
>
> then there are hits and gets and then 100% [working]. However, this
> is followed by a warning 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)
>
>  E: Some index files failed to download. They have been ignored, or
>  old ones used instead
>
>  E: Couldn't rebuild package cache.
>
> This didn't stop me from installing the flashplugin-nonfree, but with
> aptitude update I still get more or less the same warnings and errors.
>
> Haines

It sounds as though your Jessie is being identified as Wheezy.  You get that 
warning with Wheezy, even if it is 64bit Wheezy with 64bit Google-Chrome. 
Presumably because Google hasn't written a string of different error messages 
for the various different things it has just stopped supporting.

Why Jessie is being identified as Wheezy is another question.  Is there any 
reason why you might get identified as Ubuntu 12.04?  Another of the things 
that has just dropped off Google's cliff.

Lisi

Re: binary-i386 packages missing in Release file

[Haines Brown]

On Sun, Mar 06, 2016 at 08:43:56PM -0300, Martinx - ジェームズ wrote:
> Correct syntax is:
> 
> --
> deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
> --
> 
> On 6 March 2016 at 20:10, Haines Brown  wrote:
> 
> On Sun, Mar 06, 2016 at 10:47:26PM +0300, Reco wrote:
> >       Hi.
> >
> > On Sun, 6 Mar 2016 14:34:25 -0500
> > Haines Brown  wrote:
> >
> > > I have jessie installed on an AMD64 machine, which lacks any desktop
> > > environment.
> > >
> > > I downloaded google-chrome AMD64 deb from the Chrome website and
> > > installed by running dpkg -i on it. It works OK. But now I want to add
> > > flashplugin-nonfree for it or, if that fails to use it for my
> > > iceweasel. In order to install flashplugin-nonfree I added contrib to
> > > the sources.list.
> > >
> > > When I do aptitude update, the contrib it hit, but the update fails
> > > because:
> > >
> > > > W: Failed to fetch
> > > > http://dl.google.com/linux/chrome/deb/dists/stable/Release: Unable 
> to
> > > > find expected entry 'main/binary-i386/Packages' in file
> >
> > 1) Locate the line like this in a file inside /etc/apt/sources.list.d:
> >
> > deb http://dl.google.com/linux/chrome/deb/
> >
> > 2) Change it to:
> >
> > deb [amd64] http://dl.google.com/linux/chrome/deb/
> >
> > This warning should go away.
> >
> > Reco
> 
> Reco, your suggestion didn't work. When I do an update I get
> 
> > E: Malformed line 14 in source list /etc/apt/sources.list ([amd64] is
> > not an assignment)
> 
> I did not have the dl.google.com line to start with. When I removed the
> amd, and the line still malformed. When I comment the line altogether,
> I get failed to fetch because there no 'main/binary-i386/Pakages in
> release file. Why does it look for dl.google.com? The line is not in
> sources.list.
>
> Haines

Progress, but not there yet. In sources.list I have the line:

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

When I do # aptitude update, it starts with a warning:

 W: Duplicate sources.list entry
 http://dl.google.com/linus/chrome/deb stable/main amd64 Packages
 (/var/lib/apt/lists/dl.google.com_linux_chrome_deb_dists_stable_ \
 main_binary-amd64_packages)

 W: You may want to update the packages lists to correct these
 missing files

then there are hits and gets and then 100% [working]. However, this
is followed by a warning 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)

 E: Some index files failed to download. They have been ignored, or
 old ones used instead

 E: Couldn't rebuild package cache.

This didn't stop me from installing the flashplugin-nonfree, but with
aptitude update I still get more or less the same warnings and errors.

Haines

Re: binary-i386 packages missing in Release file

[Martinx - ジェームズ]

Correct syntax is:

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

On 6 March 2016 at 20:10, Haines Brown  wrote:

> On Sun, Mar 06, 2016 at 10:47:26PM +0300, Reco wrote:
> >   Hi.
> >
> > On Sun, 6 Mar 2016 14:34:25 -0500
> > Haines Brown  wrote:
> >
> > > I have jessie installed on an AMD64 machine, which lacks any desktop
> > > environment.
> > >
> > > I downloaded google-chrome AMD64 deb from the Chrome website and
> > > installed by running dpkg -i on it. It works OK. But now I want to add
> > > flashplugin-nonfree for it or, if that fails to use it for my
> > > iceweasel. In order to install flashplugin-nonfree I added contrib to
> > > the sources.list.
> > >
> > > When I do aptitude update, the contrib it hit, but the update fails
> > > because:
> > >
> > > > W: Failed to fetch
> > > > http://dl.google.com/linux/chrome/deb/dists/stable/Release: Unable
> to
> > > > find expected entry 'main/binary-i386/Packages' in file
> >
> > 1) Locate the line like this in a file inside /etc/apt/sources.list.d:
> >
> > deb http://dl.google.com/linux/chrome/deb/
> >
> > 2) Change it to:
> >
> > deb [amd64] http://dl.google.com/linux/chrome/deb/
> >
> > This warning should go away.
> >
> > Reco
>
> Reco, your suggestion didn't work. When I do an update I get
>
> > E: Malformed line 14 in source list /etc/apt/sources.list ([amd64] is
> > not an assignment)
>
> I did not have the dl.google.com line to start with. When I removed the
> amd, and the line still malformed. When I comment the line altogether,
> I get failed to fetch because there no 'main/binary-i386/Pakages in
> release file. Why does it look for dl.google.com? The line is not in
> sources.list.
>
> Haines
>
>

Re: binary-i386 packages missing in Release file

[Haines Brown]

On Sun, Mar 06, 2016 at 10:47:26PM +0300, Reco wrote:
>   Hi.
> 
> On Sun, 6 Mar 2016 14:34:25 -0500
> Haines Brown  wrote:
> 
> > I have jessie installed on an AMD64 machine, which lacks any desktop
> > environment.
> > 
> > I downloaded google-chrome AMD64 deb from the Chrome website and
> > installed by running dpkg -i on it. It works OK. But now I want to add
> > flashplugin-nonfree for it or, if that fails to use it for my
> > iceweasel. In order to install flashplugin-nonfree I added contrib to
> > the sources.list.
> > 
> > When I do aptitude update, the contrib it hit, but the update fails
> > because:
> > 
> > > W: Failed to fetch
> > > http://dl.google.com/linux/chrome/deb/dists/stable/Release: Unable to
> > > find expected entry 'main/binary-i386/Packages' in file
> 
> 1) Locate the line like this in a file inside /etc/apt/sources.list.d:
> 
> deb http://dl.google.com/linux/chrome/deb/
> 
> 2) Change it to:
> 
> deb [amd64] http://dl.google.com/linux/chrome/deb/
> 
> This warning should go away.
> 
> Reco

Reco, your suggestion didn't work. When I do an update I get

> E: Malformed line 14 in source list /etc/apt/sources.list ([amd64] is
> not an assignment)

I did not have the dl.google.com line to start with. When I removed the
amd, and the line still malformed. When I comment the line altogether,
I get failed to fetch because there no 'main/binary-i386/Pakages in
release file. Why does it look for dl.google.com? The line is not in
sources.list.

Haines

Re: binary-i386 packages missing in Release file

[Sven Hartge]

Reco  wrote:

> 1) Locate the line like this in a file inside /etc/apt/sources.list.d:

> deb http://dl.google.com/linux/chrome/deb/

> 2) Change it to:

> deb [amd64] http://dl.google.com/linux/chrome/deb/

> This warning should go away.

This will only be a temporary fix as the google-chrome package installs
a cron-job to verfiy the content of the source.list file and replace it
with a pristine copy if it has been changed.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: binary-i386 packages missing in Release file

[Reco]

Hi.

On Sun, 6 Mar 2016 14:34:25 -0500
Haines Brown  wrote:

> I have jessie installed on an AMD64 machine, which lacks any desktop
> environment.
> 
> I downloaded google-chrome AMD64 deb from the Chrome website and
> installed by running dpkg -i on it. It works OK. But now I want to add
> flashplugin-nonfree for it or, if that fails to use it for my
> iceweasel. In order to install flashplugin-nonfree I added contrib to
> the sources.list.
> 
> When I do aptitude update, the contrib it hit, but the update fails
> because:
> 
> > W: Failed to fetch
> > http://dl.google.com/linux/chrome/deb/dists/stable/Release: Unable to
> > find expected entry 'main/binary-i386/Packages' in file

1) Locate the line like this in a file inside /etc/apt/sources.list.d:

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

2) Change it to:

deb [amd64] http://dl.google.com/linux/chrome/deb/

This warning should go away.

Reco

Re: binary-i386 packages missing in Release file

[Sven Hartge]

Haines Brown  wrote:

> I have jessie installed on an AMD64 machine, which lacks any desktop
> environment.

> I downloaded google-chrome AMD64 deb from the Chrome website and
> installed by running dpkg -i on it. It works OK. But now I want to add
> flashplugin-nonfree for it or, if that fails to use it for my
> iceweasel. In order to install flashplugin-nonfree I added contrib to
> the sources.list.

> When I do aptitude update, the contrib it hit, but the update fails
> because:

>> W: Failed to fetch 
>> http://dl.google.com/linux/chrome/deb/dists/stable/Release: Unable to find 
>> expected entry 'main/binary-i386/Packages' in file

Google stopped supporting Chrome on 32bit Linux. There is no more Google
Chrome for i386.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.