summaryrefslogtreecommitdiff
path: root/man
diff options
context:
space:
mode:
authorGuillem Jover <guillem@debian.org>2018-12-02 03:35:49 +0100
committerGuillem Jover <guillem@debian.org>2019-02-23 16:18:38 +0100
commit13cad525ffbcbfba47863ea41024415ac25f7974 (patch)
tree91090089e34c12c50d207601975fb2d796b00e16 /man
parent967e990834995a6b3f8d3aa9d2cb12e7a97abdda (diff)
downloaddpkg-13cad525ffbcbfba47863ea41024415ac25f7974.tar.gz
dpkg-genbuildinfo: Add support for a new Build-Tainted-By field
This field will contain a list of tainting reason tags, which can denote that the current build has potentially been broken. Suggested-by: Alexander E. Patrakov <patrakov@gmail.com>
Diffstat (limited to 'man')
-rw-r--r--man/deb-buildinfo.man11
1 files changed, 11 insertions, 0 deletions
diff --git a/man/deb-buildinfo.man b/man/deb-buildinfo.man
index 5013aa047..1a1ddc7d1 100644
--- a/man/deb-buildinfo.man
+++ b/man/deb-buildinfo.man
@@ -149,6 +149,17 @@ via some pattern match to avoid leaking possibly sensitive information.
On Debian and derivatives only build paths starting with \fI/build/\fP
will emit this field.
.TP
+.B Build\-Tainted\-By:
+.TQ
+.I " taint-reason-list"
+This folded field contains a space-separated list of non-exhausitve reason
+tags (formed by alphanumeric and dash characters) which identify why the
+current build has been tainted (since dpkg 1.19.5).
+.IP
+On Debian and derivatives the following reason tags can be emitted:
+.RS
+.RE
+.TP
.BR Installed\-Build\-Depends: " (required)"
.TQ
.I " package-list"