August 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] 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

[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] Y2Packager::Resolvable - search by RPM dependencies
by Ladislav Slezak 01 Sep '20

01 Sep '20

Hi all, I have improved the Y2Packager::Resolvable call (and the internally used Pkg.Resolvables call) to allow searching by RPM dependencies (provides, obsoletes, conflicts, requires, recommends, suggests, supplements, enhances). Examples: Just use the dependency name as the additional parameter: Y2Packager::Resolvable.find(kind: :package, provides: "application()") This searches for the exact string. Optionally you can use a regular expression, just add the "_regexp" suffix to the dependency name: Y2Packager::Resolvable.find(kind: :package, obsoletes_regexp: "^yast2-config-") The regular expression is a POSIX extended regular expression, not a Ruby regular expression! The regexp parameter is just passed to the underlying libzypp/libsolv. The filtering happens directly on the C++ level so it's much faster than filtering on the Ruby level. Do not forget to escape regexp metacharacters like []() # seach for autoyast() supplements Y2Packager::Resolvable.find(kind: :package, supplements_regexp: "^autoyast\\(.*\\)") If an invalid regexp is passed then the ArgumentError exception is raised. You can combine more dependencies like "provides" and "obsoletes" in one call (if that makes sense). The result is logical AND, all dependencies must match. To use this new feature you need yast2-pkg-bindings-4.3.0 and yast2-4.3.21 (or newer). The old Pkg.PkgQueryProvides() call has been marked as obsolete. The enhanced Pkg.Resolvables() call is more powerful as it covers also the other dependencies than "Provides" and allows using a regexp. Enjoy! :) -- 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 2

[yast-devel] Special views in the Partitioner
by Ancor Gonzalez Sosa 31 Aug '20

31 Aug '20

As you all know, we recently got to the conclusion of adding a menu bar to the YaST Partitioner and getting rid of several entries we have in the left-hand tree. Check https://github.com/yast/yast-storage-ng/blob/master/doc/partitioner_ui.md#a… We are in the process of implementing that, but we are not sure how to represent the screens that are now a misplaced entry in the tree: Device Graphs, Installation Summary and Settings. Option 1: as pop-ups (even if they are full-screen pop-ups) In this option, "Settings" will be likely accessible through the "System" menu (which we are considering to rename to "Partitioner") and the other two would live in a "View" menu. See screenshot at https://github.com/yast/yast-storage-ng/pull/1120 We would consider that the normal view is the one with the devices tree at the left, the tables of devices at the right and the menu at the top. The other three views (settings, graph and summary) would be rendered on top of the normal one (if we use classic pop-ups) or hiding it (if we use the current approach of full-screen pop-ups). The menu bar would not be accessible from such views and the user would need to close the (maybe full-screen) pop-up using an "Ok" button to get back to the normal view. In the current Partitioner, double-clicking in a node of the Device Graph takes you to the entry of such device in the tree. I guess it would keep doing the same, so it would be an alternative way of closing the pop-up. Option 2: as four first-class citizen views In this option, there would be a "View" menu with four entries: Devices, Device Graph, Installation Summary and Settings. The "Devices" view would be equivalent to the normal one in the previous option. All the others would use the full screen (no left tree) and will still provide access to the menu bar. They would need no specific button to be closed. Instead, the user would use "View -> Devices" (or any other view, since all of them are equally important in this interface). The main advantage of this option is that we wouldn't need to change how the current Device Graphs, Summary or Settings screens work. For example, no need to add a button to save the new settings and close or another to quit the settings dialog without applying. Which option do you think would be better? 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

3 5

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

31 Aug '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 (443 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-autoinstallation: - Find the Base Product (118 days) https://github.com/yast/yast-autoinstallation/pull/599 Pending requests in repository yast-bootloader: - Add UPDATE_NVRAM in /etc/sysconfig/bootloader (bsc#1157550). (48 days) https://github.com/yast/yast-bootloader/pull/611 - Fix resume with uuid partition (410 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-core: - Fixes for gensalt handling with libxcrypt. (185 days) https://github.com/yast/yast-core/pull/144 Pending requests in repository yast-devtools: - Y2logs analyzer (187 days) https://github.com/yast/yast-devtools/pull/149 - Supplement changes from YCC (215 days) https://github.com/yast/yast-devtools/pull/148 - Move desktop files (448 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-installation: - [WIP] Warn when an old package is selected to install (20 days) https://github.com/yast/yast-installation/pull/878 - clarify that ssh_import processes host keys (bsc#1172400) (87 days) https://github.com/yast/yast-installation/pull/860 - Demo: eager mode of zombie-killer 0.5 (661 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - network-ng: test cases document (draft) (283 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (409 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (152 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-registration: - [SP3] Fix misleading default_skipping_text (BSC#1167795) (65 days) https://github.com/yast/yast-registration/pull/488 Pending requests in repository yast-vm: - bsc#1169214 - When NetworkManager is being used bridge creation will not work so show warning popup (12 days) https://github.com/yast/yast-vm/pull/47 Pending requests in repository yast-yast2: - Bnc#1081441 (137 days) https://github.com/yast/yast-yast2/pull/1047 - [WIP] CWM improvements (138 days) https://github.com/yast/yast-yast2/pull/1044 - Change the way groups are defined (447 days) https://github.com/yast/yast-yast2/pull/936 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (578 days) https://github.com/yast/yast-yast2/pull/894 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (578 days) https://github.com/yast/yast-yast2/pull/893 - [WIP] Firewalld fixes for the new UI (726 days) https://github.com/yast/yast-yast2/pull/813 - [WIP] Drop SuSEfirewall2 completely (711 days) https://github.com/yast/yast-yast2/pull/806 Pending requests in repository yast-ycp-ui-bindings: - [WIP] Support bold font inside tables (738 days) https://github.com/yast/yast-ycp-ui-bindings/pull/35 Pending requests in repository yast-ruby-bindings: - Fixes for gensalt handling with libxcrypt. (185 days) https://github.com/yast/yast-ruby-bindings/pull/239 - [WIP] Don't crash on NoMethodError when Perl is involved (241 days) https://github.com/yast/yast-ruby-bindings/pull/224 - log method name (825 days) https://github.com/yast/yast-ruby-bindings/pull/216 Pending requests in repository yast-rake: - Switch desktop directory (448 days) https://github.com/yast/yast-rake/pull/70 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] Pending Pull Requests
by yast-ci＠opensuse.org 24 Aug '20

24 Aug '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 (436 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-autoinstallation: - Find the Base Product (111 days) https://github.com/yast/yast-autoinstallation/pull/599 Pending requests in repository yast-bootloader: - Add UPDATE_NVRAM in /etc/sysconfig/bootloader (bsc#1157550). (41 days) https://github.com/yast/yast-bootloader/pull/611 - Fix resume with uuid partition (403 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-core: - Fixes for gensalt handling with libxcrypt. (178 days) https://github.com/yast/yast-core/pull/144 Pending requests in repository yast-devtools: - Y2logs analyzer (180 days) https://github.com/yast/yast-devtools/pull/149 - Supplement changes from YCC (208 days) https://github.com/yast/yast-devtools/pull/148 - Move desktop files (441 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-installation: - [WIP] Warn when an old package is selected to install (13 days) https://github.com/yast/yast-installation/pull/878 - clarify that ssh_import processes host keys (bsc#1172400) (80 days) https://github.com/yast/yast-installation/pull/860 - Demo: eager mode of zombie-killer 0.5 (654 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - network-ng: test cases document (draft) (276 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (402 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (145 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-registration: - [SP3] Fix misleading default_skipping_text (BSC#1167795) (58 days) https://github.com/yast/yast-registration/pull/488 Pending requests in repository yast-yast2: - Bnc#1081441 (130 days) https://github.com/yast/yast-yast2/pull/1047 - [WIP] CWM improvements (131 days) https://github.com/yast/yast-yast2/pull/1044 - Change the way groups are defined (440 days) https://github.com/yast/yast-yast2/pull/936 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (571 days) https://github.com/yast/yast-yast2/pull/894 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (571 days) https://github.com/yast/yast-yast2/pull/893 - [WIP] Firewalld fixes for the new UI (719 days) https://github.com/yast/yast-yast2/pull/813 - [WIP] Drop SuSEfirewall2 completely (704 days) https://github.com/yast/yast-yast2/pull/806 Pending requests in repository yast-ycp-ui-bindings: - [WIP] Support bold font inside tables (731 days) https://github.com/yast/yast-ycp-ui-bindings/pull/35 Pending requests in repository yast-ruby-bindings: - Fixes for gensalt handling with libxcrypt. (178 days) https://github.com/yast/yast-ruby-bindings/pull/239 - [WIP] Don't crash on NoMethodError when Perl is involved (234 days) https://github.com/yast/yast-ruby-bindings/pull/224 - log method name (818 days) https://github.com/yast/yast-ruby-bindings/pull/216 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] Innovation Time: installation of new server
by josef Reidinger 21 Aug '20

21 Aug '20

Hi, as my today innovation time I spend couple of hours with installing our new server in NUE. For access please see https://wiki.suse.net/index.php/YaST/team-it-infrastructure#Our_Servers ( internal only! ). Few my notes I observe during it: 1. it uses BMC to initial access to machine. Java applet version with openJDK was disaster, HTML5 version works surprising well. 2. PXE in NUE works quite fine, it just needs tuning of kernel parameter. 3. installation without ssh was not possible. I am not sure what UI is picked, but it does not show anything in console. So I do ssh installation. 4. suggested ssh -X was quite slow. Probably ssh -XYC will be faster, but I do not try it. 5. System is SLE 15 SP2 and I picked system role KVM virtualization host and configuration looks reasonable. 6. partitioning needs tunning. It wants to use just one of SSD, but guided setup with using both disk and LVM create good proposal ( reasonable system and maximum /var/lib/libvirt for images ) 7. I keep rest of defaults as it looks reasonable. So what now? Current there are only my ssh keys, but I already ask infra team to add machine to their salt slaves and apply ssh for yast team members same as we have in prague server. connection via libvirt works well for me. No VM is there yet, but maybe we can migrate our german IBS workers. Josef -- 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] Virtual Ruby Conference Tomorrow
by josef Reidinger 20 Aug '20

20 Aug '20

Hi, if you are interested tomorrow is free ruby virtual conference. See https://noruko.org/ Some talks can be interesting, maybe mvidner find Sorbet presentation interesting. Matz will talk about ruby 3.0 and more. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0