Feature changed by: Jiri Srain
Feature #100386, revision 31
Title: Support a verbose logging mode in yast
openSUSE-10.2: Rejected by Andreas Jaeger
reject date: 2006-09-30 20:43:33
reject reason: for 10.3.
Priority
Requester: Desirable
Projectmanager: Desirable
openSUSE-10.3: Rejected by Stanislav Visnovsky
reject date: 2007-08-01 10:24:26
reject reason: Postponing, needs more research.
Priority
Requester: Important
Projectmanager: Important
openSUSE-11.0: Rejected by Federico Lucifredi
reject date: 2008-06-28 19:27:16
reject reason: fixing my typo. Mandatories in the past don't work
(yet).
Priority
Requester: Important
Projectmanager: Important
- openSUSE-11.1: Candidate
+ openSUSE-11.1: Done
Priority
Requester: Important
Projectmanager: Important
SL-10.0: Rejected by Andreas Jaeger
reject date: 2005-12-02 14:56:13
reject reason: not done.
Priority
Requester: Desirable
- SLES-11: Candidate
+ SLES-11: Done
Priority
Requester: Important
Projectmanager: Important
Requested by: Andreas Jaeger
Partner organization: openSUSE.org
Description:
Create a verbose logging mode in yast, where any action yast performs
is logged. Any file yast touches should be logged (to
/var/log/YaST2/y2log AND clean up the structure of that log file, to
make it easier to read and interpret) and all changes on the systems
configuration. The goal is to make it really transparent what yast
does.
Documentation Impact:
Admin guide needs to contain information about the new log file.
Please add it to the Log file section in the troubleshooting chapter
Discussion:
#1: Edith Parzefall (2006-09-28 17:17:54)
Can't be done for 10.2. Back to TPMs.
#2: Edith Parzefall (2007-07-31 16:17:45)
Sorry, couldn't be done for 10.3. We need a concept for this. Even
within the team different developers have different needs. Improving
the logging to give all developers the best possible debugging
information will be difficult, but it's definitely something we should
attempt in the near future.
#3: Stanislav Visnovsky (2007-11-08 10:48:48)
Can we get some traction here finally?
#4: Stanislav Visnovsky (2007-11-28 10:16:38)
Reopening, the YaST transparency is often cited as a problem for
users.
#6: Federico Lucifredi (2008-06-28 17:13:54)
I think this has enough user benefit and is trivial enough, we should
just get it done.
#7: Federico Lucifredi (2008-06-28 19:28:04)
PM-Priority for product openSUSE-11.0 downgraded from mandatory to :
oops. Too many widgets for my tired brain.
#8: Stanislav Visnovsky (2008-07-01 16:49:08)
(reply to #7)
This cannot be done completely - this is non-trivial amount of work. I
suggest to start this though, having the YaST infrastructure in place
ASAP. Federico, please, downgrade the priority.
#9: Federico Lucifredi (2008-07-02 14:01:05)
PM-Priority for product SLES-11 downgraded from mandatory to important:
too much work for a one-off apparently.
#10: Federico Lucifredi (2008-07-02 14:01:27)
PM-Priority for product openSUSE-11.1 downgraded from mandatory to
important:
too much work for a one-shot.
#12: Stanislav Visnovsky (2008-09-10 11:03:50)
I've added y2useritem and y2usernote builtins into yast2-core. This
might be helpful for this feature.
--
openSUSE Feature:
https://features.opensuse.org/?rm=feature_show&id=100386
