Re: Bug#447774: Please mention proposed-updates
tags 447774 +patch
this patch may need some tweaking, I'm not so fluent in docbook.
I'm not sure about:
* the section id names (same in both files I touched)
* cross-referencing between files
--- upgrading.dbk (revision 5506)
+++ upgrading.dbk (working copy)
@@ -326,6 +326,16 @@
+If you have listed the <literal>proposed-updates</literal> section
+in your <filename>/etc/apt/sources.list</filename> file, you should remove
+it from that file before attempting to upgrade your system.
+This is a precaution to reduce the likelyhood of conflicts.
<title>Unofficial sources and backports</title>
--- whats-new.dbk (revision 5506)
+++ whats-new.dbk (working copy)
@@ -321,6 +321,31 @@
+<title>The proposed-updates section</title>
+Some users of &debian; &releasename; may wish to help test updates
+to packages before they are formally added to an upcoming point release.
+One can do this by adding the
+section to their <filename>sources.list</filename>:
+deb &url-debian-mirror-eg;/debian &releasename;-proposed-updates main contrib
+deb-src &url-debian-mirror-eg;/debian &releasename;-proposed-updates main contrib
+The next time you run <command>aptitude update</command>, the system
+will become aware of the packages in the
+<literal>proposed-updates</literal> section and will consider them
+when looking for packages to upgrade.
+This is not strictly a new feature of Debian, but one that has not
+been given much exposure.
<section id="backports.org" condition="fixme">
<para >TODO: write about probability backports.org becoming official</para>