https://bugzilla.redhat.com/show_bug.cgi?id=1178532
John Dennis 2015-01-04 10:54:39 EST
There are many places in the python install code which look like this:
print >> sys.stdout, msg,
Unfortunately these messages only go to the console and are not also included in the log file. If something goes wrong in the installation and you're trying to read the log file to trace what occurred the absence of these messages is a problem. It's as if only half the information is in the log file. A lot of the time the log file only contains a stacktrace from the failed operation but very little contextual information on what preceded the operation, you have to go back the terminal session and try to correlate the different output streams.
Fields changed
milestone: => 1.0 m1 owner: simo => npmccallum status: new => assigned
milestone: 1.0 m1 => 1.0 m2
milestone: 1.0 m2 => 1.0 m3 patch_available: => 0
owner: npmccallum =>
status: assigned => new
milestone: 1.0 m3 => 1.0
milestone: 1.0 m4 => 1.0
design_link: => owner: => rcritten status: new => accepted
patch_available: 0 => 1
https://fedorapeople.org/cgit/rcritten/public_git/ipsilon.git/.git/commit/?h=logger&id=41ea3772220b37690c7fae6a79f1b13efc7a4f8b
master: aa5dc3b
resolution: => fixed status: accepted => closed
rhbz: => 0
Metadata Update from @nkinder: - Issue assigned to rcritten - Issue set to the milestone: 1.0
Login to comment on this ticket.