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

[debian blue]

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 helps.

On Sun, Oct 29, 2017 at 12:14 PM, Andreas Beckmann <a...@debian.org> wrote:

> 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 like
>
> Bugs: mailto:aut...@example.com
>
> this address will be used as recipient instead of the Debian BTS.
>
>
> Andreas
>

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

[debian blue]

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
> > 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.
>
>
> Andreas
>