On Fri, 2011-07-29 at 12:57 -0400, Matthew Miller wrote:
> Where does the update from rpm _itself_ go? That's just spit out to
> stdout/stderr by the rpm library, right?
There are a few things we "get" from rpm:
r1. Call back data.
r2. scriptlet errors (goes to a file that yum can then read).
On Fri, Jul 29, 2011 at 12:21:38PM -0400, James Antill wrote:
> > This is used to generate a helpful subject line and (perhaps more
> > importantly) to generate meaningful log messages.
> > This all actually works very well, but makes me wince. Is there a better way
> > in these modern times?
> Th
On Fri, 2011-07-29 at 10:16 -0400, Matthew Miller wrote:
> In bulinux-autoupdate, which is approaching a decade in age, we check for
> errors and warnings from yum update transactions by saving standard error
> and standard output to files. And then, if there is output on stderr,
> awesomely, we do
In bulinux-autoupdate, which is approaching a decade in age, we check for
errors and warnings from yum update transactions by saving standard error
and standard output to files. And then, if there is output on stderr,
awesomely, we do stuff like `egrep -iq '(error|not signed)'` to decide
whether it
