Recently, since update to FC4, we have received update announcements for Fedora 4. However, when running Up2Date, we receive the response that the system is up to date. Checking the Up2Date log reveals processing errors shown below.
Has anyone experienced similar Up2Date processing errors as below? If so, what is the corrective action>
[Mon Jun 27 07:47:45 2005] up2date File "/usr/sbin/up2date", line 1265, in ?
sys.exit(main() or 0)
File "/usr/sbin/up2date", line 891, in main
gui.main()
File "/usr/share/rhn/up2date_client/gui.py", line 2158, in main
gtk.mainloop()
File "/usr/src/build/535819-i386/install/usr/lib/python2.4/site-packages/gtk-2.0/gtk/__init__.py", line 70, in __call__
File "/usr/share/rhn/up2date_client/gui.py", line 1311, in onChannelsPageNext
self.pList.run()
File "/usr/share/rhn/up2date_client/packageList.py", line 132, in run
progressCallback = self.progressCallback )
File "/usr/share/rhn/up2date_client/rhnPackageInfo.py", line 420, in obsoletesList
progressCallback = progressCallback )
File "/usr/share/rhn/up2date_client/rpcServer.py", line 316, in doCall
ret = apply(method, args, kwargs)
File "/usr/share/rhn/up2date_client/repoDirector.py", line 28, in getObsoletes
return self.handlers[channel['type']].getObsoletes(channel, msgCallback, progressCallback)
File "/usr/share/rhn/up2date_client/rpmSource.py", line 252, in getObsoletes
msgCallback, progressCallback)
File "/usr/share/rhn/up2date_client/repoBackends/repomdRepo.py", line 173, in getObsoletes
self.initRepo()
File "/usr/share/rhn/up2date_client/repoBackends/repomdRepo.py", line 123, in initRepo
log.trace_me()
File "/usr/share/rhn/up2date_client/up2dateLog.py", line 35, in trace_me
x = traceback.extract_stack()
[Mon Jun 27 07:47:45 2005] up2date File "/usr/sbin/up2date", line 1265, in ?
sys.exit(main() or 0)
File "/usr/sbin/up2date", line 891, in main
gui.main()
File "/usr/share/rhn/up2date_client/gui.py", line 2158, in main
gtk.mainloop()
File "/usr/src/build/535819-i386/install/usr/lib/python2.4/site-packages/gtk-2.0/gtk/__init__.py", line 70, in __call__
File "/usr/share/rhn/up2date_client/gui.py", line 1311, in onChannelsPageNext
self.pList.run()
File "/usr/share/rhn/up2date_client/packageList.py", line 132, in run
progressCallback = self.progressCallback )
File "/usr/share/rhn/up2date_client/rhnPackageInfo.py", line 420, in obsoletesList
progressCallback = progressCallback )
File "/usr/share/rhn/up2date_client/rpcServer.py", line 316, in doCall
ret = apply(method, args, kwargs)
File "/usr/share/rhn/up2date_client/repoDirector.py", line 28, in getObsoletes
return self.handlers[channel['type']].getObsoletes(channel, msgCallback, progressCallback)
File "/usr/share/rhn/up2date_client/rpmSource.py", line 252, in getObsoletes
msgCallback, progressCallback)
File "/usr/share/rhn/up2date_client/repoBackends/repomdRepo.py", line 173, in getObsoletes
self.initRepo()
File "/usr/share/rhn/up2date_client/repoBackends/repomdRepo.py", line 123, in initRepo
log.trace_me()
File "/usr/share/rhn/up2date_client/up2dateLog.py", line 35, in trace_me
x = traceback.extract_stack()
Ron Eckhardt Information Technology Services
Information Exchange Associates, LLC 1507 Holly Lane Junction City, KS 66441-3397 Phone: 785-375-4261 www.infoexchg.com <http://www.infoexchg.com/>rone@xxxxxxxxxxxxx
All I know about up2date is that it has never notified me when updates are available. I've had to start my own package manager (smart), refresh all channels, and then hit the update switch. Everything works.
I suppose that while I don't get notices when updates are available, others get notices when updates are not yet available--probably not promulgated to the mirrors. I've never seen up2date in such sorry shape as this.
For the record, I tried to use the "repomd" channel that tells up2date to consult the relevant file(s) in /etc/yum.repos.d/. That's a very good idea /if/ someone can make it work.
Temlakos
