March 2020 - YaST Development - openSUSE Mailing Lists

Re: [yast-devel] SLE-15-SP2 branching
by Lukas Ocilka 24 Mar '20

24 Mar '20

Dne 24. 03. 20 v 18:49 Arvin Schnell napsal(a): > I am working on SP2 so I suggest to still wait with creating the > branch. I'm afraid that most of the developers still work on SP2 fixes, but the point is that some (even the same ones) already started or want to start (or even have to start) working on new products. We can't really wait till SLE 15 SP2 is out. Or did I understand something incorrectly? Thx Lukas -- Lukas Ocilka, Systems Management Team Leader & YaST Product Owner SLE Department, SUSE Linux 🌲 Please consider the environment before printing this e-mail ☂ Handle with care - Your reply can be stored in the cloud 😱 Pie-chart is just a representation of randomly chosen data ⚠ IMPORTANT: The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email by mistake, please, notify the sender immediately and do not disclose the contents to anyone or make copies of thereof. -- 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] VirtualBox: Using Shared Folders for Development
by Stefan Hundhammer 23 Mar '20

23 Mar '20

Since nobody on our IRC channel seemed to know this and it took me quite a while to figure out, I thought I'd write this up for the benefit of others: I wanted to use a shared folder in a VirtualBox Linux VM where I can edit source files on my host system, yet build inside the VM with a well-defined development environment. By default, VirtualBox uses bizarre permissions that won't let you do very much; but that can be hammered into shape to become useful: https://github.com/shundhammer/huha-linux-tips/blob/master/doc/virtualbox-t… Kind regards -- Stefan Hundhammer <shundhammer(a)suse.de> YaST Developer SUSE Linux GmbH GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg) -- 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 23 Mar '20

23 Mar '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 (282 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (249 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-core: - Fixes for gensalt handling with libxcrypt. (24 days) https://github.com/yast/yast-core/pull/144 Pending requests in repository yast-country: - Port to rake (249 days) https://github.com/yast/yast-country/pull/217 Pending requests in repository yast-devtools: - Y2logs analyzer (26 days) https://github.com/yast/yast-devtools/pull/149 - Supplement changes from YCC (54 days) https://github.com/yast/yast-devtools/pull/148 - Move desktop files (287 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-installation: - Stop plymouth splash to avoid serial terminal splutter. (10 days) https://github.com/yast/yast-installation/pull/841 - Demo: eager mode of zombie-killer 0.5 (500 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - network-ng: test cases document (draft) (122 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (248 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-nis-client: - fix build requires (13 days) https://github.com/yast/yast-nis-client/pull/47 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (149 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-squid: - packaging: remove SuSEfirewall2 artifacts (240 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 (83 days) https://github.com/yast/yast-sudo/pull/12 Pending requests in repository yast-users: - Improve readme (46 days) https://github.com/yast/yast-users/pull/224 - Move back the UMASK default value to /etc/login.defs (bsc#1099153) (627 days) https://github.com/yast/yast-users/pull/161 Pending requests in repository yast-yast2: - Change the way groups are defined (286 days) https://github.com/yast/yast-yast2/pull/936 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (417 days) https://github.com/yast/yast-yast2/pull/894 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (417 days) https://github.com/yast/yast-yast2/pull/893 - [WIP] Firewalld fixes for the new UI (565 days) https://github.com/yast/yast-yast2/pull/813 - [WIP] Drop SuSEfirewall2 completely (550 days) https://github.com/yast/yast-yast2/pull/806 Pending requests in repository yast-ycp-ui-bindings: - [WIP] Support bold font inside tables (577 days) https://github.com/yast/yast-ycp-ui-bindings/pull/35 Pending requests in repository yast-ruby-bindings: - Fixes for gensalt handling with libxcrypt. (24 days) https://github.com/yast/yast-ruby-bindings/pull/239 - [WIP] Don't crash on NoMethodError when Perl is involved (80 days) https://github.com/yast/yast-ruby-bindings/pull/224 - log method name (664 days) https://github.com/yast/yast-ruby-bindings/pull/216 Pending requests in repository yast-rake: - Switch desktop directory (287 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] Innovation Time: libyui-ruby-bindings
by josef Reidinger 20 Mar '20

20 Mar '20

Hi, today I use my innovation time to check possible improvements for UI. After yesterday discussion I start with checking at first what we already have - libyui ruby bindings. It is just thin layer on top of libyui, but it is already there. As starting point I do two things that we can use to start discussion: 1. fix libyui-bindings to provide usable rpm ( do not create project yet in OBS ) - simply run `rake osc:build` to get rpm that you can install.[1] 2. try to port one real dialog. I pick very simple one because I do not want to face layers built on top of UI module and also because I expect obstacles.[2] So how it ends? libyui-bindings looks working for me in ncurses. In qt I am getting segfaults and also for examples in libyui-bindings itself. From a quick view it looks like for me again some pain with a way how we destruct objects. It need probably some expert view why it segfaulting as I do not see anything obvious using gdb or valgrind. Adapted dialog in yast2-cio ( you can try it yourself if you use manual_run directory and do some symlinking to bin as with recent secure change to drop custom PATH it does not longer works out of box ) looks reasonable simple for me. Only bigger code is for replace widget which is implemented in ycp-ui-bindings and is non-trivial operation. Maybe something to backport to libyui itself? So if you are interested please see both pull requests and try to use it yourself. And if there is qt expert, then checking why ruby bindings segfault would be useful. Josef [1] https://github.com/libyui/libyui-bindings/pull/32 [2] https://github.com/yast/yast-cio/pull/34 -- 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] yupdate - an alternative to DUD
by Ladislav Slezak 20 Mar '20

20 Mar '20

Hi all, testing fixes or new features is quite easy in an installed system, usually just running "sudo rake install" is enough for Ruby packages. However, if you need to test something in installation then the things gets more complicated. If it is just one-liner you can modify the file locally before running the installer. If it is more complicated you can build a Driver Update Disk. But that's not trivial and takes some time. You also need to somewhere publish the built DUD so the installer can download it, you need to configure an HTTP/FTP/NFS server... If you need to fix several packages it gets even more complicated. Therefore I have implemented the "yupdate" helper script which makes the modifications to inst-sys much easier. You need to start the installation with "start_shell=1" boot parameter to apply the changes before starting the installer. Documentation ============= The latest documentation is always available here: [1] https://github.com/yast/yast-installation/blob/master/doc/yupdate.md [2] https://github.com/yast/yast-rake/#server What it can do? ================ 1. Install the sources from GitHub ----------------------------------- It can install the sources directly from GitHub, just specify the GitHub repository name and the branch to apply. Run in the inst-sys: yupdate patch yast-yast2 master This will install the latest "yast2" package from the "master" branch. You can also use your fork, just use the full name including the user name like "user/yast-yast2". If the user name is missing it uses the "yast" organization by default. 2. Install from a local Git checkout ------------------------------------ Committing and pushing every single change to GitHub is a bit annoying if you are just adding debug messages or experimenting with the code. Therefore I have implemented a simple HTTP server which serves the local sources in a similar way as GitHub. Just run "rake server" in an YaST Git checkout to start it. To use the sources from your server run in the inst-sys: yupdate patch my_machine.suse.com Replace the "my_machine.suse.com" with your host name or IP address. (If the firewall is running you need to open the port for server, the [2] documentation for details.) 3. Install from multiple local Git checkouts -------------------------------------------- If you need to update several YaST packages, then just run "rake server" in each of them and use the same "yupdate" command. The HTTP server provides a simple introspection which lists all running "rake server" servers and the "yupdate" script applies the sources from each of them one-by-one. 4. Additional commands ----------------------- The "yupdate" script supports some more commands, see the documentation. I'd just mention here the "yupdate overlayfs reset" which removes all changes and resets the inst-sys to the original state. This can be useful if you mess up the inst-sys and you want to start from scratch. Notes ===== Logging ------- The "yupdate" logs to the standard y2log file so you can see there which files have been modified. When reading an y2log you can easily find out that the inst-sys was not the same as on the installation medium. Self Update ----------- After installing an update the "yupdate" script disables the YaST self-update feature because there is a conflict. If you need the self-update installed then start the installer, let the self-update proceed, abort the installation and then use the "yupdate" script. Limitations ------------ Of course, nothing is perfect so also this approach has some disadvantages: - Works only for packages which use the Rake tool for installation (it cannot work with the autotools based packages simply because the autoconf, automake and their dependencies are missing in the inst-sys) - Works only for Ruby packages (more exactly for packages which do not have any special build dependencies, e.g. do not require a C++ compiler). - Does not work for some specific packages which do some additional magic in the *.spec file after running "rake install". For example the yast-theme package does not work because of that. 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

1 0

[yast-devel] Looking for good UI API
by josef Reidinger 20 Mar '20

20 Mar '20

Hi, as tomorrow is innovation time, I would like to look to a good UI/widget API. Backend is not important, it can be even for windows UI. Also language is not important, I can get inspiration even from C# :) I mainly want some inspiration what works well and what not and also what is architecture and general ideas. API should be ideally really high level, as I would like to ideally use it for new API we use in YaST in ruby. Thanks for any tips for libraries or frameworks. Josef -- 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: highlights of development sprint 95
by Imobach González Sosa 19 Mar '20

19 Mar '20

Hi all, The YaST team has published another sprint report. Given that Lizards[1] is now considered as deprecated, we have migrated our blog to the project's website[2]. In this report, we have focused on: * New possibilities for pervasive encryption. * Improvements in the mechanism to install missing packages during storage system analysis. * Better handling of some conflicting attributes in AutoYaST. * Several usability improvements in the iSCSI LIO Server module. You can find the whole report at https://yast.opensuse.org/blog/2020-03-19/sprint-95 Regards, Imo PS: we will finish the migration of the old content as soon as possible. [1] https://lizards.opensuse.org/ [2] https://yast.opensuse.org -- Imobach González Sosa YaST Team at SUSE LLC https://imobachgs.github.io/

1 0

[yast-devel] Early detection of usr etc config files
by José Iván López González 16 Mar '20

16 Mar '20

Hi all, As you probably know, SUSE/openSUSE is moving config files from /etc to /usr/etc. This could make some YaST modules to fail, so we need to find a way to early detect when a package configured by YaST is doing such change. Right now we (YaST team) are noticed when we receive a bug report. But that approach is risky if the bug is not detected by openQA but a final user. I have described a possible solution here https://gist.github.com/joseivanlopez/bcf7185904922afae7d93f7518192864. Feedback is welcome. CU -- José Iván López González YaST Team at SUSE LINUX GmbH IRC: jilopez -- 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] Pending Pull Requests
by yast-ci＠opensuse.org 16 Mar '20

16 Mar '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 (275 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (242 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-core: - Fixes for gensalt handling with libxcrypt. (17 days) https://github.com/yast/yast-core/pull/144 Pending requests in repository yast-country: - Port to rake (242 days) https://github.com/yast/yast-country/pull/217 Pending requests in repository yast-devtools: - Y2logs analyzer (19 days) https://github.com/yast/yast-devtools/pull/149 - Supplement changes from YCC (47 days) https://github.com/yast/yast-devtools/pull/148 - Move desktop files (280 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-installation: - Demo: eager mode of zombie-killer 0.5 (493 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - network-ng: test cases document (draft) (115 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (241 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-nis-client: - fix build requires (6 days) https://github.com/yast/yast-nis-client/pull/47 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (142 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-squid: - packaging: remove SuSEfirewall2 artifacts (233 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 (76 days) https://github.com/yast/yast-sudo/pull/12 Pending requests in repository yast-users: - Improve readme (39 days) https://github.com/yast/yast-users/pull/224 - Move back the UMASK default value to /etc/login.defs (bsc#1099153) (620 days) https://github.com/yast/yast-users/pull/161 Pending requests in repository yast-yast2: - Change the way groups are defined (279 days) https://github.com/yast/yast-yast2/pull/936 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (410 days) https://github.com/yast/yast-yast2/pull/894 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (410 days) https://github.com/yast/yast-yast2/pull/893 - [WIP] Firewalld fixes for the new UI (558 days) https://github.com/yast/yast-yast2/pull/813 - [WIP] Drop SuSEfirewall2 completely (543 days) https://github.com/yast/yast-yast2/pull/806 Pending requests in repository yast-ycp-ui-bindings: - [WIP] Support bold font inside tables (570 days) https://github.com/yast/yast-ycp-ui-bindings/pull/35 Pending requests in repository yast-ruby-bindings: - Fixes for gensalt handling with libxcrypt. (17 days) https://github.com/yast/yast-ruby-bindings/pull/239 - [WIP] Don't crash on NoMethodError when Perl is involved (73 days) https://github.com/yast/yast-ruby-bindings/pull/224 - log method name (657 days) https://github.com/yast/yast-ruby-bindings/pull/216 Pending requests in repository yast-samba-client: - Master bsc1158916 (6 days) https://github.com/yast/yast-samba-client/pull/81 - Do not stop nmbd while running nmbstatus (6 days) https://github.com/yast/yast-samba-client/pull/80 - Use kerberos authentication by default during join (123 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] Time to decide on new priorities for next sprints
by Lukas Ocilka 13 Mar '20

13 Mar '20

Hi guys, Me and Ancor have been maintaining a long list of big topics, such as features, refactoring, wishes, future needs etc., but this list reflects the current situation trying to address all the needs from various sources at the time. I'd like to ask for your personal view now: What do you feel is important to do, let's say mid to long-term, and also why? To spoil the fun a bit, I'll use an example... ~~~~~ We've been postponing some refactoring in Packages/Patterns/Extensions/Add-Ons/Registration because we always felt it was going to change once more and thus it's not wort the effort of the refactoring. We've created a technical debt there. In fact, we should have done the refactoring even earlier exactly because we knew it was going to change again and again. The refactoring in this area is utterly needed to, e.g., split classes into smaller ones to have a simple responsibility, to increase the test coverage, to implement some realy object-oriented code, ... to be more flexible - prepared for changes to come (this real example has been written with a huge help from Imo and Ancor :)) ~~~~~ Obviously we already have many topics, but it's never too late to learn that there are even some more and more important just behind the corner :) Please, share your opinion. Thanks in advance Lukas -- Lukas Ocilka, Systems Management Team Leader & YaST Product Owner SLE Department, SUSE Linux 🌲 Please consider the environment before printing this e-mail ☂ Handle with care - Your reply can be stored in the cloud 😱 Pie-chart is just a representation of randomly chosen data ⚠ IMPORTANT: The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email by mistake, please, notify the sender immediately and do not disclose the contents to anyone or make copies of thereof. -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

4 3