Bug#879485: vhba-dkms: Upgrade vhba-dkms from vhba-20140928 to vhba-20170610

Ok. I was thinking more in the lines of "reportbug" doing a "apt-cache policy " to check if the package is associated with a debian supported repo and issue a warning to the user before reporting the bug. Though user could have removed a repo after installing the package, but a warning still

Bug#879485: vhba-dkms: Upgrade vhba-dkms from vhba-20140928 to vhba-20170610

On 10/28/2017 08:41 PM, debian blue wrote: > Sorry .. realized it was a custom deb package install. > > Is there a way for "reportbug" to detect and avoid this ? Yes and no. It needs cooperation from the package in the third party repository. If that sets a Bugs: header in the package metadata

Bug#879485: vhba-dkms: Upgrade vhba-dkms from vhba-20140928 to vhba-20170610

Sorry .. realized it was a custom deb package install. Is there a way for "reportbug" to detect and avoid this ? On Fri, Oct 27, 2017 at 10:49 PM, Andreas Beckmann wrote: > On Sun, 22 Oct 2017 12:36:47 +0530 "debian.blue" > wrote: > > Package: vhba-dkms

Bug#879485: vhba-dkms: Upgrade vhba-dkms from vhba-20140928 to vhba-20170610

On Sun, 22 Oct 2017 12:36:47 +0530 "debian.blue" wrote: > Package: vhba-dkms > Version: 20140928-1 Hi, this package is not part of Debian (nor could I find traces that it was in Debian at some point in the past). Please report problems to whomever provides this package.

Bug#879485: vhba-dkms: Upgrade vhba-dkms from vhba-20140928 to vhba-20170610

Package: vhba-dkms Version: 20140928-1 Severity: important Dear Maintainer, vhba module fails to build on kernels > 4.11.rc2, as shown below. This issue has been fixed upstream in https://sourceforge.net/p/cdemu/code/ci/7dc0d29a3ef6e45455f537c8187791446ca7e1e5/ [ root@sys: