Re: Archive fetch problem

2011-10-12 Thread Scott Webster
Yup, works now. I really don't remember ever touching that part of the config file. Anyway, if this comes up again for someone else it probably means that there was a macports upgrade path that caused people to have that specified by default. Hopefully there aren't too many other people out ther

Re: Archive fetch problem

2011-10-12 Thread Jeremy Lavergne
> portarchivetype tgz > > I've never adjusted that manually. Should I set it to tbz2 or just > comment it out? Commenting out should do the trick; the default is currently tbz2. smime.p7s Description: S/MIME cryptographic signature ___ macpo

Re: Archive fetch problem

2011-10-12 Thread Scott Webster
On Wed, Oct 12, 2011 at 2:50 PM, Jeremy Lavergne wrote: > Check your macports.conf: is there a archive type set? > Hmmm: portarchivetype tgz I've never adjusted that manually. Should I set it to tbz2 or just comment it out? Thanks, Scott __

Re: Archive fetch problem

2011-10-12 Thread Jeremy Lavergne
Check your macports.conf: is there a archive type set? Scott Webster wrote: >Here's a snippet of a recent upgrade: > >---> Fetching archive for cmake >DEBUG: Executing org.macports.archivefetch (cmake) >---> cmake-2.8.6_0.darwin_10.x86_64.tgz doesn't seem to exist in >/opt/local/var/macports/s

Archive fetch problem

2011-10-12 Thread Scott Webster
Here's a snippet of a recent upgrade: ---> Fetching archive for cmake DEBUG: Executing org.macports.archivefetch (cmake) ---> cmake-2.8.6_0.darwin_10.x86_64.tgz doesn't seem to exist in /opt/local/var/macports/software/cmake ---> Attempting to fetch cmake-2.8.6_0.darwin_10.x86_64.tgz from http: