use strict; use warnings; return [ { 'accept' => [ '.*', { 'description' => 'Additional user-defined fields Fields in the main source control information file with names starting X, followed by one or more of the letters BCS and a hyphen -, will be copied to the output files. Only the part of the field name after the hyphen will be used in the output file. Where the letter B is used the field will appear in binary package control files, where the letter S is used in Debian source control files and where C is used in upload control (.changes) files. For details, see L
', 'summary' => 'User defined field', 'type' => 'leaf', 'value_type' => 'string' } ], 'author' => [ 'Dominique Dumont' ], 'copyright' => [ '2010,2011 Dominique Dumont' ], 'element' => [ 'Source', { 'compute' => { 'allow_override' => '1', 'formula' => 'use Cwd; my $res = getcwd =~ m!/([a-z0-9][a-z0-9+.-]+)$! ? $1 : undef; ', 'use_eval' => '1' }, 'description' => 'Source package name. Defaults to the name of the current directory or undef if the directory name does not match Debian requirements for a source package', 'mandatory' => '1', 'match' => '^[a-z0-9][a-z0-9+.-]+$', 'summary' => 'source package name', 'type' => 'leaf', 'value_type' => 'uniline' }, 'debhelper-version', { 'default' => '0', 'description' => 'Debhelper version. This parameter is hidden because it does not exist in control. It\'s used to drive warp mechanism for parameters that depend on debhelper version.', 'level' => 'hidden', 'type' => 'leaf', 'value_type' => 'integer' }, 'X-Style', { 'description' => 'Uncompromising file formatting of Debian packaging files By using it, you agree to cede control over minutiae of hand-formatting. In return, the formatter gives you speed, determinism, and freedom from style discussions about formatting. The C style is inspired by the C Python code formatter. As with C, the style will evolve over time. ', 'summary' => 'Uncompromising file formatting of Debian packaging files', 'type' => 'leaf', 'value_type' => 'uniline' }, 'Standards-Version', { 'class' => 'Config::Model::Dpkg::Control::Source::StandardVersion', 'description' => 'This field indicates the Debian policy version number this package complies to. Before updating this field, please read L to know what changes came with a new policy version number and apply the required changes (if any) to your package.', 'mandatory' => '1', 'match' => '^\\d+\\.\\d+\\.\\d+(\\.\\d+)?$', 'summary' => 'Debian policy version number this package complies to', 'type' => 'leaf', 'value_type' => 'uniline', 'warn_if' => { 'current' => { 'code' => '$self->compare_with_last_version($_) == -1;', 'fix' => '$_ = $self->_fetch_std; # restore default value', 'msg' => 'Current standards version is \'$std_value\'. Please read https://www.debian.org/doc/debian-policy/upgrading-checklist.html for the changes that may be needed on your package to upgrade it from standard version \'$_\' to \'$std_value\'. ' }, 'old_lintian' => { 'code' => '$self->compare_with_last_version($_) == 1;', 'msg' => 'Current standards version \'$_\' is newer than lintian version ($std_value). Please check your system ' } } }, 'Maintainer', { 'compute' => { 'allow_override' => '1', 'formula' => 'my $name = $ENV{DEBFULLNAME}; my $email = $ENV{DEBEMAIL} ; my $ret; $ret = "$name <$email>" if $name and $email; $ret;', 'use_eval' => '1' }, 'description' => 'The package maintainer\'s name and email address. The name must come first, then the email address inside angle brackets <> (in RFC822 format). If the maintainer\'s name contains a full stop then the whole field will not work directly as an email address due to a misfeature in the syntax specified in RFC822; a program using this field as an address must check for this and correct the problem if necessary (for example by putting the name in round brackets and moving it to the end, and bringing the email address forward). ', 'summary' => 'package maintainer\'s name and email address', 'type' => 'leaf', 'value_type' => 'uniline', 'warn_unless_match' => { '@' => { 'msg' => 'Maintainer is empty or is not an email address' } } }, 'Uploaders', { 'cargo' => { 'replace_follow' => '!Dpkg my_config email-updates', 'type' => 'leaf', 'value_type' => 'uniline' }, 'type' => 'list' }, 'Section', { 'default' => 'misc', 'description' => 'The packages in the archive areas main, contrib and non-free are grouped further into sections to simplify handling. The archive area and section for each package should be specified in the package\'s Section control record (see L
). However, the maintainer of the Debian archive may override this selection to ensure the consistency of the Debian distribution. The Section field should be of the form: '.'=over '.'=item * section if the package is in the main archive area, '.'=item * area/section if the package is in the contrib or non-free archive areas. '.'=back ', 'type' => 'leaf', 'value_type' => 'uniline', 'warn_unless' => { 'area' => { 'code' => '(not defined) or m!^((contrib|non-free)/)?[\\w\\-]+$!;', 'msg' => 'Bad area. Should be \'non-free\' or \'contrib\'' }, 'empty' => { 'code' => 'defined and length', 'msg' => 'Section is empty' }, 'section' => { 'code' => '(not defined) or m!^([-\\w]+/)?(admin|cli-mono|comm|database|devel|debug|doc|editors|education|electronics|embedded|fonts|games|gnome|golang|graphics|gnu-r|gnustep|hamradio|haskell|httpd|interpreters|introspection|java|javascript|kde|kernel|libs|libdevel|lisp|localization|mail|math|metapackages|misc|net|news|ocaml|oldlibs|otherosfs|perl|php|python|ruby|rust|science|shells|sound|tex|text|utils|vcs|video|web|x11|xfce|zope)$!;', 'msg' => 'Bad section.' } } }, 'XS-Testsuite', { 'description' => 'Enable a test suite to be used with this package. For more details see L', 'status' => 'deprecated', 'summary' => 'name of the non regression test suite', 'type' => 'leaf', 'value_type' => 'uniline' }, 'Testsuite', { 'description' => 'Enable a test suite to be used with this package. For more details see L', 'migrate_from' => { 'formula' => '$xs_testsuite', 'variables' => { 'xs_testsuite' => '- XS-Testsuite' } }, 'summary' => 'name of the non regression test suite', 'type' => 'leaf', 'value_type' => 'uniline', 'warn_unless' => { 'defined-test' => { 'code' => 'my $m = $self->grab_value(\'- Maintainer\'); my ($team) = ( $m =~ /(pkg-(?:perl|ruby|go))/ ); not defined $team or defined $_ or file(\'debian/tests/control\')->exists;', 'fix' => 'my $m = $self->grab_value(\'- Maintainer\'); my ($str) = ($m =~ /pkg-(perl|ruby|go)/); $_ = $str ? \'autopkgtest-pkg-\'.$str : undef;', 'msg' => 'Undefined while packaging team supports test suite' }, 'team-test' => { 'code' => 'my $m = $self->grab_value(\'- Maintainer\'); my ($team) = ( $m =~ /(pkg-(?:perl|ruby|go))/ ); not defined $_ or not defined $team or $_ eq \'autopkgtest-\'.$team or -e \'debian/tests/control\';', 'fix' => 'my $m = $self->grab_value(\'- Maintainer\'); my ($str) = ($m =~ /pkg-(perl|ruby|go)/); $_ = $str ? \'autopkgtest-pkg-\'.$str : undef;', 'msg' => 'value does not match maintainer team' } }, 'warn_unless_match' => { '^autopkgtest(-pkg-(dkms|elpa|go|nodejs|octave|perl|pybuild|python|r|ruby))?$' => { 'fix' => 'my $m = $self->grab_value(\'- Maintainer\'); my ($str) = ($m =~ /pkg-(perl|ruby|go)/); $_ = $str ? \'autopkgtest-pkg-\'.$str : undef;', 'msg' => 'Testsuite $_ is not a known automatic test suite' } } }, 'XS-Autobuild', { 'default' => '0', 'description' => 'Read the full description from L
in Debian developer reference.', 'level' => 'hidden', 'summary' => 'Allow automatic build of non-free or contrib package', 'type' => 'leaf', 'value_type' => 'boolean', 'warp' => { 'follow' => { 'section' => '- Section' }, 'rules' => [ '$section =~ m!^(contrib|non-free)/!', { 'level' => 'normal' } ] }, 'write_as' => [ 'no', 'yes' ] }, 'Priority', { 'choice' => [ 'required', 'important', 'standard', 'optional', 'extra' ], 'help' => { 'extra' => 'This contains all packages that conflict with others with required, important, standard or optional priorities, or are only likely to be useful if you already know what they are or have specialized requirements (such as packages containing only detached debugging symbols).', 'important' => 'Important programs, including those which one would expect to find on any Unix-like system. If the expectation is that an experienced Unix person who found it missing would say "What on earth is going on, where is foo?", it must be an important package.[5] Other packages without which the system will not run well or be usable must also have priority important. This does not include Emacs, the X Window System, TeX or any other large applications. The important packages are just a bare minimum of commonly-expected and necessary tools.', 'optional' => '(In a sense everything that isn\'t required is optional, but that\'s not what is meant here.) This is all the software that you might reasonably want to install if you didn\'t know what it was and don\'t have specialized requirements. This is a much larger system and includes the X Window System, a full TeX distribution, and many applications. Note that optional packages should not conflict with each other. ', 'required' => 'Packages which are necessary for the proper functioning of the system (usually, this means that dpkg functionality depends on these packages). Removing a required package may cause your system to become totally broken and you may not even be able to use dpkg to put things back, so only do so if you know what you are doing. Systems with only the required packages are probably unusable, but they do have enough functionality to allow the sysadmin to boot and install more software. ', 'standard' => 'These packages provide a reasonably small but not too limited character-mode system. This is what will be installed by default if the user doesn\'t select anything else. It doesn\'t include many large applications. ' }, 'replace' => { 'extra' => 'optional' }, 'type' => 'leaf', 'value_type' => 'enum', 'warp' => { 'follow' => { 'std_ver' => '- Standards-Version' }, 'rules' => [ '$std_ver lt \'4.7.3\'', { 'default' => 'optional' }, '$std_ver ge \'4.7.3\'', { 'upstream_default' => 'optional' } ] } }, 'Build-Driver', { 'description' => 'The name of the build driver that dpkg (`dpkg-buildpackage`) will use for assembling the package.', 'summary' => 'Which build-driver implementation dpkg should use for the package build', 'type' => 'leaf', 'upstream_default' => 'debian-rules', 'value_type' => 'uniline' }, 'Build-Depends', { 'cargo' => { 'class' => 'Config::Model::Dpkg::Dependency', 'type' => 'leaf', 'value_type' => 'uniline', 'warn_if_match' => { 'libpng12-dev' => { 'fix' => '$_ = \'libpng-dev\';', 'msg' => 'This dependency is deprecated and should be replaced with libpng-dev. See BTS 650601 for details' } }, 'warp' => { 'follow' => { 'dhv' => '- debhelper-version' }, 'rules' => [ 'defined $dhv and $dhv and $dhv+0 >= 10', { 'warn_if_match' => { '^(autotools-dev|dh-autoreconf)' => { 'fix' => '$_ = undef', 'msg' => 'dependency "$_" is not necessary with debhelper > 10' } } } ] } }, 'class' => 'Config::Model::Dpkg::DependencyList', 'description' => '=pod List of packages that must be installed: '.'=over '.'=item * during clean '.'=item * to build architecture-dependent binaries ("Architecture: any" or specific architectures). '.'=back Technically, these packages must be installed for the following build targets: clean, build-arch, and binary-arch. See L. On the other hand, the list of packages that must be installed to build architecture-independent binaries ("Architecture: all") should be listed in "Build-Depends-Indep" field. Including a dependency in this field does not have the exact same effect as including it in both Build-Depends-Arch and Build-Depends-Indep, because the dependency also needs to be satisfied when building the source package. See also L man page. This parameter can aslo have restriction formula. For instance: Build-Depends: foo (>= 1.0) [i386 arm] , bar See L for more details. ', 'duplicates' => 'warn', 'summary' => 'List of package required during clean or build of architecture-dependent packages', 'type' => 'list' }, 'Build-Depends-Arch', { 'cargo' => { 'class' => 'Config::Model::Dpkg::Dependency', 'type' => 'leaf', 'value_type' => 'uniline' }, 'class' => 'Config::Model::Dpkg::DependencyList', 'description' => 'Same as Build-Depends, but these packages are only needed when building the architecture dependent packages. The Build-Depends are also installed in this case. See L for details', 'duplicates' => 'warn', 'summary' => 'List of package required to build architecture-dependent packages', 'type' => 'list' }, 'Build-Depends-Indep', { 'cargo' => { 'class' => 'Config::Model::Dpkg::Dependency', 'type' => 'leaf', 'value_type' => 'uniline' }, 'class' => 'Config::Model::Dpkg::DependencyList', 'description' => '=pod List of packages that must be installed to build architecture-independent binaries ("Architecture: all"). Technically, these packages must be installed for the following build targets: build, build-indep, binary, and binary-indep. See L. Note that packages required during "clean" phase must be declared in "Build-Depends" field. This parameter can aslo have restriction formula. For instance: Build-Depends: foo (>= 1.0) [i386 arm] , bar See L for more details. ', 'duplicates' => 'warn', 'summary' => 'List of package required during build of architecture-independent package', 'type' => 'list' }, 'Build-Conflicts', { 'cargo' => { 'type' => 'leaf', 'value_type' => 'uniline' }, 'class' => 'Config::Model::Dpkg::DependencyList', 'description' => 'List of packages that must be missing (i.e. B installed): '.'=over '.'=item * during clean '.'=item * to build architecture-dependent binaries ("Architecture: any" or specific architectures). '.'=back Technically, these packages must B be installed for the following build targets: clean, build-arch, and binary-arch. See L. On the other hand, the list of packages that must B be installed to build architecture-independent binaries ("Architecture: all") should be listed in "Build-Conflicts-Indep" field. Including a dependency in this list has the same effect as including it in both Build-Conflicts-Arch and Build-Conflicts-Indep, with the additional effect of being used for source-only builds. See L for details.', 'duplicates' => 'warn', 'summary' => 'List of package not wanted during clean or build of architecture-dependent packages', 'type' => 'list' }, 'Build-Conflicts-Arch', { 'cargo' => { 'type' => 'leaf', 'value_type' => 'uniline' }, 'class' => 'Config::Model::Dpkg::DependencyList', 'description' => 'List of packages that must be missing (i.e. B installed) to build archictecture dependent binaries See L for details.', 'duplicates' => 'warn', 'summary' => 'List of package not wanted during build of architecture dependent packages', 'type' => 'list' }, 'Build-Conflicts-Indep', { 'cargo' => { 'type' => 'leaf', 'value_type' => 'uniline' }, 'class' => 'Config::Model::Dpkg::DependencyList', 'description' => 'List of packages that must be missing (i.e. B installed) to build binaries with arch set to "all. Technically, these packages must B be installed for the following build targets: build, build-indep, binary, and binary-indep. See L. Note that packages not wanted during "clean" phase must be declared in "Build-Conflicts" field.', 'duplicates' => 'warn', 'summary' => 'List of package not wanted during build of architecture-independent packages', 'type' => 'list' }, 'Built-Using', { 'cargo' => { 'class' => 'Config::Model::Dpkg::Dependency', 'type' => 'leaf', 'value_type' => 'uniline' }, 'class' => 'Config::Model::Dpkg::DependencyList', 'description' => ' Some binary packages incorporate parts of other packages when built but do not have to depend on those packages. Examples include linking with static libraries or incorporating source code from another package during the build. In this case, the source packages of those other packages are a required part of the complete source (the binary package is not reproducible without them). A Built-Using field must list the corresponding source package for any such binary package incorporated during the build, including an B ("=") version relation on the version that was used to build that binary package[57]. A package using the source code from the gcc-4.6-source binary package built from the gcc-4.6 source package would have this field in its control file: Built-Using: gcc-4.6 (= 4.6.0-11) A package including binaries from grub2 and loadlin would have this field in its control file: Built-Using: grub2 (= 1.99-9), loadlin (= 1.6e-1) ', 'duplicates' => 'warn', 'summary' => 'Additional source packages used to build the binary', 'type' => 'list' }, 'Vcs-Browser', { 'compute' => { 'allow_override' => '1', 'formula' => ' $pkgname =~ /r-cran-/ ? "https://salsa.debian.org/r-pkg-team/$pkgname" : $maintainer =~ /pkg-perl/ ? "https://salsa.debian.org/perl-team/modules/packages/$pkgname" : $maintainer =~ /pkg-ruby-extras/ ? "https://salsa.debian.org/ruby-team/$pkgname" : $maintainer =~ /pkg-javascript/ ? "https://salsa.debian.org/js-team/$pkgname" : $maintainer =~ /debian-med-packaging/ ? "https://salsa.debian.org/med-team/$pkgname" : $maintainer =~ /team\\@neuro.debian.net/ ? "https://salsa.debian.org/neurodebian-team/$pkgname" : $maintainer =~ /debian-science-maintainers/ ? "https://salsa.debian.org/science-team/$pkgname" : $maintainer =~ /pkg-phototools-devel/ ? "https://salsa.debian.org/debian-phototools-team/$pkgname" : $maintainer =~ /pkg-java-maintainers/ ? "https://salsa.debian.org/java-team/$pkgname" : $maintainer =~ /r-pkg-team/ ? "https://salsa.debian.org/r-pkg-team/$pkgname" : undef ;', 'use_eval' => '1', 'variables' => { 'maintainer' => '- Maintainer', 'pkgname' => '- Source' } }, 'description' => 'Value of this field should be a https:// URL pointing to a web-browsable copy of the Version Control System repository used to maintain the given package, if available. The information is meant to be useful for the final user, willing to browse the latest work done on the package (e.g. when looking for the patch fixing a bug tagged as pending in the bug tracking system). ', 'match' => '^https?://', 'summary' => 'web-browsable URL of the VCS repository', 'type' => 'leaf', 'value_type' => 'uniline', 'warn_unless' => { 'debian-uri' => { 'code' => '!defined $_ or ! /debian.org/ or m{^https://salsa.debian.org/};', 'fix' => '$_ = undef; # let the correct value be set by compute setup', 'msg' => 'URL is not the canonical one for repositories hosted on Debian infrastructure.' } } }, 'Vcs-Arch', { 'description' => 'Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface. The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. ', 'summary' => 'URL of the VCS repository', 'type' => 'leaf', 'value_type' => 'uniline', 'warn_if' => { 'debian-uri' => { 'code' => 'defined $_ and /debian.org/;', 'fix' => '$_ = undef;', 'msg' => 'URL is invalid, no support for this Vcs on Debian infrastructure anymore.' } } }, 'Vcs-Bzr', { 'description' => 'Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface. The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. ', 'summary' => 'URL of the VCS repository', 'type' => 'leaf', 'value_type' => 'uniline', 'warn_if' => { 'debian-uri' => { 'code' => 'defined $_ and /debian.org/;', 'fix' => '$_ = undef;', 'msg' => 'URL is invalid, no support for this Vcs on Debian infrastructure anymore.' } } }, 'Vcs-Cvs', { 'description' => 'Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface. The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. ', 'summary' => 'URL of the VCS repository', 'type' => 'leaf', 'value_type' => 'uniline', 'warn_if' => { 'debian-uri' => { 'code' => 'defined $_ and /debian.org/;', 'fix' => '$_ = undef;', 'msg' => 'URL is invalid, no support for this Vcs on Debian infrastructure anymore.' } } }, 'Vcs-Darcs', { 'description' => 'Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface. The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. ', 'summary' => 'URL of the VCS repository', 'type' => 'leaf', 'value_type' => 'uniline' }, 'Vcs-Git', { 'compute' => { 'allow_override' => '1', 'formula' => ' $pkgname =~ /r-cran-/ ? "https://salsa.debian.org/r-pkg-team/$pkgname.git" : $maintainer =~ /pkg-perl/ ? "https://salsa.debian.org/perl-team/modules/packages/$pkgname.git" : $maintainer =~ /pkg-ruby-extras/ ? "https://salsa.debian.org/ruby-team/$pkgname.git" : $maintainer =~ /pkg-javascript/ ? "https://salsa.debian.org/js-team/$pkgname.git" : $maintainer =~ /debian-med-packaging/ ? "https://salsa.debian.org/med-team/$pkgname.git" : $maintainer =~ /team\\@neuro.debian.net/ ? "https://salsa.debian.org/neurodebian-team/$pkgname.git" : $maintainer =~ /debian-science-maintainers/ ? "https://salsa.debian.org/science-team/$pkgname.git" : $maintainer =~ /pkg-phototools-devel/ ? "https://salsa.debian.org/debian-phototools-team/$pkgname.git" : $maintainer =~ /pkg-java-maintainers/ ? "https://salsa.debian.org/java-team/$pkgname.git" : $maintainer =~ /r-pkg-team/ ? "https://salsa.debian.org/r-pkg-team/$pkgname.git" : \'\' ;', 'use_eval' => '1', 'variables' => { 'maintainer' => '- Maintainer', 'pkgname' => '- Source' } }, 'description' => 'Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface. The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. ', 'summary' => 'URL of the VCS repository', 'type' => 'leaf', 'value_type' => 'uniline', 'warn_if_match' => { '^(git|http)://' => { 'fix' => 's/^(git|http):/https:/;', 'msg' => 'An unencrypted transport protocol is used for this URI. It is recommended to use a secure transport such as HTTPS for anonymous read-only access.' }, 'debian.org/~' => { 'msg' => 'URL contains deprecated \'~\' path to user' } }, 'warn_unless' => { 'debian-uri' => { 'code' => '!defined $_ or ! /debian.org/ or m{^https://salsa.debian.org/};', 'fix' => '$_ = undef; # let the correct value be set by compute setup', 'msg' => 'URL is not the canonical one for repositories hosted on Debian infrastructure.' } } }, 'Vcs-Hg', { 'description' => 'Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface. The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. ', 'summary' => 'URL of the VCS repository', 'type' => 'leaf', 'value_type' => 'uniline', 'warn_if' => { 'debian-uri' => { 'code' => 'defined $_ and /debian.org/;', 'fix' => '$_ = undef;', 'msg' => 'URL is invalid, no support for this Vcs on Debian infrastructure anymore.' } } }, 'Vcs-Mtn', { 'description' => 'Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface. The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. ', 'summary' => 'URL of the VCS repository', 'type' => 'leaf', 'value_type' => 'uniline' }, 'Vcs-Svn', { 'description' => 'Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface. The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. ', 'summary' => 'URL of the VCS repository', 'type' => 'leaf', 'value_type' => 'uniline', 'warn_if' => { 'debian-uri' => { 'code' => 'defined $_ and /debian.org/;', 'fix' => '$_ = undef;', 'msg' => 'URL is invalid, no support for this Vcs on Debian infrastructure anymore.' } } }, 'DM-Upload-Allowed', { 'description' => 'If this field is present, then any Debian Maintainers listed in the Maintainer or Uploaders fields may upload the package directly to the Debian archive. For more information see the "Debian Maintainer" page at the Debian Wiki - https://wiki.debian.org/DebianMaintainer', 'match' => 'yes', 'status' => 'deprecated', 'summary' => 'The package may be uploaded by a Debian Maintainer', 'type' => 'leaf', 'value_type' => 'uniline' }, 'Homepage', { 'type' => 'leaf', 'value_type' => 'uniline' }, 'Bugs', { 'description' => 'Provide a custom bug tracker URL This field is *not* used by packages uploaded to Debian or most derivatives as the distro tooling has a default bugtracker built in. It is primarily useful for third-party provided packages so that bug reporting tooling can redirect the user to their bug tracker.', 'summary' => 'Custom bugtracker URL (for third-party packages)', 'type' => 'leaf', 'value_type' => 'uniline' }, 'Origin', { 'description' => 'Declare the origin of the package. This field is *not* used by packages uploaded to Debian or most derivatives as the origin would be the distribution. It is primarily useful for third-party provided packages as some tools will detect this field and change behavior, for instance by informing the user that the package is a third-party package.', 'summary' => 'Custom origin (for third-party packages)', 'type' => 'leaf', 'value_type' => 'uniline' }, 'Rules-Requires-Root', { 'description' => 'Depending on the value of the Rules-Requires-Root field, the package builder (e.g. dpkg-buildpackage) may run the debian/rules target as an unprivileged user and provide a gain root command. This command allows the debian/rules target to run particular subcommands under (fake)root. Can be \'no\', \'binary-targets\' (default)), or a space separated list of keywords containing a forward slash (e.g. "/"). For details, see L
', 'help' => { '.+/' => 'Space separated list of keywords. These keywords must always contain a forward slash, which sets them apart from the other possible values of Rules-Requires-Root. When this list is provided, the builder must provide a gain root command (as defined in debian/rules and Rules-Requires-Root) or pretend that the value was set to binary-targets, and both the builder and the package’s debian/rules script must downgrade accordingly.', 'binary-targets' => '(Default) Declares that the package will need the root (or fakeroot) when either of the binary, binary-arch or binary-indep targets are called. This is how every tool behaved before this field was defined.', 'no' => 'Declares that neither root nor fakeroot is required. Package builders (e.g. dpkg-buildpackage) may choose to invoke any target in debian/rules with an unprivileged user.' }, 'summary' => 'Defines if access to root (or fakeroot) is required during build.', 'type' => 'leaf', 'value_type' => 'uniline', 'warn_unless_match' => { '^no|binary-targets|([^\\P{PosixGraph}/]{2,}/\\p{PosixGraph}{2,}\\s*)+$' => { 'msg' => 'Invalid value. See help or Debian Policy chapter 5.6.31.2 for more information' } } }, 'X-DH-Compat', { 'description' => '=pod The C field is accepted by C as a way to declare the "debhelper compat level". Though, whenever possible, it is better to add C to C as a way to declare the debhelper compat level. This field does B count as a build-dependency, so the package will still need an explicit build-dependency on C on top of this field. As of C level 14, this is the only supported way to request a C level that is not yet stable. Example: Source: foo Build-Depends: debhelper (>= 13.26~) # Use the experimental compat 14 X-DH-Compat: 14 # ... This field replaces the C file that was the prior way of declaring unstable and experimental C levels. ', 'summary' => 'Declare debhelper compat level (used for experimental compat levels)', 'type' => 'leaf', 'value_type' => 'uniline' }, 'X-Cargo-Crate', { 'description' => 'This fields contains the name of the Rust cargo crate, which is packaged in this source package. It is used by Debian\'s Rust tooling to reliably identify the crate when it needs it. The source package name is not always sufficient for this purpose. As an example, the package name for the `utf-8` crate can both be read as `utf` with a major version of `8` or a as the crate name `utf-8`. This field is used to avoid the ambiguity. It is recommended to always include it for Rust packages.', 'summary' => 'Name of the Rust cargo crate packaged in this source package', 'type' => 'leaf', 'value_type' => 'uniline', 'warp' => { 'follow' => { 'maintainer' => '- Maintainer', 'source' => '- Source' }, 'rules' => [ '$maintainer =~ m!Debian Ruby!i or $source =~ /^ruby/', { 'level' => 'normal' } ] } }, 'XS-Python-Version', { 'status' => 'deprecated', 'type' => 'leaf', 'value_type' => 'uniline' }, 'X-Python-Version', { 'description' => 'This field specifies the versions of Python (not versions of Python 3) supported by the source package. When not specified, they default to all currently supported Python (or Python 3) versions. For more detail, See L', 'migrate_from' => { 'formula' => 'my $old = $xspython ; my $new ; if ($old =~ /,/) { # list of versions my @list = sort split /\\s*,\\s*/, $old ; $new = ">= ". (shift @list) . ", << " . (pop @list) ; } elsif ($old =~ /-/) { my @list = sort grep { $_ ;} split /\\s*-\\s*/, $old ; $new = ">= ". shift @list ; $new .= ", << ". pop @list if @list ; } else { $new = $old ; } $new ;', 'use_eval' => '1', 'variables' => { 'xspython' => '- XS-Python-Version' } }, 'summary' => 'supported versions of Python ', 'type' => 'leaf', 'upstream_default' => 'all', 'value_type' => 'uniline' }, 'X-Python3-Version', { 'description' => 'This field specifies the versions of Python 3 supported by the package. For more detail, See L', 'summary' => 'supported versions of Python3 ', 'type' => 'leaf', 'value_type' => 'uniline' }, 'XS-Ruby-Versions', { 'description' => 'indicate the versions of the interpreter supported by the library', 'level' => 'hidden', 'status' => 'deprecated', 'type' => 'leaf', 'value_type' => 'uniline', 'warp' => { 'follow' => { 'maintainer' => '- Maintainer', 'source' => '- Source' }, 'rules' => [ '$maintainer =~ m!Debian Ruby!i or $source =~ /^ruby/', { 'level' => 'normal' } ] } }, 'Synopsis', { 'description' => '=head1 NAME This field contains a human-readable synopsis of the package. However, it is not used directly. Binary packages can reference it via the C<${{source:Synopsis}}> substvars. Without any of these substvars, the C (part of the C field) of the C stanza remains unused. The B is a short "noun-phrase" intended to provide a one-line summary of a package. The B is usually displayed in cases where there is limited space such as when reviewing the search results from C. It is often a good idea to imagine that the B part is inserted into a sentence like "The package provides {{Synopsis-goes-here}}". Please see L for more details about the description field and suggestions for how to write it. ', 'summary' => 'Common base synopsis for all packages via substvar', 'type' => 'leaf', 'value_type' => 'string' }, 'Description', { 'description' => '=head1 NAME This field contains a human-readable description of the package. However, it is not used directly. Binary packages can reference parts it via the C<${{source:Extended-Description}}> substvars. Without this substvars, the C field of the C stanza remains unused. The B is a standalone description that should describe what the package does and how it relates to the rest of the system (in terms of, for example, which subsystem it is which part of). Please see L for more details about the description field and suggestions for how to write it. ', 'summary' => 'Common base description for all packages via substvar', 'type' => 'leaf', 'value_type' => 'string' } ], 'license' => 'LGPL2', 'name' => 'Dpkg::Control::Source' } ] ;