Package: debian-reference-en Severity: normal Tags: patch
-- System Information: Debian Release: 4.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-1-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) I came across couple things needing an update when I was translating the system.sgml to Finnish. I have attached a complete diff to this message. I can also commit these myself if the changes are accepted. The first change is to a sentence which has been copied from the description of stable (2.1.3) to the description of testing (2.1.4) and refers to things that are not mentioned in the description of testing. I suggest that we make the sentence more simple (and identical to one in the description of unstable). -Now, in addition to the above locations, new physical packages are +New physical packages are located under the <file>pool</file> directory (<ref id="pools">). Second change is in the description of frozen (2.1.5). It mentions "recent Woody release" and explains how it is different from what has been described elsewhere in the paragraph. I suggest we remove the whole sentence. This has also been reported in bug #394479. -(The recent Woody release process did not create a symbolic link -<file>frozen/</file>, so <tt>frozen</tt> was not a distribution but just a -development stage of the <tt>testing</tt> distribution.) Third is in the chapter 2.1.7 "Debian distribution codenames". At the end of the first paragraph there is a long sentence inside parenthesis, but it is included to the sentence just before it. I suggest that the earlier sentence is ended with a period and the one in parentheses is started with a capital. If I understand the meaning of the last sentence correctly, I would also suggest that it would be changed from "If a real directory like <file>unstable</file> suddenly changed its name to <file>stable/</file>, a lot of stuff would have to be needlessly downloaded again" to "If <file>unstable</file> would be a real directory and it's name would suddenly change to <file>stable/</file>, a lot of stuff would have to be needlessly downloaded again." <file>&stablecodenamedir;/</file> and <file>&testingcodenamedir;/</file>, are just "codenames". When a &debian; distribution is in the development stage, it has no version number, but a codename instead. The purpose of these codenames is to make the mirroring of -the &debian; distributions easier (if a real directory like <file>unstable</file> +the &debian; distributions easier. (If a real directory like <file>unstable</file> suddenly changed its name to <file>stable/</file>, a lot of stuff would have to be -needlessly downloaded again). +needlessly downloaded again.) The system-section also says in the chapter 2.1.10 "The pool directory" that "Also, at the time of writing, older distributions have not been converted to use pools, so you'll see paths containing distribution names such as potato or woody in the "Directory" header field." Is this still true? It seems to me that these have also been converted to use pool directory. <p>The <file>dists</file> directories are still used for the index files used by -programs like <prgn>apt</prgn>. Also, at the time of writing, older -distributions have not been converted to use pools, so you'll see paths -containing distribution names such as <tt>potato</tt> or <tt>woody</tt> in the -"Directory" header field. +programs like <prgn>apt</prgn>. Also I suggest a change of phrasing in the chapter 2.1.11. Currently in second paragraph it says: "For those architectures not yet released, the first time they were released there was a link from the current stable/ to sid/, and from then on they were created inside the unstable/ tree as usual." I would suggest this is changed to something like: "When an architecture was released the first time there was a link from the current stable/ to sid/, and from then on they were created inside the unstable/ tree as usual." In section 2.1.14 "Architecture sections" the text says: "Please note that the actual binary packages for testing and unstable no longer reside in these directories, but in the top-level pool directory." Isn't this true also stable nowadays? So we could just say: "Please note that the actual binary packages no longer reside in these directories, but in the top-level pool directory." --- system.sgml 2005-01-10 02:20:26.000000000 +0200 +++ system.sgml.mod 2006-12-09 00:20:05.000000000 +0200 @@ -158,7 +158,7 @@ <p>Package entries for the <tt>testing</tt> distribution, &testingdebian;, are recorded into the <file>testing</file> (symlink to <file>&testingcodenamedir;/</file>) directory after they have undergone some degree of testing in <tt>unstable</tt>. -Now, in addition to the above locations, new physical packages are +New physical packages are located under the <file>pool</file> directory (<ref id="pools">). There are also <file>main</file>, <file>contrib</file>, and <file>non-free</file> subdirectories in @@ -229,9 +229,6 @@ Also, a new testing tree is created in the <file>dists</file> directory, assigned a new codename. The frozen distribution passes through a few months of testing, with intermittent updates and deep freezes called "test cycles". -(The recent Woody release process did not create a symbolic link -<file>frozen/</file>, so <tt>frozen</tt> was not a distribution but just a -development stage of the <tt>testing</tt> distribution.) <p>We keep a record of bugs in the frozen distribution that can delay a package from being released or bugs that can hold back the whole release. @@ -245,9 +242,9 @@ <file>&stablecodenamedir;/</file> and <file>&testingcodenamedir;/</file>, are just "codenames". When a &debian; distribution is in the development stage, it has no version number, but a codename instead. The purpose of these codenames is to make the mirroring of -the &debian; distributions easier (if a real directory like <file>unstable</file> -suddenly changed its name to <file>stable/</file>, a lot of stuff would have to be -needlessly downloaded again). +the &debian; distributions easier. (If <file>unstable</file> would be a +real directory and it's name would suddenly change to <file>stable/</file>, +a lot of stuff would have to be needlessly downloaded again.) <p>Currently, <file>stable/</file> is a symbolic link to <file>&stablecodenamedir;/</file>, and <file>testing/</file> is a symbolic link to @@ -333,10 +330,7 @@ <file>pool/main/libp/libpaper/</file>. <p>The <file>dists</file> directories are still used for the index files used by -programs like <prgn>apt</prgn>. Also, at the time of writing, older -distributions have not been converted to use pools, so you'll see paths -containing distribution names such as <tt>potato</tt> or <tt>woody</tt> in the -"Directory" header field. +programs like <prgn>apt</prgn>. <p>Normally, you won't have to worry about any of this, as new <prgn>apt</prgn> and probably older <prgn>dpkg-ftp</prgn> will handle it @@ -356,9 +350,9 @@ <p>The archive administrators worked around this problem for several years by placing binaries for unreleased architectures in a special directory called -<file>sid</file>. For those architectures not yet released, the first time they -were released there was a link from the current <file>stable/</file> to -<file>sid/</file>, and from then on they were created inside the <file>unstable/</file> +<file>sid</file>. When an architecture was released the first time there +was a link from the current <file>stable/</file> to <file>sid/</file>, +and from then on they were created inside the <file>unstable/</file> tree as usual. This layout was somewhat confusing to users. <p>With the advent of package pools (see <ref id="pools">) during the @@ -413,8 +407,8 @@ <!-- Yes I simplified this --> </list> -<p>Please note that the actual binary packages for <tt>testing</tt> and -<tt>unstable</tt> no longer reside in these directories, but in the top-level +<p>Please note that the actual binary packages +no longer reside in these directories, but in the top-level <file>pool</file> directory. The index files (<file>Packages</file> and <file>Packages.gz</file>) have been kept, though, for backwards compatibility. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
