Installing from sources¶

Released packages¶

This page describes downloading and verifying apache-airflow-providers-fab provider version 1.5.0 using officially released packages. You can also install the provider package - as most Python packages - via PyPI . You can choose different version of the provider by selecting different version from the drop-down at the top-left of the page.

The sdist and whl packages released are the “official” sources of installation that you can use if you want to verify the origin of the packages and want to verify checksums and signatures of the packages. The packages are available via the Official Apache Software Foundations Downloads

The downloads are available at:

Sdist package (asc, sha512) - those are also official sources for the package
Whl package (asc, sha512)

If you want to install from the source code, you can download from the sources link above, it will contain a INSTALL file containing details on how you can build and install the provider.

Release integrity¶

PGP signatures KEYS

It is essential that you verify the integrity of the downloaded files using the PGP or SHA signatures. The PGP signatures can be verified using GPG or PGP. Please download the KEYS as well as the asc signature files for relevant distribution. It is recommended to get these files from the main distribution directory and not from the mirrors.

gpg -i KEYS

or

pgpk -a KEYS

or

pgp -ka KEYS

To verify the binaries/sources you can download the relevant asc files for it from main distribution directory and follow the below guide.

gpg --verify apache-airflow-providers-********.asc apache-airflow-*********

or

pgpv apache-airflow-providers-********.asc

or

pgp apache-airflow-providers-********.asc

Example:

$ gpg --verify apache-airflow-providers-fab-1.5.0.tar.gz.asc apache-airflow-providers-fab-1.5.0.tar.gz
  gpg: Signature made Sat 11 Sep 12:49:54 2021 BST
  gpg:                using RSA key CDE15C6E4D3A8EC4ECF4BA4B6674E08AD7DE406F
  gpg:                issuer "kaxilnaik@apache.org"
  gpg: Good signature from "Kaxil Naik <kaxilnaik@apache.org>" [unknown]
  gpg:                 aka "Kaxil Naik <kaxilnaik@gmail.com>" [unknown]
  gpg: WARNING: The key's User ID is not certified with a trusted signature!
  gpg:          There is no indication that the signature belongs to the owner.
  Primary key fingerprint: CDE1 5C6E 4D3A 8EC4 ECF4  BA4B 6674 E08A D7DE 406F

The “Good signature from …” is indication that the signatures are correct. Do not worry about the “not certified with a trusted signature” warning. Most of the certificates used by release managers are self signed, that’s why you get this warning. By importing the server in the previous step and importing it via ID from KEYS page, you know that this is a valid Key already.

For SHA512 sum check, download the relevant sha512 and run the following:

shasum -a 512 apache-airflow-providers-********  | diff - apache-airflow-providers-********.sha512

The SHASUM of the file should match the one provided in .sha512 file.

Example:

shasum -a 512 apache-airflow-providers-fab-1.5.0.tar.gz  | diff - apache-airflow-providers-fab-1.5.0.tar.gz.sha512

Verifying PyPI releases¶

You can verify the Provider .whl packages from PyPI by locally downloading the package and signature and SHA sum files with the script below:

#!/bin/bash
PACKAGE_VERSION=1.5.0
PACKAGE_NAME=apache-airflow-providers-fab
provider_download_dir=$(mktemp -d)
pip download --no-deps "${PACKAGE_NAME}==${PACKAGE_VERSION}" --dest "${provider_download_dir}"
curl "https://downloads.apache.org/airflow/providers/apache_airflow_providers_fab-1.5.0-py3-none-any.whl.asc" \
    -L -o "${provider_download_dir}/apache_airflow_providers_fab-1.5.0-py3-none-any.whl.asc"
curl "https://downloads.apache.org/airflow/providers/apache_airflow_providers_fab-1.5.0-py3-none-any.whl.sha512" \
    -L -o "${provider_download_dir}/apache_airflow_providers_fab-1.5.0-py3-none-any.whl.sha512"
echo
echo "Please verify files downloaded to ${provider_download_dir}"
ls -la "${provider_download_dir}"
echo

Once you verify the files following the instructions from previous chapter you can remove the temporary folder created.