Your message dated Mon, 29 May 2017 13:23:30 -0400
with message-id
<cab4xwxxnrnf+je1k1qm8srdbe2wq+cj9zozvnoqlojc55pw...@mail.gmail.com>
and subject line Re: [Reportbug-maint] Bug#840003: reportbug: wrong reporting
about bug
has caused the Debian Bug report #840003,
regarding reportbug: wrong reporting about bug
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
840003: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840003
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: reportbug
Version: 6.6.6
Severity: important
Here's the captured console log.
Need to get 0 B/89.4 MB of archives.
After this operation, 11.5 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
critical bugs of cryptsetup (2:1.7.0-2 → 2:1.7.2-2) <Outstanding>
b1 - #839994 - Newest version prevent boot of full encrypted disk
Summary:
cryptsetup(1 bug)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...] 839994
Retrieving report #839994 from Debian bug tracking system...
No report available: #839994
No bug reports found.
Are you sure you want to install/upgrade the above packages? [Y/n/?/...] 839994
Retrieving report #839994 from Debian bug tracking system...
No report available: #839994
No bug reports found.
Are you sure you want to install/upgrade the above packages? [Y/n/?/...] 839994
Retrieving report #839994 from Debian bug tracking system...
What do you want to do now? [N|x|o|r|b|e|q|?]?
As you can see, in the 3rd attempt, it was able to fetch the report. The
first 2 attempts failed because my router's ISP network was down.
Now, I expected reportbug to fail stating network timeout, with an
exception, or maybe a nice relevant message.
But instead it gave me the wrong impression that #839994 is not an
available/valid bug report.
-- Package-specific info:
** Environment settings:
DEBEMAIL="[email protected]"
DEBFULLNAME="Ritesh Raj Sarraf"
INTERFACE="text"
** /home/rrs/.reportbugrc:
reportbug_version "6.6.3"
mode advanced
editor "editor"
ui text
realname "Ritesh Raj Sarraf"
email "[email protected]"
no-cc
header "X-Debbugs-CC: [email protected]"
smtphost reportbug.debian.org
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (990, 'unstable'), (990, 'testing'), (500, 'unstable-debug'),
(500, 'testing-debug'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.8.0brk0+ (SMP w/4 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages reportbug depends on:
ii apt 1.3.1
ii python-reportbug 6.6.6
pn python:any <none>
reportbug recommends no packages.
Versions of packages reportbug suggests:
pn claws-mail <none>
pn debconf-utils <none>
pn debsums <none>
pn dlocate <none>
pn emacs23-bin-common | emacs24-bin-common <none>
ii file 1:5.28-4
ii gnupg 2.1.15-3
ii postfix [mail-transport-agent] 3.1.0-5+b1
ii python-gtk2 2.24.0-5
pn python-gtkspellcheck <none>
ii python-urwid 1.3.1-2+b1
pn python-vte <none>
ii xdg-utils 1.1.1-1
Versions of packages python-reportbug depends on:
ii apt 1.3.1
ii file 1:5.28-4
ii python-debian 0.1.29
ii python-debianbts 2.6.1
pn python:any <none>
python-reportbug suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, Oct 7, 2016 at 1:14 PM, Ritesh Raj Sarraf <[email protected]> wrote:
>> were there actual timeouts/network issues at that time? it could also
>> be something on the BTS side
>
> There was an actual power outage affecting my ISP cable modem. My wifi router
> was on because it was backed by my UPS.
>
> So, for this bug report, it was an actual network issue.
well, so you know what caused the issue.... closing
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi
--- End Message ---
_______________________________________________
Reportbug-maint mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
