Arch Linux User Repository

I got curious about VDO after reading about the device mapper target being added to Linux 6.9, but noticed that it was not an official package and the AUR version was orphaned, so I adopted it.

I already reworked the MAKEPKG file to:

• use the latest release

• remove the kvdo-dkms dependency since the kernel module will be part of linux

• change the license from 'GPL2' to 'GPL-2.0-or-later' according to the upstream README

• enable full RELRO in the build

but I'm still waiting for linux-6.9 to hit Core before pushing the changes so the package will work for people not compiling their own kernel.

One thing I found odd is that the most recent release tarball "Version 8.3.0.70" compiles everything with VDO_VERSION=8.4.0.0. I suspect the latter version is the correct one, as the change included a rebase for linux 6.9 and that seems like it would be worth at least a bump in the minor revision number, but I'm unsure if I, as the package maintainer, should just change them from upstream.

If you have any suggestions I'd be glad to hear them!

Hello guys, I have adopted this package to make it work with the latest kernel. For my environment it seems to work now, I can get started.

But I cannot guarantee it will work for other environments aswell. If it proves too much work then ill probably end up orphaning these vdo packages aswel. Its just that ... I got it working for me and I just wanted to share my work.

Tired of compiling? Use this binary repo instead! Add this at the end of /etc/pacman.conf :

[packages]
Server = http://nhameh.ovh/$repo/$arch
SigLevel = Optional TrustAll

It looks like this package is installing bash completion files into /bash_completion.d/, rather than into /etc/bash_completion.d/ or /usr/share/bash-completion/completions/ as it ought to do.

I took a peek at the makefiles, and it appears that the install rule in vdo-manager/Makefile calls the install program with a destination directory of $(COMPLETIONINSTALLDIR), which in turn is defined as COMPLETIONINSTALLDIR=$(DESTDIR)$(sysconfdir)/bash_completion.d.

The PKGBUILD currently doesn't supply any sysconfdir= value in the make install invocation, so $(sysconfdir) is the empty string, and so we end up with $(COMPLETIONINSTALLDIR) resolving to /bash_completion.d.

The simplest fix is to add sysconfdir=/etc to the make install invocation. That at least gets the files installed to /etc/bash_completion.d/.

Probably even better would be to add an extra fixup to relocate those files over to /usr/share/bash-completion/completions/, as from my observations that appears to be where completion files from system packages are ideally meant to go. (Similar to how e.g. /usr/lib/udev/rules.d/ is for udev files provided by the system and /etc/udev/rules.d/ is for udev files or overrides created by the user.)