Getting started is to difficult

I’m having some trouble getting started at all.

I wanted to try out Pijul for a repo shared between two of my computers.
I started with ‘cargo install pijul’ (installing version 0.9) on both and setting up a repo on one and, trying to clone with az@pcname:/repopath.
This is failing with a ‘cant read key error’. Having had ssl key errors before i wanted to dive into the source code and see what’s up. So i try to clone pijul from nest. This just gives me an empty directory ( likely because of some upgrade to 0.9 as far as i gather ) .

So this was all very disappointing so far.
What i would have liked is a way to get the source (and the dependencies) and edit them. With crates on github i can just clone and update deps to local versions. But i can’t easily find the sources of pijul and its deps.

For me what would have made it better , was a line on the download page saying .

  • if you don’t have pijul yet , you get the source from our read-only github mirror at…/ -

The issue with the sources is that the nest (the site which hosts the source repo) is currently down because of the migration from 0.8 to 0.9 requiring a conversion (please note that Pijul is still alpha).

Btw, if you install from cargo, you can find the source code for both pijul, libpijul and trussh in your $HOME/.cargo/registry/src folder.

Hi! Sorry for the late answer, and sorry if Pijul is in a weird state right now. First of all, I did maintain a GitHub mirror for a while, but this yielded no contribution for about a year or so, and required time, so I decided to drop it.

However, one way to get Pijul from source is to first install it from (which you already know how to do if you know some Rust: cargo install pijul), and then pijul clone or pijul clone, the SSH version being often faster).

I’d be interested in hearing more about your key problems, what version of Pijul are you using? The two major changes in Pijul 0.9 were:

  • simplification of some of our algorithms, which meant a new patch format.
  • OpenSSL and Libsodium instead of *ring* to deal with SSH keys (that one was actually in a new version of Thrussh, our SSH library). This was supposed to extend our support for different SSH key versions significantly, so I look forward to hearing more about your story. Can you for instance generate a key of the same type (i.e. with the same -t option in ssh-keygen, and a password if your key has a password), with the same version of OpenSSH, and paste it in a discussion in
1 Like