Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 25 Nov 2012 18:59:13 -0600
From:      Tim Daneliuk <tundra@tundraware.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: When Is The Ports Tree Going To Be Updated?
Message-ID:  <50B2BEE1.9030903@tundraware.com>
In-Reply-To: <201211251856.40381.lumiwa@gmail.com>
References:  <50B2A57A.3050500@tundraware.com> <50B2A8D8.90301@FreeBSD.org> <50B2AA07.8090103@tundraware.com> <201211251856.40381.lumiwa@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 11/25/2012 06:56 PM, ajtiM wrote:
> On Sunday 25 November 2012 17:30:15 Tim Daneliuk wrote:
>> On 11/25/2012 05:25 PM, Matthew Seaman wrote:
>>> On 25/11/2012 23:10, Tim Daneliuk wrote:
>>>> After the recent security scare, I know the ports tree was temporarily
>>>> frozen.  Does anyone know when it will again be updates.  I just
>>>> upgraded to 9.1-PRE and need to rebuild Firefox & Thunderbird against
>>>> the new libraries and ... they're broken, marked as security hazards...
>>>
>>> It's been being updated normally since near enough a week ago.
>>> "Normally" means subject to the pre-9.1-RELEASE restrictions on sweeping
>>> changes as is usual at this point in a release cycle.
>>>
>>> FireFox 17 and Thunderbird 17 updates were committed to ports on 20th
>>> November.
>>>
>>> 	Cheers,
>>> 	
>>> 	Matthew
>>
>> Hmmm, something is amiss:
>>
>>     [root]  ~>portsnap update
>>     Ports tree is already up to date.
>>     [root]  ~>cd /usr/ports/www/firefox
>>     [root]  /usr/ports/www/firefox>make
>>     ===>  firefox-16.0.2,1 has known vulnerabilities:
>>     Affected package: firefox-16.0.2,1
>>     Type of problem: mozilla -- multiple vulnerabilities.
>>     Reference:
>> http://portaudit.FreeBSD.org/d23119df-335d-11e2-b64c-c8600054b392.html =>
>> Please update your ports tree and try again.
>>     *** [check-vulnerable] Error code 1
>>
>>     Stop in /usr1/ports/www/firefox.
>>     ** [build] Error code 1
>>
>>     Stop in /usr1/ports/www/firefox.
>
> I use portsnap fetch update and it works...

Ah, maybe that was the problem.  That works for me as well.


----------------------------------------------------------------------------
Tim Daneliuk     tundra@tundraware.com
PGP Key:         http://www.tundraware.com/PGP/




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50B2BEE1.9030903>