Description of problem: "dkms mkrpm" fails on x86_64 because it tries to run /usr/lib/dkms/find-provides and find-provides is actually in /usr/lib64/dkms/. If I link /usr/lib/dkms to /usr/lib64/dkms, it then hangs running gzip on the tarball it makes, according to ps. Sorry I haven't time to debug it. Version-Release number of selected component (if applicable): 2.2.0.3-8.el6 How reproducible: Consistently. Steps to Reproduce: 1. dkms mkrpm -m ... -v ... 2. ln -s /usr/lib64/dkms /usr/lib 3. dkms mkrpm -m ... -v ...
Thanks for reporting. Can you please test dkms-2.2.0.3-12.el6? http://koji.fedoraproject.org/koji/buildinfo?buildID=436564 http://koji.fedoraproject.org/koji/packageinfo?packageID=1605 Thanks, --Simone
Created attachment 776887 [details] fix hang with mkrpm I just realize what was causing the hang. There was an existing compressed result and gzip was run without --force.
Did you patch the package in comment #1 or the one that was installed in your system?
Can you please test this build? Is comment #1's package with your patch. No lib64/lib link should be required: http://koji.fedoraproject.org/koji/buildinfo?buildID=436634
(In reply to Simone Caronni from comment #3) > Did you patch the package in comment #1 or the one that was installed in > your system? The latter. I haven't had time to try the new version yet, not used to such a swift response, thanks! I assume it's only necessary because the previous attempt to build the rpm failed and left the file around, but I think the compression should always be forced, and not hang the script with an existing output file.
(In reply to Dave Love from comment #5) > I assume it's only necessary because the previous attempt to build the > rpm failed and left the file around, but I think the compression > should always be forced, and not hang the script with an existing output > file. Agree, but the fix I added in comment #1 is needed anyway, some parts of DKMS have hard-coded /usr/lib/dkms paths in. Package from comment #4 should contain both fixes.
dkms-2.2.0.3-14.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/dkms-2.2.0.3-14.fc19
dkms-2.2.0.3-14.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/dkms-2.2.0.3-14.fc18
dkms-2.2.0.3-14.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/dkms-2.2.0.3-14.fc17
dkms-2.2.0.3-14.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/dkms-2.2.0.3-14.el6
dkms-2.2.0.3-14.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/dkms-2.2.0.3-14.el5
Please leave feedback in Bodhi!
Package dkms-2.2.0.3-14.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing dkms-2.2.0.3-14.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-10949/dkms-2.2.0.3-14.el6 then log in and leave karma (feedback).
(In reply to Simone Caronni from comment #12) > Please leave feedback in Bodhi! I don't know what that means, but I think the current version fixes the problem and this can be closed, thanks.
dkms-2.2.0.3-14.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
dkms-2.2.0.3-14.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
dkms-2.2.0.3-14.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
dkms-2.2.0.3-14.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.