dpkg (1.3.8) unstable; urgency=low (high for new source format)

  * dpkg-buildpackage -sa, -si options work correctly.

  * update-rc.d(8) updated to reflect design and reality.
  * Programmers' and policy manual updates.

 -- Ian Jackson <ian@chiark.chu.cam.ac.uk>  Fri, 23 Aug 1996 12:48:26 +0100

debian/changelog

@@ -1,3 +1,12 @@
+dpkg (1.3.8) unstable; urgency=low (high for new source format)
+
+  * dpkg-buildpackage -sa, -si options work correctly.
+
+  * update-rc.d(8) updated to reflect design and reality.
+  * Programmers' and policy manual updates.
+
+ -- Ian Jackson <ian@chiark.chu.cam.ac.uk>  Fri, 23 Aug 1996 12:48:26 +0100
+
 dpkg (1.3.7) unstable; urgency=low (medium for source pkg docs)
 
   * dselect +/-/_/= on lines for all broken, new, local or whatever

doc/changelog

@@ -1,3 +1,21 @@
+debian-manuals (0.2.1.0) unstable;
+
+  * Policy says when and how to include original source in upload.
+
+  * Need -sa on dpkg-genchanges/dpkg-buildpackage when converting.
+
+  * Use minor patchlevel for meaning changes which don't affect packages.
+  * More verbosity about netiquette.
+  * Reorganised participation and upload policy: merged with mailing lists.
+
+ -- Ian Jackson <ian@chiark.chu.cam.ac.uk>  Fri, 23 Aug 1996 12:48:09 +0100
+
+debian-manuals (0.2.0.1) experimental;
+
+  * Said that system administrators' manual does not exist.
+
+ -- Ian Jackson <ian@chiark.chu.cam.ac.uk>  Fri, 23 Aug 1996 04:05:36 +0100
+
 debian-manuals (0.2.0.0) experimental;
 
   * Draft releases.

doc/policy.sgml

@@ -64,6 +64,7 @@ administrators' manual.
 <p>
 
 This document assumes familiarity with these other two manuals.
+Unfortunately the system administrators' manual does not exist yet.
 <p>
 
 The Debian version of the FSF's GNU <prgn/hello/ program is provided
@@ -1126,7 +1127,8 @@ Significant changes that will require work in many packages will be
 signaled by a change to the minor number.  The major patchlevel will
 be changed for any change to the meaning of the standards, however
 small; the minor patchlevel will be changed when only cosmetic,
-typographical or other edits which do not change the meaning are made.
+typographical or other edits which do not change the meaning are made,
+or changes which do not affect the contents of packages.
 <p>
 
 You should regularly, and especially if your package has become out of
@@ -1205,9 +1207,9 @@ including most loops and conditionals you must include a separate
 <tt/set -e/ command at the start of every makefile command that's
 actually one of these miniature shellscripts.
 
-<chapt id="developer">How to become a Debian developer
+<chapt id="developer">Procedure - how to participate in the Debian project
 
-<sect>Before you start work
+<sect>Before you start work on a package
 <p>
 
 So, you've read all the documentation, you understand what everything
@@ -1294,9 +1296,30 @@ This file is a control file with the following fields:
 All of them are mandatory for a Debian upload.  See the list of
 control fields in the <prgn/dpkg/ programmers' manual for the contents
 of these fields.
+<p>
 
+The first time a version is uploaded which corresponds to a particular
+upstream version the original source tarfile should be uploaded and
+included in the <tt/.changes/ file; subsequent times the very same
+tarfile should be used to build the new diffs and <tt/.dsc/ files, and
+it need not then be uploaded.
+<p>
 
-<chapt id="mailinglists">The Debian mailing lists
+By default <prgn/dpkg-genchanges/ and <prgn/dpkg-buildpackage/ will
+include the original source tarfile if and only if the Debian revision
+part of the source version number is <tt/0/ or <tt/1/, indicating a
+new upstream version.  This behaviour may be modified by using
+<tt/-sa/ to always include it or <tt/-sd/ to always leave it out.
+<p>
+
+If no original source is included in the upload then the original
+source tarfile used by <prgn/dpkg-source/ when constructing the
+<tt/.dsc/ file and diff to be uploaded <em/must/ be byte-for-byte
+identical with the one already in the archive.  If there is some
+reason why this is not the case then the new version of the original
+source should be uploaded, possibly by using the <tt/-sa/ flag.
+
+<sect id="mailinglists">The Debian mailing lists
 <p>
 
 The mailing list server is at <tt/lists.debian.org/.  Mail
@@ -1313,7 +1336,8 @@ see the responses.
 <p>
 
 As ever on the net, please trim down the quoting of articles you're
-replying to.
+replying to.  In general, please adhere to the usual conventions for
+posting messages.
 
 
 <chapt id="conversion">Conversion procedure from old source packages
@@ -1450,18 +1474,26 @@ whether to install a package.
 Look everything over.
 
 <item>
-Do a test build using <tt/dpkg-buildpackage -ur -uc -r<var/whatever//.
-Check the permissions and locations of files in the resulting package
-by eyeballing the output of <tt/dpkg-deb --contents/, and check that
-the source build happened OK.  Test install the binary package(s) and
-test extract the source package(s).
+Do a test build using <tt/dpkg-buildpackage -ur -uc -sa
+-r<var/whatever//.  Check the permissions and locations of files in
+the resulting package by eyeballing the output of <tt/dpkg-deb
+--contents/, and check that the source build happened OK.  Test
+install the binary package(s) and test extract the source package(s).
 
 <item>
-Sign the release: either re-run <prgn/dpkg-buildpackage/ (this will
-rebuild the package entirely), or PGP-sign the <tt/.dsc/, rebuild the
-<tt/.changes/ using <prgn/dpkg-genchanges/, and then PGP-sign the
-<tt/.changes/.
+Sign the release: either rebuild everything with <tt/dpkg-buildpackage
+-sa/, or PGP-sign the <tt/.dsc/, rebuild the <tt/.changes/ using
+<tt/dpkg-genchanges -sa/, and then PGP-sign the <tt/.changes/.
 
 </list>
+<p>
+
+The use of <tt/-sa/ on <prgn/dpkg-buildpackage/ and
+<prgn/dpkg-genchanges/ is important when doing the first
+build/uploading of a new-format source package.  Unless this happens
+to be Debian revision <tt/0/ or <tt/1/ by default the original source
+tarfile will not be included in the uploaded files listed in the
+<tt/.changes/ file, and so it won't be installed on the FTP site.
+<tt/-sa/ requests that the original source be included regardless.
 
 </book>

doc/programmer.sgml

@@ -111,7 +111,8 @@ distribution.)
 <p>
 
 It is assumed that the reader is reasonably familiar with the
-<prgn/dpkg/ System Administrators' manual.
+<prgn/dpkg/ System Administrators' manual.  Unfortunately this manual
+does not yet exist.
 <p>
 
 The Debian version of the FSF's GNU hello program is provided as an

scripts/dpkg-buildpackage.sh

@@ -47,7 +47,8 @@ do
 	-p*)	pgpcommand="$value" ;;
 	-us)	signsource=: ;;
 	-uc)	signchanges=: ;;
-	-sa)	sourcestyle='' ;;
+	-si)	sourcestyle=-si ;;
+	-sa)	sourcestyle=-sa ;;
 	-sd)	sourcestyle=-sd ;;
 	-b)	binaryonly=-b ;;
 	-B)	binaryonly=-b; binarytarget=binary-arch ;;

scripts/update-rc.d.8

@@ -1,80 +1,159 @@
 .\" Hey, Emacs!  This is an -*- nroff -*- source file.
-.TH UPDATE\-RC.D 8 "6th June 1996" "Debian Project" "Debian/GNU Linux"
+.\" Authors: Ian Jackson
+.TH UPDATE\-RC.D 8 "23rd August 1996" "Debian Project" "Debian/GNU Linux"
 .SH NAME
 update\-rc.d \- install and remove System-V style init script links
 .SH SYNOPSIS
 .B update\-rc.d
-.I <basename>
-\&remove
-.LP
+.IB name " remove"
+.HP
 .B update-rc.d
-.I <basename>
-\&defaults
-.RI [ " <codenumber> " | " <startcodenumber>" " " "<stopcodenumber> " ]
-.LP
+.IB name " defaults"
+.RI [ NN " | " NN-start " " NN-stop ]
+.HP
 .B update-rc.d
-.I <basename>
-\&start | stop
-.I <codenumber> <runlevel>
-.RI [ " <runlevel> " [ " <runlevel> " [ ... ]]]
-\&.
+.I name
+.BR start | stop
+.IR "NN runlevel runlevel " ...
+.B .
+.BR start | stop
+.IR "NN runlevel runlevel " ...
+.BR . " ..."
 .SH DESCRIPTION
-This manual page explains the Debian
-.B "update-rc.d"
-System-V init script link utility.  It should be used when installing and
-removing init scripts on a Debian system.
+.B update-rc.d
+automatically updates the System V style init script links
+.BI /etc/rc runlevel .d/ NNname
+to scripts
+.BI /etc/init.d/ name \fR.
+These are run by
+.B init
+when changing runlevels and are generally used to start and stop
+system services such as daemons.
+.I runlevel
+is one of the runlevels supported by
+.BR init ", " 0123456 ,
+and
+.I NN
+is the two-digit sequence code used by
+.B init
+to decide which order to run the scripts in.
+
+This manpage documents only the usage and behaviour of
+.BR update-rc.d .
+For a discussion of the System V style init script arrangements please
+see
+.BR init (8)
+and the
+.IR "dpkg programmers' manual" .
+.SH INSTALLING INIT SCRIPT LINKS
+When run with either the
+.BR defaults ", " start ", or " stop
+options, update-rc.d makes links
+.BI /etc/rc runlevel .d/[SK] NNname
+pointing to the script
+.BI /etc/init.d/ name\fR,
+
+If any links
+.BI /etc/rc runlevel .d/?? name
+already exist then
+.B update-rc.d
+does nothing.  This is so that the system administrator can rearrange
+the links, provided that they leave at least one link remaining,
+without having their configuration overwritten.
+
+If
+.B defaults
+is used then
+.B update-rc.d
+will make links to start the service in runlevels
+.B 2345
+and stop the service in runlevels
+.BR 016 .
+By default all the links will have sequence code, but
+this can be overridden by supplying one or two
+.I NN
+arguments; one argument overrides the sequence code for both start and
+stop links whereas of two arguments the first overrides the code for
+start links and the second that for stop links.
+
+Instead of
+.B defaults
+the runlevels in which to start and stop the service may be specified
+explicitly using a series of sets of arguments:
 
+Each of these sets starts with an argument
+.BR start " or " stop
+to specify whether start or stop links are to be created by that set.
+Then follows
+.IR NN ,
+the sequence code number for all the links in the set, and one or more
+runlevel numbers as a single argument each.  The set is terminated by
+an argument
+.B .
+(a single full stop).
+
+When explicit specification, rather than
+.BR defaults ,
+is used there will usually be one
+.B start
+and one
+.B stop
+set.  If different sequence codes are required in different runlevels
+then several 
+.B start
+sets or several
+.B stop
+sets may be specified.
+
+The script
+.BI /etc/init.d/ name
+must exist before
+.B update-rc.d
+is run to create the links.
 .SH REMOVING SCRIPTS
 When invoked with the
 .I remove
-option, update-rc.d removes the links to the script for the package
-.IR basename .
+option, update-rc.d removes any links in the
+.BI /etc/rc runlevel .d
+directories to the script
+.BI /etc/init.d/ name\fR.
 The script must have been deleted already -
 .B update-rc.d
 checks for this.
-It then removes all the (now-dangling) links to the script in
-.RB "" /etc/rc[0123456].d/ .
-
-.SH INSTALLING SCRIPTS
-When run with either the
-.RI "" defaults ", " start ", or " stop
-options, update-rc.d makes links pointing to the script in
-.RB "" /etc/init.d/ .
-The script must be installed before update-rc.d is run.
-The
-.I <codenumber>
-arguments specify the order in which the script will be executed.
-When
-.B init
-changes runlevels it executes the scripts in the order of their
-.I codenumber
-from lowest to highest.
 
-The
-.I <runlevel>
-arguments specify the runlevels that the script will be run in.
-As many as seven runlevels (0-6) may be specified.
-The last runlevel must be followed by a period.
-
-When invoked with the
-.I defaults
-option the start runlevels are 
-.B 2 3 4 5
-and the stop runlevels are
-.RB "" "0 1 2 3 4 5 6" .
-If neither
-.I <codenumber>
-or
-.I <startcodenumber>
-and
-.I <stopcodenumber>
-are specified, then the stop and start codenumbers default to 20.
+.B update-rc.d
+is usually called from a package's post-removal script when that
+script detects that its first argument is
+.BR purge ,
+indicating that the user has requested the configuration for the
+package to be removed.
+.SH BUGS
+This script is written in
+.B sh
+and is therefore far too slow.
 
+There should be a way for the system administrator to specify at least
+the default start and stop runlevels to be used by
+.B defaults
+and possibly to override other things as well.
 .SH FILES
+.TP
 .B /etc/init.d/
-.bl
-.B /etc/rc[0123456].d/
-
-.SH "SEE ALSO"
-.BR init (1),
-.BR inittab (1),
+The directory containing the actual init scripts.
+.TP
+.B /etc/rc?.d/
+The directories containing the links used by
+.TP
+.B /etc/init.d/skeleton
+Model for use by writers of
+.B init.d
+scripts.
+.BR init
+and managed by
+.BR update-rc.d .
+.SH SEE ALSO
+.IR "dpkg programmers manual" ,
+.br
+.BR /etc/init.d/skeleton ,
+.br
+.BR init (8).