On Fri, Aug 29, 2014 at 12:37 PM, Lawrence Velázquez
wrote:
> > sh: error: /usr/bin/rsync -rtzv --delete-after rsync://
> rsync.macports.org/release/tarballs/base.tar
> /opt/local/var/macports/sources/rsync.macports.org/release/tarballs: No
> such file or directory
>
Somehow the whole command is
On Aug 29, 2014, at 8:02 AM, Ryan Schmidt wrote:
> However I would not think this difference would matter. I'm afraid I'm at a
> loss for why your system claims that files and directories that exist don't
> exist. There is something unusual about your computer, but I cannot figure
> out what i
Le Vendredi 29 Août 2014 14:19 CEST, Ryan Schmidt a
écrit:
>
> On Aug 29, 2014, at 4:05 AM, nb wrote:
>
> > I'm coming from Debian world (i386). When I had to report a bug, I received
> > an automatic notification and a bug number.
>
> This will also happen with the MacPorts issue tr
On Aug 29, 2014, at 4:05 AM, nb wrote:
> I'm coming from Debian world (i386). When I had to report a bug, I received
> an automatic notification and a bug number.
This will also happen with the MacPorts issue tracker—when you file a ticket.
However when you comment on an existing ticket, you w
On Aug 29, 2014, at 4:05 AM, nb wrote:
>
> Hello guys,
>
> I'm very new to Mac world, one week only.
> I don't know very well this list rules, so I'll try to do the minimum.
Welcome!
> I'm coming from Debian world (i386). When I had to report a bug, I received
> an automatic notification and
On Aug 29, 2014, at 5:59 AM, David Nicholls wrote:
>
> Doing a macports install after upgrading to Mavericks, and the above error is
> reported.
>
> Since quite a lot of important stuff depends on this, how do I work around it?
Nothing depends on llvm-3.1, except clang-3.1:
$ port echo depend
On Aug 29, 2014, at 5:32 AM, vignesh babu wrote:
>
> drwxr-xr-x4 root wheel 136 Aug 29 11:20 opt
> |- drwxr-xr-x 11 root admin 374 Aug 29 11:21 local
>
> It doesn't look like a symlink.. highlighted is the only difference as I go
> down the path. Only the opt folder belongs to wh
I found a solution online: https://trac.macports.org/ticket/41116
I had not read all the way to the bottom of the migration instructions:
https://trac.macports.org/wiki/Migration
So I'm winding back the old macports using time machine before doing the job
properly. The upgrade seems like a rat
Doing a macports install after upgrading to Mavericks, and the above error is
reported.
Since quite a lot of important stuff depends on this, how do I work around it?
DN
__
David Nicholls
Research School of Astronomy & Astrophysics
Mt Stromlo Observatory
Institute for Advanced Studies
Au
drwxr-xr-x4 root wheel 136 Aug 29 11:20 opt
|- drwxr-xr-x 11 root admin 374 Aug 29 11:21 local
It doesn't look like a symlink.. highlighted is the only difference as I go
down the path. Only the opt folder belongs to wheel group & everything down
the path is admin. I don't know how
Hello guys,
I'm very new to Mac world, one week only.
I don't know very well this list rules, so I'll try to do the minimum.
I'm coming from Debian world (i386). When I had to report a bug, I received an
automatic notification and a bug number.
I want to use gnucash with python bindings because
> On Aug 29, 2014, at 3:03 AM, vignesh babu wrote:
>
> Hi,
>
> I managed to run the rsync on the terminal and extracted the base & ports tar
> file. Upon the command, sudo port -v install arm-linux-gnueabi-gcc @4.6.2_1 ,
Note that the "install" command does not take a version number.
> the
Hi,
I managed to run the rsync on the terminal and extracted the base & ports
tar file. Upon the command, sudo port -v install arm-linux-gnueabi-gcc
@4.6.2_1 , the following message was thrown:
The highlighted text seems to be similar error like the self update error.
Do you think its related to
13 matches
Mail list logo