[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: repositories/mirror problem



On Tue, Mar 28, 2006 at 01:20:14PM +0100, mailing_anthony I&I wrote:
> Greetings,
> 
> could anyone give me a hand - I have been using Debian etch for about two
> weeks and it appears that the mirror I selected during the (network install)
> installation process is down or only part working - I cannot apt-get install
> even the most basic packages which is driving me up the wall. I have
> searched online for alternative repositories/mirrors but to no avail, could
> anyone point me to a recent list of working etch repositories or a copy of
> their sources.list . here is mine below
> 
>  # deb cdrom:[Debian GNU/Linux testing _Etch_ - Official Snapshot i386
> Binary-1 (20060312)]/ etch main
> 
> # deb cdrom:[Debian GNU/Linux testing _Etch_ - Official Snapshot i386
> Binary-1 (20060312)]/ etch main
> 
> deb http://download.mirror.ac.uk/sites/ftp.debian.org/debian/ etch main
> deb-src http://download.mirror.ac.uk/sites/ftp.debian.org/debian/ etch main
> 
> deb http://security.debian.org/ etch/updates main
> deb-src http://security.debian.org/ etch/updates main
> 
> # deb ftp://ftp.nerim.net/debian-marillat/ etch main

And here's mine:


# deb cdrom:[Debian GNU/Linux 3.0 beta _Woody_ - Unofficial i386 Binary-8 (20020723)]/ unstable contrib main non-US/contrib non-US/main non-US/non-free non-free
# deb cdrom:[Debian GNU/Linux 3.0 r1 _Woody_ - Official i386 Binary-7 (20021218)]/ unstable contrib main non-US/contrib non-US/main
# deb cdrom:[Debian GNU/Linux 3.0 r1 _Woody_ - Official i386 Binary-6 (20021218)]/ unstable contrib main non-US/contrib non-US/main
# deb cdrom:[Debian GNU/Linux 3.0 r1 _Woody_ - Official i386 Binary-5 (20021218)]/ unstable contrib main non-US/contrib non-US/main
# deb cdrom:[Debian GNU/Linux 3.0 r1 _Woody_ - Official i386 Binary-4 (20021218)]/ unstable contrib main non-US/contrib non-US/main
# deb cdrom:[Debian GNU/Linux 3.0 r1 _Woody_ - Official i386 Binary-3 (20021218)]/ unstable contrib main non-US/contrib non-US/main
# deb cdrom:[Debian GNU/Linux 3.0 r1 _Woody_ - Official i386 Binary-2 (20021218)]/ unstable contrib main non-US/contrib non-US/main
# deb cdrom:[Debian GNU/Linux 3.0 r1 _Woody_ - Official i386 Binary-1 (20021218)]/ unstable contrib main non-US/contrib non-US/main


# deb ftp://ftp3.nrc.ca/debian/ woody main contrib non-free
deb ftp://ftp3.nrc.ca/debian/ sarge main contrib non-free
deb http://security.debian.org/ woody/updates main contrib non-free
#deb http://security.debian.org/ sarge/updates main contrib non-free


I've commented out the CD's I installed everything from because, having
upgraded to sarge, I no longer need them.
Note that some repositories want specific directories specified; others 
insist on being specifically ftp: or http: and even pave you specify 
different directories for the two protocols.  Others don't care.

I noticed I very explicitly set up security updates fropm woody, not 
sarge.  I wonder what I was thinking.... would that be a mistake now?
Could that be why I so raraly get any?

Moral: even running systems used as examples have bugs in them.

-- hendrik



Reply to: