IMHO backporting OpenAFS from trusty to precise (-backports) would be the best in this case and probably meet with customers/users requirement/expectation (just like Micheal pointed out).
With that in mind,
I have backported openafs, from trusty (1.6.7-1) to precise (1.6.7-1ubuntu1), and made available packages into a ppa that customers and users can access. Of course, just like in universe repository (where openafs stands), support here is based on a best-effort/community scenario.
I do need for this packages to be tested since I'm asking here for this to be available on -backports repository as well. For now, I was able to compile successfully openafs dkms on different kernels (3.5, 3.8, 3.11, 3.13) running on precise.
IMHO backporting OpenAFS from trusty to precise (-backports) would be the best in this case and probably meet with customers/users requirement/ expectation (just like Micheal pointed out).
With that in mind,
I have backported openafs, from trusty (1.6.7-1) to precise (1.6.7-1ubuntu1), and made available packages into a ppa that customers and users can access. Of course, just like in universe repository (where openafs stands), support here is based on a best-effort/ community scenario.
https:/ /launchpad. net/~inaddy/ +archive/ lp1206387
I do need for this packages to be tested since I'm asking here for this to be available on -backports repository as well. For now, I was able to compile successfully openafs dkms on different kernels (3.5, 3.8, 3.11, 3.13) running on precise.
inaddy@ 12-04-precise- lts-amd64: /var/lib/ dkms/openafs/ 1.6.7$ find . -name openafs.ko 0-27-generic/ x86_64/ module/ openafs. ko 41-generic/ x86_64/ module/ openafs. ko 0-22-generic/ x86_64/ module/ openafs. ko 49-generic/ x86_64/ module/ openafs. ko
./3.13.
./3.8.0-
./3.11.
./3.5.0-
Hope this helps... Attaching source on next commits.
Please provide feedback on test results.