This is pretty much ready to go in now, it's split out a bit so
here's the summary:

[PATCH 1/9] Add skip broken packages to history transaction.

 This is the one posted a few weeks ago.

[PATCH 2/9] Add three views to make look at history by hand easier

 Add some VIEWs, they aren't used by the code but are very helpful
when humans are debugging the .sqlite by hand ... and they take up
almost no space.

[PATCH 3/9] Add rpmdb problems, and cmdline to the history DBv2 update

 These are two new additions/tables:

1. We save the command line, this is the exact same thing as
yumdb.command_line. This might be helpful in debugging, but is
probably more useful as a "wtf did this happen" to the tired
sysadmin :) ... saying that we don't get args. here.

2. We save all current rpmdb problems. The big problem here is that
if you do something funky and have problems, as soon as you do a
single history transaction the warning is gone and it's not easy
to see it again. So we save it, and everyone can easily find it
again.

[PATCH 4/9] Save rpmdb problems, and cmdline, into yum history

 This is just saving the data for PATCH 3.

[PATCH 5/9] Output cmdline and rpmdb problems in history info

 This is outputting the data, in yum history info, for PATCH 3.

[PATCH 6/9] Move obsoleted.obsoleter check into the correct problem loop

 Stupid bug fix that I found while testing :o

[PATCH 7/9] Mark pre-exsting rpmdb problems in history list, with 'P'.

 This is outputting the data, in yum history list, for PATCH 3.
 Uses the 'P' flag, for Problem ... maybe '!' would be better?

[PATCH 8/9] Fix sorting of historic rpmdb problems

 Stupid cleanup.

[PATCH 9/9] Save, and then Highlight, the "main" package which has a problem

 Save which package is the "main" package, in a problem and highlight that
line.
_______________________________________________
Yum-devel mailing list
Yum-devel@lists.baseurl.org
http://lists.baseurl.org/mailman/listinfo/yum-devel

Reply via email to