From cbffab246997fb5a06211dfb706b54e5ae5bb59f Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 7 Apr 2024 16:58:51 +0200 Subject: Adding upstream version 1.21.22. Signed-off-by: Daniel Baumann --- man/deb-buildinfo.pod | 259 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 259 insertions(+) create mode 100644 man/deb-buildinfo.pod (limited to 'man/deb-buildinfo.pod') diff --git a/man/deb-buildinfo.pod b/man/deb-buildinfo.pod new file mode 100644 index 0000000..626d12c --- /dev/null +++ b/man/deb-buildinfo.pod @@ -0,0 +1,259 @@ +# dpkg manual page - deb-buildinfo(5) +# +# Copyright © 1995-1996 Ian Jackson +# Copyright © 2010 Russ Allbery +# Copyright © 2015-2016 Guillem Jover +# +# This is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, see . + +=encoding utf8 + +=head1 NAME + +deb-buildinfo - Debian build information file format + +=head1 SYNOPSIS + +IB<.buildinfo> + +=head1 DESCRIPTION + +Each Debian source package build can record the build information in +a B<.buildinfo> control file, which contains a number of fields in +L format. + +Each field begins with a tag, such as +B +or +B +(case insensitive), followed by a colon, and the body of the field +(case sensitive unless stated otherwise). +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, B, B, +B, B +and +B, +see below). + +The control data might be enclosed in an OpenPGP ASCII Armored signature, +as specified in RFC4880. + +The name of the B<.buildinfo> file will depend on the type of build and +will be as specific as necessary but not more; +for a build that includes B the name will be +IB<_>IB<_>IB<.buildinfo>, +or otherwise for a build that includes B the name will be +IB<_>IB<_>B, +or otherwise for a build that includes B the name will be +IB<_>IB<_>B. + +=head1 FIELDS + +=over + +=item B I (required) + +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.0>. + +=item B I [B<(>IB<)>] (required) + +The name of the source package. +If the source version differs from the binary version, then the +I will be followed by a I in parenthesis. +This can happen when the build is for a binary-only non-maintainer upload. + +=item B I (required in context) + +This folded field is a space-separated list of binary packages built. +If the build is source-only, then the field is omitted (since dpkg 1.20.0). + +=item B I (required) + +This space-separated field lists the architectures of the files currently +being built. +Common architectures are B, B, B, etc. +Note that the B value is meant for packages that are architecture +independent. +If the source for the package is also being built, the special entry +B is also present. +Architecture wildcards must never be present in the list. + +=item B I (required) + +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(7). + +=item B + +=item S< >I + +This multiline field contains the concatenated text of the changelog +entry for a binary-only non-maintainer upload (binNMU) if that is the case. +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. + +=item B (required) + +=item B (required) + +=item B (required) + +=item S< >I I 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: MD5 for B, SHA-1 for B and +SHA-256 for B. + +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. + +These fields list all files that make up the build. + +=item B I + +The name of the distribution this package is originating from. + +=item B I (required) + +The Debian architecture for the installation the packages is being built in. +Common architectures are B, B, B, etc. + +=item B I + +The date the package was built. +It must be in the same format as the date in a B(5) +entry. + +=item B I + +The release and version (in an unspecified format) of the kernel running +on the build system. +This field is only going to be present if the builder has explicitly +requested it, to avoid leaking possibly sensitive information. + +=item B I + +The absolute build path, which correspond to the unpacked source tree. +This field is only going to be present if the vendor has allowed it +via some pattern match to avoid leaking possibly sensitive information. + +On Debian and derivatives only build paths starting with I +will emit this field. + +=item B + +=item S< >I + +This folded field contains a space-separated list of non-exhaustive reason +tags (formed by alphanumeric and dash characters) which identify why the +current build has been tainted (since dpkg 1.19.5). + +On Debian and derivatives the following reason tags can be emitted: + +=over + +=item B + +The system has a merged I via aliased directories (previously known +as B). +This will confuse B, B, +B, B and any other tool using +pathnames as keys into their databases, as it creates filesystem aliasing +problems, and messes with the understanding of the filesystem that +B has recorded in its database. +For build systems that hardcode pathnames to specific binaries or libraries +on the resulting artifacts, it can also produce packages that will be +incompatible with non-/usr-merged filesystems. + +=item B + +The system has configuration files under I. + +=item B + +The system has header files under I. + +=item B + +The system has programs under I or I. + +=item B + +The system has libraries, either static or shared under I. + +=item B + +The system can execute cross built programs, either directly or via some +emulation layer. + +Since dpkg 1.21.10. + +=back + +=item B (required) + +=item S< >I + +The list of installed and configured packages that might affect the package +build process. + +The list consists of each package name, optionally arch-qualified for foreign +architectures, with an exact version restriction, separated by commas. + +The list includes all essential packages, packages listed in +B, B, B +source control fields, any vendor specific builtin dependencies, and all +their recursive dependencies. +On Debian and derivatives the dependency builtin is B. + +For dependencies coming from the source control fields, all dependency +alternatives and all providers of virtual packages depended on will be +included. + +=item B + +=item S< >I + +The list of environment variables that are known to affect the package build +process, with each environment variable followed by an equal sign (‘=’) +and the variable's quoted value, using double quotes (‘"’), and +backslashes escaped (‘\\’). + +=back + +=head1 SEE ALSO + +L, +B(5), +B(7), +B(1). -- cgit v1.2.3