February 2020 - 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] Reminder: verify_partial_doubles is not default
by Josef Reidinger 03 Dec '20

03 Dec '20

Hi, again I hit by thinking that verify_partial_doubles is now default in rspec3. It is not and will be in rspec4. So what it means? rspec does not check if mocked methods exists at all and it can result in many not so funny errors in test suite. I am just faced it in network, so I create non trivial commit[1] that enables it there. It includes also how to avoid failures on mocked class[2] which avoided build dependencies. From list of errors it can check is typos[3], mocking of wrong class[4] and mocking non-existing methods[5]. So feel free to take it as inspiration and enable it also in your test helper. Josef [1] https://github.com/yast/yast-network/pull/830/commits/e18da64fce25242a51710… [2] https://github.com/yast/yast-network/pull/830/commits/e18da64fce25242a51710… [3] https://github.com/yast/yast-network/pull/830/commits/e18da64fce25242a51710… [4] https://github.com/yast/yast-network/pull/830/commits/e18da64fce25242a51710… [5] https://github.com/yast/yast-network/pull/830/commits/e18da64fce25242a51710… -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

4 3

[yast-devel] Unifying YaST Contributing Guidelines
by David Díaz 04 Mar '20

04 Mar '20

Hi! As you probably know ;) we have more than 100 repositories. There fore, we have more than 100 CONTRIBUTING.md files, all of them with (in theory) the same content. That's means that we need to do more than 100 commits and pull requests for every little change in that file. Like now, that we should fix the broken Bugzilla link[1] fixing the product param. So, I'd like to propose having the full content only in the yast-yast2/CONTRIBUTING.md file[2] and a link to this file in the rest of them. What do you think? Do you have a better idea? Thank you! [1] https://github.com/yast/yast-yast2/issues/682 [2] https://github.com/yast/yast-yast2/blob/master/CONTRIBUTING.md -- David Díaz González YaST Team at SUSE Linux GmbH

4 5

[yast-devel] 15.2 enable online repositories?
by Felix Miata 02 Mar '20

02 Mar '20

Why, when attempting a NET upgrade, after selecting which installation to upgrade, is the subject question asked? Answering no causes a nothing to do result. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- 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] 15.2 y2logs (no journal files were found)
by Felix Miata 25 Feb '20

25 Feb '20

I was attempting HTTP upgrade from 42.3/TDE to 15.2beta. It found 531 packages to update, over 700 to install, and lots to remove. I went into package selection and deselected install recommended packages. That cut the to-be-installed to 144 and to-be-removed to 67. That seemed to be a lot to remove, including LLVM2, so I decided to abort, but wanted to save the logs to discuss here. That's when I found save_y2logs could find no journal files. Nevertheless, 2,682,680 bytes were saved: http://fm.no-ip.com/Tmp/SUSE/Leap/y2l-gx320-abort.tgz After abort I tried zypper dup: ... CommitResult (total 818, done 818, error 0, skipped 0, updateMessages 0) http://fm.no-ip.com/Tmp/SUSE/Leap/updateTestcase-2020-02-24-19-52-21/ # WINDOWMANAGER=/usr/bin/icewm startx still works # WINDOWMANAGER=/opt/trinity/bin/starttde startx still works TDM (from 15.1 repo) still works sound still works # pinxi -bxx System: Host: gx320 Kernel: 5.3.18-lp152.4-default x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Trinity R14.0.7 tk: Qt 3.5.0 wm: Twin dm: TDM Distro: openSUSE Leap 15.2 Beta Machine: Type: Desktop System: Dell product: OptiPlex 320 v: N/A serial: 214F6F1 Chassis: type: 7 serial: 214F6F1 Mobo: Dell model: 0TY915 serial: ..CN708217AGC1TI. BIOS: Dell v: 1.1.12 date: 06/17/2009 CPU: Dual Core: Intel Core2 Duo E4400 type: MCP arch: Core Merom speed: 2000 MHz Graphics: Device-1: Advanced Micro Devices [AMD/ATI] RC410 [Radeon Xpress 200/1100] vendor: Dell driver: radeon v: kernel bus ID: 01:05.0 chip ID: 1002:5a61 Display: server: X.Org 1.20.3 driver: ati,radeon unloaded: fbdev,modesetting,vesa resolution: 1680x1050~60Hz OpenGL: renderer: ATI RC410 v: 2.1 Mesa 19.2.6 direct render: Yes Network: Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter driver: 8139too v: 0.9.28 port: dc00 bus ID: 02:01.0 chip ID: 10ec:8139 Drives: Local Storage: total: 149.01 GiB used: 43.36 GiB (29.1%) Info: Processes: 169 Uptime: N/A Memory: 1.90 GiB used: 277.7 MiB (14.3%) Init: systemd v: 234 runlevel: 5 target: graphical.target Compilers: gcc: N/A Shell: bash v: 4.4.23 running in: konsole pinxi: 3.0.37-38 -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- 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 24 Feb '20

24 Feb '20

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-apparmor: - Port to rake (254 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (221 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-country: - Port to rake (221 days) https://github.com/yast/yast-country/pull/217 Pending requests in repository yast-devtools: - Y2logs analyzer (6 days) https://github.com/yast/yast-devtools/pull/149 - Supplement changes from YCC (26 days) https://github.com/yast/yast-devtools/pull/148 - Move desktop files (259 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-http-server: - Drop old testsuite (6 days) https://github.com/yast/yast-http-server/pull/49 Pending requests in repository yast-installation: - Demo: eager mode of zombie-killer 0.5 (472 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - network-ng: test cases document (draft) (94 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (220 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (121 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-squid: - packaging: remove SuSEfirewall2 artifacts (212 days) https://github.com/yast/yast-squid/pull/30 Pending requests in repository yast-sudo: - WIP: Add a CFA model for handling the sudoers file (55 days) https://github.com/yast/yast-sudo/pull/12 Pending requests in repository yast-users: - Improve readme (18 days) https://github.com/yast/yast-users/pull/224 - Move back the UMASK default value to /etc/login.defs (bsc#1099153) (599 days) https://github.com/yast/yast-users/pull/161 Pending requests in repository yast-yast2: - Change the way groups are defined (258 days) https://github.com/yast/yast-yast2/pull/936 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (389 days) https://github.com/yast/yast-yast2/pull/894 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (389 days) https://github.com/yast/yast-yast2/pull/893 - [WIP] Firewalld fixes for the new UI (537 days) https://github.com/yast/yast-yast2/pull/813 - [WIP] Drop SuSEfirewall2 completely (522 days) https://github.com/yast/yast-yast2/pull/806 Pending requests in repository yast-ycp-ui-bindings: - [WIP] Support bold font inside tables (549 days) https://github.com/yast/yast-ycp-ui-bindings/pull/35 Pending requests in repository yast-ruby-bindings: - [WIP] Don't crash on NoMethodError when Perl is involved (52 days) https://github.com/yast/yast-ruby-bindings/pull/224 - log method name (636 days) https://github.com/yast/yast-ruby-bindings/pull/216 Pending requests in repository yast-samba-client: - Use kerberos authentication by default during join (102 days) https://github.com/yast/yast-samba-client/pull/79 Pending requests in repository yast-rake: - Switch desktop directory (259 days) https://github.com/yast/yast-rake/pull/70 Pending requests in repository skelcd-control-openSUSE: - Adjust the roles to the new YaST Patterns (55 days) https://github.com/yast/skelcd-control-openSUSE/pull/195 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] Snapper-0.8.9 not building on old distros
by Martin Vidner 19 Feb '20

19 Feb '20

Hi, since we rewrote snapper's zypp plugin from Python to C++, snapper has new build dependencies that break the build for old distros. https://build.opensuse.org/package/show/filesystems:snapper/snapper I suspect that many of the build targets were addded just because we could, not because they serve a purpose. Can we simply drop them? If not, what should our supported distro policy for Snapper be? | Distro | Good Version | Bad Version | Bad Ver EOL | Reason | |------------------+--------------+-------------+-------------+----------------------------------------------| | Centos, SciLinux | ? | 7 | 2020-2024 | no libjson-c-devel | | RHEL | ? | 7 | | no libjson-c-devel | | Debian | 10 | 9 | 2020-2022 | boost/process.hpp: No such file or directory | | Fedora | 27 | 26 | 2018-05-29 | boost/process.hpp: No such file or directory | | SLE | 15-GA | 12-SP4 | | boost/process.hpp: No such file or directory | | oS Leap | 15.0 | 42.3 | 2019-07-01 | boost/process.hpp: No such file or directory | | xUbuntu | 18.04 (LTS) | 17.10 | 2018-07-19 | boost/process.hpp: No such file or directory | -- Martin Vidner, YaST Team http://en.opensuse.org/User:Mvidner

3 3

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

17 Feb '20

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-apparmor: - Port to rake (247 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (214 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-country: - Port to rake (214 days) https://github.com/yast/yast-country/pull/217 Pending requests in repository yast-devtools: - Supplement changes from YCC (19 days) https://github.com/yast/yast-devtools/pull/148 - Move desktop files (252 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-http-server: - Drop old testsuite (9 days) https://github.com/yast/yast-http-server/pull/49 Pending requests in repository yast-installation: - Demo: eager mode of zombie-killer 0.5 (465 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - Fixed validation of hostname (9 days) https://github.com/yast/yast-network/pull/1036 - Hostname(s) documentation (9 days) https://github.com/yast/yast-network/pull/1033 - network-ng: test cases document (draft) (87 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (213 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (114 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-pkg-bindings: - Remove legacy zypp::target::rpm::ConvertDBReport (68 days) https://github.com/yast/yast-pkg-bindings/pull/119 Pending requests in repository yast-security: - Using SysctlConfig class (9 days) https://github.com/yast/yast-security/pull/66 Pending requests in repository yast-squid: - packaging: remove SuSEfirewall2 artifacts (205 days) https://github.com/yast/yast-squid/pull/30 Pending requests in repository yast-sudo: - WIP: Add a CFA model for handling the sudoers file (48 days) https://github.com/yast/yast-sudo/pull/12 Pending requests in repository yast-users: - Improve readme (11 days) https://github.com/yast/yast-users/pull/224 - Move back the UMASK default value to /etc/login.defs (bsc#1099153) (592 days) https://github.com/yast/yast-users/pull/161 Pending requests in repository yast-yast2: - Handling sysctl values over different files/directories (9 days) https://github.com/yast/yast-yast2/pull/1021 - Change the way groups are defined (251 days) https://github.com/yast/yast-yast2/pull/936 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (382 days) https://github.com/yast/yast-yast2/pull/894 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (382 days) https://github.com/yast/yast-yast2/pull/893 - [WIP] Firewalld fixes for the new UI (530 days) https://github.com/yast/yast-yast2/pull/813 - [WIP] Drop SuSEfirewall2 completely (515 days) https://github.com/yast/yast-yast2/pull/806 Pending requests in repository yast-ycp-ui-bindings: - [WIP] Support bold font inside tables (542 days) https://github.com/yast/yast-ycp-ui-bindings/pull/35 Pending requests in repository yast-ruby-bindings: - [WIP] Don't crash on NoMethodError when Perl is involved (45 days) https://github.com/yast/yast-ruby-bindings/pull/224 - log method name (629 days) https://github.com/yast/yast-ruby-bindings/pull/216 Pending requests in repository yast-samba-client: - Use kerberos authentication by default during join (95 days) https://github.com/yast/yast-samba-client/pull/79 Pending requests in repository yast-rake: - Switch desktop directory (252 days) https://github.com/yast/yast-rake/pull/70 Pending requests in repository skelcd-control-openSUSE: - Adjust the roles to the new YaST Patterns (48 days) https://github.com/yast/skelcd-control-openSUSE/pull/195 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] Hack Week Project: YaST logs analyzer
by Josef Reidinger 13 Feb '20

13 Feb '20

Hi, for this hackweek beside checking crystal I also plan to move a bit forward with long standing question about usage of our modules and start writing logs analyzer[1]. So far what analyzer is able to do? 1. can read logs from archive or search directory tree. Of course also works with single y2log file even compressed. 2. can detect what module user runs for old and new runner ( y2core and also y2base ). 3. detects which UI is used for given modules 4. output is written as YAML so it can be easily process further example output: --- :modules: installation: :count: 26 :ui: :qt: 22 :ncurses: 4 firstboot: :count: 4 :ui: :qt: 3 :ncurses: 1 ftp-server: :count: 3 :ui: :ncurses: 3 Now question is what would be the most useful to proceed further? Few ideas: - obtain collection of real yast logs ( so not from autoyast or from testing, but from real customer ) and store it somewhere internally ( as it can contain sensitive data ). - add additional analysis. What will be useful? E.g. usage of expert partitioner, detailed time configuration, what is clicked in installation proposal? architecture usage and check differences in usage based on architecture? - filtering ability e.g. by arch or base product. Something like what customers use on SLE15SP1, what customers use on s390. What is often used on Tumbleweed. What is often used in ncurses, etc. Any other ideas? I still have one more day, so I can try to play with some ideas. Josef [1] https://github.com/yast/yast-devtools/pull/149 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0