Thanks Ryan for the suggestions. I did use sudo of course but I wasn’t sure
about Xcode. I fired it up and license was agreed to. I tried the self update
again just to be safe and the same error message was returned. I have no
explanation for this.
Mike
> On Dec 21, 2015, at 11:08 PM, Ryan
Might be a silly question but do you have enough disk space and or inodes
available to create the required files/directories? Maybe try relaxing the
permissions temporarily? The ownership and permissions are the same as
mine and I have no issues running selfupdate.
On Dec 17, 2015 7:58 PM, "Mr.
> On Dec 17, 2015, at 6:08 PM, Mr. Michael Wilson
> wrote:
>
> I had not updated my ports in a while and when I tried I got this with sudo
> port -v selfupdate...
>
> ---> Updating MacPorts base sources using rsync
> receiving file list ... done
>
> sent 36 bytes
I had not updated my ports in a while and when I tried I got this with sudo
port -v selfupdate...
---> Updating MacPorts base sources using rsync
receiving file list ... done
sent 36 bytes received 69 bytes 19.09 bytes/sec
total size is 27013120 speedup is 257267.81
receiving file list ...
Looks good to me. I’m stumped.
drwxr-xr-x 5 root admin - 170 Dec 17 18:47
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/
se
Mike
> On Dec 17, 2015, at 7:16 PM, Brandon Allbery wrote:
>
> ls -ldeO@
>
Hi!
When i m trying to sync ports tree using subversion, the following command
giving error
$svn co http://svn.macports.org/repository/macports/trunk/dports/ .
Error:
svn: E175002: Unable to connect to a repository at URL '
http://svn.macports.org/repository/macports/trunk/dports'
svn:
On April 11, 2015 6:31:04 AM EDT, Ryan Schmidt ryandes...@macports.org wrote:
On Apr 11, 2015, at 2:50 AM, Pragati Srivastava wrote:
When i m trying to sync ports tree using subversion, the following
command giving error
$svn co http://svn.macports.org/repository/macports/trunk/dports/ .
Thanks Ryan: turned out I had XCode 3.2.3 installed, so I've upgraded to
the latest version and re-installed Macports and now everything's running
fine.
On 10 April 2012 01:19, Ryan Schmidt ryandes...@macports.org wrote:
On Apr 9, 2012, at 19:07, James Benstead wrote:
Thanks Ryan, Jim.
On Apr 9, 2012, at 13:39, James Benstead wrote:
Thanks Ryan. Logfile attached. The error message created this time is as
follows (long):
jims-mbp-2:~ jim$ sudo port -v selfupdate
[snip]
checking Xcode location... xcode-select: Error: No Xcode folder is set. Run
xcode-select -switch
Thanks Ryan, Jim.
I think I've now resolved the problem with the XCode location, but on
attempting to run selfupdate again I'm hitting what appears to be a similar
problem with the gcc compiler. What should I try next? From the log:
configure:2945: checking Xcode location
configure:2948:
On Apr 9, 2012, at 19:07, James Benstead wrote:
Thanks Ryan, Jim.
I think I've now resolved the problem with the XCode location, but on
attempting to run selfupdate again I'm hitting what appears to be a similar
problem with the gcc compiler. What should I try next? From the log:
On Apr 8, 2012, at 20:36, James Benstead wrote:
On running sudo port selfupdate I get the following error:
jims-mbp-2:default jim$ sudo port selfupdate
--- Updating the ports tree
--- Updating MacPorts base sources using rsync
MacPorts base version 1.9.2 installed,
MacPorts base
12 matches
Mail list logo