{
    "mode": "man",
    "parameter": "deb-buildinfo",
    "section": "5",
    "url": "https://www.chedong.com/phpMan.php/man/deb-buildinfo/5/json",
    "generated": "2026-05-30T06:08:11Z",
    "synopsis": "filename.buildinfo",
    "sections": {
        "NAME": {
            "content": "deb-buildinfo - Debian build information file format\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "filename.buildinfo\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "Each Debian source package build can record the build information in a .buildinfo control\nfile, which contains a number of fields in deb822(5) format.\n\nEach field begins with a tag, such as Source or Binary (case insensitive), followed by a\ncolon, and the body of the field (case sensitive unless stated otherwise).  Fields are\ndelimited only by field tags.  In other words, field text may be multiple lines in length,\nbut the installation tools will generally join lines when processing the body of the field\n(except in case of the multiline fields Binary-Only-Changes, Installed-Build-Depends,\nEnvironment, Checksums-Md5, Checksums-Sha1 and Checksums-Sha256, see below).\n\nThe control data might be enclosed in an OpenPGP ASCII Armored signature, as specified in\nRFC4880.\n\nThe name of the .buildinfo file will depend on the type of build and will be as specific as\nnecessary but not more; for a build that includes any the name will be source-namebinary-\nversionarch.buildinfo, or otherwise for a build that includes all the name will be source-\nnamebinary-versionall.buildinfo, or otherwise for a build that includes source the name\nwill be source-namesource-versionsource.buildinfo.\n",
            "subsections": []
        },
        "FIELDS": {
            "content": "Format: format-version (required)\nThe value of this field declares the format version of the file.  The syntax of the field\nvalue is a version number with a major and minor component.  Backward incompatible\nchanges to the format will bump the major version, and backward compatible changes (such\nas field additions) will bump the minor version.  The current format version is 1.0.\n\nSource: source-name [(source-version)] (required)\nThe name of the source package.  If the source version differs from the binary version,\nthen the source-name will be followed by a source-version in parenthesis.  This can\nhappen when the build is for a binary-only non-maintainer upload.\n\nBinary: binary-package-list (required in context)\nThis folded field is a space-separated list of binary packages built.  If the build is\nsource-only, then the field is omitted (since dpkg 1.20.0).\n\nArchitecture: arch-list (required)\nThis space-separated field lists the architectures of the files currently being built.\nCommon architectures are amd64, armel, i386, etc.  Note that the all value is meant for\npackages that are architecture independent.  If the source for the package is also being\nbuilt, the special entry source is also present.  Architecture wildcards must never be\npresent in the list.\n\nVersion: version-string (required)\nTypically, this is the original package's version number in whatever form the program's\nauthor uses.  It may also include a Debian revision number (for non-native packages).\nThe exact format and sorting algorithm are described in deb-version(7).\n",
            "subsections": [
                {
                    "name": "Binary-Only-Changes:",
                    "content": " changelog-entry\nThis multiline field contains the concatenated text of the changelog entry for a binary-\nonly non-maintainer upload (binNMU) if that is the case.  To make this a valid multiline\nfield empty lines are replaced with a single full stop (‘.’) and all lines are indented\nby one space character.  The exact content depends on the changelog format.\n"
                },
                {
                    "name": "Checksums-Md5: (required)",
                    "content": ""
                },
                {
                    "name": "Checksums-Sha1: (required)",
                    "content": ""
                },
                {
                    "name": "Checksums-Sha256: (required)",
                    "content": " checksum size filename\nThese multiline fields contain a list of files with a checksum and size for each one.\nThese fields have the same syntax and differ only in the checksum algorithm used: MD5 for\nChecksums-Md5, SHA-1 for Checksums-Sha1 and SHA-256 for Checksums-Sha256.\n\nThe first line of the field value (the part on the same line as the field name followed\nby a colon) is always empty.  The content of the field is expressed as continuation\nlines, one line per file.  Each line consists of space-separated entries describing the\nfile: the checksum, the file size, and the file name.\n\nThese fields list all files that make up the build.\n\nBuild-Origin: name\nThe name of the distribution this package is originating from.\n\nBuild-Architecture: arch (required)\nThe Debian architecture for the installation the packages is being built in.  Common\narchitectures are amd64, armel, i386, etc.\n\nBuild-Date: build-date\nThe date the package was built.  It must be in the same format as the date in a deb-\nchangelog(5) entry.\n\nBuild-Kernel-Version: build-kernel-version\nThe release and version (in an unspecified format) of the kernel running on the build\nsystem.  This field is only going to be present if the builder has explicitly requested\nit, to avoid leaking possibly sensitive information.\n\nBuild-Path: build-path\nThe absolute build path, which correspond to the unpacked source tree.  This field is\nonly going to be present if the vendor has allowed it via some pattern match to avoid\nleaking possibly sensitive information.\n\nOn Debian and derivatives only build paths starting with /build/ will emit this field.\n"
                },
                {
                    "name": "Build-Tainted-By:",
                    "content": " taint-reason-list\nThis folded field contains a space-separated list of non-exhaustive reason tags (formed\nby alphanumeric and dash characters) which identify why the current build has been\ntainted (since dpkg 1.19.5).\n\nOn Debian and derivatives the following reason tags can be emitted:\n\nmerged-usr-via-aliased-dirs\nThe system has a merged /usr via aliased directories (previously known as merged-usr-\nvia-symlinks).  This will confuse dpkg-query, dpkg-statoverride, dpkg-trigger,\nupdate-alternatives and any other tool using pathnames as keys into their databases,\nas it creates filesystem aliasing problems, and messes with the understanding of the\nfilesystem that dpkg has recorded in its database.  For build systems that hardcode\npathnames to specific binaries or libraries on the resulting artifacts, it can also\nproduce packages that will be incompatible with non-/usr-merged filesystems.\n\nusr-local-has-configs\nThe system has configuration files under /usr/local/etc.\n\nusr-local-has-includes\nThe system has header files under /usr/local/include.\n\nusr-local-has-programs\nThe system has programs under /usr/local/bin or /usr/local/sbin.\n\nusr-local-has-libraries\nThe system has libraries, either static or shared under /usr/local/lib.\n"
                },
                {
                    "name": "Installed-Build-Depends: (required)",
                    "content": " package-list\nThe list of installed and configured packages that might affect the package build\nprocess.\n\nThe list consists of each package name, optionally arch-qualified for foreign\narchitectures, with an exact version restriction, separated by commas.\n\nThe list includes all essential packages, packages listed in Build-Depends, Build-\nDepends-Arch, Build-Depends-Indep source control fields, any vendor specific builtin\ndependencies, and all their recursive dependencies.  On Debian and derivatives the\ndependency builtin is build-essential.\n\nFor dependencies coming from the source control fields, all dependency alternatives and\nall providers of virtual packages depended on will be included.\n"
                },
                {
                    "name": "Environment:",
                    "content": " variable-list\nThe list of environment variables that are known to affect the package build process,\nwith each environment variable followed by an equal sign (‘=’) and the variable's quoted\nvalue, using double quotes (‘\"’), and backslashes escaped (‘\\\\’).\n"
                }
            ]
        },
        "SEE ALSO": {
            "content": "deb822(5), deb-changes(5), deb-version(7), dpkg-genbuildinfo(1).\n\n\n\n1.21.1                                       2025-09-09                             deb-buildinfo(5)",
            "subsections": []
        }
    },
    "summary": "deb-buildinfo - Debian build information file format",
    "flags": [],
    "examples": [],
    "see_also": [
        {
            "name": "deb822",
            "section": "5",
            "url": "https://www.chedong.com/phpMan.php/man/deb822/5/json"
        },
        {
            "name": "deb-changes",
            "section": "5",
            "url": "https://www.chedong.com/phpMan.php/man/deb-changes/5/json"
        },
        {
            "name": "deb-version",
            "section": "7",
            "url": "https://www.chedong.com/phpMan.php/man/deb-version/7/json"
        },
        {
            "name": "dpkg-genbuildinfo",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/dpkg-genbuildinfo/1/json"
        }
    ]
}