[Bug 1244513] rpm rebuild --what to do to recover from database crash

bugzilla at redhat.com bugzilla at redhat.com
Mon Sep 28 13:40:24 UTC 2015


https://bugzilla.redhat.com/show_bug.cgi?id=1244513

Leslie Satenstein <lsatenstein at yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
         Resolution|---                         |UPSTREAM
              Flags|needinfo?(lsatenstein at yahoo |
                   |.com)                       |
        Last Closed|                            |2015-09-28 09:40:24



--- Comment #7 from Leslie Satenstein <lsatenstein at yahoo.com> ---
I wish to close this bug.

The interesting thing about winning software and technical systems, is that
good systems always have a « code » followed with an accompanying brief error
message For example:

dnfnnnnA  run dnf rebuild rpm --rebuilddb followed by  rpmdb_verify Packages  

If the support person needed more information, he could then look up dnfnnnnA
via the man pages or other guide. If the end-user was Romanian or other for
which there is  no translated version, the code would be most useful for
individuals (support) to understand the why and what to do. This code idea
helps  technical support, as the user could quote the « code »


So, as a suggestion  Letters I,A,W,E       
dnfnnnnnI follows with an informative message  with Retcode 0
dnfnnnnnA follows with the requirements for User action Retcode 0 if action
taken, otherwise exit with retcode 4

dnfnnnnnW is a warning message, which may be ignored or reviewed for further
action. Retcode 4

dnfnnnnnE The system experienced an error with "blah blah blah" Corrective
action required. Retcode 16 

As Linux is growing in number of platforms and number of systems (docker) etc.
Linux needs some structure for error messages.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.


More information about the docs-qa mailing list