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 wrote:
>
>> On 3/03/2014 6:22 PM, Andrew Berg wrote:
>>> On 2014.03.03 01:20, Dmitry Sivachenko wr
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 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
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
Sorry if I wasn't more clear, my ports tree was updated a few minutes
before I wrote the email, from March 3 @ 0700 UTC... and the patch for
CVE-2014-1912 was already in /usr/ports/lang/python33/files... otherwise I
never would have updated the port! I always verify changes with the FreeBSD
svn web
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.
___
freebsd-python@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-python
T
I already fixed that yesterday, update your ports tree.
> 03 марта 2014 г., в 11:05, JEREMY COX написал(а):
>
> Hello all,
> I was having difficulty updating python33 today, even though the
> vulnerability to python 3.3.3_2 (CVE-2014-1912) was patched. After
> verifying with Freshports python 3
Hello all,
I was having difficulty updating python33 today, even though the
vulnerability to python 3.3.3_2 (CVE-2014-1912) was patched. After
verifying with Freshports python 3.3.3_3 was correct, I used
*portmaster -m DISABLE_VULNERABILITIES=yes python33*
to update the port. However, pkg audit i
