https://bugzilla.novell.com/show_bug.cgi?id=263698 alpha096@tpg.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|alpha096@tpg.com.au | ------- Comment #3 from alpha096@tpg.com.au 2007-04-12 15:04 MST ------- RPM database rebuilt successful - no error or nil response after re-built command executed. RPM printer file installed without any online access attempted. Online-update performed due updates available with no issue.
From memory - an online update corrupted. IF you require YAST log files please advise.
Do we close as fixed or do we act now to offset potential corruption of the RPM database by implementing a RPM rebuild under the following options? I understand that the RPM package manager install with Yast is very complex code, however would you consider more code in response to install with Yast failure due corrupted RPM database can you offer the user the ability to rebuild on screen option window. Alternatively is it worth adding to the end of the install script a mandatory RPM rebuild as part of the process. Another possible option may be to add RPM rebuild as a cron job. Periodically force an RPM re-build as part of an online update. If we close as fixed due manual user intervention do we miss the ability to offset potential issues especially as the RPM database grows in size dramatically, is frequently accessed by online updates, both of which will become an issue as time and development proceed. Potential negative is how do we handle a RPM file that will not re-build and cause data loss if indices's are lost in re-build. Over to your for further action or close fixed Cheers ....Scott -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.