more britney foo

git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@3945 313b444b-1b9f-4f58-a734-7bb04f332e8d

diff --git a/debian/changelog b/debian/changelog
index 495723177fa4eacdb6521c6b8b29e39204134e9a..ee29fa70b741e35ae03ef8e379b9112cda2c8dd8 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -2,7 +2,7 @@ developers-reference (3.3.8) unstable; urgency=low
 
   * mia-history is replaced by mia-query. Thanks, Christoph Berg.
     Closes: #350792
-  * fix missing quite. Thanks, Franks Küster. Closes: #365994
+  * fix missing quite. Thanks, Frank Küster. Closes: #365994
   * use gnugp instead of gpg. Thanks, Justin Pryzby, Jon Dowland.
     Closes: #376411
   * better destinction between maintainer and developer. Thanks for
@@ -11,6 +11,10 @@ developers-reference (3.3.8) unstable; urgency=low
     Closes: #382721
   * Bugs are now always closed thanks to version tracking.
     Closes: #339552, #353447
+  * Clarify what "a conflicts b" means in testing migration. 
+    Closes: #361311
+  * Packages in testing disappear if they're removed from unstable.
+    Thanks, Frank Küster, Al Stone. Closes: #365993
 
  -- Andreas Barth <aba@not.so.argh.org>  Sat, 11 Nov 2006 10:55:44 -0700
 

diff --git a/developers-reference.sgml b/developers-reference.sgml
index 678e02b4c2e2a8cbf3742822326108463ed5ae4c..b44d8da4efb4437df6d2dc7291fe77e7ba72518a 100644 (file)
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -7,7 +7,7 @@
   <!ENTITY % dynamicdata  SYSTEM "dynamic.ent" > %dynamicdata;
 
   <!-- CVS revision of this document -->
-  <!ENTITY cvs-rev "$Revision: 1.298 $">
+  <!ENTITY cvs-rev "$Revision: 1.299 $">
 
   <!-- if you are translating this document, please notate the CVS
        revision of the original developer's reference in cvs-en-rev -->
@@ -2527,6 +2527,12 @@ are not removed from <em>testing</em> directly. Rather, they will be
 removed automatically after the package has been removed from
 <em>unstable</em> and no package in <em>testing</em> depends on it.
        <p>
+If you are simply restructuring a source package so that it no longer
+produces one or more binary packages, there is no need to explicitly ask
+for the packages that are no longer created to be removed.  Such packages
+will be removed when the new package structure has been uploaded into 
+<em>unstable</em> and when no package in <em>testing</em> depends on it.
+        <p>
 You also have to detail the reasons justifying that request. This is to
 avoid unwanted removals and to keep a trace of why a package has been
 removed. For example, you can provide the name of the package that
@@ -3419,11 +3425,16 @@ if you maintain glibc or so.)
        <p>
 Sometimes, a package is removed to allow another package in: This happens
 only to allow <em>another</em> package to go in if it's ready in every other
-sense. Suppose e.g. that <em>a</em> conflicts with the new version of
+sense. Suppose e.g. that <em>a</em> cannot be installed with the new version of
 <em>b</em>; then <em>a</em> may be removed to allow <em>b</em> in.
        <p>
 Of course, there is another reason to remove a package from testing: It's
 just too buggy (and having a single RC-bug is enough to be in this state).
+        <p>
+Furthermore, if a package has been removed from unstable,
+and no package in testing depends on it any more,
+then it will automatically be removed.
+
 
        <sect2 id="circular">
        <heading>circular dependencies</heading>