Package: git-buildpackage Version: 0.9.13 Severity: wishlist Dear maintainer,
Please document the actual effect of specifying "auto" for tristate command-line options such as --git-color and --git-notify. For example, the current documentation --git-color=COLOR Whether to use colored output, default is 'auto' doesn't actually tell the user what the value "auto" means. It can be inferred if they are familiar with git's color options. Similarly, with --git-notify set to "auto", the user is left to infer what is decided automatically. Is it the presence of a terminal? The presence of an active desktop session? The presence of a particular Python library? I had to use the source to find the answer, and only then notice that the suggested python3-notify2 was not installed. Thank you for your valuable contributions to Debian! -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages git-buildpackage depends on: ii devscripts 2.18.10 ii git 1:2.19.2-1 ii man-db 2.8.4-3 ii python3 3.7.1-3 ii python3-dateutil 2.6.1-1 ii python3-pkg-resources 40.6.2-1 ii sensible-utils 0.0.12 Versions of packages git-buildpackage recommends: ii pristine-tar 1.45 ii python3-requests 2.20.0-2 ii sbuild 0.77.1-2 Versions of packages git-buildpackage suggests: ii python3-notify2 0.3-3 ii sudo 1.8.26-2 ii unzip 6.0-21 -- no debconf information
