Great, glad to hear you're in business!

On Thursday, February 12, 2015, Eric S <[email protected]> wrote:

> I deleted Julia and the Julia folder and reinstalled. Now it installs and
> I can perform the Pkg.update() and Pkg.add() without errors.
>
> Eric
>
> On Thursday, February 12, 2015 at 2:59:53 PM UTC-6, Kevin Squire wrote:
>>
>> Hi Eric,
>>
>> Sorry, I saw this, but wasn't able to respond easily when I did.
>>
>> Is it still the case that there is no .julia/v0.3 directory?  If there
>> isn't, then somehow you've gotten .julia into an inconsistent state where
>> there's no v0.3 directory, and yet julia thinks it's initialized (per the
>> output of Pkg.init()).
>>
>> Even if that's not true, the next easiest thing to try would be to rename
>> (or delete) your .julia directory, and then rerun the Pkg.init() command.
>>
>> Kevin
>>
>> On Thu, Feb 12, 2015 at 12:37 PM, Eric S <[email protected]> wrote:
>>
>>> Kevin,
>>>
>>> Your suggestion about "Pkg.init()" didn't work. Any others?
>>>
>>> Eric
>>>
>>> On Sunday, February 8, 2015 at 12:51:11 PM UTC-6, Kevin Squire wrote:
>>>>
>>>> Yep! If you run "Pkg.init()", then try everything again, I think that
>>>> should fix it.
>>>>
>>>> On Sun, Feb 8, 2015 at 10:28 AM, Eric S <[email protected]> wrote:
>>>>
>>>>> Perhaps this is a clue. On my iMac, in the  ~ .julia directory there
>>>>> is a folder named "v0.3". There is no equivalent folder on my MacBook Air.
>>>>> The Pkg.update() works on my iMac and not my MacBook Air. The iMac is
>>>>> pretty new and this was the first installation of Julia. The MacBook Air
>>>>> had a previous installation of JuliaStudio on it.
>>>>>
>>>>> Eric
>>>>>
>>>>>
>>>>> On Sunday, February 8, 2015 at 12:07:29 PM UTC-6, Eric S wrote:
>>>>>>
>>>>>> If by the usual message you meet the following, then I think yes:
>>>>>>
>>>>>> Erics-iMac:~ ericshain$ git
>>>>>>
>>>>>> usage: git [--version] [--help] [-C <path>] [-c name=value]
>>>>>>
>>>>>>            [--exec-path[=<path>]] [--html-path] [--man-path]
>>>>>> [--info-path]
>>>>>>
>>>>>>            [-p|--paginate|--no-pager] [--no-replace-objects] [--bare]
>>>>>>
>>>>>>            [--git-dir=<path>] [--work-tree=<path>]
>>>>>> [--namespace=<name>]
>>>>>>
>>>>>>            <command> [<args>]
>>>>>>
>>>>>>
>>>>>> The most commonly used git commands are:
>>>>>>
>>>>>>    add        Add file contents to the index
>>>>>>
>>>>>>    bisect     Find by binary search the change that introduced a bug
>>>>>>
>>>>>>    branch     List, create, or delete branches
>>>>>>
>>>>>>    checkout   Checkout a branch or paths to the working tree
>>>>>>
>>>>>>    clone      Clone a repository into a new directory
>>>>>>
>>>>>>    commit     Record changes to the repository
>>>>>>
>>>>>>    diff       Show changes between commits, commit and working tree,
>>>>>> etc
>>>>>>
>>>>>>    fetch      Download objects and refs from another repository
>>>>>>
>>>>>>    grep       Print lines matching a pattern
>>>>>>
>>>>>>    init       Create an empty Git repository or reinitialize an
>>>>>> existing one
>>>>>>
>>>>>>    log        Show commit logs
>>>>>>
>>>>>>    merge      Join two or more development histories together
>>>>>>
>>>>>>    mv         Move or rename a file, a directory, or a symlink
>>>>>>
>>>>>>    pull       Fetch from and integrate with another repository or a
>>>>>> local branch
>>>>>>
>>>>>>    push       Update remote refs along with associated objects
>>>>>>
>>>>>>    rebase     Forward-port local commits to the updated upstream head
>>>>>>
>>>>>>    reset      Reset current HEAD to the specified state
>>>>>>
>>>>>>    rm         Remove files from the working tree and from the index
>>>>>>
>>>>>>    show       Show various types of objects
>>>>>>
>>>>>>    status     Show the working tree status
>>>>>>
>>>>>>    tag        Create, list, delete or verify a tag object signed with
>>>>>> GPG
>>>>>>
>>>>>>
>>>>>> 'git help -a' and 'git help -g' lists available subcommands and some
>>>>>>
>>>>>> concept guides. See 'git help <command>' or 'git help <concept>'
>>>>>>
>>>>>> to read about a specific subcommand or concept.
>>>>>>
>>>>>> Erics-iMac:~ ericshain$
>>>>>>
>>>>>> On Sunday, February 8, 2015 at 11:41:39 AM UTC-6, Kevin Squire wrote:
>>>>>>>
>>>>>>> Not sure if that helps. Does running git by itself produce a usage
>>>>>>> message?
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Feb 8, 2015 at 9:08 AM, Eric S <[email protected]> wrote:
>>>>>>>
>>>>>>>> Perhaps I should clarify one thing. I'm running Julia by
>>>>>>>> double-clicking the "Julia-0.3.5.app". It launches the terminal and 
>>>>>>>> seems
>>>>>>>> to run within a terminal window.
>>>>>>>>
>>>>>>>> Eric
>>>>>>>>
>>>>>>>> On Sunday, February 8, 2015 at 11:04:32 AM UTC-6, Eric S wrote:
>>>>>>>>>
>>>>>>>>> This is what I get when running the command (copied and pasted
>>>>>>>>> into the terminal):
>>>>>>>>>
>>>>>>>>> Erics-MacBook-Air:~ ericshain$ git 
>>>>>>>>> --git-dir=/Users/ericshain/.julia/.cache/Stats
>>>>>>>>> merge-base 78f5810a78fa8bee684137d703d21eca3b1d8c78
>>>>>>>>> 8208e29af9f80ef633e50884ffb17cb25a9f5113
>>>>>>>>>
>>>>>>>>> Erics-MacBook-Air:~ ericshain$
>>>>>>>>>
>>>>>>>>> Does this help?
>>>>>>>>>
>>>>>>>>> Eric
>>>>>>>>>
>>>>>>>>> On Sunday, February 8, 2015 at 7:42:39 AM UTC-6, Kevin Squire
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Sat, Feb 7, 2015 at 6:33 PM, Seth <[email protected]>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Saturday, February 7, 2015 at 3:03:14 PM UTC-8, Eric S wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> That is what I get running Julia from the Terminal.
>>>>>>>>>>>>
>>>>>>>>>>>> Eric
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> Can you run git from the command line? I'm wondering whether you
>>>>>>>>>>> need to accept the license agreement or something.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Yes, what Seth said--sorry I wasn't clearer.  Specifically, what
>>>>>>>>>> happens when you run
>>>>>>>>>>
>>>>>>>>>> *git --git-dir=/Users/ericshain/.julia/.cache/Stats merge-base
>>>>>>>>>> 78f5810a78fa8bee684137d703d21eca3b1d8c78
>>>>>>>>>> 8208e29af9f80ef633e50884ffb17cb25a9f5113*
>>>>>>>>>>
>>>>>>>>>> at the command line.
>>>>>>>>>>
>>>>>>>>>> Kevin
>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>
>>

Reply via email to