--- Comment #32 from Thomas Fehr <fehr(a)suse.com> 2013-06-24 03:56:16 UTC ---
The problem occurs during second stage of yast2 installation.
So releasing an update would only help if the user installs
the updates together with original medium in initial install.
This can of course be done, e.g. by adding
as add-on product.
But I doubt many autoyast setups use such a setup, mostly they
will install from original medium and simply do a online update
afterward. For such a scenario, releasing an update for autoyast
would not help since autoyast package from original medium is
used and the bug is already triggered in YaST2 second stage of
autoyast install. Therefore I would assume that after releasing an
online update there would be more confusion under which install
scenarios the new autoyast would be in place already during
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.