Bug#963073: reportbug: please update documentation on how to use reportbug.debian.org
Package: reportbug
Version: 7.6.0
Severity: wishlist
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
It's not very clear from README.Users what options precisely the user
should use to submit via reportbug.debian.org. At least I just spent
some minutes trying and failing to help a new user to do so.
- -- Package-specific info:
** Environment settings:
EDITOR="eedit"
DEBEMAIL="bremner@debian.org"
EMAIL="david@tethera.net"
** /home/bremner/.reportbugrc:
sign gpg
keyid 922C87617C1A6344A263A7EA0345391B55AA1521!
mode advanced
- -- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.6.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages reportbug depends on:
ii apt 2.1.6
ii python3 3.8.2-3
ii python3-reportbug 7.6.0
ii sensible-utils 0.0.12+nmu1
reportbug recommends no packages.
Versions of packages reportbug suggests:
pn claws-mail <none>
ii debconf-utils 1.5.74
ii debsums 3.0.0
ii dlocate 1.07+nmu1
ii emacs-bin-common 1:26.3+1-2
ii file 1:5.38-5
ii gnupg 2.2.20-1
ii nullmailer [mail-transport-agent] 1:2.2-3
ii python3-urwid 2.0.1-3+b1
pn reportbug-gtk <none>
ii xdg-utils 1.1.3-2
Versions of packages python3-reportbug depends on:
ii apt 2.1.6
ii file 1:5.38-5
ii python3 3.8.2-3
ii python3-apt 2.1.3
ii python3-debian 0.1.37
ii python3-debianbts 3.0.2
ii python3-requests 2.23.0+dfsg-2
ii sensible-utils 0.0.12+nmu1
python3-reportbug suggests no packages.
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl7rh5cACgkQA0U5G1Wq
FSG8ow//avhybWyiIS5FcGVAofVLO3DHvgXqKU8m/VKvhJG+qJ/lVsrM7iQo3Cdx
IqahSOxvcuY8vmvfzlhFIlQfzp3l5gIG8MG0klRTs87q+5Vnp4NyxqzJjAkmMZFU
TSLnMnrc4ov501bUUN94Qipa8zQKwzlRJBM1wXyNBm+reK7M5jwokGDD/wjeYeAE
IQ0HfY6JKsB8S4ISaBsBwKnnQlxDRd83E2h3d7Ro4qv2S6bP18DybcrswmQFMuQC
RoNL7hVKHMZoBSwgTrMYQhPcU6ZNlJ6u4fi84sSZrr3AA1hW2uZMlohAkMYIwAEW
HYtmRRvmeUNxxMiz1MqCz764qtY6YXgpzTZn46aZZD7jOSoMFzzTH12zmGtiUF+A
Naqtmo9Q8P3yPRAx2lseZRcXS1DtKVCBxZXGyOMAdHB+3qbbRyXuN1FI6E62cMpk
2Rnx86P6uamrQ0qA4GzVItMCjvsSoedssE3bhOgS3ybA7cR3GJOfsQlaqUG2G74l
5sM718xckzVDCJXNejzfWJrIy5SiEDQ7uIES6hbFqkPKhW2CzGR8QZslkS6oONFF
MIRt4wiLMojXHmhSDiUKB7SvFCvyi/ng2JAzIE5iqYMxY08GUTqfrNtKIzuiWI4I
Hj78TTGe11U/gqOnKit1SoVYhNgMTME4aAWRBDCtkBW869HrEm8=
=34Sh
-----END PGP SIGNATURE-----
Reply to: