I'm implementing some new AutoYaST feature and I found out that it's not easy
to test the AutoYaST functionality.
1. Even for testing a trivial scenario you have to write your own XML file.
If you do not have much experience with AutoYaST you have to read the
documentation, search the internet, etc... Cloning your current system helps
a bit but usually the cloned profile contains too many options so you still need
to polish it a bit...
2. When you have your profile ready you have to host it at some HTTP/FTP/NFS/...
server so AutoYaST can use it for installation. I usually run simple
"ruby -run -ehttpd" command to have a web server quickly, but that's quite
tricky for people not familiar with Ruby.
My idea is to have some repository with example XML profiles which would be
publicly available and ready for instant use. We already have some XML files in the
autoyast-profiles-test Git repository but writing something like
on boot command line is a real pain. We could use some URL shortening service
but I do not like that much. Shortened URLs do not look nice and it's not
obvious where they point to (security). I'd like to have some nice URLs...
So my proposal is to use the GitHub pages for building an AutoYaST profile
repository. Then you could use
for testing a minimal SLES/Leap profile.
Actually these URLs already work! :-) You can give it a try. Most likely you will
need additional "netsetup=dhcp" boot option for configuring network.
The profiles would be well described (what they do) and well commented (so the users
can easily adapt them to their needs).
The profiles could be automatically validated (via Travis) and it would be nice
to use them also in openQA tests to be sure they really work.
We could also link this repository from the official SUSE documentation.
The proof of concept is available at https://autoyast.github.io, please check it.
It is still just a concept for getting early feedback, there is a lot of work to do.
See the README file in https://github.com/autoyast/autoyast.github.io
What do you think about it?
SUSE LINUX, s.r.o.
18600 Praha 8
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
after quite long playing with achieving layout I decide to write down what I found.
To get nice box centered at middle of screen, but content in box left aligned use
It start with feature to adapt theme and our designed team found some strange alignment that they want to change in dialog layout.
So I start with trivial idea to have something like `Center(VBox(Left(*content)))` This sadly does not work as it in
the end create box over whole place and everything is ugly on left side. which looks strange ( see screenshots in ).
So next attempt with a bit of help is MarginBox. It looks fine and is shrinkable, so even on very small screen in ncurses
looks fine, but in qt it is hard to pick good sizes as with different resolutions it is never on center for all resolutions.
So good to make some spacing, but not to align box.
The proper solution is to use that stretches around that create spacing around box that is proportional and content in Box
then can left alignment with proper position.
Pro tip: If you do not want center but e.g. in one third, it is possible to use Weight to stretch. See documentation at 
There are many ways to teak the installer and people keep asking for more.
We are discussing use cases and ways to improve things on github:
If you have suggestions or more use cases or just want to stay in touch,
feel free to join the discussion.
2020 is coming to an end. Let's celebrate that with the last development
report of the year from the YaST Team, which includes:
- Several additions to AutoYaST
- Better management of required packages
- Usability improvements in the registration process
- Drop of the SysVinit support
- Translation infrastructure for the wicked Cockpit module
Check the whole report at:
Ancor González Sosa
YaST Team at SUSE Linux GmbH
as I play nowadays a lot with layout of one of installation dialog I need to effectively test it. For runtime you can always use just resize of window and see various results. For installation it is a bit different as installation runs fullscreen. I use for testing virt-manager and runs VM on our server. So for various resolution you can use F3 on grub screen after boot to play with different resolutions ( just pick "Installer size" and not others like me ). For testing ncurses you can enable there text mode and if minimal console needs to be tested then combination of Text Mode and Text Console Size No KMS do the trick for me.
HuHa tip: you can use same approach as for runtime testing, just use ssh installation either with X forwarding or without and resize your ssh window.
with the release of package yast2 version 4.3.46 YaST will not support
So we have removed the SCR agent ".etc.inittab" .
Please check your code if you are still using this agent.