X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=policy.sgml;h=73b8d6a4deeb0dcc5e885fd5cc388f899b2d5346;hb=6b71dce45c85d443ac478005d7107351db2b6119;hp=43926534da730cac53b3f8dcd6ae16b0e9f1f441;hpb=fadd5e8b67183327a7b3c0f9872396242e784875;p=debian%2Fdebian-policy.git
diff --git a/policy.sgml b/policy.sgml
index 4392653..73b8d6a 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -1729,7 +1729,7 @@ zope.
/closes:\s*(?:bug)?\#?\s?\d+(?:,\s*(?:bug)?\#?\s?\d+)*/i
Then all of the bug numbers listed will be closed by the
- archive maintenance script (katie) using the
+ archive maintenance software (dak) using the
version of the changelog entry.
This information is conveyed via the Closes field
@@ -2649,7 +2649,6 @@ Package: libc6
- Source (mandatory)
- Maintainer (mandatory)
- Uploaders
- - DM-Upload-Allowed
- Section (recommended)
- Priority (recommended)
- Build-Depends et al
@@ -2748,13 +2747,12 @@ Package: libc6
- Version (mandatory)
- Maintainer (mandatory)
- Uploaders
- - DM-Upload-Allowed
- Homepage
- Vcs-Browser, Vcs-Git, et al.
- Standards-Version (recommended)
- Build-Depends et al
- Checksums-Sha1
- and Checksums-Sha256 (recommended)
+ and Checksums-Sha256 (mandatory)
- Files (mandatory)
@@ -2807,7 +2805,7 @@ Package: libc6
- Closes
- Changes (mandatory)
- Checksums-Sha1
- and Checksums-Sha256 (recommended)
+ and Checksums-Sha256 (mandatory)
- Files (mandatory)
@@ -3741,28 +3739,19 @@ Checksums-Sha256:
- In the .dsc file, these fields should list all
+ In the .dsc file, these fields list all
files that make up the source package. In
- the .changes file, these fields should list all
+ the .changes file, these fields list all
files being uploaded. The list of files in these fields
must match the list of files in the Files field.
-
+
DM-Upload-Allowed
- Indicates that Debian Maintainers may upload this package to
- the Debian archive. The only valid value is yes. If
- the field DM-Upload-Allowed: yes is present in the
- source section of the source control file of the most recent
- version of a package in unstable or experimental, the Debian
- archive will accept uploads of this package signed with a key
- in the Debian Maintainer keyring. See the General
- Resolution for more
- details.
+ Obsolete, see below.
@@ -3858,6 +3847,28 @@ Checksums-Sha256:
+
+ Obsolete fields
+
+
+ The following fields have been obsoleted and may be found in packages
+ conforming with previous versions of the Policy.
+
+
+
+ DM-Upload-Allowed
+
+
+ Indicates that Debian Maintainers may upload this package to
+ the Debian archive. The only valid value is yes. This
+ field was used to regulate uploads by Debian Maintainers, See the
+ General Resolution for more details.
+
+
+
+
+
@@ -6623,7 +6634,7 @@ Built-Using: grub2 (= 1.99-9), loadlin (= 1.6e-1)
The shlibs system
- The shlibs system is an simpler alternative to
+ The shlibs system is a simpler alternative to
the symbols system for declaring dependencies for
shared libraries. It may be more appropriate for C++
libraries and other cases where tracking individual symbols is
@@ -8038,33 +8049,28 @@ Reloading description configuration...done.
- Packages which provide the ability to view/show/play,
- compose, edit or print MIME types should register themselves
- as such following the current MIME support policy.
+ Packages which provide programs to view/show/play, compose, edit or
+ print MIME types should register them as such by placing a file in
+ format (RFC 1524) in the directory
+ /usr/lib/mime/packages/. The file name should be the
+ binary package's name.
The mime-support package provides the
- update-mime program which allows packages to
- register programs that can show, compose, edit or print
- MIME types.
-
-
-
- Packages containing such programs must register them
- with update-mime as documented in . They should not depend
- on, recommend, or suggest mime-support. Instead,
- they should just put something like the following in the
- postinst and postrm scripts:
-
-
- if [ -x /usr/sbin/update-mime ]; then
- update-mime
- fi
-
+ update-mime program, which integrates these
+ registrations in the /etc/mailcap file, using dpkg
+ triggers
+ Creating, modifying or removing a file in
+ /usr/lib/mime/packages/ using maintainer scripts will
+ not activate the trigger. In that case, it can be done by calling
+ dpkg-trigger --no-await /usr/lib/mime/packages from
+ the maintainer script after creating, modifying, or removing
+ the file.
+ .
+ Packages using this facility should not depend on,
+ recommend, or suggest mime-support.
-