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.  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
22       The  control  data  might  be  enclosed  in  an  OpenPGP  ASCII Armored
23       signature, as specified in RFC4880.
24
25       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

FIELDS

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
42       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
48       Binary: binary-package-list (required)
49              This folded field is a space-separated list of  binary  packages
50              built.
51
52       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
60       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(7).
65
66       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
75       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
85              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
92              These fields list all files that make up the build.
93
94       Build-Origin: name
95              The name of the distribution this package is originating from.
96
97       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
102       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
106       Build-Kernel-Version: build-kernel-version
107              The release and version (in an unspecified format) of the kernel
108              running  on  the  build  system.  This field is only going to be
109              present if the builder has explicitly  requested  it,  to  avoid
110              leaking possibly sensitive information.
111
112       Build-Path: build-path
113              The absolute build path, which correspond to the unpacked source
114              tree.  This field is only going to be present if the vendor  has
115              whitelisted  it via some pattern match to avoid leaking possibly
116              sensitive information.
117
118              On Debian and derivatives only build paths starting with /build/
119              will emit this field.
120
121       Build-Tainted-By:
122        taint-reason-list
123              This  folded  field  contains  a  space-separated  list  of non-
124              exhaustive  reason  tags  (formed  by  alphanumeric   and   dash
125              characters)  which  identify  why  the  current  build  has been
126              tainted (since dpkg 1.19.5).
127
128              On Debian and derivatives  the  following  reason  tags  can  be
129              emitted:
130
131              merged-usr-via-symlinks
132                     The  system  has  a  merged /usr via symlinks.  This will
133                     confuse  dpkg-query,   dpkg-statoverride,   dpkg-trigger,
134                     update-alternatives and any other tool using pathnames as
135                     keys into  their  databases,  as  it  creates  filesystem
136                     aliasing  problems,  and messes with the understanding of
137                     the filesystem that dpkg has recorded  in  its  database.
138                     For  build  systems  that  hardcode pathnames to specific
139                     binaries or libraries on the resulting artifacts, it  can
140                     also  produce  packages  that  will  be incompatible with
141                     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       Installed-Build-Depends: (required)
158        package-list
159              The list of installed and configured packages that might  affect
160              the package build process.
161
162              The  list  consists  of  each  package  name,  optionally  arch-
163              qualified for  foreign  architectures,  with  an  exact  version
164              restriction, separated by commas.
165
166              The  list  includes  all  essential packages, packages listed in
167              Build-Depends,  Build-Depends-Arch,  Build-Depends-Indep  source
168              control  fields,  any  vendor specific builtin dependencies, and
169              all their recursive dependencies.  On Debian and derivatives the
170              dependency builtin is build-essential.
171
172              For  dependencies  coming  from  the  source control fields, all
173              dependency alternatives and all providers  of  virtual  packages
174              depended on will be included.
175
176       Environment:
177        variable-list
178              The  list  of environment variables that are known to affect the
179              package build process, with each environment  variable  followed
180              by  an  equal  sign (‘=’) and the variable's quoted value, using
181              double quotes (‘"’), and backslashes escaped (‘\\’).
182

SEE ALSO

184       deb-changes(5), deb-version(7), dpkg-genbuildinfo(1).
185
186
187
1881.19.7                            2019-06-03                  deb-buildinfo(5)
Impressum