* Michael Andres <ma@suse.de> [Jul 31. 2008 18:17]:
On Thu, Jul 31, Klaus Kaempf wrote:
Well, I believe you can. After the 'rpm -e', zypper (resp. libzypp) will not that the rpm database is not in sync with @system.solv and log the differences.
But whatever we do, it's guessing unless rpm itself provides a reliable history. In that case any commit could simply grep the last entry, and later check if something happened thereafter.
What if zypp dies or is aborted by user, in or after commit, before re-rebuilding the @system.solv.
The changes are already logged in the history, but not reflected by the solv file. We would re-log them as foreign.
The log could get 'start' and 'end' markers for each libzypp transaction, then 'zypp crashing' should be detectable. Otoh, I haven't seen zypp crashing for a very long time ;-) Klaus -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org