thanks a lot, and thanks for the corrections.
Anyway I never use more than one dkms module built for different kernel
versions and usually I build the lustre dkms module always on the
current version of the running kernel, but yes your fixes will address
correctly the issues you mentioned and
Hi,
Am Mittwoch, dem 13.10.2021 um 16:06 -0700 schrieb Riccardo Veraldi:
>
> This is my patch to make things works and build the lustre-dkms rpm
Thank you! I just ran into the exact same problem. Two comments on the
patch:
> - ZFS_VERSION=$(dkms status -m zfs -k $3 -a $5 | awk -F', ' '{prin
Riccardo,
It would be great if you could submit your patch to Gerrit.
Cheers, Andreas
> On Oct 13, 2021, at 17:06, Riccardo Veraldi
> wrote:
>
> yes, same problem for me, I Addressed this a few weeks go and I think I
> Reported to the mailing list.
>
> This is my patch to make things works
yes, same problem for me, I Addressed this a few weeks go and I think I
Reported to the mailing list.
This is my patch to make things works and build the lustre-dkms rpm
diff -ru lustre-2.12.7/lustre-dkms_pre-build.sh
lustre-2.12.7-dkms-pcds/lustre-dkms_pre-build.sh
--- lustre-2.12.7/lustre-d
dkms was recently updated to version 2.8.6 in epel/7.
After this update installation of lustre-zfs-dkms-2.12.7-1.el7.noarch
fails with following error:
./configure: line 33341: test: zfs: integer expression expected
configure: error:
Breakage seems to be caused by following dkms commit:
https