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

68 lines
2.0 KiB
TOML
Raw Normal View History

initial version
2018-10-30 10:04:30 +01:00
[package]
use proxmox-backup as package name
2018-12-20 10:32:49 +01:00
name = "proxmox-backup"
bump version to 0.8.19-1
2020-09-22 13:30:52 +02:00
version = "0.8.19"
initial version
2018-10-30 10:04:30 +01:00
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 14:42:27 +01:00
edition = "2018"
switch to debcargo for generating d/control Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
2020-01-15 10:29:57 +01:00
license = "AGPL-3"
description = "Proxmox Backup"
homepage = "https://www.proxmox.com"
exclude = [ "build", "debian", "tests/catar_data/test_symlink/symlink1"]
move code into lib.rs
2018-10-30 10:40:05 +01:00
[lib]
use proxmox-backup as package name
2018-12-20 10:32:49 +01:00
name = "proxmox_backup"
move code into lib.rs
2018-10-30 10:40:05 +01:00
path = "src/lib.rs"
initial version
2018-10-30 10:04:30 +01:00
[dependencies]
add .../apt/update API call Depends on patched apt-pkg-native-rs. Changelog-URL detection is inspired by PVE perl code for now, though marked with fixme to use 'apt changelog' later on, if/when our repos have APT-compatible changelogs set up. list_installed_apt_packages iterates all packages and creates an APTUpdateInfo with detailed information for every package matched by the given filter Fn. Sadly, libapt-pkg has some questionable design choices regarding their use of 'iterators', which means quite a bit of nesting... Signed-off-by: Stefan Reiter <s.reiter@proxmox.com>
2020-07-21 13:41:07 +02:00
apt-pkg-native = "0.3.1" # custom patched version
update dependencies Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
2020-05-18 09:06:44 +02:00
base64 = "0.12"
add tools/disks.rs (work in progress...) Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2020-05-05 10:14:41 +02:00
bitflags = "1.2.1"
update a chunk of stuff to the hyper release Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-12-12 15:27:07 +01:00
bytes = "0.5"
switch to futures 0.3 * cleanup Cargo.toml * pull in tower_service (required for newer hyper) * use local hyper-openssl fixup (its Cargo.toml has broken outdated dependencies) * add pin-utils dependency Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-08-23 12:20:33 +02:00
crc32fast = "1"
endian_trait = { version = "0.6", features = ["arrays"] }
switch from failure to anyhow Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2020-04-17 14:11:25 +02:00
anyhow = "1.0"
update a chunk of stuff to the hyper release Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-12-12 15:27:07 +01:00
futures = "0.3"
h2 = { version = "0.2", features = ["stream"] }
change index to templates using handlebars using a handlebars instance in ApiConfig, to cache the templates as long as possible, this is currently ok, as the index template can only change when the whole package changes if we split this in the future, we have to trigger a reload of the daemon on gui package upgrade (so that the template gets reloaded) Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
2020-04-29 11:59:31 +02:00
handlebars = "3.0"
update a chunk of stuff to the hyper release Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-12-12 15:27:07 +01:00
http = "0.2"
server: set http2 max frame size else we get the default of 16k, which is quite low for our use case. this improves the TLS upload benchmark speed by about 30-40% for me. Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
2020-09-10 10:36:33 +02:00
hyper = "0.13.6"
Cargo.toml: update dependencies to those that are packaged. Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
2019-12-18 10:47:30 +01:00
lazy_static = "1.4"
impl sweep_used_chunks, first try
2018-12-19 09:51:33 +01:00
libc = "0.2"
switch to futures 0.3 * cleanup Cargo.toml * pull in tower_service (required for newer hyper) * use local hyper-openssl fixup (its Cargo.toml has broken outdated dependencies) * add pin-utils dependency Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-08-23 12:20:33 +02:00
log = "0.4"
update to nix 0.16
2019-12-19 09:29:44 +01:00
nix = "0.16"
add statistics module provides some basic statistics functions (sum, mean, etc.) and a function to return the parameters of the linear regression of two variables implemented using num_traits to be more flexible for the types Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
2020-06-09 10:01:12 +02:00
num-traits = "0.2"
add tools/disks.rs (work in progress...) Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2020-05-05 10:14:41 +02:00
once_cell = "1.3.1"
use newer versions
2019-01-20 10:06:29 +01:00
openssl = "0.10"
switch to futures 0.3 * cleanup Cargo.toml * pull in tower_service (required for newer hyper) * use local hyper-openssl fixup (its Cargo.toml has broken outdated dependencies) * add pin-utils dependency Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-08-23 12:20:33 +02:00
pam = "0.7"
pam-sys = "0.5"
update to url/percent-encoding to 2.1 Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-12-13 11:55:52 +01:00
percent-encoding = "2.1"
update pin-utils dep to stable version Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
2020-05-14 11:46:05 +02:00
pin-utils = "0.1.0"
bump pathpatterns to 0.1.2 Fixes `**/foo` not matching "foo" without slashes. (`**/lost+found` now matches the `lost+found` dir at the root of our tree properly). Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2020-07-09 14:33:07 +02:00
pathpatterns = "0.1.2"
bump proxmox version to 0.4.1
2020-09-21 13:51:33 +02:00
proxmox = { version = "0.4.1", features = [ "sortable-macro", "api-macro", "websocket" ] }
cargo: add alternative proxmox crate locations for convenience Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
2020-01-08 15:12:37 +01:00
#proxmox = { git = "ssh://gitolite3@proxdev.maurer-it.com/rust/proxmox", version = "0.1.2", features = [ "sortable-macro", "api-macro" ] }
api2/nodes: add termproxy and vncwebsocket api calls Even though it has nothing to do with vnc, we keep the name of the api call for compatibility with our xtermjs client. termproxy: verifies that the user is allowed to open a console and starts termproxy with the correct parameters starts a TcpListener on "localhost:0" so that the kernel decides the port (instead of trying to rerserving like in pve). Then it leaves the fd open for termproxy and gives the number as port and tells it via '--port-as-fd' that it should interpret this as an open fd the vncwebsocket api call checks the 'vncticket' (name for compatibility) and connects the remote side (after an Upgrade) with a local TcpStream connecting to the port given via WebSocket from the proxmox crate to make sure that only the client can connect that called termproxy and no one can connect to an arbitrary port on the host we have to include the port in the ticket data Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
2020-07-21 11:10:38 +02:00
#proxmox = { path = "../proxmox/proxmox", features = [ "sortable-macro", "api-macro", "websocket" ] }
Cargo.toml: pathpatterns, pxar, proxmox-fuse Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2020-04-23 12:26:14 +02:00
proxmox-fuse = "0.1.0"
depend on pxar 0.6.1
2020-09-18 12:02:17 +02:00
pxar = { version = "0.6.1", features = [ "tokio-io", "futures-io" ] }
Cargo.toml: pathpatterns, pxar, proxmox-fuse Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2020-04-23 12:26:14 +02:00
#pxar = { path = "../pxar", features = [ "tokio-io", "futures-io" ] }
Cargo.toml: update dependencies to those that are packaged. Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
2019-12-18 10:47:30 +01:00
regex = "1.2"
update dependencies Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
2020-05-18 09:06:44 +02:00
rustyline = "6"
switch to futures 0.3 * cleanup Cargo.toml * pull in tower_service (required for newer hyper) * use local hyper-openssl fixup (its Cargo.toml has broken outdated dependencies) * add pin-utils dependency Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-08-23 12:20:33 +02:00
serde = { version = "1.0", features = ["derive"] }
serde_json = "1.0"
use external crate siphasher Because std::hash::SipHasher is deprecated.
2018-12-28 19:50:07 +01:00
siphasher = "0.3"
switch to futures 0.3 * cleanup Cargo.toml * pull in tower_service (required for newer hyper) * use local hyper-openssl fixup (its Cargo.toml has broken outdated dependencies) * add pin-utils dependency Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-08-23 12:20:33 +02:00
syslog = "4.0"
api2/nodes: add termproxy and vncwebsocket api calls Even though it has nothing to do with vnc, we keep the name of the api call for compatibility with our xtermjs client. termproxy: verifies that the user is allowed to open a console and starts termproxy with the correct parameters starts a TcpListener on "localhost:0" so that the kernel decides the port (instead of trying to rerserving like in pve). Then it leaves the fd open for termproxy and gives the number as port and tells it via '--port-as-fd' that it should interpret this as an open fd the vncwebsocket api call checks the 'vncticket' (name for compatibility) and connects the remote side (after an Upgrade) with a local TcpStream connecting to the port given via WebSocket from the proxmox crate to make sure that only the client can connect that called termproxy and no one can connect to an arbitrary port on the host we have to include the port in the ticket data Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
2020-07-21 11:10:38 +02:00
tokio = { version = "0.2.9", features = [ "blocking", "fs", "dns", "io-util", "macros", "process", "rt-threaded", "signal", "stream", "tcp", "time", "uds" ] }
update a chunk of stuff to the hyper release Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-12-12 15:27:07 +01:00
tokio-openssl = "0.4.0"
update dependencies Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
2020-05-18 09:06:44 +02:00
tokio-util = { version = "0.3", features = [ "codec" ] }
update a chunk of stuff to the hyper release Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-12-12 15:27:07 +01:00
tower-service = "0.3.0"
bump udev build-dependency 0.4 contains a fix for C chars on non-x86 architectures. Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
2020-07-20 12:07:45 +02:00
udev = ">= 0.3, <0.5"
update to url/percent-encoding to 2.1 Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-12-13 11:55:52 +01:00
url = "2.1"
switch to debcargo for generating d/control Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
2020-01-15 10:29:57 +01:00
#valgrind_request = { git = "https://github.com/edef1c/libvalgrind_request", version = "1.1.0", optional = true }
backup/datastore.rs: list all index files using walkdir crate
2019-01-18 12:24:58 +01:00
walkdir = "2"
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 10:23:56 +01:00
xdg = "2.2"
drop our zstd-sys replacement Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2019-12-18 12:23:10 +01:00
zstd = { version = "0.4", features = [ "bindgen" ] }
depend on nom, add parser for systemd calendar enents and time span
2020-05-14 12:17:20 +02:00
nom = "5.1"
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 14:43:24 +02:00
[features]
default = []
switch to debcargo for generating d/control Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
2020-01-15 10:29:57 +01:00
#valgrind = ["valgrind_request"]
Reference in New Issue Copy Permalink