{ "mode": "man", "parameter": "debchange", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/debchange/1/json", "generated": "2026-05-30T06:06:24Z", "synopsis": "debchange [options] [text ...]\ndch [options] [text ...]", "sections": { "NAME": { "content": "debchange - Tool for maintenance of the debian/changelog file in a source package\n", "subsections": [] }, "SYNOPSIS": { "content": "debchange [options] [text ...]\ndch [options] [text ...]\n", "subsections": [] }, "DESCRIPTION": { "content": "debchange or its alias dch will add a new comment line to the Debian changelog in the current\nsource tree. This command must be run from within that tree. If the text of the change is\ngiven on the command line, debchange will run in batch mode and simply add the text, with\nline breaks as necessary, at the appropriate place in debian/changelog (or the changelog\nspecified by options, as described below). If the text given on the command line is a null\nstring, debchange will run in batch mode without adding any text. If the text given on the\ncommand line is a space string, debchange will run in batch mode and add a blank changelog\nentry. If no text is specified then debchange will run the editor as determined by sensible-\neditor for you to edit the file. (The environment variables VISUAL and EDITOR are used in\nthis order to determine which editor to use.) Editors which understand the +n option for\nstarting the editing on a specified line will use this to move to the correct line of the\nfile for editing. If the editor is quit without modifying the temporary file, debchange will\nexit without touching the existing changelog. Note that the changelog is assumed to be en‐‐\ncoded with the UTF-8 encoding. If it is not, problems may occur. Please see the iconv(1)\nmanpage to find out how to convert changelogs from legacy encodings. Finally, a changelog or\nNEWS file can be created from scratch using the --create option described below.\n\ndebchange also supports automatically producing bug-closing changelog entries, using the\n--closes option. This will usually query the BTS, the Debian Bug Tracking System (see\nhttps://bugs.debian.org/) to determine the title of the bug and the package in which it oc‐\ncurs. This behaviour can be stopped by giving a --noquery option or by setting the configu‐\nration variable DEBCHANGEQUERYBTS to no, as described below. In either case, the editor\n(as described above) will always be invoked to give an opportunity to modify the entries, and\nthe changelog will be accepted whether or not modifications are made. An extra changelog en‐\ntry can be given on the command line in addition to the closes entries.\n\nAt most one of --append, --increment, --edit, --release, and --newversion may be specified as\nlisted below. If no options are specified, debchange will use heuristics to guess whether or\nnot the package has been successfully released, and behave as if --increment had been speci‐\nfied if the package has been released, or otherwise as if --append has been specified.\n\nTwo different sets of heuristics can be used, as controlled by the --release-heuristic option\nor the DEBCHANGERELEASEHEURISTIC configuration variable. The default changelog heuristic\nassumes the package has been released unless its changelog contains UNRELEASED in the distri‐\nbution field. If this heuristic is enabled then the distribution will default to UNRELEASED\nin new changelog entries, and the --mainttrailer option described below will be automatically\nenabled. This can be useful if a package can be released by different maintainers, or if you\ndo not keep the upload logs. The alternate log heuristic determines if a package has been re‐\nleased by looking for an appropriate dupload(1) or dput(1) log file in the parent directory.\nA warning will be issued if the log file is found but a successful upload is not recorded.\nThis may be because the previous upload was performed with a version of dupload prior to 2.1\nor because the upload failed.\n\nIf either --increment or --newversion is used, the name and email for the new version will be\ndetermined as follows. If the environment variable DEBFULLNAME is set, this will be used for\nthe maintainer full name; if not, then NAME will be checked. If the environment variable\nDEBEMAIL is set, this will be used for the email address. If this variable has the form\n\"name \", then the maintainer name will also be taken from here if neither DEBFULLNAME\nnor NAME is set. If this variable is not set, the same test is performed on the environment\nvariable EMAIL. Next, if the full name has still not been determined, then use getpwuid(3)\nto determine the name from the password file. If this fails, use the previous changelog en‐\ntry. For the email address, if it has not been set from DEBEMAIL or EMAIL, then look in\n/etc/mailname, then attempt to build it from the username and FQDN, otherwise use the email\naddress in the previous changelog entry. In other words, it's a good idea to set DEBEMAIL\nand DEBFULLNAME when using this script.\n\nSupport is included for changelogs that record changes by multiple co-maintainers of a pack‐\nage. If an entry is appended to the current version's entries, and the maintainer is differ‐\nent from the maintainer who is listed as having done the previous entries, then lines will be\nadded to the changelog to tell which maintainers made which changes. Currently only one of\nthe several such styles of recording this information is supported, in which the name of the\nmaintainer who made a set of changes appears on a line before the changes, inside square\nbrackets. This can be switched on and off using the --[no]multimaint option or the DE‐‐\nBCHANGEMULTIMAINT configuration file option; the default is to enable it. Note that if an\nentry has already been marked in this way, then this option will be silently ignored.\n\nIf the directory name of the source tree has the form package-version, then debchange will\nalso attempt to rename it if the (upstream) version number changes. This can be prevented by\nusing the --preserve command line or configuration file option as described below.\n\nIf --force-bad-version or --allow-lower-version is used, debchange will not stop if the new\nversion is less than the current one. This is especially useful while doing backports.\n", "subsections": [ { "name": "Directory name checking", "content": "In common with several other scripts in the devscripts package, debchange will climb the di‐\nrectory tree until it finds a debian/changelog file. As a safeguard against stray files\ncausing potential problems, it will examine the name of the parent directory once it finds\nthe debian/changelog file, and check that the directory name corresponds to the package name.\nPrecisely how it does this is controlled by two configuration file variables DE‐‐\nVSCRIPTSCHECKDIRNAMELEVEL and DEVSCRIPTSCHECKDIRNAMEREGEX, and their corresponding com‐\nmand-line options --check-dirname-level and --check-dirname-regex.\n\nDEVSCRIPTSCHECKDIRNAMELEVEL can take the following values:\n\n0 Never check the directory name.\n\n1 Only check the directory name if we have had to change directory in our search for de‐\nbian/changelog. This is the default behaviour.\n\n2 Always check the directory name.\n\nThe directory name is checked by testing whether the current directory name (as determined by\npwd(1)) matches the regex given by the configuration file option DE‐‐\nVSCRIPTSCHECKDIRNAMEREGEX or by the command line option --check-dirname-regex regex. Here\nregex is a Perl regex (see perlre(3perl)), which will be anchored at the beginning and the\nend. If regex contains a '/', then it must match the full directory path. If not, then it\nmust match the full directory name. If regex contains the string ´PACKAGE', this will be re‐\nplaced by the source package name, as determined from the changelog. The default value for\nthe regex is: ´PACKAGE(-.+)?', thus matching directory names such as PACKAGE and PACKAGE-ver‐\nsion.\n\nThe default changelog to be edited is debian/changelog; however, this can be changed using\nthe --changelog or --news options or the CHANGELOG environment variable, as described below.\n" } ] }, "OPTIONS": { "content": "--append, -a\nAdd a new changelog entry at the end of the current version's entries.\n\n--increment, -i\nIncrement either the final component of the Debian release number or, if this is a na‐\ntive Debian package, the version number. On Ubuntu or Tanglu, this will also change\nthe suffix from buildX to ubuntu1/tanglu1. Use -R, --rebuild for a no change rebuild\nincrement. This creates a new section at the beginning of the changelog with appro‐\npriate headers and footers. Also, if this is a new version of a native Debian pack‐\nage, the directory name is changed to reflect this. If DEBCHANGERELEASEHEURISTIC is\nchangelog (default) and the current release is UNRELEASED, this will only change the\nversion of the current changelog stanza. Otherwise, this will create a new changelog\nstanza with the new version.\n\n--newversion version, -v version\nThis specifies the version number (including the Debian release part) explicitly and\nbehaves as the --increment option in other respects. It will also change the direc‐\ntory name if the upstream version number has changed. If DEBCHANGERELEASEHEURISTIC\nis changelog (default) and the current release is UNRELEASED, this will only change\nthe version of the current changelog stanza. Otherwise, this will create a new\nchangelog stanza with the new version.\n\n--edit, -e\nEdit the changelog in an editor.\n\n--release, -r\nFinalize the changelog for a release. Update the changelog timestamp. If the distri‐\nbution is set to UNRELEASED, change it to the distribution from the previous changelog\nentry (or another distribution as specified by --distribution). If there are no pre‐\nvious changelog entries and an explicit distribution has not been specified, unstable\nwill be used (or the name of the current development release when run under Ubuntu).\n", "subsections": [ { "name": "--force-save-on-release", "content": "When --release is used, an editor is opened to allow inspection of the changelog. The\nuser is required to save the file to accept the modified changelog, otherwise the\noriginal will be kept (default).\n", "long": "--force-save-on-release" }, { "name": "--no-force-save-on-release", "content": "Do not do so. Note that a dummy changelog entry may be supplied in order to achieve\nthe same effect - e.g. debchange --release \"\". The entry will not be added to the\nchangelog but its presence will suppress the editor.\n", "long": "--no-force-save-on-release" }, { "name": "--create", "content": "This will create a new debian/changelog file (or NEWS if the --news option is used).\nYou must be in the top-level directory to use this; no directory name checking will be\nperformed. The package name and version can either be specified using the --package\nand --newversion options, determined from the directory name using the --fromdirname\noption or entered manually into the generated changelog file. The maintainer name is\ndetermined from the environment if this is possible, and the distribution is specified\neither using the --distribution option or in the generated changelog file.\n", "long": "--create" }, { "name": "--empty", "content": "When used in combination with --create, suppress the automatic addition of an \"initial\nrelease\" changelog entry (so that the next invocation of debchange adds the first en‐\ntry). Note that this will cause a dpkg-parsechangelog warning on the next invocation\ndue to the lack of changes.\n\n--package package\nThis specifies the package name to be used in the new changelog; this may only be used\nin conjunction with the --create, --increment and --newversion options.\n\n--nmu, -n\nIncrement the Debian release number for a non-maintainer upload by either appending a\n\".1\" to a non-NMU version number (unless the package is Debian native, in which case\n\"+nmu1\" is appended) or by incrementing an NMU version number, and add an NMU\nchangelog comment. This happens automatically if the packager is neither in the Main‐‐\ntainer nor the Uploaders field in debian/control, unless DEBCHANGEAUTONMU is set to\nno or the --no-auto-nmu option is used.\n", "long": "--empty" }, { "name": "--bin-nmu", "content": "Increment the Debian release number for a binary non-maintainer upload by either ap‐\npending a \"+b1\" to a non-binNMU version number or by incrementing a binNMU version\nnumber, and add a binNMU changelog comment.\n\n--qa, -q\nIncrement the Debian release number for a Debian QA Team upload, and add a QA upload\nchangelog comment.\n\n--rebuild, -R\nIncrement the Debian release number for a no-change rebuild by appending a \"build1\" or\nby incrementing a rebuild version number.\n\n--security, -s\nIncrement the Debian release number for a Debian Security Team non-maintainer upload,\nand add a Security Team upload changelog comment.\n\n--lts Increment the Debian release number for a LTS Security Team non-maintainer upload, and\nadd a LTS Security Team upload changelog comment.\n\n--team Increment the Debian release number for a team upload, and add a Team upload changelog\ncomment.\n\n--upstream, -U\nDon't append distro-name1 to the version on a derived distribution. Increment the De‐\nbian version.\n\n--bpo Increment the Debian release number for an upload to bullseye-backports, and add a\nbackport upload changelog comment.\n", "long": "--bin-nmu" }, { "name": "--stable", "content": "Increment the Debian release number for an upload to the current stable release.\n\n--local, -lsuffix\nAdd a suffix to the Debian version number for a local build.\n\n--force-bad-version, -b\nForce a version number to be less than the current one (e.g., when backporting).\n\n--allow-lower-version pattern\nAllow a version number to be less than the current one if the new version matches the\nspecified pattern.\n", "long": "--stable" }, { "name": "--force-distribution", "content": "Force the provided distribution to be used, even if it doesn't match the list of known\ndistributions (e.g. for unofficial distributions).\n", "long": "--force-distribution" }, { "name": "--auto-nmu", "content": "Attempt to automatically determine whether a change to the changelog represents a Non\nMaintainer Upload. This is the default.\n", "long": "--auto-nmu" }, { "name": "--no-auto-nmu", "content": "Disable automatic NMU detection. Equivalent to setting DEBCHANGEAUTONMU to no.\n\n--fromdirname, -d\nThis will take the upstream version number from the directory name, which should be of\nthe form package-version. If the upstream version number has increased from the most\nrecent changelog entry, then a new entry will be made with version number version-1\n(or version if the package is Debian native), with the same epoch as the previous\npackage version. If the upstream version number is the same, this option will behave\nin the same way as -i.\n\n--closes nnnnn[,nnnnn ...]\nAdd changelog entries to close the specified bug numbers. Also invoke the editor af‐\nter adding these entries. Will generate warnings if the BTS cannot be contacted (and\n--noquery has not been specified), or if there are problems with the bug report lo‐\ncated.\n\n--[no]query\nShould we attempt to query the BTS when generating closes entries?\n\n--preserve, -p\nPreserve the source tree directory name if the upstream version number (or the version\nnumber of a Debian native package) changes. See also the configuration variables sec‐\ntion below.\n\n--no-preserve, --nopreserve\nDo not preserve the source tree directory name (default).\n\n--vendor vendor\nOverride the distributor ID over the default returned by dpkg-vendor. This name is\nused for heuristics applied to new package versions and for sanity checking of the\ntarget distribution.\n\n--distribution dist, -D dist\nUse the specified distribution in the changelog entry being edited, instead of using\nthe previous changelog entry's distribution for new entries or the existing value for\nexisting entries.\n\n--urgency urgency, -u urgency\nUse the specified urgency in the changelog entry being edited, instead of using the\ndefault \"medium\" for new entries or the existing value for existing entries.\n\n--changelog file, -c file\nThis will edit the changelog file instead of the standard debian/changelog. This op‐\ntion overrides any CHANGELOG environment variable setting. Also, no directory\ntraversing or checking will be performed when this option is used.\n\n--news [newsfile]\nThis will edit newsfile (by default, debian/NEWS) instead of the regular changelog.\nDirectory searching will be performed. The changelog will be examined in order to de‐\ntermine the current package version.\n\n--[no]multimaint\nShould we indicate that parts of a changelog entry have been made by different main‐\ntainers? Default is yes; see the discussion above and also the DEBCHANGEMULTIMAINT\nconfiguration file option below.\n\n--[no]multimaint-merge\nShould all changes made by the same author be merged into the same changelog section?\nDefault is no; see the discussion above and also the DEBCHANGEMULTIMAINTMERGE con‐\nfiguration file option below.\n\n--maintmaint, -m\nDo not modify the maintainer details previously listed in the changelog. This is use‐\nful particularly for sponsors wanting to automatically add a sponsorship message with‐\nout disrupting the other changelog details. Note that there may be some interesting\ninteractions if multi-maintainer mode is in use; you will probably wish to check the\nchangelog manually before uploading it in such cases.\n\n--controlmaint, -M\nUse maintainer details from the debian/control Maintainer field rather than relevant\nenvironment variables (DEBFULLNAME, DEBEMAIL, etc.). This option might be useful to\nrestore details of the main maintainer in the changelog trailer after a bogus edit\n(e.g. when -m was intended but forgot) or when releasing a package in the name of the\nmain maintainer (e.g. the team).\n\n--[no]mainttrailer, -t\nIf mainttrailer is set, it will avoid modifying the existing changelog trailer line\n(i.e. the maintainer and date-stamp details), unless used with options that require\nthe trailer to be modified (e.g. --create, --release, -i, --qa, etc.) This option\ndiffers from --maintmaint in that it will use multi-maintainer mode if appropriate,\nwith the exception of editing the trailer. See also the DEBCHANGEMAINTTRAILER config‐\nuration file option below.\n\n--check-dirname-level N\nSee the above section \"Directory name checking\" for an explanation of this option.\n\n--check-dirname-regex regex\nSee the above section \"Directory name checking\" for an explanation of this option.\n\n--no-conf, --noconf\nDo not read any configuration files. This can only be used as the first option given\non the command-line.\n\n--release-heuristic log|changelog\nControls how debchange determines if a package has been released, when deciding\nwhether to create a new changelog entry or append to an existing changelog entry.\n\n--help, -h\nDisplay a help message and exit successfully.\n", "long": "--no-auto-nmu" }, { "name": "--version", "content": "Display version and copyright information and exit successfully.\n", "long": "--version" } ] }, "CONFIGURATION VARIABLES": { "content": "The two configuration files /etc/devscripts.conf and ~/.devscripts are sourced in that order\nto set configuration variables. Command line options can be used to override configuration\nfile settings. Environment variable settings are ignored for this purpose. The currently\nrecognised variables are:\n\nDEBCHANGEPRESERVE\nIf this is set to yes, then it is the same as the --preserve command line parameter\nbeing used.\n\nDEBCHANGEQUERYBTS\nIf this is set to no, then it is the same as the --noquery command line parameter be‐\ning used.\n\nDEVSCRIPTSCHECKDIRNAMELEVEL, DEVSCRIPTSCHECKDIRNAMEREGEX\nSee the above section \"Directory name checking\" for an explanation of these variables.\nNote that these are package-wide configuration variables, and will therefore affect\nall devscripts scripts which check their value, as described in their respective man‐\npages and in devscripts.conf(5).\n\nDEBCHANGERELEASEHEURISTIC\nControls how debchange determines if a package has been released, when deciding\nwhether to create a new changelog entry or append to an existing changelog entry. Can\nbe either log or changelog.\n\nDEBCHANGEMULTIMAINT\nIf set to no, debchange will not introduce multiple-maintainer distinctions when a\ndifferent maintainer appends an entry to an existing changelog. See the discussion\nabove. Default is yes.\n\nDEBCHANGEMULTIMAINTMERGE\nIf set to yes, when adding changes in multiple-maintainer mode debchange will check\nwhether previous changes by the current maintainer exist and add the new changes to\nthe existing block rather than creating a new block. Default is no.\n\nDEBCHANGEMAINTTRAILER\nIf this is set to no, then it is the same as the --nomainttrailer command line parame‐\nter being used.\n\nDEBCHANGETZ\nUse this timezone for changelog entries. Default is the user/system timezone as shown\nby `date -R` and affected by the environment variable TZ.\n\nDEBCHANGELOWERVERSIONPATTERN\nIf this is set, then it is the same as the --allow-lower-version command line parame‐\nter being used.\n\nDEBCHANGEAUTONMU\nIf this is set to no then debchange will not attempt to automatically determine\nwhether the current changelog stanza represents an NMU. The default is yes. See the\ndiscussion of the --nmu option above.\n\nDEBCHANGEFORCESAVEONRELEASE\nIf this is set to no, then it is the same as the --no-force-save-on-release command\nline parameter being used.\n\nDEBCHANGEVENDOR\nUse this vendor instead of the default (dpkg-vendor output). See --vendor for de‐\ntails.\n", "subsections": [] }, "ENVIRONMENT": { "content": "DEBEMAIL, EMAIL, DEBFULLNAME, NAME\nSee the above description of the use of these environment variables.\n\nCHANGELOG\nThis variable specifies the changelog to edit in place of debian/changelog. No direc‐\ntory traversal or checking is performed when this variable is set. This variable is\noverridden by the --changelog command-line setting.\n\nVISUAL, EDITOR\nThese environment variables (in this order) determine the editor used by sensible-edi‐‐\ntor.\n", "subsections": [] }, "SEE ALSO": { "content": "debc(1), debclean(1), dput(1), dupload(1), devscripts.conf(5)\n", "subsections": [] }, "AUTHOR": { "content": "The original author was Christoph Lameter . Many substantial changes\nand improvements were made by Julian Gilbey .\n\n\n\nDEBIAN Debian Utilities DEBCHANGE(1)", "subsections": [] } }, "summary": "debchange - Tool for maintenance of the debian/changelog file in a source package", "flags": [ { "flag": "", "long": "--force-save-on-release", "arg": null, "description": "When --release is used, an editor is opened to allow inspection of the changelog. The user is required to save the file to accept the modified changelog, otherwise the original will be kept (default)." }, { "flag": "", "long": "--no-force-save-on-release", "arg": null, "description": "Do not do so. Note that a dummy changelog entry may be supplied in order to achieve the same effect - e.g. debchange --release \"\". The entry will not be added to the changelog but its presence will suppress the editor." }, { "flag": "", "long": "--create", "arg": null, "description": "This will create a new debian/changelog file (or NEWS if the --news option is used). You must be in the top-level directory to use this; no directory name checking will be performed. The package name and version can either be specified using the --package and --newversion options, determined from the directory name using the --fromdirname option or entered manually into the generated changelog file. The maintainer name is determined from the environment if this is possible, and the distribution is specified either using the --distribution option or in the generated changelog file." }, { "flag": "", "long": "--empty", "arg": null, "description": "When used in combination with --create, suppress the automatic addition of an \"initial release\" changelog entry (so that the next invocation of debchange adds the first en‐ try). Note that this will cause a dpkg-parsechangelog warning on the next invocation due to the lack of changes. --package package This specifies the package name to be used in the new changelog; this may only be used in conjunction with the --create, --increment and --newversion options. --nmu, -n Increment the Debian release number for a non-maintainer upload by either appending a \".1\" to a non-NMU version number (unless the package is Debian native, in which case \"+nmu1\" is appended) or by incrementing an NMU version number, and add an NMU changelog comment. This happens automatically if the packager is neither in the Main‐‐ tainer nor the Uploaders field in debian/control, unless DEBCHANGEAUTONMU is set to no or the --no-auto-nmu option is used." }, { "flag": "", "long": "--bin-nmu", "arg": null, "description": "Increment the Debian release number for a binary non-maintainer upload by either ap‐ pending a \"+b1\" to a non-binNMU version number or by incrementing a binNMU version number, and add a binNMU changelog comment. --qa, -q Increment the Debian release number for a Debian QA Team upload, and add a QA upload changelog comment. --rebuild, -R Increment the Debian release number for a no-change rebuild by appending a \"build1\" or by incrementing a rebuild version number. --security, -s Increment the Debian release number for a Debian Security Team non-maintainer upload, and add a Security Team upload changelog comment. --lts Increment the Debian release number for a LTS Security Team non-maintainer upload, and add a LTS Security Team upload changelog comment. --team Increment the Debian release number for a team upload, and add a Team upload changelog comment. --upstream, -U Don't append distro-name1 to the version on a derived distribution. Increment the De‐ bian version. --bpo Increment the Debian release number for an upload to bullseye-backports, and add a backport upload changelog comment." }, { "flag": "", "long": "--stable", "arg": null, "description": "Increment the Debian release number for an upload to the current stable release. --local, -lsuffix Add a suffix to the Debian version number for a local build. --force-bad-version, -b Force a version number to be less than the current one (e.g., when backporting). --allow-lower-version pattern Allow a version number to be less than the current one if the new version matches the specified pattern." }, { "flag": "", "long": "--force-distribution", "arg": null, "description": "Force the provided distribution to be used, even if it doesn't match the list of known distributions (e.g. for unofficial distributions)." }, { "flag": "", "long": "--auto-nmu", "arg": null, "description": "Attempt to automatically determine whether a change to the changelog represents a Non Maintainer Upload. This is the default." }, { "flag": "", "long": "--no-auto-nmu", "arg": null, "description": "Disable automatic NMU detection. Equivalent to setting DEBCHANGEAUTONMU to no. --fromdirname, -d This will take the upstream version number from the directory name, which should be of the form package-version. If the upstream version number has increased from the most recent changelog entry, then a new entry will be made with version number version-1 (or version if the package is Debian native), with the same epoch as the previous package version. If the upstream version number is the same, this option will behave in the same way as -i. --closes nnnnn[,nnnnn ...] Add changelog entries to close the specified bug numbers. Also invoke the editor af‐ ter adding these entries. Will generate warnings if the BTS cannot be contacted (and --noquery has not been specified), or if there are problems with the bug report lo‐ cated. --[no]query Should we attempt to query the BTS when generating closes entries? --preserve, -p Preserve the source tree directory name if the upstream version number (or the version number of a Debian native package) changes. See also the configuration variables sec‐ tion below. --no-preserve, --nopreserve Do not preserve the source tree directory name (default). --vendor vendor Override the distributor ID over the default returned by dpkg-vendor. This name is used for heuristics applied to new package versions and for sanity checking of the target distribution. --distribution dist, -D dist Use the specified distribution in the changelog entry being edited, instead of using the previous changelog entry's distribution for new entries or the existing value for existing entries. --urgency urgency, -u urgency Use the specified urgency in the changelog entry being edited, instead of using the default \"medium\" for new entries or the existing value for existing entries. --changelog file, -c file This will edit the changelog file instead of the standard debian/changelog. This op‐ tion overrides any CHANGELOG environment variable setting. Also, no directory traversing or checking will be performed when this option is used. --news [newsfile] This will edit newsfile (by default, debian/NEWS) instead of the regular changelog. Directory searching will be performed. The changelog will be examined in order to de‐ termine the current package version. --[no]multimaint Should we indicate that parts of a changelog entry have been made by different main‐ tainers? Default is yes; see the discussion above and also the DEBCHANGEMULTIMAINT configuration file option below. --[no]multimaint-merge Should all changes made by the same author be merged into the same changelog section? Default is no; see the discussion above and also the DEBCHANGEMULTIMAINTMERGE con‐ figuration file option below. --maintmaint, -m Do not modify the maintainer details previously listed in the changelog. This is use‐ ful particularly for sponsors wanting to automatically add a sponsorship message with‐ out disrupting the other changelog details. Note that there may be some interesting interactions if multi-maintainer mode is in use; you will probably wish to check the changelog manually before uploading it in such cases. --controlmaint, -M Use maintainer details from the debian/control Maintainer field rather than relevant environment variables (DEBFULLNAME, DEBEMAIL, etc.). This option might be useful to restore details of the main maintainer in the changelog trailer after a bogus edit (e.g. when -m was intended but forgot) or when releasing a package in the name of the main maintainer (e.g. the team). --[no]mainttrailer, -t If mainttrailer is set, it will avoid modifying the existing changelog trailer line (i.e. the maintainer and date-stamp details), unless used with options that require the trailer to be modified (e.g. --create, --release, -i, --qa, etc.) This option differs from --maintmaint in that it will use multi-maintainer mode if appropriate, with the exception of editing the trailer. See also the DEBCHANGEMAINTTRAILER config‐ uration file option below. --check-dirname-level N See the above section \"Directory name checking\" for an explanation of this option. --check-dirname-regex regex See the above section \"Directory name checking\" for an explanation of this option. --no-conf, --noconf Do not read any configuration files. This can only be used as the first option given on the command-line. --release-heuristic log|changelog Controls how debchange determines if a package has been released, when deciding whether to create a new changelog entry or append to an existing changelog entry. --help, -h Display a help message and exit successfully." }, { "flag": "", "long": "--version", "arg": null, "description": "Display version and copyright information and exit successfully." } ], "examples": [], "see_also": [ { "name": "debc", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/debc/1/json" }, { "name": "debclean", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/debclean/1/json" }, { "name": "dput", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/dput/1/json" }, { "name": "dupload", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/dupload/1/json" }, { "name": "devscripts.conf", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/devscripts.conf/5/json" } ] }