bug #1065588 is still open. It deals with the installation of
NTFS packages if an NTFS file system is found on the system. Even
though the file system is not mounted YaST wants to install the
NTFS tools. Some users do not like that behaviour.
The idea already mentioned in the bug is to make the used
features as reported by libstorage-ng more relaxed: When a file
system is present but not mounted the corresponding used feature
will not be set. So YaST will not propose to install the tools.
I think this has one disadvantage: When making a new installation
the NTFS tools will not be installed (since AFAIR YaST does not
create entries in fstab for those anymore). Anyway, now users or
desktop environments cannot mount NTFS. That looks like a
regression to me.
So my proposal is to have a used_features() function in
libstorage-ng that takes an argument, say REQUIRED and
SUGGESTED. During installation YaST would install the SUGGESTED
tools. In the running system it would only install the REQUIRED
Does that look fine?
This has one additional consequence: The user could use YaST to
just create an XFS. In that case the XFS tools are not required
in the final system - but surely they are required to create the
XFS. So the actiongraph will also have a used_features() function
and YaST must install the corresponding tools.
Arvin Schnell, <aschnell(a)suse.com>
Senior Software Engineer, Research & Development
SUSE Software Solutions Germany GmbH
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
As you may know, we introduced automatic profile validation in AutoYaST for
SLE 15 SP3 and Tumbleweed. When the profile is not correct, AutoYaST complains
at the beginning of the autoinstallation. So, as expected, we are getting
regular bug reports from openQA.
In some cases, the profile is just wrong. However, we have detected several
problems in yast2-schema.
Although you can disable this feature at boot time (setting
YAST_SKIP_XML_VALIDATION to 1), I fear that we are going to get a ton of
errors from our users and customers.
So I was considering whether we should disable this feature by default,
although in that case I would ask openQA to enable it so we can improve yast2-
What is your point of view?
Imobach González Sosa
YaST Team at SUSE LLC