postponed ports freeze for FreeBSD 9.1-RELEASE?

M

marwis

I've tried to update my Ports tree for the past couple of days with the following result:

Code: 
# portsnap fetch
Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found.
Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done.
Latest snapshot on server matches what we already have.
No updates needed.

To rule out the possibility my usual portsnap server ec2-eu-west-1.portsnap.freebsd.org is out of sync, I tried to change the server manually. No success either.

Code: 
# portsnap -s us.portsnap.freebsd.org fetch
Looking up us.portsnap.freebsd.org mirrors... 6 mirrors found.
Fetching snapshot tag from your-org.portsnap.freebsd.org... done.
Latest snapshot on server matches what we already have.
No updates needed.

After this I searched for "FreeBSD 9.1 ports freeze" and found a dated post from July 25, 2012.

Historically we have done a Feature Freeze at RC1, we are going to try do it with RC2 this time, tentatively scheduled for August 3, subject to schedule slippage.
Click to expand...

Has this Port freeze been postponed until couple of days ago?
 
It's been over a week now and I'm not able to update my ports tree either.

Any ideas when this will be fixed?

Code: 
Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found.
Fetching snapshot tag from your-org.portsnap.freebsd.org... done.
Latest snapshot on server matches what we already have.
No updates needed.
Ports tree is already up to date.

I'm using FreeBSD 7.4
 
Martillo1 said:
So 9.1-RC2 & 9.2-RC3 are compromised as well?
Click to expand...
Not according to http://www.freebsd.org/news/2012-compromise.html
No part of the base FreeBSD system has been put at risk. At no point has the intruder modified any part of the FreeBSD base system software in any way. However, the attacker had access sufficient to potentially allow the compromise of third-party packages. No evidence of this has been found during in-depth analysis, however the FreeBSD Project is taking an extremely conservative view on this and is working on the assumption that third-party packages generated and distributed within a specific window could theoretically have been modified.
Click to expand...
 
You must log in or register to reply here.
Back
Top