> It occurs to me to wonder what's in these files. Could there be a proxy in > the way that's trying to e.g. ask for a password?
In both instances, you can run the `file ...` utility to learn what your
computer might think the file is. For example:
$ file
/opt/local/var/macports/software/libiconv/libiconv-1.14_0.darwin_10.x86_64.tbz2
/opt/local/var/macports/software/libiconv/libiconv-1.14_0.darwin_10.x86_64.tbz2:
bzip2 compressed data, block size = 900k
$ file
/opt/local/var/macports/software/libiconv/libiconv-1.14_0.darwin_10.x86_64.tbz2.rmd160
/opt/local/var/macports/software/libiconv/libiconv-1.14_0.darwin_10.x86_64.tbz2.rmd160:
data
The *.tbz2 file should be an archive of the destroot folder for any given
package, so if you expand it you'd fine the usual opt/local structures inside
it.
The *.rmd160 file is a hash which will just be gibberish, always of a specific
length. If you see HTML in this file or `file ...` tells you it's not just
data, then you are right to assume something is blocking access.
You might find some extra information if you try downloading the files using a
browser:
http://packages.macports.org/libiconv/
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
