Custom Query (344 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (31 - 33 of 344)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Ticket Resolution Summary Owner Reporter
#198 fixed Cannot run yum when logged onto non-writable volume or volume not supporting long filenames Silvan Scherrer Lewis Rosenthal
Description

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?

#12 invalid ClamAV install Incomplete? Yuri Dario David McKenna
Description

I tried to install ClamAV using yum: YUM INSTALL CLAMAV. Three files were downloaded:

clamav-0.96.4-2.oc00.i386.rpm clamav-data-0.96.4-2.oc00.i386.rpm clamav-lib-0.96.4-2.oc00.i386.rpm

and then extracted to various folders. No objects were created so it is hard to see how to use it. There is no clamd.exe to be found anywhere.

A quick look at http://rpm.netlabs.org/release/00/i386/i386/ shows there are other ClamAV files than the three above - aren't they supposed to be downloaded and installed also?

It seems the install of ClamAV is not completed using YUM...

#11 fixed Consider adding SET PYTHONPATH to CONFIG.SYS Yuri Dario David McKenna
Description

The 'Next Steps' instructions recommends removing the bootstrap programs after installing YUM (presumably to recover disc space). However, after doing that, trying to run YUM from the command line fails because SET PYTHONPATH is not added to CONFIG.SYS by the installer.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Note: See TracQuery for help on using queries.