# python-cryptography

**Repository Path**: src-oepkgs-fedora-rv/python-cryptography

## Basic Information

- **Project Name**: python-cryptography
- **Description**: No description available
- **Primary Language**: Unknown
- **License**: Not specified
- **Default Branch**: bz1952522
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2021-10-05
- **Last Updated**: 2022-04-17

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# 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

```shell
fedpkg switch-branch rawhide
fedpkg pull
```

Bump version and get sources

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

Upload new source

```shell
fedpkg new-sources cryptography-3.4.tar.gz
```

Commit changes

```shell
fedpkg commit --clog
fedpkg push
```

Build

```shell
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:

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