Bug 61024

Summary: up2date fails to run
Product: [Retired] Red Hat Linux Reporter: Tim Wunder <wundertp>
Component: up2dateAssignee: Adrian Likins <alikins>
Status: CLOSED CURRENTRELEASE QA Contact: Jay Turner <jturner>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: gafton, mihai.ibanescu, srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-05-09 13:51:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tim Wunder 2002-03-12 13:06:25 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9+)
Gecko/20020308

Description of problem:
Executing 'up2date' exits with this error:

Traceback (innermost last):
File "/usr/sbin/up2date", line 12, in ?
import xmlrpclib
File "/usr/lib/python1.5/sire-packages/xmlrpclib.py", line 28, in ?
import urllib, xmllib
File "/usr/lib/python1.5/urllib.py", line 25, in ?
import socket
ImportError: symbol __sysconf, version GLIBC_2.2 not defined in file libc.so.6
with link time reference

libc.so.6 is a symlink to libc-2.1.92.so
I have python-xmlrpc-1.5.1-7.x.3 installed


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. run ep2date
2.
3.
	

Additional info:

Comment 1 Adrian Likins 2002-05-08 21:08:30 UTC
You will need to update to the latest glibc by hand.

Comment 2 Tim Wunder 2002-05-09 13:51:19 UTC
OK. Some quick questions, though:

When updating glibc from RPM, is it a good idea to force the update with 'rpm -Uvh --force'?

Then again, would I be better served by updating to  RedHat 7.3, and starting from a more current code base?

If so, is it feasible to update 7.0 to 7.3, or would a reinstall be recommended?

Comment 3 Adrian Likins 2002-08-09 03:10:33 UTC
No need to use "--force" to upgrade glibc (I would stronly recomended
against useing it with rpm....)