* Sec. "Architectures": correction on supported architecture in Linux

    2.2, from Job Bogan
  * Sec. "Experimental": other reasons to use or not use the experiment
    archive "section", from comments by Guy Maor
  * Sec. "Being Kind to Porters": replace x86 with i386 (closes Bug#36485)
  * debian/rules: date printing protected from local l10n (closes Bug#36891)
  * Ch. "Mailing Lists, Servers, and Other Machines": renamed chapter; add
    intro paragraph
  * Sec. "Debian Servers": new, for talking about the standard servers,
    with intro; demoted server sections under that
  * Sec. "The FTP servers": was empty, removed
  * Sec. "The master server": fill in more info and cross-refs on how to
    report problems
  * Sec. "The CVS server": add some more detail which should be included
    when requesting cvs areas; mention the cvsweb URL
  * Sec. "Other Debian Machines": new section, list the machines for which
    a normal developer may have access.

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

diff --git a/debian/changelog b/debian/changelog
index 5c286f7c691bbe985280cb10545bcd977cd11a19..395e15beeb38ed8433fe342928a5d20008664a51 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,25 @@
+developers-reference (2.6.5) unstable; urgency=low
+
+  * Sec. "Architectures": correction on supported architecture in Linux
+    2.2, from Job Bogan
+  * Sec. "Experimental": other reasons to use or not use the experiment
+    archive "section", from comments by Guy Maor
+  * Sec. "Being Kind to Porters": replace x86 with i386 (closes Bug#36485)
+  * debian/rules: date printing protected from local l10n (closes Bug#36891)
+  * Ch. "Mailing Lists, Servers, and Other Machines": renamed chapter; add
+    intro paragraph
+  * Sec. "Debian Servers": new, for talking about the standard servers,
+    with intro; demoted server sections under that
+  * Sec. "The FTP servers": was empty, removed
+  * Sec. "The master server": fill in more info and cross-refs on how to
+    report problems
+  * Sec. "The CVS server": add some more detail which should be included
+    when requesting cvs areas; mention the cvsweb URL
+  * Sec. "Other Debian Machines": new section, list the machines for which
+    a normal developer may have access.
+
+ -- Adam Di Carlo <aph@debian.org>  Tue,  4 May 1999 03:32:21 -0400
+

 developers-reference (2.6.4) unstable; urgency=low
 
   * debian/rules: hack 'byhand' file entries to include debian version
 developers-reference (2.6.4) unstable; urgency=low
 
   * debian/rules: hack 'byhand' file entries to include debian version

diff --git a/debian/rules b/debian/rules
index 6207e0784517a620c14060bcb81c59445d73ee65..d9302e12403c5820ee85b361c9e932870905dd76 100755 (executable)
--- a/debian/rules
+++ b/debian/rules
@@ -23,7 +23,7 @@ compress      := gzip -9f
 # version abstraction
 DEB_VERSION    := $(shell LC_ALL=C dpkg-parsechangelog | grep '^Version: ' | sed 's/^Version: *//')
 # pretty-print the date
 # version abstraction
 DEB_VERSION    := $(shell LC_ALL=C dpkg-parsechangelog | grep '^Version: ' | sed 's/^Version: *//')
 # pretty-print the date

-DATE           := $(shell date --date="`dpkg-parsechangelog | grep '^Date: ' | sed 's/^Date: *//'`" '+%d %B, %Y')
+DATE           := $(shell LC_ALL=C date --date="`dpkg-parsechangelog | grep '^Date: ' | sed 's/^Date: *//'`" '+%d %B, %Y')

 
 # source depends -- check if these packages are installed
 SRC_DEPENDS    := debiandoc-sgml lout psutils
 
 # source depends -- check if these packages are installed
 SRC_DEPENDS    := debiandoc-sgml lout psutils

diff --git a/developers-reference.sgml b/developers-reference.sgml
index 6d10f2562ad8163f7d4f8b7fc9d50a07a445f93c..e99f83dc135ab5e8be2951d7111e2c4aad3040f0 100644 (file)
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -286,7 +286,11 @@ to <email>keyring-maint@debian.org</email>.
          </enumlist>
 
 
          </enumlist>
 
 

-    <chapt id="servers">Mailing Lists and Servers
+    <chapt id="servers">Mailing Lists, Servers, and Other Machines
+      <p>
+In this chapter you will find a very brief road map of the Debian
+mailing lists, the main Debian servers, and other Debian machines
+which may be available to you as a developer.

 
       <sect id="mailing-lists">Mailing lists
        <p>
 
       <sect id="mailing-lists">Mailing lists
        <p>


@@ -331,8 +335,22 @@ posting messages.
 Online archives of mailing lists are available at <url
 id="http://www.debian.org/Lists-Archives/">.
 
 Online archives of mailing lists are available at <url
 id="http://www.debian.org/Lists-Archives/">.
 

+      <sect id="server-machines">Debian servers
+       <p>
+Debian servers are well known servers which serve critical functions
+in the Debian project.  Every developer should know what these servers
+are and what they do.
+       <p>
+If you have a problem with the operation of Debian server, and you
+think that the system operators need to be notified of this problem,
+please find the contact address for the particular role at <url
+id="http://www.debian.org/devel/maintainer_contacts">.  If you have a
+non-operating problems (such as packages to be remove, suggestions for
+the web site, etc.), generally you'll report a bug against a
+``pseudo-package''.  See <ref id="submit-bug"> for information on how
+to submit bugs.

 
 

-      <sect id="servers-master">The master server
+      <sect1 id="servers-master">The master server

        <p>
 The master server, <tt/master.debian.org/, holds the canonical copy
 of the Debian archive (excluding the non-U.S. packages). Generally,
        <p>
 The master server, <tt/master.debian.org/, holds the canonical copy
 of the Debian archive (excluding the non-U.S. packages). Generally,


@@ -352,12 +370,12 @@ clear.
        <p>
 If you find a problem with <tt/master.debian.org/ such as disk full,
 suspicious activity, or whatever, send an email to
        <p>
 If you find a problem with <tt/master.debian.org/ such as disk full,
 suspicious activity, or whatever, send an email to

-<email>debian-admin@debian.org</email>.
+<email>debian-admin@debian.org</email>.  Problems with the Debian FTP
+archive generally need to be reported as bugs against the
+<package>ftp.debian.org</package> pseudo-package, but also see the
+procedures in <ref id="archive-manip">.

 
 

-      <sect id="servers-ftp">The FTP servers
-       <p>
-
-      <sect id="servers-www">The WWW servers
+      <sect1 id="servers-www">The WWW servers

        <p>
 The main web server, <tt/www.debian.org/, is also known as
 <tt/va.debian.org/.  All developers are given accounts on this
        <p>
 The main web server, <tt/www.debian.org/, is also known as
 <tt/va.debian.org/.  All developers are given accounts on this


@@ -383,21 +401,27 @@ else has already reported the problem on the <url
 id="http://www.debian.org/Bugs/db/pa/lwww.debian.org.html" name="Bug
 Tracking System">.
 
 id="http://www.debian.org/Bugs/db/pa/lwww.debian.org.html" name="Bug
 Tracking System">.
 

-      <sect id="servers-cvs">The CVS server
+
+      <sect1 id="servers-cvs">The CVS server

        <p>
 <tt/cvs.debian.org/ is also known as <tt/va.debian.org/, discussed
 above.  If you need the use of a publically accessible CVS server, for
 instance, to help coordinate work on a package between many different
        <p>
 <tt/cvs.debian.org/ is also known as <tt/va.debian.org/, discussed
 above.  If you need the use of a publically accessible CVS server, for
 instance, to help coordinate work on a package between many different

-developers, you can request a CVS area on the server.  Generally,
-<tt/cvs.debian.org/ offers a combination of local CVS access,
-anonymous client-server read-only access, and full client-server
-access through <prgn>ssh</prgn>.
+developers, you can request a CVS area on the server.
+         <p>
+Generally, <tt/cvs.debian.org/ offers a combination of local CVS
+access, anonymous client-server read-only access, and full
+client-server access through <prgn>ssh</prgn>.  Also, the CVS area can
+be accessed read-only via the Web at <url
+id="http://cvs.debian.org/cgi-bin/cvsweb">.

        <p>
 To request a CVS area, send a request via email to
        <p>
 To request a CVS area, send a request via email to

-<email>debian-admin@debian.org</email>.
+<email>debian-admin@debian.org</email>.  Include the name of the
+requested CVS area, what <tt>va.debian.org</tt> user account should
+own the CVSROOT, and why you need it.

 
 
 
 

-      <sect id="servers-mirrors">Mirrors of Debian servers
+      <sect1 id="servers-mirrors">Mirrors of Debian servers

        <p>
 The web and FTP servers have several mirrors available.  Please do not
 put heavy load on the canonical FTP or web servers.  Ideally, the
        <p>
 The web and FTP servers have several mirrors available.  Please do not
 put heavy load on the canonical FTP or web servers.  Ideally, the


@@ -423,6 +447,70 @@ Please do not mirror off of <tt/master.debian.org/.  This host already
 has too much load.  Check the sites above for information, or email
 <email/debian-devel@lists.debian.org/.
 
 has too much load.  Check the sites above for information, or email
 <email/debian-devel@lists.debian.org/.
 

+
+      <sect id="other-machines">Other Debian Machines
+       <p>
+There are other Debian machines which may be made available to you.
+You can use these for Debian-related purposes as you see fit.  Please
+be kind to system administrators, and do not use up tons and tons of
+disk space, network bandwidth, or CPU without first getting the
+approval of the local maintainers.  Usually these machines are run by
+volunteers.  Generally, these machines are for porting activities.
+       <p>
+Aside from the servers mentioned in <ref id="server-machines">, the
+following machines are, or may be made, available to you.  If an email
+address is listed, generally that person is the party to contact about
+issues on the machine.  Otherwise, the machine is probably managed by
+<email>debian-admin@debian.org</email>.
+
+<taglist>
+           <tag><tt>faure.debian.org</tt></tag>
+           <item>
+An Alpha; if you have an account on <tt>master</tt>, you probably
+already have an account here.
+
+           <tag><tt>kubrick.debian.org</tt></tag>
+           <item>
+A SPARC; if you have an account on <tt>master</tt>, you probably
+already have an account here.
+
+           <tag><tt>pandora.debian.org</tt></tag>
+           <item>
+An i386; if you have an account on <tt>master</tt>, you probably
+already have an account here.
+
+           <tag><tt>albert.debian.org</tt></tag>
+           <item>
+An Alpha; you probably want to use <tt>faure</tt> instead, but you may
+request an account from <email>debian-admin@debian.org</email>.
+
+           <tag><tt>powerpc.debian.org</tt></tag>
+           <item>
+A PowerPC; also known as <tt>tervola.infodrom.north.de</tt>. You may
+request an account from <email>joey@debian.org</email> or
+<email>koptein@debian.org</email>.
+
+           <tag><tt>m68k.debian.org</tt></tag>
+           <item>
+A Motorola 6800x0 machine; you may request an account from
+<email>joey@debian.org</email> or <email>james@nocrew.org</email>.
+Runs an autobuilder.
+
+           <tag><tt>alpha.debian.nl</tt></tag>
+           <item>
+An Alpha; you may request an account from
+<email>debian@cistron.nl</email>.
+
+           <tag><tt>xia0[123].kachinatech.com</tt></tag>
+           <item>
+SPARC and UltraSPARC machines.  <tt>xia0[12]</tt> are used for
+automatic compilation; you can request an account on xia03 (an
+UltraSPARC) from <email>wdeng@kachinatech.com</email>.
+
+         </taglist>
+
+
+

     <chapt id="archive">The Debian Archive
 
       <sect>Overview
     <chapt id="archive">The Debian Archive
 
       <sect>Overview


@@ -543,14 +631,14 @@ more and more popular, the kernel was ported to other architectures,
 too.
        <p>
 The Linux 2.0 kernel supports Intel x86, DEC Alpha, SPARC, Motorola
 too.
        <p>
 The Linux 2.0 kernel supports Intel x86, DEC Alpha, SPARC, Motorola

-680x0 machines (like Atari, Amiga and Macintoshes), MIPS, and PowerPC.
-Newer kernels support more architectures, including ARM, UltraSPARC,
-and MIPS.  Since Linux supports these platforms, Debian decided that
-it should, too.  Therefore, Debian has ports underway.  In fact, we
-also have ports underway to non-Linux kernel.  Aside from
+680x0 (like Atari, Amiga and Macintoshes), MIPS, and PowerPC.
+The Linux 2.2 kernel supports even more architectures, including ARM
+and UltraSPARC.  Since Linux supports these platforms, Debian decided
+that it should, too.  Therefore, Debian has ports underway.  In fact,
+we also have ports underway to non-Linux kernel.  Aside from

 <em>i386</em> (our name for Intel x86), there is <em>m68k</em>,
 <em>alpha</em>, <em>powerpc</em>, <em>sparc</em>, <em>hurd-i386</em>,
 <em>i386</em> (our name for Intel x86), there is <em>m68k</em>,
 <em>alpha</em>, <em>powerpc</em>, <em>sparc</em>, <em>hurd-i386</em>,

-and <em>arm</em> as of this writing.
+and <em>arm</em>, as of this writing.

 
        <p>
 Debian GNU/Linux 1.3 is only available as <em>i386</em>.  Debian 2.0
 
        <p>
 Debian GNU/Linux 1.3 is only available as <em>i386</em>.  Debian 2.0


@@ -568,7 +656,6 @@ excepting perhaps the `base' subsection.  Subsections exist simply
 to simplify the organization and browsing of available packages.
 Please check the current Debian distribution to see which sections are
 available.
 to simplify the organization and browsing of available packages.
 Please check the current Debian distribution to see which sections are
 available.

-<p>

 
 
       <sect>Packages
 
 
       <sect>Packages


@@ -686,10 +773,22 @@ could do grave damage to a system, it might be better to put it into
 <em/experimental/.
          <p>
 For instance, an experimental encrypted file system should probably go
 <em/experimental/.
          <p>
 For instance, an experimental encrypted file system should probably go

-into experimental.  A new, beta, version of some software which uses
-completely different configuration might go into experimental at the
-maintainer's discretion.  New software which isn't likely to damage
-your system can go into <em/unstable/.
+into <em>experimental</em>.  A new, beta, version of some software
+which uses completely different configuration might go into
+<em>experimental</em> at the maintainer's discretion.  New software
+which isn't likely to damage your system can go into
+<em>unstable</em>.  If you are working on an incompatible or complex
+upgrade situation, you can also use <em>experimental</em> as a staging
+area, so that testers can get early access.
+         <p>
+However, using <em>experimental</em> as a personal staging area is not
+always the best idea.  You can't replace or upgrade the files in there
+on your own (<prgn>dinstall</prgn> and the Debian archive maintainers
+do that).  Additionally, you'll have to remember to ask the archive
+maintainers to delete the package one you have uploaded it to
+<em>unstable</em>.  Using your personal web space on
+<tt>va.debian.org</tt> is generally a better idea, so that you put
+less strain on the Debian archive maintainers.

 
 
       <sect id="codenames">Release code names
 
 
       <sect id="codenames">Release code names


@@ -1324,7 +1423,7 @@ Porting is the act of building Debian packages for architectures which
 is different from the original architecture of the package
 maintainer's binary package.  It is a unique and essential activity.
 In fact, porters do most of the actual compiling of Debian packages.
 is different from the original architecture of the package
 maintainer's binary package.  It is a unique and essential activity.
 In fact, porters do most of the actual compiling of Debian packages.

-For instance, for one <em>x86</em> binary package, there has to be a
+For instance, for one <em>i386</em> binary package, there has to be a

 recompile for each architecture, which is around five more builds.
 
 
 recompile for each architecture, which is around five more builds.
 
 


@@ -1352,7 +1451,7 @@ Don't set architecture to a value other than ``all'' or ``any'' unless
 you really mean it.  In too many cases, maintainers don't follow the
 instructions in the <url
 id="http://www.debian.org/doc/packaging-manuals/packaging.html/"
 you really mean it.  In too many cases, maintainers don't follow the
 instructions in the <url
 id="http://www.debian.org/doc/packaging-manuals/packaging.html/"

-name="Debian Packaging Manual">.  Setting your architecture to ``x86''
+name="Debian Packaging Manual">.  Setting your architecture to ``i386''

 is usually incorrect.
            <item>
 Make sure your source package is correct.  Do <tt>dpkg-source -x
 is usually incorrect.
            <item>
 Make sure your source package is correct.  Do <tt>dpkg-source -x


@@ -1628,7 +1727,7 @@ outlining all the open bugs against your packages:
 Replace <var>maintainer-address</var> with you official Debian
 maintainer address.
 
 Replace <var>maintainer-address</var> with you official Debian
 maintainer address.
 

-      <sect>Submitting Bugs
+      <sect id="submit-bug">Submitting Bugs

        <p>
 Often as a package maintainer, you find bugs in other packages or else
 have bugs reported to your packages which need to be reassigned.  The
        <p>
 Often as a package maintainer, you find bugs in other packages or else
 have bugs reported to your packages which need to be reassigned.  The