Re: more RHEL3 up2date failures

Tim Powers <[email protected]>
Newsgroups gmane.linux.redhat.taroon
Message-ID <[email protected]>
On Wed, 2003-09-10 at 14:20, Matt Domsch wrote:
> Different from what has been previously reported:
> 
> > Remove all of the packages listed in this mail:
> > http://www.redhat.com/archives/taroon-beta-list/2003-September/msg00148.html
> 
> Done, they're all removed.
> 
> # up2date -u -f
> (lots of stuff)
> kdenetwork-3.1.3-1.4.i386.r ########################## Done.
> kdenetwork-3.1.3-1.4.src.rp ########################## Done.
> kdenetwork-devel-3.1.3-1.4. ########################## Done.
> kdenetwork-3.1.3-1.4.src.rp ########################## Done.
> kernel-utils-2.4-8.37.i386. ########################## Done.
> kernel-utils-2.4-8.37.src.r ########################## Done.
> krb5-libs-1.2.7-18.i386.rpm ########################## Done.
> Traceback (most recent call last):
>   File "/usr/sbin/up2date", line 1150, in ?
>     sys.exit(main() or 0)
>   File "/usr/sbin/up2date", line 748, in main
>     fullUpdate, dryRun=options.dry_run))
>   File "/usr/sbin/up2date", line 1015, in batchRun
>     batch.run()
>   File "/usr/share/rhn/up2date_client/up2dateBatch.py", line 73, in run
>     self.__getPackages()
>   File "/usr/share/rhn/up2date_client/up2dateBatch.py", line 139, in __getPackages
>     up2date.getPackage(pkg, wrapperUtils.printPkg, wrapperUtils.printRetrieveHash)
>   File "/usr/share/rhn/up2date_client/up2date.py", line 327, in getPackage
>     progressCallback)
>   File "/usr/share/rhn/up2date_client/rpcServer.py", line 160, in doCall
>     pkgName = "%s-%s-%s.%s" % (pkg[0], pkg[1], pkg[2], pkg[4])
>   File "/usr/share/rhn/up2date_client/rhnChannel.py", line 50, in __getitem__
>     return self.dict[item]
> KeyError: 0

That's new. Please file a bug against up2date.

Tim


--
Taroon-beta-list mailing list
[email protected]
http://www.redhat.com/mailman/listinfo/taroon-beta-list
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.