Package Details: openafs 1.8.13.1-1

Git Clone URL: https://aur.archlinux.org/openafs.git (read-only, click to copy)
Package Base: openafs
Description: Open source implementation of the AFS distributed file system
Upstream URL: http://www.openafs.org
Licenses: IPL-1.0
Conflicts: openafs-features
Submitter: None
Maintainer: Bevan
Last Packager: Bevan
Votes: 61
Popularity: 0.000000
First Submitted: 2006-02-01 17:18 (UTC)
Last Updated: 2024-12-21 09:26 (UTC)

Latest Comments

« First ‹ Previous 1 .. 10 11 12 13 14 15 16 17 18 19 20 .. 32 Next › Last »

cptiglo commented on 2014-03-20 08:47 (UTC)

@Bevan: I am suggesting the following changes to your package files: http://www.treefish.org/~alex/afspatches openafs: * Changing package description from "client" to "open source implementation" to reflect that the openafs package does not only contain the client, but also database-/volume-server, pam-modules, etc... * Modified configure flags in order for the build not to depend on kernel headers. openafs-modules: * Made modules dependend on the latest kernel and kernel-headers major release, which is conform to the ARCH Kernel Module Package Guidelines (https://wiki.archlinux.org/index.php/Kernel_Module_Package_Guidelines). This ensures that the modules will be automatically rebuild when updating the kernel to a new major release. * Getting the latest kernel version from /usr/lib/modules/extramodules-x.xx-ARCH/version and not with "uname -r". This and adding the --with-linux-kernel-build flag to the configuration will ensure that the modules are always build for the latest installed kernel version even without a reboot. * Added the specific kernel major version to the depmod calls in the openafs-modules.install file. Updating the install-file to the correct kernel version using sed in the PKGBUILD (This is also done in the NVIDIA kernel module in the official ARCH repositories).

Bevan commented on 2014-03-19 22:35 (UTC)

I worked on splitting the package. You can find the result here: https://bitbucket.org/Bewahn/openafs-archlinux-package/get/master.tar.bz2 I will wait a bit before releasing it here so people who are interested can test it.

Bevan commented on 2014-03-18 17:12 (UTC)

@cptiglo: Definately on my TODO list. Unfortunately I didn't find time until now. I'll give it a higher priority in the next days.

cptiglo commented on 2014-03-18 11:20 (UTC)

@Beavan: Would you be willing to split your package in kernel module and userspace tools?

Bevan commented on 2014-01-20 23:58 (UTC)

@cptiglo: I think a first step would be to separate the kernel module and the userspace tools like it is done in the openafs-features package. This should be possible and would reduce the amount of code that needs to be rebuilt after a kernel update. A second step would then be to provide a openafs-dkms package that provides openafs-module (or whatever it's called). I have little to no experience with dkms so this would either require some effort by me or a package/patch from someone else. One way or the other the dkms package should be an alternative to a "classic" openafs-module package so that dkms is not strictly required.

cptiglo commented on 2014-01-20 23:03 (UTC)

@Bevan Wouldn't it be desireable to have the openafs kernel module in a separate openafs-dkms package to have it rebuild automatically on a kernel upgrade?

darkxsun commented on 2014-01-15 20:11 (UTC)

@nickoe Restarting the service succeeds for me even though it shows the reload message.

nickoe commented on 2014-01-15 20:07 (UTC)

@Bevan, well, I need to do the deamon-reload, systemctl don't allow me to ignore it. But I can indeed see the implication that it could make by making the install do it. Maybe it is best to do nothing further.

Bevan commented on 2014-01-15 20:03 (UTC)

@nickoe: Rebuilding the package is necessary after some but not all minor kernel updates. The last two kernel updates it was unfortunately nescessary. Regarding the service file: systemd detects that the service file was overwritten. If you just rebuild/reinstall the package you can safely ignore this because the file was overwritten with exactly the same content it had before. If you upgrade this package it might be that the content of the file changes (this was the case when we introduced encryption by default in this package). So I would recommend to do a daemon-reload after an upgrade. But if it is really necessary I will inform about this during upgrade. Reloading in the post install script would make this message disappear but I think this is not something people expect (and it could cause harm if people are working on service files in that moment or something fails during reload), so I won't include that.

« First ‹ Previous 1 .. 10 11 12 13 14 15 16 17 18 19 20 .. 32 Next › Last »