[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#917846: marked as done (/usr/bin/querybts: querybts doesn't find bug that exists)



Your message dated Mon, 31 Dec 2018 10:27:18 -0500
with message-id <CAB4XWXxo=9yJxQWi2KONUJBgisoCobYOQCYaTw3PPKesrTgg+A@mail.gmail.com>
and subject line Re: Bug#917846: /usr/bin/querybts: querybts doesn't find bug that exists
has caused the Debian Bug report #917846,
regarding /usr/bin/querybts: querybts doesn't find bug that exists
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 owner@bugs.debian.org
immediately.)


-- 
917846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917846
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: reportbug
Version: 7.5.1
Severity: important
File: /usr/bin/querybts

Dear Maintainer,

   * What led up to the situation?

When doing an upgrade I got a warning that there is a grave bug in gimp:
grave bugs of gimp (2.10.8-1 → 2.10.8-2) <Outstanding>
 b1 - #917782 - [gimp] Missing symbol

So, I wanted to read more about it and used querybts on it with the following results:
$ querybts 917782
Retrieving report #917782 from Debian bug tracking system...
No report available: #917782
No bug reports found.

But that doesn't make sense, as this bug really exists!

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?

I tried several times more. I have no problems with my internet connection and
also under root I get the same result.

   * What outcome did you expect instead?

Just expected to get bug info about that bug...

-- Package-specific info:
** Environment settings:
EDITOR="vim"

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-1-amd64 (SMP w/4 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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages reportbug depends on:
ii  apt                1.8.0~alpha2
ii  python3            3.7.1-3
ii  python3-reportbug  7.5.1
ii  sensible-utils     0.0.12

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail                                 <none>
pn  debconf-utils                              <none>
pn  debsums                                    <none>
pn  dlocate                                    <none>
pn  emacs24-bin-common | emacs25-bin-common    <none>
ii  exim4-daemon-light [mail-transport-agent]  4.91-9
ii  file                                       1:5.34-2
ii  gnupg                                      2.2.12-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.8.0~alpha2
ii  file               1:5.34-2
ii  python3            3.7.1-3
ii  python3-apt        1.7.0
ii  python3-debian     0.1.33
ii  python3-debianbts  2.7.2
ii  python3-requests   2.20.0-2

python3-reportbug suggests no packages.

-- Configuration Files:
/etc/reportbug.conf changed:
submit
query-bts
cc
config-files
compress
email "Manuel.Bilderbeek@gmail.com"
realname "Manuel Bilderbeek"
editor "gvim -f"
verify


-- no debconf information

--- End Message ---
--- Begin Message ---
this has been fixed, closing

On Mon, Dec 31, 2018 at 5:45 AM Nis Martensen <nis.martensen@web.de> wrote:
>
> On 31 Dec 2018 Manuel Bilderbeek wrote:
> > $ querybts 917782
> > Retrieving report #917782 from Debian bug tracking system...
> > No report available: #917782
> > No bug reports found.
> >
> > But that doesn't make sense, as this bug really exists!
>
> Thanks for the report. The actual bug is in python-debianbts (tracked in
> #917165), one of the libraries reportbug depends on.
>
> I'm not reassigning or closing this bug, in order to keep it visible to
> reportbug users and help avoid further duplicates. This bug will be
> closed once it is fixed in the proper package.
>


-- 
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 ---

Reply to: