May 2022 - 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

Modified installation progress
by josef Reidinger 06 Jul '22

06 Jul '22

Challenge: ---------- Libzypp supports parallel download and install. Yast installation progress does not fit it at all [1]. Issues are secondary progress bar that does not work with parallel installation. Also there are overwhelming amount of information on screen that is quite distracting. That information is often wrong like time estimation. And also table for media is a bit useless nowadays as everything is on one iso/medium, so there is no need to see when cd switch will be needed. The details tab are the most visible as it is default one. Proposal: --------- Remove completely that details tab and keep just release notes one[2]. It contains release notes that contain useful information and also has just one progress bar. For that bar remove keep always just remaining size and count of packages, so user has idea how it does, but do not print what exactly is installing or any time estimation. If there are more release notes allow to switch between them. Also keep possibility to have slide show which we had in past for installation if someone create some ( when checked other OSes, the Ubuntu slide show during installation looks probably the best from user POV ). The same changes will apply to ncurses front end[3], we just need to check why formatting of release notes are so badly formatted. And same for opensuse[4] of course. Josef [1] https://pasteboard.co/cNBjER6SnLLT.png [2] https://pasteboard.co/WnI7wS7VVVqq.png [3] https://pasteboard.co/vzQvY1PaVDaD.png [4] https://pasteboard.co/FzEqcIN7Xnas.png

15 40

Talk for openSUSE Conference 2022
by Ancor Gonzalez Sosa 04 Jun '22

04 Jun '22

I plan to submit this. Feel free to provide feedback before I do it. Title: Almost two years of YaST News Subtitle: Recent changes and future plans at YaSTland Abstract: YaST, the flagship installer and configuration tool of openSUSE is in constant development. Just as its unattended companion AutoYaST. Although the YaST Team at SUSE tries to communicate progress as often as possible in the YaST Blog, it has been almost two years since we presented the "Top 25 New Features in (Auto)YaST" at openSUSE Conference 2020. So it's time for another live update! We will recap the main changes and new features that are already integrated into openSUSE Tumbleweed and that will be included at openSUSE Leap 15.4, to be released just a couple of days after the talk. We will also take a look to some ideas for future development... and we really need the feedback of the whole openSUSE community for that. So please join us and speak up! -- Ancor González Sosa YaST Team at SUSE Software Solutions

5 8

"YaST in a container" or "YaST without YaST"
by Ladislav Slezák 31 May '22

31 May '22

Hello! I did some research about YaST and containers and here is my summary what I found. But at first lets start with two IMPORTANT DISCLAIMERS: 1. This is still just a research or proof of concept project, we might or might not use this approach in the future, i.e. no promises for anything! 2. If you want to test this approach then it is highly recommended to use a testing virtual machine, do NOT use it in production systems, it is still an experiment! Why? ==== OK, let's start with the reasons why to have YaST in a container. As you probably know YaST has quite a big dependency tree and that makes it difficult to use it a really minimal system. It needs Ruby, Perl, libyui, lots of other libraries and tools. And all of that might mess up your fine tuned minimal system. On the other hand a container has all dependencies hidden inside, from the outside it actually looks like one big binary blob. Additionally it can be very easily removed from the system if it is not needed anymore. Another reason might be using different versions of libraries or languages than shipped in the product. In theory we could use Ruby 3.1 in the container although SLES would be still shipped with the old Ruby 2.5 for compatibility reasons. Another interesting feature could be cross distribution ability. For example you could run the powerful YaST partitioner in a container on an Ubuntu or Debian system. Nice, isn't it? :-o Today I found one more interesting use case: disaster recovery. First I removed zypper + libzypp from the system and I was able to install it back using YaST package manager in a container. Then I even removed rpm (!) itself and I was still able to install it back to the system via the YaST container! Of course, this requires that you have already installed docker or podman and they work properly. ;-) YaST Changes ============ Of course, running in a container needs some small changes in YaST. Unfortunately you cannot take the existing modules and expect everything will just work. So far I have adapted these YaST clients: "repositories" - the repository manager (the GPG key manager which can be started from it works as well) "sw_single" - the package manager "scc - registration module, designed for SLES but you can actually also register openSUSE Leap (so you can later migrate it to SLES automatically) Prototype ========= I built a small package "yast-in-container" [1][2]. It is just a small shell script which does not depend on YaST at all. It only requires podman or docker to be installed (and running, in case of docker). See the README.md file [2] for details how to install it. It provides two commands, "yast2_container" and "yast_container" which work the same way as the original "yast2" and "yast" commands. You need to be logged in as "root" user to use them. The script downloads the container image [3][4] from OBS and runs the specified client (see above) from the container. The prototype works in Leap 15.4 or SLES15-SP4. It should work in older versions (15.3 or SP3), but that's untested and makes it even more "dangerous" to use as the container is based on openSUSE Leap 15.4. Feedback ======== It would be nice to get some feedback about this idea or about using the prototype. For more details see the README.md file [3]. Enjoy! Ladislav [1] https://github.com/yast/yast-in-container [2] https://build.opensuse.org/package/show/YaST:Head/yast-in-container [3] https://build.opensuse.org/package/show/YaST:Head/yast-mgmt-ncurses-leap_la… [4] https://build.opensuse.org/package/show/YaST:Head/yast-mgmt-qt-leap_latest -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

1 0

Pending Pull Requests
by yast-ci＠opensuse.org 30 May '22

30 May '22

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-devtools: - Sle15sp3 boo1199396 (19 days) https://github.com/yast/yast-devtools/pull/168 - Set %yast_icondir to /usr/share/icons/hicolor (bsc#1186066) (111 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-installation: - Remake some icons (76 days) https://github.com/yast/yast-installation/pull/1028 Pending requests in repository yast-kdump: - Implement KDUMP_AUTO_RESIZE (34 days) https://github.com/yast/yast-kdump/pull/123 Pending requests in repository yast-packager: - Remake some icons (95 days) https://github.com/yast/yast-packager/pull/603 Pending requests in repository yast-python-bindings: - Sle15 sp1 examples fixup (9 days) https://github.com/yast/yast-python-bindings/pull/42 Pending requests in repository yast-theme: - Add pantheon desktop support (180 days) https://github.com/yast/yast-theme/pull/154 Pending requests in repository yast-update: - [SP3] Use the "norecovery" mount option (bsc#1195894) (103 days) https://github.com/yast/yast-update/pull/179 Pending requests in repository yast-auth-server: - Fix log path (65 days) https://github.com/yast/yast-auth-server/pull/72 Pending requests in repository yast.github.io: - [dependencies] Bump nokogiri from 1.13.3 to 1.13.6 (10 days) https://github.com/yast/yast.github.io/pull/324 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (110 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository helper_scripts: - [dependencies] Bump nokogiri from 1.13.3 to 1.13.6 in /jekyll (10 days) https://github.com/yast/helper_scripts/pull/39 Pending requests in repository yast-samba-provision: - Sle15 sp1 update (9 days) https://github.com/yast/yast-samba-provision/pull/10 Pending requests in repository yast-sap-ha: - Sle 15 sp3 (7 days) https://github.com/yast/yast-sap-ha/pull/9 - SUSE SAP HA Yast wizard for HANA doesn´t configure the HANA hooks. (7 days) https://github.com/yast/yast-sap-ha/pull/7

1 0

FYI: parted and Partition Type GUIDs
by Arvin Schnell 23 May '22

23 May '22

Hi, upstream parted accepted several new patches from SUSE and can now print and set the "Partition Type GUID" on GPT. The changes are already included in openSUSE Factory. So if needed it would be easy to support all the GUIDs needed for the Discoverable Partitions Specification [1]. Two possible implementation in libstorage-ng look obvious: 1. Extend the existing list of IDs: + No additional interface + Good names in commit messages 2. Add extra interface to directly deal with GUIDs: + More flexible ciao Arvin [1] https://systemd.io/DISCOVERABLE_PARTITIONS/ -- Arvin Schnell, <aschnell(a)suse.com> Senior Software Engineer, Research & Development SUSE Software Solutions Germany GmbH Maxfeldstraße 5 90409 Nürnberg Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman

1 0

Gettext and Qt Designer
by Ladislav Slezák 23 May '22

23 May '22

Hello, JFYI, this might be interesting for the community or developers, we added translation support for Qt Designer files to YaST/libyui. This includes support for extracting the widget labels to POT file (https://github.com/yast/yast-devtools/pull/169) and processing them via Gettext in Qt when loading the *.ui files (https://github.com/libyui/libyui/pull/76). These PRs might be interesting for you if you want to use Gettext translations in a Qt application designed with Qt Designer. Thanks to Stefan (HuHa) for the libyui part! Enjoy! :-) -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

1 0

Pending Pull Requests
by yast-ci＠opensuse.org 23 May '22

23 May '22

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-devtools: - Sle15sp3 boo1199396 (12 days) https://github.com/yast/yast-devtools/pull/168 - Set %yast_icondir to /usr/share/icons/hicolor (bsc#1186066) (104 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-installation: - Remake some icons (69 days) https://github.com/yast/yast-installation/pull/1028 Pending requests in repository yast-kdump: - Implement KDUMP_AUTO_RESIZE (27 days) https://github.com/yast/yast-kdump/pull/123 Pending requests in repository yast-packager: - Remake some icons (88 days) https://github.com/yast/yast-packager/pull/603 Pending requests in repository yast-theme: - Add pantheon desktop support (173 days) https://github.com/yast/yast-theme/pull/154 Pending requests in repository yast-update: - [SP3] Use the "norecovery" mount option (bsc#1195894) (96 days) https://github.com/yast/yast-update/pull/179 Pending requests in repository yast-auth-server: - Fix log path (58 days) https://github.com/yast/yast-auth-server/pull/72 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (103 days) https://github.com/yast/yast-journal/pull/45

1 0

YaST: 4th development report of 2022
by Ancor Gonzalez Sosa 17 May '22

17 May '22

As you all know, the YaST team is lately involved in many projects not limited to YaST itself. So it's time to take a look to how things are moving on: - Recent changes for YaST (just in time for Leap 15.4) - Containerizing YaST to make it useful in container-based environments like openSUSE Micro. - Evolution of D-Installer Check the whole report at https://yast.opensuse.org/blog/2022-05-17/yast-report-2022-4 Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH

1 0

Pending Pull Requests
by yast-ci＠opensuse.org 16 May '22

16 May '22

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-devtools: - Set %yast_icondir to /usr/share/icons/hicolor (bsc#1186066) (97 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-installation: - Remake some icons (62 days) https://github.com/yast/yast-installation/pull/1028 Pending requests in repository yast-kdump: - Implement KDUMP_AUTO_RESIZE (20 days) https://github.com/yast/yast-kdump/pull/123 Pending requests in repository yast-packager: - Remake some icons (81 days) https://github.com/yast/yast-packager/pull/603 Pending requests in repository yast-python-bindings: - Sle15 sp1 examples fixup (6 days) https://github.com/yast/yast-python-bindings/pull/42 Pending requests in repository yast-theme: - Add pantheon desktop support (166 days) https://github.com/yast/yast-theme/pull/154 Pending requests in repository yast-update: - [SP3] Use the "norecovery" mount option (bsc#1195894) (89 days) https://github.com/yast/yast-update/pull/179 Pending requests in repository yast-auth-server: - Fix log path (51 days) https://github.com/yast/yast-auth-server/pull/72 Pending requests in repository yast.github.io: - [dependencies] Bump nokogiri from 1.13.3 to 1.13.4 (33 days) https://github.com/yast/yast.github.io/pull/321 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (96 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository helper_scripts: - [dependencies] Bump nokogiri from 1.13.3 to 1.13.4 in /jekyll (33 days) https://github.com/yast/helper_scripts/pull/38 Pending requests in repository system-role-common-criteria: - add a missing Wizard.CloseDialog (bsc#1194279) (27 days) https://github.com/yast/system-role-common-criteria/pull/7

1 0