/[ddp]/manuals/trunk/quick-reference/debian-reference.raw.xml
ViewVC logotype

Diff of /manuals/trunk/quick-reference/debian-reference.raw.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 7355 by osamu, Tue May 18 15:35:25 2010 UTC revision 7364 by osamu, Sat May 22 13:36:35 2010 UTC
# Line 4838  The 3rd and following arguments are the Line 4838  The 3rd and following arguments are the
4838          </itemizedlist>          </itemizedlist>
4839          <simpara>The "<literal>deb-src</literal>" lines can safely be omitted (or commented out by placing "#" at the start of the line) if it is just for <literal>aptitude</literal> which does not access source related meta data. It speeds up the updates of the archive meta data. The URL can be "<literal>http://</literal>", "<literal>ftp://</literal>", "<literal>file://</literal>", ….</simpara>          <simpara>The "<literal>deb-src</literal>" lines can safely be omitted (or commented out by placing "#" at the start of the line) if it is just for <literal>aptitude</literal> which does not access source related meta data. It speeds up the updates of the archive meta data. The URL can be "<literal>http://</literal>", "<literal>ftp://</literal>", "<literal>file://</literal>", ….</simpara>
4840          <tip>          <tip>
4841            <simpara>If "<literal>sid</literal>" is used in the above example instead of "<literal>@-@codename-stable@-@</literal>", the "<literal>deb: <ulink url="http://security.debian.org/">http://security.debian.org/</ulink> …</literal>" line for security updates in the "<literal>/etc/apt/sources.list</literal>" is not required.   This is because "<literal>sid</literal>" (<literal>unstable</literal>) is always updated whenever security issues are fixed.  There is no need to have a separate security update archive for "<literal>sid</literal>".</simpara>            <simpara>If "<literal>sid</literal>" is used in the above example instead of "<literal>@-@codename-stable@-@</literal>", the "<literal>deb: <ulink url="http://security.debian.org/">http://security.debian.org/</ulink> …</literal>" line for security updates in the "<literal>/etc/apt/sources.list</literal>" is not required.   This is because there is no security update archive for "<literal>sid</literal>" (<literal>unstable</literal>).</simpara>
4842          </tip>          </tip>
4843          <simpara>Here is the list of URL of the Debian archive sites and suite name or codename used in the configuration file.</simpara>          <simpara>Here is the list of URL of the Debian archive sites and suite name or codename used in the configuration file.</simpara>
4844          <table pgwide="0" frame="topbot" rowsep="1" colsep="1">          <table pgwide="0" frame="topbot" rowsep="1" colsep="1">
# Line 4972  The 3rd and following arguments are the Line 4972  The 3rd and following arguments are the
4972            </tgroup>            </tgroup>
4973          </table>          </table>
4974          <caution>          <caution>
4975            <simpara>Only pure <emphasis role="strong"><literal>stable</literal></emphasis> release with security updates provides the best stability. Running mostly <emphasis role="strong"><literal>stable</literal></emphasis> release mixed with some packages from <emphasis role="strong"><literal>testing</literal></emphasis> or <emphasis role="strong"><literal>unstable</literal></emphasis> release is riskier than running pure <emphasis role="strong"><literal>unstable</literal></emphasis> release.  If you really need the latest version of some programs under <emphasis role="strong"><literal>stable</literal></emphasis> release, please use packages from <ulink url="http://www.debian.org/volatile/">the debian-volatile project</ulink> and <ulink url="http://backports.org">backports.org</ulink> (see <xref linkend="_volatile_and_backports_org"/>) services.  These services must be used with extra care.</simpara>            <simpara>Only pure <emphasis role="strong"><literal>stable</literal></emphasis> release with security updates provides the best stability. Running mostly <emphasis role="strong"><literal>stable</literal></emphasis> release mixed with some packages from <emphasis role="strong"><literal>testing</literal></emphasis> or <emphasis role="strong"><literal>unstable</literal></emphasis> release is riskier than running pure <emphasis role="strong"><literal>unstable</literal></emphasis> release for library version mismatch etc.  If you really need the latest version of some programs under <emphasis role="strong"><literal>stable</literal></emphasis> release, please use packages from <ulink url="http://www.debian.org/volatile/">the debian-volatile project</ulink> and <ulink url="http://backports.org">backports.org</ulink> (see <xref linkend="_volatile_and_backports_org"/>) services.  These services must be used with extra care.</simpara>
4976          </caution>          </caution>
4977          <caution>          <caution>
4978            <simpara>You should basically list only one of <literal>stable</literal>, <literal>testing</literal>, or <literal>unstable</literal> suites in the "<literal>deb</literal>" line.  If you list any combination of <literal>stable</literal>, <literal>testing</literal>, and <literal>unstable</literal> suites in the "<literal>deb</literal>" line, APT programs slow down while only the latest archive is effective.  Multiple listing makes sense for these when the "<literal>/etc/apt/preferences</literal>" file is used with clear objectives (see <xref linkend="_tweaking_candidate_version"/>).</simpara>            <simpara>You should basically list only one of <literal>stable</literal>, <literal>testing</literal>, or <literal>unstable</literal> suites in the "<literal>deb</literal>" line.  If you list any combination of <literal>stable</literal>, <literal>testing</literal>, and <literal>unstable</literal> suites in the "<literal>deb</literal>" line, APT programs slow down while only the latest archive is effective.  Multiple listing makes sense for these when the "<literal>/etc/apt/preferences</literal>" file is used with clear objectives (see <xref linkend="_tweaking_candidate_version"/>).</simpara>
4979          </caution>          </caution>
4980          <note>          <tip>
4981            <simpara>For the Debian system with the <literal>stable</literal> and <literal>testing</literal> suites, it is a good idea to include lines with "<literal>http://security.debian.org/</literal>" in the "<literal>/etc/apt/sources.list</literal>" to enable security updates as in the example above.</simpara>            <simpara>For the Debian system with the <literal>stable</literal> and <literal>testing</literal> suites, it is a good idea to include lines with "<literal>http://security.debian.org/</literal>" in the "<literal>/etc/apt/sources.list</literal>" to enable security updates as in the example above.</simpara>
4982            </tip>
4983            <note>
4984              <simpara>The security bugs for the <literal>stable</literal> archive are fixed by the Debian security team.  This activity has been quite rigorous and reliable.  Those for the <literal>testing</literal> archive may be fixed by the Debian testing security team.  For <ulink url="http://lists.debian.org/debian-testing-security-announce/2008/12/msg00019.html">several</ulink> <ulink url="http://lists.debian.org/debian-testing-security-announce/2010/01/msg00000.html">reasons</ulink>, this activity is not as rigorous as that for <literal>stable</literal> and you may need to wait for the migration of fixed <literal>unstable</literal> packages.  Those for the <literal>unstable</literal> archive are fixed by the individual maintainer.  Actively maintained <literal>unstable</literal> packages are usually in a fairly good shape by leveraging latest upstream security fixes.  See <ulink url="http://www.debian.org/security/faq">Debian security FAQ</ulink> for how Debian handles security bugs.</simpara>
4985          </note>          </note>
4986          <simpara>Each Debian archive consists of 3 components. Components are alternatively called <ulink url="http://www.debian.org/doc/debian-policy/ch-archive#s-sections">categories in "Debian Policy"</ulink> or areas in <ulink url="http://www.debian.org/social_contract">"Debian Social Contract"</ulink>.  The component is grouped by the compliance to <ulink url="http://www.debian.org/social_contract#guidelines">"The Debian Free Software Guidelines" (DFSG)</ulink>.</simpara>          <simpara>Each Debian archive consists of 3 components. Components are alternatively called <ulink url="http://www.debian.org/doc/debian-policy/ch-archive#s-sections">categories in "Debian Policy"</ulink> or areas in <ulink url="http://www.debian.org/social_contract">"Debian Social Contract"</ulink>.  The component is grouped by the compliance to <ulink url="http://www.debian.org/social_contract#guidelines">"The Debian Free Software Guidelines" (DFSG)</ulink>.</simpara>
4987          <table pgwide="0" frame="topbot" rowsep="1" colsep="1">          <table pgwide="0" frame="topbot" rowsep="1" colsep="1">
# Line 28649  $ svn cp file:///srv/svn/project/module1 Line 28652  $ svn cp file:///srv/svn/project/module1
28652        </section>        </section>
28653        <section id="_work_flow_of_subversion">        <section id="_work_flow_of_subversion">
28654          <title>Work flow of Subversion</title>          <title>Work flow of Subversion</title>
28655          <simpara>Here is an example of typical work flow using Subversion.</simpara>          <simpara>Here is an example of typical work flow using Subversion with its native client.</simpara>
28656            <tip>
28657              <simpara>Client commands offered by the &lt;package&gt;git-svn&lt;/package&gt; package may offer alternative work flow of Subversion using the &lt;prgn&gt;git&lt;/prgn&gt; command.  See <xref linkend="_git"/>.</simpara>
28658            </tip>
28659          <simpara>Check all available modules from Subversion project pointed by URL "<literal>file:///srv/svn/project</literal>" by the following.</simpara>          <simpara>Check all available modules from Subversion project pointed by URL "<literal>file:///srv/svn/project</literal>" by the following.</simpara>
28660          <screen>$ svn list file:///srv/svn/project          <screen>$ svn list file:///srv/svn/project
28661  module1  module1
Legend:
Removed from v.7355  
changed lines
  Added in v.7364
  ViewVC Help
Powered by ViewVC 1.1.5