authentication works, but then it hangs
I don’t have a pijul directory now. because ssh do not work…
did you install pijul beta9 from crates first ?
Beta9 with some package Manager in Windows…
now clone pijul from nest via https and build pijul from nest
i could clone and build. but when i try:
ssh -T nest.pijul.com
…
Authenticated to nest.pijul.com ([3.254.166.252]:22) using “publickey”.
debug1: channel 0: new session [client-session] (inactive timeout: 0)
debug1: Entering interactive session.
debug1: pledge: filesystem
and then it stucks
why? Why? you do ssh -T against nest? 
Do this for github.
At least do something useful. Do you have any questions about Pijul?
Because If use Clone with ssh, IT still ASK me for Passwort and it doesn’t work…
did you upload ssh pub key to nest ?
Yes, i don’t know why IT doesen’t Work…
perfect, we move fast to destination.
now go and read how to fix it in link i post 3 days ago.
pijul remote I5GEGWCQIJKTINCFGJEEIVZXKU: pijul/pijul pijul
error: unrecognized subcommand ‘I5GEGWCQIJKTINCFGJEEIVZXKU:’
Usage: pijul remote [OPTIONS] [COMMAND]
For more information, try ‘–help’.
pijul remote is just command all next is output from it
C:\Users\alexa\pijul\pijul>cd pijul-remote
C:\Users\alexa\pijul\pijul\pijul-remote>notepad Cargo.toml
C:\Users\alexa\pijul\pijul\pijul-remote>cargo update
Updating crates.io index
Locking 1 package to latest compatible version
Updating thrussh v0.34.1 → v0.35.6
Removing thrussh-libsodium v0.3.0
note: pass --verbose to see 40 unchanged dependencies behind latest
C:\Users\alexa\pijul\pijul\pijul-remote>cd …
C:\Users\alexa\pijul\pijul>cargo build --release
warning: C:\Users\alexa\pijul\pijul\pijul-remote\Cargo.toml: default_features is deprecated in favor of default-features and will not work in the 2024 edition
(in the keyring dependency)
Compiling libpijul v1.0.0-beta.10 (C:\Users\alexa\pijul\pijul\libpijul)
warning: unexpected cfg condition value: deterministic_hash
→ libpijul\src\lib.rs:79:7
|
79 | #[cfg(feature = “deterministic_hash”)]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: expected values for feature are: canonical-path, default, flate2, ignore, lru-cache, mmap, ondisk-repos, path-slash, tar, tarball, tempfile, text-changes, zstd, and zstd-seekable
= help: consider adding deterministic_hash as a feature in Cargo.toml
= note: see https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html for more information about checking conditional configuration
= note: #[warn(unexpected_cfgs)] on by default
warning: unexpected cfg condition value: deterministic_hash
→ libpijul\src\lib.rs:81:11
|
81 | #[cfg(not(feature = “deterministic_hash”))]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: expected values for feature are: canonical-path, default, flate2, ignore, lru-cache, mmap, ondisk-repos, path-slash, tar, tarball, tempfile, text-changes, zstd, and zstd-seekable
= help: consider adding deterministic_hash as a feature in Cargo.toml
= note: see https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html for more information about checking conditional configuration
warning: field is_cyclic is never read
→ libpijul\src\diff\diff.rs:80:9
|
75 | pub struct Replacement {
| ----------- field in this struct
…
80 | pub is_cyclic: bool,
| ^^^^^^^^^
|
= note: Replacement has a derived impl for the trait Debug, but this is intentionally ignored during dead code analysis
= note: #[warn(dead_code)] on by default
warning: field conflict_type is never read
→ libpijul\src\diff\vertex_buffer.rs:23:9
|
20 | pub struct Conflict {
| -------- field in this struct
…
23 | pub conflict_type: ConflictType,
| ^^^^^^^^^^^^^
|
= note: Conflict has derived impls for the traits Clone and Debug, but these are intentionally ignored during dead code analysis
warning: non-local impl definition, impl blocks should be written at the same level as their item
→ libpijul\src\text_encoding.rs:68:9
|
64 | / fn deserialize(deserializer: D) → Result<Self, D::Error>
65 | | where
66 | | D: serde::Deserializer<'de>,
| |____________________________________- move the impl block outside of this associated function deserialize
67 | {
68 | impl<'de> Visitor<'de> for EncodingVisitor {
| ^^^^^^^^^^-------^^^^^^^^^^---------------
| | |
| | EncodingVisitor is not local
| Visitor is not local
|
= note: an impl is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the impl
= note: #[warn(non_local_definitions)] on by default
Compiling pijul-repository v0.0.1 (C:\Users\alexa\pijul\pijul\pijul-repository)
Compiling pijul-identity v0.0.1 (C:\Users\alexa\pijul\pijul\pijul-identity)
Compiling pijul-remote v1.0.0-beta.6 (C:\Users\alexa\pijul\pijul\pijul-remote)
warning: libpijul (lib) generated 5 warnings
Compiling pijul v1.0.0-beta.9 (C:\Users\alexa\pijul\pijul\pijul)
warning: use of deprecated type alias std::panic::PanicInfo: use PanicHookInfo instead
→ pijul\src\main.rs:149:5
|
149 | setup_panic!();
| ^^^^^^^^^^^^^^
|
= note: #[warn(deprecated)] on by default
= note: this warning originates in the macro $crate::setup_panic which comes from the expansion of the macro setup_panic (in Nightly builds, run with -Z macro-backtrace for more info)
warning: use of deprecated type alias std::panic::PanicInfo: use PanicHookInfo instead
→ pijul\src\main.rs:149:5
|
149 | setup_panic!();
| ^^^^^^^^^^^^^^
|
= note: this warning originates in the macro $crate::setup_panic which comes from the expansion of the macro setup_panic (in Nightly builds, run with -Z macro-backtrace for more info)
warning: use of deprecated associated function chrono::NaiveDateTime::from_timestamp_opt: use DateTime::from_timestamp instead
→ pijul\src\commands\record.rs:268:44
|
268 | chrono::NaiveDateTime::from_timestamp_opt(t, 0).unwrap(),
| ^^^^^^^^^^^^^^^^^^
warning: use of deprecated associated function chrono::NaiveDateTime::from_timestamp_opt: use DateTime::from_timestamp instead
→ pijul\src\commands\tag.rs:291:40
|
291 | chrono::NaiveDateTime::from_timestamp_opt(t, 0).unwrap(),
| ^^^^^^^^^^^^^^^^^^
warning: pijul (bin “pijul”) generated 4 warnings
Finished release profile [optimized] target(s) in 1m 03s
C:\Users\alexa\pijul\pijul>cd
C:\Users\alexa\pijul\pijul
C:\Users\alexa\pijul\pijul>pijul clone 19aklopf84@nest.pijul.com:19aklopf84/mynewproject
Warning: Unable to automatically authenticate with server. Please make sure your SSH keys have been uploaded to the Nest.
For more information, please visit Uploading public keys - The Pijul manual
Error: Not authenticated. Please check your credentials and try again.
C:\Users\alexa\pijul\pijul>
my ssh config:
Pijul Nest SSH-Zugang
Host nest.pijul.com
User 19aklopf84
IdentityFile C:\Users\alexa.ssh\id_ed25119
IdentitiesOnly yes
PreferredAuthentications publickey
LogLevel DEBUG
pijul not using ssh config.
ok i gave ssh config away. if i want to clone, it asks me for password.
did you upload correct key to nest?
yes i uploaded correct key