pijul_org / pijul

#34 pijul init only uses current directory

Opened by berkowski, on April 4, 2017
Closed
berkowski commented on April 4, 2017

pijul init does not seem to accept the optional directory name when creating a repository in 0.4.1

Starting with a bare directory:

$ ls -a $ pijul init test_repo $ ls -a .pijul

Creating the directory first does not seem to work either:

$ mkdir test_repo $ ls -a test_repo $ pijul init test_repo $ ls -a .pijul test_repo $ ls -a test_repo $

pmeunier commented on April 4, 2017

Thanks for reporting! Apparently, the recent change in repository format created a big mess, and our versions are a bit confused.

I can't replicate on my machine, unfortunately. But it seems your pijul is working, could you try to get the version on the nest, and test again?

pijul get berkowski@nest.pijul.com:pijul_org/pijul

This can also be done over HTTP, if you prefer:

pijul get https://nest.pijul.com/pijul_org/pijul
berkowski commented on April 4, 2017

get is failing as well...

$ pijul get berkowski@nest.pijul.com:pijul_org/piju

error: Found argument 'get' which wasn't expected, or isn't valid in this context

USAGE:
    pijul [SUBCOMMAND]

For more information try --help

And there is no get command in the output of --help

$ pijul --help
pijul 0.4.1
Pierre-√Čtienne Meunier and Florent Becker
Version Control: fast, distributed, easy to use; pick any three

USAGE:
    pijul [SUBCOMMAND]

FLAGS:
    -h, --help       Prints help information
    -V, --version    Prints version information

SUBCOMMANDS:
    add              add a file to the repository
    apply            apply a patch
    branches         List all branches
    changes          List the patches applied to the given branch
    checkout         Change the current branch
    clone            clone a remote branch
    delete-branch    Delete a branch in the local repository
    fork             Create a new branch
    help             Prints this message or the help of the given subcommand(s)
    info             Get information about the current repository, if any
    init             Create a new repository
    ls               list tracked files
    mv               Change file names
    patch            Output a patch (in binary)
    pull             pull from a remote repository
    push             push to a remote repository
    record           record changes in the repository
    remove           remove file from the repository
    revert           Rewrite the working copy from the pristine
    status           show what would be recorded if record were called
    unrecord         Unrecord some patches (remove them without reverting them)

For what it's worth I installed via cargo as directed by https://pijul.com/documentation/install/

pmeunier commented on April 4, 2017

Sorry, I meant "clone" instead of "get". Darcs has both, which is why I got confused.

berkowski commented on April 4, 2017

Ah, OK. This does seem to be fixed in the latest (AdY3c-T0k...). Now I can get to poking around, thanks!