LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Debian (http://www.linuxquestions.org/questions/debian-26/)
-   -   apt-get update errors since Debian released ( bad /etc/apt/sources.list ?) (http://www.linuxquestions.org/questions/debian-26/apt-get-update-errors-since-debian-released-bad-etc-apt-sources-list-331712/)

forgox 06-08-2005 09:44 PM

apt-get update errors since Debian released ( bad /etc/apt/sources.list ?)
 
Hi,
Since Debian testing as been released, it seems that there is some errors when trying to do an apt-get update (see errors below). The source.list file below has been working for more than a year and coincidently after Debian testing got released, "apt-get update" started to fails. Maybe they moved packages around and now the testing branch isn't ready yet???

The system is a Debian stable (i.e. Woody) on which the sources.list has change to be pointing to the testing version (see below) thus making the system a Debian testing system. Again, this configuration has been working for long time until now.

thanks for your help


$ cat /etc/apt/sources.list
#deb file:///cdrom/ sarge main
deb http://http.us.debian.org/debian testing main non-free contrib
deb http://non-us.debian.org/debian-non-US testing/non-US main non-free contrib
deb http://security.debian.org testing/updates main non-free contrib


$ apt-get update
Get:1 http://http.us.debian.org testing/main Packages [3413kB]
Err http://security.debian.org testing/updates/main Packages
404 Not Found
Ign http://security.debian.org testing/updates/main Release
Err http://security.debian.org testing/updates/non-free Packages
404 Not Found
Ign http://security.debian.org testing/updates/non-free Release
Err http://security.debian.org testing/updates/contrib Packages
404 Not Found
Ign http://security.debian.org testing/updates/contrib Release
Err http://non-us.debian.org testing/non-US/main Packages
404 Not Found
Ign http://non-us.debian.org testing/non-US/main Release
Err http://non-us.debian.org testing/non-US/non-free Packages
404 Not Found
Ign http://non-us.debian.org testing/non-US/non-free Release
Err http://non-us.debian.org testing/non-US/contrib Packages
404 Not Found
Ign http://non-us.debian.org testing/non-US/contrib Release
Get:2 http://http.us.debian.org testing/main Release [81B]
Get:3 http://http.us.debian.org testing/non-free Packages [58.9kB]
Get:4 http://http.us.debian.org testing/non-free Release [85B]
Get:5 http://http.us.debian.org testing/contrib Packages [57.1kB]
Get:6 http://http.us.debian.org testing/contrib Release [84B]
Fetched 3529kB in 6s (521kB/s)
Failed to fetch http://non-us.debian.org/debian-non-...86/Packages.gz 404 Not Found
Failed to fetch http://non-us.debian.org/debian-non-...86/Packages.gz 404 Not Found
Failed to fetch http://non-us.debian.org/debian-non-...86/Packages.gz 404 Not Found
Failed to fetch http://security.debian.org/dists/tes...86/Packages.gz 404 Not Found
Failed to fetch http://security.debian.org/dists/tes...86/Packages.gz 404 Not Found
Failed to fetch http://security.debian.org/dists/tes...86/Packages.gz 404 Not Found
Reading Package Lists... Done
E: Some index files failed to download, they have been ignored, or old ones used instead.

juanbobo 06-08-2005 10:06 PM

You should find the answer here...

http://osnews.com/comment.php?news_id=10785

rickh 06-09-2005 01:16 AM

Quote:

deb http://security.debian.org testing/updates main non-free contrib
I think everyone is having this problem. I changed the line quoted to:
deb http://security.debian.org stable/updates main non-free contrib
in /etc/apt/sources.list, and that's working fine. Guess I'll just change it back to 'testing' every so often until they get it working.

Dead Parrot 06-09-2005 01:54 AM

Quote:

Guess I'll just change it back to 'testing' every so often until they get it working.
Or you could add this page to your bookmarks and check every now and then if "testing" will appear among the available options: http://security.debian.org/dists/

I'm also curious to see how Etch/testing will be receiving security updates -- but so far there has been very little info about this available. Apparently the "testing security team" already exists and their plans are that:

"After sarge is released and once the autobuilder infrastructure is in place, we hope to begin issuing security advisories for holes in testing, and providing fixed packages immediatly on security.debian.org or a similar site." http://secure-testing.alioth.debian.org/

However, they merely say that they "hope to" start these actions after Sarge has been released, so we will have to wait to see if these hopes will actually turn into concrete actions.

jsmarshall85 06-09-2005 03:09 PM

you might want to change testing to sarge. sarge is no longer the testing build but the stable build, there will be a new name for testing (as far as i know). try changing it to sarge.

goozlq 06-09-2005 04:02 PM

If you used to be using Sarge search and replace all testing into sarge in /etc/apt/sources.list

Testing is after the release of Debian 3.1 (Sarge) the stable version.

Remeber to run lilo before you reboor after a (apt-get update, apt-get upgrade) apt-get dist-upgrade! Otherwise you wil have the same problem as I had: lilo will not boot....

stimpsonjcat 06-09-2005 04:19 PM

you can remove the non-us lines from your sources.list
the non-us archives are obsolete
stimpy

craigevil 06-09-2005 04:35 PM

"non-US obsoleted
For the sarge release, packages that were formerly in the non-US part of the archive have been moved into the regular archive. If you have any lines referring to "non-us" in your /etc/apt/sources.list, you should remove them." http://www.debian.org/releases/sarge....html#s-non-us


I would guess that applies to testing and unstable as well since it says "any lines".

I know by removing the non-us and testing security updates lines, apt-get update works with no errors nd the number of packages is about the same.

jsmarshall85 06-10-2005 11:00 PM

Quote:

Originally posted by goozlq
Remeber to run lilo before you reboor after a (apt-get update, apt-get upgrade) apt-get dist-upgrade! Otherwise you wil have the same problem as I had: lilo will not boot....
well thats only if you have lilo installed. the debian-installer by defalut installs grub

goozlq 06-13-2005 11:17 AM

@ jsmarshall85:

That's correct, but my 1.5 years old install of Debian Sarge uses Lilo and I didn't want to change that.

Maybe Grub users do not need to run Grub after the dist-upgrade, but I needed to run Lilo in order to get the system up again...

jsmarshall85 06-13-2005 01:28 PM

gotcha


All times are GMT -5. The time now is 01:27 PM.