Differences between version 19 and predecessor to the previous major change of FlavoursOfDebian.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 19 | Last edited on Thursday, July 28, 2005 7:06:01 pm | by MattBrown | Revert |
| Older page: | version 18 | Last edited on Sunday, June 12, 2005 12:15:52 am | by BartVanDeventer | Revert |
@@ -35,10 +35,11 @@
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 Sarge/Etch etc it won't work
-* You can find out
package versions at packages.debian.org - try also =
apt-cache policy=
+* The definitive reference for
package versions in each flavour of debian is found
at http://
packages.debian.org
+* To see your current system policy use ''
apt-cache policy''
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
