Comment 11 for bug 288743

Now that openafs 1.4.8.dfsg1-3, which includes all of the necessary changes, is in Jaunty, only the control file entry for the new openafs-modules-dkms binary package needs to be uncommented. (It is commented in Debian because the Debian dkms package is still in the NEW queue.) Therefore, I request a FFE for this change.

The attached debdiff bumps the version to 1.4.8.dfsg1-3+ubuntu1, updates the maintainer to ubuntu-motu, and uncomments openafs-modules-dkms from debian/control.

(Why -3+ubuntu1 instead of -3ubuntu1? The openafs-modules-source package is built with module-assistant and results in a binary package named openafs-modules-2.6.28-11-generic with version 1.4.8.dfsg1-3+2.6.28-11.38. As it turns out, 1.4.8.dfsg1-3ubuntu1+2.6.28-11.38 would actually be a lower version. The Debian maintainer says that -3+ubuntu1 is consistent with the versioning scheme they use for Debian security updates.)

Risk of regression is very low because this only adds a new binary package and does not change the existing packages. The existing openafs-modules-source package still works with module-assistant as before, so users who do not choose to install openafs-modules-dkms will be unaffected.

As soon as the Debian dkms package enters unstable and openafs-modules-dkms is enabled in Debian, this Ubuntu patch can be dropped.

This package has been built and tested in my PPA. I verified that the openafs-modules-dkms package works correctly. Previous versions of it have been tested across kernel and openafs upgrades.
<https://launchpad.net/~anders-kaseorg/+archive/ppa>
(It is currently rebuilding with the new version number.)