Linux Lite Forums

Software - Support => Installing Software => Topic started by: torreydale on March 02, 2016, 08:33:28 PM

Title: Failed to Download Repository Information
Post by: torreydale on March 02, 2016, 08:33:28 PM
Getting this popup when trying to install updates. 
(http://i.imgur.com/89AR7Zr.png)

When trying to change updates server, I get the following:
(http://i.imgur.com/7xM1hzH.png)

UPDATE:  Got the answer here: 
https://www.linuxliteos.com/forums/linux-lite-software-development/update-checker/msg21846/?topicseen#msg21846
Title: Re: Failed to Download Repository Information
Post by: aviceda on March 02, 2016, 08:40:02 PM
Just had the same problem, there are a couple of issues (mentioned in my previous threads and other similar posts) when I 'unchecked' the Google repo and changed the LL path in the software dialogue from Trusty to Beryl.
Have a try with that (...you might need to reference previous posts to get better detail)
Tom
Title: Re: Failed to Download Repository Information
Post by: firenice03 on March 02, 2016, 08:48:24 PM
I'd say 32-bit OS - un-check the Goggle repo

For 64-bit... Repo not updated yet (See below)

Recently google removed 32bit chrome from repo. However not updated repo data yet.

If you are on 64bit, simply edit
Code: [Select]
/etc/apt/sources.list.d/google-chrome.list
Change from:
Code: [Select]
deb http://dl.google.com/linux/chrome/deb/ stable main
To:
Code: [Select]
deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
Title: Re: Failed to Download Repository Information
Post by: Jocklad on March 03, 2016, 03:55:00 AM
That fixed the 64 bit.......Thanks Firenice03  :) :) :)
Title: Re: Failed to Download Repository Information
Post by: Coastie on March 03, 2016, 10:59:08 AM
I'd say 32-bit OS - un-check the Goggle repo

Thanks. That fixed 32 bit OS.  8)
Title: Re: Failed to Download Repository Information
Post by: Richard B on March 03, 2016, 12:27:49 PM
I see this is marked as solved, but I don't think it is. If some of the repositories listed are wrong then the list needs correcting. Just "unticking" them so they don't get checked does not seem the right solution - and how is a noob to know what to do? I use and promote Linux Lite, but problems like this when following the advice given (update after an install) will give it a bad name.
Title: Re: Failed to Download Repository Information
Post by: Featherman on March 03, 2016, 04:36:15 PM
hello,
I am experiencing exactly the same issue.The system updates run fine until google chrome is installed then i get the pop ups and cannot update anywhere on the system and that includes the package manager.I have had to re-install a saved image to a pre chrome state and i dare not install chrome now...bit off putting to be honest.
Title: Re: Failed to Download Repository Information
Post by: mandoran on March 03, 2016, 04:44:52 PM
I tend to agree - I have the same issue and besides not feeling completely at ease just dropping a few repositories, I am not getting any clue about which one(s) are failing.
Title: Re: Failed to Download Repository Information
Post by: nomko on March 03, 2016, 04:55:17 PM
Today an update on webupd8.org:
http://www.webupd8.org/2016/03/fix-failed-to-fetch-google-chrome_3.html
Title: Re: Failed to Download Repository Information
Post by: Featherman on March 03, 2016, 04:59:44 PM
Thats all well and good but why would the complete package manager not update at all..?.its not just chrome which needs updating.
I tried (with chrome installed) to update everywhere on the system with no joy.A complete newbie will be mystified.
Is there a proper fix on the way from the repo maintainers.?

So what happens now.?
Are linux lite users to be left up the creek without a paddle and unable
 to install the chrome browser.Surely the repo maintainers were prepared for this.?

I have tried 4-5 times today to get chrome installed and i gave up in the end.
this needs sorting asap.
Title: Re: Failed to Download Repository Information
Post by: firenice03 on March 03, 2016, 05:30:40 PM
Remember folks - Google ended Chrome support for 32-bit linux (not just LL) on 3/1..  :(
This has been mentioned previously.. Feel free to search for specific info..
*Thread* https://www.linuxliteos.com/forums/on-topic/so-what-are-we-going-to-do-about-this/msg20345/#msg20345

The Google repo's will fail for and may continue to fail for 32-bit Linux OS's as Chrome is no longer supported.
The 64-bit version can be updated but at this time requires manual intervention.

I'm not one of the Dev's but I'm sure they will update the repos and all will be as it was  8)

In the meanwhile you can uncheck the offending or if your running 64-bit you can update the source.list file as mentioned previously..



Title: Re: Failed to Download Repository Information
Post by: mzito59 on March 03, 2016, 07:40:38 PM
This worked for me:

sudo sed -i -e 's/deb http/deb [arch=amd64] http/' "/etc/apt/sources.list.d/google-chrome.list"
sudo sed -i -e 's/deb http/deb [arch=amd64] http/' "/opt/google/chrome/cron/google-chrome"

More info on WebUpd8 page:
http://www.webupd8.org/2016/03/fix-failed-to-fetch-google-chrome_3.html#more
Title: Re: Failed to Download Repository Information
Post by: Featherman on March 04, 2016, 01:33:34 PM
Im using a 64bit system and installing 64bit chrome still causes problems updating.I can understand a problem with updating chrome but the computer is not being updated because of this.I dont understand why all the other updates will not function plus the package manager will not work with chrome installed.
Title: Re: Failed to Download Repository Information
Post by: Wirezfree on March 04, 2016, 02:03:20 PM
The repo information needs updating per the many posts on various threads.
If you run the 2 commands in a terminal it will be fine.
Code: [Select]
sudo sed -i -e 's/deb http/deb [arch=amd64] http/' "/etc/apt/sources.list.d/google-chrome.list"
sudo sed -i -e 's/deb http/deb [arch=amd64] http/' "/opt/google/chrome/cron/google-chrome"

The 32bit Chrome issue was well publicised
It appears however that Google changed the 64bit repo for some reason..??
I don't see this as a LL issue, but poor information from Google.