<!ENTITY % commondata SYSTEM "common.ent" > %commondata;
<!-- CVS revision of this document -->
- <!ENTITY cvs-rev "$Revision: 1.238 $">
+ <!ENTITY cvs-rev "$Revision: 1.239 $">
<!-- if you are translating this document, please notate the CVS
revision of the original developer's reference in cvs-en-rev -->
<p>
Consider this example:
<p>
- <tt>
- foo | alpha | arm
+ <example>
+foo | alpha | arm
---------+-------+----
testing | 1 | -
unstable | 1 | 2
-</tt>
+</example>
<p>
The package is out of date on alpha in unstable, and will not go to
testing. And removing foo from testing would not help at all, the package
<p>
However, if ftp-master removes a package in unstable (here on arm):
<p>
- <tt>
+ <example>
foo | alpha | arm | hurd-i386
---------+-------+-----+----------
testing | 1 | 1 | -
unstable | 2 | - | 1
- </tt>
+ </example>
<p>
In this case, the package is up to date on all release architectures in
unstable (and the extra hurd-i386 doesn't matter, as it's not a release