Bug 1393058 - lorax logging should give package version and releases
Summary: lorax logging should give package version and releases
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lorax
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Brian Lane
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-08 18:36 UTC by Dennis Gilmore
Modified: 2017-02-09 20:24 UTC (History)
2 users (show)

Fixed In Version: lorax-25.18-1.fc25
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-09 20:24:26 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Dennis Gilmore 2016-11-08 18:36:52 UTC 
Description of problem:
digging into rawhide compose failures is difficult when something goes wrong in lorax. take https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20161108.n.0/logs/x86_64/buildinstall-Cloud.x86_64.log we have no idea from the logs the version of the software installed. to try and start to work out what changed causing things to go wrong.
Comment 1 Fedora Update System 2017-02-06 18:50:19 UTC 
lorax-25.18-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-4b7056b1a2
Comment 2 Fedora Update System 2017-02-07 02:50:17 UTC 
lorax-25.18-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-4b7056b1a2
Comment 3 Fedora Update System 2017-02-09 20:24:26 UTC 
lorax-25.18-1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.