deb-o-matic

Logging doesnt work correctly

Bug #250633 reported by David Futcher
2
Affects Status Importance Assigned to Milestone
deb-o-matic
Fix Released
Low
Luca Falavigna
deb-o-matic 0.6 "bobbo"

Bug Description

Using Debians build of 0.5 (etch) logging doesnt seem to work. The logs generated by --pkgname-logfile dont seem to work, or at least arent placed in an easily visible directory (ie, I couldnt find them).

It would be better to build the logfile path manually and place the log in $INCOMING/$DISTRO/result/$PACKAGE/$PACKAGE.log

Attached is a patch to make this work (tested working on my etch box)

Revision history for this message
David Futcher (bobbo) wrote :
Revision history for this message
David Futcher (bobbo) wrote :

Woops, I must have been blind: It does place a lot in incoming/distro/result/package but it has the filename .build which doesnt make it stand out as a log. Not really a bug but the patch above would stop it being an annoyance.

Revision history for this message
Luca Falavigna (dktrkranz) wrote :

--pkgname-logfile produces a .build logfile actually.
As you reported, it is not easily predictable what that .build file is, switching to .log or .buildlog would be more intuitive.

Changed in debomatic:
importance: Undecided → Low
status: New → Triaged
Luca Falavigna (dktrkranz)
Changed in debomatic:
assignee: nobody → dktrkranz
milestone: none → 0.6
Revision history for this message
Luca Falavigna (dktrkranz) wrote :

r109

Changed in debomatic:
status: Triaged → Fix Committed
Revision history for this message
Luca Falavigna (dktrkranz) wrote :

Version 0.6 released.

Changed in debomatic:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.