September 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] Innovation time: A repository with AutoYaST XML profiles (PoC )
by Ladislav Slezak 03 May '21

03 May '21

Hi all! I'm implementing some new AutoYaST feature and I found out that it's not easy to test the AutoYaST functionality. 1. Even for testing a trivial scenario you have to write your own XML file. If you do not have much experience with AutoYaST you have to read the documentation, search the internet, etc... Cloning your current system helps a bit but usually the cloned profile contains too many options so you still need to polish it a bit... 2. When you have your profile ready you have to host it at some HTTP/FTP/NFS/... server so AutoYaST can use it for installation. I usually run simple "ruby -run -ehttpd" command to have a web server quickly, but that's quite tricky for people not familiar with Ruby. My idea is to have some repository with example XML profiles which would be publicly available and ready for instant use. We already have some XML files in the autoyast-profiles-test Git repository but writing something like autoyast=https://raw.githubusercontent.com/yast/autoyast-profiles-test/mast… on boot command line is a real pain. We could use some URL shortening service but I do not like that much. Shortened URLs do not look nice and it's not obvious where they point to (security). I'd like to have some nice URLs... So my proposal is to use the GitHub pages for building an AutoYaST profile repository. Then you could use autoyast=https://autoyast.github.io/mini/sles15.xml or autoyast=https://autoyast.github.io/mini/leap15.xml for testing a minimal SLES/Leap profile. Actually these URLs already work! :-) You can give it a try. Most likely you will need additional "netsetup=dhcp" boot option for configuring network. The profiles would be well described (what they do) and well commented (so the users can easily adapt them to their needs). The profiles could be automatically validated (via Travis) and it would be nice to use them also in openQA tests to be sure they really work. We could also link this repository from the official SUSE documentation. The proof of concept is available at https://autoyast.github.io, please check it. It is still just a concept for getting early feedback, there is a lot of work to do. See the README file in https://github.com/autoyast/autoyast.github.io What do you think about it? -- 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] Innovation Time: Feedback from forums
by josef Reidinger 13 Nov '20

13 Nov '20

Hi, I use my todays innovation time to try to collect feedback from forums and as we have quite nice opensuse retrospective output, I try to focus on SLE. So I use forums.suse.com and here is few links with short description: AutoYast - looking for recommended autoyast profile for VM server http://forums.suse.com/discussion/13055/template-best-practices-and-hardeni… - problem with configuring network using autoyast ( not clear what is root of issue ) http://forums.suse.com/discussion/14165/autoyast-sles15-sp1 - easy way to install also custom rpms in autoyast http://forums.suse.com/discussion/14138/adding-custom-rpm-to-installer - trying to add packages iso to directory and use it in autoyast and failed http://forums.suse.com/discussion/14065/installer-fails-to-find-add-ons-fro… - not clear documenation how to reference files from enhanced DVD in autoyast http://forums.suse.com/discussion/13986/copy-a-file-from-the-installer-dvd - autoyast use case unattended installation from USB - documenation not clear http://forums.suse.com/discussion/12227/sles15-unattended-install-from-usb Storage - user trying to resize living system with partitioner and failed. Error probably does not help much: http://forums.suse.com/discussion/14113/resize-partition-error - kudos to partitioner for easy way of deleting btrfs snapshot http://forums.suse.com/discussion/11718/how-to-delete-btrfs-subvolume - switching DOS MBR and GPT real use case http://forums.suse.com/discussion/13961/need-to-convert-mbr-to-gpt - another fs resize http://forums.suse.com/discussion/13205/file-system-increase - another replacing filesystem, this time root one http://forums.suse.com/discussion/12576/replacing-root-filesystem-from-sdb2… Features ( new use cases ) - disable usb due to sec certificates - ca management missing and auth_server missing wizard like setup http://forums.suse.com/discussion/14022/authentication-server-with-yast-and… - again ca management missing http://forums.suse.com/discussion/13084/ca-management-yast-tool-missing - problem to configure proxy in SLES. Works in opensuse http://forums.suse.com/discussion/14221/install-sles-behind-a-proxy - offline self-update from medium http://forums.suse.com/discussion/13582/self-update-offline Misc - package search with RMT error message confuse user: http://forums.suse.com/discussion/14233/how-to-add-a-module-repo-to-an-exis… - issue with packager, cannot find patterns view http://forums.suse.com/discussion/14120/install-selinux-sles-15-sp1 - people use suse firewall module http://forums.suse.com/discussion/13097/sles-12-sp4-cant-manage-firewall-du… - looks like systemd sockets are not always understandable for users and complain to yast http://forums.suse.com/discussion/12846/vnc-server-service - upgrade of system to the same version sometimes can help with boot problems http://forums.suse.com/discussion/14797/sles12sp5-vm-stuck-at-grub-when-boo… - many confusion with SP1 DVD layout like in http://forums.suse.com/discussion/13504/yast-yast2-is-missing-after-install… - even servers is now installed using USB http://forums.suse.com/discussion/14228/install-from-usb 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] Automatic AutoYaST Schema Validation
by Imobach González Sosa 05 Oct '20

05 Oct '20

Hi all, As you may know, we introduced automatic profile validation in AutoYaST for SLE 15 SP3 and Tumbleweed. When the profile is not correct, AutoYaST complains at the beginning of the autoinstallation. So, as expected, we are getting regular bug reports from openQA. In some cases, the profile is just wrong. However, we have detected several problems in yast2-schema. Although you can disable this feature at boot time (setting YAST_SKIP_XML_VALIDATION to 1), I fear that we are going to get a ton of errors from our users and customers. So I was considering whether we should disable this feature by default, although in that case I would ask openQA to enable it so we can improve yast2- schema quality. What is your point of view? Regards, Imo -- Imobach González Sosa YaST Team at SUSE LLC https://imobachgs.github.io/

6 10

[yast-devel] YaST in Hacktoberfest?
by Srinidhi B 01 Oct '20

01 Oct '20

Hello YaST Team, I was looking at the list of issues marked for Hacktoberfest [1] and couldn't find any YaST issues marked for it. I don't see YaST mentioned in the openSUSE blog post for Hacktoberfest as well. Are there any plans to participate in Hactoberfest? Regards, Srinidhi. [1] https://github.com/search?q=label%3Ahacktoberfest+state%3Aopen+no%3Aassigne… [2] https://news.opensuse.org/2020/09/14/opensuse-projects-support-hacktoberfes… N��r��y隊\��^��~�{.n�+��Ǩ��r��i�m��0��ޙ��ɫ-u�ޗ�0��Ǩ�

3 3

[yast-devel] Highlights of development sprint 109
by Ancor Gonzalez Sosa 29 Sep '20

29 Sep '20

The YaST Team continues focusing on improving both AutoYaST and the management of storage devices. Let's take a quick glance at some of the results. - New YaST test client to check AutoYaST dynamic profiles. - Improved detection of which YaST package is needed to process each section of the profile, relying on RPM’s supplement information. - First steps to annotate the documentation of AutoYaST with better information about the corresponding version for each feature. - Final design of the new Partitioner user interface. - Improved automatic submission of translations to Leap and SLE. Check the whole report at https://yast.opensuse.org/blog/2020-09-29/sprint-109 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] Pending Pull Requests
by yast-ci＠opensuse.org 28 Sep '20

28 Sep '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-autoinstallation: - [PoC] Run the unit tests in parallel (33 days) https://github.com/yast/yast-autoinstallation/pull/670 - Find the Base Product (146 days) https://github.com/yast/yast-autoinstallation/pull/599 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (438 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-devtools: - Y2logs analyzer (215 days) https://github.com/yast/yast-devtools/pull/149 - Supplement changes from YCC (243 days) https://github.com/yast/yast-devtools/pull/148 - Move desktop files (476 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (180 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-pkg-bindings: - WIP: Master jira sle 15184 (10 days) https://github.com/yast/yast-pkg-bindings/pull/138 Pending requests in repository yast-update: - WIP: Master jira sle 15184 (10 days) https://github.com/yast/yast-update/pull/156 Pending requests in repository yast-vm: - bsc#1169214 - When NetworkManager is being used bridge creation will not work so show warning popup (40 days) https://github.com/yast/yast-vm/pull/47 Pending requests in repository yast-yast2: - [WIP] Drop SuSEfirewall2 completely (739 days) https://github.com/yast/yast-yast2/pull/806 Pending requests in repository yast-ycp-ui-bindings: - [WIP] Support bold font inside tables (766 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 (269 days) https://github.com/yast/yast-ruby-bindings/pull/224 Pending requests in repository yast-rake: - Switch desktop directory (476 days) https://github.com/yast/yast-rake/pull/70 Pending requests in repository yast-cio: - convert to libyui ruby bindings (191 days) https://github.com/yast/yast-cio/pull/34 Pending requests in repository skelcd-control-openSUSE: - Adjust the roles to the new YaST Patterns (272 days) https://github.com/yast/skelcd-control-openSUSE/pull/195 Pending requests in repository yast-auth-server: - Fixes to make the YaST modules work (459 days) https://github.com/yast/yast-auth-server/pull/48 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (170 days) https://github.com/yast/yast-journal/pull/45 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] Hint: Easy adapting changes from forks
by josef Reidinger 25 Sep '20

25 Sep '20

Hi, as I now work on merging various pull requests, it often lives in own forks, where I do not have permissions and I am looking for the easiest way to make them again mergeable and sometimes adapt it to our needs. what works best for me is e.g. for this pr: https://github.com/yast/yast-ruby-bindings/pull/239 ```shell git checkout master && git pull && git checkout -b my_branch wget https://github.com/yast/yast-ruby-bindings/pull/239.patch # notice .patch suffix git am -3 239.patch # and then solve conflicts and branch is ready for new pr ``` Do you know easier way? This way it is for me like good old kernel mailing lists where you get set of patches that you can apply. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 2