Your message dated Fri, 17 Feb 2017 01:20:09 +0100
with message-id <[email protected]>
and subject line Re: Bug#855230: RM: virglrenderer -- RoQA; many security bugs,
orphaned without new maintainer
has caused the Debian Bug report #855230,
regarding RM: virglrenderer -- RoQA; many security bugs, orphaned without new
maintainer
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
855230: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855230
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
Hi
virglrenderer was orphaned, since qemu, one of the consumers reverted
the corresponding support. virglrenderer is collecting an increasing
amount of security issues detected, cf. [1].
Please remove virglrenderer from the archive. It can be included in a
later stage again once it has an active maintainer and virglrenderer
going to stabilize more.
Regards,
Salvatore
[1] https://security-tracker.debian.org/tracker/source-package/virglrenderer
--- End Message ---
--- Begin Message ---
On 17.02.2017 00:44, Scott Kitterman wrote:
> On February 16, 2017 6:36:39 PM EST, Andreas Cadhalpun
> <[email protected]> wrote:
>> Please don't remove virglrenderer, since it's planned to re-enable
>> the virgl support in qemu for buster [2]. Removing it now, just to
>> add it back again soon seems quite pointless.
>> All the known security issues are fixed upstream with the 0.6.0
>> release.
>
> Does that mean you are going to maintain it?
Probably, if nobody else does it. ;)
> If so, I'd suggest you upload the fixed version to unstable taking
> over maintainership and make sure there's an RC bug to keep it out of stretch.
I'll work on that.
> If that's all correct, then go ahead and close this bug.
Doing so now.
Best regards,
Andreas
--- End Message ---
