openstack-zuul-jobs/roles/openafs-deb-package-build
Ian Wienand 183000d937 openafs-deb-package-build: use upstream source
As noted inline, if the source already exists we need to use it from
the primary archive.  Do this for 1.8.8.1 but leave notes behind on
building non-packaged versions.

Change-Id: I6d637c81dd4a8d712b5fa84722d7559178e40de2
2022-05-05 14:01:13 +10:00
..
files/debian openafs: generate deb packages for openstack-ci PPA 2022-05-04 13:39:10 +10:00
tasks openafs-deb-package-build: use upstream source 2022-05-05 14:01:13 +10:00
README.rst openafs-deb-package-build: add some explainers to README 2022-05-05 09:13:20 +10:00

README.rst

Build OpenAFS Ubuntu Packages

This builds openafs source packages and, with the publishing steps, pushes them to be built by as an Ubuntu PPA.

OpenDev has traditionally kept separate OpenAFS packages in a PPA which are used by production hosts. In the past the LTS distro versions have had bugs, or lacked support for architectures/kernels (ARM64 + HWE kernels, practically) we needed -- necessitating keeping separate, fresh versions.

Upstream packages keep a PPA at https://launchpad.net/~openafs/+archive/ubuntu/stable

As much as possible, we generally import and use their debian/* infrastructure (including patches, etc.) as a base here. This PPA doesn't build all the architectures we need, but also isn't focused on the immediate needs of OpenDev production; thus despite it's regular maintence it is still helpful for us to have our own package builds.

These problems are much less with current distros (>= 2022) and openafs 1.8 series; our goal is to generally carry no differences.

Note the openafs-rpm-package-build jobs are a counter-part to this, as OpenAFS hasn't been available on RPM distros. We try to keep these in sync so our infrastructure is more or less at the same level.