Re: sources.list directory specification
On 02/09/11 03:06, Tom H wrote:
On Thu, Sep 1, 2011 at 11:13 AM,<email@example.com> wrote:
I am trying to compose a sources.list file for each of three machines;
one is for Lenny (oldstable), one is for Squeeze (stable), and one is
for Wheezy (testing).
According to "Index of /pub/debian/dists" at
for Squeeze there are three directories, namely:
� �=> squeeze
� �=> squeeze-updates
� �=> squeeze-proposed-updates
Likewise, for Lenny there are two directories, namely:
� �=> lenny
� �=> lenny-proposed-updates
And for Wheezy, there are two directories, namely:
� �=> wheezy
� �=> wheezy-proposed-updates
However, the Debian Sources List Generator
(http://debgen.simplylinux.ch/) and numerous sources.list examples
posted on the web by various individuals use the form:
� �=> lenny/updates
� �=> squeeze/updates
� �=> wheezy/updates
� �=> lenny-updates
� �=> squeeze-updates
� �=> wheezy-updates
Which form is correct? is it permissible to use either form? �may the
forms be mixed within a single sources.list file?
Yes - though you might consider reading up on pinning.
deb http://http.us.debian.org/debian/ lenny main contrib non-free
deb http://volatile.debian.org/debian-volatile lenny/volatile main
deb http://security.debian.org/ lenny/updates main contrib non-free
# deb http://http.us.debian.org/debian/ lenny-proposed-updates main
deb http://http.us.debian.org/debian/ squeeze main contrib non-free
deb http://http.us.debian.org/debian/ squeeze-updates main contrib non-free
deb http://security.debian.org/ squeeze/updates main contrib non-free
# deb http://http.us.debian.org/debian/ squeeze-proposed-updates main
"<release>/updates" is meant for security updates.
"<release>-updates" is a Squeeze/Wheezy replacement of Lenny's "lenny/volatile".
"<release>-proposed-updates" is meant for testing packages before
I'd echo Tom's suggestions.
NOTE: http://debgen.simplylinux.ch/ doesn't appear to be an official
Debian site, strangely it's located in China, registered in Switzerland,
by a German (!)
I'd be cautious about enabling backports, proposed, and, especially,
multimedia - except on a case-by-case basis (enable when needed, install
only what cannot be got from the standard repo, disable when done).
"I'm just so sick of airports, sitting on planes on runways and the
planes won't take off.
Every time I read about a hijacking on the news I just think to myself
- just do it - let's see how far you get, I paid and didn't get off the
I've thought about that too - dreamed of it - putting a gun to the
pilot's head. That would feel so good.
"this is a hijacking"
"where do you want to go - Cuba?"
"No, I want to go where this plane was supposed to be five hours ago"
That's right, I'm hijacking this plane to it's scheduled destination."
— Bill Hicks