244 lines
8.1 KiB
HTML
244 lines
8.1 KiB
HTML
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<HTML><HEAD><TITLE>Man page of deb-changes</TITLE>
|
|
</HEAD><BODY>
|
|
<H1>deb-changes</H1>
|
|
Section: dpkg suite (5)<BR>Updated: 2020-03-23<BR><A HREF="#index">Index</A>
|
|
<A HREF="/cgi-bin/man/man2html">Return to Main Contents</A><HR>
|
|
|
|
|
|
<A NAME="lbAB"> </A>
|
|
<H2>NAME</H2>
|
|
|
|
deb-changes - Debian changes file format
|
|
<A NAME="lbAC"> </A>
|
|
<H2>SYNOPSIS</H2>
|
|
|
|
<I>filename</I><B>.changes</B>
|
|
|
|
<A NAME="lbAD"> </A>
|
|
<H2>DESCRIPTION</H2>
|
|
|
|
Each Debian upload is composed of a .changes control file, which
|
|
contains a number of fields.
|
|
Each field begins with a tag, such as
|
|
<B>Source</B>
|
|
|
|
or
|
|
<B>Binary</B>
|
|
|
|
(case insensitive), followed by a colon, and the body of the field.
|
|
Fields are delimited only by field tags.
|
|
In other words, field text may be multiple lines in length, but the
|
|
installation tools will generally join lines when processing the body
|
|
of the field (except in case of the multiline fields
|
|
<B>Description</B>, <B>Changes</B>, <B>Files</B>, <B>Checksums-Sha1</B>
|
|
|
|
and
|
|
<B>Checksums-Sha256</B>,
|
|
|
|
see below).
|
|
<P>
|
|
|
|
The control data might be enclosed in an OpenPGP ASCII Armored signature,
|
|
as specified in RFC4880.
|
|
<A NAME="lbAE"> </A>
|
|
<H2>FIELDS</H2>
|
|
|
|
<DL COMPACT>
|
|
<DT id="1"><B>Format:</B> <I>format-version</I> (required)
|
|
|
|
<DD>
|
|
The value of this field declares the format version of the file.
|
|
The syntax of the field value is a version number with a major and minor
|
|
component.
|
|
Backward incompatible changes to the format will bump the major version,
|
|
and backward compatible changes (such as field additions) will bump the
|
|
minor version.
|
|
The current format version is <B>1.8</B>.
|
|
<DT id="2"><B>Date:</B> <I>release-date</I> (required)
|
|
|
|
<DD>
|
|
The date the package was built or last edited.
|
|
It must be in the same format as the date in a <B><A HREF="/cgi-bin/man/man2html?5+deb-changelog">deb-changelog</A></B>(5)
|
|
entry.
|
|
<P>
|
|
The value of this field is usually extracted from the <I>debian/changelog</I>
|
|
file.
|
|
<DT id="3"><B>Source:</B> <I>source-name</I> [<B>(</B><I>source-version</I><B>)</B>] (required)
|
|
|
|
<DD>
|
|
The name of the source package.
|
|
If the source version differs from the binary version, then the
|
|
<I>source-name</I> will be followed by a <I>source-version</I> in parenthesis.
|
|
This can happen when the upload is a binary-only non-maintainer upload.
|
|
<DT id="4"><B>Binary:</B> <I>binary-package-list</I> (required in context)
|
|
|
|
<DD>
|
|
This folded field is a space-separated list of binary packages to upload.
|
|
If the upload is source-only, then the field is omitted (since dpkg 1.19.3).
|
|
<DT id="5"><B>Architecture:</B> <I>arch-list</I>
|
|
|
|
<DD>
|
|
Lists the architectures of the files currently being uploaded.
|
|
Common architectures are <B>amd64</B>, <B>armel</B>, <B>i386</B>, etc.
|
|
Note that the <B>all</B> value is meant for packages that are architecture
|
|
independent.
|
|
If the source for the package is also being uploaded, the special entry
|
|
<B>source</B> is also present.
|
|
Architecture wildcards must never be present in the list.
|
|
<DT id="6"><B>Version:</B> <I>version-string</I> (required)
|
|
|
|
<DD>
|
|
Typically, this is the original package's version number in whatever form
|
|
the program's author uses.
|
|
It may also include a Debian revision number (for non-native packages).
|
|
The exact format and sorting algorithm are described in
|
|
<B><A HREF="/cgi-bin/man/man2html?7+deb-version">deb-version</A></B>(7).
|
|
|
|
<DT id="7"><B>Distribution:</B> <I>distribution</I>s (required)
|
|
|
|
<DD>
|
|
Lists one or more space-separated distributions where this version should
|
|
be installed when it is uploaded to the archive.
|
|
<DT id="8"><B>Urgency:</B> <I>urgency</I> (recommended)
|
|
|
|
<DD>
|
|
The urgency of the upload.
|
|
The currently known values, in increasing order of urgency, are:
|
|
<B>low</B>, <B>medium</B>, <B>high</B>, <B>critical</B> and <B>emergency</B>.
|
|
|
|
<DT id="9"><B>Maintainer:</B> <I>fullname-email</I> (required)
|
|
|
|
<DD>
|
|
Should be in the format "Joe Bloggs <<A HREF="mailto:jbloggs@example.org">jbloggs@example.org</A>>", and is
|
|
typically the person who created the package, as opposed to the author of
|
|
the software that was packaged.
|
|
<DT id="10"><B>Changed-By:</B><I> fullname-email</I>
|
|
|
|
<DD>
|
|
Should be in the format "Joe Bloggs <<A HREF="mailto:jbloggs@example.org">jbloggs@example.org</A>>", and is
|
|
typically the person who prepared the package changes for this release.
|
|
<DT id="11"><B>Description:</B> (recommended)
|
|
|
|
<DD>
|
|
|
|
<I>binary-package-name</I> <B>-</B> <I>binary-package-summary</I>
|
|
|
|
This multiline field contains a list of binary package names followed by
|
|
a space, a dash ('<B>-</B>') and their possibly truncated short
|
|
descriptions.
|
|
If the upload is source-only, then the field is omitted (since dpkg 1.19.3).
|
|
<DT id="12"><B>Closes:</B><I> bug-number-list</I>
|
|
|
|
<DD>
|
|
A space-separated list of bug report numbers that have been resolved with
|
|
this upload.
|
|
The distribution archive software might use this field to automatically
|
|
close the referred bug numbers in the distribution bug tracking system.
|
|
<DT id="13"><B>Binary-Only: yes</B>
|
|
|
|
<DD>
|
|
This field denotes that the upload is a binary-only non-maintainer build.
|
|
It originates from the <B>binary-only=yes</B> key/value from the changelog
|
|
metadata entry.
|
|
<DT id="14"><B>Built-For-Profiles:</B><I> profile-list</I>
|
|
|
|
<DD>
|
|
This field specifies a whitespace separated list of build profiles that
|
|
this upload was built with.
|
|
<DT id="15"><B>Changes:</B> (required)
|
|
|
|
<DD>
|
|
|
|
<I> changelog-entries</I>
|
|
|
|
This multiline field contains the concatenated text of all changelog
|
|
entries that are part of the upload.
|
|
To make this a valid multiline field empty lines are replaced with a
|
|
single full stop ('.') and all lines are indented by one space
|
|
character.
|
|
The exact content depends on the changelog format.
|
|
<DT id="16"><B>Files:</B> (required)
|
|
|
|
<DD>
|
|
|
|
<I>md5sum</I> <I>size</I> <I>section</I> <I>priority</I> <I>filename</I>
|
|
|
|
This multiline field contains a list of files with an md5sum, size, section
|
|
and priority for each one.
|
|
<P>
|
|
The first line of the field value (the part on the same line as the field
|
|
name followed by a colon) is always empty.
|
|
The content of the field is expressed as continuation lines, one line per file.
|
|
Each line consists of space-separated entries describing the file:
|
|
the md5sum, the file size, the file section, the file priority, and
|
|
the file name.
|
|
<P>
|
|
This field lists all files that make up the upload.
|
|
The list of files in this field must match the list of files in the
|
|
other related <B>Checksums</B> fields.
|
|
<DT id="17"><B>Checksums-Sha1:</B> (required)
|
|
|
|
<DD>
|
|
|
|
<B>Checksums-Sha256:</B> (required)
|
|
|
|
|
|
<I>checksum</I> <I>size</I> <I>filename</I>
|
|
|
|
These multiline fields contain a list of files with a checksum and size
|
|
for each one.
|
|
These fields have the same syntax and differ only in the checksum algorithm
|
|
used: SHA-1 for <B>Checksums-Sha1</B> and SHA-256 for <B>Checksums-Sha256</B>.
|
|
<P>
|
|
The first line of the field value (the part on the same line as the field
|
|
name followed by a colon) is always empty.
|
|
The content of the field is expressed as continuation lines, one line per file.
|
|
Each line consists of space-separated entries describing the file:
|
|
the checksum, the file size, and the file name.
|
|
<P>
|
|
These fields list all files that make up the upload.
|
|
The list of files in these fields must match the list of files in the
|
|
<B>Files</B> field and the other related <B>Checksums</B> fields.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</DL>
|
|
<A NAME="lbAF"> </A>
|
|
<H2>BUGS</H2>
|
|
|
|
The <B>Files</B> field is inconsistent with the other <B>Checksums</B> fields.
|
|
The <B>Changed-By</B> and <B>Maintainer</B> fields have confusing names.
|
|
The <B>Distribution</B> field contains information about what is commonly
|
|
referred to as a suite.
|
|
<A NAME="lbAG"> </A>
|
|
<H2>SEE ALSO</H2>
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?5+deb-src-control">deb-src-control</A></B>(5),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?7+deb-version">deb-version</A></B>(7).
|
|
|
|
<P>
|
|
|
|
<HR>
|
|
<A NAME="index"> </A><H2>Index</H2>
|
|
<DL>
|
|
<DT id="18"><A HREF="#lbAB">NAME</A><DD>
|
|
<DT id="19"><A HREF="#lbAC">SYNOPSIS</A><DD>
|
|
<DT id="20"><A HREF="#lbAD">DESCRIPTION</A><DD>
|
|
<DT id="21"><A HREF="#lbAE">FIELDS</A><DD>
|
|
<DT id="22"><A HREF="#lbAF">BUGS</A><DD>
|
|
<DT id="23"><A HREF="#lbAG">SEE ALSO</A><DD>
|
|
</DL>
|
|
<HR>
|
|
This document was created by
|
|
<A HREF="/cgi-bin/man/man2html">man2html</A>,
|
|
using the manual pages.<BR>
|
|
Time: 00:06:02 GMT, March 31, 2021
|
|
</BODY>
|
|
</HTML>
|