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

[yast-devel] Hack Week report: learn Crystal by porting part of YaST to that language
by Ancor Gonzalez Sosa 13 Feb '20

13 Feb '20

During this Hack Week I wanted to experiment with Crystal doing something concrete. See more details at [1] and [2]. Josef Reidinger joined the project as well. So first, the TLDR; 1) We migrated quite some non-trivial code from Ruby to Crystal. Porting Ruby+RSpec code to Crystal+Spectator was surprisingly smooth. 2) No, we don't have benchmarks to show the memory consumption or speed improvement of the migrated code. 3) Then we tried to create Crystal bindings for libstorage-ng (a library written in C++). The experience was not that good, we failed. 4) I have been asked, so you plan to port YaST to Crystal? The answer is no. Crystal is a great language but the ecosystem is far from the level of maturity needed for a multi-platform LTSS system. Now the long version... For those who don't know what Crystal is. It's a statically type-checked programming language that compiles into very efficient native code, while looking very similar to Ruby. It has a VERY similar syntax (although compatibility with it is not a goal) and a very similar approach to object oriented programming (at least, in the part of it everyone uses in a daily basis). So back to (1). Porting code from Ruby to Crystal is often as simple as: mv class.rb class.cr Yes, really. It's surprisingly easy. Although Crystal is statically type-checked, the compiler does a great job in inferring the types for everything. That, together with union types and null reference checks, makes everything really smooth. But we wanted to challenge the language, so the code we ported included many things I expected to be tricky to migrate, like defining operators, using metaprogramming to add new class methods to the native numeric classes, using Ruby's "const_get" to decide during runtime which exact class to instantiate, using Ruby's "send" with a variable number of arguments, defining and using mixins, holding references to objects that could be of several classes with no common ancestor... Some of those things just worked as-is in Crystal. With no change needed. All the others were easy to implement using macros. Macros are Crystal's answer to metaprogramming and they are a really powerful tool. The approach is very different to Ruby metaprogramming, so this is the part where a simple rename of the file or even some semi-advanced automatic conversion wouldn't be enough to migrate. But macros definitely look powerful enough to solve most of the things we currently solve with metaprogramming in Ruby. Another nice surprise. But we also wanted to port the RSpec testsuite. A testsuite that makes good use of contexts, "let", mocking and stubbing. That is, things like this: describe Y2Storage::AutoinstIssues::List do subject(:list) { described_class.new } let(:section) { Y2Storage::AutoinstProfile::SkipListSection.new } let(:issue) { instance_double(Y2Storage::AutoinstIssues::Exception) } describe "#add" do it "adds a new issue to the list" do list.add(:exception, StandardError.new) expect(list.to_a) .to all(be_an(Y2Storage::AutoinstIssues::Exception)) end it "passes extra arguments to issue instance constructor" do expect(Y2Storage::AutoinstIssues::InvalidValue) .to receive(:new).with(section, :size, "value") list.add(:invalid_value, section, :size, "value") end end end Thanks to Spectator, this turned to also be almost a matter of renaming the file. See the Crystal equivalent: Spectator.describe Y2Storage::AutoinstIssues::List do subject(:list) { described_class.new } let(:section) { Y2Storage::AutoinstProfile::SkipListSection.new } mock Y2Storage::AutoinstIssues::InvalidValue do stub self.new(*args) end describe "#add" do it "adds a new issue to the list" do list.add(:exception, NilAssertionError.new) expect(list.to_a) .to all(be_an(Y2Storage::AutoinstIssues::Exception)) end it "passes extra arguments to issue instance constructor" do expect(Y2Storage::AutoinstIssues::InvalidValue) .to receive(:new).with(section, :size, "value") list.add(:invalid_value, section, :size, "value") end end end Almost identical, isn't it? In short, the experience in migrating code and tests could hardly be better. Now let's skip the second point and jump to (3) - creating bindings for libstorage-ng. The experience there was not that good. We only found one usable generator of C++ bindings for Crystal[3]. It's being currently used to create Qt5 bindings, but is the typical project that relies on a single person which has a single use-case (the mentioned Qt5 bindings). It almost works for the general case, so it could really be a perfect tool with some investment from other sources other than his current only developer. But is still not there. And no, Swig[4] does not support Crystal as output language. Looking at the Crystal code generated by bindgen and at the Ruby code generated by Swig, implementing Swig support for Crystal would be doable, but I don't think there is anyone even trying right now. Which leads us directly to (4). After a week of playing with Crystal I clearly see it is a perfect language to migrate away from the Ruby runtime. The language retains many of the nice things we love from Ruby and it adds some extra goodies. And porting Ruby code to it is a pleasure. If the YaST Team managed to migrate from YCP to Ruby, doing it from Ruby to Crystal would be 20 times easier. But YaST is not a simple project that has to run in a limited set of servers. We must be able to ship a product that can be executed in x86, PowerPC, s390, ARM and whatnot. And we need to be sure the tool used to generate C++ bindings is properly maintained for the following X years. We also need to feel that in the future we will be able to find a library for whatever task (parsing a new file format, for example). In short, we need solid ground to be able to provide LTSS support for something written in Crystal. All that will not happen without a sustained investment in the language itself. Since I don't see SUSE hiring two people to work full-time in Crystal and its ecosystem for the following couple of years, I wouldn't advise any project that needs to be shipped in SLE to migrate from Ruby to Crystal. But for smaller projects that only need to run in a controlled environment... give it a try! EOREPORT [1] https://hackweek.suse.com/projects/learn-crystal-by-porting-part-of-yast-to… [2] https://github.com/ancorgs/y3storage [3] https://github.com/Papierkorb/bindgen [4] http://www.swig.org/ -- Ancor González Sosa YaST Team at SUSE Software Solutions -- 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] YaST logs permissions
by David Díaz 10 Feb '20

10 Feb '20

Hi! Recently, we have been asked to change the save_y2logs generated file permissions[1] because it's only readable by root, which causes troubles[2] when trying to upload it elsewhere as a common user. However, this is not possible because generated logs contain sensitive information like configuration of services, the content of the journal, or firewall configuration. Adding a short explanation in the command output about the need to adjust the permissions when you are going to upload the file could help the user to understand what's going on, but seems to not be enough. The user should also be aware that logs might contain sensitive data and keep them safe. How do you think we could improve that situation? Regards. [1] https://github.com/yast/yast-yast2/issues/978 [2] https://en.opensuse.org/openSUSE:Report_a_YaST_bug#Firefox_fails_to_attach_… -- David Díaz González YaST Team at SUSE Linux GmbH

5 8

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

10 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 (240 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (207 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-country: - Port to rake (207 days) https://github.com/yast/yast-country/pull/217 Pending requests in repository yast-devtools: - Supplement changes from YCC (12 days) https://github.com/yast/yast-devtools/pull/148 - Move desktop files (245 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-installation: - Demo: eager mode of zombie-killer 0.5 (458 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - network-ng: test cases document (draft) (80 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (206 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (107 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-pkg-bindings: - Remove legacy zypp::target::rpm::ConvertDBReport (61 days) https://github.com/yast/yast-pkg-bindings/pull/119 Pending requests in repository yast-python-bindings: - Make python2 binding optional due to its removal (31 days) https://github.com/yast/yast-python-bindings/pull/31 Pending requests in repository yast-squid: - packaging: remove SuSEfirewall2 artifacts (198 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 (41 days) https://github.com/yast/yast-sudo/pull/12 Pending requests in repository yast-users: - Move back the UMASK default value to /etc/login.defs (bsc#1099153) (585 days) https://github.com/yast/yast-users/pull/161 Pending requests in repository yast-yast2: - Change the way groups are defined (244 days) https://github.com/yast/yast-yast2/pull/936 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (375 days) https://github.com/yast/yast-yast2/pull/894 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (375 days) https://github.com/yast/yast-yast2/pull/893 - [WIP] Firewalld fixes for the new UI (523 days) https://github.com/yast/yast-yast2/pull/813 - [WIP] Drop SuSEfirewall2 completely (508 days) https://github.com/yast/yast-yast2/pull/806 Pending requests in repository yast-ycp-ui-bindings: - [WIP] Support bold font inside tables (535 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 (38 days) https://github.com/yast/yast-ruby-bindings/pull/224 - log method name (622 days) https://github.com/yast/yast-ruby-bindings/pull/216 Pending requests in repository yast-samba-client: - Use kerberos authentication by default during join (88 days) https://github.com/yast/yast-samba-client/pull/79 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] YaST: highlights of development sprint 93
by Imobach González Sosa 07 Feb '20

07 Feb '20

Hi all, Lately, the YaST team has been quite busy fixing bugs and finishing some features for the upcoming (open)SUSE releases. Although we did quite some things, in this report we will have a closer look at just a few topics: - A feature to search for packages across all SLE modules has arrived to YaST. - Improved support for S390 systems in the network module. - YaST command-line interface now returns a proper exit-code. - Added progress feedback to the Expert Partitioner. - Partial support for Bitlocker and, as a lesson learned from that, a new warning about resizing empty partitions. You can find the whole report at https://lizards.opensuse.org/2020/02/07/yast-sprint-93/ Enjoy the Hack Week! -- Imobach González Sosa YaST Team at SUSE LLC https://imobachgs.github.io/

1 0

[yast-devel] YaST at the openSUSE Summit Dublin
by Ancor Gonzalez Sosa 07 Feb '20

07 Feb '20

Douglas DeMaio asked if me or any other YaST developer was planning to give a talk at openSUSE Summit Dublin[1]. I have to admit that was out of my radar. That summit is a small event that takes place right after SUSECON[2] in the same location, reusing part of its infrastructure. So it sounds like a nice place to meet people who are both openSUSE enthusiasts and SUSE customers. To be honest, YaST had almost not presence In the latest openSUSE Conference and that felt pretty wrong. Imo and me tried to fix that with some lighting talks but, although they were well received locally, there is no online record of those. I'm not sure whether I will be personally able to attend, but I think that at least one member of the YaST Team should be there presenting all the new stuff that debuted in 15.1 (we can extend my lighting talk about it) or what we are working on. Being visible is one of our strategies, after all. Cheers. [1] https://events.opensuse.org/conferences/Dublin [2] https://www.susecon.com/ -- 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 4

[yast-devel] Fwd: openSUSE - Google Summer of Code 2020
by Ancor Gonzalez Sosa 05 Feb '20

05 Feb '20

openSUSE is considering to apply for Google Summer of Code this year. We offered some projects in the past, some of them were indeed executed([1],[2]). [1] Alternatives YaST Module https://github.com/openSUSE/mentoring/issues/13 [2] Rewrite Keyboard Management - Done out of GSoC https://github.com/openSUSE/mentoring/issues/79 Others never made it to GSoC for several reasons, although some of them were finally implemented by the YaST Team itself ([3],[4],[5]) [3] REST API for testing based on libYUI https://github.com/openSUSE/mentoring/issues/87 [4] Apache initial setup YaST Module https://github.com/openSUSE/mentoring/issues/12 [5] Native Ruby interface for libYUI https://github.com/openSUSE/mentoring/issues/11 Time to resurrect any of those projects or come with a new one? Anyone willing to mentor? I am, although I have not decided the project yet. Cheers. PS.- It doesn't have to be exactly about YaST, we have had projects in the past about Jangouts, One-click installer, the Travel Support Program application.... https://github.com/openSUSE/mentoring/issues/63 https://github.com/openSUSE/mentoring/issues/78 https://github.com/openSUSE/mentoring/issues/80 https://github.com/openSUSE/mentoring/issues/82 https://github.com/openSUSE/mentoring/issues/16 https://github.com/openSUSE/mentoring/issues/77 https://github.com/openSUSE/mentoring/issues/15 -------- Forwarded Message -------- Subject: [Research] openSUSE - Google Summer of Code 2020 Date: Mon, 27 Jan 2020 10:00:18 +0100 From: ddemaio To: ----- Hi All, Applications for the Google Summer of Code are open and openSUSE members are considering applying for this year's GSoC to be a mentor organization. You would need to be committed to providing a mentor and the mentors would need to write progress reports; I believe there are 2 reports the mentors must write (mid-term review and final review) in addition to the mentoring of the student. The application deadline is Feb. 5, so if you want to do this, please update the git repository (https://github.com/openSUSE/mentoring) for https://101.opensuse.org and I can submit the application. If you have a project that you would like to consider as a GSoC project, please let me know. v/r Doug -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

4 10

[yast-devel] Inconsistent behavior of YaST Modules when closing without changes
by Ancor Gonzalez Sosa 03 Feb '20

03 Feb '20

This started as a discussion in https://bugzilla.suse.com/show_bug.cgi?id=1161460 which leads me to realize we have the same "hack" repeated in dozens of YaST modules. The point is that there is a function called `Popup::ReallyAbort` that all YaST modules call when asked to quit. The only argument of that function is a boolean saying whether something has changed. If nothing has changed, the function displays a "Really abort?" pop-up. But if some change has been made (i.e. the argument is true), it will add "All changes will be lost!" So we have a common API used by all modules to show a consistent behavior. So far, so good... Or not? Of course, not. This was surely conceived to be used like this: Popup.ReallyAbort(TheModule.modified?) But in practice most modules (all except 4 or 5, as far as I can say) use that function like this: def ReallyAbort !TheModule.modified? || Popup.ReallyAbort(true) end Which actually invalidates the logic of the function and simply shows nothing when quiting without changes. And that very same code is repeated over and over in a dozen of YaST modules. See [1]. Did we at some point decided that quiting without changes should not ask for confirmation? If so, why did we implement the very same bypass for the `Popup.ReallyAbort` logic in dozens of modules instead of changing the behavior of the function (or providing an alternative function)? We should agreed on which is the desired behavior and then implement it by using whatever common function (ReallyAbort or a new one) in an honest way. I created a card for that[2] but I wanted to start the discussion here first. Cheers [1] https://github.com/search?q=org%3Ayast+reallyabort&type=Code [2] https://trello.com/c/UlVLiDTU/ -- Ancor González Sosa YaST Team at SUSE Software Solutions -- 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] Pending Pull Requests
by yast-ci＠opensuse.org 03 Feb '20

03 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 (233 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (200 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-country: - Port to rake (200 days) https://github.com/yast/yast-country/pull/217 Pending requests in repository yast-devtools: - Move desktop files (238 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-installation: - Demo: eager mode of zombie-killer 0.5 (451 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - network-ng: test cases document (draft) (73 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (199 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-online-update-configuration: - Prompt for root password. (292 days) https://github.com/yast/yast-online-update-configuration/pull/21 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (100 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-pkg-bindings: - Remove legacy zypp::target::rpm::ConvertDBReport (54 days) https://github.com/yast/yast-pkg-bindings/pull/119 Pending requests in repository yast-python-bindings: - Make python2 binding optional due to its removal (24 days) https://github.com/yast/yast-python-bindings/pull/31 Pending requests in repository yast-squid: - packaging: remove SuSEfirewall2 artifacts (191 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 (34 days) https://github.com/yast/yast-sudo/pull/12 Pending requests in repository yast-users: - Move back the UMASK default value to /etc/login.defs (bsc#1099153) (578 days) https://github.com/yast/yast-users/pull/161 Pending requests in repository yast-yast2: - Change the way groups are defined (237 days) https://github.com/yast/yast-yast2/pull/936 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (368 days) https://github.com/yast/yast-yast2/pull/894 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (368 days) https://github.com/yast/yast-yast2/pull/893 - [WIP] Firewalld fixes for the new UI (516 days) https://github.com/yast/yast-yast2/pull/813 - [WIP] Drop SuSEfirewall2 completely (501 days) https://github.com/yast/yast-yast2/pull/806 Pending requests in repository yast-ycp-ui-bindings: - [WIP] Support bold font inside tables (528 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 (31 days) https://github.com/yast/yast-ruby-bindings/pull/224 - log method name (615 days) https://github.com/yast/yast-ruby-bindings/pull/216 Pending requests in repository yast-samba-client: - Use kerberos authentication by default during join (81 days) https://github.com/yast/yast-samba-client/pull/79 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