Date: Mon, 6 May 2019 22:18:02 +1000 From: Kubilay Kocak <koobs@FreeBSD.org> To: lev@FreeBSD.org, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Cc: FreeBSD Ports Security Team <ports-secteam@freebsd.org> Subject: Re: svn commit: r500915 - head/devel/subversion-lts Message-ID: <391a0a82-1892-a1bf-cc72-8e1cc5892a65@FreeBSD.org> In-Reply-To: <239b5e72-ab45-c28d-b224-f1d487639fca@FreeBSD.org> References: <201905061158.x46BwmWZ072987@repo.freebsd.org> <bc2d3b32-976b-36b6-f674-627247ab080e@FreeBSD.org> <239b5e72-ab45-c28d-b224-f1d487639fca@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/05/2019 10:09 pm, Lev Serebryakov wrote: > On 06.05.2019 15:02, Kubilay Kocak wrote: > >> Will this be added to security/vuxml and will it be MFH'd ? > It is "new" port, it could not be merged to quarterly. > > And this vulnerability is already in security/vuxml, for other ports. > Good question is, should I fix this old security/vuxml record? > Since its the same underlying vulnerability, I'd amend the existing vuxml entry (4af3241d-1f0c-11e9-b4bd-d43d7eed0ce2) - Adding a second <package> entry for subversion-lts I'd probably also remove "www/mod_dav_svn" from the topic, as if affects multiple port/package names.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?391a0a82-1892-a1bf-cc72-8e1cc5892a65>