May 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

Revamping yast2-users: the UI
by David Díaz 14 Sep '21

14 Sep '21

Hi there! In the context of revamping yast2-users[1], I spent some days looking for an alternative layout that could help to improve the current UI by reducing the number of tabs and grouping form fields to make better use of available space. However, due to our resolution constraints (UI must fit well in an 80x24 terminal) and some UI library limitations[2], looks like there is not too much room for big changes and our best bet is to keep the layout almost as it is, just making some necessary adjustments[3]. Summarizing them a lot, those changes will consist of adding a top menu bar for making easier the user navigation, moving all settings to the same dialog, improving filters by using a popup, making small changes in forms, and adding some summary views. Of course, nothing is written in stone and it would be nice to know your feedback and/or ideas too. So, please, keep reading the following links if you are interested and tell us what do you think. Is there anything we overlooked? Some other ideas we should evaluate? Remember that you can reach us by email, on IRC, or even by directly leaving a comment in those Github issues. Thanks! [1] "Revamping yast2-users" mailing list thread - https://lists.opensuse.org/archives/list/yast-devel@lists.opensuse.org/thre… [2] "UI library limitations" https://github.com/yast/yast-users-ng/issues/8 [3] "Revamping yast2-users UI: an initial proposal" https://github.com/yast/yast-users-ng/issues/6 -- David Díaz YaST Team at SUSE LINUX GmbH IRC: dgdavid

1 1

[yast-devel] https://en.opensuse.org/SDB:Linuxrc in need of edit???
by Felix Miata 30 Aug '21

30 Aug '21

NameScheme=by-label on installer cmdline has had no effect I have observed for a lot longer than I can remember, several years at least, continuing in 15.3 build 117.13. Has it been removed and the linuxrc page need matching update? Is this a broken installer option? Am I not understanding why it's listed on the linuxrc page? Shouldn't it prevent me from needing to change default mount by in the expert partitioner? -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

2 1

Fwd: Moving from Freenode to Libera.Chat
by Ancor Gonzalez Sosa 02 Jun '21

02 Jun '21

I know there is already a #yast channel at libera. But so far I have never seen more than 5-8 people there. Now it seems it's kind of official that most openSUSE channels are being moved. What should we do? Cheers. -------- Forwarded Message -------- Subject: Moving from Freenode to Libera.Chat Date: Thu, 27 May 2021 12:04:51 +0200 (CEST) From: Gerald Pfeifer <gp(a)suse.com> To: opensuse-project(a)opensuse.org, factory(a)lists.opensuse.org Hi everyone, as some of you noticed, lately there've been challenges around Freenode, the IRC network that has been home to a number of openSUSE channels for years. See, for example, https://arstechnica.com/gadgets/2021/05/freenode-irc-has-been-taken-over-by… https://news.itsfoss.com/freenode-controversy/ Approached by several of you we discussed this with those, the board, and the weekly release meeting. There is consensus to move our channels to Libera.Chat ( https://libera.chat ), a new network many other projects are migrating to as well. With help from Antonio and Sasi I already registered the openSUSE project with Libera.Chat (which by itself is not a move yet) and Marcus R. and others are ready to execute the move. The plan of record is to move quickly. If you have any concerns or questions, please advise as soon as possible. Likewise if you support. Thanks, Gerald PS: https://code.opensuse.org/board/tickets/issue/4 publicly tracks this matter on the openSUSE side; feel free to chime in there. -- Dr. Gerald Pfeifer <gp(a)suse.com>, CTO @SUSE + chair @openSUSE

7 9

Pending Pull Requests
by yast-ci＠opensuse.org 31 May '21

31 May '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-bootloader: - Avoid conflicts with filesystem and hicolor-icon-theme (bsc#1184786) (13 days) https://github.com/yast/yast-bootloader/pull/642 - arm can boot on uefi (13 days) https://github.com/yast/yast-bootloader/pull/641 Pending requests in repository yast-devtools: - Set %yast_icondir to /usr/share/icons/hicolor (bsc#1186066) (13 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-drbd: - packaging: Do not build for i586 and s390 (9 days) https://github.com/yast/yast-drbd/pull/32 Pending requests in repository yast-installation: - Avoid conflicts with filesystem and hicolor-icon-theme (bsc#1184786) (11 days) https://github.com/yast/yast-installation/pull/958 - Replace old splash commands with plymouth ones (131 days) https://github.com/yast/yast-installation/pull/904 Pending requests in repository yast-instserver: - Adapt Rakefile and Dockerfile for SLE-15-SP2 (198 days) https://github.com/yast/yast-instserver/pull/50 Pending requests in repository yast-metapackage-handler: - Extend unit test for existing functions (139 days) https://github.com/yast/yast-metapackage-handler/pull/23 Pending requests in repository yast-online-update: - Improved openSUSE/SLE detection (bsc#1184243) (59 days) https://github.com/yast/yast-online-update/pull/35 - Added recommends to yast2-online-update-frontend (bsc#1177997) (207 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… (172 days) https://github.com/yast/yast-packager/pull/543 - Include some hints in the "Priority" label (bsc#1154693) (240 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-python-bindings: - Fix backtrace formatting in YPython::PyErrorHandler() (Merge SLE-15-SP3 into master) (59 days) https://github.com/yast/yast-python-bindings/pull/39 - Fix backtrace formatting in YPython::PyErrorHandler() (Merge SLE-15-SP2 into SLE-15-SP3) (59 days) https://github.com/yast/yast-python-bindings/pull/38 Pending requests in repository yast-theme: - Add pattern-deepin.svg (25 days) https://github.com/yast/yast-theme/pull/146 - Fix the icons' style and minify them (43 days) https://github.com/yast/yast-theme/pull/143 - Add pattern-budgie icon (boo#1176164) (101 days) https://github.com/yast/yast-theme/pull/131 Pending requests in repository yast-ycp-ui-bindings: - Failing autowrap (173 days) https://github.com/yast/yast-ycp-ui-bindings/pull/64 - New UI Example for ComboBox (188 days) https://github.com/yast/yast-ycp-ui-bindings/pull/62 Pending requests in repository skelcd-control-openSUSE: - Add support for riscv64 (23 days) https://github.com/yast/skelcd-control-openSUSE/pull/241 - Ntp servers (139 days) https://github.com/yast/skelcd-control-openSUSE/pull/223 Pending requests in repository yast-auth-server: - Fix an issue where pkg dependencies were not install (247 days) https://github.com/yast/yast-auth-server/pull/63 - Fixes to make the YaST modules work (704 days) https://github.com/yast/yast-auth-server/pull/48 Pending requests in repository yast.github.io: - [dependencies] Bump nokogiri from 1.11.2 to 1.11.5 (10 days) https://github.com/yast/yast.github.io/pull/289 - [dependencies] Bump rexml from 3.2.4 to 3.2.5 (30 days) https://github.com/yast/yast.github.io/pull/286 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (237 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository yast-storage-ng: - Partial fix for bug#176140 (194 days) https://github.com/yast/yast-storage-ng/pull/1166 Pending requests in repository helper_scripts: - [dependencies] Bump nokogiri from 1.11.3 to 1.11.4 in /jekyll (11 days) https://github.com/yast/helper_scripts/pull/28 Pending requests in repository docker-yast-ruby: - drop travis (125 days) https://github.com/yast/docker-yast-ruby/pull/37 Pending requests in repository docker-yast-cpp: - drop travis (125 days) https://github.com/yast/docker-yast-cpp/pull/26 Pending requests in repository skelcd-control-leanos: - Default ntp servers (139 days) https://github.com/yast/skelcd-control-leanos/pull/72 Pending requests in repository yast-rmt: - Add metadata into packages (238 days) https://github.com/yast/yast-rmt/pull/51 - use docker image from OBS (257 days) https://github.com/yast/yast-rmt/pull/50 - Enforce full coverage (257 days) https://github.com/yast/yast-rmt/pull/40 Pending requests in repository skelcd-control-MicroOS: - sync with SLE (179 days) https://github.com/yast/skelcd-control-MicroOS/pull/27 - unify proposed partition sizes with openSUSE MicroOS (180 days) https://github.com/yast/skelcd-control-MicroOS/pull/26 Pending requests in repository skelcd-control-SMO: - install the microos-selinux pattern by default (39 days) https://github.com/yast/skelcd-control-SMO/pull/6

1 0

New /var/log/YaST2/installation_info/
by Ladislav Slezak 25 May '21

25 May '21

Hi all, I (with Schubi's help) have added a new logging facility into the YaST installer. It dumps some data in YAML format into the /var/log/YaST2/installation_info/ directory. Currently YaST writes the new logs when starting the installation and when that "No base product found" error happens (that was actually the original reason for creating this logging functionality). But you can easily create a dump whenever you need, usually when something goes wrong: require "installation/installation_info" ::Installation::InstallationInfo.instance.write( "Setting foo option failed", additional_info: "File foo does not exist" ) The default dump contains some basic data (repositories, products....) but you can easily extend the dumped data by calling: ::Installation::InstallationInfo.instance.add_callback("my_module") do { "foo" => foo.value, "bar" => bar.value } end The data will be saved into the YAML file as key "my_module" with the data returned by the block. The key should be unique to avoid collisions, a good idea is to use the package name. Note: avoid saving some sensitive private data like passwords or registration keys. The dump files are also archived by the "save_y2logs" script and they might be attached to bugzilla or sent my email... Why using blocks? The block behaves like a callback, the advantage is that it is evaluated at the time when writing the dump file. That ensures you always write the current. Reading the y2log is difficult if user changes same values, goes back and forth in the workflow..., having the current dump helps a lot in that cases. That is also important for product selection because the libzypp products might change whenever a repository is added or modified, the dependency solver might change the selected products, etc... See installation/installation_info.rb for more details: https://github.com/yast/yast-yast2/blob/e9b29cf6ac80a2ef9148021c516f4e58e09… Enjoy! :) -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

1 0

[yast-devel] Equality is important (comparing Array elements issue)
by Knut Alejandro Anderssen González 24 May '21

24 May '21

## Short version or Reminder Any subclass that overrides 'eql?' should also override 'hash' appropriately. ## Long version Probably all of us will agree that equality is very important... but it will vary depending on what we are trying to compare. In ruby we have different methods to compare objects... (==, ===, eql?, equal?), and it is very important to know their differences. The '==' is the 'daily used one' and in descendant subclasses. https://ruby-doc.org/core-2.5.3/BasicObject.html#method-i-3D-3D As described in the documentation subclasses, For objects of class Object, 'eql?' is synonymous with '==' and subclasses normally continue this tradition by aliasing 'eql?' to the overriden '==' method. We have done this in different places in YaST (just look for 'alias_method :eql?, :=='). But in most of the cases we have omitted the 'hash' method override which could be a problem in case we use Hashes or Arrays. And this is basically what has happened in a recent bug where the user had 16 interfaces configured and adding one more deleted all his routes. (What? 16 is fine but 17 is not?) https://ruby-doc.org/core-2.7.0/Array.html#method-i-2D https://github.com/ruby/ruby/blob/master/array.c Basically the 'difference' or '-' methods use 'eql?' for comparing elements when the array is smaller than 17 elements and the␣ 'hash' when it is bigger. Some Links: - Recent bug https://bugzilla.suse.com/show_bug.cgi?id=1186082 - https://github.com/yast/yast-storage-ng/pull/491/commits/1144a6ee3d88154f92… - https://stevenharman.net/well-behaved-ruby-object-equality -- Knut Alejandro Anderssen González YaST Team at SUSE Linux GmbH

3 2

Pending Pull Requests
by yast-ci＠opensuse.org 24 May '21

24 May '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-bootloader: - Avoid conflicts with filesystem and hicolor-icon-theme (bsc#1184786) (6 days) https://github.com/yast/yast-bootloader/pull/642 - arm can boot on uefi (6 days) https://github.com/yast/yast-bootloader/pull/641 Pending requests in repository yast-devtools: - Set %yast_icondir to /usr/share/icons/hicolor (bsc#1186066) (6 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-installation: - Replace old splash commands with plymouth ones (124 days) https://github.com/yast/yast-installation/pull/904 Pending requests in repository yast-instserver: - Adapt Rakefile and Dockerfile for SLE-15-SP2 (191 days) https://github.com/yast/yast-instserver/pull/50 Pending requests in repository yast-metapackage-handler: - Extend unit test for existing functions (132 days) https://github.com/yast/yast-metapackage-handler/pull/23 Pending requests in repository yast-network: - Removed unused methods and imports. (11 days) https://github.com/yast/yast-network/pull/1221 Pending requests in repository yast-online-update: - Improved openSUSE/SLE detection (bsc#1184243) (52 days) https://github.com/yast/yast-online-update/pull/35 - Added recommends to yast2-online-update-frontend (bsc#1177997) (200 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… (165 days) https://github.com/yast/yast-packager/pull/543 - Include some hints in the "Priority" label (bsc#1154693) (233 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-python-bindings: - Fix backtrace formatting in YPython::PyErrorHandler() (Merge SLE-15-SP3 into master) (52 days) https://github.com/yast/yast-python-bindings/pull/39 - Fix backtrace formatting in YPython::PyErrorHandler() (Merge SLE-15-SP2 into SLE-15-SP3) (52 days) https://github.com/yast/yast-python-bindings/pull/38 Pending requests in repository yast-theme: - Add pattern-deepin.svg (18 days) https://github.com/yast/yast-theme/pull/146 - Fix the icons' style and minify them (36 days) https://github.com/yast/yast-theme/pull/143 - Add pattern-budgie icon (boo#1176164) (94 days) https://github.com/yast/yast-theme/pull/131 Pending requests in repository yast-ycp-ui-bindings: - Failing autowrap (166 days) https://github.com/yast/yast-ycp-ui-bindings/pull/64 - New UI Example for ComboBox (181 days) https://github.com/yast/yast-ycp-ui-bindings/pull/62 Pending requests in repository yast-ruby-bindings: - Logging all available products information into directory /var/log/Ya… (100 days) https://github.com/yast/yast-ruby-bindings/pull/267 Pending requests in repository skelcd-control-openSUSE: - Add support for riscv64 (16 days) https://github.com/yast/skelcd-control-openSUSE/pull/241 - Ntp servers (132 days) https://github.com/yast/skelcd-control-openSUSE/pull/223 Pending requests in repository yast-auth-server: - Fix an issue where pkg dependencies were not install (240 days) https://github.com/yast/yast-auth-server/pull/63 - Fixes to make the YaST modules work (697 days) https://github.com/yast/yast-auth-server/pull/48 Pending requests in repository yast.github.io: - [dependencies] Bump rexml from 3.2.4 to 3.2.5 (23 days) https://github.com/yast/yast.github.io/pull/286 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (230 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository yast-storage-ng: - Partial fix for bug#176140 (187 days) https://github.com/yast/yast-storage-ng/pull/1166 Pending requests in repository docker-yast-ruby: - drop travis (118 days) https://github.com/yast/docker-yast-ruby/pull/37 Pending requests in repository docker-yast-cpp: - drop travis (118 days) https://github.com/yast/docker-yast-cpp/pull/26 Pending requests in repository skelcd-control-leanos: - Default ntp servers (132 days) https://github.com/yast/skelcd-control-leanos/pull/72 Pending requests in repository yast-rmt: - Add metadata into packages (231 days) https://github.com/yast/yast-rmt/pull/51 - use docker image from OBS (250 days) https://github.com/yast/yast-rmt/pull/50 - Enforce full coverage (250 days) https://github.com/yast/yast-rmt/pull/40 Pending requests in repository skelcd-control-MicroOS: - sync with SLE (172 days) https://github.com/yast/skelcd-control-MicroOS/pull/27 - unify proposed partition sizes with openSUSE MicroOS (173 days) https://github.com/yast/skelcd-control-MicroOS/pull/26 Pending requests in repository skelcd-control-SMO: - install the microos-selinux pattern by default (32 days) https://github.com/yast/skelcd-control-SMO/pull/6

1 0

Packaging icons and %{yast_icondir} macro
by Ladislav Slezak 18 May '21

18 May '21

Hi! In Tumbleweed they want to change the default permissions of the /usr/share/icons/ directory. That makes troubles with YaST packages as we also own that directory, this creates a conflict [1]. One possibility is to change the %{yast_icondir} macro to point to /usr/share/icons/hicolor, see [2]. All YaST packages install the icons to the "hicolor" subdirectory so this is a pretty safe change. The advantage is that this fix is trivial (only one package affected), the disadvantage is that the problem is just moved one level down, in the future the same problem might appear with the "hicolor" subdirectory. But that "hicolor" is owned by more than 270 packages (excluding YaST) so they will not hurry with that change... Dirk suggested a better solution, fix the spec files of the YaST packages so the %{yast_icondir} is not owned, see example [3]. This example also fixes the same problem with the sysconfig fillup templates. The advantage is that this is a future proof change, the disadvantage is that we will need to update many spec files. My quick grep reports more than 70 spec files... So the question is which way to go? The simple way or the more complex one that might on the other hand save some time in the future? [1] https://bugzilla.suse.com/show_bug.cgi?id=1186066 [2] https://github.com/yast/yast-devtools/pull/161 [3] https://github.com/yast/yast-bootloader/pull/642 -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

2 1