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

Bug#808867: marked as done (reportbug: Bug against snappy (src:snappy-player) reported against src:snappy)

Your message dated Sat, 12 Feb 2022 22:51:40 +0100
with message-id <36d0534d-67e7-149f-7864-4f03a122aa25@web.de>
and subject line Re: reportbug: Bug against snappy (src:snappy-player) reported against src:snappy
has caused the Debian Bug report #808867,
regarding reportbug: Bug against snappy (src:snappy-player) reported against src:snappy
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.)


-- 
808867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808867
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: reportbug
Version: 6.6.5
Severity: normal

This is somewhat strange:

The snappy package comes from the source package snappy-player, whereas
there also is a snappy source package that builds some development
libraries.

reportbug snappy fails, it will report the bug against Source: snappy
instead of Package: snappy.

-- Output

$ reportbug snappy
Detected character set: UTF-8
Please change your locale if this is incorrect.

Using 'Julian Andres Klode <jak@debian.org>' as your from address.
Getting status for snappy...
Which of the following packages is the bug in?

1 libsnappy-dev  fast compression/decompression library (development files)

2 libsnappy1     fast compression/decompression library

3 libsnappy1v5   fast compression/decompression library

4 snappy         Powerful media player with a minimalistic interface

Select one of these packages: 4
Please enter the version of the package this report applies to (blank OK)
> 
Will send report to Debian (per lsb_release).
Querying Debian BTS for reports on snappy (source)...
1 bug report found:

Bugs with severity wishlist
  1) #748627  libsnappy-dev: Static archive unsuitable for linking into dynamic object
(1-1/1) Is the bug you found listed above [y|N|b|m|r|q|s|f|e|?]? n



-- Package-specific info:
** Environment settings:
EDITOR="editor"
DEBEMAIL="jak@debian.org"
EMAIL="Julian Andres Klode <jak@debian.org>"

** /home/jak/.reportbugrc:
reportbug_version "3.99.0"
mode expert
no-cc
header "X-Debbugs-CC: jak@debian.org"
mutt

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

Kernel: Linux 4.4.0-rc5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages reportbug depends on:
ii  apt               1.1.6~jak1
ii  python            2.7.11-1
ii  python-reportbug  6.6.5
pn  python:any        <none>

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail                               <none>
ii  debconf-utils                            1.5.58
pn  debsums                                  <none>
pn  dlocate                                  <none>
pn  emacs23-bin-common | emacs24-bin-common  <none>
ii  esmtp-run [mail-transport-agent]         1.2-12
ii  file                                     1:5.25-2
ii  gnupg                                    1.4.20-1
ii  python-gtk2                              2.24.0-4
pn  python-gtkspell                          <none>
pn  python-urwid                             <none>
pn  python-vte                               <none>
ii  xdg-utils                                1.1.1-1

Versions of packages python-reportbug depends on:
ii  apt               1.1.6~jak1
ii  python-debian     0.1.27
ii  python-debianbts  2.6.0
pn  python:any        <none>

python-reportbug suggests no packages.

-- no debconf information

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.

--- End Message ---
--- Begin Message --- 
On 03.10.2021 Nis Martensen wrote:
> On 23 Dec 2015 Julian Andres Klode wrote:
>> Package: reportbug
>> Version: 6.6.5
>> Severity: normal
>>
>> This is somewhat strange:
>>
>> The snappy package comes from the source package snappy-player, whereas
>> there also is a snappy source package that builds some development
>> libraries.
>>
>> reportbug snappy fails, it will report the bug against Source: snappy
>> instead of Package: snappy.
> 
> Are you sure? The output you pasted below only shows which package was
> used when looking for existing bugs, not which package the new bug will
> be reported against.
> 
> When retrieving existing bugs reportbug uses a somewhat wider query to
> increase the likelyhood of finding all relevant bugs.
> 
> I intend to close this bug when the next version of reportbug is uploaded.

No new evidence for this being a bug has turned up. Closing.

--- End Message ---
Reply to: