Differences between version 17 and revision by previous author of FlavoursOfDebian.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 17 | Last edited on Friday, June 10, 2005 1:43:40 pm | by CraigBox | Revert |
| Older page: | version 15 | Last edited on Wednesday, May 18, 2005 10:04:20 am | by RichardAmes | Revert |
@@ -5,22 +5,23 @@
; testing : The testing distribution contains packages that haven't been accepted into a stable release yet, but they are in the queue for it. The main advantage of using this distribution is that it has more recent versions of software, and the main disadvantage is that it's not completely tested and has no official support from Debian security team.
; unstable: The unstable distribution is where active development of Debian occurs. Generally, this distribution is run by developers and those who like to live on the edge. It's where you have to go if you want things as soon as they come out - packages don't move to testing as quickly as you might like them to.
-There is a fourth
criterion
+There are other
criterion
; experimental : So unstable that unstable doesn't even want them. You have to get these packages from other apt repositories. They are labelled experiemental so you don't install them unless you __really really__ want to, and tell apt that with ''apt-get -t experimental package''.
-The current (at time of writing) stable distribution of Debian is 3.0r5, codenamed woody. It was released on April 16th, 2005. Check http
://www.debian.org/releases/ to ensure it is still current
, and if not
, come back and edit the wiki so it is
. The current testing distribution is sarge. Eventually, sarge will become stable (a FeatureFreeze will occur), woody will become an unsupported older distribution, and a new name will
be picked for the new testing tree
.
+; volatile
: a "backports-esque" repository that updates packages that are made useless by their outdatedness
, for example virus defintions
and [GAIM]
, which breaks when protocols change
. Designed to
be able to used as safely as security
.
-On a debian machine, you can find out the version number
of the installed
-by looking in
/etc
/debian_version
.
+The current (at time
of writing) stable
distribution of Debian is 3.1, codenamed sarge. It was released on June 6th, 2005. Check http:
//www.
debian.org/releases/ to ensure it is still current, and if not, come back and edit the wiki so it is. The current testing distribution is etch. Eventually, etch will become stable (a FeatureFreeze will occur), sarge will become an unsupported older distribution, and the testing tree will be reborn with a new name
.
-Previous versions of stable have been named "potato
" (debian version 2
.2, 2000), "slink" (v 2.1, 1999) "hamm" (v2., 1998), "bo" (v1.3, 1997), "rex" (v1.2, 1996), and "buzz" (v1.1, 1996).
+On a debian machine, you can find out the version number of the installed distribution by looking in /etc/debian_version.
+
+
Previous versions of stable have been named "woody
",
(debian version 3., 2002), "potato" (v2
.2, 2000), "slink" (v 2.1, 1999) "hamm" (v2., 1998), "bo" (v1.3, 1997), "rex" (v1.2, 1996), and "buzz" (v1.1, 1996).
The unstable distribution is called sid, and it doesn't get renamed.
-The code names come from the movie Toy Story, because ex-Debian project leader BrucePerens used to work for Pixar. (He's now
[HP]'s [Linux] evangelist.- NB. This is no longer true. He has recently been
fired by HP for "microsoft-baiting".)
+The code names come from the movie Toy Story, because ex-Debian project leader BrucePerens used to work for Pixar. (He went on to become
[HP]'s [Linux] evangelist, but was allegedly
fired by HP for "microsoft-baiting".)
Packages are installed into the `testing' directory after they have undergone some degree of testing in unstable. They must be in sync on all architectures where they have been built and must not have dependencies that make them uninstallable; they also have to have fewer release-critical bugs than the versions currently in testing. This way, they ensure (hope) that testing is always close to being a release candidate.
! Using Packages from different releases
@@ -28,16 +29,16 @@
# Add APT::Default-Release "stable"; to apt.conf(5)
# Make sure you have sources for unstable/testing specified in sources.list(5)
# Install packages with:
-#* apt-get install [
[packagename]=[
[packageversion]
-#* apt-get install -t unstable [
[packagename]
+#* apt-get install ~
[packagename]=~
[packageversion]
+#* apt-get install -t unstable ~
[packagename]
Some notes on the above.
-* When specifying your default release it appears that you can only use "Stable"/"Testing"/"Unstable" don't try and use Woody/
Sarge etc it won't work
-* You can find out package versions at packages.debian.org
+* When specifying your default release it appears that you can only use "Stable"/"Testing"/"Unstable" don't try and use Sarge/Etch
etc it won't work
+* You can find out package versions at packages.debian.org - try also =apt-cache policy=
-And this prompts a question unanswered everywhere I have looked: When sarge
becomes "stable" how will I prevent my regular and automated executing of "apt-get dist-upgrade" updating all my packages to sarge
? How does one configure apt to stay with woody
given that default-release "woody
" does not work? It seesm
the way is this: Do not set default-release. In sources.list do not mention stable or testing but woody and
sarge instead. In preferences pin 500 > woody
> stable > sarge
> testing > 100. Then when packages in sarge
becomes marked stable packages in woody
, also still stable, presumably will still be preferred. Does that work?
+And this prompts a question unanswered everywhere I have looked: When etch
becomes "stable" how will I prevent my regular and automated executing of "apt-get dist-upgrade" updating all my packages to etch
? How does one configure apt to stay with sarge
given that default-release "sarge
" does not work? It seems
the way is this: Do not set default-release. In sources.list do not mention stable or testing but sarge and etch
instead. In preferences pin 500 > sarge
> stable > etch
> testing > 100. Then when packages in etch
becomes marked stable packages in sarge
, also still stable, presumably will still be preferred. Does that work?
----
CategoryDebian
