https://bugzilla.novell.com/show_bug.cgi?id=297321#c6
Thomas Fehr changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |INVALID
--- Comment #6 from Thomas Fehr 2007-08-29 03:09:09 MST ---
All yast2 related bugs without y2log files are resolved as invalid.
This does not mean the bug is not there bug that it is in a state where
one cannot currently work on it.
As soon as you attach y2log file you should of course reopen the bug.
Some more explanations:
The bug report is against 10.3. My tests did not reproduce the problem on
10.3, this is not really surprising since I added code to 10.3 that should
prevent these cases. Of course this also does not prove that you do not have a
special case that currently is not handled correctly even in 10.3.
Therefore I need a test and y2log files for 10.3.
Reproducing it on SLES10 is of course not a problem, but unless SLES product
management sets this on the list of problems that need to get fixed for SLES10
SP2 this will not get fixed in SLES10 code base anyway.
IMHO it is not really a critical problem, simply changing the proposal for such
a case should not be too hard.
Development stage of 10.3 progressed too far to fix such problems (if the
problem
is still present in 10.3 at all) and SLES10 SP2 is far away, so there is no
need to hurry to reproduce this.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.