Your message dated Sat, 6 Nov 1999 21:13:58 +0000 (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in debian-policy 3.1.0.0
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Darren Benham
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 5 Jul 1999 04:55:40 +0000
Received: (qmail 13549 invoked by alias); 5 Jul 1999 04:55:39 -0000
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 13543 invoked from network); 5 Jul 1999 04:55:36 -0000
Received: from adsl-216-62-156-206.dsl.hstntx.swbell.net (HELO molehole.sg)
([EMAIL PROTECTED])
by master.debian.org with SMTP; 5 Jul 1999 04:55:36 -0000
Received: from steveg by molehole.sg with local (Exim 2.05 #1 (Debian))
id 1110mw-0007my-00; Sun, 4 Jul 1999 23:55:30 -0500
Date: Sun, 4 Jul 1999 23:55:29 -0500
From: Steve Greenland <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: [PROPOSED] wording cleanup w.r.t. conffile/configuration file
Message-ID: <[EMAIL PROTECTED]>
Reply-To: Steve Greenland <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
Organization: Not my strong point
Sender: Steve Greenland <[EMAIL PROTECTED]>
package: debian-policy
version: 3.0.0.0
(NOTE: This is not a repeat of of 'Bug#40766: [PROPOSED] Rewrite of
"Configuration files" section')
This proposal is to clean up the wording of several sections in the
document that discuss "conffiles" and "configuration files", as well
as a few other minor rewordings that I noted on the way. The path I
took was to change almost all of the references to "mark (or tag) as a
conffile" to "treat as a configuration file", based on my belief that
*any* configuration file should have consistent behavior (local mods
preserved, not removed except when the package is purged, etc.), and
that dpkg's "conffile" mechanism is simply a way to conveniently achieve
this. By using "treat as a configuration file", this allows a package to
(for example) create its /etc/init.d/<package> file during installation,
if it so desires, so long as the sysadmin can modify it without losing
changes.
I believe these changes are independent of the re-write of section 4.7
"Configuration files", and should be dealt with seperately.
Anyway, here's the (text) diff; I'm also keeping an sgml diff for use
when the proposal is accepted. (Many of the diff sections actually only
vary by a few words in the first couple of lines, but the change in
linelength causes the rest of the paragraph to show different as well.)
================================================================
--- policy.text.orig Sun Jul 4 23:37:54 1999
+++ policy.text Sun Jul 4 23:37:45 1999
@@ -980,11 +980,13 @@
should behave as if the configuration has been reloaded successfully.
These scripts should not fail obscurely when the configuration files
- remain but the package has been removed, as the default in `dpkg' is
- to leave configuration files on the system after the package has been
- removed. Only when it is executed with the `--purge' option will dpkg
- remove configuration files. Therefore, you should include a `test'
- statement at the top of the script, like this:
+ remain but the package has been removed, as configuration files remain
+ on the system after the package has been removed. Only when dpkg is
+ executed with the `--purge' option will configuration files be
+ removed. In particular, the init script itself is usually a
+ configuration file (see Section 3.3.5, `Notes'), and will remain on
+ the system if the package is removed but not purged. Therefore, you
+ should include a `test' statement at the top of the script, like this:
test -f <program-executed-later-in-script> || exit 0
@@ -1054,10 +1056,12 @@
them with `update-rc.d', as above.
_Do not_ include the `/etc/rc<n>.d/*' symbolic links in `dpkg''s
- conffiles list! _This will cause problems!_ _Do_, however, include the
- `/etc/init.d' scripts in conffiles. (This is important since we want
+ conffiles list! _This will cause problems!_ _Do_, however, treat the
+ `/etc/init.d' scripts as configuration files, either by marking them
+ as conffiles or managing them correctly in the maintainer scripts (see
+ Section 4.7, `Configuration files'). (This is important since we want
to give the local system administrator the chance to adapt the scripts
- to the local system--e.g., to disable a service without De-installing
+ to the local system--e.g., to disable a service without de-installing
the package, or to specify some special command line options when
starting a service--while making sure her changes aren't lost during
the next package upgrade.)
@@ -1132,7 +1136,7 @@
3.4. Cron jobs
--------------
- Packages may not touch the configuration file `/etc/crontab', nor may
+ Packages may not modify the configuration file `/etc/crontab', nor may
they modify the files in `/var/spool/cron/crontabs'.
If a package wants to install a job that has to be executed via cron,
@@ -1143,26 +1147,28 @@
/etc/cron.weekly
/etc/cron.monthly
- As these directory names say, the files within them are executed on a
- daily, weekly, or monthly basis, respectively.
-
- If a certain job has to be executed more frequently than `daily,' the
- package should install a file `/etc/cron.d/<package-name>' tagged as
- configuration file. This file uses the same syntax as `/etc/crontab'
- and is processed by `cron' automatically. (Note, that scripts in the
- `/etc/cron.d' directory are not handled by `anacron'. Thus, you should
- only use this directory for jobs which may be skipped if the system is
- not running.)
+ As these directory names imply, the files within them are executed on
+ a daily, weekly, or monthly basis, respectively. The exact times are
+ listed in /etc/crontab.
All files installed in any of these directories have to be scripts
(shell scripts, Perl scripts, etc.) so that they can easily be
- modified by the local system administrator. In addition, they have to
- be registered as configuration file.
+ modified by the local system administrator. In addition, they must be
+ treated as configuration files.
- The scripts in these directories have to check, if all necessary
- programs are installed before they try to execute them. Otherwise,
- problems will arise when a package was removed (but not purged), since
- the configuration files are kept on the system in this situation.
+ If a certain job has to be executed more frequently than `daily,' the
+ package should install a file `/etc/cron.d/<package-name>'. This file
+ uses the same syntax as `/etc/crontab' and is processed by `cron'
+ automatically. The file must also be treated as a configuration file.
+ (Note, that entries in the `/etc/cron.d' directory are not handled by
+ `anacron'. Thus, you should only use this directory for jobs which may
+ be skipped if the system is not running.)
+
+ The scripts or crontab entries in these directories should check if
+ all necessary programs are installed before they try to execute them.
+ Otherwise, problems will arise when a package was removed but not
+ purged since configuration files are kept on the system in this
+ situation.
3.5. Console messages
@@ -1738,8 +1744,8 @@
this was deemed not enough.
A better scheme is to use logrotate, a GPL'd program developed by Red
- Hat, which centralizes log management. It has both a config file
- (`/etc/logrotate.conf') and a directory where packages can drop
+ Hat, which centralizes log management. It has both a configuration
+ file (`/etc/logrotate.conf') and a directory where packages can drop
logrotation info (`/etc/logrotate.d').
Log files should usually be named `/var/log/<package>.log'. If you
@@ -2082,13 +2088,14 @@
_Application defaults_ files have to be installed in the directory
`/usr/X11R6/lib/X11/app-defaults/'. They are considered as part of the
program code. Thus, they should not be modified and should not be
- tagged as _conffile_s. If the local system administrator wants to
- customize X applications globally, a file with the same name as that
- of the package should be placed in the `/etc/X11/Xresources/'
- directory instead. _Important:_ packages that install files into the
- `/etc/X11/Xresources/' directory _must_ declare a conflict with `xbase
- (<< 3.3.2.3a-2)'; if this is not done it is possible for the package
- to destroy a previously-existing `/etc/X11/Xresources' _file_.
+ tagged as _conffile_s nor otherwise treated as configuration files. If
+ the local system administrator wants to customize X applications
+ globally, a file with the same name as that of the package should be
+ placed in the `/etc/X11/Xresources/' directory instead. _Important:_
+ packages that install files into the `/etc/X11/Xresources/' directory
+ _must_ declare a conflict with `xbase (<< 3.3.2.3a-2)'; if this is not
+ done it is possible for the package to destroy a previously-existing
+ `/etc/X11/Xresources' _file_.
No package should ever install files into the directories
`/usr/bin/X11/', `/usr/doc/X11/', `/usr/include/X11/', or
================================================================
---------------------------------------
Received: (at 40767-done) by bugs.debian.org; 6 Nov 1999 21:31:44 +0000
Received: (qmail 17140 invoked from network); 6 Nov 1999 21:15:11 -0000
Received: from mserv1c.u-net.net (195.102.240.33)
by master.debian.org with SMTP; 6 Nov 1999 21:15:11 -0000
Received: from [195.102.196.44] (helo=polya)
by mserv1c.u-net.net with esmtp (Exim 2.10 #35)
id 11kD9x-0005Qp-00; Sat, 6 Nov 1999 21:14:05 +0000
Received: from jdg by polya with local (Exim 3.03 #1 (Debian))
id 11kD9q-0000Vf-00; Sat, 06 Nov 1999 21:13:58 +0000
Subject: Fixed in debian-policy 3.1.0.0
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED]
Date: Sat, 6 Nov 1999 21:13:58 +0000 (GMT)
X-Mailer: ELM [version 2.4ME+ PL60 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <[EMAIL PROTECTED]>
From: Julian Gilbey <[EMAIL PROTECTED]>
These bugs have been fixed in debian-policy 3.1.0.0; changelog follows.
Julian
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Julian Gilbey, Dept of Maths, QMW, Univ. of London. [EMAIL PROTECTED]
Debian GNU/Linux Developer, see http://www.debian.org/~jdg
Changes: debian-policy (3.1.0.0) unstable; urgency=low
.
* Add instructions on /usr/doc -> /usr/share/doc symlinks (closes:
#45561, #42447, #48570)
* Added source dependencies (closes: #41232)
* Deprecated /etc/rc.boot (closes: #32448, #32449)
* Update-rc.d now only legal way to automatically access /etc/rc?.d
directoried (closes: #41547)
* FHS compliant location of examples (closes: #42849)
* Added ispell-dictionary to virtual-packages.list (following new
suggestions: no objections => accept) (closes: #8221)
* Added man-browser to virtual-packages.list (closes: #24695)
* Added ident-server to virtual-packages.list (closes: #45307)
* Alphabeticised virtual packages list ;)
* Corrected GPL reference in proposal.sgml
* Clarification of "extra" priority (closes: #33076)
* Remove buggy and seriously problematic licenses from list of contrib
package criteria (closes: #45318)
* Move docs to /usr/share/doc with a compatibility symlink (closes:
#41829)
* Update to FHS 2.1 draft #3 (for /var/state etc. changes).
* Correct /var/lib/games -> /var/games (closes: #42358)
* Added MIME subpolicy (closes: #46516)
* Added support for VISUAL (closes: #41121)
* Clarify non-dependence on /usr/local (closes: #44922)
* Modified description of mail spool locking (closes: #43651)
* Clarified wording of conffiles and configuration files (closes:
#40766, #40767)
* Changed description of release numbers (closes: #44620)
* Added changelog.html -> changelog requirement (closes: $40934)
* packaging-manual now correctly installs its docs (closes: #44643)
* The packaging manual now discusses version numbers based on dates
(closes: #17621)
* Mention ls -f for testing order in which files appear on disk (closes:
#19179)
* Change order of '.' and '+' in description of version numbers (closes:
#41095)
* s/fields/field names/ in section 4.1 of packaging manual for clarity
* Add Build-Depends-Indep: field to control file
