Hi Ben,
thanks for your report.
On Mon, Mar 28, 2011 at 05:53, Ben Hutchings <b...@decadent.org.uk> wrote:
> Package: reportbug
> Version: 5.0
> Severity: normal
>
> If a user tries to report a bug on 'kernel', they are redirected to
> 'linux-2.6'. Since that is not the name of a binary package, they
> then get a long list of packages to choose from:
>
> 1 firmware-linux-free Binary firmware for various drivers in the
> Linux kernel
> 2 linux-base Linux image base package
> [...]
> 18 linux-image-2.6.32-5-amd64 Linux 2.6.32 for 64-bit PCs
> 19 linux-image-2.6.37-2-amd64 Linux 2.6.37 for 64-bit PCs
> 20 linux-image-2.6.38-1-amd64 Linux 2.6.38 for 64-bit PCs
> [...]
> 37 linux-2.6 Source package
>
> Possibly as a result of this, we get a fair number of reports against
> linux-base or linux-2.6 (source package) which should have been made
> against the appropriate linux-image package. These reports do not
> include much of the useful information that our bug script would
> generate.
>
> I tried installing a bug script for linux-2.6 as if it was a binary
> package, but that just confuses reportbug:
>
> Looking up status of additional packages...
> Traceback (most recent call last):
> File "/usr/bin/reportbug", line 2127, in <module>
> main()
> File "/usr/bin/reportbug", line 1052, in main
> return iface.user_interface()
> File "/usr/bin/reportbug", line 1726, in user_interface
> package, [[x] for x in supplemental], rel='is related to')
> File "/usr/lib/pymodules/python2.6/reportbug/utils.py", line 627, in
> get_dependency_info
> for info in get_package_info(dependencies):
> File "/usr/lib/pymodules/python2.6/reportbug/utils.py", line 583, in
> get_package_info
> vers = versob.search(p).group('vers')
> AttributeError: 'NoneType' object has no attribute 'group'
Nah, that's another bug (#616455) :) I ran:
sudo cp -a /usr/share/bug/linux-image-2.6.38-1-amd64/ /usr/share/bug/linux-2.6
and reporting a bug against linux-2.6 actually calls the
presubj/script+subscripts as if it was a binpkg. I don't know if
providing such directory could be feasable for you, but at least we
have a chance.
> Please can you redirect 'kernel' to 'linux-image-$(uname -r)' instead
> when reportbug is running on Linux?
as said in your presubj, it might happen that the reporter is not
running the kernel with problems (because it doesn't boot or so): what
should reportbug do in this case? still trying to assing it to
'linux-image-$(uname -r)' ? Another interesting question is: what to
do if the reporter is running a custom-built kernel but wants to
report a bug for a Debian kernel?
> (You should presumably do
> something different on kFreeBSD.)
And what would that be? :) /me haz no freebsd to play with.
Cheers,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
