Description of problem: many src packages that provide RPM build options that rely on dkms for kernel modules fail to build packages useable by mageia dkms 2.0.19 required minimum > 2.2.0.2 How reproducible: Always Example Software zfsonlinux Steps to Reproduce: 1. download spl or zfs tarball from zfsonlinux 2. unpack tarball 3. ./configure --with-spec=generic 4. copy src tarball to /root/rpmbuild/SOURCES/ 5. rpmbuild -bb rpm/generic/spl.spec 6. rpm -ivh /root/rpmbuild/RPMS/noarch/spl-dkms-0.6.5.3-1.mga5.noarch.rpm Result: error: Failed dependencies: dkms >= 2.2.0.2 is needed by spl-dkms-0.6.5.3-1.mga5.noarch This situation will just get worse as time goes on. I love all the work the mageia team do and would "like" to have plasma5, but I'd rather have an uptodate dkms system. Reproducible: Steps to Reproduce:
actually most of the changes between 2.0.19 and 2.2.0.2 are cosmetic or distro specific... just fix your spec to not require a specific dkms version... We will get to it if/when we see the real need for it as our dkms is heavily customized for mandriva/mageia... so it takes some time to review all of it and rebase... and we have more important stuff to fix before
CC: (none) => tmb
Severity: normal => enhancement
Assignee: bugsquad => kernel
Current upstream version is 2.3 (released on Aug 2016, 5 years after 2.2.0.3 [2011] and thus 8 years after 2.0.19 [2008]): https://github.com/dell/dkms/releases Couldn't find a human-readable changelog / release notes though. There's of course https://github.com/dell/dkms/commits/master
And indeed reviewing/rediffing all our patches would likely be quite some work: http://svnweb.mageia.org/packages/cauldron/dkms/current/SPECS/dkms.spec?view=markup When someone gets to it, there should likely also be some attempts done to get some of the patches upstreamed if relevant.
the work could be done in a branch in the svn the time it works.
CC: (none) => mageia
I'll take a crack at it...
Assignee: kernel => ngompa13CC: (none) => kernel, ngompa13Status: NEW => ASSIGNED
Blocks: (none) => 19779
The report is for Mageia 5 times, and bug#19779 is for Mageia 7 as both versions are EOL and for Mageia 8 & 9 I don't see this kind of bug, but Mageia 9 dkms is 2.0.19 and upstream is in 3.0.12
The problem is not just upgrading to latest upstream version, but to backport all the extra mageia patches that applies to 2.0.19 and not to 3.0.12; such patches adds new features (used by mageia) that are not in upstream code. There were some attempt, here: https://svnweb.mageia.org/packages/cauldron/dkms/branches/WIP/current/SPECS/dkms.spec?view=log but incomplete, and in the meanwhile the upstream code has changed a lot, so the work is basically to be redone from the beginning. Any volunteer welcome.
CC: (none) => ghibomgx
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=31835