{
    "mode": "man",
    "parameter": "dsc",
    "section": "5",
    "url": "https://www.chedong.com/phpMan.php/man/dsc/5/json",
    "generated": "2026-10-04T17:33:16Z",
    "synopsis": "filename.dsc",
    "sections": {
        "NAME": {
            "content": "dsc - Debian source package control file format\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "filename.dsc\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "Each Debian source package is composed of a .dsc control file, which contains a number of\nfields, 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 Package-List, Files, Checksums-Sha1 and\nChecksums-Sha256, see below).\n\nThe control data might be enclosed in an OpenPGP ASCII Armored signature, as specified in\nRFC4880.\n",
            "subsections": []
        },
        "FIELDS": {
            "content": "Format: format-version (required)\nThe  value  of  this  field declares the format version of the source package.  The field\nvalue is used by programs acting on a source package to interpret the list  of  files  in\nthe  source  package  and determine how to unpack it.  The syntax of the field value is a\nnumeric major revision (“0-9”), a period (“.”), a numeric  minor  revision  (“0-9”),  and\nthen  an  optional  subtype  after  whitespace (“ \\t”), which if specified is a lowercase\nalphanumeric (“a-z0-9”) word in parentheses (“()”).   The  subtype  is  optional  in  the\nsyntax but may be mandatory for particular source format revisions.\n\nThe  source  formats currently supported by dpkg are 1.0, 2.0, 3.0 (native), 3.0 (quilt),\n3.0 (git), 3.0 (bzr) and 3.0 (custom).  See dpkg-source(1) for their description.\n\nSource: source-name (required)\nThe value of this field determines the package name, and is used to generate  file  names\nby most installation tools.\n\nBinary: binary-package-list\nThis  folded field lists binary packages which this source package can produce, separated\nby commas.\n\nThis field has now  been  superseded  by  the  Package-List  field,  which  gives  enough\ninformation  about what binary packages are produced on which architecture, build-profile\nand other involved restrictions.\n\nArchitecture: arch-list (recommended)\nA list of architectures and architecture wildcards separated by spaces which specify  the\ntype  of  hardware  this  package  can  be  compiled  for.  Common architecture names and\narchitecture wildcards are amd64, armel, i386, linux-any, any-amd64, etc.\n\nNote that the all value is meant for packages that are architecture independent, and  any\nfor  packages  that  are architecture dependent.  The list may include (or consist solely\nof) the special value all.  When the list contains the  architecture  wildcard  any,  the\nonly other value allowed in the list is all.\n\nThe   field   value   is  generally  generated  from  Architecture  fields  from  in  the\ndebian/control in the source package.\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\nOrigin: name\nThe name of the distribution this package is originating from.\n\nMaintainer: fullname-email (recommended)\nShould be in the format “Joe Bloggs <jbloggs@foo.com>”, and is typically the  person  who\ncreated the package, as opposed to the author of the software that was packaged.\n\nUploaders: fullname-email-list\nLists  all  the  names  and email addresses of co-maintainers of the package, in the same\nformat as the Maintainer field.  Multiple co-maintainers should be separated by a comma.\n\nDescription short-description\nlong-description\nThe format for the source package description is a short brief summary on the first  line\n(after  the  Description  field).   The  following lines should be used as a longer, more\ndetailed description.  Each line of the long description must be preceded by a space, and\nblank lines in the long description must contain a single  ‘.’  following  the  preceding\nspace.\n\nHomepage: url\nThe upstream project home page url.\n\nStandards-Version: version-string (recommended)\nThis  documents the most recent version of the distribution policy standards this package\ncomplies with.\n\nVcs-Browser: url\nThe url of a web interface to browse the Version Control System repository.\n\nVcs-Arch: url\nVcs-Bzr: url\nVcs-Cvs: url\nVcs-Darcs: url\nVcs-Git: url\nVcs-Hg: url\nVcs-Mtn: url\nVcs-Svn: url\nThese fields declare the url of the Version Control System repository  used  to  maintain\nthis package.  See deb-src-control(5) for more details.\n\nTestsuite: name-list\nThis  field  declares  that  the  source package contains the specified test suites.  The\nvalue is a comma-separated list of test suites.  If the autopkgtest value is  present,  a\ndebian/tests/control is expected to be present, if the file is present but not the value,\nthen dpkg-source will automatically add it, preserving previous values.\n\nTestsuite-Triggers: package-list\nThis field declares the comma-separated union of all test dependencies (Depends fields in\ndebian/tests/control  file), with all restrictions removed, and OR dependencies flattened\n(that is, converted to separate AND relationships), except for binaries generated by this\nsource package and its meta-dependency equivalent @.\n\nRationale:  this  field  is  needed  because  otherwise  to  be  able  to  get  the  test\ndependencies, each source package would need to be unpacked.\n\nBuild-Depends: package-list\nBuild-Depends-Arch: package-list\nBuild-Depends-Indep: package-list\nBuild-Conflicts: package-list\nBuild-Conflicts-Arch: package-list\nBuild-Conflicts-Indep: package-list\nThese  fields declare relationships between the source package and packages used to build\nit.  They are discussed in the deb-src-control(5) manual page.\n",
            "subsections": [
                {
                    "name": "Package-List:",
                    "content": "package package-type section priority key-value-list\nThis multiline field contains a list of binary packages generated by this source package.\n\nThe package is the binary package name.\n\nThe package-type is the binary package type, usually deb, another common value is udeb.\n\nThe section and priority match the binary package fields of the same name.\n\nThe key-value-list is a space separated key=value list, and the currently known  optional\nkeys are:\n\narch\nThe  architecture restriction from the binary package Architecture field, with spaces\nconverted to ‘,’.\n\nprofile\nThe normalized build-profile restriction  formula  from  the  binary  package  Build-\nProfile field, with ORs converted to ‘+’ and ANDs to ‘,’.\n\nprotected\nIf  the binary package is protected, this key will contain the value of the Protected\nfield, that is a yes value.\n\nSupported since dpkg 1.20.1.\n\nessential\nIf the binary package is essential, this key will contain the value of the  Essential\nfield, that is a yes value.\n"
                },
                {
                    "name": "Files: (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\nFiles, 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 the checksum, a space, the file size,  a\nspace, and the file name.\n\nThese  fields list all files that make up the source package.  The list of files in these\nfields must match the list of files in the other related fields.\n"
                }
            ]
        },
        "BUGS": {
            "content": "The Format field conflates the format for  the  .dsc  file  itself  and  the  format  of  the\nextracted source package.\n",
            "subsections": []
        },
        "SEE ALSO": {
            "content": "deb822(5), deb-src-control(5), deb-version(7), dpkg-source(1).\n\n1.22.6                                       2026-05-06                                       dsc(5)",
            "subsections": []
        }
    },
    "summary": "dsc - Debian source package control file format",
    "flags": [],
    "examples": [],
    "see_also": [
        {
            "name": "deb822",
            "section": "5",
            "url": "https://www.chedong.com/phpMan.php/man/deb822/5/json"
        },
        {
            "name": "deb-src-control",
            "section": "5",
            "url": "https://www.chedong.com/phpMan.php/man/deb-src-control/5/json"
        },
        {
            "name": "deb-version",
            "section": "7",
            "url": "https://www.chedong.com/phpMan.php/man/deb-version/7/json"
        },
        {
            "name": "dpkg-source",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/dpkg-source/1/json"
        }
    ]
}