#783400 reportbug: include package taint information in reportbug reports

#783400#5
Date:
2015-04-26 18:42:53 UTC
From:
To:
package: reportbug
version: 6.6.3
severity: wishlist

Somewhat often users report bugs that are caused by packages from
non-debian sources, for example #782365 is due to deb-multimedia.org
packages.

It would be nice by default include information about the non-debian
packages on a users system and/or non-debian sources.list in reportbug
reports generated on such systems.  And mark the bug report as tainted
so that the problem is known early and less time is wasted on these
kinds of easily avoidable problems.

Best wishes,
Mike

#783400#10
Date:
2015-05-02 17:14:22 UTC
From:
To:
control: tags -1 + moreinfo

AFAIK there is no way to reliably tell if a package is from Debian repos or not.

how does a non-debian entry in sources.list look like? with debian
mirrors and internal/organizational mirrors, the chance of false
positive/negative is very high.

Regards,

#783400#17
Date:
2015-05-03 22:49:04 UTC
From:
To:
It could be a matter of looking for packages that aren't in a Packages
file with a correct checksum specified by an InRelease file signed by
one of the Debian Archive Signing keys (using files cached in
/var/lib/apt/lists).  If the cache is missing or there is something
wrong, could state that in the report instead.

Best wishes,
Mike

#783400#22
Date:
2015-05-04 00:00:57 UTC
From:
To:
a package could be only in the local cache, because superseded by a
newer version, so it wont be in the Packages and thus the check will
report a fail positive. It seems very fragile. also, this seems like a
very corner case (a package maintain both inside and outside debian,
with a clear "communication breakdown" between the 2 parties), so
either Debian provides a way to retrieve the information if a package
is coming from a Debian archive or not, I not inclined to introduce
another heuristic in reportbug.

Regards,