Pijul

Where is Pijul / Pijul Nest bug tracker?


#1

Like other open source software, I expect there to be some public issue tracker.

For example, It can be a issues in a Github repository (the code inside may be content of latest Pijul release).

Here is some list of issues I’d submitted:

  • Pijul asks for SSH key’s password even if it is already in ssh agent, if trying to use invalid account on Nest;
  • Attempt to clone, but not providing a value password leaves incompletely cloned repository interfering with futher clone attempts;
  • Missing verbose mode that shows details of SSH connection (but not that excessively verbose like RUST_LOG=debug). RUST_LOG=info shows seemingly nothing.
  • Pijul’s SSH client asks password for the next key even when the password is the same as already entered password;
  • Pijul asks password for “nest.pijul.com” in a loop without even telling that it’s incorrect password. SSH keys’ protection passwords are asked once, but reaction to valid and invalid password is also the same.
  • Documentation recommends cloning Pijul from the Nest using pijul clone me@nest.pijul.com:pijul_org/pijul command without specifying that me should be replaced by your account name (unlike in Github where git@... stays the same).

(that’s before cloning and playing with it).


#2

I’m not sure I understand the question, but we wrote Pijul to be better and more automated than Git (especially on merges), so we won’t use Git or GitHub now that Pijul is starting to work.

The bug tracker is https://nest.pijul.com/pijul_org/pijul/discussions

Please check that you’re using the latest version before reporting a bug, though, I believe the problems you’re talking about were fixed by thrussh-keys 0.11.9 (and cargo install pijul --force will fix your problem).