1deb-buildinfo(5) dpkg suite deb-buildinfo(5)
2
6 deb-buildinfo - Debian build information file format
7
9 filename.buildinfo
10
12 Each Debian source package build can record the build information in a
13 .buildinfo control file, which contains a number of fields. Each field
14 begins with a tag, such as Source or Binary (case insensitive),
15 followed by a colon, and the body of the field. Fields are delimited
16 only by field tags. In other words, field text may be multiple lines
17 in length, but the installation tools will generally join lines when
18 processing the body of the field (except in case of the multiline
19 fields Binary-Only-Changes, Installed-Build-Depends, Environment,
20 Checksums-Md5, Checksums-Sha1 and Checksums-Sha256, see below).
21 The control data might be enclosed in an OpenPGP ASCII Armored
23 signature, as specified in RFC4880.
24 The name of the .buildinfo file will depend on the type of build and
26 will be as specific as necessary but not more; for a build that
27 includes any the name will be source-name_binary-
28 version_arch.buildinfo, or otherwise for a build that includes all the
29 name will be source-name_binary-version_all.buildinfo, or otherwise for
30 a build that includes source the name will be source-name_source-
31 version_source.buildinfo.
32
34 Format: format-version (required)
35 The value of this field declares the format version of the file.
36 The syntax of the field value is a version number with a major
37 and minor component. Backward incompatible changes to the
38 format will bump the major version, and backward compatible
39 changes (such as field additions) will bump the minor version.
40 The current format version is 1.0.
41 Source: source-name [(source-version)] (required)
43 The name of the source package. If the source version differs
44 from the binary version, then the source-name will be followed
45 by a source-version in parenthesis. This can happen when the
46 build is for a binary-only non-maintainer upload.
47 Binary: binary-package-list (required)
49 This folded field is a space-separated list of binary packages
50 built.
51 Architecture: arch-list (required)
53 This space-separated field lists the architectures of the files
54 currently being built. Common architectures are amd64, armel,
55 i386, etc. Note that the all value is meant for packages that
56 are architecture independent. If the source for the package is
57 also being built, the special entry source is also present.
58 Architecture wildcards must never be present in the list.
59 Version: version-string (required)
61 Typically, this is the original package's version number in
62 whatever form the program's author uses. It may also include a
63 Debian revision number (for non-native packages). The exact
64 format and sorting algorithm are described in deb-version(5).
65 Binary-Only-Changes:
67 changelog-entry
68 This multiline field contains the concatenated text of the
69 changelog entry for a binary-only non-maintainer upload (binNMU)
70 if that is the case. To make this a valid multiline field empty
71 lines are replaced with a single full stop (‘.’) and all lines
72 are indented by one space character. The exact content depends
73 on the changelog format.
74 Checksums-Md5: (required)
76 Checksums-Sha1: (required)
77 Checksums-Sha256: (required)
78 checksum size filename
79 These multiline fields contain a list of files with a checksum
80 and size for each one. These fields have the same syntax and
81 differ only in the checksum algorithm used: MD5 for
82 Checksums-Md5, SHA-1 for Checksums-Sha1 and SHA-256 for
83 Checksums-Sha256.
84 The first line of the field value (the part on the same line as
86 the field name followed by a colon) is always empty. The
87 content of the field is expressed as continuation lines, one
88 line per file. Each line consists of space-separated entries
89 describing the file: the checksum, the file size, and the file
90 name.
91 These fields list all files that make up the build.
93 Build-Origin: name
95 The name of the distribution this package is originating from.
96 Build-Architecture: arch (required)
98 The Debian architecture for the installation the packages is
99 being built in. Common architectures are amd64, armel, i386,
100 etc.
101 Build-Date: build-date
103 The date the package was built. It must be in the same format
104 as the date in a deb-changelog(5) entry.
105 Build-Path: build-path
107 The absolute build path, which correspond to the unpacked source
108 tree. This field is only going to be present if the vendor has
109 whitelisted it via some pattern match to avoid leaking possibly
110 sensitive information.
111 On Debian and derivatives only build paths starting with /build/
113 will emit this field.
114 Installed-Build-Depends: (required)
116 package-list
117 The list of installed and configured packages that might affect
118 the package build process.
119 The list consists of each package name, optionally arch-
121 qualified for foreign architectures, with an exact version
122 restriction, separated by commas.
123 The list includes all essential packages, packages listed in
125 Build-Depends, Build-Depends-Arch, Build-Depends-Indep source
126 control fields, any vendor specific builtin dependencies, and
127 all their recursive dependencies. On Debian and derivatives the
128 dependency builtin is build-essential.
129 For dependencies coming from the source control fields, all
131 dependency alternatives and all providers of virtual packages
132 depended on will be included.
133 Environment:
135 variable-list
136 The list of environment variables that are known to affect the
137 package build process, with each environment variable followed
138 by an equal sign (‘=’) and the variable's quoted value, using
139 double quotes (‘"’), and backslashes escaped (‘\\’).
140
142 deb-changes(5), deb-version(5), dpkg-genbuildinfo(1).
1431.18.25 2018-06-26 deb-buildinfo(5)