June 2020 - YaST Development - openSUSE Mailing Lists

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

15 Jun '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 (366 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-autoinstallation: - Find the Base Product (41 days) https://github.com/yast/yast-autoinstallation/pull/599 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (333 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-core: - Fixes for gensalt handling with libxcrypt. (108 days) https://github.com/yast/yast-core/pull/144 Pending requests in repository yast-country: - Port to rake (333 days) https://github.com/yast/yast-country/pull/217 Pending requests in repository yast-devtools: - Y2logs analyzer (110 days) https://github.com/yast/yast-devtools/pull/149 - Supplement changes from YCC (138 days) https://github.com/yast/yast-devtools/pull/148 - Move desktop files (371 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-installation: - clarify that ssh_import processes host keys (bsc#1172400) (10 days) https://github.com/yast/yast-installation/pull/860 - Demo: eager mode of zombie-killer 0.5 (584 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - network-ng: test cases document (draft) (206 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (332 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (75 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-registration: - [SP3] Fix misleading default_skipping_text (BSC#1167795) (73 days) https://github.com/yast/yast-registration/pull/488 Pending requests in repository yast-yast2: - Bnc#1081441 (60 days) https://github.com/yast/yast-yast2/pull/1047 - [WIP] CWM improvements (61 days) https://github.com/yast/yast-yast2/pull/1044 - Change the way groups are defined (370 days) https://github.com/yast/yast-yast2/pull/936 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (501 days) https://github.com/yast/yast-yast2/pull/894 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (501 days) https://github.com/yast/yast-yast2/pull/893 - [WIP] Firewalld fixes for the new UI (649 days) https://github.com/yast/yast-yast2/pull/813 - [WIP] Drop SuSEfirewall2 completely (634 days) https://github.com/yast/yast-yast2/pull/806 Pending requests in repository yast-ycp-ui-bindings: - [WIP] Support bold font inside tables (661 days) https://github.com/yast/yast-ycp-ui-bindings/pull/35 Pending requests in repository yast-ruby-bindings: - Fixes for gensalt handling with libxcrypt. (108 days) https://github.com/yast/yast-ruby-bindings/pull/239 - [WIP] Don't crash on NoMethodError when Perl is involved (164 days) https://github.com/yast/yast-ruby-bindings/pull/224 - log method name (748 days) https://github.com/yast/yast-ruby-bindings/pull/216 Pending requests in repository yast-rake: - Switch desktop directory (371 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

Re: [yast-devel] What is the best way to use AugeasTree in a dialog tree?
by josef Reidinger 11 Jun '20

11 Jun '20

On Wed, 10 Jun 2020 20:32:25 -0600 "David Benjamin" <dbenjamin(a)ontario.k12.or.us> wrote: > Thank you. > > So CWM is good? I thought I read it is being phased out. > > Thanks again, > David. Well, it is not perfect and we are experimenting how to have object UI without need to load and store values, but for now I think it is the best representation of the object based UI. So we have two concepts there: 1. event based UI where you have defined how UI looks and event loop which react on user actions for whole dialog. Its advantage is that everything is together. Disadvantage is very low re-usability as it is all or nothing and often lead to just copy pasting of same code. Example in more modern code is in yast2-journal - https://github.com/yast/yast-journal/blob/master/src/lib/y2journal/query_di… 2. widget based UI ( represented by object CWM ) which define each widget as object that itself handle user input on that widget. Its advantage is re-usability as you can you can just reuse widget that you need in different dialog. Disadvantage is that on dialog level you do not see immediatelly how it will react and need to check each widget. Example is e.g. bootloader module - widgets at https://github.com/yast/yast-bootloader/blob/master/src/lib/bootloader/grub… and dialog at https://github.com/yast/yast-bootloader/blob/master/src/lib/bootloader/conf… Sadly we do not have now the one best way how to write UI and sometime we suffer from it as those two concepts is not so easy to mix. Josef > > > > > > >>> josef Reidinger <jreidinger(a)suse.cz> 06/10/20 4:29 PM >>> > On Wed, 10 Jun 2020 12:21:06 -0600 > "David Benjamin" <dbenjamin(a)ontario.k12.or.us> wrote: > > > Hello everyone, > > > > I have data from a file that was parsed using CFA::AugeasParsser. > > > > Can it be used in a dialog without translating from CFA::AugeasTree it to Yast::Term.Tree? > > Hi David, > sadly(?) it cannot be done. Usual work-flow is to have own model class that is child of CFA::BaseModel that provide access to variables you are interested ( as usually you do not want to present user everything in file to not overwhelm him ). > > This model is then used as backend and in frontend you use various terms to represent widgets. As beside parsing, config file values often have its semantic and you want to help user to fill it correct. So e.g. for variables that are on/off you want to use checkbox, > if it is local path, you want input field with Browse button that allows to select file on system, or int field for integer values. Also often configuration files has dependent values, like if value A is true, then value A1 is used, but if it is false, it is ignored. > You can represent it in frontend by event handling that disable widget for A1 if A is unselected. > > If you are interested in example code, just write and I can point you to some. ( also nowadays we use quite lot CWM widgets, which is object oriented way how to write widgets, so if you are interested, I can also point you to some examples and code ). > > > > > Thanks, > > David. > > > > 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] What is the best way to use AugeasTree in a dialog tree?
by David Benjamin 10 Jun '20

10 Jun '20

Hello everyone, I have data from a file that was parsed using CFA::AugeasParsser. Can it be used in a dialog without translating from CFA::AugeasTree it to Yast::Term.Tree? 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] YaST: highlights of development sprint 101
by Ancor Gonzalez Sosa 10 Jun '20

10 Jun '20

As explained in our previous blog post, or latest YaST development report is basically a collection of links to (rather descriptive) Github’s pull requests. You can find the report, which includes the links and a couple of extra details here: https://yast.opensuse.org/blog/2020-06-09/sprint-101 Or maybe you want to jump directly to any of the mentioned pull requests: - Added F8 shortcut to switch installation to Chinese https://github.com/openSUSE/gfxboot/pull/46 - Linuxrc support for `$releasever` in repository URLs https://github.com/openSUSE/linuxrc/pull/224 - Fixed problems when the user rejects the license of SLE addons https://github.com/yast/yast-registration/pull/494 - Improvements in the AutoYaST command line https://github.com/yast/yast-autoinstallation/pull/622 - Fixed `xmllint` messages for invalid AutoYaST profiles https://github.com/yast/yast-schema/pull/77 - Do not propose insecure signature settings in AutoYaST https://github.com/yast/yast-autoinstallation/pull/618 - Earlier AutoYaST network configuration https://github.com/yast/yast-autoinstallation/pull/617 In any case, have a lot of reading fun! -- 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] Meeting about the Partitioner UI
by Ancor Gonzalez Sosa 09 Jun '20

09 Jun '20

We agreed to have a meeting to discuss the ideas collected here and decide how to move forward: https://github.com/yast/yast-storage-ng/blob/master/doc/partitioner_ui.md It will take place tomorrow Wednesday June 10th "after lunch", which I guess can be translated to 2pm CEST (so nobody has to eat in a hurry). Usual location for YaST Team pandemic meetings: https://li2023-182.members.linode.com/#/rooms/2001 Cheers. -- 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

1 0

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

08 Jun '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 (359 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-autoinstallation: - Find the Base Product (34 days) https://github.com/yast/yast-autoinstallation/pull/599 Pending requests in repository yast-bootloader: - Cleanup issue handling (9 days) https://github.com/yast/yast-bootloader/pull/606 - Fix resume with uuid partition (326 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-core: - Fixes for gensalt handling with libxcrypt. (101 days) https://github.com/yast/yast-core/pull/144 Pending requests in repository yast-country: - Port to rake (326 days) https://github.com/yast/yast-country/pull/217 Pending requests in repository yast-devtools: - Y2logs analyzer (103 days) https://github.com/yast/yast-devtools/pull/149 - Supplement changes from YCC (131 days) https://github.com/yast/yast-devtools/pull/148 - Move desktop files (364 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-installation: - Demo: eager mode of zombie-killer 0.5 (577 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - Autoyast based installation does not seem to respect defined udev rules. (13 days) https://github.com/yast/yast-network/pull/1061 - network-ng: test cases document (draft) (199 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (325 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (68 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-registration: - [SP3] Fix misleading default_skipping_text (BSC#1167795) (66 days) https://github.com/yast/yast-registration/pull/488 Pending requests in repository yast-yast2: - Bnc#1081441 (53 days) https://github.com/yast/yast-yast2/pull/1047 - [WIP] CWM improvements (54 days) https://github.com/yast/yast-yast2/pull/1044 - Change the way groups are defined (363 days) https://github.com/yast/yast-yast2/pull/936 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (494 days) https://github.com/yast/yast-yast2/pull/894 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (494 days) https://github.com/yast/yast-yast2/pull/893 - [WIP] Firewalld fixes for the new UI (642 days) https://github.com/yast/yast-yast2/pull/813 - [WIP] Drop SuSEfirewall2 completely (627 days) https://github.com/yast/yast-yast2/pull/806 Pending requests in repository yast-ycp-ui-bindings: - [WIP] Support bold font inside tables (654 days) https://github.com/yast/yast-ycp-ui-bindings/pull/35 Pending requests in repository yast-ruby-bindings: - Fixes for gensalt handling with libxcrypt. (101 days) https://github.com/yast/yast-ruby-bindings/pull/239 - [WIP] Don't crash on NoMethodError when Perl is involved (157 days) https://github.com/yast/yast-ruby-bindings/pull/224 - log method name (741 days) https://github.com/yast/yast-ruby-bindings/pull/216 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] 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] yast-hello-world Customization
by David Benjamin 02 Jun '20

02 Jun '20

Hello everyone, Here is my first working copy of the rake customization: https://github.com/dwbenjamin/yast-hello-world.git Now you can run "rake new_module:create" to generate a new working module. Please let me know if any additional files should be included in the new module. Thanks, David. -- 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] 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