Device-mapper thin provisioning tools

Go to file

Marian Csontos 130ef4c9c2 Fix testing issues Tests are sometimes failing non deterministicly on some architectures. We were bitten by some tests exhausting available disk in the past with similar results. This is not reproducible by developer so trying to reduce the environment complexity. Related: RHEL-65306 RHEL-57084		2024-10-30 16:48:35 +01:00
tests	Fix some compatibility issues with Python3	2024-01-18 13:36:46 +01:00
.gitignore	Update to version 1.1.0	2024-10-30 11:45:32 +01:00
0001-Tweak-cargo.toml-to-work-with-vendor-directory.patch	Update to version 1.1.0	2024-10-30 11:45:32 +01:00
device-mapper-persistent-data-avoid-strip.patch	New upstream release v0.7.2	2017-09-22 09:05:47 +02:00
device-mapper-persistent-data.spec	Fix testing issues	2024-10-30 16:48:35 +01:00
README.md	Update to upstream release 0.9.0	2020-09-17 17:23:28 +02:00
sources	Update to version 1.1.0	2024-10-30 11:45:32 +01:00

Packaging dmpd

This is mostly regular package except recent addition of rust to used languages.

rust-tools

To build the rust-tools (make rust-tools) one needs:

rust >= 1.35
cargo with vendor subcommand (now upstream, included in latest Fedora and RHEL8)

run cargo vendor in the disrectory with sources
run tar czf device-mapper-persistent-data-vendor-$VERSION.tar.gz ./vendor
copy the file (if version changed) and run the fedpkg new-sources command:
- fedpkg new-sources v$VERSION.tar.gz device-mapper-persistent-data-vendor-$VERSION.tar.gz

Some of the dependencies may be already packaged by Fedora. Can we instruct cargo vendor to include only those which are not provided by Fedora?

%cargo_install installs by defualt in /usr/bin but the package expects /usr/sbin. For now I run make install-rust-tools.