From: Jeroen Roovers <jer@gentoo.org>
To: Matt Turner <mattst88@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites: =x11-drivers/nvidia-drivers-375* =x11-drivers/nvidia-drivers-378* =x11-drivers/nvidia-drivers-381* =x11-drivers/nvidia-drivers-384* =x11-drivers/nvidia-drivers-387* =x11-drivers/nvidia-drivers-396*
Date: Sun, 16 Dec 2018 20:40:00 +0100 [thread overview]
Message-ID: <20181216204000.18747088@wim.jer> (raw)
In-Reply-To: <CAEdQ38GeUC6Ybh_-tfSZ7YVj3Rv=7=29RtDK84K-Z1WKVkTBQg@mail.gmail.com>
On Fri, 14 Dec 2018 12:03:52 -0800
Matt Turner <mattst88@gentoo.org> wrote:
> Thanks. What do we want to do about -304?
It's not on the list above because it's a "legacy driver", not a
"short lived" branch[1]. It's not relevant in this context what happens
to the 304 branch, the context being a cleanup of intermediate branches
that were abandoned and surpassed by "long lived" branches.
> It still requires xorg-server-1.19 which I'd like to drop due to a
> security vulnerability. After the listed versions are gone, -304 will
> be the only thing keeping 1.19 in tree.
I see no open security bug report for this. If we had one of those, then
we could write a package.mask entry for both xorg-server and
nvidia-drivers with a reference to the security issue, or add the
branches that are now masked for removal. That way people can plan
their hardware's obsolescence properly or shift to a different driver.
Kind regards,
jer
[1] https://www.nvidia.com/object/IO_32667.html
next prev parent reply other threads:[~2018-12-16 19:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 14:04 [gentoo-dev] Last rites: =x11-drivers/nvidia-drivers-375* =x11-drivers/nvidia-drivers-378* =x11-drivers/nvidia-drivers-381* =x11-drivers/nvidia-drivers-384* =x11-drivers/nvidia-drivers-387* =x11-drivers/nvidia-drivers-396* Jeroen Roovers
2018-12-14 20:03 ` Matt Turner
2018-12-16 19:40 ` Jeroen Roovers [this message]
2018-12-16 19:45 ` Matt Turner
2018-12-16 21:12 ` Mart Raudsepp
2018-12-16 21:54 ` Jeroen Roovers
2018-12-16 22:20 ` Jeroen Roovers
2018-12-17 17:25 ` Matt Turner
2018-12-15 8:53 ` Kent Fredric
2018-12-16 19:41 ` Jeroen Roovers
2018-12-16 22:14 ` Kent Fredric
2018-12-16 22:32 ` [gentoo-dev] " Jeroen Roovers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181216204000.18747088@wim.jer \
--to=jer@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mattst88@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox