Custom Query (344 matches)

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 <module>
    import os
  File "/@unixroot/usr/lib/python2.7/os.py", line 400, in <module>
    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?

I have seen this on several systems now, but I am not sure whether it may be a dependency issue (ordering of packages). YUM | update all from ANPM produces an error panel when finishing:

error: %prein(coreutils-8.25-1.oc00.i686) scriptlet failed, with exit status 2

I can;t find a report in yum.log or in anpm.log, and yum reinstall coreutils from a prompt seems to run without the error.

I'll update a few more systems from the prompt and see if i can catch this happening, as it would be odd for it to be coming from ANPM.

I also can't find anything actually wrong with anything in the coreutils package, either, even without the reinstall.

The below sequence is executed as in the macros to see how many CPU's are available. But as we don't have getconf, RPM_BUILD_NCPUS is uninitialized. This leads to warnings and errors in the log. As we don't have getconf, I vote for initializing the value with 1

# Maximum number of CPU's to use when building, 0 for unlimited.
#%_smp_ncpus_max 0
%_smp_mflags %([ -z "$RPM_BUILD_NCPUS" ] \\\
	&& RPM_BUILD_NCPUS="`/usr/bin/getconf _NPROCESSORS_ONLN`"; \\\
        ncpus_max=%{?_smp_ncpus_max}; \\\
        if [ -n "$ncpus_max" ] && [ "$ncpus_max" -gt 0 ] && [ "$RPM_BUILD_NCPUS" -gt "$ncpus_max" ]; then RPM_BUILD_NCPUS="$ncpus_max"; fi; \\\
        if [ "$RPM_BUILD_NCPUS" -gt 1 ]; then echo "-j$RPM_BUILD_NCPUS"; fi)