$ pijul clone tankf33der@nest.pijul.com::tankf33der/pil21
Repository not found, or insufficient permissions
<HANG>
^C
$

Or this path tankf33der@nest.pijul.com/tankf33der/pil21/kkk

Hang is silence:

$ pijul clone ftp://nest.pijul.com/tankf33der/pil21
^C

I’ve just fixed the issues with SSH, I can’t reproduce the other one (ftp). Let’s see if fixing #257 will solve it for you.

The same hang on ftp with all todays changes.

I couldn’t reproduce this, because ftp seems to be a hostname for you, and Pijul tried to connect to host ftp using the SSH protocol in this case.

The patch I just pushed (#GYXIF25T2BCTCWCQI5DQOF3F4HBWDJUDJUMZ2WLHVBIOYATJTFAQC) fixes this. I would be curious to know whether it fixes your other issue with the .config (I can’t reproduce that issue).

I cant believe you cant reproduce issue inside s1/s2 dir tree.

A lot of dirs deleted in /home/mpech, it tried delete full mpech dir, /home/mpech/.config is just critical and I notified fast.

I dont see GYX commit nor in “Changes” or “CI” tabs.

You can pull it with --from-channel :260, that is, pijul pull tankf33der@nest.pijul.com:pijul/pijul --from-channel :260.

Come on!

Remember those three wrong URLs: 1,2,3;

Legend: OK or FAIL (deletes);

Latest pijul from nest:

Manjaro-ArchLinux - FAIL FAIL FAIL
Ubuntu 20.04 LTS - OK FAIL FAIL
Fedora Rawhide - OK FAIL FAIL

I could indeed reproduce the last two FAILs, the first one might be due to filesystem differences.

Anyway, I’ve just pushed two patches that fix this, by first testing which directories exist, and cleanup only those directories that didn’t exist when the command started. Since this is really serious, I’m republishing a version of libpijul and pijul now.

And once again: good job! Thanks a million for your work on this.