February 2019 - 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] Highlights for the Leap 15.1 announcement
by Ancor Gonzalez Sosa 28 Mar '19

28 Mar '19

The time for the release announcement of Leap 15.1 is approaching. I was asked to provide some list of highlights related to YaST. Some obvious things that come to mind are: Look&Feel ========= - The sidebar with the steps of the installation process is back. - New icons everywhere. - Better HiDPI (4k Display) Support Installer improvements ====================== - Choosing the network backend during installation with one click. - Just click "next" to install (open)SUSE in a Raspberry Pi. - Configuration of SSH keys during installation (password-less systems) - Better default partitioning proposal in several scenarios (like small disks, systems with several disks and more). New Functionality ================= - Better management of services. - New UI to manage Firewalld, including AutoYaST support. - Better support for Salt formulas in yast2-configuration-management. - Better management of SSH keys per user. - The Partitioner can now directly format full disks, create software MD RAIDs on top of full disks, create partitions within a software-defined MD RAID and many others combinations. Including AutoYaST support for all those combinations. - Preliminary support for bcache in the Partitioner. I plan to expand those bullet points to be something bigger than a sentence (in the cases in which that makes sense), but first a wondered whether I was overlooking something interesting for the majority of final Leap 15.1 users. Thanks. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 5

[yast-devel] "can't modify frozen String" and ruby-bindings
by Ladislav Slezak 05 Mar '19

05 Mar '19

Hi all, I was fixing a "can't modify frozen String" crash in YaST registration when processing a translated string. After debugging and trying to write an unit test for it I found an interesting difference: it depends whether the translation for the message is available or not. Translation Available --------------------- > rpm -q yast2-trans-cs yast2-trans-cs-84.87.20180514.157a0650d-lp150.1.1.noarch > LC_ALL=cs_CZ.UTF-8 ruby -ryast -e 'include Yast::I18n; textdomain "base"; puts _("&Yes"); puts _("&Yes").frozen?' &Ano true So the result is a *frozen* translated string. The code would crash in this case. Translation Not Available ------------------------- > rpm -q yast2-trans-es package yast2-trans-es is not installed > LC_ALL=es_ES.UTF-8 ruby -ryast -e 'include Yast::I18n; textdomain "base"; puts _("&Yes"); puts _("&Yes").frozen?' &Yes false In this case you'll get the original untranslated and *not frozen* string. In this case it would NOT crash. :-S The Problem ----------- The problem is that when running the unit tests in Travis, Jenkins or in OBS no translation is installed and the tests run in the English locale. However, on user systems or during installation the translations are usually available. That means it's hard to test it in the same environment, the unit tests might not find this problem in the code. Moreover the translations for new texts might be available later, so it could work fine but crash later after updating the translation package without changing the YaST module. That's a debugging nightmare... Proposed Solution ----------------- The ruby-bindings code contains this line [1]: found ? Translation._(str) : str The fast_gettext gem returns nil when the translation is not available. In that case we return the original text. My proposed solution is to also freeze the not translated message to have consistent output: found ? Translation._(str) : str.freeze The Disadvantage ---------------- The disadvantage is that as a side effect of this change the passed parameter will be modified (becomes frozen), like this: a = "text" a.frozen? # => false puts _(a) a.frozen? # => true Usually that should not make any troubles as we either use string literals _("foo") or we use constants which should be preferably frozen anyway: TEXT = N_("foo") ... _(TEXT) (Or at least I'm not aware of any place where it would make troubles.) Of course, we could duplicate the string to not modify the original one: found ? Translation._(str) : str.dup.freeze but I'm afraid this would have memory and performance impact as all not translated strings would be duplicated. So I'd prefer the first solution and if you need to avoid freezing the original string you can make the copy yourselves, e.g.: puts _(a.dup) a.frozen? # => false (Or course this behavior and the solution needs to be well documented.) Any comments or ideas to this topic? Thank you! [1] https://github.com/yast/yast-ruby-bindings/blob/4652448963160abc234d1199f06… -- 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 4

[yast-devel] New documentation: Registration and SSL, generic SSL debugging hints
by Ladislav Slezak 28 Feb '19

28 Feb '19

Hi all, I was doing some small fixes and improvements in the SSL area in the registration module. I created a documentation about the SSL certificates and the registration module: https://github.com/yast/yast-registration/wiki/OpenSSL-Certificates For debugging and testing I learned some OpenSSL debugging commands and tricks, I have summarized them in this document: https://github.com/yast/yast-registration/wiki/OpenSSL-Debugging-Hints If you ever need to dump the server certificate, inspect a certificate in a *.pem file, check the SSL connection, run a testing HTTPS server or something like that then see the link above. -- 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

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 28 Feb '19

28 Feb '19

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-bootloader: - Not crash with internal error when grub install device not found (47 days) https://github.com/yast/yast-bootloader/pull/548 - Secure boot arm (96 days) https://github.com/yast/yast-bootloader/pull/544 - patch to not show popup when editenv list failed (166 days) https://github.com/yast/yast-bootloader/pull/537 - [no merge] More logging sle12 (253 days) https://github.com/yast/yast-bootloader/pull/523 Pending requests in repository yast-country: - Keyboard rewrite: encapsulate systemd actions (60 days) https://github.com/yast/yast-country/pull/200 - Keyboard rewrite: add documentation and license information (97 days) https://github.com/yast/yast-country/pull/199 - Keyboard rewrite: fix error setting x11 keymap (97 days) https://github.com/yast/yast-country/pull/198 - Keyboard rewrite: add more layouts to the module (97 days) https://github.com/yast/yast-country/pull/197 - Keyboard rewrite: select current layout on startup (97 days) https://github.com/yast/yast-country/pull/196 - Keyboard rewrite: Use strategy pattern to avoid coupling (97 days) https://github.com/yast/yast-country/pull/195 - Keyboard rewrite: Add rubocop (97 days) https://github.com/yast/yast-country/pull/174 - Keyboard rewrite: Test keyboard layout before change it (97 days) https://github.com/yast/yast-country/pull/173 - Keyboard rewrite: Change keyboard layout (97 days) https://github.com/yast/yast-country/pull/168 - Keyboard rewrite: Load keyboard layouts (97 days) https://github.com/yast/yast-country/pull/144 Pending requests in repository yast-devtools: - [RFC] Update the Rubocop config to version 0.59.2 (121 days) https://github.com/yast/yast-devtools/pull/134 Pending requests in repository yast-http-server: - Merged SLE-12-SP4 (5 days) https://github.com/yast/yast-http-server/pull/40 Pending requests in repository yast-installation: - Demo: eager mode of zombie-killer 0.5 (111 days) https://github.com/yast/yast-installation/pull/761 - Sp4 merge (273 days) https://github.com/yast/yast-installation/pull/708 Pending requests in repository yast-mail: - bsc#105491 setup of postfix with amavis DKIM signing does not work at all (125 days) https://github.com/yast/yast-mail/pull/37 Pending requests in repository yast-network: - [WIP] AutoYaST change the way the profile is intepreted (257 days) https://github.com/yast/yast-network/pull/646 - [RFC] Udev rule preparations (258 days) https://github.com/yast/yast-network/pull/639 - Fixed Internal Error on 'yast remote allow set=yes' (257 days) https://github.com/yast/yast-network/pull/635 - [WIP] Stop systemd socket associated services and ask for installing firewalld service definition (310 days) https://github.com/yast/yast-network/pull/624 - [WIP] Drop replace direct access to LanItems::Items whenever it is possible. (281 days) https://github.com/yast/yast-network/pull/588 Pending requests in repository yast-printer: - Security Audit Fixes: Hardening for Calling External Commands (71 days) https://github.com/yast/yast-printer/pull/23 Pending requests in repository yast-proxy: - Replace novell sites by SUSE ones for testing (bsc#1100366) (236 days) https://github.com/yast/yast-proxy/pull/19 Pending requests in repository yast-python-bindings: - Update documentation to be useful (23 days) https://github.com/yast/yast-python-bindings/pull/25 ERROR: API query limit exceeded -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Presenting new YaST features: Bcache and SUMA Salt formulas
by Ancor Gonzalez Sosa 27 Feb '19

27 Feb '19

Those who don't follow the YaST development sprint reports may overlook some extra blog posts the YaST Team has published to present a couple of features we have been working on lately. Let's fix that by providing direct access to the links here. Recapping the Bcache support in the YaST Partitioner https://lizards.opensuse.org/2019/02/27/recap-bcache-in-yast/ Getting YaST Configuration Module up-to-date (a.k.a. SUMA Salt Parametrizable Formulas in YaST) https://lizards.opensuse.org/2019/02/27/getting-yast-cm-up-to-date/ Enjoy. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] YaST: highlights of development sprint 71 and 72
by Ancor Gonzalez Sosa 27 Feb '19

27 Feb '19

What is better than a blog post explaining the novelties in YaST? Three blog posts! Check our usual sprint report covering the following topics. - Improvements in the Bcache support in the Partitioner - Users home as Btrfs subvolumes - Better visualization of Salt formulas - Automatic selection of the needed driver packages - Improvements in many other YaST areas https://lizards.opensuse.org/2019/02/27/yast-sprint-71-72/ As special bonus, it includes links to other two more exhaustive blog posts about the recently added Bcache support and about the revamped Configuration Management module. Cheers -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 27 Feb '19

27 Feb '19

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-bootloader: - Not crash with internal error when grub install device not found (46 days) https://github.com/yast/yast-bootloader/pull/548 - Secure boot arm (95 days) https://github.com/yast/yast-bootloader/pull/544 - patch to not show popup when editenv list failed (165 days) https://github.com/yast/yast-bootloader/pull/537 - [no merge] More logging sle12 (252 days) https://github.com/yast/yast-bootloader/pull/523 Pending requests in repository yast-country: - Keyboard rewrite: encapsulate systemd actions (59 days) https://github.com/yast/yast-country/pull/200 - Keyboard rewrite: add documentation and license information (96 days) https://github.com/yast/yast-country/pull/199 - Keyboard rewrite: fix error setting x11 keymap (96 days) https://github.com/yast/yast-country/pull/198 - Keyboard rewrite: add more layouts to the module (96 days) https://github.com/yast/yast-country/pull/197 - Keyboard rewrite: select current layout on startup (96 days) https://github.com/yast/yast-country/pull/196 - Keyboard rewrite: Use strategy pattern to avoid coupling (96 days) https://github.com/yast/yast-country/pull/195 - Keyboard rewrite: Add rubocop (96 days) https://github.com/yast/yast-country/pull/174 - Keyboard rewrite: Test keyboard layout before change it (96 days) https://github.com/yast/yast-country/pull/173 - Keyboard rewrite: Change keyboard layout (96 days) https://github.com/yast/yast-country/pull/168 - Keyboard rewrite: Load keyboard layouts (96 days) https://github.com/yast/yast-country/pull/144 Pending requests in repository yast-devtools: - [RFC] Update the Rubocop config to version 0.59.2 (120 days) https://github.com/yast/yast-devtools/pull/134 Pending requests in repository yast-http-server: - Merged SLE-12-SP4 (4 days) https://github.com/yast/yast-http-server/pull/40 Pending requests in repository yast-installation: - Demo: eager mode of zombie-killer 0.5 (110 days) https://github.com/yast/yast-installation/pull/761 - Sp4 merge (272 days) https://github.com/yast/yast-installation/pull/708 Pending requests in repository yast-mail: - bsc#105491 setup of postfix with amavis DKIM signing does not work at all (124 days) https://github.com/yast/yast-mail/pull/37 Pending requests in repository yast-network: - [WIP] AutoYaST change the way the profile is intepreted (256 days) https://github.com/yast/yast-network/pull/646 - [RFC] Udev rule preparations (257 days) https://github.com/yast/yast-network/pull/639 - Fixed Internal Error on 'yast remote allow set=yes' (256 days) https://github.com/yast/yast-network/pull/635 - [WIP] Stop systemd socket associated services and ask for installing firewalld service definition (309 days) https://github.com/yast/yast-network/pull/624 - [WIP] Drop replace direct access to LanItems::Items whenever it is possible. (280 days) https://github.com/yast/yast-network/pull/588 ERROR: API query limit exceeded -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Text freeze in RC1 (March 14th)
by Ladislav Slezak 26 Feb '19

26 Feb '19

Hi all, I asked about the translation schedule, particularly about the text freeze and I got this answer: "We would need all strings to be available to us in Weblate by RC 1 at the latest (March 14th)." So please make sure your new or updated texts are merged to master before March 14th, the sooner the better. If you know you will need a bug fix or a feature for RC2 you might commit the texts in advance and implement the code later. Keep in mind that the POT files are generated and uploaded once a day via a Jenkins job [1]. If you add/change the texts at the very last moment you might need to trigger that Jenkins job manually to ensure everything is processed. (The Jenkins job processes only the YaST packages, the other packages like snapper need to be handled by their respective maintainers or the automation.) [1] https://ci.suse.de/view/YaST/job/yast-POT-updater/ -- 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

1 0