January 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

Pending Pull Requests
by yast-ci＠opensuse.org 31 Jan '22

31 Jan '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-country: - Unify YaST module mocking in unit tests (9 days) https://github.com/yast/yast-country/pull/289 Pending requests in repository yast-devtools: - Set %yast_icondir to /usr/share/icons/hicolor (bsc#1186066) (186 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-s390: - S390 formatting progress dialog improvements (6 days) https://github.com/yast/yast-s390/pull/93 Pending requests in repository yast-sound: - Fix module filename matching (jsc#SLE-21256). (41 days) https://github.com/yast/yast-sound/pull/53 Pending requests in repository yast-theme: - Add pantheon desktop support (61 days) https://github.com/yast/yast-theme/pull/154 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (118 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository yast-sap-ha: - SUSE SAP HA Yast wizard for HANA doesn´t configure the HANA hooks. (48 days) https://github.com/yast/yast-sap-ha/pull/7

1 0

[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

Heads-up: SUSEConnect-ng is included in SP4
by Imobach Gonzalez Sosa 25 Jan '22

25 Jan '22

Hi all, While working on a P1[1], I found out that the SP4 inst-sys already ships SUSEConnect-ng (the new Go-based version). So we should have that into account when dealing with registration bugs and contact the SCC team if something does not work as we expected. Regards, Imo [1] https://bugzilla.suse.com/show_bug.cgi?id=1194989#c7 -- Imobach González Sosa YaST Team at SUSE LLC https://imobachgs.github.io/

3 6

Pending Pull Requests
by yast-ci＠opensuse.org 24 Jan '22

24 Jan '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) (179 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-sound: - Fix module filename matching (jsc#SLE-21256). (34 days) https://github.com/yast/yast-sound/pull/53 Pending requests in repository yast-theme: - Add pantheon desktop support (54 days) https://github.com/yast/yast-theme/pull/154 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (111 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository skelcd-control-MicroOS: - Add bootloader pattern for all roles (51 days) https://github.com/yast/skelcd-control-MicroOS/pull/44 - keylime: remove ALPHA tag (59 days) https://github.com/yast/skelcd-control-MicroOS/pull/43 Pending requests in repository yast-sap-ha: - SUSE SAP HA Yast wizard for HANA doesn´t configure the HANA hooks. (41 days) https://github.com/yast/yast-sap-ha/pull/7

1 0

RSpec verifying doubles and better YaST module mocking
by Ladislav Slezák 21 Jan '22

21 Jan '22

Hi! I have enabled RSpec verifying doubles in all remaining YaST unit tests where they were not used. The advantage is that RSpec checks that the mocked methods really exist in the original class. Without it if you make a typo in a method call in the code and make the same typo in the unit test mock then the test will pass but the code will actually crash at run time. So ideally we should enable this feature everywhere. But in the YaST unit test we quite often replace some YaST modules with an empty class to avoid too long or cyclic build dependencies. If you mock an YaST module completely then you have the same problem back as the dummy methods are really defined there so even RSpec verifying doubles will not catch the problems there. To use advantages from the both worlds I have created a new Yast::RSpec::Helpers.define_yast_module helper method. [1] It tries to load the requested YaST module via the usual YaST.import call. If that fails then it defines a dummy replacement for it. So if the module is present in the system, like when you run the unit tests locally on your machine or when running in GitHub Actions where most of the modules are present, then it will load the real modules and the verifying doubles will fully work. In RPM build it will create dummy modules and the build dependencies can be avoided. Examples: # defined here, needs yast2-ruby-bindings >= 4.4.7 require "yast/rspec" # if you do not mock the module methods in the tests you can use # this simple variant Yast::RSpec::Helpers.define_yast_module("AutoInstall") # if you mock some methods then they must be defined in the mocked class # so the verifying doubles check does not fail Yast::RSpec::Helpers.define_yast_module("Profile", methods: [:current]) # note: for simplification all mocked methods accept any number of parameters, # the real parameters should be verified when running against the real modules # you can also pass a block which is evaluated in the context of the created class # so you can define some defaults, in theory you could define also some logic there # but I'd avoid it, the mocked logic might easily go out of sync with the real module Yast::RSpec::Helpers.define_yast_module("Language") do def language # the default "en_US" end end Then if you run "rake test:unit" locally the modules will be loaded from system when found. If you want to force creating the mocked modules even when they are present in the system then just set the YAST_FORCE_MODULE_STUBS environment variable, e.g.: YAST_FORCE_MODULE_STUBS=1 rake test:unit This is useful if you want to test locally how it will work in RPM build, whether your mocks implement all the methods used in the tests. You can check some real examples in [2] and [3]. And interestingly enabling verifying doubles found a real bug in the code! [4] Enjoy! Ladislav [1] https://github.com/yast/yast-ruby-bindings/pull/281 [2] https://github.com/yast/yast-bootloader/pull/663/files [3] https://github.com/yast/yast-network/pull/1278/files [4] https://github.com/yast/yast-installation/pull/1013/files#diff-05183469b1a0… -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

1 0

Announcing the D-Installer project
by Imobach Gonzalez Sosa 18 Jan '22

18 Jan '22

Hi all, During 2021, the YaST team was playing with the idea of building a web- based installer using our libraries. Finally, we have decided to define the project and try to invest some CPU cycles on it. 🙂 Please, read the announcement in our blog and do not hesitate to share your point of view with us. https://yast.opensuse.org/blog/2022-01-18/announcing-the-d-installer-project Regards, Imo -- Imobach González Sosa YaST Team at SUSE LLC https://imobachgs.github.io/

1 0

Pending Pull Requests
by yast-ci＠opensuse.org 17 Jan '22

17 Jan '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) (172 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-sound: - Fix module filename matching (jsc#SLE-21256). (27 days) https://github.com/yast/yast-sound/pull/53 Pending requests in repository yast-theme: - Add pantheon desktop support (47 days) https://github.com/yast/yast-theme/pull/154 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (104 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository skelcd-control-MicroOS: - Add bootloader pattern for all roles (44 days) https://github.com/yast/skelcd-control-MicroOS/pull/44 - keylime: remove ALPHA tag (52 days) https://github.com/yast/skelcd-control-MicroOS/pull/43 Pending requests in repository yast-sap-ha: - SUSE SAP HA Yast wizard for HANA doesn´t configure the HANA hooks. (34 days) https://github.com/yast/yast-sap-ha/pull/7

1 0

Empty testing RPM repository
by Ladislav Slezák 14 Jan '22

14 Jan '22

Hello! I created an empty testing RPM repository [1] which might be easily used in some tests. Advantage of an empty repository is that it cannot affect the installed packages or cause any conflicts. It can be also used with any product in any version. The most important feature of this particular repository is that it is signed by the official SUSE GPG keys! So YaST or zypper will not complain about unknown or missing GPG signatures and it can be easily used in automated tests. Enjoy! :-) Ladislav [1] https://github.com/lslezak/empty_repo -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

1 0

Updated YaST GitHub Actions
by Ladislav Slezák 12 Jan '22

12 Jan '22

Hi all! I have added another Docker image into the YaST:Head OBS project. It's a Ruby image based on Leap 15.4. The reason is that Leap 15.4 contains Ruby 2.5 (just like SLE), the original image based on Tumbleweed contains Ruby 3.0 now (3.1 soon...). The goal is to run CI using both images so we can be sure the YaST packages work properly in both Tumbleweed and SLE/Leap. Another goal is to run Rubocop and Yardoc in the Ruby 2.5 image as they do not work properly in Ruby 3.x. I have adapted all YaST repositories which use our Ruby Docker image in the GitHub Actions. See [1] as an example. Notes: - Only the unit tests and package build jobs run in both images, the rest (Rubocop, Yardoc, ...) run in just one image, that should be enough. - Code coverage is sent only from the Tumbleweed build to avoid race conditions and possibly inconsistent results. - The YAML files were automatically patched by a script (in 120 Git repositories!) but I did a manual review of each change and did some manual tweaks in some cases (e.g. it does no make sense to build the TW control file in Leap, or the other way round, the SLES control file does not make sense to build in TW). - If you think some builds or some changes do not make sense, or the other way round, something is missing feel free to fix that. The config is not set in a stone. :-) If you have any questions just ping me. Enjoy! Ladislav [1] https://github.com/yast/yast-autoinstallation/commit/a50cf8e2455342ccef96d5… -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

1 0

[yast-devel][installation] Next button background color looks wrong (too light)
by Felix Miata 12 Jan '22

12 Jan '22

15.4 Alpha This has been going on too many releases to remember when it started. The FG/BG contrast on the (active) Next button is low. The BG color seems lighter than the what appears should be the matching color elsewhere. It might not seem so if only the FG was #FFF or #000 instead of gray. It seems as if the Next button is colored to indicate something else needs to be done before it can be selected to proceed. The other buttons' dark gray on light gray seems could stand to have improved contrast too. More contrast should help make up for fuzziness on lower resolution screens. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

2 1

Fwd: openSUSE - Google Summer of Code 2022
by Ancor Gonzalez Sosa 12 Jan '22

12 Jan '22

Now that we are toying with the idea of yastd and a web interface to it, maybe we have a mentorship opportunity there. Cheers. -------- Forwarded Message -------- Subject: openSUSE - Google Summer of Code 2022 Date: Tue, 11 Jan 2022 17:06:41 +0100 From: ddemaio <ddemaio(a)suse.de> To: research(a)suse.de Hi All, Applications for mentor organizations for the Google Summer of Code 2022, will be from February 7 - 21, 2022. The openSUSE Project has a long history of participating as a mentor organization, and we hope to do so again this year! If you are interested in mentoring for your open source project, please let us know so that we can come up with a list of interested mentors, and can move forward with our application. As a mentor you would be committed to actively mentoring a student(s) if/when openSUSE becomes selected as an organization.This would involve keeping the student(s) on task, actively communicating with them and writing progress reports; there are 2 reports that mentors must write (a midterm and final review). The timeline for GSoC can be found at https://developers.google.com/open-source/gsoc/timeline <https://developers.google.com/open-source/gsoc/timeline>, along with other relevant information on roles and responsibilities for both mentors and students. If there are enough interested mentors to proceed with an application, which we will let you know ASAP, potential mentors would need to update the git repository (https://github.com/openSUSE/mentoring <https://github.com/openSUSE/mentoring>) for https://101.opensuse.org <https://101.opensuse.org>, so that we can submit the application. If you have any questions, please let us know. v/r Doug

1 0

Improve given information in crash popups
by David Díaz 10 Jan '22

10 Jan '22

Hi folks! Related to [1], I'd like to update error messages where YaST suggest the user filling a bug report because some of them[2][3] does not include the hint about collection logs with save_y2logs command. What do you think? Is there any reason for keeping them as they are? Do you have any other proposal? Do you think is there any other place where save_y2logs deserves to be mention? Thank you! [1] https://bugzilla.suse.com/show_bug.cgi?id=1194342#c4 [2] https://github.com/yast/yast-yast2/blob/8c6f0fe1d8b82da1c76d227defa2cd44781… [3] https://github.com/yast/yast-yast2/blob/8c6f0fe1d8b82da1c76d227defa2cd44781… -- David Díaz YaST Team at SUSE LINUX GmbH IRC: dgdavid

5 4

Pending Pull Requests
by yast-ci＠opensuse.org 10 Jan '22

10 Jan '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-country: - WIP: First very rough table extension for new keymaps (25 days) https://github.com/yast/yast-country/pull/288 Pending requests in repository yast-devtools: - Set %yast_icondir to /usr/share/icons/hicolor (bsc#1186066) (165 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-sound: - Fix module filename matching (jsc#SLE-21256). (20 days) https://github.com/yast/yast-sound/pull/53 Pending requests in repository yast-theme: - Add pantheon desktop support (40 days) https://github.com/yast/yast-theme/pull/154 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (97 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository skelcd-control-MicroOS: - Add bootloader pattern for all roles (37 days) https://github.com/yast/skelcd-control-MicroOS/pull/44 - keylime: remove ALPHA tag (45 days) https://github.com/yast/skelcd-control-MicroOS/pull/43 Pending requests in repository yast-sap-ha: - SUSE SAP HA Yast wizard for HANA doesn´t configure the HANA hooks. (27 days) https://github.com/yast/yast-sap-ha/pull/7

1 0

new rubocop and new config for it
by josef Reidinger 09 Jan '22

09 Jan '22

Hi, Short Version ------------- New rubocop in testing. New shared config is done and also demonstrated on three example modules. Speak now or complain later. PR with new shared rubocop including reasoning: https://github.com/yast/yast-devtools/pull/163 PR with adaptation of picked modules: - https://github.com/yast/yast-storage-ng/pull/1278 - https://github.com/yast/yast-yast2/pull/1230 - https://github.com/yast/yast-bootloader/pull/660 Long Version and Observations ----------------------------- Why === TW now uses ruby 3.0 and will be soon using 3.1. The bad part is that our ancient versions of rubocop does not work with new ruby. So we had two options either patch old rubocop or adapt to new one. After discussion we decide for the second option as even our older version had problem with some ruby 2.3 syntax. Observations ============ - new rubocop has safe and unsafe auto corrections. --auto-correct do only safe ones. -A does both. It is useful when doing adaptation as I usually do safe first and then carefully review rest of changes done by -A - rubocop --only is useful to fix just set of cops if you have huge list of issues. I do it, when I want to do manual cops one per commit - redundant branch cop has issue with some workflow encoded in elsifs..as two branches looks identical, but it is under chain of previous condition . In general problem mainly in uterly old ugly code and it is quite rare - similar issue applies to new combinable loops cop. As a loop can modify itself or order is important like in this case of storage-ng https://github.com/yast/yast-storage-ng/pull/1278/commits/e1d9020409409f0b5… - new cop to check if important methods like constructor call super is quite useful and reveal some real bugs in storage-ng code ( like using nil as widget ID for Empty object ). I think majority of issues needs fix in https://github.com/yast/yast-storage-ng/pull/1278/commits/14ca4c6f4544362d5… as trivial fix was not enough and I overlook it at first. - also Lint/DuplicateElsifCondition find real bug in yast2 - https://github.com/yast/yast-yast2/pull/1230/commits/6866413d9fdfc94619d823… So please comment in pull request or directly as answer here to email. I think quick discussion can happen on review meeting. Josef

1 0

Ruby FFI using Fiddle (calling native functions from Ruby directly)
by Ladislav Slezák 07 Jan '22

07 Jan '22

Hi all! You probably know the "ffi" gem (this is what you get if you google for "ruby ffi"), but I accidentally found out an alternative implementation called "fiddle". The advantage is that this library is a part of the Ruby stdlib so you do not need to depend on any external gem. And it is even included in Ruby 2.5, so it is already part of SLE15... It also provides a simple wrapper for accessing the functions from Ruby similar to the ffi gem. I wrote a simple example which sorts strings using the current locale (that's not possible in standard Ruby) and uses the strcoll() glibc function. The nice thing is that it can directly parse the C function signatures, so you can just use "man strcoll" and copy and paste the signature to Ruby: dlload "libc.so.6" extern "int strcoll(char*, char*)" ...and that's it! See the full example at https://github.com/lslezak/scripts/blob/master/misc/locale_sorter.rb This might be useful if you ever need some low-level system call in Ruby. Notes: As this internally uses dlopen() for opening the *.so libraries then obviously you cannot use the constants and macros defined in the *.h header files. That might complicate things in some cases... You might open also a C++ library, e.g. zypp = Fiddle.dlopen("libzypp.so") works fine, but the problem is that C++ uses method name mangling and working with objects would be difficult. So in practice this is limited to some simple plain C libraries, but it still might be useful as you do not need to write any line of C code and you do not even need a compiler... Ladislav -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

2 2

New debugger in Ruby 3.1
by Ladislav Slezák 06 Jan '22

06 Jan '22

Hello, Currently we use the "byebug" Ruby debugger [1] in YaST [2], however the latest Ruby 3.1 includes [3] a new debugger "debug" [4] in the standard library. I have quickly checked the provided features and it seems it provides the same features as the byebug gem, including the remote debugging which is necessary for YaST. (We need to run the debugger frontend in a different process because it cannot use the current terminal if it is used by the ncurses UI or not available at all like in an VNC installation.) Byebug works fine with Ruby 3.1 but in the long term we should switch to the standard debugger to avoid external dependency. The new debugger is actually a standard Ruby gem, I thought we could backport it to SLE so we could use only one implementation consistently. Unfortunately it needs Ruby version 2.6 or higher so that's not possible. :-( So my plan is to spend some innovation time later and use either "byebug" or "debug" debugger in YaST depending on what is currently available. If you are interested in this and would like to join then just ping me... Ladislav [1] https://github.com/deivid-rodriguez/byebug [2] https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/debugg… [3] https://www.ruby-lang.org/en/news/2021/12/25/ruby-3-1-0-released/ [4] https://github.com/ruby/debug -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

3 2

Pending Pull Requests
by yast-ci＠opensuse.org 03 Jan '22

03 Jan '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-country: - WIP: First very rough table extension for new keymaps (18 days) https://github.com/yast/yast-country/pull/288 Pending requests in repository yast-devtools: - Set %yast_icondir to /usr/share/icons/hicolor (bsc#1186066) (158 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-sound: - Fix module filename matching (jsc#SLE-21256). (13 days) https://github.com/yast/yast-sound/pull/53 Pending requests in repository yast-theme: - Add pantheon desktop support (33 days) https://github.com/yast/yast-theme/pull/154 Pending requests in repository yast-samba-client: - Don't call 'net' with '-U%' boo#1193533 (16 days) https://github.com/yast/yast-samba-client/pull/91 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (90 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository yast-storage-ng: - Added YaST Console checkbox for enabling LUKS2 support (10 days) https://github.com/yast/yast-storage-ng/pull/1260 Pending requests in repository skelcd-control-MicroOS: - Add bootloader pattern for all roles (30 days) https://github.com/yast/skelcd-control-MicroOS/pull/44 - keylime: remove ALPHA tag (38 days) https://github.com/yast/skelcd-control-MicroOS/pull/43 Pending requests in repository yast-sap-ha: - SUSE SAP HA Yast wizard for HANA doesn´t configure the HANA hooks. (20 days) https://github.com/yast/yast-sap-ha/pull/7

1 0