Terje Rosten wrote:
* seth vidal
|
| it might be useful to allow that field to look like:
|
| Dec 12 08:09:38 hostname yum(yum-cli): Updated: openssh-server.x86_64
| 4.3p2-14.fc6
| Dec 12 08:09:38 hostname yum(yumex): Updated: openssh-server.x86_64
| 4.3p2-14.fc6
| Dec 12 08:09:38 hostname yum(pirut): Updated: openssh-server.x86_64
| 4.3p2-14.fc6
| Dec 12 08:09:38 hostname yum(yum-updatesd): Updated:
| openssh-server.x86_64 4.3p2-14.fc6
|
| so you can distinguish how the update/install/etc was performed.
New patch with this fixed, tested with yum-cli, pirut and
yum-updatesd.
( However logging with yum-updatesd is not possible unless you use the
patch I posted some days ago:
https://lists.dulug.duke.edu/pipermail/yum-devel/2006-December/002955.html
See also:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=212507
Comment #41. )
yumex seems to do some funny thing with logging, Tim?
Yes, yumex do some funny stuff with logging, it don't use the
logginglevels.doLoggingSetup to setup logging, because it is using
a custom logging handler to print the logging output to a GTK TextView.
I will try to fix it so it is using the default yum logging setup and
just add another logging handler to handle the gtk.Textview output.
Tim
_______________________________________________
Yum-devel mailing list
[email protected]
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
