id summary reporter owner description type status priority milestone component version severity resolution keywords cc 198 Cannot run yum when logged onto non-writable volume or volume not supporting long filenames Lewis Rosenthal Silvan Scherrer "Paths (and path rewriters) all set correctly. %UNIXROOT% is set to J: (no trailing backslash) Running just {{{yum}}} from the following volumes produces different output: {{{ A: [FAT16] fails - see message, below C: [JFS] succeeds D: [HPFS] succeeds E: [DVD] fails - see message, below F: [NetWare] succeeds I: [NetDrive - ISOFS] succeeds J: [JFS] succeeds N: [HPFS] succeeds O: [FAT16] fails - see message, below Q: [FAT32] succeeds }}} Failure text (no yum.log): {{{ [e:\]yum Traceback (most recent call last): File ""/@unixroot/usr/lib/python2.7/site.py"", line 62, in import os File ""/@unixroot/usr/lib/python2.7/os.py"", line 400, in import UserDict ImportError: No module named UserDict }}} Obviously, !UserDict.py and friends look just fine, or we would not have success anywhere. Some package verisons: yum-plugin-verify-1.1.31-3.oc00.noarch yum-utils-1.1.31-3.oc00.noarch yum-3.4.3-10.oc00.pentium4 yum-plugin-versionlock-1.1.31-3.oc00.noarch yum-metadata-parser-1.1.4-7.oc00.pentium4 python-devel-2.7.6-14.oc00.pentium4 python-2.7.6-14.oc00.pentium4 python-libs-2.7.6-14.oc00.pentium4 libxml2-python-2.7.7-6.oc00.i386 python-pycurl-7.19.5.1-2.oc00.pentium4 rpm-python-4.13.0-9.oc00.pentium4 The mystery to me is how the !NetDrive-mapped read-only media is not a problem. Marking as critical because we need to be able to run yum from the Blue Lion installation media (DVD, usually). This was not the case with the previous bootstrap, but my latest one seems to have the latest files (the test above was from my production machine, which is regularly updated, and does not involve the bootstrap; the issue is easily reproduced on multiple systems with both fresh and maintained installations). Possibly related to #71?" defect closed Feedback Pending python medium fixed