Err http://http.debian.net jessie-backports/main


#1

I’ve been using ee on Debian 8 (Jessie) for as long as my VM Host has had it available. In the last four days I’ve completed two ee setups (one to run PIWIK and one to run WordPress). Both installations worked fine. Today, though, after running the:

ee stack install --web

…command, the installation would not complete, due to error shown in the screenshot below:

tail /var/log/ee/ee.log

…seems a little redundant in its explanation, as you can see in the screenshot below:

This error seems to be a sources.list problem but upon checking:

cat /etc/apt/sources.list

…the output doesn’t even have a backports deb or deb-src referenced in it, as you can see in the screenshot below:

Can I simply add:

deb http://httpredir.debian.org/debian jessie-backports main

…to the sources.list file and if so, why is it not in there already?


#2

I answered one of my questions:

No, I can’t simply add:

deb http://httpredir.debian.org/debian jessie-backports main

…to the sources.list file!

Doing so creates a “Duplicate Sources” issue, as you can see in the screenshot below:


#3

After 30-45 minutes of dealing with these errors/issues, after me posting (here) the errors I got and what I’ve tried and finally reverting back to the original sources.list file, it now seems to be working correctly.

Although I have no explanation to offer, as to why, I guess this issue is resolved.


#4

I’m not sure it is a “thumb rule,” but I always run apt-get update before ee update. I’m aware ee update includes internally a call to apt-get update but I’d rather think I’ve got some kind of controle over it.

Probably that solved your issue, too: after fixing your sources list you probably ran an apt-get update that magically made the error go away.


#5

Actually @janiosarmento I usually run apt-get update, out of habit. Its typically the first thing I do after sudo passwd root. However, in switching over to using NGINX and EE (on the Google Developers Console - Compute Engine), I’ve fallen out of that habit, depending instead on ee update.

To Do:

  1. Add apt-get update back to server setup workflow - DONE!

Thank you sir!


#6