PyCA's cryptography library

Go to file

Yaakov Selkowitz a64728bbef Use vendored rust-pem in RHEL builds		2023-06-13 14:51:32 -04:00
.gitignore	Update to 40.0.2	2023-05-15 13:43:05 +02:00
conftest-skipper.py	Skip iso8601 and pretend tests on RHEL	2021-02-12 16:47:08 +01:00
python-cryptography.spec	Use vendored rust-pem in RHEL builds	2023-06-13 14:51:32 -04:00
README.md	Update to 3.4.7, use vectors from sources (#1952024 )	2021-04-22 08:07:57 +02:00
sources	Update to 40.0.2	2023-05-15 13:43:05 +02:00
vendor_rust.py	Create reproducible tar file	2021-02-16 14:33:41 +01:00

README.md

PyCA cryptography

https://cryptography.io/en/latest/

Packaging python-cryptography

The example assumes

Fedora Rawhide (f34)
PyCA cryptography release 3.4
Update Bugzilla issue is RHBZ#00000001

Build new python-cryptography

Switch and update branch

fedpkg switch-branch rawhide
fedpkg pull

Bump version and get sources

rpmdev-bumpspec -c "Update to 3.4 (#00000001)" -n 3.4 python-cryptography.spec
spectool -gf python-cryptography.spec

Upload new source

fedpkg new-sources cryptography-3.4.tar.gz

Commit changes

fedpkg commit --clog
fedpkg push

Build

fedpkg build

RHEL/CentOS builds

RHEL and CentOS use a different approach for Rust crates packaging than Fedora. On Fedora Rust dependencies are packaged as RPMs, e.g. rust-pyo3+default-devel RPM. These packages don't exist on RHEL and CentOS. Instead python-cryptography uses a tar ball with vendored crates. The tar ball is created by a script:

./vendor_rust.py
rhpkg upload cryptography-3.4-vendor.tar.bz2