On 31.08.19 07:07, Nis Martensen wrote:
I've just tried that out, I didn't manage to find the bug with https://www.debian.org/Bugs/ and I've got not a single idea how to properly search on https://udd.debian.org/bugs/ .On 29 Aug 2019 Michael Meier wrote:I wanted to report a bug for linux-image-5.2.0-2-amd64. I've used reportbug-ng to find out if the bug was already reported. Yes, I know it's not maintainedanymore, but it still just works better to find existing bug reports.The bug was already reported. The Bug number is 935852. Then I wanted to addsome information to the bug so I've tried to find it again with querybts linux-image-5.2.0-2-amd64 But it doesn't find it at all, it also can't find it for linux-image-amd64 or any other similar package I've tried out.Thank you for the report. I've tried to reproduce and can confirm the problem. However, I don't think this is a bug in reportbug:- The binary package names you list (linux-image-5.2.0-2-amd64, linux-image-amd64) belong to the source package linux-signed-amd64.- The bug you've been looking for was reported against a different source package (linux). Reportbug doesn't query bug reports across multiple source packages, so the bug was evidently not listed.To search bugs across different packages, you are better off using a web search, see https://www.debian.org/Bugs/ or https://udd.debian.org/bugs/ Such complex bug searches are beyond what is reasonable for a simple tool like reportbug.
Probably it would be possible to somehow find them over those pages. But when I want to report a bug, I usually just want to make sure nobody reported it yet, on which i don't want to spend more than a minute. And since reportbug shows me already reported bugs, I expect that if no report similar to mine shows up, that it hasn't been reported yet. It basically was just an accident that I've noticed that the bug was already reported against an other source package. Anyway, I guess that problem only appears with the linux kernel? So it would be the only one which would get double bug reports because of that.
I've noticed there are quite a few bug reports for the kernel 5.2.0 which seemingly were reported against the other source package, so you can't find them when reporting against linux-image-5.2.0 .
Maybe it would be possible to somehow make sure, those bug reports are bundled at the same place, but I guess that's not the responsibility of reportbug.
I'm not familiar with reportbug-ng so I cannot tell how you managed to find the bug there. In any case, if you already have the bug number and want to submit followup information, you canIn reportbug-ng I've just entered as package linux-image-5.2.0-2-amd64 and it found all relevant bug reports for it.
use "reportbug -N $BUG".
Thanks. that actually helps :-).