tyler
/
proxmox-backup
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
proxmox-backup/Cargo.toml

60 lines
1.2 KiB
TOML
Raw Normal View History

initial version
2018-10-30 09:04:30 +00:00
[package]
use proxmox-backup as package name
2018-12-20 09:32:49 +00:00
name = "proxmox-backup"
initial version
2018-10-30 09:04:30 +00:00
version = "0.1.0"
authors = ["Dietmar Maurer <dietmar@proxmox.com>"]
use edition 2018 (beta) This is expected to be stable by the end of the year.
2018-11-01 13:42:27 +00:00
edition = "2018"
move code into lib.rs
2018-10-30 09:40:05 +00:00
[lib]
use proxmox-backup as package name
2018-12-20 09:32:49 +00:00
name = "proxmox_backup"
move code into lib.rs
2018-10-30 09:40:05 +00:00
path = "src/lib.rs"
initial version
2018-10-30 09:04:30 +00:00
[dependencies]
use ssh+git for the proxmox repository This works for me, note the `ssh://` protocol, and using `/` to separate the path instead of `:`. Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-06-12 11:16:36 +00:00
proxmox = { git = "ssh://gitolite3@proxdev.maurer-it.com/rust/proxmox", version = "0.1" }
api2/admin/datastore: add a backup protocol test api path Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-03-06 09:21:22 +00:00
proxmox-protocol = { path = "proxmox-protocol" }
use crate log and syslog
2019-01-26 09:56:11 +00:00
log = "0.4"
syslog = "4.0"
use newer versions
2019-01-20 09:06:29 +00:00
failure = "0.1"
serde = "1.0"
serde_json = "1.0"
serde_derive = "1.0"
url = "1.7"
futures = "0.1"
rc/client/http_client.rs: add experimental h2 upgrade code
2019-04-29 09:57:58 +00:00
bytes = "0.4"
tools/wrapped_reader_stream.rs: use tokio_threadpool::blocking
2019-01-20 09:28:51 +00:00
tokio-threadpool = "0.1"
use newer versions
2019-01-20 09:06:29 +00:00
tokio = "0.1"
add protocol test client This uses futures for everything which is mostly useful as a test to see if the protocol crate's non-blocking I/O support can handle it... Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-03-06 09:23:56 +00:00
tokio-fs = "0.1"
implement server state/signal handling, depend on tokio-signal
2019-04-08 10:21:29 +00:00
tokio-tls = "0.2"
tokio-signal = "0.2"
native-tls = "0.2"
use newer versions
2019-01-20 09:06:29 +00:00
http = "0.1"
src/api2/admin/datastore/h2upload.rs: add test code for http2
2019-04-27 06:57:35 +00:00
h2 = "0.1"
use newer versions
2019-01-20 09:06:29 +00:00
hyper = "0.12"
client: use hyper-tls for now Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-02-13 10:03:02 +00:00
hyper-tls = "0.3"
use newer versions
2019-01-20 09:06:29 +00:00
lazy_static = "1.1"
regex = "1.0"
impl sweep_used_chunks, first try
2018-12-19 08:51:33 +00:00
libc = "0.2"
src/tools/process_locker.rs: implement inter-process reader-writer locks
2019-03-22 07:04:12 +00:00
nix = "0.13"
use newer versions
2019-01-20 09:06:29 +00:00
shellwords = "1.0"
image_index.rs: write header
2018-12-15 16:05:49 +00:00
uuid = { version = "0.7", features = ["v4"] }
use newer versions
2019-01-20 09:06:29 +00:00
chrono = "0.4" # Date and time library for Rust
openssl = "0.10"
use external crate siphasher Because std::hash::SipHasher is deprecated.
2018-12-28 18:50:07 +00:00
siphasher = "0.3"
use endian_trait arrays feature
2019-04-23 12:23:36 +00:00
endian_trait = { version = "0.6", features = ["arrays"] }
backup/datastore.rs: list all index files using walkdir crate
2019-01-18 11:24:58 +00:00
walkdir = "2"
api2/subscription.rs: add subscription api class
2019-01-22 11:50:19 +00:00
md5 = "0.6"
tools/ticket.rs: add basic ticket support
2019-01-29 11:59:07 +00:00
base64 = "0.10"
depend on pam-auth, use pam for root login Please use username "root@pam" for login via GUI.
2019-02-01 08:30:50 +00:00
pam-sys = "0.5"
update to pam 0.7 (renamed from pam-auth) It now supports custom conversation methods, so instead of new() we ask for a default authenticator taking a password via with_password(). Since the password is now handled by the now separate conversation handler, `set_credentials()` is now called on the handler we get via `.get_handler()`. Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-02-15 09:32:14 +00:00
pam = "0.7"
src/backup/chunk_store.rs: use zstd compression insteadf of lz4 Provides better compressionm rate, and is still fast.
2019-03-07 10:42:59 +00:00
zstd = "0.4"
add protocol test client This uses futures for everything which is mostly useful as a test to see if the protocol crate's non-blocking I/O support can handle it... Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-03-06 09:23:56 +00:00
xdg = "2.2"
add missing mio crate for signalfd This is what actually provides EventedFd used by tokio. Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-03-12 07:05:55 +00:00
mio = "0.6"
tools: add helpful vector and read operations After importing the I/O ops trait via: use crate::tools::io::ops::*; Instead of: let mut buffer = vec![0u8; 65536]; file.read_exact(&mut buffer)?; use: let buffer = file.read_exact_allocated(65536)?; After importing the vector helpers via: use crate::tools::vec::{self, ops::*}; For a buffer which *could* be uninitialized but you prefer zero-initialization anyway for security reasons, instead of: let mut buffer = vec![0u8; len]; use: let mut buffer = vec::undefined(len); which zero-initializes, but, if the `valgrind` feature flag is enabled, marks the vector as having undefined contents, so reading from it will cause valgrind errors. Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-05-22 12:43:24 +00:00
valgrind_request = { version = "1.1", optional = true }
src/api_schema/format.rs: depend on textwrap, new wrap_text helper
2019-06-04 10:42:02 +00:00
textwrap = "0.11"
tools: add helpful vector and read operations After importing the I/O ops trait via: use crate::tools::io::ops::*; Instead of: let mut buffer = vec![0u8; 65536]; file.read_exact(&mut buffer)?; use: let buffer = file.read_exact_allocated(65536)?; After importing the vector helpers via: use crate::tools::vec::{self, ops::*}; For a buffer which *could* be uninitialized but you prefer zero-initialization anyway for security reasons, instead of: let mut buffer = vec![0u8; len]; use: let mut buffer = vec::undefined(len); which zero-initializes, but, if the `valgrind` feature flag is enabled, marks the vector as having undefined contents, so reading from it will cause valgrind errors. Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-05-22 12:43:24 +00:00
[features]
default = []
valgrind = ["valgrind_request"]
cargo: patch zstd-sys to use system library Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-03-07 10:50:32 +00:00
[replace]
bump zstd-sys version Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-06-05 07:44:43 +00:00
"zstd-sys:1.4.10" = { path = "zstd-sys" }