-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've recently made some improvements to our Fedora / RHEL build
system, which I thought I'd share with you all. These put the build
system on a more reliable footing - removing all bar one human step
from getting new kernel modules out into the world, and increase its
capacity for building for more operating systems.
Firstly, I should outline what I'm going to provide. In the stable
series, kernel modules will be built for the current and previous
release (so we're currently building 1.4.7 and 1.4.8) for all versions
of RHEL newer than 4, and the current and previous 3 Fedora releases
(so we're building for RHEL4, RHEL5, and Fedoras 7 thru 10). Where
necessary, I'll pick up patches from the OpenAFS CVS to keep the
current release building on all of these platforms. I won't, however,
update previous releases - as and when they stop building for a
particular architecture, I'll just stop building them (so we have
1.4.8 for every platform, but 1.4.7 isn't being built for Fedoras 9 or
10). We're currently building for both i386 and x86_64 platforms.
Secondly, due to popular demand, packages coming out of the build
system are now being signed with a GPG key. The details of this key
are below. Note that this is intentionally not a personal, or
institutional, key. All that the presence of this key indicates is
that the package was successfully built on lochranza, and hasn't been
tampered with since it left that system. No personal guarantees are
made, or should be implied. The key should be on the keyservers, and
has the following key ID and fingerprint:
pub 1024D/C19E4A0A 2008-11-21
Key fingerprint = 7FD2 7090 17A6 457B C146 3B12 14F5 6B3F C19E
4A0A
uid OpenAFS builds from lochranza
Thirdly, the new system builds modules every evening at 17:30 UTC.
Copying modules over to the OpenAFS download site is still a manual
process, and there may be some latency between builds being generated,
and them being copied and the relevant volumes released. Also, the
regeneration of the html distribution pages requires an additional
manual step. On many occasions new kernel module RPMs will be
available from the repository, but not listed in the distribution
pages. Browsing to /afs/grand.central.org/software/openafs/<version>/
will always let you see the latest RPMs available for your system.
Other factors that may cause delays are mirroring of kernel modules,
and the fact that we build from the Centos distribution, rather than
direct from RHEL. The Centos delay causes particular problems around
major and point operating system releases - for example, builds for
kernels in RHEL 5.3 will not become available until Centos 5.3 ships,
which may be some weeks afterwards.
Finally, I'm also generating RPMs for the 1.5.x development release.
Please let me know if you're interested in using these RPMs to test
1.5.x at your site.
Cheers,
Simon.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
iD8DBQFJKy2eqWndc26pXmcRAgVCAKCb7AzGCDlS8RvnNRHZKiygMYPvVACeLSl0
vXNuScaSXuJSLtOUZXS6QG4=
=9JHZ
-----END PGP SIGNATURE-----
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
