May 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] Starting YaST modules in bash without using return
by Christian Boltz 02 Jun '20

02 Jun '20

Hello, if you have bash-completion installed, several YaST modules can be started by typing yast2 $module <tab><tab> without pressing return. Background: when pressing <tab><tab>, bash completion runs yast2 $module --help in the background to find out which commandline options are available. Affected modules: a) modules that simply get started by yast2 $module --help alternatives auth-client fonts journal krb-server ldapkrb ldap-server partitioner virt-install vpn b) modules that show a window for a second and then print the help (wrong order in the code): users samba-client samba-server c) special case nis - asks to install the "ypbind" package, then exits and prints the help. Also a case of wrong order in the code. I don't have all YaST modules installed, therefore I'd recommend that you test yourself: for mod in `yast2 -l | sed 1d` ; do echo === trying $mod yast2 $mod --help echo === done $mod echo done Can/will you fix this based on this mail, or should I open a bugreport for each affected module? Each module should at least have enough commandline handling to print This YaST2 module does not support the command line interface. (Ideally using exactly this text, because it's already translated.) Regards, Christian Boltz -- > vorweg: Hier war gerade Stromausfall. Da hat der Sturm wohl > irgendwo einen Baum auf die Leitung geworfen... > ext3 hat mich zwar anscheinend vor größeren Schäden bewahrt. Mit reiserfs stände der Baum noch. :-) [> Christian Boltz und Ratti in fontlinge-devel] -- 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] Debugging Travis - SSH Access
by Ladislav Slezak 01 Jun '20

01 Jun '20

Hi all, Travis now supports debugging builds where it enables SSH access to the running VM: https://docs.travis-ci.com/user/running-build-in-debug-mode Unfortunately, for security reasons this is not available for public repositories. And public forks cannot be simply changed to private ones... :-/ So there is a bit complicated way, you need to create a new empty repository and mirror the content from the target repository there: https://help.github.com/en/github/creating-cloning-and-archiving-repositori… Note: for accessing the private repositories at Travis you need to use the https://travis-ci.com URL, the https://travis-ci.org only displays the public GitHub repositories. When you start a debug build the VM prints the SSH command for accessing it. It does not start the build, you can do that via SSH or you can inspect the environment before running the tests... The session is running for some limited time (maybe 20 minutes? I have not measured that, but it is quite long). After a timeout the job is aborted. If you still need it you can restart the build again, just maybe you will need to repeat some steps again, just be prepared for that. HTH -- 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] New Hello World module
by David Benjamin 01 Jun '20

01 Jun '20

Per Josef Reidingers recommendation I have created a "Hello World" module. The idea is a complete working module with documentation, testing, and examples. This module then can be used as a base for a new yast-devtools script to bootstrap new module creation for beginners. I have put the files that I think should be there based on different sources. ToDo: Testing Packaging Please see: https://github.com/dwbenjamin/yast-hello-world/pull/1 Thank you for your time and help, David. -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

5 5

[yast-devel] yast-hello-world module completed first draft.
by David Benjamin 31 May '20

31 May '20

Hello, I have completed the first draft of my Hello World module: https://github.com/dwbenjamin/yast-hello-world/tree/documents Any and all feedback is welcome. This should be a complete working module and instructions for cloning to your own GitHub and OBS accounts. TODO; Documentation for Travis and Coveralls Integration. Thank you, David. -- 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 99 & 100
by Ancor Gonzalez Sosa 29 May '20

29 May '20

One hundred development sprints, that’s a nice rounded number… to write the last YaST development report. This post will be the last one following our traditional format (read the post if you want to know what the future will bring instead) and it covers several topics like: - A better editor for the "partitioning" section of AutoYaST - Improved YaST support for advanced LVM and Btrfs features - Ensuring YaST is not left behind in the migration to /usr/etc - Taking XML processing in YaST to the next level Find the whole report at https://yast.opensuse.org/blog/2020-05-29/sprint-99-100 Cheers -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] rspec testing fails
by David Benjamin 27 May '20

27 May '20

Hello, I am trying to use rake test:unit with this branch: https://github.com/dwbenjamin/yast-hello-world/tree/testing-configuration When I run rake test:unit I get an error that the test not "nil" and I don't understand why. If someone could take a minute and fix the test or tell me how I would really appreciate the help. Thanks, David. -- 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] Expert Partioner: Leap 15.3 and beyond
by Ancor Gonzalez Sosa 26 May '20

26 May '20

The interface of the YaST Partitioner has reached a point in which is really hard to deal with it. We need to find a way to move forward. As a first step, we have created this document that explains the problem and we hope it can be used as a base to discuss the future of the Partitioner interface. https://github.com/yast/yast-storage-ng/blob/master/doc/partitioner_ui.md This is a very important topic for the future of YaST. All ideas are welcome. Feel free to reply to this mail, to create pull requests for the document, to discuss the topic at #yast channel at Freenode... whatever works for you. Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

5 15

[yast-devel] Innovation Time - Videos from Conferences
by josef Reidinger 25 May '20

25 May '20

Hi, I use this friday to see some rest in published talks from conferences. This time I check some videos from RubyConf 2019. I see three of them and let me share my personal impressions. Lucky You by Sandi Metz - https://www.youtube.com/watch?v=c5WWTvHB_sA This talk was not about programming but about some history and social effects. Some topics are America specific, but in general interesting talk about real life dependencies and consequences. Containerizing Local Development... Is It Worth it? by Tony Drake - https://www.youtube.com/watch?v=NZ02hy6QOOk Very interesting talk about docker and docker-compose that allows easy to setup environment for development, even when it include some dependencies. Some ideas I have during watching this video: - we can have prepared docker image for each SLE code stream that has prepared env for schema validation using jing - we can prepare Dockerfile for some technologies that use communication with server like iscsi-client, auth-client, etc. which can significantly speed up testing of changes for that modules where we are not much familiar with technology and do not have prepared testing env as we do not touch it often - Yast usage in this env sadly looks mostly for CLI that sets up service during build or during run. Less abstract! Surprising effects of expressing rules of OOP... by Ivan Nemytchenko - https://www.youtube.com/watch?v=JH8KSPfFvxs Using some visual language to show code design. I am not much impressed by this talk and do not find it useful. I hope you find this useful. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 2

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

25 May '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 (345 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-autoinstallation: - WIP: cleanup issue handling (6 days) https://github.com/yast/yast-autoinstallation/pull/601 - Find the Base Product (20 days) https://github.com/yast/yast-autoinstallation/pull/599 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (312 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-core: - Fixes for gensalt handling with libxcrypt. (87 days) https://github.com/yast/yast-core/pull/144 Pending requests in repository yast-country: - Port to rake (312 days) https://github.com/yast/yast-country/pull/217 Pending requests in repository yast-devtools: - Y2logs analyzer (89 days) https://github.com/yast/yast-devtools/pull/149 - Supplement changes from YCC (117 days) https://github.com/yast/yast-devtools/pull/148 - Move desktop files (350 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-installation: - Demo: eager mode of zombie-killer 0.5 (563 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - WIP: cleanup issue handling (16 days) https://github.com/yast/yast-network/pull/1057 - network-ng: test cases document (draft) (185 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (311 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-online-update-configuration: - drop old testsuite and convert to rake (59 days) https://github.com/yast/yast-online-update-configuration/pull/24 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (54 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-pkg-bindings: - drop old empty testsuite (59 days) https://github.com/yast/yast-pkg-bindings/pull/127 Pending requests in repository yast-registration: - [SP3] Fix misleading default_skipping_text (BSC#1167795) (52 days) https://github.com/yast/yast-registration/pull/488 Pending requests in repository yast-schema: - [WIP] Support for optional string and map types (17 days) https://github.com/yast/yast-schema/pull/76 Pending requests in repository yast-sysconfig: - Drop old testsuite (58 days) https://github.com/yast/yast-sysconfig/pull/30 Pending requests in repository yast-users: - Move back the UMASK default value to /etc/login.defs (bsc#1099153) (690 days) https://github.com/yast/yast-users/pull/161 Pending requests in repository yast-yast2: - Test bigger Docker image at Travis (19 days) https://github.com/yast/yast-yast2/pull/1051 - Bnc#1081441 (39 days) https://github.com/yast/yast-yast2/pull/1047 - [WIP] CWM improvements (40 days) https://github.com/yast/yast-yast2/pull/1044 - Change the way groups are defined (349 days) https://github.com/yast/yast-yast2/pull/936 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (480 days) https://github.com/yast/yast-yast2/pull/894 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (480 days) https://github.com/yast/yast-yast2/pull/893 - [WIP] Firewalld fixes for the new UI (628 days) https://github.com/yast/yast-yast2/pull/813 - [WIP] Drop SuSEfirewall2 completely (613 days) https://github.com/yast/yast-yast2/pull/806 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] Hello World module review
by David Benjamin 22 May '20

22 May '20

I have made changes per recommendations from yast-devel list help. https://github.com/dwbenjamin/yast-hello-world/pull/2 I hope to have the "little" things fixed now. I am planning on using this as template on GitHub for new YaST contributors. This first iteration is intended to have a fully functioning module with documentation for beginners. As this is built I will submit documentation changes to help shorten the learning curve for new developers. TODO Write functioning test. I don't know how to do this for only a dialog box. Add header to all files, not sure what exactly it should look like. I have narrowed the licensing down to GPL 2 or 3, MIT, or Public Domain. Packaging. Desktop integration. Thank you all again for your help and your time. David. -- 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] New ruby create-new-package script.
by David Benjamin 21 May '20

21 May '20

Good evening to most of you on this list. I have worked on a new https://github.com/dwbenjamin/yast-devtools/tree/create-new-package script, it is not complete. I would like to know some thoughts on continuing to put time into this, here is a little more information: I am not a professional developer, so I will need some help with Licensing and such. Is there any real value to this? For me it would shorten the learning curve as the script would build the minimum directory and file structure. The idea is to reduce the time to start actually hacking in Yast, it might help external contributors. There currently isn't any docs for this tool but I will continue to work on that if this is something you think is of value. Thank you for any and all of your time, David. -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 2

[yast-devel] Branching SLE-15-SP2 today at 16:00 CEST (14:00 UTC)
by Ladislav Slezak 19 May '20

19 May '20

Hello! Today I'll create the SLE-15-SP2 maintenance branch from master for all YaST and libyui packages. I'll start around 16:00 CEST (14:00 UTC). Because there are so many packages it will take some time, I'll let you know when it's done. So if you still have some pull requests for the SP2 open then merge them ASAP, or change the target branch after the SP2 branch is created. -- 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

3 5

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

18 May '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 (338 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-autoinstallation: - WIP: cleanup issue handling (9 days) https://github.com/yast/yast-autoinstallation/pull/601 - Find the Base Product (13 days) https://github.com/yast/yast-autoinstallation/pull/599 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (305 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-core: - Fixes for gensalt handling with libxcrypt. (80 days) https://github.com/yast/yast-core/pull/144 Pending requests in repository yast-country: - Port to rake (305 days) https://github.com/yast/yast-country/pull/217 Pending requests in repository yast-devtools: - Y2logs analyzer (82 days) https://github.com/yast/yast-devtools/pull/149 - Supplement changes from YCC (110 days) https://github.com/yast/yast-devtools/pull/148 - Move desktop files (343 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-installation: - Demo: eager mode of zombie-killer 0.5 (556 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-iscsi-lio-server: - Write service after save sp1 (10 days) https://github.com/yast/yast-iscsi-lio-server/pull/104 Pending requests in repository yast-network: - WIP: cleanup issue handling (9 days) https://github.com/yast/yast-network/pull/1057 - network-ng: test cases document (draft) (178 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (304 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-online-update-configuration: - drop old testsuite and convert to rake (52 days) https://github.com/yast/yast-online-update-configuration/pull/24 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (47 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-pkg-bindings: - drop old empty testsuite (52 days) https://github.com/yast/yast-pkg-bindings/pull/127 Pending requests in repository yast-registration: - [SP3] Fix misleading default_skipping_text (BSC#1167795) (45 days) https://github.com/yast/yast-registration/pull/488 Pending requests in repository yast-schema: - [WIP] Support for optional string and map types (10 days) https://github.com/yast/yast-schema/pull/76 Pending requests in repository yast-squid: - packaging: remove SuSEfirewall2 artifacts (296 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 (139 days) https://github.com/yast/yast-sudo/pull/12 Pending requests in repository yast-sysconfig: - Drop old testsuite (51 days) https://github.com/yast/yast-sysconfig/pull/30 Pending requests in repository yast-users: - Improve readme (102 days) https://github.com/yast/yast-users/pull/224 - Move back the UMASK default value to /etc/login.defs (bsc#1099153) (683 days) https://github.com/yast/yast-users/pull/161 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] Translatable strings and language tags, do not use the %<foo>s placeholder
by Ladislav Slezak 14 May '20

14 May '20

Hi all, The script for collecting the translatable strings from the source code has been improved to add Gettext language format tags for strings which contain the old YCP %1 or new Ruby %s or %{foo} placeholders. (Thanks to HuHa!) This should ensure that the same tags are also present in the translated messages and avoid YaST crashes. Because there is no suitable language tag for the Ruby %<foo>s placeholders they should not be used in the YaST code. They can be easily replaced by the %{foo} tags. It turned out that this variant was used only in one YaST module (yast2-rmt) so the fix was easy. Additionally I have enhanced the "rake check:pot" task to scan for the %<> tags and complain when found. This task is automatically used at Travis so this should find the possible issues very early. For more details see these links: - Script for adding the language tags: https://github.com/yast/yast-devtools/pull/152 - Example how the new language tags were added: https://github.com/yast/yast-translations/commit/5433f5b952fe883df8b74c0c35… - Fixed yast2-rmt: https://github.com/yast/yast-rmt/pull/56 - Enhanced "check:pot" task: https://github.com/yast/yast-rake/pull/79 -- 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] New Yard Warnings
by josef Reidinger 13 May '20

13 May '20

Hi YaSTies, new yardoc is here and because we do not freeze its version, we also using it. It adds a more strictness to link resolving. So it no longer resolve links to method of constant or to attribute that is not found. Sadly those constant include also yast modules which is costant created as instance of class so it is singleton. What is affected? All packages that use links and use check:doc to verify documentation. How error looks like? ``` [warn]: The namespace of link "Y2ModuleConfig#resource_aliases_map" is a constant or invalid. [warn]: The namespace of link "Profile.Prepare" is a constant or invalid. [warn]: The namespace of link "Yast::Profile.current" is a constant or invalid. [warn]: In file `src/lib/autoinstall/activate_callbacks.rb':40: Cannot resolve link to Yast::Profile.current from text: ...{Yast::Profile.current}... ``` How to fix it? Using Class suffix to link class that implements method. Example can be seen in this commit - https://github.com/yast/yast-autoinstallation/pull/607/commits/dd3e20dc54ec… Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

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

11 May '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 (331 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-autoinstallation: - Find the Base Product (6 days) https://github.com/yast/yast-autoinstallation/pull/599 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (298 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-core: - Fixes for gensalt handling with libxcrypt. (73 days) https://github.com/yast/yast-core/pull/144 Pending requests in repository yast-country: - Port to rake (298 days) https://github.com/yast/yast-country/pull/217 Pending requests in repository yast-devtools: - Y2logs analyzer (75 days) https://github.com/yast/yast-devtools/pull/149 - Supplement changes from YCC (103 days) https://github.com/yast/yast-devtools/pull/148 - Move desktop files (336 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-installation: - Demo: eager mode of zombie-killer 0.5 (549 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - network-ng: test cases document (draft) (171 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (297 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-online-update-configuration: - drop old testsuite and convert to rake (45 days) https://github.com/yast/yast-online-update-configuration/pull/24 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (40 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-pkg-bindings: - drop old empty testsuite (45 days) https://github.com/yast/yast-pkg-bindings/pull/127 Pending requests in repository yast-registration: - [SP3] Fix misleading default_skipping_text (BSC#1167795) (38 days) https://github.com/yast/yast-registration/pull/488 Pending requests in repository yast-squid: - packaging: remove SuSEfirewall2 artifacts (289 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 (132 days) https://github.com/yast/yast-sudo/pull/12 Pending requests in repository yast-sysconfig: - Drop old testsuite (44 days) https://github.com/yast/yast-sysconfig/pull/30 Pending requests in repository yast-users: - Improve readme (95 days) https://github.com/yast/yast-users/pull/224 - Move back the UMASK default value to /etc/login.defs (bsc#1099153) (676 days) https://github.com/yast/yast-users/pull/161 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 98
by Ancor Gonzalez Sosa 05 May '20

05 May '20

It's time for another report from the YaST trenches. This time with links to other interesting reads and with several calls to action. Today topics include: * Some considerations about the usage of YaST * A sneak peek at the future of AutoYaST, including a separate full blog post * Some kind of UI design contest for the YaST Partitioner * Better compatibility with LVM cache * Interesting researchs about combining disks and about Unicode support for VFAT in Linux * An impressive speedup of the partitioning proposal for SUSE Manager * A summary of the enhancements in Leap 15.2 Find the whole report at https://yast.opensuse.org/blog/2020-05-05/sprint-98 Cheers -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] XML Schema Meeting Conclusion
by josef Reidinger 04 May '20

04 May '20

Hi, today we had meeting about changes in xml schema and also we revisit some topics in XML parser. Here are conclusions we reach ( do not hesitate to opposite or add anything I miss or forget ): - allow in schema types everywhere. Current situation is that type string and map is forbidden and rest is mandatory. So newly string and map can be optionally specified in XML. - allow for backward compatibility type disksize and fallback to string as before. This needs modification in xml parser and also in schema allow beside disksize also string type for given types. - if no type is specified, use string type ( for backward compatibility it still use hash when there are no value and sub elements ). This simplify situation with implicit type and also helps a lot with backward compatibility. - when exporting ( aka serializing data ) it won't write type string to make xml smaller as it is now default type. On other hand, map is always written down, so if user edit XML and remove sub elements, it won't be considered as empty string. - martin propose to have alternative with `t=<type>` syntax as shortcut to `config:type=<type>` and use it by default. Idea looks good for all participants. Martin plan to introduce it for discussion. - no modification of skelcd will be needed due to changes mentioned above even in post install script of yast2.rpm - For autoyast profile, we should still work with old profiles. It needs testing if we do not export anywhere empty hash, which in past will be skipped, but newly it will be empty string. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Upcoming changes in AppArmor aa-status output
by Christian Boltz 04 May '20

04 May '20

Hello, AFAIK the YaST AppArmor module uses the JSON output of aa-status. There are two upcoming changes, and I'd like to point them out so that you can adjust the YaST AppArmor module if needed. a) new profile modes Besides complain and enforce mode, future AppArmor versions (>= 3.0) will also have `unconfined`, `mixed` and `kill`. Technically the structure of the JSON doesn't change, but there will be new values for the status, for example "processes": { "/usr/lib/GConf/2/gconfd-2": [ { "pid": "3899", "profile": "/usr/lib/GConf/2/gconfd-2", "status": "kill" } ] } "profiles": { "/does/not/exist": "kill" } Side question: Do you think this warrants increasing the JSON version number? Quick explanation about the new modes: - unconfined: similar to not having a profile, but when using an unconfined profile, it's possible to replace it with a "real" profile later, so that programs initially running under an unconfined profile get a profile in enforce mode - kill: similar to enforce, but on profile violations, the process will be killed instead of "just" getting EPERM - mixed: when using stacked profiles, this indicates that a program is for example using a stack of two profiles, one in complain and one in enforce mode. (This also means you'll see "mixed" only in aa-status output, but never in a profile's "flags=(...)".) (Extending the aa-* tools to support switching to kill and unconfined mode is still on my TODO list.) b) whitespace changes aa-status was rewritten to C, which results in changed whitespace in the --json output. Currently --pretty-json also results in "compressed" JSON, but I hope that this will change again in the future. I'd guess/hope that whitespace changes shouldn't matter, but please check nevertheless. Currently the new aa-status is only available in upstream git master. If it makes testing easier for you, I can provide the compiled binary or some example output. Regards, Christian Boltz -- Es kann dadurch , daß der Rechner ( wenn er an Trenn - zeichen umbricht [Ratti erklärt ) die falschen Stellen den Begriff erwischt , zu ganz gräß "Plenken" - lichen Effekten kommen in suse-linux] ! -- 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 04 May '20

04 May '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 (324 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (291 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-core: - Fixes for gensalt handling with libxcrypt. (66 days) https://github.com/yast/yast-core/pull/144 Pending requests in repository yast-country: - Port to rake (291 days) https://github.com/yast/yast-country/pull/217 Pending requests in repository yast-devtools: - Y2logs analyzer (68 days) https://github.com/yast/yast-devtools/pull/149 - Supplement changes from YCC (96 days) https://github.com/yast/yast-devtools/pull/148 - Move desktop files (329 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-installation: - Stop plymouth splash to avoid serial terminal splutter. (52 days) https://github.com/yast/yast-installation/pull/841 - Demo: eager mode of zombie-killer 0.5 (542 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-iscsi-lio-server: - Write service after save sp1 (9 days) https://github.com/yast/yast-iscsi-lio-server/pull/104 Pending requests in repository yast-network: - network-ng: test cases document (draft) (164 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (290 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-nis-client: - fix build requires (55 days) https://github.com/yast/yast-nis-client/pull/47 Pending requests in repository yast-online-update-configuration: - drop old testsuite and convert to rake (38 days) https://github.com/yast/yast-online-update-configuration/pull/24 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (33 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-pkg-bindings: - drop old empty testsuite (38 days) https://github.com/yast/yast-pkg-bindings/pull/127 Pending requests in repository yast-registration: - [SP3] Fix misleading default_skipping_text (BSC#1167795) (31 days) https://github.com/yast/yast-registration/pull/488 Pending requests in repository yast-squid: - packaging: remove SuSEfirewall2 artifacts (282 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 (125 days) https://github.com/yast/yast-sudo/pull/12 Pending requests in repository yast-sysconfig: - Drop old testsuite (37 days) https://github.com/yast/yast-sysconfig/pull/30 Pending requests in repository yast-users: - Improve readme (88 days) https://github.com/yast/yast-users/pull/224 - Move back the UMASK default value to /etc/login.defs (bsc#1099153) (669 days) https://github.com/yast/yast-users/pull/161 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