On Thu, 6 Feb 2020, Nis Martensen wrote:
> hinted at above: By default reportbug shows the list of bugs belonging
> to the source package of the target package, while "affects:" are more
> likely to be set for binary target packages. Really showing a more
Indeed, I set affects to the binary
control: tags -1 patch
On 3 Sep 2009 James Vega wrote:
>
> In doing a little more poking around, I see this is only an issue when
> using querybts on a source package. This may simply be an artifact of
> screen-scraping the BTS, but I'd have to do some tests with the BTS'
> SOAP interface to
On Tue, 7 Jan 2020, Thorsten Glaser wrote:
> This bug’s still pertinent and leads to reported duplicates:
This needs to be priorised and fixed, it is ridiculous:
Merged with [15]949645, [16]949646, [17]949647, [18]949648, [19]949650,
[20]949657, [21]949668
Tons of bugreport duplicates
Package: reportbug
Version: 7.6.0
Followup-For: Bug #544812
This bug’s still pertinent and leads to reported duplicates:
Querying Debian BTS for reports on kmod (source)...
5 bug reports found:
Bugs with severity serious
1) #939779 kmod FTBFS: dh_makeshlibs: The udeb libkmod2-udeb does not
Package: reportbug
Version: 4.6
Severity: wishlist
Now that debbugs has the affects feature, pkgreport.cgi will show bugs
which have been marked as affecting a given package (commonly for bugs
in libraries or other leaf packages). Reportbug should do something
similar in its bug listing.
--
5 matches
Mail list logo
