Description of problem: During repeated RPM compilation, /tmp/wafcache tends to fill and use all vailable inodes. Version-Release number of selected component (if applicable): smaba-4.0.4-2 and all previous samba-4.x releases How reproducible: Completely. Steps to Reproduce: 1. rpmbbuild --rebuild samba-4.0.4-2.fc20.src.rpm 2. find /tmp/wafcache | wc 3. Repeat half a dozen times in development Actual results: Complete operating system failure if you re-build the RPM's too many times in time. Expected results: Not to overwhelm th eoperating sytem. Additional info: Easily fixed by setting "export WAFCACHE=$PWD/wafcache", in the build directory, instead of using /tmp/. This wouldn't ordinarily show up in a koji or mock build environment, but is deadly when compiling locally, and reflects a fundamental flaw in WAFCACHE handling. If WAFCACHE is going to continue to be used by other python build systems, then we need a designated location and a cron job to scrub it.
samba-4.0.4-3.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/samba-4.0.4-3.fc18
Package samba-4.0.4-3.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing samba-4.0.4-3.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-4247/samba-4.0.4-3.fc18 then log in and leave karma (feedback).
samba-4.0.4-3.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.