Recompile dahdi modules on kernel upgrade

Hi,
I am a NethServer developer and as just explained here we are trying to have FreePBX 14 packaged for NS.

My problem is that after upgrade kernel from 3.10.0-327.22.2.el7.x86_64 to 3.10.0-327.28.3.el7, dahdi kernel modules are not automatically recompiled.

kmod-dahdi-linux provides dahdi modules for 3.10.0-327.22.2.el7.x86_64. Is it scheduled to have the automatic re-compilation @bwalters ?

p.s. I’ve tried the following solution:

cp -r /lib/modules/3.10.0-327.22.2.el7.x86_64/dahdi/* /lib/modules/3.10.0-327.22.2.el7.x86_64/extra
yum update kernel

and at the end new dahdi modules are present into /lib/modules/3.10.0-327.28.3.el7.x86_64/weak-updates/

Yes as kernels are released we will release dahdi and wanpipe updates but right now everything is in early Alpha stages so we are not keeping up with kernel updates. When we go into stable this will automatically happen on our jenkin build servers when new kernels are released. @xrobau handles this.

Perfect, but you could avoid to release a new package each time. If you put dahdi kernel modules into

/lib/modules/3.10.0-327.22.2.el7.x86_64/extra/dahdi

instead of

/lib/modules/3.10.0-327.22.2.el7.x86_64/dahdi

kernel upgrade itself links the new dahdi modules automatically using weak-modules script.
New dahdi modules are placed for example into the new directory

/lib/modules/3.10.0-327.28.3.el7.x86_64/weak-updates/dahdi/

We’re explicitly not using weak linking at the moment, because we’ve had numerous issues with it catastrophically breaking on 5 and 6 kernels (historically it’s been the xpp-usb drivers and… another one I have forgotten 8-))

When we get some time I’ll try it again on 7.

Also wanpipe has to build against the specific kernel and dahdi so we are stuck building wanpipe for each minor release of dahdi and kernels regardless.