{
    "mode": "man",
    "parameter": "uscan",
    "section": "1",
    "url": "https://www.chedong.com/phpMan.php/man/uscan/1/json",
    "generated": "2026-11-21T06:11:08Z",
    "synopsis": "uscan [options] [path]",
    "sections": {
        "NAME": {
            "content": "uscan - scan/watch upstream sources for new releases of software\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "uscan [options] [path]\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "For basic usage, uscan is executed without any arguments from the root of the Debianized\nsource tree where you see the debian/ directory, or a directory containing multiple source\ntrees.\n\nUnless --watchfile is given, uscan looks recursively for valid source trees starting from the\ncurrent directory (see the below section \"Directory name checking\" for details).\n\nFor each valid source tree found, typically the following happens:\n\n•   uscan  reads  the  first  entry  in debian/changelog to determine the source package name\n<spkg> and the last upstream version.\n\n•   uscan process the watch lines debian/watch from the top to the bottom in a single pass.\n\n•   uscan downloads a web page from the specified URL in debian/watch.\n\n•   uscan extracts hrefs pointing to the upstream tarball(s) from the web page using  the\nspecified matching-pattern in debian/watch.\n\n•   uscan  downloads  the  upstream  tarball with the highest version newer than the last\nupstream version.\n\n•   uscan   saves   the   downloaded   tarball   to    the    parent    ../    directory:\n../<upkg>-<uversion>.tar.gz\n\n•   uscan      invokes     mk-origtargz     to     create     the     source     tarball:\n../<spkg><oversion>.orig.tar.gz\n\n•   For a multiple upstream tarball (MUT) package,  the  secondary  upstream  tarball\nwill instead be named ../<spkg><oversion>.orig-<component>.tar.gz.\n\n•   Repeat until all lines in debian/watch are processed.\n\n•   uscan invokes uupdate to create the Debianized source tree: ../<spkg>-<oversion>/*\n\nPlease note the following.\n\n•   For  simplicity,  the compression method used in examples is gzip with .gz suffix.  Other\nmethods such as xz, bzip2, and lzma with corresponding xz, bz2 and lzma suffixes may also\nbe used.\n\n•   The new version=4 enables handling of multiple upstream tarball (MUT) packages  but  this\nis  a  rare  case  for Debian packaging.  For a single upstream tarball package, there is\nonly one watch line and no ../<spkg><oversion>.orig-<component>.tar.gz .\n\n•   uscan with the --verbose option produces a human readable report of uscan's execution.\n\n•   uscan with the --debug option produces a  human  readable  report  of  uscan's  execution\nincluding internal variable states.\n\n•   uscan with the --extra-debug option produces a human readable report of uscan's execution\nincluding internal variable states and remote content during \"search\" step.\n\n•   uscan with the --dehs option produces an upstream package status report in XML format for\nother programs such as the Debian External Health System.\n\n•   The primary objective of uscan is to help identify if the latest version upstream tarball\nis used or not; and to download the latest upstream tarball.  The ordering of versions is\ndecided by dpkg --compare-versions.\n\n•   uscan  with the --safe option limits the functionality of uscan to its primary objective.\nBoth the repacking of downloaded files and updating of the source  tree  are  skipped  to\navoid  running  unsafe  scripts.   This  also  changes  the  default to --no-download and\n--skip-signature.\n",
            "subsections": []
        },
        "FORMAT OF THE WATCH FILE": {
            "content": "The current version 4 format of debian/watch can be summarized as follows:\n\n•   Leading spaces and tabs are dropped.\n\n•   Empty lines are dropped.\n\n•   A line started by # (hash) is a comment line and dropped.\n\n•   A single \\ (back slash) at the end of a line is dropped and the next line is concatenated\nafter removing leading spaces and tabs. The concatenated line is parsed as a single line.\n(The existence or non-existence of the space before the tailing single \\ is significant.)\n\n•   The first non-comment line is:\n\nversion=4\n\nThis is a required line and the recommended version number.\n\nIf you use \"version=3\" instead here, some features may not work as documented here.   See\n\"HISTORY AND UPGRADING\".\n\n•   The  following non-comment lines (watch lines) specify the rules for the selection of the\ncandidate upstream tarball URLs and are in one of the following three formats:\n\n•   opts=\" ... \" http://URL matching-pattern [version [script]]\n\n•   http://URL matching-pattern [version [script]]\n\n•   opts=\" ... \"\n\nHere,\n\n•   opts=\" ... \" specifies the behavior of uscan.  See \"WATCH FILE OPTIONS\".\n\n•   http://URL specifies the web page where upstream publishes the  link  to  the  latest\nsource archive.\n\n•   https://URL may also be used, as may\n\n•   ftp://URL\n\n•   Some  parts  of  URL may be in the regex match pattern surrounded between ( and )\nsuch as /foo/bar-([\\.\\d]+)/.  (If multiple directories match, the highest version\nis picked.) Otherwise, the URL is taken as verbatim.\n\n•   matching-pattern specifies the full string matching pattern  for  hrefs  in  the  web\npage.  See \"WATCH FILE EXAMPLES\".\n\n•   All  matching  parts  in  (  and  )  are concatenated with . (period) to form the\nupstream version.\n\n•   If the hrefs do not contain directories, you can combine this with  the  previous\nentry. I.e., http://URL/matching-pattern .\n\n•   version restricts the upstream tarball which may be downloaded.  The newest available\nversion is chosen in each case.\n\n•   debian  (default)  requires the downloading upstream tarball to be newer than the\nversion obtained from debian/changelog.\n\n•   version-number such as 12.5 requires the upstream tarball to be  newer  than  the\nversion-number.\n\n•   same  requires the downloaded version of the secondary tarballs to be exactly the\nsame as the one for the first upstream tarball downloaded. (Useful only for MUT)\n\n•   previous  restricts   the   version   of   the   signature   file.   (Used   with\npgpmode=previous)\n\n•   ignore does not restrict the version of the secondary tarballs. (Maybe useful for\nMUT)\n\n•   group  requires  the  downloading  upstream  tarball to be newer than the version\nobtained from debian/changelog. Package  version  is  the  concatenation  of  all\n\"group\" upstream version.\n\n•   checksum  requires  the downloading upstream tarball to be newer than the version\nobtained from debian/changelog. Package  version  is  the  concatenation  of  the\nversion of the main tarball, followed by a checksum of all the tarballs using the\n\"checksum\"  version system.  At least the main upstream source has to be declared\nas \"group\".\n\n•   script is executed at the end of uscan execution with appropriate arguments  provided\nby uscan (default: no action).\n\n•   The  typical  Debian  package  is  a  non-native  package  made from one upstream\ntarball.  Only a single line of the watch line in one of the first two formats is\nusually used with its version set to debian and script set to uupdate.\n\n•   A native package should not specify script.\n\n•   A multiple upstream tarball (MUT) package should specify uupdate as script in the\nlast watch line and should skip specifying script in the rest of the watch lines.\n\n•   The last format of the watch line is useful to set the persistent  parameters:  user-\nagent,  compression.   If  this  format  is  used,  this  must be followed by the URL\ndefining watch line(s).\n\n•   [ and ] in the above format are there to mark the optional parts and  should  not  be\ntyped.\n\nThere  are  a few special strings which are substituted by uscan to make it easy to write the\nwatch file.\n",
            "subsections": [
                {
                    "name": "@PACKAGE@",
                    "content": "This is substituted with the  source  package  name  found  in  the  first  line  of  the\ndebian/changelog file.\n"
                },
                {
                    "name": "@ANY_VERSION@",
                    "content": "This is substituted by the legal upstream version regex (capturing).\n\n[-]?[Vv]?(\\d[\\-+\\.:\\~\\da-zA-Z]*)\n"
                },
                {
                    "name": "@ARCHIVE_EXT@",
                    "content": "This is substituted by the typical archive file extension regex (non-capturing).\n\n(?i)(?:\\.(?:tar\\.xz|tar\\.bz2|tar\\.gz|tar\\.zstd?|zip|tgz|tbz|txz))\n"
                },
                {
                    "name": "@SIGNATURE_EXT@",
                    "content": "This is substituted by the typical signature file extension regex (non-capturing).\n\n(?i)(?:\\.(?:tar\\.xz|tar\\.bz2|tar\\.gz|tar\\.zstd?|zip|tgz|tbz|txz))'(?:\\.(?:asc|pgp|gpg|sig|sign))'\n"
                },
                {
                    "name": "@DEB_EXT@",
                    "content": "This is substituted by the typical Debian extension regexp (capturing).\n\n[\\+~](debian|dfsg|ds|deb)(\\.)?(\\d+)?$\n\nSome  file  extensions  are not included in the above intentionally to avoid false positives.\nYou can still set such file extension patterns manually.\n"
                }
            ]
        },
        "WATCH FILE OPTIONS": {
            "content": "uscan reads the watch options specified in opts=\" ... \" to customize its  behavior.  Multiple\noptions option1, option2, option3, ... can be set as opts=\"option1, option2, option3,  ...  \"\n.  The double quotes are necessary if options contain any spaces.\n\nUnless  otherwise  noted  as  persistent, most options are valid only within their containing\nwatch line.\n\nThe available watch options are:\n\ncomponent=component\nSet the name of the secondary source tarball as <spkg><oversion>.orig-<component>.tar.gz\nfor a MUT package.\n\nctype=component-type\nSet the type of component (only \"nodejs\" and \"perl\" are available for  now).   This  will\nhelp uscan to find current version if component version is ignored.\n\nWhen  using  ctype=nodejs,  uscan  tries  to find a version in \"package.json\", when using\nctype=perl, uscan tries to find a version in \"META.json\".  If a version is found,  it  is\nused  as  current  version for this component, regardless version found in Debian version\nstring. This permits a better change detection when using ignore or  checksum  as  Debian\nversion.\n\ncompression=method\nSet the compression method when the tarball is repacked (persistent).\n\nAvailable  method  values  are  what mk-origtargz supports, so xz, gzip (alias gz), bzip2\n(alias bz2), lzma, default. The default method is currently xz.  When uscan  is  launched\nin  a debian source repository which format is \"1.0\" or undefined, the method switches to\ngzip.\n\nPlease note the repacking of the upstream tarballs by mk-origtargz happens only if one of\nthe following conditions is satisfied:\n\n•   USCANREPACK is set in the devscript  configuration.   See  \"DEVSCRIPT  CONFIGURATION\nVARIABLES\".\n\n•   --repack is set on the commandline.  See <COMMANDLINE OPTIONS>.\n\n•   repack is set in the watch line as opts=\"repack,...\".\n\n•   The upstream archive is of zip type including jar, xpi, ...\n\n•   The upstream archive is of zstd (Zstandard) type.\n\n•   Files-Excluded  or  Files-Excluded-component  stanzas  are set in debian/copyright to\nmake mk-origtargz invoked from uscan remove  files  from  the  upstream  tarball  and\nrepack it.  See \"COPYRIGHT FILE EXAMPLES\" and mk-origtargz(1).\n",
            "subsections": [
                {
                    "name": "repack",
                    "content": "Force repacking of the upstream tarball using the compression method.\n\nrepacksuffix=suffix\nAdd  suffix  to  the  Debian  package  upstream  version  only when the source tarball is\nrepackaged.  This rule should be used only for a single upstream tarball package.\n\nmode=mode\nSet the archive download mode.\n\nLWP This mode is the default one which downloads the specified tarball from  the  archive\nURL  on  the web.  Automatically internal mode value is updated to either http or ftp\nby URL.\n\ngit This mode accesses the upstream git archive directly with the git command  and  packs\nthe source tree with the specified tag via matching-pattern into spkg-version.tar.xz.\n\nIf  the  upstream publishes the released tarball via its web interface, please use it\ninstead of using this mode. This mode is the last resort method.\n\nFor git mode, matching-pattern specifies the full string matching  pattern  for  tags\ninstead of hrefs. If matching-pattern is set to refs/tags/tag-matching-pattern, uscan\ndownloads  source from the refs/tags/matched-tag of the git repository.  The upstream\nversion is extracted from concatenating the matched parts in ( ... ) with  .  .   See\n\"WATCH FILE EXAMPLES\".\n\nIf  matching-pattern  is set to HEAD, uscan downloads source from the HEAD of the git\nrepository and the pertinent version is automatically generated  with  the  date  and\nhash of the HEAD of the git repository.\n\nIf  matching-pattern  is  set  to  refs/heads/branch, uscan downloads source from the\nnamed branch of the git repository.\n\nThe local repository is temporarily created as a bare git repository directory  under\nthe  destination  directory  where  the  downloaded  archive  is  generated.  This is\nnormally erased after the uscan execution.  This local repository is kept if  --debug\noption is used.\n\nIf  the  current  directory is a git repository and the searched repository is listed\namong the registered \"remotes\", then uscan will use it instead of cloning separately.\nThe only local change is that uscan  will  run  a  \"fetch\"  command  to  refresh  the\nrepository.\n\nsvn This  mode accesses the upstream Subversion archive directly with the svn command and\npacks the source tree.\n\nFor svn mode,  matching-pattern  specifies  the  full  string  matching  pattern  for\ndirectories  under  Subversion repository directory, specified via URL.  The upstream\nversion is extracted from concatenating the matched parts in ( ...  ) with . .\n\nIf matching-pattern is set to HEAD, uscan downloads the latest  source  tree  of  the\nURL.   The upstream version is then constructed by appending the last revision of the\nURL to 0.0~svn.\n\nAs commit signing is not possible with Subversion, the default pgpmode is set to none\nwhen mode=svn. Settings of pgpmode other  than  default  and  none  are  reported  as\nerrors.\n\npretty=rule\nSet  the upstream version string to an arbitrary format as an optional opts argument when\nthe matching-pattern is HEAD or heads/branch for git mode.  For the exact syntax, see the\ngit-log manpage under tformat.  The default is pretty=0.0~git%cd.%h.   No  uversionmangle\nrules is applicable for this case.\n\nWhen  pretty=describe  is  used,  the  upstream  version string is the output of the \"git\ndescribe --tags | sed s/-/./g\" command instead. For example, if the commit  is  the  5-th\nafter  the  last  tag  v2.17.12  and  its  short  hash  is  ged992511, then the string is\nv2.17.12.5.ged992511 .  For this case, it is good idea to add uversionmangle=s/^/0.0~/ or\nuversionmangle=s/^v// to make the upstream version string compatible with Debian.  Please\nnote that in order for pretty=describe to function well, upstream need to  avoid  tagging\nwith random alphabetic tags.\n\nThe  pretty=describe  forces  to  set  gitmode=full  to  make  a  full local clone of the\nrepository automatically.\n\ndate=rule\nSet the date string used by the pretty option to an arbitrary format as an optional  opts\nargument  when  the matching-pattern is HEAD or heads/branch for git mode.  For the exact\nsyntax, see the strftime manpage.  The default is date=%Y%m%d.\n\ngitexport=mode\nSet the git archive export operation mode. The default is gitexport=default.  Set this to\ngitexport=all to include all files in the .orig.tar archive, ignoring  any  export-ignore\ngit attributes defined by the upstream.\n\nThis option is valid only in git mode.\n\ngitmode=mode\nSet  the  git  clone  operation  mode. The default is gitmode=shallow.  For some dumb git\nserver, you may need to manually set gitmode=full to force full clone operation.\n\nIf the current directory is a git repository and the searched repository is listed  among\nthe registered \"remotes\", then uscan will use it instead of cloning separately.\n\npgpmode=mode\nSet the PGP/GPG signature verification mode.\n\nauto\nuscan checks possible URLs for the signature file and autogenerates a pgpsigurlmangle\nrule to use it.\n\ndefault\nUse  pgpsigurlmangle=rules  to  generate  the  candidate  upstream signature file URL\nstring from the upstream tarball URL. (default)\n\nIf the specified pgpsigurlmangle is missing,  uscan  checks  possible  URLs  for  the\nsignature file and suggests adding a pgpsigurlmangle rule.\n\nmangle\nUse  pgpsigurlmangle=rules  to  generate  the  candidate  upstream signature file URL\nstring from the upstream tarball URL.\n\nnext\nVerify this downloaded tarball file with the signature file  specified  in  the  next\nwatch   line.    The  next  watch  line  must  be  pgpmode=previous.   Otherwise,  no\nverification occurs.\n\nprevious\nVerify the downloaded tarball file specified in the previous  watch  line  with  this\nsignature file.  The previous watch line must be pgpmode=next.\n\nself\nVerify  the  downloaded  file foo.ext with its self signature and extract its content\ntarball file as foo.\n\ngittag\nVerify tag signature if mode=git.\n\nnone\nNo signature available. (No warning.)\n\nsearchmode=mode\nSet the parsing search mode.\n"
                },
                {
                    "name": "html _(default)",
                    "content": "plain: search pattern in the full page\nThis is useful if page content is not HTML but JSON. Example with npmjs.com:\n\nversion=4\nopts=\"searchmode=plain\" \\\nhttps://registry.npmjs.org/aes-js \\\nhttps://registry.npmjs.org/aes-js/-/aes-js-(\\d[\\d\\.]*)@ARCHIVEEXT@\n"
                },
                {
                    "name": "decompress",
                    "content": "Decompress compressed archive before the pgp/gpg signature verification.\n"
                },
                {
                    "name": "bare",
                    "content": "Disable all site specific special case code such as URL redirector uses and page  content\nalterations. (persistent)\n\nuser-agent=user-agent-string\nSet  the  user-agent  string  used  to  contact  the HTTP(S) server as user-agent-string.\n(persistent)\n\nuser-agent option should be specified by itself in the watch line without URL,  to  allow\nusing semicolons and commas in it.\n\npasv, passive\nUse PASV mode for the FTP connection.\n\nIf  PASV  mode  is  required due to the client side network environment, set uscan to use\nPASV mode via \"COMMANDLINE OPTIONS\" or \"DEVSCRIPT CONFIGURATION VARIABLES\" instead.\n\nactive, nopasv\nDon't use PASV mode for the FTP connection.\n\nunzipopt=options\nAdd the extra options to use with the unzip command,  such  as  -a,  -aa,  and  -b,  when\nexecuted by mk-origtargz.\n\ndversionmangle=rules\nNormalize the last upstream version string found in debian/changelog to compare it to the\navailable  upstream  tarball  version.   Removal  of  the  Debian specific suffix such as\ns/@DEBEXT@// is usually done here.\n\nYou   can   also   use   dversionmangle=auto,   this   is   exactly   the    same    than\ndversionmangle=s/@DEBEXT@//\n\ndirversionmangle=rules\nNormalize  the  directory  path  string  matching  the  regex  in a set of parentheses of\nhttp://URL as the sortable version index string.  This is  used  as  the  directory  path\nsorting index only.\n\nSubstitution such as s/PRE/~pre/; s/RC/~rc/ may help.\n\npagemangle=rules\nNormalize  the  downloaded  web  page  string.  (Don't use this unless this is absolutely\nneeded.  Generally, g flag is required for these rules.)\n\nThis is handy if you wish to access Amazon AWS or Subversion  repositories  in  which  <a\nhref=\"...\"> is not used.\n\nuversionmangle=rules\nNormalize  the  candidate  upstream version strings extracted from hrefs in the source of\nthe web page.  This is used as the  version  sorting  index  when  selecting  the  latest\nupstream version.\n\nSubstitution such as s/PRE/~pre/; s/RC/~rc/ may help.\n\nversionmangle=rules\nSyntactic shorthand for uversionmangle=rules, dversionmangle=rules\n"
                },
                {
                    "name": "hrefdecode=percent-encoding",
                    "content": "Convert  the  selected  upstream tarball href string from the percent-encoded hexadecimal\nstring to the decoded normal URL string for obfuscated web sites.  Only  percent-encoding\nis available and it is decoded with s/%([A-Fa-f\\d]{2})/chr hex $1/eg.\n\ndownloadurlmangle=rules\nConvert  the selected upstream tarball href string into the accessible URL for obfuscated\nweb sites.  This is run after hrefdecode.\n\nfilenamemangle=rules\nGenerate the upstream tarball filename from the selected href string if  matching-pattern\ncan  extract  the  latest  upstream  version  <uversion>  from  the selected href string.\nOtherwise, generate the upstream tarball filename from its full URL string  and  set  the\nmissing <uversion> from the generated upstream tarball filename.\n\nWithout  this  option,  the  default upstream tarball filename is generated by taking the\nlast component of the URL and removing everything after any '?' or '#'.\n\npgpsigurlmangle=rules\nGenerate the candidate upstream signature file URL string from the upstream tarball URL.\n\noversionmangle=rules\nGenerate    the    version    string     <oversion>     of     the     source     tarball\n<spkg><oversion>.orig.tar.gz  from <uversion>.  This should be used to add a suffix such\nas +dfsg to a MUT package.\n\nHere, the mangling rules apply the rules to the pertinent  string.   Multiple  rules  can  be\nspecified  in  a  mangling  rule string by making a concatenated string of each mangling rule\nseparated by ; (semicolon).\n\nEach mangling rule cannot contain ; (semicolon), , (comma), or \" (double quote).\n\nEach mangling rule behaves as if a Perl command \"$string =~ rule\"  is  executed.   There  are\nsome notable details.\n\n•   rule may only use the s, tr, and y operations.\n\ns/regex/replacement/options\nRegex  pattern  match  and  replace the target string.  Only the g, i and x flags are\navailable.  Use the $1 syntax for back references (No \\1 syntax).  Code execution  is\nnot allowed (i.e. no (?{}) or (??{}) constructs).\n\ny/source/dest/ or tr/source/dest/\nTransliterate the characters in the target string.\n"
                }
            ]
        },
        "EXAMPLE OF EXECUTION": {
            "content": "uscan  reads the first entry in debian/changelog to determine the source package name and the\nlast upstream version.\n\nFor example, if the first entry of debian/changelog is:\n\n•   bar (3:2.03+dfsg-4) unstable; urgency=low\n\nthen, the source package name is bar and the last Debian package version is 3:2.03+dfsg-4.\n\nThe last upstream version is normalized to 2.03+dfsg by removing the  epoch  and  the  Debian\nrevision.\n\nIf  the  dversionmangle  rule  exists,  the  last  upstream  version is further normalized by\napplying this rule to it.  For example, if the last upstream version is 2.03+dfsg  indicating\nthe  source  tarball  is  repackaged,  the suffix +dfsg is removed by the string substitution\ns/\\+dfsg\\d*$// to make the (dversionmangled) last upstream version 2.03 and it is compared to\nthe candidate upstream tarball versions such as 2.03, 2.04, ... found  in  the  remote  site.\nThus, set this rule as:\n\n•   opts=\"dversionmangle=s/\\+dfsg\\d*$//\"\n\nuscan downloads a web page from http://URL specified in debian/watch.\n\n•   If the directory name part of URL has no parentheses, ( and ), it is taken as verbatim.\n\n•   If  the  directory  name  part  of  URL  has parentheses, ( and ), then uscan recursively\nsearches all possible directories to  find  a  page  for  the  newest  version.   If  the\ndirversionmangle  rule  exists,  the  generated  sorting index is used to find the newest\nversion.  If a specific version is specified  for  the  download,  the  matching  version\nstring has priority over the newest version.\n\nFor example, this http://URL may be specified as:\n\n•   http://www.example.org/@ANYVERSION@/\n\nPlease note the trailing / in the above to make @ANYVERSION@ as the directory.\n\nIf  the  pagemangle  rule  exists, the whole downloaded web page as a string is normalized by\napplying this rule to it.  This is very powerful tool and needs to be used with caution.   If\nother mangling rules can be used to address your objective, do not use this rule.\n\nThe  downloaded  web  page is scanned for hrefs defined in the <a href=\" ... \"> tag to locate\nthe candidate upstream tarball hrefs.  These candidate upstream tarball hrefs are matched  by\nthe  Perl  regex pattern matching-pattern such as DL-(?:[\\d\\.]+?)/foo-(.+)\\.tar\\.gz to narrow\ndown the candidates.  This pattern match needs to be anchored at the beginning and  the  end.\nFor example, candidate hrefs may be:\n\n•   DL-2.02/foo-2.02.tar.gz\n\n•   DL-2.03/foo-2.03.tar.gz\n\n•   DL-2.04/foo-2.04.tar.gz\n\nHere  the matching string of (.+) in matching-pattern is considered as the candidate upstream\nversion.  If there are multiple matching strings of capturing patterns  in  matching-pattern,\nthey are all concatenated with .  (period) to form the candidate upstream version.  Make sure\nto  use  the  non-capturing regex such as (?:[\\d\\.]+?) instead for the variable text matching\npart unrelated to the version.\n\nThen, the candidate upstream versions are:\n\n•   2.02\n\n•   2.03\n\n•   2.04\n\nThe downloaded tarball filename is basically set to the same as the filename  in  the  remote\nURL of the selected href.\n\nIf the uversionmangle rule exists, the candidate upstream versions are normalized by applying\nthis  rule  to  them.  (This  rule  may be useful if the upstream version scheme doesn't sort\ncorrectly to identify the newest version.)\n\nThe upstream tarball href corresponding to the newest  (uversionmangled)  candidate  upstream\nversion newer than the (dversionmangled) last upstream version is selected.\n\nIf  multiple  upstream  tarball  hrefs  corresponding  to  a  single  version  with different\nextensions exist, the highest compression one is  chosen.  (Priority:  tar.xz  >  tar.lzma  >\ntar.bz2 > tar.gz.)\n\nIf  the  selected  upstream tarball href is the relative URL, it is converted to the absolute\nURL using the base URL of the web page.  If the <base href=\"  ...  \"> tag exists in  the  web\npage, the selected upstream tarball href is converted to the absolute URL using the specified\nbase URL in the base tag, instead.\n\nIf  the  downloadurlmangle  rule  exists, the selected upstream tarball href is normalized by\napplying this rule to it. (This is useful for some sites with the obfuscated download URL.)\n\nIf the filenamemangle rule exists, the downloaded tarball filename is generated  by  applying\nthis  rule  to  the selected href if matching-pattern can extract the latest upstream version\n<uversion> from the selected href string. Otherwise, generate the upstream  tarball  filename\nfrom  its  full URL string and set the missing <uversion> from the generated upstream tarball\nfilename.\n\nWithout the filenamemangle rule, the default upstream tarball filename is generated by taking\nthe last component of the URL and removing everything after any '?' or '#'.\n\nuscan downloads the selected upstream tarball to the parent ../ directory.  For example,  the\ndownloaded file may be:\n\n•   ../foo-2.04.tar.gz\n\nLet's call this downloaded version 2.04 in the above example generically as <uversion> in the\nfollowing.\n\nIf  the pgpsigurlmangle rule exists, the upstream signature file URL is generated by applying\nthis rule to the (downloadurlmangled) selected upstream tarball href and the  signature  file\nis tried to be downloaded from it.\n\nIf  the  pgpsigurlmangle  rule  doesn't  exist,  uscan  warns  user  if the matching upstream\nsignature file is available from the same URL with their filename being  suffixed  by  the  5\ncommon  suffix  asc,  gpg,  pgp,  sig  and  sign.  (You  can  avoid  this  warning by setting\npgpmode=none.)\n\nIf the signature file is downloaded, the downloaded  upstream  tarball  is  checked  for  its\nauthenticity   against   the   downloaded   signature   file   using   the   armored  keyring\ndebian/upstream/signing-key.asc  (see \"KEYRING FILE EXAMPLES\").   If  its  signature  is  not\nvalid, or not made by one of the listed keys, uscan will report an error.\n\nIf  the oversionmangle rule exists, the source tarball version oversion is generated from the\ndownloaded upstream version uversion by applying this rule. This rule is useful to add suffix\nsuch as +dfsg to the version of all the source packages of the  MUT  package  for  which  the\nrepacksuffix mechanism doesn't work.\n\nuscan invokes mk-origtargz to create the source tarball properly named for the source package\nwith .orig. (or .orig-<component>. for the secondary tarballs) in its filename.\n\ncase A: packaging of the upstream tarball as is\nmk-origtargz  creates  a  symlink  ../bar<oversion>.orig.tar.gz linked to the downloaded\nlocal upstream tarball. Here, bar is the source package name found  in  debian/changelog.\nThe generated symlink may be:\n\n•   ../bar2.04.orig.tar.gz -> foo-2.04.tar.gz (as is)\n\nUsually, there is no need to set up opts=\"dversionmangle= ... \" for this case.\n\ncase B: packaging of the upstream tarball after removing non-DFSG files\nmk-origtargz  checks  the filename glob of the Files-Excluded stanza in the first section\nof debian/copyright, removes matching  files  to  create  a  repacked  upstream  tarball.\nNormally,    the    repacked    upstream    tarball    is    renamed   with   suffix   to\n../bar<oversion><suffix>.orig.tar.gz  using  the  repacksuffix  option  for  the  single\nupstream package.    Here <oversion> is updated to be <oversion><suffix>.\n\nThe  removal  of files is required if files are not DFSG-compliant.  For such case, +dfsg\nis used as suffix.\n\nSo   the   combined    options    are    set    as    opts=\"dversionmangle=s/\\+dfsg\\d*$//\n,repacksuffix=+dfsg\", instead.\n\nFor example, the repacked upstream tarball may be:\n\n•   ../bar2.04+dfsg.orig.tar.gz (repackaged)\n\nuscan  normally invokes \"uupdate --find --upstream-version oversion \" for the version=4 watch\nfile.\n\nPlease note that --find option is used here since  mk-origtargz  has  been  invoked  to  make\n*.orig.tar.gz file already.  uscan picks bar from debian/changelog.\n\nIt  creates  the new upstream source tree under the ../bar-<oversion> directory and Debianize\nit leveraging the last package contents.\n",
            "subsections": []
        },
        "WATCH FILE EXAMPLES": {
            "content": "When writing the watch file, you should rely on the latest upstream source  announcement  web\npage.   You  should not try to second guess the upstream archive structure if possible.  Here\nare the typical debian/watch files.\n\nPlease note that executing uscan with -v or -vv reveals what exactly happens internally.\n\nThe existence and non-existence of a space the before tailing \\ (back slash) are significant.\n\nSome undocumented shorter configuration strings are used in the below EXAMPLES  to  help  you\nwith  typing.   These  are  intentional  ones.   uscan is written to accept such common sense\nabbreviations but don't push the limit.\n",
            "subsections": [
                {
                    "name": "HTTP site (basic)",
                    "content": "Here is an example for the basic single upstream tarball.\n\nversion=4\nhttp://example.com/~user/release/@PACKAGE@.html \\\nfiles/@PACKAGE@@ANYVERSION@@ARCHIVEEXT@\n\nOr without using the substitution strings (not recommended):\nhttp://example.com/~user/release/foo.html \\\nfiles/foo-([\\d\\.]+)\\.tar\\.gz\n\nversion=4\n\nFor the upstream source package foo-2.0.tar.gz, this watch file  downloads  and  creates  the\nDebian orig.tar file foo2.0.orig.tar.gz.\n"
                },
                {
                    "name": "HTTP site (pgpsigurlmangle)",
                    "content": "Here  is an example for the basic single upstream tarball with the matching signature file in\nthe same file path.\n\nversion=4\nopts=\"pgpsigurlmangle=s%$%.asc%\" http://example.com/release/@PACKAGE@.html \\\nfiles/@PACKAGE@@ANYVERSION@@ARCHIVEEXT@\n\nFor  the  upstream  source  package  foo-2.0.tar.gz   and   the   upstream   signature   file\nfoo-2.0.tar.gz.asc,  this  watch  file downloads these files, verifies the authenticity using\nthe  keyring  debian/upstream/signing-key.asc  and   creates   the   Debian   orig.tar   file\nfoo2.0.orig.tar.gz.\n\nHere  is  another  example  for the basic single upstream tarball with the matching signature\nfile on decompressed tarball in the same file path.\n\nversion=4\nopts=\"pgpsigurlmangle=s%@ARCHIVEEXT@$%.asc%,decompress\" \\\nhttp://example.com/release/@PACKAGE@.html \\\nfiles/@PACKAGE@@ANYVERSION@@ARCHIVEEXT@\n\nFor  the  upstream  source  package  foo-2.0.tar.gz   and   the   upstream   signature   file\nfoo-2.0.tar.asc,  this  watch file downloads these files, verifies the authenticity using the\nkeyring   debian/upstream/signing-key.asc   and   creates   the    Debian    orig.tar    file\nfoo2.0.orig.tar.gz.\n"
                },
                {
                    "name": "HTTP site (pgpmode=next/previous)",
                    "content": "Here  is an example for the basic single upstream tarball with the matching signature file in\nthe unrelated file path.\n\nversion=4\nopts=\"pgpmode=next\" http://example.com/release/@PACKAGE@.html \\\nfiles/(?:\\d+)/@PACKAGE@@ANYVERSION@@ARCHIVEEXT@ debian\nopts=\"pgpmode=previous\" http://example.com/release/@PACKAGE@.html \\\nfiles/(?:\\d+)/@PACKAGE@@ANYVERSION@@SIGNATUREEXT@ previous\n\n(?:\\d+) part can be any random value.  The tarball file can have 53, while the signature file\ncan have 33.\n\n([\\d\\.]+) part for the signature file has a strict requirement to match that for the upstream\ntarball specified in the previous line by having previous as version in the watch line.\n"
                },
                {
                    "name": "HTTP site (flexible)",
                    "content": "Here is an example for the  maximum  flexibility  of  upstream  tarball  and  signature  file\nextensions.\n\nversion=4\nopts=\"pgpmode=next\" http://example.com/DL/ \\\nfiles/(?:\\d+)/@PACKAGE@@ANYVERSION@@ARCHIVEEXT@ debian\nopts=\"pgpmode=previous\" http://example.com/DL/ \\\nfiles/(?:\\d+)/@PACKAGE@@ANYVERSION@@SIGNATUREEXT@ \\\nprevious\n"
                },
                {
                    "name": "HTTP site (basic MUT)",
                    "content": "Here is an example for the basic multiple upstream tarballs.\n\nversion=4\nopts=\"pgpsigurlmangle=s%$%.sig%\" \\\nhttp://example.com/release/foo.html \\\nfiles/foo-@ANYVERSION@@ARCHIVEEXT@ debian\nopts=\"pgpsigurlmangle=s%$%.sig%, component=bar\" \\\nhttp://example.com/release/foo.html \\\nfiles/foobar-@ANYVERSION@@ARCHIVEEXT@ same\nopts=\"pgpsigurlmangle=s%$%.sig%, component=baz\" \\\nhttp://example.com/release/foo.html \\\nfiles/foobaz-@ANYVERSION@@ARCHIVEEXT@ same\n\nFor  the  main  upstream  source  package  foo-2.0.tar.gz  and  the secondary upstream source\npackages foobar-2.0.tar.gz and foobaz-2.0.tar.gz which install  under  bar/  and  baz/,  this\nwatch   file   downloads   and   creates   the   Debian  orig.tar  file  foo2.0.orig.tar.gz,\nfoo2.0.orig-bar.tar.gz and  foo2.0.orig-baz.tar.gz.   Also,  these  upstream  tarballs  are\nverified by their signature files.\n"
                },
                {
                    "name": "HTTP site (recursive directory scanning)",
                    "content": "Here  is  an  example  with the recursive directory scanning for the upstream tarball and its\nsignature files released in a directory named after their version.\n\nversion=4\nopts=\"pgpsigurlmangle=s%$%.sig%, dirversionmangle=s/-PRE/~pre/;s/-RC/~rc/\" \\\nhttp://tmrc.mit.edu/mirror/twisted/Twisted/@ANYVERSION@/ \\\nTwisted-@ANYVERSION@@ARCHIVEEXT@\n\nHere, the web site should be accessible at the following URL:\n\nhttp://tmrc.mit.edu/mirror/twisted/Twisted/\n\nHere, dirversionmangle option is used to normalize the sorting order of the directory names.\n"
                },
                {
                    "name": "HTTP site (alternative shorthand)",
                    "content": "For the bare HTTP site where you can directly see archive filenames, the normal watch file:\n\nversion=4\nopts=\"pgpsigurlmangle=s%$%.sig%\" \\\nhttp://www.cpan.org/modules/by-module/Text/ \\\nText-CSVXS-@ANYVERSION@@ARCHIVEEXT@\n\ncan be rewritten in an alternative shorthand form only with a single string covering URL  and\nfilename:\n\nversion=4\nopts=\"pgpsigurlmangle=s%$%.sig%\" \\\nhttp://www.cpan.org/modules/by-module/Text/Text-CSVXS-@ANYVERSION@@ARCHIVEEXT@\n\nIn  version=4,  initial  white spaces are dropped.  Thus, this alternative shorthand form can\nalso be written as:\n\nversion=4\nopts=\"pgpsigurlmangle=s%$%.sig%\" \\\nhttp://www.cpan.org/modules/by-module/Text/\\\nText-CSVXS-@ANYVERSION@@ARCHIVEEXT@\n\nPlease note the subtle difference of a space before the tailing \\ between the first  and  the\nlast examples.\n"
                },
                {
                    "name": "HTTP site (funny version)",
                    "content": "For  a  site  which has funny version numbers, the parenthesized groups will be joined with .\n(period) to make a sanitized version number.\n\nversion=4\nhttp://www.site.com/pub/foobar/foobarv(\\d+)(\\d+)@ARCHIVEEXT@\n"
                },
                {
                    "name": "HTTP site (DFSG)",
                    "content": "The upstream part of the Debian version number can be mangled to indicate the source  package\nwas repackaged to clean up non-DFSG files:\n\nversion=4\nopts=\"dversionmangle=s/\\+dfsg\\d*$//,repacksuffix=+dfsg\" \\\nhttp://some.site.org/some/path/foobar-@ANYVERSION@@ARCHIVEEXT@\n\nSee \"COPYRIGHT FILE EXAMPLES\".\n"
                },
                {
                    "name": "HTTP site (filenamemangle)",
                    "content": "The  upstream  tarball filename is found by taking the last component of the URL and removing\neverything after any '?' or '#'.\n\nIf   this   does   not   fit   to    you,    use    filenamemangle.     For    example,    <A\nhref=\"http://foo.bar.org/dl/?path=&dl=foo-0.1.1.tar.gz\"> could be handled as:\n\nversion=4\nopts=filenamemangle=s/.*=(.*)/$1/ \\\nhttp://foo.bar.org/dl/\\?path=&dl=foo-@ANYVERSION@@ARCHIVEEXT@\n\n<A href=\"http://foo.bar.org/dl/?path=&dlversion=0.1.1\"> could be handled as:\n\nversion=4\nopts=filenamemangle=s/.*=(.*)/foo-$1\\.tar\\.gz/ \\\nhttp://foo.bar.org/dl/\\?path=&dlversion=@ANYVERSION@\n\nIf  the  href  string  has no version using <I>matching-pattern>, the version can be obtained\nfrom the full URL using filenamemangle.\n\nversion=4\nopts=filenamemangle=s&.*/dl/(.*)/foo\\.tar\\.gz&foo-$1\\.tar\\.gz& \\\nhttp://foo.bar.org/dl/@ANYVERSION@/ foo.tar.gz\n"
                },
                {
                    "name": "HTTP site (downloadurlmangle)",
                    "content": "The option downloadurlmangle can be used to mangle the URL of the file to download.  This can\nonly be used with http:// URLs.  This may be necessary if the link  given  on  the  web  page\nneeds to be transformed in some way into one which will work automatically, for example:\n\nversion=4\nopts=downloadurlmangle=s/prdownload/download/ \\\nhttp://developer.berlios.de/project/showfiles.php?groupid=2051 \\\nhttp://prdownload.berlios.de/softdevice/vdr-softdevice-@ANYVERSION@@ARCHIVEEXT@\n"
                },
                {
                    "name": "HTTP site (oversionmangle, MUT)",
                    "content": "The  option  oversionmangle  can  be  used  to  mangle  the  version  of  the  source tarball\n(.orig.tar.gz and .orig-bar.tar.gz).  For example, +dfsg can be added to the upstream version\nas:\n\nversion=4\nopts=oversionmangle=s/(.*)/$1+dfsg/ \\\nhttp://example.com/~user/release/foo.html \\\nfiles/foo-@ANYVERSION@@ARCHIVEEXT@ debian\nopts=\"component=bar\" \\\nhttp://example.com/~user/release/foo.html \\\nfiles/bar-@ANYVERSION@@ARCHIVEEXT@ same\n\nSee \"COPYRIGHT FILE EXAMPLES\".\n"
                },
                {
                    "name": "HTTP site (pagemangle)",
                    "content": "The option pagemangle can be used to mangle the downloaded web  page  before  applying  other\nrules.   The  non-standard  web  page  without  proper  <a href=\" << ... >> \"> entries can be\nconverted.  For example, if foo.html uses <a bogus=\" ... \">, this can  be  converted  to  the\nstandard page format with:\n\nversion=4\nopts=pagemangle=\"s/<a\\s+bogus=/<a href=/g\" \\\nhttp://example.com/release/foo.html \\\nfiles/@PACKAGE@@ANYVERSION@@ARCHIVEEXT@\n\nPlease note the use of g here to replace all occurrences.\n\nIf foo.html uses <Key> ... </Key>, this can be converted to the standard page format with:\n\nversion=4\nopts=\"pagemangle=s%<Key>([^<]*)</Key>%<Key><a href=\"$1\">$1</a></Key>%g\" \\\nhttp://example.com/release/foo.html \\\n(?:.*)/@PACKAGE@@ANYVERSION@@ARCHIVEEXT@\n"
                },
                {
                    "name": "FTP site (basic):",
                    "content": "version=4\nftp://ftp.tex.ac.uk/tex-archive/web/ccpp/cweb/cweb-@ANYVERSION@@ARCHIVEEXT@\n"
                },
                {
                    "name": "FTP site (regex special characters):",
                    "content": "version=4\nftp://ftp.worldforge.org/pub/worldforge/libs/\\\nAtlas-C++/transitional/Atlas-C\\+\\+-@ANYVERSION@@ARCHIVEEXT@\n\nPlease  note  that  this URL is connected to be  ... libs/Atlas-C++/ ...  . For ++, the first\none in the directory path is verbatim while the one in the filename is escaped by \\.\n"
                },
                {
                    "name": "FTP site (funny version)",
                    "content": "This is another way of handling site with funny version numbers, this  time  using  mangling.\n(Note  that  multiple  groups  will  be  concatenated  before mangling is performed, and that\nmangling will only be performed  on  the  basename  version  number,  not  any  path  version\nnumbers.)\n\nversion=4\nopts=\"uversionmangle=s/^/0.0./\" \\\nftp://ftp.ibiblio.org/pub/Linux/ALPHA/wine/\\\ndevelopment/Wine-@ANYVERSION@@ARCHIVEEXT@\n"
                },
                {
                    "name": "sf.net",
                    "content": "For  SourceForge  based projects, qa.debian.org runs a redirector which allows a simpler form\nof URL. The format below will automatically be rewritten to use the redirector with the watch\nfile:\n\nversion=4\nhttps://sf.net/<project>/ <tar-name>-@ANYVERSION@@ARCHIVEEXT@\n\nFor audacity, set the watch file as:\n\nversion=4\nhttps://sf.net/audacity/ audacity-minsrc-@ANYVERSION@@ARCHIVEEXT@\n\nPlease note, you can still use normal functionalities of uscan to set up  a  watch  file  for\nthis site without using the redirector.\n\nversion=4\nopts=\"uversionmangle=s/-pre/~pre/, \\\nfilenamemangle=s%(?:.*)audacity-minsrc-(.+)\\.tar\\.xz/download%\\\naudacity-$1.tar.xz%\" \\\nhttp://sourceforge.net/projects/audacity/files/audacity/@ANYVERSION@/ \\\n(?:.*)audacity-minsrc-@ANYVERSION@@ARCHIVEEXT@/download\n\nHere, % is used as the separator instead of the standard /.\n"
                },
                {
                    "name": "github.com",
                    "content": "For  GitHub  based projects, you can use the releases or tags API page.  If upstream releases\nproperly named tarballs on their releases page, you can search for the browser  download  URL\n(API key browserdownloadurl):\n\nversion=4\nopts=\"searchmode=plain\" \\\nhttps://api.github.com/repos/<user>/<project>/releases?perpage=100 \\\nhttps://github.com/<user>/<project>/releases/download/[^/]+/@PACKAGE@-@ANYVERSION@@ARCHIVEEXT@\n\nIf  the  release page only contains the auto-generated tar.gz source code tarball, search for\nthe tarball URL (API key tarballurl). The tarball URL uses only the version as the filename.\nYou can rename the downloaded upstream tarball into the  standard  <project>-<version>.tar.gz\nusing filenamemangle:\n\nversion=4\nopts=\"filenamemangle=s%.*/@ANYVERSION@%@PACKAGE@-$1.tar.gz%,searchmode=plain\" \\\nhttps://api.github.com/repos/<user>/<project>/releases?perpage=100 \\\nhttps://api.github.com/repos/<user>/<project>/tarball/@ANYVERSION@\n\nIf there are no upstream releases, you can query the equivalent tags page:\n\nversion=4\nopts=\"filenamemangle=s%.*/@ANYVERSION@%@PACKAGE@-$1.tar.gz%,searchmode=plain\" \\\nhttps://api.github.com/repos/<user>/<project>/tags?perpage=100 \\\nhttps://api.github.com/repos/<user>/<project>/tarball/refs/tags/@ANYVERSION@\n\nIf  upstream  releases  alpha/beta  tarballs, you will need to make use of the uversionmangle\noption: uversionmangle=s/(a|alpha|b|beta|c|dev|pre|rc)/~$1/\n"
                },
                {
                    "name": "PyPI",
                    "content": "For PyPI based projects, pypi.debian.net runs a redirector which allows  a  simpler  form  of\nURL.  The  format  below will automatically be rewritten to use the redirector with the watch\nfile:\n\nversion=4\nhttps://pypi.python.org/packages/source/<initial>/<project>/ \\\n<tar-name>-@ANYVERSION@@ARCHIVEEXT@\n\nFor cfn-sphere, set the watch file as:\n\nversion=4\nhttps://pypi.python.org/packages/source/c/cfn-sphere/ \\\ncfn-sphere-@ANYVERSION@@ARCHIVEEXT@\n\nPlease note, you can still use normal functionalities of uscan to set up  a  watch  file  for\nthis site without using the redirector.\n\nversion=4\nopts=\"pgpmode=none\" \\\nhttps://pypi.python.org/pypi/cfn-sphere/ \\\nhttps://pypi.python.org/packages/.*/.*/.*/\\\ncfn-sphere-@ANYVERSION@@ARCHIVEEXT@#.*\n"
                },
                {
                    "name": "code.google.com",
                    "content": "Sites  which  used  to be hosted on the Google Code service should have migrated to elsewhere\n(github?).  Please look for the newer upstream site if available.\n"
                },
                {
                    "name": "npmjs.org (node modules)",
                    "content": "npmjs.org modules are published in JSON files. Here is a way to read them:\n\nversion=4\nopts=\"searchmode=plain\" \\\nhttps://registry.npmjs.org/aes-js \\\nhttps://registry.npmjs.org/aes-js/-/aes-js-@ANYVERSION@@ARCHIVEEXT@\n"
                },
                {
                    "name": "grouped package",
                    "content": "Some node modules are split into multiple little upstream package. Here is  a  way  to  group\nthem:\n\nversion=4\nopts=\"searchmode=plain,pgpmode=none\" \\\nhttps://registry.npmjs.org/mongodb \\\nhttps://registry.npmjs.org/mongodb/-/mongodb-@ANYVERSION@@ARCHIVEEXT@ group\nopts=\"searchmode=plain,pgpmode=none,component=bson\" \\\nhttps://registry.npmjs.org/bson \\\nhttps://registry.npmjs.org/bson/-/bson-@ANYVERSION@@ARCHIVEEXT@ group\nopts=\"searchmode=plain,pgpmode=none,component=mongodb-core\" \\\nhttps://registry.npmjs.org/mongodb-core \\\nhttps://registry.npmjs.org/mongodb-core/-/mongodb-core-@ANYVERSION@@ARCHIVEEXT@ group\nopts=\"searchmode=plain,pgpmode=none,component=requireoptional\" \\\nhttps://registry.npmjs.org/requireoptional \\\nhttps://registry.npmjs.org/requireoptional/-/requireoptional-@ANYVERSION@@ARCHIVEEXT@ group\n\nPackage version is then the concatenation of upstream versions separated by \"+~\".\n\nTo  avoid  having  a  too long version, the \"checksum\" method can be used.  In this case, the\nmain source has to be declared as \"group\":\n\nversion=4\nopts=\"searchmode=plain,pgpmode=none\" \\\nhttps://registry.npmjs.org/mongodb \\\nhttps://registry.npmjs.org/mongodb/-/mongodb-@ANYVERSION@@ARCHIVEEXT@ group\nopts=\"searchmode=plain,pgpmode=none,component=bson\" \\\nhttps://registry.npmjs.org/bson \\\nhttps://registry.npmjs.org/bson/-/bson-@ANYVERSION@@ARCHIVEEXT@ checksum\nopts=\"searchmode=plain,pgpmode=none,component=mongodb-core\" \\\nhttps://registry.npmjs.org/mongodb-core \\\nhttps://registry.npmjs.org/mongodb-core/-/mongodb-core-@ANYVERSION@@ARCHIVEEXT@ checksum\nopts=\"searchmode=plain,pgpmode=none,component=requireoptional\" \\\nhttps://registry.npmjs.org/requireoptional \\\nhttps://registry.npmjs.org/requireoptional/-/requireoptional-@ANYVERSION@@ARCHIVEEXT@ checksum\n\nThe \"checksum\" is made up of  the  separate  sum  of  each  number  composing  the  component\nversions.   Following is an example with 3 components whose versions are \"1.2.4\", \"2.0.1\" and\n\"10.0\", with the main tarball having version \"2.0.6\":\n\nMain: 2.0.6\nComp1:         1 .     2 .     4\nComp2:         2 .     0 .     1\nComp3:        10 .     0\n================================\nResult  : 1+2+10 . 2+0+0 .   4+1\nChecksum:     13 .     2 .     5\n================================\nFinal Version:   2.0.6+~cs13.2.5\n\nuscan will also display the original version string before being encoded into  the  checksum,\nwhich can for example be used in a debian/changelog entry to easily follow the changes:\n\n2.0.6+~1.2.4+~2.0.1+~10.0\n\nNote: This feature currently accepts only versions composed of digits and full stops (`.`).\n"
                },
                {
                    "name": "direct access to the git repository (tags)",
                    "content": "If  the  upstream  only  publishes  its  code  via the git repository and its code has no web\ninterface to obtain the release tarball,  you  can  use  uscan  with  the  tags  of  the  git\nrepository to track and package the new upstream release.\n\nversion=4\nopts=\"mode=git, gitmode=full, pgpmode=none\" \\\nhttp://git.ao2.it/tweeper.git \\\nrefs/tags/v@ANYVERSION@\n\nPlease note \"git ls-remote\" is used to obtain references for tags.\n\nIf a tag v20.5 is the newest tag, the above example downloads spkg-20.5.tar.xz after making a\nfull clone of the git repository which is needed for dumb git server.\n\nIf tags are signed, set pgpmode=gittag to verify them.\n"
                },
                {
                    "name": "direct access to the git repository (HEAD)",
                    "content": "If  the  upstream  only  publishes  its  code  via the git repository and its code has no web\ninterface nor the tags to obtain the released tarball, you can use uscan with the HEAD of the\ngit repository to track and package the new upstream release with an automatically  generated\nversion string.\n\nversion=4\nopts=\"mode=git, pgpmode=none\" \\\nhttps://github.com/Debian/dh-make-golang \\\nHEAD\n\nPlease  note  that  a local shallow copy of the git repository is made with \"git clone --bare\n--depth=1 ...\" normally in the target directory.  uscan generates the  new  upstream  version\nwith  \"git  log --date=format:%Y%m%d --pretty=0.0~git%cd.%h\" on this local copy of repository\nas its default behavior.\n\nThe generation of the upstream version string may the adjusted to your taste by adding pretty\nand date options to the opts arguments.\n"
                },
                {
                    "name": "direct access to the Subversion repository (tags)",
                    "content": "If the upstream only publishes its code via the Subversion repository and its code has no web\ninterface to obtain the release tarball, you can use uscan with the tags  of  the  Subversion\nrepository to track and package the new upstream release.\n\nversion=4\nopts=\"mode=svn, pgpmode=none\" \\\nsvn://svn.code.sf.net/p/jmol/code/tags/ \\\n@ANYVERSION@\\/\n"
                },
                {
                    "name": "direct access to the Subversion repository (HEAD)",
                    "content": "If the upstream only publishes its code via the Subversion repository and its code has no web\ninterface to obtain the release tarball, you can use uscan to get the most recent source of a\nsubtree in the repository with an automatically generated version string.\n\nversion=4\nopts=\"mode=svn, pgpmode=none\" \\\nsvn://svn.code.sf.net/p/jmol/code/trunk/ \\\nHEAD\n\nBy  default,  uscan  generates  the  new upstream version by appending the revision number to\n\"0.0~svn\". This can later be changed using uversionmangle.\n"
                }
            ]
        },
        "COPYRIGHT FILE EXAMPLES": {
            "content": "Here is an example for the debian/copyright file which initiates automatic repackaging of the\nupstream tarball into <spkg><oversion>.orig.tar.gz (In debian/copyright, the  Files-Excluded\nand  Files-Excluded-component  stanzas are a part of the first paragraph and there is a blank\nline before the following paragraphs which contain Files and other stanzas.):\n\nFormat: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/\nFiles-Excluded: exclude-this\nexclude-dir\n*/exclude-dir\n.*\n*/js/jquery.js\n\nFiles: *\nCopyright: ...\n...\n\nHere is another example for the debian/copyright file which initiates  automatic  repackaging\nof    the    multiple    upstream    tarballs    into    <spkg><oversion>.orig.tar.gz    and\n<spkg><oversion>.orig-bar.tar.gz:\n\nFormat: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/\nFiles-Excluded: exclude-this\nexclude-dir\n*/exclude-dir\n.*\n*/js/jquery.js\nFiles-Excluded-bar: exclude-this\nexclude-dir\n*/exclude-dir\n.*\n*/js/jquery.js\n\nFiles: *\nCopyright: ...\n...\n\nSee mk-origtargz(1).\n",
            "subsections": []
        },
        "KEYRING FILE EXAMPLES": {
            "content": "Let's assume that the upstream \"uscan test  key  (no  secret)  <none@debian.org>\"  signs  its\npackage  with  a secret OpenPGP key and publishes the corresponding public OpenPGP key.  This\npublic OpenPGP key can be identified in 3 ways using the hexadecimal form.\n\n•   The fingerprint as the 20 byte data calculated from the public OpenPGP key. E.  g., 'CF21\n8F0E 7EAB F584 B7E2 0402 C77E 2D68 7254 3FAF'\n\n•   The long keyid as the last 8 byte data of the fingerprint. E. g., 'C77E2D6872543FAF'\n\n•   The short keyid is the last 4 byte data of the fingerprint. E. g., '72543FAF'\n\nConsidering the existence of the collision attack on the short keyid, the  use  of  the  long\nkeyid  is  recommended  for  receiving keys from the public key servers.  You must verify the\ndownloaded OpenPGP key using its full fingerprint value which you know is the trusted one.\n\nThe armored keyring file debian/upstream/signing-key.asc can be created by using the gpg  (or\ngpg2) command as follows.\n\n$ gpg --recv-keys \"C77E2D6872543FAF\"\n...\n$ gpg --finger \"C77E2D6872543FAF\"\npub   4096R/72543FAF 2015-09-02\nKey fingerprint = CF21 8F0E 7EAB F584 B7E2  0402 C77E 2D68 7254 3FAF\nuid                  uscan test key (no secret) <none@debian.org>\nsub   4096R/52C6ED39 2015-09-02\n$ cd path/to/<upkg>-<uversion>\n$ mkdir -p debian/upstream\n$ gpg --export --export-options export-minimal --armor \\\n'CF21 8F0E 7EAB F584 B7E2  0402 C77E 2D68 7254 3FAF' \\\n>debian/upstream/signing-key.asc\n\nThe        binary        keyring       files,       debian/upstream/signing-key.pgp       and\ndebian/upstream-signing-key.pgp, are still supported but deprecated.\n\nIf a group of developers sign the package, you need to list fingerprints of all  of  them  in\nthe argument for gpg --export ... to make the keyring to contain all OpenPGP keys of them.\n\nSometimes  you  may  wonder  who made a signature file.  You can get the public keyid used to\ncreate the detached signature file foo-2.0.tar.gz.asc by running gpg as:\n\n$ gpg -vv foo-2.0.tar.gz.asc\ngpg: armor: BEGIN PGP SIGNATURE\ngpg: armor header: Version: GnuPG v1\n:signature packet: algo 1, keyid C77E2D6872543FAF\nversion 4, created 1445177469, md5len 0, sigclass 0x00\ndigest algo 2, begin of digest 7a c7\nhashed subpkt 2 len 4 (sig created 2015-10-18)\nsubpkt 16 len 8 (issuer key ID C77E2D6872543FAF)\ndata: [4091 bits]\ngpg: assuming signed data in `foo-2.0.tar.gz'\ngpg: Signature made Sun 18 Oct 2015 11:11:09 PM JST using RSA key ID 72543FAF\n...\n",
            "subsections": []
        },
        "COMMANDLINE OPTIONS": {
            "content": "For the basic usage, uscan does not require to set these options.\n\n--conffile, --conf-file\nAdd or replace default configuration files (\"/etc/devscripts.conf\" and  \"~/.devscripts\").\nThis can only be used as the first option given on the command-line.\n\nreplace:\nuscan --conf-file test.conf --verbose\n\nadd:\nuscan --conf-file +test.conf --verbose\n\nIf one --conf-file has no \"+\", default configuration files are ignored.\n\n--no-conf, --noconf\nDon't  read  any  configuration files. This can only be used as the first option given on\nthe command-line.\n",
            "subsections": [
                {
                    "name": "--no-verbose",
                    "content": "Don't report verbose information. (default)\n\n--verbose, -v\nReport verbose information.\n\n--debug, -vv\nReport verbose information and some internal state values.\n\n--extra-debug, -vvv\nReport verbose information including the downloaded web pages as processed to STDERR  for\ndebugging.\n",
                    "long": "--no-verbose"
                },
                {
                    "name": "--dehs",
                    "content": "Send DEHS style output (XML-type) to STDOUT, while send all other uscan output to STDERR.\n",
                    "long": "--dehs"
                },
                {
                    "name": "--no-dehs",
                    "content": "Use only traditional uscan output format. (default)\n\n--download, -d\nDownload the new upstream release. (default)\n\n--force-download, -dd\nDownload the new upstream release even if up-to-date. (may not overwrite the local file)\n\n--overwrite-download, -ddd\nDownload the new upstream release even if up-to-date. (may overwrite the local file)\n\n--no-download, --nodownload\nDon't download and report information.\n\nPreviously downloaded tarballs may be used.\n\nChange default to --skip-signature.\n",
                    "long": "--no-dehs"
                },
                {
                    "name": "--signature",
                    "content": "Download signature. (default)\n",
                    "long": "--signature"
                },
                {
                    "name": "--no-signature",
                    "content": "Don't download signature but verify if already downloaded.\n",
                    "long": "--no-signature"
                },
                {
                    "name": "--skip-signature",
                    "content": "Don't bother download signature nor verifying signature.\n\n--safe, --report\nAvoid running unsafe scripts by skipping both the repacking of the downloaded package and\nthe updating of the new source tree.\n\nChange default to --no-download and --skip-signature.\n\nWhen  the  objective  of running uscan is to gather the upstream package status under the\nsecurity conscious environment, please make sure to use this option.\n",
                    "long": "--skip-signature"
                },
                {
                    "name": "--report-status",
                    "content": "This is equivalent of setting \"--verbose --safe\".\n\n--download-version version\nSpecify the version which the upstream release must match  in  order  to  be  considered,\nrather than using the release with the highest version.  (a best effort feature)\n\n--download-debversion version\nSpecify  the  Debian  package  version  to  download  the  corresponding upstream release\nversion.  The dversionmangle and uversionmangle rules are  considered.   (a  best  effort\nfeature)\n",
                    "long": "--report-status"
                },
                {
                    "name": "--download-current-version",
                    "content": "Download the currently packaged version.  (a best effort feature)\n\n--check-dirname-level N\nSee the below section \"Directory name checking\" for an explanation of this option.\n\n--check-dirname-regex regex\nSee the below section \"Directory name checking\" for an explanation of this option.\n\n--destdir path Normally, uscan changes its internal current directory to the package's source\ndirectory where the debian/ is located.  Then the destination directory for the downloaded\ntarball and other files is set to the parent directory ../ from this internal current\ndirectory.\nThis  default  destination  directory  can be overridden by setting --destdir option to a\nparticular path.  If  this  path  is  a  relative  path,  the  destination  directory  is\ndetermined in relative to the internal current directory of uscan execution. If this path\nis a absolute path, the destination directory is set to path irrespective of the internal\ncurrent directory of uscan execution.\n\nThe  above  is  true not only for the simple uscan run in the single source tree but also\nfor the advanced scanning uscan run with subdirectories holding multiple source trees.\n\nOne exception is when --watchfile and --package are used together.  For  this  case,  the\ninternal  current  directory of uscan execution and the default destination directory are\nset to the current directory . where uscan is started.  The default destination directory\ncan be overridden by setting --destdir option as well.\n\n--package package\nSpecify the name of the package to check for rather than examining debian/changelog; this\nrequires the --upstream-version (unless a version is specified in  the  watch  file)  and\n--watchfile options as well.  Furthermore, no directory scanning will be done and nothing\nwill  be  downloaded.  This option automatically sets --no-download and --skip-signature;\nand probably most useful in conjunction with the DEHS system (and --dehs).\n\n--upstream-version upstream-version\nSpecify the current upstream version rather than examine debian/watch or debian/changelog\nto determine it. This is ignored if a directory scan is being performed and more than one\ndebian/watch file is found.\n\n--watchfile watchfile\nSpecify the watchfile rather than perform a directory scan  to  determine  it.   If  this\noption  is  used  without  --package,  then  uscan  must be called from within the Debian\npackage source tree (so that debian/changelog can be found simply by stepping up  through\nthe tree).\n\nOne  exception  is when --watchfile and --package are used together.  uscan can be called\nfrom anywhare and the internal current directory  of  uscan  execution  and  the  default\ndestination directory are set to the current directory . where uscan is started.\n\nSee more in the --destdir explanation.\n",
                    "long": "--download-current-version"
                },
                {
                    "name": "--bare",
                    "content": "Disable all site specific special case codes to perform URL redirections and page content\nalterations.\n",
                    "long": "--bare"
                },
                {
                    "name": "--http-header",
                    "content": "Add specified header in HTTP requests for matching url. This option can be used more than\none time, values must be in the form \"baseUrl@Name=value. Example:\n\nuscan --http-header https://example.org@My-Token=qwertyuiop\n\nSecurity:\n\nThe given baseUrl must exactly match the base url before '/'. Examples:\n|        --http-header value         |           Good for          | Never used |\n+------------------------------------+-----------------------------+------------+\n| https://example.org.com@Hdr=Value  | https://example.org.com/... |            |\n| https://example.org.com/@Hdr=Value |                             |     X      |\n| https://e.com:1879@Hdr=Value       | https://e.com:1879/...      |            |\n| https://e.com:1879/dir@Hdr=Value   | https://e.com:1879/dir/...  |            |\n| https://e.com:1879/dir/@Hdr=Value  |                             |     X      |\n\nIt is strongly recommended to not use this feature to pass a secret token over unciphered\nconnection (http://)\nYou can use \"USCANHTTPHEADER\" variable (in \"~/.devscripts\") to hide secret token from\nscripts",
                    "long": "--http-header"
                },
                {
                    "name": "--no-exclusion",
                    "content": "Don't automatically exclude files mentioned in debian/copyright field Files-Excluded.\n",
                    "long": "--no-exclusion"
                },
                {
                    "name": "--pasv",
                    "content": "Force PASV mode for FTP connections.\n",
                    "long": "--pasv"
                },
                {
                    "name": "--no-pasv",
                    "content": "Don't use PASV mode for FTP connections.\n",
                    "long": "--no-pasv"
                },
                {
                    "name": "--no-symlink",
                    "content": "Don't rename nor repack upstream tarball.\n\n--timeout N\nSet timeout to N seconds (default 20 seconds).\n\n--user-agent, --useragent\nOverride the default user agent header.\n",
                    "long": "--no-symlink"
                },
                {
                    "name": "--help",
                    "content": "Give brief usage information.\n",
                    "long": "--help"
                },
                {
                    "name": "--version",
                    "content": "Display version information.\n\nuscan also accepts following options and passes them to mk-origtargz:\n",
                    "long": "--version"
                },
                {
                    "name": "--symlink",
                    "content": "Make  orig.tar.gz (with the appropriate extension) symlink to the downloaded files. (This\nis the default behavior.)\n",
                    "long": "--symlink"
                },
                {
                    "name": "--copy",
                    "content": "Instead of symlinking as described above, copy the downloaded files.\n",
                    "long": "--copy"
                },
                {
                    "name": "--rename",
                    "content": "Instead of symlinking as described above, rename the downloaded files.\n",
                    "long": "--rename"
                },
                {
                    "name": "--repack",
                    "content": "After having downloaded an lzma tar, xz tar, bzip  tar,  gz  tar,  zip,  jar,  xpi,  zstd\narchive, repack it to the specified compression (see --compression).\n\nThe  unzip  package  must be installed in order to repack zip, jar, and xpi archives, the\nxz-utils package must be installed to repack lzma or xz tar archives, and  zstd  must  be\ninstalled to repack zstd archives.\n\n--compression [ gzip | bzip2 | lzma | xz ]\nIn  the  case  where the upstream sources are repacked (either because --repack option is\ngiven or debian/copyright contains the field Files-Excluded), it is possible  to  control\nthe  compression  method via the parameter.  The default is gzip for normal tarballs, and\nxz for tarballs generated directly from the git repository.\n\n--copyright-file copyright-file\nExclude files mentioned in Files-Excluded in the given copyright-file.   This  is  useful\nwhen running uscan not within a source package directory.\n",
                    "long": "--repack"
                }
            ]
        },
        "DEVSCRIPT CONFIGURATION VARIABLES": {
            "content": "For the basic usage, uscan does not require to set these configuration variables.\n\nThe  two configuration files /etc/devscripts.conf and ~/.devscripts are sourced by a shell in\nthat order to set configuration variables. These may be overridden by command  line  options.\nEnvironment  variable settings are ignored for this purpose. If the first command line option\ngiven is --noconf, then these files will not be read. The currently recognized variables are:\n\nUSCANDOWNLOAD\nDownload or report only:\n\nno: equivalent to --no-download, newer upstream files will not be downloaded.\nyes: equivalent to --download, newer upstream files will be downloaded. This is the\ndefault behavior.\nSee also --force-download and --overwrite-download.\n\nUSCANSAFE\nIf this is set to yes, then uscan avoids running unsafe  scripts  by  skipping  both  the\nrepacking  of  the  downloaded  package  and the updating of the new source tree; this is\nequivalent to the --safe options;  this  also  sets  the  default  to  --no-download  and\n--skip-signature.\n\nUSCANPASV\nIf  this is set to yes or no, this will force FTP connections to use PASV mode or not to,\nrespectively. If this is set to default, then Net::FTP(3)  makes  the  choice  (primarily\nbased on the FTPPASSIVE environment variable).\n\nUSCANTIMEOUT\nIf  set  to  a  number  N,  then  set the timeout to N seconds. This is equivalent to the\n--timeout option.\n\nUSCANSYMLINK\nIf this is set to no, then a pkgversion.orig.tar.{gz|bz2|lzma|xz} symlink  will  not  be\nmade  (equivalent  to  the --no-symlink option). If it is set to yes or symlink, then the\nsymlinks will be made. If it is set to rename, then the files are renamed (equivalent  to\nthe --rename option).\n\nUSCANDEHSOUTPUT\nIf  this  is  set  to yes, then DEHS-style output will be used. This is equivalent to the\n--dehs option.\n\nUSCANVERBOSE\nIf this is set to yes, then verbose output will be given.   This  is  equivalent  to  the\n--verbose option.\n\nUSCANUSERAGENT\nIf  set,  the  specified user agent string will be used in place of the default.  This is\nequivalent to the --user-agent option.\n\nUSCANDESTDIR\nIf set, the downloaded files will be placed in this  directory.  This  is  equivalent  to\nthe --destdir option.\n\nUSCANREPACK\nIf  this is set to yes, then after having downloaded a bzip tar, lzma tar, xz tar, zip or\nzstd archive, uscan will repack it to the specified compression (see --compression). This\nis equivalent to the --repack option.\n\nUSCANEXCLUSION\nIf this is set to no, files mentioned in the  field  Files-Excluded  of  debian/copyright\nwill  be  ignored  and  no  exclusion  of files will be tried.  This is equivalent to the\n--no-exclusion option.\n\nUSCANHTTPHEADER\nIf set, the specified http header will be used  if  URL  match.  This  is  equivalent  to\n--http-header option.\n",
            "subsections": []
        },
        "EXIT STATUS": {
            "content": "The  exit  status  gives  some indication of whether a newer version was found or not; one is\nadvised to read the output to determine exactly what happened  and  whether  there  were  any\nwarnings to be noted.\n\n0   Either  --help  or --version was used, or for some watch file which was examined, a newer\nupstream version was located.\n\n1   No newer upstream versions were located for any of the watch files examined.\n",
            "subsections": []
        },
        "ADVANCED FEATURES": {
            "content": "uscan has many other enhanced features which  are  skipped  in  the  above  section  for  the\nsimplicity.  Let's check their highlights.\n\nuscan  can  be  executed with path as its argument to change the starting directory of search\nfrom the current directory to path .\n\nIf you are not sure what exactly is happening behind the scene, please enable  the  --verbose\noption.   If  this  is  not  enough,  enable  the  --debug  option  too  see all the internal\nactivities.\n\nSee \"COMMANDLINE OPTIONS\" and \"DEVSCRIPT CONFIGURATION VARIABLES\" for other variations.\n",
            "subsections": [
                {
                    "name": "Custom script",
                    "content": "The optional script parameter in debian/watch means to  execute  script  with  options  after\nprocessing this line if specified.\n\nSee \"HISTORY AND UPGRADING\" for how uscan invokes the custom script.\n\nFor  compatibility  with  other  tools such as git-buildpackage, it may not be wise to create\ncustom scripts with random behavior.  In general, uupdate is the best  choice  for  the  non-\nnative package and custom scripts, if created, should behave as if uupdate.  For possible use\ncase, see <http://bugs.debian.org/748474> as an example.\n"
                },
                {
                    "name": "URL diversion",
                    "content": "Some  popular  web sites changed their web page structure causing maintenance problems to the\nwatch file.  There are some redirection services created to ease  maintenance  of  the  watch\nfile.   Currently,  uscan  makes automatic diversion of URL requests to the following URLs to\ncope with this situation.\n\n•   <http://sf.net>\n\n•   <http://pypi.python.org>\n"
                },
                {
                    "name": "Directory name checking",
                    "content": "Similarly to several other scripts in the devscripts package, uscan  explores  the  requested\ndirectory  trees  looking for debian/changelog and debian/watch files. As a safeguard against\nstray files causing potential problems, and in order to promote efficiency, it  will  examine\nthe  name of the parent directory once it finds the debian/changelog file, and check that the\ndirectory name corresponds to the package name.  It  will  only  attempt  to  download  newer\nversions  of  the package and then perform any requested action if the directory name matches\nthe package name. Precisely how  it  does  this  is  controlled  by  two  configuration  file\nvariables   DEVSCRIPTSCHECKDIRNAMELEVEL   and  DEVSCRIPTSCHECKDIRNAMEREGEX,  and  their\ncorresponding command-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\ndebian/changelog, that is, the directory containing debian/changelog is not the directory\nfrom which uscan was invoked.  This is the default behavior.\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\nDEVSCRIPTSCHECKDIRNAMEREGEX or by the command  line  option  --check-dirname-regex  regex.\nHere  regex  is a Perl regex (see perlre(3perl)), which will be anchored at the beginning and\nthe end. 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\nreplaced by the source package name, as determined from  the  debian/changelog.  The  default\nvalue  for  the  regex  is:  package(-.+)?, thus matching directory names such as package and\npackage-version.\n"
                }
            ]
        },
        "HISTORY AND UPGRADING": {
            "content": "This section briefly describes the backwards-incompatible watch file features which have been\nadded in each watch file version, and the first  version  of  the  devscripts  package  which\nunderstood them.\n\nPre-version 2\nThe  watch  file  syntax was significantly different in those days. Don't use it.  If you\nare upgrading from a pre-version 2 watch file, you are advised to read this  manpage  and\nto start from scratch.\n\nVersion 2\ndevscripts  version  2.6.90:  The  first incarnation of the current style of watch files.\nThis version is also deprecated and will be rejected after the Debian 11 release.\n\nVersion 3\ndevscripts version 2.8.12: Introduced the following: correct handling  of  regex  special\ncharacters  in  the path part, directory/path pattern matching, version number in several\nparts, version number mangling. Later versions have also introduced URL mangling.\n\nIf you are upgrading from version 2, the key incompatibility  is  if  you  have  multiple\ngroups  in  the pattern part; whereas only the first one would be used in version 2, they\nwill all be used in version 3. To avoid  this  behavior,  change  the  non-version-number\ngroups to be (?:  ... ) instead of a plain (  ...  ) group.\n\n•   uscan   invokes   the   custom   script   as   \"script   --upstream-version   version\n../spkgversion.orig.tar.gz\".\n\n•   uscan invokes  the  standard  uupdate  as  \"uupdate  --no-symlink  --upstream-version\nversion ../spkgversion.orig.tar.gz\".\n\nVersion 4\ndevscripts  version  2.15.10:  The  first  incarnation of watch files supporting multiple\nupstream tarballs.\n\nThe syntax of the watch file is relaxed to allow more spaces for readability.\n\nIf you have a custom script in place of uupdate, you may also encounter problems updating\nfrom Version 3.\n\n•   uscan invokes the custom script as \"script --upstream-version version\".\n\n•   uscan invokes the standard uupdate as \"uupdate --find --upstream-version version\".\n\nRestriction for --dehs is lifted by  redirecting  other  output  to  STDERR  when  it  is\nactivated.\n",
            "subsections": []
        },
        "SEE ALSO": {
            "content": "dpkg(1), mk-origtargz(1), perlre(1), uupdate(1), devscripts.conf(5)\n",
            "subsections": []
        },
        "AUTHOR": {
            "content": "The  original  version  of  uscan  was  written  by  Christoph Lameter <clameter@debian.org>.\nSignificant improvements, changes and bugfixes were made by Julian  Gilbey  <jdg@debian.org>.\nHTTP  support was added by Piotr Roszatycki <dexter@debian.org>. The program was rewritten in\nPerl by Julian Gilbey. Xavier Guimard converted it in object-oriented Perl using Moo.\n\nDebian Utilities                             2026-02-25                                     USCAN(1)",
            "subsections": []
        }
    },
    "summary": "uscan - scan/watch upstream sources for new releases of software",
    "flags": [],
    "examples": [],
    "see_also": [
        {
            "name": "dpkg",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/dpkg/1/json"
        },
        {
            "name": "mk-origtargz",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/mk-origtargz/1/json"
        },
        {
            "name": "perlre",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/perlre/1/json"
        },
        {
            "name": "uupdate",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/uupdate/1/json"
        },
        {
            "name": "devscripts.conf",
            "section": "5",
            "url": "https://www.chedong.com/phpMan.php/man/devscripts.conf/5/json"
        }
    ]
}