January 2021 - YaST Development - openSUSE Mailing Lists

[yast-devel] Overcommit - automatic checks via Git hooks
by Ladislav Slezak 21 Dec '22

21 Dec '22

Hi, I found a quite interesting tool called Overcommit [1]. It provides an easy way for setting up Git commit hooks and provides some basic checking plugins. The nice feature of the Git commit hooks is that you can run some checks automatically and early in the development. For example with the commit hooks you can run Rubocop check automatically whenever a commit is created. And if the check fails the commit is not created. I can see "make Rubocop happy" commits quite often (happens to me as well), with Overcommit you can easily avoid that. I have tried several Overcommit checks: - Rubocop - runs Rubocop at "commit" - Rspec - runs the tests before "push" - Branch blacklist - can forbid direct commits to configured branches, e.g. "master" (forces using pull requests, avoids commits to master my mistake) - Commit message spellcheck - warns when there is a possible typo Check my blog post [2] for the details, esp. watch the recorded screencast where I wanted to show some mistakes which it can catch. The tool looks promising, I'll try using it for some time. If you want to try it as well check the blog post for the installation steps. Enjoy! [1] https://github.com/brigade/overcommit [2] http://blog.ladslezak.cz/2016/06/06/overcommit/ -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak(a)suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 3

[yast-devel] YaST Tips&Tricks
by Ladislav Slezak 25 Jan '22

25 Jan '22

Hi all, some time ago we discussed where and how we should share "Tips&Tricks" for YaST users and developers. IIRC there was no clear conclusion so I decided to start a wiki [1] to collect all our tricks we know or use. For now it's just a place for dumping your ideas, links, short howtos, etc... When we collect enough data we can probably split it to several categories or move it somewhere else. We just need the data first. I have added there some my tricks from my personal "knowledgebase" file. If you have better tricks or find something wrong simply change it, it's a wiki ;-) Ladislav [1] https://github.com/yast/yast.github.io/wiki/YaST-Tips-and-Tricks -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 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

2 1

[yast-devel] Innovation time: A repository with AutoYaST XML profiles (PoC )
by Ladislav Slezak 03 May '21

03 May '21

Hi all! 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 autoyast=https://raw.githubusercontent.com/yast/autoyast-profiles-test/mast… 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 autoyast=https://autoyast.github.io/mini/sles15.xml or autoyast=https://autoyast.github.io/mini/leap15.xml 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? -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 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

2 1

Lesson Learned: How to Create Layout - Center Aligned Box with Left Aligned Content
by josef Reidinger 12 Feb '21

12 Feb '21

Hi, after quite long playing with achieving layout[1] I decide to write down what I found. Short Version ------------- To get nice box centered at middle of screen, but content in box left aligned use HBox( HStretch, VBox( VStretch, Left(<content>), VStretch ), HStretch ) Long Version ------------ 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 [1]). 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 [2] Josef [1] https://github.com/yast/yast-registration/pull/519 [2] https://yast-ui-bindings.surge.sh/classYWeight.html

3 3

Extended handling of YaST settings
by Steffen Winterfeldt 27 Jan '21

27 Jan '21

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: https://github.com/yast/yast-installation/issues/898 If you have suggestions or more use cases or just want to stay in touch, feel free to join the discussion. Steffen

3 2

YaST: highlights of development sprint 116
by Ancor Gonzalez Sosa 25 Jan '21

25 Jan '21

2021 is here with a lot of interesting news, and YaST development is not an exception. During the first sprint of the year we have worked on: - Writing NetworkManager configuration during system installation - Refining the mechanism to reuse existing EFI partitions - Using better names to reference devices in the boot loader - Improving AutoYaST behavior when no product has been specified - Updating the roles offered by yast2-vm - Many more small improvements here and there Check the whole report at: https://yast.opensuse.org/blog/2021-01-25/sprint-116 Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH

1 0

Pending Pull Requests
by yast-ci＠opensuse.org 25 Jan '21

25 Jan '21

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-installation: - bsc#1180142: do not use 'installation-helper' to create snapshots (9 days) https://github.com/yast/yast-installation/pull/901 Pending requests in repository yast-instserver: - Adapt Rakefile and Dockerfile for SLE-15-SP2 (72 days) https://github.com/yast/yast-instserver/pull/50 Pending requests in repository yast-metapackage-handler: - Extend unit test for existing functions (13 days) https://github.com/yast/yast-metapackage-handler/pull/23 Pending requests in repository yast-network: - [RFC] Permit to disable the virt bridge config proposal (31 days) https://github.com/yast/yast-network/pull/1137 Pending requests in repository yast-online-update: - Added recommends to yast2-online-update-frontend (bsc#1177997) (81 days) https://github.com/yast/yast-online-update/pull/33 Pending requests in repository yast-packager: - Adding NFS repository: Checking user input e.g. white spaces in serve… (46 days) https://github.com/yast/yast-packager/pull/543 - Include some hints in the "Priority" label (bsc#1154693) (114 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-theme: - Update branding (38 days) https://github.com/yast/yast-theme/pull/132 - Add pattern-budgie icon (boo#1176164) (72 days) https://github.com/yast/yast-theme/pull/131 Pending requests in repository yast-yast2: - add autowrapping to Yast2::Popup class (44 days) https://github.com/yast/yast-yast2/pull/1122 Pending requests in repository yast-ycp-ui-bindings: - Failing autowrap (47 days) https://github.com/yast/yast-ycp-ui-bindings/pull/64 - New UI Example for ComboBox (62 days) https://github.com/yast/yast-ycp-ui-bindings/pull/62 Pending requests in repository skelcd-control-openSUSE: - Ntp servers (13 days) https://github.com/yast/skelcd-control-openSUSE/pull/223 Pending requests in repository yast-auth-client: - Bsc1172340 (59 days) https://github.com/yast/yast-auth-client/pull/94 Pending requests in repository yast-auth-server: - Bsc1172340 (59 days) https://github.com/yast/yast-auth-server/pull/66 - Fix an issue where pkg dependencies were not install (121 days) https://github.com/yast/yast-auth-server/pull/63 - Fixes to make the YaST modules work (578 days) https://github.com/yast/yast-auth-server/pull/48 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (111 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository yast-storage-ng: - Partial fix for bug#176140 (68 days) https://github.com/yast/yast-storage-ng/pull/1166 - Display pathnames correctly in a Right-to-Left context (bsc#1128091) (62 days) https://github.com/yast/yast-storage-ng/pull/873 Pending requests in repository yast-caasp: - Allow Mirror configuration (72 days) https://github.com/yast/yast-caasp/pull/39 Pending requests in repository skelcd-control-leanos: - Default ntp servers (13 days) https://github.com/yast/skelcd-control-leanos/pull/72 Pending requests in repository yast-rmt: - Add metadata into packages (112 days) https://github.com/yast/yast-rmt/pull/51 - use docker image from OBS (131 days) https://github.com/yast/yast-rmt/pull/50 - Enforce full coverage (131 days) https://github.com/yast/yast-rmt/pull/40 Pending requests in repository skelcd-control-MicroOS: - sync with SLE (53 days) https://github.com/yast/skelcd-control-MicroOS/pull/27 - unify proposed partition sizes with openSUSE MicroOS (54 days) https://github.com/yast/skelcd-control-MicroOS/pull/26

1 0

Starting the installation in the summary
by David Díaz 19 Jan '21

19 Jan '21

Hi! Today I opened an issue[1] in yast2-installation for proposing to (almost) start the installation process in the summary screen. Benefits? Since the product control file[2] of each product sets reasonable defaults for most users (correct me if I'm wrong), the installation steps could be shortened. Users should adjust just the desired settings, nothing else. So, there is no reason for forcing them to go through the whole installation options in a specific order (unless, of course, for those dependent/coupled steps). What do you think? PS: I'm not sure if it has been discussed already in the past, but IMHO it worth it to (re)evaluate it. [1] https://github.com/yast/yast-installation/issues/903 [2] https://github.com/yast/yast-installation/blob/master/doc/control-file.md

5 10

Let's be stricter (and more helpful) in Debug mode
by Lukas Ocilka 19 Jan '21

19 Jan '21

Hi guys, I've already mentioned this at some calls before, but this is actually the right channel for discussing the idea. I've seen many times before, that there is, for instance, a media layout error, but we simply report that problem into the log and try to continue. Usually it's nothing critical in our eyes. As an example, we've recently seen that someone reported a missing Czech license in installer. Ladislav found out that the license actually exists, but wrongly uses "cz" instead of "cs" in its filename. The installer actually reported a warning into the log. Something like "unknown language 'cz'". So, what is the problem? It could have been spotted 3 months earlier. Plus it could have been fixed without us debugging the problem. Proposed solution: In case of Y2DEBUG==1, raise an internal error or rather show a pop-up error/warning message. This would not influence common installations, but openQA would catch and record it. With a little piece of work openQA could even skip it if needed. I would like to have a separate Y2SOMETHING variable to control the behavior (by default, X==1 in case of Y2DEBUG==1). Obviously, this means more work now and from time to time for adding such warning/error reports one by one. But that IMO pays off mid-to-long term. At the end we could have more time to fix "our" bugs :) What do you think? Thx Lukas

5 4

Let's improve yast2-firstboot
by David Díaz 19 Jan '21

19 Jan '21

Hi there! As a result of small research about the current status of the YaST Firstboot module, I have created a couple of issues in its Github repository[1] pointing out what I found wrong and my (sometimes wild) ideas to fix/improve it. I used the Github's issues feature to ease the interaction/discussion since you can add there your thoughts/ideas as a comment. But, of course, you can just reply to this thread if it is better for you. So, let me invite you to follow the links you can find in the first issue[2] and give your feedback to both, commented gotchas and suggested solutions. Thanks! [1] https://github.com/yast/yast-firstboot [2] https://github.com/yast/yast-firstboot/issues/115

2 1