YaST Development August 2019

yast-devel@lists.opensuse.org

12 participants
12 discussions

[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] YaST Sprint 83 Report
by Imobach González Sosa 02 Sep '19

02 Sep '19

Hi all, The YaST team has just published another sprint report that, as usual, you can find in lizards.opensuse.org: https://lizards.opensuse.org/2019/08/30/yast-sprint-83/ During the last two weeks, we have been basically busy squashing bugs and trying to get the network module as feature-complete as possible. And, after all, we have had also some time to improve our infrastructure and organize for the future. Enjoy! Regards, Imo -- Imobach González Sosa YaST Team at SUSE LINUX GmbH https://imobachgs.github.io/

4 4

[yast-devel] detected a file system next to a partition table on the device /dev/md4; &
by Felix Miata 29 Aug '19

29 Aug '19

1 http://fm.no-ip.com/SS/Suse/YaST/yast2md4error.png Is this a real error, or a bug that either exists or I should file? http://fm.no-ip.com/Tmp/SUSE/Factory/gb250L08x2.txt has possibly relevant data I collected, much of which I don't believe needs to stay in the list archive. http://fm.no-ip.com/Tmp/SUSE/Factory/y2l-201908.xz is /var/log/YaST2/y2log. http://fm.no-ip.com/Tmp/SUSE/Factory/y2l-201908.tgz has control/ and storage/. When I chose to continue, no more messages appeared. 2 The reason I opened bootloader in the first place was a search for a correspondence to /etc/default/grub's GRUB_DISABLE_SUBMENU= which seems to be absent. Need I report a B.O.O. bug asking that this be added? Has this wish been made already? I tried searching, but it's reliably returning either document contains no data, or simply timing out "Secure Connection Failed...The page you are trying to view cannot be shown because the authenticity of the received data could not be verified". -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- 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] Automatically delete the PR branches at GitHub?
by Ladislav Slezak 27 Aug '19

27 Aug '19

Hi all, I just noticed that GitHub has a new option (well, new for me, I do not know how long actually it is there...) in the repository settings in the "Merge Button" section with description "After pull requests are merged, you can have head branches deleted automatically." For testing I have enabled that in https://github.com/yast/yast-hardware-detection and merged the https://github.com/yast/yast-hardware-detection/pull/22 PR. After pressing the "Merge" button the PR was merged and the branch was automatically deleted. Nice! Enabling this feature would avoid leaving obsolete branches at GitHub. They accumulated in some repositories to a quite big amount so I'd like to enable this globally for all YaST repositories to avoid this situation. Anybody against this? BTW there is still displayed that "Restore branch" button after deleting the branch automatically, you can manually restore the branch if needed. But IIRC I have never needed that so far... Ladislav -- 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 2

[yast-devel] Collecting bugs related to the desktop files change
by David Díaz 27 Aug '19

27 Aug '19

Hi there! Yesterday, Imobach suggested collecting the reported bugs related to changes done recently in the desktop files[1] to document the implications to bear in mind next time that they need to be changed. It looks to be a good idea, thus I'm asking for help to do it. At the moment, we have located the followings * Inferring correct module name in AutoYaST: https://bugzilla.suse.com/show_bug.cgi?id=1140233 * Confusion about using the right module name: https://bugzilla.suse.com/show_bug.cgi?id=1138144 https://bugzilla.suse.com/show_bug.cgi?id=1140339 * "Missing" desktop translations: https://bugzilla.suse.com/show_bug.cgi?id=1145197 * Changes the user experience in Gnome search (for both, better and worst): https://bugzilla.suse.com/show_bug.cgi?id=1144952 * Wrong references in yast2-schema: http://bugzilla.suse.com/show_bug.cgi?id=1144894 If you don't mind, please help us to complete the list. Thanks in advance. Regards. PS: originally sent to the yast-internal list by mistake :) [1] https://github.com/yast/yast-yast2/issues/934 -- David Díaz González YaST Team at SUSE Linux GmbH

3 2

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 26 Aug '19

26 Aug '19

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 (72 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (39 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-country: - [NOT READY TO MERGE] Add missing Persian/Farsi language and keyboard layout (30 days) https://github.com/yast/yast-country/pull/222 - Port to rake (39 days) https://github.com/yast/yast-country/pull/217 - Adding Persian (Farsi) (bsc#1092920) (135 days) https://github.com/yast/yast-country/pull/211 - Keyboard rewrite: encapsulate systemd actions (239 days) https://github.com/yast/yast-country/pull/200 - Keyboard rewrite: add documentation and license information (276 days) https://github.com/yast/yast-country/pull/199 - Keyboard rewrite: fix error setting x11 keymap (276 days) https://github.com/yast/yast-country/pull/198 - Keyboard rewrite: add more layouts to the module (276 days) https://github.com/yast/yast-country/pull/197 - Keyboard rewrite: select current layout on startup (276 days) https://github.com/yast/yast-country/pull/196 - Keyboard rewrite: Use strategy pattern to avoid coupling (276 days) https://github.com/yast/yast-country/pull/195 Pending requests in repository yast-devtools: - Move desktop files (77 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-dhcp-server: - Fix check of 'set' and 'key' options (19 days) https://github.com/yast/yast-dhcp-server/pull/47 Pending requests in repository yast-installation: - BSC#1132915 - Bootparameter url file:///PATH will not be evaluated co… (109 days) https://github.com/yast/yast-installation/pull/796 - Demo: eager mode of zombie-killer 0.5 (290 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - Infer interface type (6 days) https://github.com/yast/yast-network/pull/920 - add initial test cases document (38 days) https://github.com/yast/yast-network/pull/853 - [RFC] First impressions of the current network configuration status (167 days) https://github.com/yast/yast-network/pull/729 - [RFC] Udev rule preparations (437 days) https://github.com/yast/yast-network/pull/639 Pending requests in repository yast-online-update-configuration: - Prompt for root password. (131 days) https://github.com/yast/yast-online-update-configuration/pull/21 Pending requests in repository yast-squid: - packaging: remove SuSEfirewall2 artifacts (30 days) https://github.com/yast/yast-squid/pull/30 Pending requests in repository yast-update: - [RFC] Move the target /etc/resolv.conf to /run (88 days) https://github.com/yast/yast-update/pull/114 Pending requests in repository yast-users: - Move back the UMASK default value to /etc/login.defs (bsc#1099153) (417 days) https://github.com/yast/yast-users/pull/161 Pending requests in repository yast-yast2: - Change the way groups are defined (76 days) https://github.com/yast/yast-yast2/pull/936 - Added Hostname class in y2network (115 days) https://github.com/yast/yast-yast2/pull/921 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (207 days) https://github.com/yast/yast-yast2/pull/894 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (207 days) https://github.com/yast/yast-yast2/pull/893 - [WIP] Firewalld fixes for the new UI (355 days) https://github.com/yast/yast-yast2/pull/813 - [WIP] Drop SuSEfirewall2 completely (340 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] YaST: highlights of development sprint 82
by Ancor Gonzalez Sosa 14 Aug '19

14 Aug '19

Chameleons like sun. That's why most YaST developers are on vacation (it's summer in Europe) and YaST development is moving slower than usual. But we still have some news for you. Read in the link below about our summer activities that includes: * Enhancing the development documentation * Extending AutoYaST capabilities regarding Bcache * Lots of small fixes and improvements https://lizards.opensuse.org/2019/08/14/yast-sprint-82/ 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] Temporary branches cleanup
by José Iván López González 13 Aug '19

13 Aug '19

Hi guys, I see we have several temporary branches in many YaST repos, for example in yast-storage-ng: SLE-12-SP2 tracked SLE-12-SP3 tracked SLE-15-GA tracked SLE-15-SP1 tracked feature/bsc-1123688 tracked feature/export-stray-blk-devices tracked feature/suma tracked master tracked missing-textdomain tracked parallel_rubocop_at_travis tracked pre-SLE-15-SP2 tracked rtl-pathnames tracked sle15_parallel_tests tracked stray_blk_dev_impl tracked suma_guided_setup tracked suma_proposal_devices tracked upstream/feature/partitioner-remember-tree-state tracked In this particular repo I would only expect to have: SLE-12-SP2, SLE-12-SP3, SLE-15-GA, SLE-15-SP1 and master. For other repos is even worst, for example yast-yast2: SLE-12-SP2 tracked SLE-12-SP3 tracked SLE-12-SP4 tracked SLE-15-GA tracked SLE-15-GA-1113732 tracked SLE-15-GA-registration-popup tracked SLE-15-SP1 tracked add_hostname tracked better_socket_support tracked bsc_1098919 tracked commandline-crash tracked drop_perl tracked drop_susefirewall_code tracked expanded_ids tracked fw-interfaces-read tracked ifconfig_parser tracked kill_logging_builtins tracked list_all_cards_in_fw tracked master tracked merge_SLE-12-SP3 tracked merge_SLE-12-SP4 tracked new_rubocop tracked no-xversion tracked openSUSE-10_0 tracked openSUSE-10_1 tracked openSUSE-10_2 tracked openSUSE-10_3 tracked openSUSE-11_0 tracked openSUSE-11_2 tracked openSUSE-11_3 tracked openSUSE-11_4 tracked openSUSE-12_1 tracked openSUSE-12_2 tracked openSUSE-12_3 tracked openSUSE-13_1 tracked openSUSE-13_2 tracked openSUSE-9_3 tracked readline tracked review_180109_double_entries tracked review_180125_checking_package_installed tracked review_180130_xvnc_socket_disabled tracked rubocop-0.59.2 tracked sorbet tracked sw_01 tracked systemd_table tracked unsigned_repo tracked Having all these temporary branches is not a big problem, but sometimes it is quite annoying when you run a "git fetch". What do you think about doing some cleanup in all YaST repos? I could extend my HW project [1] (still a WIP) to do it. It should be quite easy to add a new script to clean the repos. The good thing is that it is not necessary to locally clone the repos. With [1] we have the base to do it directly to GitHub thanks to Octokit [2]. CU, Iván [1] https://github.com/joseivanlopez/yast-dev [2] https://github.com/octokit/octokit.rb -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

6 7

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

YaST Development August 2019