Date: Mon, 03 Mar 2014 22:21:47 +1100 From: Kubilay Kocak <koobs.freebsd@gmail.com> To: JEREMY COX <jeremy.m.cox@gmail.com>, freebsd-python@freebsd.org Cc: antoine@FreeBSD.org Subject: Re: pyhon33 still listed as vulnerable Message-ID: <531465CB.7080107@FreeBSD.org> In-Reply-To: <CAPH9q1pv5YnSVLjDZwYsH1LoQS-sHiVBiHiKL1LnEkEYa16Y3g@mail.gmail.com> References: <CAPH9q1p0vzjzmhyeQKqMp=JWp22sMJPSa4vBywEcgAgYuKojqA@mail.gmail.com> <B09BA639-565A-40C6-A5E1-46555213BE8B@gmail.com> <53142DA3.9000604@gmail.com> <53143F24.500@FreeBSD.org> <CAPH9q1pv5YnSVLjDZwYsH1LoQS-sHiVBiHiKL1LnEkEYa16Y3g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/03/2014 8:45 PM, JEREMY COX wrote: > pkg audit -F was the correct solution. Thank you very much for the > assistance! > > Regards, > Jeremy > > > On Mon, Mar 3, 2014 at 2:36 AM, Kubilay Kocak <koobs.freebsd@gmail.com>wrote: > >> On 3/03/2014 6:22 PM, Andrew Berg wrote: >>> On 2014.03.03 01:20, Dmitry Sivachenko wrote: >>>> I already fixed that yesterday, update your ports tree. >>> I have this issue as well on a fresh ports tree. >> >> Does updating the vulnerability database help? Either via: >> >> pkg audit -F if using pkg, or portaudit -F if using portaudit >> >> >> > My pleasure Jeremy, thank you for bringing it to our attention. Full credit to antoine@ for the hint -- koobs
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?531465CB.7080107>