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