Add basic docs on updating the OpenAFS ppa
This adds documentation that should at least remind us that we have a repo with the .deb files for our openafs packages and roughly how to go about updating them. Change-Id: I4e52be22eef0cf9daf8e3d92d3df04fa3a523c2f
This commit is contained in:
parent
1290609bd5
commit
d1dcda1410
@ -34,6 +34,7 @@ At a Glance
|
||||
* :git_file:`playbooks/service-mirror-update.yaml`
|
||||
:Projects:
|
||||
* http://openafs.org/
|
||||
* http://opendev.org/opendev/infra-openafs-deb
|
||||
:Bugs:
|
||||
* http://bugs.launchpad.net/openstack-ci
|
||||
* `http://rt.central.org/...SNIPPED... <http://rt.central.org/rt/Search/Results.html?Order=ASC&DefaultQueue=10&Query=Queue%20%3D%20%27openafs-bugs%27%20AND%20%28Status%20%3D%20%27open%27%20OR%20Status%20%3D%20%27new%27%29&Rows=50&OrderBy=id&Page=1&Format=&user=guest&pass=guest>`_
|
||||
@ -720,3 +721,29 @@ that only A (IPv4 address) records are used in the SRV data. Since OpenAFS
|
||||
lacks support for IPv6, avoid entering corresponding AAAA (IPv6 address)
|
||||
records for these so that it won't cause fallback delays for other
|
||||
v6-supporting AFS client implementations.
|
||||
|
||||
Custom Packages
|
||||
---------------
|
||||
|
||||
We run custom built packages (typically so that we have access to
|
||||
bugfixes faster than appear in Ubuntu). The packages are in the
|
||||
`openstack-ci-core` PPA on launchpad.
|
||||
|
||||
The deb configuration files are contained in the
|
||||
`opendev/infra-openafs-deb` repo. Changes to that repo cause the
|
||||
packages to be built in the check and gate pipeline for build
|
||||
verification, and the promote pipeline uploads the package definition
|
||||
to the PPA for launchpad to build.
|
||||
|
||||
This repo has a branch for each target to build. To create a new
|
||||
operating system target, make a new branch.
|
||||
|
||||
To update the contents of a branch, the `debian/*` files may need to
|
||||
be updated by copying from the upstream debian package. The
|
||||
`make-orig.sh` script should be updated to point to new upstream
|
||||
version archives.
|
||||
|
||||
Push a change to the appropriate target branch, merge it, and check on
|
||||
the launchpad PPA to verify that it built correctly. If launchpad was
|
||||
unable to build the package, you may need to fix it and increment the
|
||||
revision number to trigger a new build.
|
||||
|
Loading…
Reference in New Issue
Block a user