Your message dated Fri, 2 Jan 2015 23:06:01 +0000
with message-id
<CAB4XWXzsH6gZ_N=Lj=0vkpz2s-t6p6ht1ssk5kkzf+smlbr...@mail.gmail.com>
and subject line Re: Bug#759433: reportbug should refuse to create a report
about non Debian packages
has caused the Debian Bug report #759433,
regarding reportbug should refuse to create a report about non Debian packages
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.)
--
759433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759433
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: reportbug
Version: 6.5.0+nmu1
Severity: normal
Dear Maintainer,
To reproduce this:
* Add the following line to /etc/apt/sources.list and install libdvdcss2:
echo deb http://www.deb-multimedia.org/ testing main non-free
>>/etc/apt/sources.list
apt-get update
apt-get install libdvdcss2
* Report a bug against libdvdcss2:
reportbug libdvdcss2
reportbug will happily report the bug despite the fact this is not a Debian
package and will only lead to the bug being immediately closed:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759430
Given that reportbug already accesses the Debian servers to grab the list of
bugs for the broken package, it could certainly also check whether that package
actually is a Debian package. This would avoid wasted time on both sides.
Alternately, given that it correctly identifies the package maintainer, it
could print a warning and offer to email the bug report to him directly.
-- Package-specific info:
** Environment settings:
EDITOR="vi"
INTERFACE="text"
** /home/fgouget/.reportbugrc:
reportbug_version "4.7"
mode standard
ui text
email "[email protected]"
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages reportbug depends on:
ii apt 1.0.6
ii python 2.7.8-1
ii python-reportbug 6.5.0+nmu1
reportbug recommends no packages.
Versions of packages reportbug suggests:
pn claws-mail <none>
pn debconf-utils <none>
ii debsums 2.0.52+nmu2
ii dlocate 1.02+nmu3
ii emacs23-bin-common 23.4+1-4.1+b1
ii exim4 4.84-1
ii exim4-daemon-light [mail-transport-agent] 4.84-1+b1
ii file 1:5.19-1
ii gnupg 1.4.18-2
ii python-gtk2 2.24.0-3+b1
ii python-gtkspell 2.25.3-13
pn python-urwid <none>
ii python-vte 1:0.28.2-5
ii xdg-utils 1.1.0~rc1+git20111210-7.1
Versions of packages python-reportbug depends on:
ii apt 1.0.6
ii python 2.7.8-1
ii python-debian 0.1.22
ii python-debianbts 1.12
ii python-support 1.0.15
python-reportbug suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello,
> Given that reportbug already accesses the Debian servers to grab the list of
> bugs for the broken package, it could certainly also check whether that
> package actually is a Debian package. This would avoid wasted time on both
> sides.
>
> Alternately, given that it correctly identifies the package maintainer, it
> could print a warning and offer to email the bug report to him directly.
Sadly there is no reliable way to determine if a package is in Debian
or not, hence I can implement the requested fix.
Regards,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--- End Message ---
_______________________________________________
Reportbug-maint mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
