In this case I let the automated app store magick happen. This will frustrate anyone who has a large installation of Macs that need to install Xcode on but that is a discussion for another time. Upgrading Xcode is no longer a simple download (weighing in at a hefty 1.65GB) in that you must use the AppStore in order to attain access to the binaries. To report a bug, follow the instructions in the guide: > Attempting to fetch adns-1.4_0.darwin_12.x86_64.tbz2.rmd160Įrror: The installed version of Xcode (2.0orlower) is too old to Another positive was that the error was pretty explicit, identifying the source of the problem which was an incompatibility between well the source and the compiler. nothing is more frustrating than building a large project from source only to have it explode during the last stage of package registration. I figured what’s the worst that could happen right? Unfortunately for me as you’ll note form the output this command failed. Port upgrade outdated Xcode (Photo credit: Wikipedia)īeing the adventurous tech guy that I am I ran the upgrade outdated command as directed. > MacPorts base is already the latest version Permissions 0755 Tcl-Package in /Library/TclĮrror: /opt/local/bin/port: port selfupdate failed:Įrror installing new MacPorts base: command execution failedĪt this point I resorted to using the latest packaged installer for Mountain Lion and one that was completed I reran the self update just to reassure myself that things were right. Installing new MacPorts release in /opt/local as root:admin > MacPorts base is outdated, installing new version 2.2.0 > Updating MacPorts base sources using rsync As promising as the update started after a few minutes the results ended up in failure as demonstrated by the following output: While it may seem like small change to upgrade to 2.2.0 from 2.1.2 unfortunately, there were issues. Initially as a shot in the dark I attempted to run a self update. While it may seem logical upon reading it was a lot of trial and error (mostly error) to reach this point. I hope that writing this will help some future self avoid the pain points I did experienced during this process. so given the Linux box says it supports xattrs why does it throw a complaint about extended-attributes being requested by the Mac ?įWIW the Mac is running OS X 10.6.1 & The server is running Ubuntu 2.6.28-15-generic - both machines are running with up to date standard packages (no special flavours of rsync installed on either side beyond what ships by default).Recently I upgraded one of my Macs to Mountain Lion and subsequently need to upgrade the installation of MacPorts. Socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, LINUX (Server/Remote): rsync version 3.0.5 protocol version 30Ħ4-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints, Inplace, IPv6, 64-bit system inums, 64-bit internal inums MAC (Client/Local): rsync version 2.6.9 protocol version 29Ĭapabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, clear enough error, however -v shows the following for the two machines: Rsync error: error in rsync protocol data stream (code 12) at /SourceCache/rsync/rsync-37.3/rsync/io.c(452) Rsync: connection unexpectedly closed (0 bytes received so far) Rsync error: syntax or usage error (code 1) at main.c(1441) Rsync: on remote machine: -extended-attributes: unknown option Hullo all - I'm using rsync to back up from my mac to a fileserver runnning linux, and I see the following error: rsync -e ssh -va圎 -delete -ignore-errors 192.168.1.3:/bkup/mac/Users/dave/ password:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |