As part of preparing to release rpm-5.1.2, I've pushed fixes for
the most serious known issues on to the rpm-5_1 (and rpm-5_0)
branches in cvs:
Log:
- jbj: disable loop unraveling error msgs for now. better needs
to be done.
- jbj: fix: rpm-python h['filenames'] needs tagName(0x54aafb71) to
return "Filenames" in order to find the filepathsTag extension.
- jbj: add a missing newline to a debug message.
- jbj: revert rpmtsOpenDB on --checksig path, rely on the lazy open
in rpmtsFindPubkey instead.
- jbj: fix: rpm -qp returns NOKEY because rpmdb is not yet open.
Do a lazy
open in rpmtsFindPubkey.
- jbj: python: fix: insure that ts.setProbFilter() return is
initialized.
- jbj: fix: use rpmlog instead of rpmError for messages.
I may push a few more changes from HEAD to the rpm-5_1 branch in the
next 2 days. Dunno yet.
(aside) Perhaps the prettiest "eye candy" patch is automated "make
check" rpm
coverage testing (the tests are still feeble) using LCOV/GCOV as seen
here:
http://wraptastic.org/pub/jbj/rpm-lcov/
What is still under development is a more rigorous test harness for rpm,
so maybe "Not yet" for rpm-5.1.2 is the wiser answer. We'll see ...
Are there any other issues or known problems that need to be
addressed in rpm-5.1.2?
73 de Jeff
Received on Sun May 18 19:28:14 2008