cupt

Langue: en

Autres versions - même langue

Version: 2010-06-14 (ubuntu - 24/10/10)

Section: 1 (Commandes utilisateur)

NAME

cupt - console package management tool

SYNOPSIS

cupt [ option... ] action [ { parameter | option } ... ]

ACTIONS

Query actions

version,-v,--version
prints versions of packages 'cupt' and 'libcupt-perl'
help,-h,--help
prints the short help for available actions
config-dump
If invoked without arguments, prints all configuration variables to standard output.

If one argument is supplied, it is treaten as a configuration option and only the value of this option is printed (empty string in case of undefined value). Note that only scalar (non-list) options can be retrieved in this mode.

Examples:

"cupt config-dump"

"cupt config-dump acquire::http::timeout"

show
prints version info of specified binary packages

This subcommand receives list of ``Binary package version expression'''s, see below.

Specific options:

--all-versions,-a
print all versions of the package, not selected one

Corresponding configuration variable: apt::cache::allversions

--no-all-versions
don't print all versions of the package, use only selected one

Corresponding configuration variable: apt::cache::allversions

--with-release-info
also print information about release info where the version of the package live

Examples:
"cupt show qmmp"
"cupt show --all-versions qmmp debianutils"
"cupt show --with-release-info audacious/testing apt debianutils=2.3.38"
showsrc
The same as show, only for source packages.

Examples:

"cupt showsrc --all-versions qmmp"

"cupt showsrc --with-release-info audacious/testing apt"

"cupt showsrc libxine1"

search
searches for packages that contains some string within package names and package descriptions

This subcommand receives a list a Perl-compatible Regular Expressions (PCRE) to search. Only those packages will be printed that contain all of specified patterns.

Specific options:

--case-sensitive
search case-sensitively
--names-only,-n
search only in package names

Corresponding configuration variable: apt::cache::namesonly


Examples:
"cupt search nvidia driver"
"cupt search --case-sensitive Vim"
"cupt search -n vim"
"cupt search "package manager""
depends
prints dependency relation expressions for given version of package

By default prints 'Pre-Depends', 'Depends' and 'Recommends' for the version.

This subcommand receives list of ``Binary package version expression'''s, see below.

Specific options:

--with-suggests
take also 'Suggests' dependencies into account
--recurse
process the dependencies recursively

Corresponding configuration variable: apt::cache::recursedepends

--all-versions,-a
when --recurse is specified, pick up all versions for the relation expression, not the ``best'' one

Corresponding configuration variable: apt::cache::allversions


Examples:
"cupt depends nlkt perl/stable"
"cupt depends --important xserver-xorg-core"
"cupt depends --recurse xmlto"
rdepends
same as depends, but prints reverse relations instead of forward ones
why
prints one of available dependency paths between package(s)/system and the package.

This subcommand receives a list of binary package expressions (which can be empty), then one binary package expression without wildcards.

If the list of binary package expressions is empty (i.e. subcommand received only one argument), then the list is build of manually installed packages in the system.

If no dependency paths found, prints nothing.

Uses configuration variables cupt::resolver::keep-recommends and cupt::resolver::keep-suggests to determine whether to honor Recommends and Suggests respectively when building dependency paths.

Examples:

"cupt why kmail libgnutls26"

"cupt why libgnutls26"

"cupt why icedove kmail libgnutls26"

policy
prints available versions with pins and release info for each binary package name

This subcommand receives the list of package names.

Examples:

"cupt policy dpkg"

"cupt policy libpqxx-2.6.9ldbl libpqxx-3.0"

policysrc
prints available versions with pins and release info for each source package name

This subcommand receives the list of package names.

Examples:

"cupt policysrc dpkg"

"cupt policysrc libpqxx libpqxx3"

pkgnames
prints package names that start with a supplied suffix

If no suffix is given, prints all package names

Examples:

"cupt pkgnames"

"cupt pkgnames liba"

changelog
displays changelog for given versions of packages

This subcommand receives list of ``Binary package version expression'''s, see below.

Works only with installed packages and official Debian and Ubuntu repositories.

Examples:

"cupt changelog dpkg/installed"

"cupt changelog --installed-only dpkg nlkt lintian"

"cupt changelog libqtcore4"

copyright
displays copyright for given versions of packages

This subcommand receives list of ``Binary package version expression'''s, see below.

Works only with installed packages and official Debian and Ubuntu repositories.

Examples:

"cupt copyright dpkg/installed"

"cupt copyright --installed-only dpkg nlkt lintian"

"cupt copyright libqtcore4"

screenshots
open a browser window/tab with screenshots of given packages.

This subcommand receives list of package names.

Example:

"cupt screenshots arora"

snapshot list
list names of the available system snapshots, one per line

This subcommand receives no arguments.

Example: "cupt snapshot list"

query-specific options

--important,-i
don't take 'Recommends' dependencies into account

Corresponding configuration variable: apt::cache::important

--installed-only
work only with installed versions of packages; valuable only for ``show'', ``depends'', ``rdepends'', ``search'', ``pkgnames'', ``changelog'' actions

Management actions

update
updates package indexes

This subcommand receives no arguments.

Example:

"cupt update"

install
installs, upgrades or downgrades specified packages

This subcommand receives list of ``Binary package version expression'''s, see below.

If some version of package was already installed, this command will upgrade/downgrade it; otherwise, the package will be freshly installed.

Examples:

"cupt install nlkt"

"cupt install devscripts xserver-xorg/experimental xfce4-mixer=4.6.0-2"

remove
removes specified packages

This subcommand receives the list of package names.

Examples:

"cupt remove nlkt"

"cupt remove devscripts kde4-minimal"

full-upgrade
performs as more upgrades of the installed packages as possible, the recommended way to do upgrades

This subcommand is usually invoked without any further parameters:

"cupt full-upgrade"

List of ``Binary package version expression'''s can be however specified as additional parameters.

Example: the command "cupt full-upgrade xserver-xorg/installed" will try to upgrade your system, however preserving package 'xserver-xorg' to be sticked with currently installed version.

safe-upgrade
the same as ``full-upgrade'', but with the change that problem resolver won't try to remove non-automatically installed packages in order to upgrade more packages, equivalent of 'full-upgrade --no-remove'.
dist-upgrade
the same as ``full-upgrade'', but firstly upgrades the package management tools, then upgrades the whole system.

Recommended over ``full-upgrade'' for major upgrades.

reinstall
reinstalls specified binary packages

This subcommand receives list of binary package names.

Examples:

"cupt reinstall libc6"

markauto
marks specified packages as automatically installed

This subcommand receives the list of package names.

Examples:

"cupt markauto libstreamanalyzer0"

"cupt markauto lsof gimp-data"

unmarkauto
marks specified packages as manually installed

This subcommand receives the list of package names.

Examples:

"cupt unmarkauto kpogre"

"cupt unmarkauto dpkg-dev"

satisfy
performs all needed operations to satisfy list of specified relations

This subcommand receives the list of relations or relation lines. Relation and relation lines has the same syntax as defined in Debian Policy §7.1.

The minus sign can be appended to some of relation expression lines to make relation expressions unsatisfied instead.

Examples:

"cupt satisfy "kmail (>= 4:4.2)""

"cupt satisfy "xserver-xorg (>> 1.6)" "xserver-common (<< 1.6.1~)""

"cupt satisfy "nautilus (>= 2.16.0), libnautilus-extension1 (>= 2.16.0), wget (>= 1.10.0)""

"cupt satisfy "gettext (= 0.17-7)" "mail-transport-agent-""

build-dep
performs all needed operations to satisfy list of build-dependencies of specified source packages

This subcommand receives the list of ``Source package version expression'''s.

Examples:

"cupt build-dep qt4-x11"

"cupt build-dep unetbootin/unstable libcdio/experimental"

source
fetches Debian source files needed to build a Debian binary package

This subcommand receives the list of ``Source package version expression'''s.

Parameters:

--tar-only
download only original tarball
--diff-only
download only Debian diff
--dsc-only
download only Debian dsc
--download-only
don't unpack downloaded source files

Examples:
"cupt source libsort-fields-perl"
"cupt source --diff-only libpqxx cupt/unstable"
"cupt source libxine1"
clean
removes all deb archives from cache on disk

This subcommand receives no arguments.

Example: "cupt clean"

autoclean
removes deb archives which are not available in package indexes from cache on disk

This subcommand receives no arguments.

Example: "cupt autoclean"

snapshot save
saves a snapshot of the current packages state

This subcommand receives one argument - desired snapshot name.

Example: "cupt snapshot save old-udev"

snapshot load
returns the system (as set of installed packages) to the previously saved state

This subcommand receives one argument - snapshot name to load.

Example: "cupt snapshot load old-udev"

snapshot remove
removes the system snapshot

This subcommand receives one argument - snapshot name to remove.

Example: "cupt snapshot remove old-libgtk"

snapshot rename
renames the system snapshot

This subcommand receives two arguments - old snapshot name and new snapshot name.

Example: "cupt snapshot rename old-libgtk 20091005"

shell
starts interactive shell-like environment

This subcommand receives no arguments.

This subcommand can receive all common options which will be preserved across all session. You can override them for any subcommand in a usual way.

On every shell prompt you can supply any valid subcommand from this manual page, using all allowed parameters, just if it was command line. Simple shell quotes around arguments are also allowed.

Example:

         $ cupt shell
         This is interactive shell of cupt package manager.
         Building the package cache... [done]
         cupt>policy libsoprano4
         libsoprano4:
           Installed: 2.2.2+dfsg.1-1
           Candidate: 2.3.0+dfsg.1-2
           Version table:
                  2.3.0+dfsg.1-2 501
                         http://debian.org.ua/debian unstable/main (signed)
          *** 2.2.2+dfsg.1-1 100
                         /var/lib/dpkg/status installed/ (unsigned)
                  2.3.0+dfsg.1-1 2
                         http://debian.org.ua/debian experimental/main (signed)
         cupt>depends libsoprano4/experimental
         libsoprano4 2.3.0+dfsg.1-1:
           Depends: libc6 (>= 2.2.5)
           Depends: libclucene0ldbl (>= 0.9.20-1)
           Depends: libgcc1 (>= 1:4.1.1)
           Depends: libqt4-dbus (>= 4:4.5.2)
           Depends: libqt4-network (>= 4:4.5.2)
           Depends: libqt4-xml (>= 4:4.5.2)
           Depends: libqtcore4 (>= 4:4.5.2)
           Depends: libstdc++6 (>= 4.1.1)
           Depends: soprano-daemon (= 2.3.0+dfsg.1-1)
         cupt>rdepends soprano-daemon
         soprano-daemon 2.3.0+dfsg.1-2:
           Reverse-Depends: libsoprano4 2.3.0+dfsg.1-2: soprano-daemon (= 2.3.0+dfsg.1-2)
         cupt>show soprano-daemon
         Package: soprano-daemon
         Version: 2.3.0+dfsg.1-2
         Status: not installed
         Source: soprano
         Priority: optional
         Section: utils
         Size: 153KiB
         Uncompressed size: 536KiB
         Maintainer: Debian Qt/KDE Maintainers <debian-qt-kde@lists.debian.org>
         Architecture: amd64
         Depends: libc6 (>= 2.2.5), libgcc1 (>= 1:4.1.1), libqt4-dbus (>= 4:4.5.2), libqt4-network (>= 4:4.5.2),
         libqtcore4 (>= 4:4.5.2), libraptor1 (>= 1.4.18), librdf0 (>= 1.0.9), libsoprano4 (>= 2.3.0), libstdc++6 (>= 4.1.1)
         Conflicts: libsoprano-dev (<< 2.3.0+dfsg.1-1), libsoprano4 (<< 2.3.0+dfsg.1-1)
         Replaces: libsoprano-dev (<< 2.3.0+dfsg.1-1), libsoprano4 (<< 2.3.0+dfsg.1-1)
         URI: http://debian.org.ua/debian/pool/main/s/soprano/soprano-daemon_2.3.0+dfsg.1-2_amd64.deb
         MD5: af29b39a741d9a52de91c8e5562e0609
         SHA1: 1dfebe27b79f10911358949e56f89c64b43265eb
         SHA256: d5b290a60de56f6a7e0af44f5265c6668bb4689204556b9022a5233a808349fc
         Description: daemon for the Soprano RDF framework
          Soprano is a pluggable RDF storage, parsing, and serialization framework based
          on Qt 4. Soprano is targeted at desktop applications that need to store RDF
          data. Its API has been optimized for simplicity and ease of use, while its
          modular structure allows it to use various different RDF storage
          implementations as its backend.
          .
          This package contains the Soprano daemon, D-Bus service, parser
          plugins, and a storage plugin for the Redland RDF Application Framework.
         Homepage: http://soprano.sourceforge.net
 
         cupt>--simulate install libsoprano4
         Building the package cache... [done]
         Initializing package resolver and worker... [done]
         Scheduling requested actions... [done]
         Resolving possible unmet dependencies... 
         The following 1 packages will be INSTALLED:
 
         soprano-daemon 
 
         The following 1 packages will be UPGRADED:
 
         libsoprano4 
 
         Need to get 700KiB/700KiB of archives. After unpacking 196KiB will be used.
         Do you want to continue? [y/N/q] q
 
         cupt>exit
 
 

You can use 'quit', 'exit', ':q' or 'q' command to exit cupt shell.

One caveat exists, though: --installed-only option won't work under 'shell' subcommand.

query-specific options

--no-remove
disallow problem resolver to remove manually installed packages. Packages that are marked to remove/purge in the command line will be remove/purged as usual.

Corresponding configuration option: cupt::resolver::no-remove

--no-auto-remove
don't try to remove automatically installed packages after doing requested actions

Corresponding configuration option: cupt::resolver::auto-remove

--simulate,-s
don't modify anything in the system, just print supposed actions

Doesn't require root privileges.

Corresponding configuration option: cupt::worker::simulate

--resolver=
string, determines type of resolver: can be
fair
medium-class resolver. It chooses best possible solution (by overall score) each time. This is a default resolver.
full
full resolver. Guaranteed to suggest solution in precise order from the best to the worst result score (by the resolver's opinion). Latter means that resolver builds full resolve tree before suggesting the solutions, which means large RAM and speed penalties. Use it with caution.

Corresponding configuration option: cupt::resolver::type
--max-solution-count=
number, determines how many maximum solutions will resolver store in memory. This option prevents large memory grows by purging away solutions with worst scores. Defaults to 256. Note that very complex requests or requests on multi-repository system will increase size of solution tree dramatically, so prepare to play with increasing this option accordingly.

Corresponding configuration option: cupt::resolver::max-solution-count

--no-install-recommends,-R
cupt installs recommended packages by default, this option cancels described behavior

Corresponding configuration option: apt::install-recommends

--show-versions,-V
when displaying actions preview prompt, display also versions of packages
--show-size-changes,-Z
when displaying actions preview prompt, display also changes in disk space usage for each package
--show-reasons,--show-deps,-D
when displaying actions preview prompt, display also reasons why this action was considered to perform

Corresponding configuration option: cupt::resolver::track-reasons

--no-install-unpacked
By default cupt will implicitly install all already unpacked packages, this is needed, for example, for proper continue of interrupted upgrades. This option cancels behavior described.
--download-only,-d
stop after download stage, don't modify the system; not applicable for ``markauto'' and ``markauto'' actions

Corresponding configuration option: cupt::worker::download-only

--assume-yes,--yes,-y
don't ask for solution confirmation, assume the answer is 'y' (``yes''), except for dangerous actions, where assume 'q' (``decline and exit'')

Corresponding configuration options: apt::get::assume-yes, cupt::console::assume-yes

management modifiers

-
remove the package, can be used in non-remove actions

Examples:

"cupt install kde4 icewm-" - install the package 'kde4' and remove the package 'icewm' simultaneously.

"cupt full-upgrade iceweasel- icedove-" - upgrade the system, deleting iceweasel and icedove

+
install the package, can be used in remove actions

Examples:

"cupt remove kde konqueror+" - remove kde, but install/upgrade konqueror

"cupt remove kde konqueror/installed+" - remove kde, but leave konqueror

EXPRESSIONS

This section documents some common expressions used by actions.

Binary package version expression

package_name[modifier]

selects one version of given binary package.

Possible modifiers:

<none>
selects policy version of the package

Example: "audacious".

=<version string>
selects specified version of the package

Example: "audacious=1.5.1-2"

/<distribution>
selects a version from specified distribution (archive name or codename)

Examples: "audacious/lenny" (by codename), "audacious/stable" (by archive name)

/installed
selects installed version of the package

Example: "audacious/installed"

Also, you may specify shell wildcars '*' and '?' in the package names.

Examples: "xfce4-*", "python2.5-*/unstable", "?aff*/installed"

For all management subcommands, there is also '@<path-to-file>' syntax. In this case this construction will be substituted by binary package expressions listed in the specified file one by line.

Source package version expression

package_name[modifier]

selects one version of given source package.

Possible modifiers are identical to those defined in ``Binary package version expression'', except for '/installed'.

Also, you can specify ``Binary package version expression'' as ``Source package version expression'', then binary-to-source mapping will be performed.

COMMON OPTIONS

--option=,-o
sets specified configuration option, syntax: ``<name>=<value>''

Examples:

"cupt remove nlkt -o 'cupt::resolver::keep-recommends=0'" (regular option)

"cupt remove nlkt -o 'apt::neverautoremove::=libcanberra0" (list option)

--target-release=,--default-release=,-t
sets preferred release to pick up packages from, you can specify codename or archive name

Corresponding configuration option: apt::default-release

Examples: "cupt install -t unstable xserver-xorg", "cupt -t squeeze full-upgrade"

--purge
when removing packages, also delete their configuration files

Corresponding configuration option: cupt::worker::purge

--quiet,-q
don't output anything to standard output

CONFIGURATION VARIABLES

Firstly, Cupt uses following APT configuration variables:

acquire::*::timeout, acquire::*::proxy, acquire::retries, apt::acquire::translation, apt::cache::allversions, apt::cache::important, apt::cache::namesonly, apt::cache::recursedepends, apt::default-release, apt::install-recommends, apt::install-suggests, apt::neverautoremove, apt::get::assume-yes, apt::get::allowunauthenticated, apt::get::automaticremove, apt::get::purge, apt::update::pre-invoke, apt::update::post-invoke, apt::update::post-invoke-success, dir, dir::bin::dpkg, dir::cache, dir::cache::archives, dir::etc, dir::etc::sourcelist, dir::etc::sourceparts, dir::etc::parts, dir::etc::main, dir::etc::preferences, dir::state, dir::state::extendedstates, dir::state::lists, dir::state::status, dpkg::options, dpkg::pre-invoke, dpkg::post-invoke, dpkg::pre-install-pkgs, gpgv::trustedkeyring, quiet

See apt.conf(5) for their meanings.

Secondly, Cupt recognizes (but doesn't use) following configuration variables:

apt::archives::*, acquire::pdiffs, apt::cache-limit, apt::periodic::*, unattended-upgrade::*, acquire::compressiontypes, apt::get::show-upgraded, apt::get::build-dep-automatic, rpm::pre-invoke, rpm::post-invoke

Thirdly, Cupt introduces following cupt-specific configuration variables:

acquire::http::allow-redirects
boolean (0/1), specifies whether should downloader follow HTTP redirects. True by default.
cupt::cache::obey-hold
integer, specifies priority increase for versions that are put on hold. Defaults to 1000000. Set this option to 0 if you do not want to obey holds. You may want to increase this option in (very unlikely to happen) situations: when you have thousands of manually installed packages and very large query; when you have a manually crafted pin priorities system with very large pin values.
cupt::console::allow-untrusted
don't treat using untrusted packages as dangerous action
cupt::console::assume-yes
see --assume-yes
cupt::directory::state
directory which contains Cupt state info
cupt::downloader::max-simultaneous-downloads
positive number, specifies maximum number of simultaneous downloads
cupt::downloader::protocols::protocol::priority
positive number, defines the priority of download protocol protocol, determines an order in which different URIs for the same file will be tried. Defaults to 100.
cupt::downloader::protocols::protocol::methods::method::priority
positive number, defines the priority of download method method, the method with maximum priority will be used for downloading the URI of protocol protocol. Defaults to 100.
cupt::downloader::protocols::protocol::methods
list of names of the methods available to download protocol protocol
cupt::update::compression-types::*::priority
defines preference to download compressed files with higher priority first. 100 by default.

'*' can be 'gz', 'bz2', 'lzma' and 'uncompressed'.

Set some option to <100 value to make it low-precedence than default, and >100 to make it high-precedence than default.

If some methods have the equal priority (which is the default setting), then files with smaller size with be chosen over the files with bigger size.

Example:

You have a low-speed CPU but rather high-speed internet connection and want to prefer gzip over lzma and lzma over bzip2. Then you have to set options like:

   cupt::update::compression-types
   {
     gz::priority "200";
     lzma::priority "150";
   }
 
 

Also, if you have a local mirror, which may store uncompressed indexes too (an official Debian archive doesn't store them), you may set also

cupt::update::compression-types::uncompressed::priority ``300'';

cupt::update::keep-bad-signatures
boolean (0/1), specifies whether to keep signature files that failed GPG check when doing update. False by default. Setting this option to true will break compatibility with APT in area of signature checking.
cupt::resolver::keep-recommends
boolean (0/1), specifies whether should resolver try to keep already installed recommended packages or not. True by default.
cupt::resolver::keep-suggests
boolean (0/1), specifies whether should resolver try to keep already installed suggested packages or not. False by default.
cupt::resolver::auto-remove
see --no-auto-remove/
cupt::resolver::max-solution-count
see --max-solution-count
cupt::resolver::quality-bar
integer number, the ``quality bar'' for the native resolver. For the situations when a lot of solutions available, increasing this value slows down choosing the solution to propose, but may increase its quality. Defaults to -50. The sane value borders: from -1000 to 1000.
cupt::resolver::external-command
a preview-only, experimental option to use external resolver using CUDF protocol. Don't use it unless you know what you are doing.

Example: "cupt -s safe-upgrade -o "cupt::resolver::external-command=cat > cudfout.txt""

cupt::resolver::no-remove
see --no-remove
cupt::resolver::synchronize-source-versions
string, this option controls whether and how the native resolver will attempt to keep all binary packages from the same source package at the same source version

Possible values:

none
Don't attempt to synchronize source versions. This is the default value.
soft
Don't forbid any modifications to the packages and attempt to synchronize related binary packages when possible upon the modifications of certain binary package.
hard
Forbid any modifications to the packages when at least one related binary package cannot be synchronized with the modified one.

It's highly recommended to have source entries for as more as possible available binary packages for more fast and accurate results.
Example:
Suppose we have 'libfoo1' and 'foo' binary packages which came from the same source package. We have libfoo1 '1.2-1' and foo '1.2-1' installed.
Situation 1: libfoo1 has new '1.3-1' version and foo has new '1.3-1' version.
Situation 2: libfoo1 has new '1.3-1' version and foo has new '1.3-2' version.
We called: "cupt install foo".
What would be done by resolver:
none
Situation 1: install new foo, leave libfoo1 as of installed version

Situation 2: install new foo, leave libfoo1 as of installed version

soft
Situation 1: install new foo and libfoo1

Situation 2: install new foo, leave libfoo1 as of installed version

hard
Situation 1: install new foo and libfoo1

Situation 2: prohibit to install new version of foo

cupt::resolver::synchronize-source-versions::exceptions
lists source package names (Perl regular expressions) of known exceptions.
cupt::resolver::track-reasons
see --show-reasons
cupt::resolver::type
see --resolver
cupt::worker::allow-indirect-upgrade
list of package names which will be upgraded indirectly

There are some packages with dependencies that make unable to upgrade the package properly. List them here. See also Debian BTS #551831.

cupt::worker::archives-space-limit
integer, bytes, if set, limits the worker to not download more than specified amount of archives, and use download-install-clean algorithm (download archives, install packages, clean just downloaded archives). Worker will try to split all actions into unrelated changesets so each changeset require only limited download space. Any system changes will be started only if changesets are generated successfully.
cupt::worker::archives-space-limit::tries
integer, specifies how many times will worker try to generate unrelated changesets if cupt::worker::archives-space-limit is set. As genearting algorithm uses randomization, increasing this option increases the chances to generate. 20 by default.
cupt::worker::defer-triggers
boolean (0/1), specifies whether should worker defer dpkg trigger processing to the end of the whole operation or not. Being set to true, speeds up large-amount actions, but if the operation will somewhy be interrupted, leaves system in the interim trigger state, which can be fixed by manual run of 'dpkg --triggers-only --pending' command. False by default due to tiresome dpkg bug (Debian BTS #526774).
cupt::worker::download-only
see --download-only
cupt::worker::purge
boolean (0/1), specifies whether purge packages in addition to removing or not. False by default.
cupt::worker::simulate
see --simulate
debug::resolver
boolean (0/1), if true, resolver will print a lot of debug information to the standard error
debug::worker
boolean (0/1), if true, worker will print some debug information to the standard error
debug::gpgv
boolean (0/1), if true, cache will print some debug information while verifying signatures to the standard error
debug::downloader
boolean (0/1), if true, the downloader manager will print some debug messages

REPORTING

Please report all bugs in Cupt to Debian BTS using reportbug(1).

The discussion channel about Cupt is irc://irc.debian.org#cupt.

SEE ALSO

cupt_vs_apt(5), cupt_howto(7)

AUTHOR

Eugene V. Lyubimkin <jackyf@debian.org>