1deb-buildinfo(5)                  dpkg suite                  deb-buildinfo(5)
2
3
4

NAME

6       deb-buildinfo - Debian build information file format
7

SYNOPSIS

9       filename.buildinfo
10

DESCRIPTION

12       Each Debian source package build can record the build information in a
13       .buildinfo control file, which contains a number of fields in deb822(5)
14       format.
15
16       Each field begins with a tag, such as Source or Binary (case
17       insensitive), followed by a colon, and the body of the field (case
18       sensitive unless stated otherwise).  Fields are delimited only by field
19       tags.  In other words, field text may be multiple lines in length, but
20       the installation tools will generally join lines when processing the
21       body of the field (except in case of the multiline fields Binary-Only-
22       Changes, Installed-Build-Depends, Environment, Checksums-Md5,
23       Checksums-Sha1 and Checksums-Sha256, see below).
24
25       The control data might be enclosed in an OpenPGP ASCII Armored
26       signature, as specified in RFC4880.
27
28       The name of the .buildinfo file will depend on the type of build and
29       will be as specific as necessary but not more; for a build that
30       includes any the name will be source-name_binary-
31       version_arch.buildinfo, or otherwise for a build that includes all the
32       name will be source-name_binary-version_all.buildinfo, or otherwise for
33       a build that includes source the name will be source-name_source-
34       version_source.buildinfo.
35

FIELDS

37       Format: format-version (required)
38           The value of this field declares the format version of the file.
39           The syntax of the field value is a version number with a major and
40           minor component.  Backward incompatible changes to the format will
41           bump the major version, and backward compatible changes (such as
42           field additions) will bump the minor version.  The current format
43           version is 1.0.
44
45       Source: source-name [(source-version)] (required)
46           The name of the source package.  If the source version differs from
47           the binary version, then the source-name will be followed by a
48           source-version in parenthesis.  This can happen when the build is
49           for a binary-only non-maintainer upload.
50
51       Binary: binary-package-list (required in context)
52           This folded field is a space-separated list of binary packages
53           built.  If the build is source-only, then the field is omitted
54           (since dpkg 1.20.0).
55
56       Architecture: arch-list (required)
57           This space-separated field lists the architectures of the files
58           currently being built.  Common architectures are amd64, armel,
59           i386, etc.  Note that the all value is meant for packages that are
60           architecture independent.  If the source for the package is also
61           being built, the special entry source is also present.
62           Architecture wildcards must never be present in the list.
63
64       Version: version-string (required)
65           Typically, this is the original package's version number in
66           whatever form the program's author uses.  It may also include a
67           Debian revision number (for non-native packages).  The exact format
68           and sorting algorithm are described in deb-version(7).
69
70       Binary-Only-Changes:
71        changelog-entry
72           This multiline field contains the concatenated text of the
73           changelog entry for a binary-only non-maintainer upload (binNMU) if
74           that is the case.  To make this a valid multiline field empty lines
75           are replaced with a single full stop (‘.’) and all lines are
76           indented by one space character.  The exact content depends on the
77           changelog format.
78
79       Checksums-Md5: (required)
80       Checksums-Sha1: (required)
81       Checksums-Sha256: (required)
82        checksum size filename
83           These multiline fields contain a list of files with a checksum and
84           size for each one.  These fields have the same syntax and differ
85           only in the checksum algorithm used: MD5 for Checksums-Md5, SHA-1
86           for Checksums-Sha1 and SHA-256 for Checksums-Sha256.
87
88           The first line of the field value (the part on the same line as the
89           field name followed by a colon) is always empty.  The content of
90           the field is expressed as continuation lines, one line per file.
91           Each line consists of space-separated entries describing the file:
92           the checksum, the file size, and the file name.
93
94           These fields list all files that make up the build.
95
96       Build-Origin: name
97           The name of the distribution this package is originating from.
98
99       Build-Architecture: arch (required)
100           The Debian architecture for the installation the packages is being
101           built in.  Common architectures are amd64, armel, i386, etc.
102
103       Build-Date: build-date
104           The date the package was built.  It must be in the same format as
105           the date in a deb-changelog(5) entry.
106
107       Build-Kernel-Version: build-kernel-version
108           The release and version (in an unspecified format) of the kernel
109           running on the build system.  This field is only going to be
110           present if the builder has explicitly requested it, to avoid
111           leaking possibly sensitive information.
112
113       Build-Path: build-path
114           The absolute build path, which correspond to the unpacked source
115           tree.  This field is only going to be present if the vendor has
116           allowed it via some pattern match to avoid leaking possibly
117           sensitive information.
118
119           On Debian and derivatives only build paths starting with /build/
120           will emit this field.
121
122       Build-Tainted-By:
123        taint-reason-list
124           This folded field contains a space-separated list of non-exhaustive
125           reason tags (formed by alphanumeric and dash characters) which
126           identify why the current build has been tainted (since dpkg
127           1.19.5).
128
129           On Debian and derivatives the following reason tags can be emitted:
130
131           merged-usr-via-aliased-dirs
132               The system has a merged /usr via aliased directories
133               (previously known as merged-usr-via-symlinks).  This will
134               confuse dpkg-query, dpkg-statoverride, dpkg-trigger, update-
135               alternatives and any other tool using pathnames as keys into
136               their databases, as it creates filesystem aliasing problems,
137               and messes with the understanding of the filesystem that dpkg
138               has recorded in its database.  For build systems that hardcode
139               pathnames to specific binaries or libraries on the resulting
140               artifacts, it can also produce packages that will be
141               incompatible with non-/usr-merged filesystems.
142
143           usr-local-has-configs
144               The system has configuration files under /usr/local/etc.
145
146           usr-local-has-includes
147               The system has header files under /usr/local/include.
148
149           usr-local-has-programs
150               The system has programs under /usr/local/bin or
151               /usr/local/sbin.
152
153           usr-local-has-libraries
154               The system has libraries, either static or shared under
155               /usr/local/lib.
156
157           can-execute-cross-built-programs
158               The system can execute cross built programs, either directly or
159               via some emulation layer.
160
161               Since dpkg 1.21.10.
162
163       Installed-Build-Depends: (required)
164        package-list
165           The list of installed and configured packages that might affect the
166           package build process.
167
168           The list consists of each package name, optionally arch-qualified
169           for foreign architectures, with an exact version restriction,
170           separated by commas.
171
172           The list includes all essential packages, packages listed in Build-
173           Depends, Build-Depends-Arch, Build-Depends-Indep source control
174           fields, any vendor specific builtin dependencies, and all their
175           recursive dependencies.  On Debian and derivatives the dependency
176           builtin is build-essential.
177
178           For dependencies coming from the source control fields, all
179           dependency alternatives and all providers of virtual packages
180           depended on will be included.
181
182       Environment:
183        variable-list
184           The list of environment variables that are known to affect the
185           package build process, with each environment variable followed by
186           an equal sign (‘=’) and the variable's quoted value, using double
187           quotes (‘"’), and backslashes escaped (‘\\’).
188

SEE ALSO

190       deb822(5), deb-changes(5), deb-version(7), dpkg-genbuildinfo(1).
191
192
193
1941.21.21                           2023-02-25                  deb-buildinfo(5)
Impressum