serokell/deploy-rs
1
1
Fork 0
mirror of https://github.com/serokell/deploy-rs.git synced 2024-11-29 01:02:26 +03:00
Code Issues Projects Releases Wiki Activity
88b3059b02
deploy-rs/Cargo.lock

1162 lines
30 KiB
Plaintext
Raw Normal View History

stuff
2020-09-28 20:48:21 +03:00
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
version = 3
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "aho-corasick"
[#202] Provide '^out' suffix for deriver on newer nix Problem: Since 2.15 nix no longer reference '.drv' as derivation outputs. At the same time, nix before '2.13' doesn't support '.drv' special suffix handling. Solution: Provide '^out' suffix for the profile deriver in case 'nix path-info <...>.drv' returns the same '<...>.drv' path. In other cases either an error about the build result not being present in the /nix/store is returned or an actual build result path is returned.
2023-04-18 10:28:39 +03:00
version = "0.7.20"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[#202] Provide '^out' suffix for deriver on newer nix Problem: Since 2.15 nix no longer reference '.drv' as derivation outputs. At the same time, nix before '2.13' doesn't support '.drv' special suffix handling. Solution: Provide '^out' suffix for the profile deriver in case 'nix path-info <...>.drv' returns the same '<...>.drv' path. In other cases either an error about the build result not being present in the /nix/store is returned or an actual build result path is returned.
2023-04-18 10:28:39 +03:00
checksum = "cc936419f96fa211c1b9166887b38e5e40b19958e5b895be7c1f93adec7071ac"
stuff
2020-09-28 20:48:21 +03:00
dependencies = [
"memchr",
]
[[package]]
name = "atty"
version = "0.2.14"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d9b39be18770d11421cdb1b9947a45dd3f37e93092cbf377614828a319d5fee8"
dependencies = [
"hermit-abi",
"libc",
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
"winapi",
stuff
2020-09-28 20:48:21 +03:00
]
[[package]]
name = "autocfg"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cdb031dd78e28731d87d56cc8ffef4a8f36ca26c38fe2de700543e627f8a464a"
[[package]]
name = "bitflags"
version = "1.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cf1de2fe8c75bc145a2f577add951f8134889b4795d47466a54a5c846d691693"
[[package]]
name = "bytes"
update tokio
2021-07-15 00:55:57 +03:00
version = "1.0.1"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update tokio
2021-07-15 00:55:57 +03:00
checksum = "b700ce4376041dcd0a327fd0097c41095743c4c8af8887265942faf1100bd040"
stuff
2020-09-28 20:48:21 +03:00
Use crude Nix parsing for parsing the flake path
2020-11-29 21:51:52 +03:00
[[package]]
name = "cbitset"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "29b6ad25ae296159fb0da12b970b2fe179b234584d7cd294c891e2bbb284466b"
dependencies = [
"num-traits",
]
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "cfg-if"
version = "0.1.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4785bdd1c96b2a846b2bd7cc02e86b6b3dbf14e7e53446c4f54c92a361040822"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
[[package]]
name = "cfg-if"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "baf1de4339761588bc0619e3cbc0120ee582ebb74b53b4efbf79117bd2da40fd"
Replace logger, add more logging options including files
2020-12-27 20:48:18 +03:00
[[package]]
name = "chrono"
version = "0.4.19"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "670ad68c9088c2a963aaa298cb369688cf3f9465ce5e2d4ca10e6e0098a1ce73"
dependencies = [
"libc",
"num-integer",
"num-traits",
"time",
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
"winapi",
Replace logger, add more logging options including files
2020-12-27 20:48:18 +03:00
]
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "clap"
version = "3.0.0-beta.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4bd1061998a501ee7d4b6d449020df3266ca3124b941ec56cf2005c3779ca142"
dependencies = [
"atty",
"bitflags",
"clap_derive",
"indexmap",
"lazy_static",
"os_str_bytes",
"strsim",
"termcolor",
optimize release build for size
2021-08-04 18:03:05 +03:00
"terminal_size",
stuff
2020-09-28 20:48:21 +03:00
"textwrap",
"unicode-width",
"vec_map",
]
[[package]]
name = "clap_derive"
version = "3.0.0-beta.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "370f715b81112975b1b69db93e0b56ea4cd4e5002ac43b2da8474106a54096a1"
dependencies = [
"heck",
"proc-macro-error",
"proc-macro2",
"quote",
"syn",
]
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
[[package]]
name = "crossbeam-channel"
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
version = "0.5.8"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
checksum = "a33c2bf77f2df06183c3aa30d1e96c0695a313d4f9c453cc3762a6db39f99200"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
dependencies = [
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
"cfg-if 1.0.0",
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
"crossbeam-utils",
]
[[package]]
name = "crossbeam-utils"
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
version = "0.8.15"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
checksum = "3c063cd8cc95f5c377ed0d4b49a4b21f632396ff690e8470c29b3359b346984b"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
dependencies = [
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
"cfg-if 1.0.0",
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
]
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "deploy-rs"
version = "0.1.0"
dependencies = [
"clap",
[#201] Deduce profile directory during activation Problem: Since https://github.com/NixOS/nix/pull/5226 nix profiles for users are stored in 'XDG_STATE_HOME' or 'HOME' directory. However, 'deploy-rs' still expects profiles to be present in '/nix/var/nix/profiles/per-user'. As a result, an attempt to deploy a profile with newer nix may fail with an error about non-existing files. Solution: Instead of deducing the profile path prior to ssh'ing and actual activation, deduce the path to the profile during as a part of 'activate-rs' invocation. Now if the profile path is not specified explicitly as an attribute in profile within the deploy flake, the path to the profile is determined based on the user to which the profile belongs and on the values of 'XDG_STATE_HOME' and 'HOME' variables. Additionally, if the old profile directory (in '/nix/var/nix/profiles/per-user') for a given user already exists, it is used instead for the sake of backward compatibility.
2023-09-06 15:54:22 +03:00
"dirs",
Replace logger, add more logging options including files
2020-12-27 20:48:18 +03:00
"flexi_logger",
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
"fork",
"futures-util",
stuff
2020-09-28 20:48:21 +03:00
"log",
"merge",
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
"notify",
Use crude Nix parsing for parsing the flake path
2020-11-29 21:51:52 +03:00
"rnix",
add support for entering password for sudo
2024-02-03 07:42:36 +03:00
"rpassword",
stuff
2020-09-28 20:48:21 +03:00
"serde",
"serde_json",
Modify activation logic to keep SSH connection alive for magic-rollback and avoid forking or disconnecting std{out,err}
2020-12-31 06:25:59 +03:00
"signal-hook",
Debump the smol_str version to 0.1.16 to build on rust 1.45.2 (#28) * Debump the smol_str version to 0.1.16 to build on rust 1.45.2 Rust 1.45.2 is what ships in the 20.09 release, and smol_str 0.1.17 is incompatible with it. * Clarify version bounds on the smol_str dependency
2020-12-15 22:08:31 +03:00
"smol_str",
Make all the errors work correctly (I am so so sorry)
2020-10-30 05:33:53 +03:00
"thiserror",
stuff
2020-09-28 20:48:21 +03:00
"tokio",
Partially add deployment confirmation utilities (for #4)
2020-11-23 06:03:04 +03:00
"toml",
stuff
2020-09-28 20:48:21 +03:00
"whoami",
Partially add deployment confirmation utilities (for #4)
2020-11-23 06:03:04 +03:00
"yn",
stuff
2020-09-28 20:48:21 +03:00
]
[#201] Deduce profile directory during activation Problem: Since https://github.com/NixOS/nix/pull/5226 nix profiles for users are stored in 'XDG_STATE_HOME' or 'HOME' directory. However, 'deploy-rs' still expects profiles to be present in '/nix/var/nix/profiles/per-user'. As a result, an attempt to deploy a profile with newer nix may fail with an error about non-existing files. Solution: Instead of deducing the profile path prior to ssh'ing and actual activation, deduce the path to the profile during as a part of 'activate-rs' invocation. Now if the profile path is not specified explicitly as an attribute in profile within the deploy flake, the path to the profile is determined based on the user to which the profile belongs and on the values of 'XDG_STATE_HOME' and 'HOME' variables. Additionally, if the old profile directory (in '/nix/var/nix/profiles/per-user') for a given user already exists, it is used instead for the sake of backward compatibility.
2023-09-06 15:54:22 +03:00
[[package]]
name = "dirs"
version = "5.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "44c45a9d03d6676652bcb5e724c7e988de1acad23a711b5217ab9cbecbec2225"
dependencies = [
"dirs-sys",
]
[[package]]
name = "dirs-sys"
version = "0.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "520f05a5cbd335fae5a99ff7a6ab8627577660ee5cfd6a94a6a929b52ff0321c"
dependencies = [
"libc",
"option-ext",
"redox_users",
"windows-sys 0.48.0",
]
stuff
2020-09-28 20:48:21 +03:00
[[package]]
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
name = "filetime"
version = "0.2.13"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "0c122a393ea57648015bf06fbd3d372378992e86b9ff5a7a497b076a28c79efe"
dependencies = [
"cfg-if 1.0.0",
"libc",
[#201] Deduce profile directory during activation Problem: Since https://github.com/NixOS/nix/pull/5226 nix profiles for users are stored in 'XDG_STATE_HOME' or 'HOME' directory. However, 'deploy-rs' still expects profiles to be present in '/nix/var/nix/profiles/per-user'. As a result, an attempt to deploy a profile with newer nix may fail with an error about non-existing files. Solution: Instead of deducing the profile path prior to ssh'ing and actual activation, deduce the path to the profile during as a part of 'activate-rs' invocation. Now if the profile path is not specified explicitly as an attribute in profile within the deploy flake, the path to the profile is determined based on the user to which the profile belongs and on the values of 'XDG_STATE_HOME' and 'HOME' variables. Additionally, if the old profile directory (in '/nix/var/nix/profiles/per-user') for a given user already exists, it is used instead for the sake of backward compatibility.
2023-09-06 15:54:22 +03:00
"redox_syscall 0.1.57",
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
"winapi",
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
]
stuff
2020-09-28 20:48:21 +03:00
Replace logger, add more logging options including files
2020-12-27 20:48:18 +03:00
[[package]]
name = "flexi_logger"
version = "0.16.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c37586928c27a25ff5fce49ff3f8e071b3beeef48b4f004fe7d40d75a26e3db5"
dependencies = [
"atty",
"chrono",
"glob",
"lazy_static",
"log",
"regex",
"thiserror",
"yansi",
]
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
[[package]]
name = "fork"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "0.1.18"
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "e4c5b9b0bce249a456f83ac4404e8baad0d2ba81cf651949719a4f74eb7323bb"
dependencies = [
"libc",
]
[[package]]
name = "fsevent-sys"
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
version = "4.1.0"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
checksum = "76ee7a02da4d231650c7cea31349b889be2f45ddb3ef3032d2ec8185f6313fd2"
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
dependencies = [
"libc",
]
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "futures-core"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "0.3.8"
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "847ce131b72ffb13b6109a221da9ad97a64cbe48feb1028356b836b47b8f1748"
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
[[package]]
name = "futures-macro"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "0.3.8"
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "77408a692f1f97bcc61dc001d752e00643408fbc922e4d634c655df50d595556"
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
dependencies = [
"proc-macro-hack",
"proc-macro2",
"quote",
"syn",
]
[[package]]
name = "futures-task"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "0.3.8"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "7c554eb5bf48b2426c4771ab68c6b14468b6e76cc90996f528c3338d761a4d0d"
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
dependencies = [
"once_cell",
]
[[package]]
name = "futures-util"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "0.3.8"
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "d304cff4a7b99cfb7986f7d43fbe93d175e72e704a8860787cc95e9ffd85cbd2"
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
dependencies = [
"futures-core",
"futures-macro",
"futures-task",
"pin-project",
"pin-utils",
"proc-macro-hack",
"proc-macro-nested",
"slab",
]
stuff
2020-09-28 20:48:21 +03:00
[#201] Deduce profile directory during activation Problem: Since https://github.com/NixOS/nix/pull/5226 nix profiles for users are stored in 'XDG_STATE_HOME' or 'HOME' directory. However, 'deploy-rs' still expects profiles to be present in '/nix/var/nix/profiles/per-user'. As a result, an attempt to deploy a profile with newer nix may fail with an error about non-existing files. Solution: Instead of deducing the profile path prior to ssh'ing and actual activation, deduce the path to the profile during as a part of 'activate-rs' invocation. Now if the profile path is not specified explicitly as an attribute in profile within the deploy flake, the path to the profile is determined based on the user to which the profile belongs and on the values of 'XDG_STATE_HOME' and 'HOME' variables. Additionally, if the old profile directory (in '/nix/var/nix/profiles/per-user') for a given user already exists, it is used instead for the sake of backward compatibility.
2023-09-06 15:54:22 +03:00
[[package]]
name = "getrandom"
version = "0.2.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "be4136b2a15dd319360be1c07d9933517ccf0be8f16bf62a3bee4f0d618df427"
dependencies = [
"cfg-if 1.0.0",
"libc",
"wasi 0.11.0+wasi-snapshot-preview1",
]
Replace logger, add more logging options including files
2020-12-27 20:48:18 +03:00
[[package]]
name = "glob"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9b919933a397b79c37e33b77bb2aa3dc8eb6e165ad809e58ff75bc7db2e34574"
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "hashbrown"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "0.9.1"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "d7afe4a420e3fe79967a00898cc1f4db7c8a49a9333a29f8a4bd76a253d5cd04"
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "heck"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "20564e78d53d2bb135c343b3f47714a56af2061f1c928fdb541dc7b9fdd94205"
dependencies = [
"unicode-segmentation",
]
[[package]]
name = "hermit-abi"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "0.1.17"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "5aca5565f760fb5b220e499d72710ed156fdb74e631659e99377d9ebfbd13ae8"
stuff
2020-09-28 20:48:21 +03:00
dependencies = [
"libc",
]
[[package]]
name = "indexmap"
version = "1.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "55e2e4c765aa53a0424761bf9f41aa7a6ac1efa87238f59560640e27fca028f2"
dependencies = [
"autocfg",
"hashbrown",
]
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
[[package]]
name = "inotify"
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
version = "0.9.6"
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
checksum = "f8069d3ec154eb856955c1c0fbffefbf5f3c40a104ec912d4797314c1801abff"
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
dependencies = [
"bitflags",
"inotify-sys",
"libc",
]
[[package]]
name = "inotify-sys"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "0.1.4"
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "c4563555856585ab3180a5bf0b2f9f8d301a728462afffc8195b3f5394229c55"
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
dependencies = [
"libc",
]
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "itoa"
version = "0.4.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "dc6f3ad7b9d11a0c00842ff8de1b60ee58661048eb8049ed33c73594f359d7e6"
[[package]]
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
name = "kqueue"
version = "1.0.7"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
checksum = "2c8fc60ba15bf51257aa9807a48a61013db043fcf3a78cb0d916e8e396dcad98"
stuff
2020-09-28 20:48:21 +03:00
dependencies = [
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
"kqueue-sys",
"libc",
stuff
2020-09-28 20:48:21 +03:00
]
[[package]]
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
name = "kqueue-sys"
version = "1.0.3"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
checksum = "8367585489f01bc55dd27404dcf56b95e6da061a256a666ab23be9ba96a2e587"
dependencies = [
"bitflags",
"libc",
]
stuff
2020-09-28 20:48:21 +03:00
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
[[package]]
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
name = "lazy_static"
version = "1.4.0"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
checksum = "e2abad23fbc42b3700f2f279844dc832adb2b2eb069b2df918f455c4e18cc646"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "libc"
[#201] Deduce profile directory during activation Problem: Since https://github.com/NixOS/nix/pull/5226 nix profiles for users are stored in 'XDG_STATE_HOME' or 'HOME' directory. However, 'deploy-rs' still expects profiles to be present in '/nix/var/nix/profiles/per-user'. As a result, an attempt to deploy a profile with newer nix may fail with an error about non-existing files. Solution: Instead of deducing the profile path prior to ssh'ing and actual activation, deduce the path to the profile during as a part of 'activate-rs' invocation. Now if the profile path is not specified explicitly as an attribute in profile within the deploy flake, the path to the profile is determined based on the user to which the profile belongs and on the values of 'XDG_STATE_HOME' and 'HOME' variables. Additionally, if the old profile directory (in '/nix/var/nix/profiles/per-user') for a given user already exists, it is used instead for the sake of backward compatibility.
2023-09-06 15:54:22 +03:00
version = "0.2.147"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[#201] Deduce profile directory during activation Problem: Since https://github.com/NixOS/nix/pull/5226 nix profiles for users are stored in 'XDG_STATE_HOME' or 'HOME' directory. However, 'deploy-rs' still expects profiles to be present in '/nix/var/nix/profiles/per-user'. As a result, an attempt to deploy a profile with newer nix may fail with an error about non-existing files. Solution: Instead of deducing the profile path prior to ssh'ing and actual activation, deduce the path to the profile during as a part of 'activate-rs' invocation. Now if the profile path is not specified explicitly as an attribute in profile within the deploy flake, the path to the profile is determined based on the user to which the profile belongs and on the values of 'XDG_STATE_HOME' and 'HOME' variables. Additionally, if the old profile directory (in '/nix/var/nix/profiles/per-user') for a given user already exists, it is used instead for the sake of backward compatibility.
2023-09-06 15:54:22 +03:00
checksum = "b4668fb0ea861c1df094127ac5f1da3409a82116a4ba74fca2e58ef927159bb3"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "log"
version = "0.4.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4fabed175da42fed1fa0746b0ea71f412aa9d35e76e95e59b192c64b9dc2bf8b"
dependencies = [
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
"cfg-if 0.1.10",
stuff
2020-09-28 20:48:21 +03:00
]
[[package]]
name = "memchr"
[#202] Provide '^out' suffix for deriver on newer nix Problem: Since 2.15 nix no longer reference '.drv' as derivation outputs. At the same time, nix before '2.13' doesn't support '.drv' special suffix handling. Solution: Provide '^out' suffix for the profile deriver in case 'nix path-info <...>.drv' returns the same '<...>.drv' path. In other cases either an error about the build result not being present in the /nix/store is returned or an actual build result path is returned.
2023-04-18 10:28:39 +03:00
version = "2.5.0"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[#202] Provide '^out' suffix for deriver on newer nix Problem: Since 2.15 nix no longer reference '.drv' as derivation outputs. At the same time, nix before '2.13' doesn't support '.drv' special suffix handling. Solution: Provide '^out' suffix for the profile deriver in case 'nix path-info <...>.drv' returns the same '<...>.drv' path. In other cases either an error about the build result not being present in the /nix/store is returned or an actual build result path is returned.
2023-04-18 10:28:39 +03:00
checksum = "2dffe52ecf27772e601905b7522cb4ef790d2cc203488bbd0e2fe85fcb74566d"
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "merge"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "10bbef93abb1da61525bbc45eeaff6473a41907d19f8f9aa5168d214e10693e9"
dependencies = [
"merge_derive",
"num-traits",
]
[[package]]
name = "merge_derive"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "209d075476da2e63b4b29e72a2ef627b840589588e71400a25e3565c4f849d07"
dependencies = [
"proc-macro-error",
"proc-macro2",
"quote",
"syn",
]
[[package]]
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
name = "mio"
version = "0.7.6"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "f33bc887064ef1fd66020c9adfc45bb9f33d75a42096c81e7c56c65b75dd1a8b"
stuff
2020-09-28 20:48:21 +03:00
dependencies = [
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
"libc",
stuff
2020-09-28 20:48:21 +03:00
"log",
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
"miow",
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
"ntapi",
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
"winapi",
stuff
2020-09-28 20:48:21 +03:00
]
[[package]]
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
name = "mio"
version = "0.8.6"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
checksum = "5b9d9a46eff5b4ff64b45a9e316a6d1e0bc719ef429cbec4dc630684212bfdf9"
stuff
2020-09-28 20:48:21 +03:00
dependencies = [
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
"libc",
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
"log",
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
"wasi 0.11.0+wasi-snapshot-preview1",
"windows-sys 0.45.0",
stuff
2020-09-28 20:48:21 +03:00
]
[[package]]
name = "miow"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "0.3.6"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "5a33c1b55807fbed163481b5ba66db4b2fa6cde694a5027be10fb724206c5897"
stuff
2020-09-28 20:48:21 +03:00
dependencies = [
"socket2",
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
"winapi",
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
]
[[package]]
name = "notify"
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
version = "5.1.0"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
checksum = "58ea850aa68a06e48fdb069c0ec44d0d64c8dbffa49bf3b6f7f0a901fdea1ba9"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
dependencies = [
"bitflags",
"crossbeam-channel",
"filetime",
"fsevent-sys",
"inotify",
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
"kqueue",
stuff
2020-09-28 20:48:21 +03:00
"libc",
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
"mio 0.8.6",
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
"walkdir",
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
"windows-sys 0.42.0",
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
]
[[package]]
name = "ntapi"
version = "0.3.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3f6bb902e437b6d86e03cce10a7e2af662292c5dfef23b65899ea3ac9354ad44"
dependencies = [
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
"winapi",
stuff
2020-09-28 20:48:21 +03:00
]
Replace logger, add more logging options including files
2020-12-27 20:48:18 +03:00
[[package]]
name = "num-integer"
version = "0.1.44"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d2cc698a63b549a70bc047073d2949cce27cd1c7b0a4a862d08a8031bc2801db"
dependencies = [
"autocfg",
"num-traits",
]
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "num-traits"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "0.2.14"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "9a64b1ec5cda2586e284722486d802acf1f7dbdc623e2bfc57e65ca1cd099290"
stuff
2020-09-28 20:48:21 +03:00
dependencies = [
"autocfg",
]
[[package]]
name = "num_cpus"
version = "1.13.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "05499f3756671c15885fee9034446956fff3f243d6077b91e5767df161f766b3"
dependencies = [
"hermit-abi",
"libc",
]
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
[[package]]
name = "once_cell"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "1.5.2"
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "13bd41f508810a131401606d54ac32a467c97172d74ba7662562ebba5ad07fa0"
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
[#201] Deduce profile directory during activation Problem: Since https://github.com/NixOS/nix/pull/5226 nix profiles for users are stored in 'XDG_STATE_HOME' or 'HOME' directory. However, 'deploy-rs' still expects profiles to be present in '/nix/var/nix/profiles/per-user'. As a result, an attempt to deploy a profile with newer nix may fail with an error about non-existing files. Solution: Instead of deducing the profile path prior to ssh'ing and actual activation, deduce the path to the profile during as a part of 'activate-rs' invocation. Now if the profile path is not specified explicitly as an attribute in profile within the deploy flake, the path to the profile is determined based on the user to which the profile belongs and on the values of 'XDG_STATE_HOME' and 'HOME' variables. Additionally, if the old profile directory (in '/nix/var/nix/profiles/per-user') for a given user already exists, it is used instead for the sake of backward compatibility.
2023-09-06 15:54:22 +03:00
[[package]]
name = "option-ext"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "04744f49eae99ab78e0d5c0b603ab218f515ea8cfe5a456d7629ad883a3b6e7d"
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "os_str_bytes"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "2.4.0"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "afb2e1c3ee07430c2cf76151675e583e0f19985fa6efae47d6848a3e2c824f85"
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
[[package]]
name = "pin-project"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "1.0.2"
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "9ccc2237c2c489783abd8c4c80e5450fc0e98644555b1364da68cc29aa151ca7"
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
dependencies = [
"pin-project-internal",
]
[[package]]
name = "pin-project-internal"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "1.0.2"
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "f8e8d2bf0b23038a4424865103a4df472855692821aab4e4f5c3312d461d9e5f"
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
dependencies = [
"proc-macro2",
"quote",
"syn",
]
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "pin-project-lite"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "0.2.0"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "6b063f57ec186e6140e2b8b6921e5f1bd89c7356dda5b33acc5401203ca6131c"
stuff
2020-09-28 20:48:21 +03:00
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
[[package]]
name = "pin-utils"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8b870d8c151b6f2fb93e84a13146138f05d02ed11c7e7c54f8826aaaf7c9f184"
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "proc-macro-error"
version = "1.0.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "da25490ff9892aab3fcf7c36f08cfb902dd3e71ca0f9f9517bea02a73a5ce38c"
dependencies = [
"proc-macro-error-attr",
"proc-macro2",
"quote",
"syn",
"version_check",
]
[[package]]
name = "proc-macro-error-attr"
version = "1.0.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a1be40180e52ecc98ad80b184934baf3d0d29f979574e439af5a55274b35f869"
dependencies = [
"proc-macro2",
"quote",
"version_check",
]
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
[[package]]
name = "proc-macro-hack"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "0.5.19"
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "dbf0c48bc1d91375ae5c3cd81e3722dff1abcf81a30960240640d223f59fe0e5"
Auto rollback if deployment is not confirmed
2020-10-14 04:27:27 +03:00
[[package]]
name = "proc-macro-nested"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "eba180dafb9038b050a4c280019bbedf9f2467b61e5d892dcad585bb57aadc5a"
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "proc-macro2"
update tokio
2021-07-15 00:55:57 +03:00
version = "1.0.27"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update tokio
2021-07-15 00:55:57 +03:00
checksum = "f0d8caf72986c1a598726adc988bb5984792ef84f5ee5aa50209145ee8077038"
stuff
2020-09-28 20:48:21 +03:00
dependencies = [
"unicode-xid",
]
[[package]]
name = "quote"
version = "1.0.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "aa563d17ecb180e500da1cfd2b028310ac758de548efdd203e18f283af693f37"
dependencies = [
"proc-macro2",
]
[[package]]
name = "redox_syscall"
version = "0.1.57"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "41cc0f7e4d5d4544e8861606a285bb08d3e70712ccc7d2b84d7c0ccfaf4b05ce"
[#201] Deduce profile directory during activation Problem: Since https://github.com/NixOS/nix/pull/5226 nix profiles for users are stored in 'XDG_STATE_HOME' or 'HOME' directory. However, 'deploy-rs' still expects profiles to be present in '/nix/var/nix/profiles/per-user'. As a result, an attempt to deploy a profile with newer nix may fail with an error about non-existing files. Solution: Instead of deducing the profile path prior to ssh'ing and actual activation, deduce the path to the profile during as a part of 'activate-rs' invocation. Now if the profile path is not specified explicitly as an attribute in profile within the deploy flake, the path to the profile is determined based on the user to which the profile belongs and on the values of 'XDG_STATE_HOME' and 'HOME' variables. Additionally, if the old profile directory (in '/nix/var/nix/profiles/per-user') for a given user already exists, it is used instead for the sake of backward compatibility.
2023-09-06 15:54:22 +03:00
[[package]]
name = "redox_syscall"
version = "0.2.16"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fb5a58c1855b4b6819d59012155603f0b22ad30cad752600aadfcb695265519a"
dependencies = [
"bitflags",
]
[[package]]
name = "redox_users"
version = "0.4.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b033d837a7cf162d7993aded9304e30a83213c648b6e389db233191f891e5c2b"
dependencies = [
"getrandom",
"redox_syscall 0.2.16",
"thiserror",
]
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "regex"
[#202] Provide '^out' suffix for deriver on newer nix Problem: Since 2.15 nix no longer reference '.drv' as derivation outputs. At the same time, nix before '2.13' doesn't support '.drv' special suffix handling. Solution: Provide '^out' suffix for the profile deriver in case 'nix path-info <...>.drv' returns the same '<...>.drv' path. In other cases either an error about the build result not being present in the /nix/store is returned or an actual build result path is returned.
2023-04-18 10:28:39 +03:00
version = "1.7.3"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[#202] Provide '^out' suffix for deriver on newer nix Problem: Since 2.15 nix no longer reference '.drv' as derivation outputs. At the same time, nix before '2.13' doesn't support '.drv' special suffix handling. Solution: Provide '^out' suffix for the profile deriver in case 'nix path-info <...>.drv' returns the same '<...>.drv' path. In other cases either an error about the build result not being present in the /nix/store is returned or an actual build result path is returned.
2023-04-18 10:28:39 +03:00
checksum = "8b1f693b24f6ac912f4893ef08244d70b6067480d2f1a46e950c9691e6749d1d"
stuff
2020-09-28 20:48:21 +03:00
dependencies = [
"aho-corasick",
"memchr",
"regex-syntax",
]
[[package]]
name = "regex-syntax"
[#202] Provide '^out' suffix for deriver on newer nix Problem: Since 2.15 nix no longer reference '.drv' as derivation outputs. At the same time, nix before '2.13' doesn't support '.drv' special suffix handling. Solution: Provide '^out' suffix for the profile deriver in case 'nix path-info <...>.drv' returns the same '<...>.drv' path. In other cases either an error about the build result not being present in the /nix/store is returned or an actual build result path is returned.
2023-04-18 10:28:39 +03:00
version = "0.6.29"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[#202] Provide '^out' suffix for deriver on newer nix Problem: Since 2.15 nix no longer reference '.drv' as derivation outputs. At the same time, nix before '2.13' doesn't support '.drv' special suffix handling. Solution: Provide '^out' suffix for the profile deriver in case 'nix path-info <...>.drv' returns the same '<...>.drv' path. In other cases either an error about the build result not being present in the /nix/store is returned or an actual build result path is returned.
2023-04-18 10:28:39 +03:00
checksum = "f162c6dd7b008981e4d40210aca20b4bd0f9b60ca9271061b07f78537722f2e1"
stuff
2020-09-28 20:48:21 +03:00
Use crude Nix parsing for parsing the flake path
2020-11-29 21:51:52 +03:00
[[package]]
name = "rnix"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cbbea4c714e5bbf462fa4316ddf45875d8f0e28e5db81050b5f9ce99746c6863"
dependencies = [
"cbitset",
"rowan",
]
[[package]]
name = "rowan"
version = "0.9.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1ea7cadf87a9d8432e85cb4eb86bd2e765ace60c24ef86e79084dcae5d1c5a19"
dependencies = [
"rustc-hash",
"smol_str",
"text_unit",
"thin-dst",
]
add support for entering password for sudo
2024-02-03 07:42:36 +03:00
[[package]]
name = "rpassword"
version = "7.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "80472be3c897911d0137b2d2b9055faf6eeac5b14e324073d83bc17b191d7e3f"
dependencies = [
"libc",
"rtoolbox",
"windows-sys 0.48.0",
]
[[package]]
name = "rtoolbox"
version = "0.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c247d24e63230cdb56463ae328478bd5eac8b8faa8c69461a77e8e323afac90e"
dependencies = [
"libc",
"windows-sys 0.48.0",
]
Use crude Nix parsing for parsing the flake path
2020-11-29 21:51:52 +03:00
[[package]]
name = "rustc-hash"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "08d43f7aa6b08d49f382cde6a7982047c3426db949b1424bc4b7ec9ae12c6ce2"
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "ryu"
version = "1.0.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "71d301d4193d031abdd79ff7e3dd721168a9572ef3fe51a1517aba235bd8f86e"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
[[package]]
name = "same-file"
version = "1.0.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "93fc1dc3aaa9bfed95e02e6eadabb4baf7e3078b0bd1b4d7b6b0b68378900502"
dependencies = [
"winapi-util",
]
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "serde"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "1.0.118"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "06c64263859d87aa2eb554587e2d23183398d617427327cf2b3d0ed8c69e4800"
changed: remove 2015-style extern crate
2021-01-25 10:38:44 +03:00
dependencies = [
"serde_derive",
]
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "serde_derive"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "1.0.118"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "c84d3526699cd55261af4b941e4e725444df67aa4f9e6a3564f18030d12672df"
stuff
2020-09-28 20:48:21 +03:00
dependencies = [
"proc-macro2",
"quote",
"syn",
]
[[package]]
name = "serde_json"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "1.0.60"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "1500e84d27fe482ed1dc791a56eddc2f230046a040fa908c08bda1d9fb615779"
stuff
2020-09-28 20:48:21 +03:00
dependencies = [
"itoa",
"ryu",
"serde",
]
Modify activation logic to keep SSH connection alive for magic-rollback and avoid forking or disconnecting std{out,err}
2020-12-31 06:25:59 +03:00
[[package]]
name = "signal-hook"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6b3799fa361789a685db59e3986fb5f6f949e478728b9913c6759f7b014d0372"
dependencies = [
"libc",
"signal-hook-registry",
]
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "signal-hook-registry"
Modify activation logic to keep SSH connection alive for magic-rollback and avoid forking or disconnecting std{out,err}
2020-12-31 06:25:59 +03:00
version = "1.3.0"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Modify activation logic to keep SSH connection alive for magic-rollback and avoid forking or disconnecting std{out,err}
2020-12-31 06:25:59 +03:00
checksum = "16f1d0fef1604ba8f7a073c7e701f213e056707210e9020af4528e0101ce11a6"
stuff
2020-09-28 20:48:21 +03:00
dependencies = [
"libc",
]
[[package]]
name = "slab"
version = "0.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c111b5bd5695e56cffe5129854aa230b39c93a305372fdbb2668ca2394eea9f8"
Use crude Nix parsing for parsing the flake path
2020-11-29 21:51:52 +03:00
[[package]]
name = "smol_str"
Debump the smol_str version to 0.1.16 to build on rust 1.45.2 (#28) * Debump the smol_str version to 0.1.16 to build on rust 1.45.2 Rust 1.45.2 is what ships in the 20.09 release, and smol_str 0.1.17 is incompatible with it. * Clarify version bounds on the smol_str dependency
2020-12-15 22:08:31 +03:00
version = "0.1.16"
Use crude Nix parsing for parsing the flake path
2020-11-29 21:51:52 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Debump the smol_str version to 0.1.16 to build on rust 1.45.2 (#28) * Debump the smol_str version to 0.1.16 to build on rust 1.45.2 Rust 1.45.2 is what ships in the 20.09 release, and smol_str 0.1.17 is incompatible with it. * Clarify version bounds on the smol_str dependency
2020-12-15 22:08:31 +03:00
checksum = "2f7909a1d8bc166a862124d84fdc11bda0ea4ed3157ccca662296919c2972db1"
Use crude Nix parsing for parsing the flake path
2020-11-29 21:51:52 +03:00
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "socket2"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "0.3.17"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "2c29947abdee2a218277abeca306f25789c938e500ea5a9d4b12a5a504466902"
stuff
2020-09-28 20:48:21 +03:00
dependencies = [
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
"cfg-if 1.0.0",
stuff
2020-09-28 20:48:21 +03:00
"libc",
[#201] Deduce profile directory during activation Problem: Since https://github.com/NixOS/nix/pull/5226 nix profiles for users are stored in 'XDG_STATE_HOME' or 'HOME' directory. However, 'deploy-rs' still expects profiles to be present in '/nix/var/nix/profiles/per-user'. As a result, an attempt to deploy a profile with newer nix may fail with an error about non-existing files. Solution: Instead of deducing the profile path prior to ssh'ing and actual activation, deduce the path to the profile during as a part of 'activate-rs' invocation. Now if the profile path is not specified explicitly as an attribute in profile within the deploy flake, the path to the profile is determined based on the user to which the profile belongs and on the values of 'XDG_STATE_HOME' and 'HOME' variables. Additionally, if the old profile directory (in '/nix/var/nix/profiles/per-user') for a given user already exists, it is used instead for the sake of backward compatibility.
2023-09-06 15:54:22 +03:00
"redox_syscall 0.1.57",
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
"winapi",
stuff
2020-09-28 20:48:21 +03:00
]
[[package]]
name = "strsim"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "73473c0e59e6d5812c5dfe2a064a6444949f089e20eec9a2e5506596494e4623"
[[package]]
name = "syn"
update tokio
2021-07-15 00:55:57 +03:00
version = "1.0.73"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update tokio
2021-07-15 00:55:57 +03:00
checksum = "f71489ff30030d2ae598524f61326b902466f72a0fb1a8564c001cc63425bcc7"
stuff
2020-09-28 20:48:21 +03:00
dependencies = [
"proc-macro2",
"quote",
"unicode-xid",
]
[[package]]
name = "termcolor"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "1.1.2"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "2dfed899f0eb03f32ee8c6a0aabdb8a7949659e3466561fc0adf54e26d88c5f4"
stuff
2020-09-28 20:48:21 +03:00
dependencies = [
"winapi-util",
]
optimize release build for size
2021-08-04 18:03:05 +03:00
[[package]]
name = "terminal_size"
version = "0.1.17"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "633c1a546cee861a1a6d0dc69ebeca693bf4296661ba7852b9d21d159e0506df"
dependencies = [
"libc",
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
"winapi",
optimize release build for size
2021-08-04 18:03:05 +03:00
]
Use crude Nix parsing for parsing the flake path
2020-11-29 21:51:52 +03:00
[[package]]
name = "text_unit"
version = "0.1.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "20431e104bfecc1a40872578dbc390e10290a0e9c35fffe3ce6f73c15a9dbfc2"
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "textwrap"
version = "0.12.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "203008d98caf094106cfaba70acfed15e18ed3ddb7d94e49baec153a2b462789"
dependencies = [
optimize release build for size
2021-08-04 18:03:05 +03:00
"terminal_size",
stuff
2020-09-28 20:48:21 +03:00
"unicode-width",
]
Use crude Nix parsing for parsing the flake path
2020-11-29 21:51:52 +03:00
[[package]]
name = "thin-dst"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "db3c46be180f1af9673ebb27bc1235396f61ef6965b3fe0dbb2e624deb604f0e"
Make all the errors work correctly (I am so so sorry)
2020-10-30 05:33:53 +03:00
[[package]]
name = "thiserror"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "1.0.22"
Make all the errors work correctly (I am so so sorry)
2020-10-30 05:33:53 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "0e9ae34b84616eedaaf1e9dd6026dbe00dcafa92aa0c8077cb69df1fcfe5e53e"
Make all the errors work correctly (I am so so sorry)
2020-10-30 05:33:53 +03:00
dependencies = [
"thiserror-impl",
]
[[package]]
name = "thiserror-impl"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "1.0.22"
Make all the errors work correctly (I am so so sorry)
2020-10-30 05:33:53 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "9ba20f23e85b10754cd195504aebf6a27e2e6cbe28c17778a0c930724628dd56"
Make all the errors work correctly (I am so so sorry)
2020-10-30 05:33:53 +03:00
dependencies = [
"proc-macro2",
"quote",
"syn",
]
Replace logger, add more logging options including files
2020-12-27 20:48:18 +03:00
[[package]]
name = "time"
version = "0.1.44"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6db9e6914ab8b1ae1c260a4ae7a49b6c5611b40328a735b21862567685e73255"
dependencies = [
"libc",
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
"wasi 0.10.0+wasi-snapshot-preview1",
"winapi",
Replace logger, add more logging options including files
2020-12-27 20:48:18 +03:00
]
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "tokio"
update tokio
2021-07-15 00:55:57 +03:00
version = "1.9.0"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update tokio
2021-07-15 00:55:57 +03:00
checksum = "4b7b349f11a7047e6d1276853e612d152f5e8a352c61917887cc2169e2366b4c"
stuff
2020-09-28 20:48:21 +03:00
dependencies = [
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
"autocfg",
stuff
2020-09-28 20:48:21 +03:00
"bytes",
"libc",
add support for entering password for sudo
2024-02-03 07:42:36 +03:00
"memchr",
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
"mio 0.7.6",
stuff
2020-09-28 20:48:21 +03:00
"num_cpus",
update tokio
2021-07-15 00:55:57 +03:00
"once_cell",
stuff
2020-09-28 20:48:21 +03:00
"pin-project-lite",
"signal-hook-registry",
"tokio-macros",
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
"winapi",
stuff
2020-09-28 20:48:21 +03:00
]
[[package]]
name = "tokio-macros"
update tokio
2021-07-15 00:55:57 +03:00
version = "1.3.0"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update tokio
2021-07-15 00:55:57 +03:00
checksum = "54473be61f4ebe4efd09cec9bd5d16fa51d70ea0192213d754d2d500457db110"
stuff
2020-09-28 20:48:21 +03:00
dependencies = [
"proc-macro2",
"quote",
"syn",
]
Partially add deployment confirmation utilities (for #4)
2020-11-23 06:03:04 +03:00
[[package]]
name = "toml"
version = "0.5.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "75cf45bb0bef80604d001caaec0d09da99611b3c0fd39d3080468875cdb65645"
dependencies = [
"serde",
]
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "unicode-segmentation"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
version = "1.7.1"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
checksum = "bb0d2e7be6ae3a5fa87eed5fb451aff96f2573d2694942e40543ae0bbe19c796"
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "unicode-width"
version = "0.1.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9337591893a19b88d8d87f2cec1e73fad5cdfd10e5a6f349f498ad6ea2ffb1e3"
[[package]]
name = "unicode-xid"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f7fe0bb3479651439c9112f72b6c505038574c9fbb575ed1bf3b797fa39dd564"
[[package]]
name = "vec_map"
version = "0.8.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f1bddf1187be692e79c5ffeab891132dfb0f236ed36a43c7ed39f1165ee20191"
[[package]]
name = "version_check"
version = "0.9.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b5a972e5669d67ba988ce3dc826706fb0a8b01471c088cb0b6110b805cc36aed"
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
[[package]]
name = "walkdir"
version = "2.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "777182bc735b6424e1a57516d35ed72cb8019d85c8c9bf536dccb3445c1a2f7d"
dependencies = [
"same-file",
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
"winapi",
Update tokio & pull in notify, instead of inotify The notify crate is cross-platform, and the newer tokio has some bug fixes. Let's use those.
2020-12-14 04:48:38 +03:00
"winapi-util",
]
Replace logger, add more logging options including files
2020-12-27 20:48:18 +03:00
[[package]]
name = "wasi"
version = "0.10.0+wasi-snapshot-preview1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1a143597ca7c7793eff794def352d41792a93c481eb1042423ff7ff72ba2c31f"
stuff
2020-09-28 20:48:21 +03:00
[[package]]
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
name = "wasi"
version = "0.11.0+wasi-snapshot-preview1"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
checksum = "9c8d87e72b64a3b4db28d11ce29237c246188f4f51057d65a7eab63b7987e423"
stuff
2020-09-28 20:48:21 +03:00
[[package]]
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
name = "whoami"
version = "0.9.0"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
checksum = "7884773ab69074615cb8f8425d0e53f11710786158704fca70f53e71b0e05504"
stuff
2020-09-28 20:48:21 +03:00
[[package]]
name = "winapi"
version = "0.3.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5c839a674fcd7a98952e593242ea400abe93992746761e38641405d28b00f419"
dependencies = [
"winapi-i686-pc-windows-gnu",
"winapi-x86_64-pc-windows-gnu",
]
[[package]]
name = "winapi-i686-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
[[package]]
name = "winapi-util"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "70ec6ce85bb158151cae5e5c87f95a8e97d2c0c4b001223f33a334e3ce5de178"
dependencies = [
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
"winapi",
stuff
2020-09-28 20:48:21 +03:00
]
[[package]]
name = "winapi-x86_64-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
[[package]]
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
name = "windows-sys"
version = "0.42.0"
stuff
2020-09-28 20:48:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
checksum = "5a3e1820f08b8513f676f7ab6c1f99ff312fb97b553d30ff4dd86f9f15728aa7"
stuff
2020-09-28 20:48:21 +03:00
dependencies = [
[#201] Deduce profile directory during activation Problem: Since https://github.com/NixOS/nix/pull/5226 nix profiles for users are stored in 'XDG_STATE_HOME' or 'HOME' directory. However, 'deploy-rs' still expects profiles to be present in '/nix/var/nix/profiles/per-user'. As a result, an attempt to deploy a profile with newer nix may fail with an error about non-existing files. Solution: Instead of deducing the profile path prior to ssh'ing and actual activation, deduce the path to the profile during as a part of 'activate-rs' invocation. Now if the profile path is not specified explicitly as an attribute in profile within the deploy flake, the path to the profile is determined based on the user to which the profile belongs and on the values of 'XDG_STATE_HOME' and 'HOME' variables. Additionally, if the old profile directory (in '/nix/var/nix/profiles/per-user') for a given user already exists, it is used instead for the sake of backward compatibility.
2023-09-06 15:54:22 +03:00
"windows_aarch64_gnullvm 0.42.2",
"windows_aarch64_msvc 0.42.2",
"windows_i686_gnu 0.42.2",
"windows_i686_msvc 0.42.2",
"windows_x86_64_gnu 0.42.2",
"windows_x86_64_gnullvm 0.42.2",
"windows_x86_64_msvc 0.42.2",
stuff
2020-09-28 20:48:21 +03:00
]
Partially add deployment confirmation utilities (for #4)
2020-11-23 06:03:04 +03:00
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
[[package]]
name = "windows-sys"
version = "0.45.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "75283be5efb2831d37ea142365f009c02ec203cd29a3ebecbc093d52315b66d0"
dependencies = [
[#201] Deduce profile directory during activation Problem: Since https://github.com/NixOS/nix/pull/5226 nix profiles for users are stored in 'XDG_STATE_HOME' or 'HOME' directory. However, 'deploy-rs' still expects profiles to be present in '/nix/var/nix/profiles/per-user'. As a result, an attempt to deploy a profile with newer nix may fail with an error about non-existing files. Solution: Instead of deducing the profile path prior to ssh'ing and actual activation, deduce the path to the profile during as a part of 'activate-rs' invocation. Now if the profile path is not specified explicitly as an attribute in profile within the deploy flake, the path to the profile is determined based on the user to which the profile belongs and on the values of 'XDG_STATE_HOME' and 'HOME' variables. Additionally, if the old profile directory (in '/nix/var/nix/profiles/per-user') for a given user already exists, it is used instead for the sake of backward compatibility.
2023-09-06 15:54:22 +03:00
"windows-targets 0.42.2",
]
[[package]]
name = "windows-sys"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "677d2418bec65e3338edb076e806bc1ec15693c5d0104683f2efe857f61056a9"
dependencies = [
"windows-targets 0.48.5",
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
]
[[package]]
name = "windows-targets"
version = "0.42.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8e5180c00cd44c9b1c88adb3693291f1cd93605ded80c250a75d472756b4d071"
dependencies = [
[#201] Deduce profile directory during activation Problem: Since https://github.com/NixOS/nix/pull/5226 nix profiles for users are stored in 'XDG_STATE_HOME' or 'HOME' directory. However, 'deploy-rs' still expects profiles to be present in '/nix/var/nix/profiles/per-user'. As a result, an attempt to deploy a profile with newer nix may fail with an error about non-existing files. Solution: Instead of deducing the profile path prior to ssh'ing and actual activation, deduce the path to the profile during as a part of 'activate-rs' invocation. Now if the profile path is not specified explicitly as an attribute in profile within the deploy flake, the path to the profile is determined based on the user to which the profile belongs and on the values of 'XDG_STATE_HOME' and 'HOME' variables. Additionally, if the old profile directory (in '/nix/var/nix/profiles/per-user') for a given user already exists, it is used instead for the sake of backward compatibility.
2023-09-06 15:54:22 +03:00
"windows_aarch64_gnullvm 0.42.2",
"windows_aarch64_msvc 0.42.2",
"windows_i686_gnu 0.42.2",
"windows_i686_msvc 0.42.2",
"windows_x86_64_gnu 0.42.2",
"windows_x86_64_gnullvm 0.42.2",
"windows_x86_64_msvc 0.42.2",
]
[[package]]
name = "windows-targets"
version = "0.48.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9a2fa6e2155d7247be68c096456083145c183cbbbc2764150dda45a87197940c"
dependencies = [
"windows_aarch64_gnullvm 0.48.5",
"windows_aarch64_msvc 0.48.5",
"windows_i686_gnu 0.48.5",
"windows_i686_msvc 0.48.5",
"windows_x86_64_gnu 0.48.5",
"windows_x86_64_gnullvm 0.48.5",
"windows_x86_64_msvc 0.48.5",
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
]
[[package]]
name = "windows_aarch64_gnullvm"
version = "0.42.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "597a5118570b68bc08d8d59125332c54f1ba9d9adeedeef5b99b02ba2b0698f8"
[#201] Deduce profile directory during activation Problem: Since https://github.com/NixOS/nix/pull/5226 nix profiles for users are stored in 'XDG_STATE_HOME' or 'HOME' directory. However, 'deploy-rs' still expects profiles to be present in '/nix/var/nix/profiles/per-user'. As a result, an attempt to deploy a profile with newer nix may fail with an error about non-existing files. Solution: Instead of deducing the profile path prior to ssh'ing and actual activation, deduce the path to the profile during as a part of 'activate-rs' invocation. Now if the profile path is not specified explicitly as an attribute in profile within the deploy flake, the path to the profile is determined based on the user to which the profile belongs and on the values of 'XDG_STATE_HOME' and 'HOME' variables. Additionally, if the old profile directory (in '/nix/var/nix/profiles/per-user') for a given user already exists, it is used instead for the sake of backward compatibility.
2023-09-06 15:54:22 +03:00
[[package]]
name = "windows_aarch64_gnullvm"
version = "0.48.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2b38e32f0abccf9987a4e3079dfb67dcd799fb61361e53e2882c3cbaf0d905d8"
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
[[package]]
name = "windows_aarch64_msvc"
version = "0.42.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e08e8864a60f06ef0d0ff4ba04124db8b0fb3be5776a5cd47641e942e58c4d43"
[#201] Deduce profile directory during activation Problem: Since https://github.com/NixOS/nix/pull/5226 nix profiles for users are stored in 'XDG_STATE_HOME' or 'HOME' directory. However, 'deploy-rs' still expects profiles to be present in '/nix/var/nix/profiles/per-user'. As a result, an attempt to deploy a profile with newer nix may fail with an error about non-existing files. Solution: Instead of deducing the profile path prior to ssh'ing and actual activation, deduce the path to the profile during as a part of 'activate-rs' invocation. Now if the profile path is not specified explicitly as an attribute in profile within the deploy flake, the path to the profile is determined based on the user to which the profile belongs and on the values of 'XDG_STATE_HOME' and 'HOME' variables. Additionally, if the old profile directory (in '/nix/var/nix/profiles/per-user') for a given user already exists, it is used instead for the sake of backward compatibility.
2023-09-06 15:54:22 +03:00
[[package]]
name = "windows_aarch64_msvc"
version = "0.48.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "dc35310971f3b2dbbf3f0690a219f40e2d9afcf64f9ab7cc1be722937c26b4bc"
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
[[package]]
name = "windows_i686_gnu"
version = "0.42.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c61d927d8da41da96a81f029489353e68739737d3beca43145c8afec9a31a84f"
[#201] Deduce profile directory during activation Problem: Since https://github.com/NixOS/nix/pull/5226 nix profiles for users are stored in 'XDG_STATE_HOME' or 'HOME' directory. However, 'deploy-rs' still expects profiles to be present in '/nix/var/nix/profiles/per-user'. As a result, an attempt to deploy a profile with newer nix may fail with an error about non-existing files. Solution: Instead of deducing the profile path prior to ssh'ing and actual activation, deduce the path to the profile during as a part of 'activate-rs' invocation. Now if the profile path is not specified explicitly as an attribute in profile within the deploy flake, the path to the profile is determined based on the user to which the profile belongs and on the values of 'XDG_STATE_HOME' and 'HOME' variables. Additionally, if the old profile directory (in '/nix/var/nix/profiles/per-user') for a given user already exists, it is used instead for the sake of backward compatibility.
2023-09-06 15:54:22 +03:00
[[package]]
name = "windows_i686_gnu"
version = "0.48.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a75915e7def60c94dcef72200b9a8e58e5091744960da64ec734a6c6e9b3743e"
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
[[package]]
name = "windows_i686_msvc"
version = "0.42.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "44d840b6ec649f480a41c8d80f9c65108b92d89345dd94027bfe06ac444d1060"
[#201] Deduce profile directory during activation Problem: Since https://github.com/NixOS/nix/pull/5226 nix profiles for users are stored in 'XDG_STATE_HOME' or 'HOME' directory. However, 'deploy-rs' still expects profiles to be present in '/nix/var/nix/profiles/per-user'. As a result, an attempt to deploy a profile with newer nix may fail with an error about non-existing files. Solution: Instead of deducing the profile path prior to ssh'ing and actual activation, deduce the path to the profile during as a part of 'activate-rs' invocation. Now if the profile path is not specified explicitly as an attribute in profile within the deploy flake, the path to the profile is determined based on the user to which the profile belongs and on the values of 'XDG_STATE_HOME' and 'HOME' variables. Additionally, if the old profile directory (in '/nix/var/nix/profiles/per-user') for a given user already exists, it is used instead for the sake of backward compatibility.
2023-09-06 15:54:22 +03:00
[[package]]
name = "windows_i686_msvc"
version = "0.48.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8f55c233f70c4b27f66c523580f78f1004e8b5a8b659e05a4eb49d4166cca406"
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
[[package]]
name = "windows_x86_64_gnu"
version = "0.42.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8de912b8b8feb55c064867cf047dda097f92d51efad5b491dfb98f6bbb70cb36"
[#201] Deduce profile directory during activation Problem: Since https://github.com/NixOS/nix/pull/5226 nix profiles for users are stored in 'XDG_STATE_HOME' or 'HOME' directory. However, 'deploy-rs' still expects profiles to be present in '/nix/var/nix/profiles/per-user'. As a result, an attempt to deploy a profile with newer nix may fail with an error about non-existing files. Solution: Instead of deducing the profile path prior to ssh'ing and actual activation, deduce the path to the profile during as a part of 'activate-rs' invocation. Now if the profile path is not specified explicitly as an attribute in profile within the deploy flake, the path to the profile is determined based on the user to which the profile belongs and on the values of 'XDG_STATE_HOME' and 'HOME' variables. Additionally, if the old profile directory (in '/nix/var/nix/profiles/per-user') for a given user already exists, it is used instead for the sake of backward compatibility.
2023-09-06 15:54:22 +03:00
[[package]]
name = "windows_x86_64_gnu"
version = "0.48.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "53d40abd2583d23e4718fddf1ebec84dbff8381c07cae67ff7768bbf19c6718e"
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
[[package]]
name = "windows_x86_64_gnullvm"
version = "0.42.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "26d41b46a36d453748aedef1486d5c7a85db22e56aff34643984ea85514e94a3"
[#201] Deduce profile directory during activation Problem: Since https://github.com/NixOS/nix/pull/5226 nix profiles for users are stored in 'XDG_STATE_HOME' or 'HOME' directory. However, 'deploy-rs' still expects profiles to be present in '/nix/var/nix/profiles/per-user'. As a result, an attempt to deploy a profile with newer nix may fail with an error about non-existing files. Solution: Instead of deducing the profile path prior to ssh'ing and actual activation, deduce the path to the profile during as a part of 'activate-rs' invocation. Now if the profile path is not specified explicitly as an attribute in profile within the deploy flake, the path to the profile is determined based on the user to which the profile belongs and on the values of 'XDG_STATE_HOME' and 'HOME' variables. Additionally, if the old profile directory (in '/nix/var/nix/profiles/per-user') for a given user already exists, it is used instead for the sake of backward compatibility.
2023-09-06 15:54:22 +03:00
[[package]]
name = "windows_x86_64_gnullvm"
version = "0.48.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0b7b52767868a23d5bab768e390dc5f5c55825b6d30b86c844ff2dc7414044cc"
[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String' Problem: 'temp_path' and 'lock_path' are handled as 'String'. This can be a problem when the 'temp_path' directory is a symlink on the target system, e.g. this is the case with the default '/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'. Solution: Handle 'temp_path' and 'lock_path' as actual Paths. Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking filesystem events. As a side effect, also update the 'notify' dependency to the latest stable version.
2023-04-19 12:46:43 +03:00
[[package]]
name = "windows_x86_64_msvc"
version = "0.42.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9aec5da331524158c6d1a4ac0ab1541149c0b9505fde06423b02f5ef0106b9f0"
[#201] Deduce profile directory during activation Problem: Since https://github.com/NixOS/nix/pull/5226 nix profiles for users are stored in 'XDG_STATE_HOME' or 'HOME' directory. However, 'deploy-rs' still expects profiles to be present in '/nix/var/nix/profiles/per-user'. As a result, an attempt to deploy a profile with newer nix may fail with an error about non-existing files. Solution: Instead of deducing the profile path prior to ssh'ing and actual activation, deduce the path to the profile during as a part of 'activate-rs' invocation. Now if the profile path is not specified explicitly as an attribute in profile within the deploy flake, the path to the profile is determined based on the user to which the profile belongs and on the values of 'XDG_STATE_HOME' and 'HOME' variables. Additionally, if the old profile directory (in '/nix/var/nix/profiles/per-user') for a given user already exists, it is used instead for the sake of backward compatibility.
2023-09-06 15:54:22 +03:00
[[package]]
name = "windows_x86_64_msvc"
version = "0.48.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ed94fce61571a4006852b7389a063ab983c02eb1bb37b47f8272ce92d06d9538"
Replace logger, add more logging options including files
2020-12-27 20:48:18 +03:00
[[package]]
name = "yansi"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9fc79f4a1e39857fc00c3f662cbf2651c771f00e9c15fe2abc341806bd46bd71"
Partially add deployment confirmation utilities (for #4)
2020-11-23 06:03:04 +03:00
[[package]]
name = "yn"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d789b24a50ca067124e6e6ad3061c48151da174043cb09285ba934425e8739ec"
Reference in New Issue Copy Permalink