Package: reportbug Version: 7.5.0 Severity: important Dear Maintainer, for several months, I reported without problems about the bugnumber 885947 (the last correct was on 23-Jul-2018).
>From 29-Jul-2018, this command fails to recover the report, with messages '500 >Internal Server Error' and 'No report available'. $ reportbug -N 885947 *** Welcome to reportbug. Use ? for help at prompts. *** . . . Retrieving report #885947 from Debian bug tracking system... b'<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">\n<html><head>\n<title>500 Internal Server Error</title>\n</head><body>\n<h1>Internal Server Error</h1>\n<p>The server encountered an internal error or\nmisconfiguration and was unable to complete\nyour request.</p>\n<p>Please contact the server administrator at \n ow...@bugs.debian.org to inform them of the time this error occurred,\n and the actions you performed just before this error.</p>\n<p>More information about this error may be available\nin the server error log.</p>\n<hr>\n<address>Apache Server at bugs.debian.org Port 443</address>\n</body></html>\n' No report available: #885947 No such bug report. If I try other bugnumbers, several work fine (825930, 904391) but some work badly (750587) with the same error. $ reportbug -N 825930 *** Welcome to reportbug. Use ? for help at prompts. *** . . . Retrieving report #825930 from Debian bug tracking system... What do you want to do now? [N|x|o|r|b|e|q|?]? q Exiting. $ reportbug -N 904391 *** Welcome to reportbug. Use ? for help at prompts. *** . . . Retrieving report #904391 from Debian bug tracking system... What do you want to do now? [x|O|r|b|e|q|?]? q Exiting. $ reportbug -N 750587 *** Welcome to reportbug. Use ? for help at prompts. *** . . . Retrieving report #885947 from Debian bug tracking system... b'<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">\n<html><head>\n<title>500 Internal Server Error</title>\n</head><body>\n<h1>Internal Server Error</h1>\n<p>The server encountered an internal error or\nmisconfiguration and was unable to complete\nyour request.</p>\n<p>Please contact the server administrator at \n ow...@bugs.debian.org to inform them of the time this error occurred,\n and the actions you performed just before this error.</p>\n<p>More information about this error may be available\nin the server error log.</p>\n<hr>\n<address>Apache Server at bugs.debian.org Port 443</address>\n</body></html>\n' No report available: #885947 No such bug report. Is it a bug in this package or is it a problem in the bug report? How can I now inform the maintainer of bugnumber 885947? Regards. -- Package-specific info: ** Environment settings: INTERFACE="text" ** /home/iotest/.reportbugrc: reportbug_version "7.1.7" mode novice ui text realname "Santiago" email "yg2...@hotmail.com" no-cc header "X-Debbugs-CC: yg2...@hotmail.com" smtphost reportbug.debian.org -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES.UTF-8 (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 1.6.3 ii python3 3.6.5-3 ii python3-reportbug 7.5.0 ii sensible-utils 0.0.12 reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail <none> ii debconf-utils 1.5.69 ii debsums 2.2.3 pn dlocate <none> pn emacs24-bin-common | emacs25-bin-common <none> ii exim4-daemon-light [mail-transport-agent] 4.91-6 ii file 1:5.33-3 ii gnupg 2.2.9-1 pn python3-urwid <none> pn reportbug-gtk <none> ii xdg-utils 1.1.3-1 Versions of packages python3-reportbug depends on: ii apt 1.6.3 ii file 1:5.33-3 ii python3 3.6.5-3 ii python3-apt 1.6.2 ii python3-debian 0.1.32 ii python3-debianbts 2.7.2 ii python3-requests 2.18.4-2 python3-reportbug suggests no packages. -- no debconf information
