app-misc/beagle-0.2.14 uses a broken sed expression to disable debugging. This expression exists in prior ebuilds although I haven't verified its effectiveness. From a cursory inspection of the code and prior patches, I'd say partially effective in prior ebuilds, not at all in this one. Result is that beagle always logs with full debug info which can be very very extensive consuming huge amounts of disc space. Reproducible: Always Steps to Reproduce: Actual Results: Beagle debug log level is always enabled. Set log level to info throughout the application. Ideally using a patch which would actually alert if the code changed.
*** This bug has been marked as a duplicate of bug 158446 ***
bug #161666 is not exactly a dupe of bug #158446 bug #158446 describes an error in the helper that adds temp files My bug describes an issue with LogLevel that can result in massive ~/.beagle/Logs I really did check for existing bugs before filing mine I was moderately surprised there wasn't one already since I had diagnosed this to someone in #gentoo-desktop or #gentoo-help or somewhere a few weeks ago I'd say bug #158446 is probably an upstream bug Mine is definitely gentoo's fault Especially since upstream says that they won't customise logging, explicitly saying it is up to the distro to do that if they want to.
We can remove the sed expression now that beagle is more stable. We don't need the debug anymore. Thanks
*** Bug 162317 has been marked as a duplicate of this bug. ***
(In reply to comment #3) > We can remove the sed expression now that beagle is more stable. We don't need > the debug anymore. Well I guess you've misunderstood the bug here? People are complaining about their HD space being drained by beagle debug noise (also see Bug 158446) and you've now left debug enabled by default for anyone? *blink*
Aye. The default is to have debug. Without the sed, debug would be enabled and although according to the beagle folks they do truncate logs, they only do that on restart. I suppose the filled HDs is a testament to recent stability of beagle and mono, but all the same...
I don't think there was a misunderstanding. The broken sed expression was causing the explosion, but that is now removed. Am I right in saying that the problem goes away when you sync and re-merge 0.2.14?
(In reply to comment #7) > I don't think there was a misunderstanding. The broken sed expression was > causing the explosion, but that is now removed. Am I right in saying that the > problem goes away when you sync and re-merge 0.2.14? Humpf... No; that sed was broken, did nothing. Removing it did nothing. Debug is still enabled and noisy like hell, eating tons of disk space.
i added a patch to 0.2.15.1 bump used on suse rpm's that decreases the log. We can't do much about this since this is upstream problem. Thanks
