yum check-update performance slow

Mike McIntyre <[email protected]>
Newsgroups gmane.linux.rpm.yum
Message-ID <OF488EA7F1.69200210-ON85257617.0069F0C9-85257617.006C7E01@ca.ibm.com>
Used the yum-metadata-parser-1.1.0.tar.gz and modified 
yum-metadata-parser.spec for python_sitelib_platform location. rpmbuild 
--bb yum-metadata-parser.spec successfully produced a 
yum-metadata-parser-1.1.0-1.s390x.rpm file. Also was able to rpmbuild 
pygpgme-0.1-8.s390x.rpm, python-iniparse-0.2.4-3.5.s390x.rpm files and 
install these prequisites.

rpm -e yum-2.4.2-13.4 and rpm -i yum-3.2.23-0.noarch.rpm 
yum-metadata-parser-1.1.0-1.s390x.rpm successfull.  yum check-update 
failed with message "No module named yum".  Found 
http://www.linux-archive.org/fedora-development/315317-upgrade-f11-now-yum-python-module-missing.html 
with command export PYTHONPATH=/usr/lib/python2.4/site-packages that 
resolved this problem.

yum check-update fails with:
(process:10777): GLib-CRITICAL **: g_timer_stop: assertion `timer != NULL' 
failed
(process:10777): GLib-CRITICAL **: g_timer_destroy: assertion `timer != 
NULL' failed
Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in ?
    yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/yummain.py", line 309, in user_main
    errcode = main(args)
  File "/usr/share/yum-cli/yummain.py", line 178, in main
    result, resultmsgs = base.doCommands()
  File "/usr/share/yum-cli/cli.py", line 348, in doCommands
    self._getTs(needTsRemove)
  File "/usr/lib/python2.4/site-packages/yum/depsolve.py", line 101, in 
_getTs
    self._getTsInfo(remove_only)
  File "/usr/lib/python2.4/site-packages/yum/depsolve.py", line 112, in 
_getTsInfo
    pkgSack = self.pkgSack
  File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 646, in 
<lambda>
    pkgSack = property(fget=lambda self: self._getSacks(),
  File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 488, in 
_getSacks
    self.repos.populateSack(which=repos)
  File "/usr/lib/python2.4/site-packages/yum/repos.py", line 260, in 
populateSack
    sack.populate(repo, mdtype, callback, cacheonly)
  File "/usr/lib/python2.4/site-packages/yum/yumRepo.py", line 184, in 
populate
    dobj = repo_cache_function(xml, csum)
  File "/usr/local/lib64/python2.4/site-packages/sqlitecachec.py", line 
40, in getPrimary
    self.repoid))
TypeError: Can not create index on requires table: near "NOT": syntax 
error

Found https://lists.dulug.duke.edu/pipermail/yum/2008-January/010452.html 
and tried yum clean metadata and then rm -rf /var/cache/yum.  Same error 
above again.
Noticed 
http://wiki.contribs.org/Updating_to_SME_7.2#GLib-CRITICAL_.2A.2A:_file_gtimer.c:_line_106_.28g_timer_stop.29
GLib-CRITICAL **: file gtimer.c: line 106 (g_timer_stop)
This error indicates that you have installed yum packages that require 
later versions of sqlite and python-sqlite than you have installed on your 
system.

rpm levels are sqlite-3.2.8-15.2, python-sqlite-1.1.6-17.4, 
python-2.4.2-18.13.  Did not see newer Novell levels of these rpms to 
install for SLES 10 SP1 s390x.

Did a rpmbuild and install for yum-3.2.22-0, yum-3.2.0-1, yum-3.1.0-1, 
yum-3.0.1-1.  yum check-update fails with same error above.

>From prereq checking all the yum-3.2.23-0, yum-3.2.22-0, yum-3.2.0-1, 
yum-3.1.0-1, yum-3.0.1-1 rpms successfully installed. 

Seth:
Should the yum-spec file be updated to specify the higher rpm prereq 
levels for yum-3.2.23-0?  Can you tell me the prereq levels of rpms for 
sqlite, python-sqlite, other rpms that are needed to avoid above error? Do 
I have to wait to install SLES 11 zlinux s390x to use the newer yum levels 
like yum-3.2.23-0?

Regards,....Mike McIntyre
Distributed System Management
Infrastructure Services | Server Support Team
Securities Industry Services | Financial Services Sector
IBM Global Technology Services, Canada

_______________________________________________
Yum mailing list
[email protected]
http://lists.baseurl.org/mailman/listinfo/yum
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.