Description of problem: "yum install" uses some strange "doubled" pathname prefixes: "/ext4/Fedora13/work/x86_64/tmp/yumdir.5182/ext4/Fedora13/work/x86_64/tmp/yumdir.5182" where the string repeats itself after the first "yumdir.5182". During a typical pungi compose of DVD then there are about 16800 system calls which specify such strings. This is inefficient. Version-Release number of selected component (if applicable): yum-3.2.25-12.fc13.noarch How reproducible: every time Steps to Reproduce: 1. strace -f -s 256 -o "| gzip -c >/tmp/strace-pungi.$$.gz" \ -e trace=file,write,pwrite,fork,vfork,clone -v \ pungi -c /usr/share/pungi/rawhide-fedora.ks --destdir=$DESTDIR \ --name Fedora --ver $VERSION --nosource 2. grep decompressed strace output for 'yumdir[^"]*yumdir' 3. Actual results: 5197 execve("/usr/bin/yum", ["yum", "--quiet", "-c", "/ext4/Fedora13/work/x86_64/tmp/yum.conf.RxZIbc", "-y", "--installroot=/ext4/Fedora13/work/x86_64/tmp/yumdir.5182", "install", ... ... 5197 stat("/ext4/Fedora13/work/x86_64/tmp/yumdir.5182/ext4/Fedora13/work/x86_64/tmp/yumdir.5182/var/lib/yum/yumdb", 0x7fffd9a802d0) = -1 ENOENT (No such file or directory) ... 5197 mkdir("/ext4/Fedora13/work/x86_64/tmp/yumdir.5182/ext4/Fedora13/work/x86_64/tmp/yumdir.5182", 0777) = 0 ---- and so forth. The "doubling" is not part of the specified --installroot pathname. Instead, probably there is misuse of chroot() and/or chdir() for "." and/or "/". Expected results: No "doubled" pathname prefixes. Additional info:
It looks like this is an interaction with the environment variable TMPDIR, specifically mkstemp() [and/or mktemp()] after chroot(). Probably TMPDIR should be adjusted (and/or removed from the environment) when chroot() is called.
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle. Changing version to '13'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fixed in upstream and will be in the next pkg built for f13 and rawhide. commit 1: http://yum.baseurl.org/gitweb?p=yum.git;a=commitdiff;h=9714379777bfa6569a46ef8d2cc1131b951eebf7 and commit 2: http://yum.baseurl.org/gitweb?p=yum.git;a=commitdiff;h=f48b1d9f0ede0eae518f5b353ed9dda74dde6d7c
yum-3.2.27-4.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/yum-3.2.27-4.fc13
yum-3.2.27-4.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update yum'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/yum-3.2.27-4.fc13
yum-3.2.27-4.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
yum-3.2.28-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/yum-3.2.28-1.fc13
yum-3.2.28-1.fc14 has been submitted as an update for Fedora 14. http://admin.fedoraproject.org/updates/yum-3.2.28-1.fc14
yum-3.2.28-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/yum-3.2.28-1.fc12
yum-3.2.28-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
yum-3.2.28-3.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/yum-3.2.28-3.fc12
yum-3.2.28-3.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/yum-3.2.28-3.fc13
yum-3.2.28-3.fc14 has been submitted as an update for Fedora 14. http://admin.fedoraproject.org/updates/yum-3.2.28-3.fc14
yum-3.2.28-3.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
yum-3.2.28-3.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
yum-3.2.28-3.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.