Pushing changes to the repository we’re in blocks (presumably due to trying to lock the repository multiple times). If this isn’t supported (makes sense), it should probably fail explicitly with an error.

$ pijul push .
^C

(Why would I be doing this? I thought pijul push --to-channel channel . might be a way to move changes to a channel after I missed to pijul record --channel.)

Right, I made a mistake with Thrussh lately, but published a fix this morning. Would you mind trying again after a cargo update / cargo install on Pijul itself?

Edit: I misread the report. You were right to think this way, and Pijul is wrong (it’s trying to take a lock on the repository twice).

Thanks for this report, I’ve just fixed this by adding a new variant of remotes: local channels.

#76PCXGML77EZWTRI5E6KHLVRAFTJ2AB5YRN5EKOYNAPKTWY2KCGAC