Lukas Ocilka napsal(a):
Stefan Schubert wrote:
Ladislav Slezak schrieb:
If you are removing a log message consider using the debug level (level 0) if the message might be useful in some situation later. It's usually easy to ask the reporter to enable debug and reproduce the problem again if you need more information for debugging.
Do you really think that a beta tester will be able/willing to reproduce an update error again if he has finished an update ?
Just a thought.....
I also always thought that those <0> debug logs from zypp were intentional there :) We have had them in the YaST log since the zypp was born, don't we?
Yes, because nobody has complained of this behavior. So the question is how should we proceed? There are three possibilities: 1) I can revert the change in pkg-bindings, some unnecessary log messages from libzypp should be removed. 2) Leave the change in pkg-bindings and increase log level of really needed debug messages in libzypp. 3) Revert pkg-bindings back and leave libzypp as is (i.e. revert to the previous state) and solve it after 10.3. In the log run we should use 2), libzypp logging should be compatible with yast logging. But we are close to the release, which solution should we choose for 10.3? What do you think? Ladislav -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org