Macports updating Cam sara sexy web

done sent 36 bytes received 77 bytes 75.33 bytes/sec total size is 512 speedup is 4.53 receiving file list ... The location of the Tcl framework has changed, breaking the existing Mac Ports infrastructure.

rsync: change_dir "tarballs/Port Index_darwin_13_i386" (in release) failed: No such file or directory (2) done sent 4 bytes received 9 bytes 26.00 bytes/sec total size is 0 speedup is 0.00 rsync error: some files could not be transferred (code 23) at /Source Cache/rsync/rsync-42/rsync/main.c(1400) [receiver=2.6.9] Command failed: /usr/bin/rsync -rtzv --delete-after rsync:// Index_darwin_13_i386/Port Index /opt/local/var/macports/sources/ Exit code: 23 --- Mac Ports base is outdated, installing new version 2.2.1 Installing new Mac Ports release in /opt/local as root:admin; permissions 0755; Tcl-Package in /Library/Tcl checking build system type... The 2.2.1 installer for Mavericks has since become available here.

Once Mac Ports has been installed you need to apply available updates by running the following: available, installing it if appropriate, and updates your ports tree to the latest version.

This step should be done every now and again to ensure you are running the latest version, of both Mac Ports base and the ports tree.

done sent 36 bytes received 69 bytes 210.00 bytes/sec total size is 4925440 speedup is 46908.95 receiving file list ... /usr/bin/cc checking whether the C compiler works... --- Extracting gperf Error: org.macports.extract for port gperf returned: command execution failed Please see the log file for port gperf for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gperf/gperf/Error: Problem while installing gperf To report a bug, follow the instructions in the guide: $ Updating Mac Ports base sources using rsync receiving file list ...

However, the use of a custom compiler can provide certain advantages: A quicker first-time build of MIRIAD because the Mac Port version of GCC doesn’t need to be built.

2) If svn fails too, you can try using Daily tarball.

You can test the changes by running "sudo port -d sync" Note: If the https fails, you can replace it with http.

There is a reason why Mac Ports doesn't attempt to install a package when a dependency fails to build.

This exact question has been discussed on the macports-users mailing list not so long ago: Considering an old closed ticket, a defect that was fixed: 333 (dependancy failure are ignored and port continues to try and install) – Mac Ports If I understand correctly: to continue following a failure may, in some cases, be defective.