experiences with 20021018 snapshot

I've given the snapshot a bit of a beating now. :)

A Red Hat 6.2 test client worked fine, as are production 7.1/7.3
clients.

Are you (the Current developers) interested in hearing about my
experiences with a Red Hat 6.1/up2date 2.8 client? It mostly worked, but
I got two tracebacks. (I'll send you the text of one or the other, or
both, if you're interested. If you're interested enough and if you can't
reproduce these, I can give you more details, or SSH access to a box of
mine again.)

One was caused by having Red Hat 6.1's raidtools package in the channel.
Once I removed that package, the traceback went away. (This was when I
had both the original 6.1 packages and the 6.1 errata in a channel.)

The other traceback, as far as I could tell, happened when the delete
code tried to delete Red Hat 6.1's sgml-tools-1.0.9-2 package to replace
it with the 6.2 errata's sgml-tools-1.0.9-6.2 package. (This was when I
added the 6.2 errata to the previous channel.) I worked around this by
placing the 6.2 errata earlier than the 6.1 original or errata packages
in the rpm_dirs list in current.conf.

BTW, for anyone else who wants to attempt this, here's a sequence of
packages to install from the 6.2 errata to get up2date 2.8 going on a
Red Hat 6.1 install:
popt, db3, rpm (preferably all on the same rpm command line; also, add
 rpm-build etc. if you have those installed but leave rpm-python for
 later)
[it would be a good idea to run "rpm --rebuilddb" at this point]
openssl
python* (all the packages with names beginning with "python")
rpm-python
rhn_register
gnupg
up2date

I think I'm very close to getting up2date 2.8 working on Red Hat 6.0;
I'll send an e-mail to the list about that later.

-Barry K. Nathan <[email protected]>