YaST Development October 2019

yast-devel@lists.opensuse.org

6 participants
13 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] Fwd: Re: [Research] Recommendation for swap space
by Stefan Hundhammer 28 Oct '19

28 Oct '19

Following up on the swap space thread on [research], I just received an interesting piece of information from Jeff Mahoney (see below). Summary: kdump does not need swap with the same size as RAM. It doesn't need swap at all. (!) Jeff just put that into a Jira request: https://jira.suse.com/browse/PM-1444 -------- Forwarded Message -------- Subject: Re: [Research] Recommendation for swap space Date: Mon, 28 Oct 2019 09:55:22 -0400 From: Jeff Mahoney <jeffm(a)suse.com> To: Stefan Hundhammer <shundhammer(a)suse.de> On 10/28/19 9:02 AM, Stefan Hundhammer wrote: > On 28.10.19 13:48, Jeff Mahoney wrote: >> I wasn't looking to point fingers. I'm not aware of*any* swap requirement for kdump, so I was looking for the historical reason why it was added so we could address that directly (especially if it's changed). > > That's interesting. It is common knowledge^W^Wgeneral folklore here (at least at the YaST team) that kdump needs as much swap space as there is RAM to be able to write a complete kernel dump. So this is not really true? No. This was the case using the old LKCD system that last shipped with SLES9. It was modeled after historical UNIX systems that had firmware writing to swap partitions for dump recovery. The kdump system we've shipped since SLE10 doesn't read or write to swap. >> Unfortunately, I wouldn't know where to look to find the source feature request for that in our products. > > Welcome to the club. ;-( When we rewrote the YaST storage stack, it was pretty much impossible to figure out the old requirements, so we reverse engineered them by identifying existing features and a lot of common sense^W^W Kentucky windage. And that was one area where that was reasonably easy to do. Ok, that's an easy enough explanation. I'll open a JIRA ticket to remove that requirement. -Jeff -- Jeff Mahoney Director, SUSE Labs Data & Performance ------------------------------------------------------------------- Kind regards -- Stefan Hundhammer <shundhammer(a)suse.de> YaST Developer SUSE Software Solutions Germany GmbH Geschäftsführer: Felix Imendörffer HRB 36809 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany -- 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 Oct '19

28 Oct '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: - [SLE-15-GA] Backports (45 days) https://github.com/yast/yast-apparmor/pull/44 - Port to rake (135 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (102 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-country: - Port to rake (102 days) https://github.com/yast/yast-country/pull/217 Pending requests in repository yast-devtools: - Associate metadata to desktop files, for appstream builder (47 days) https://github.com/yast/yast-devtools/pull/147 - Move desktop files (140 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-firstboot: - Don't use deprecated Progress.on (10 days) https://github.com/yast/yast-firstboot/pull/79 Pending requests in repository yast-installation: - BSC#1132915 - Bootparameter url file:///PATH will not be evaluated co… (172 days) https://github.com/yast/yast-installation/pull/796 - Demo: eager mode of zombie-killer 0.5 (353 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - network-ng: test cases document (draft) (6 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (101 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-online-update-configuration: - Prompt for root password. (194 days) https://github.com/yast/yast-online-update-configuration/pull/21 Pending requests in repository yast-squid: - packaging: remove SuSEfirewall2 artifacts (93 days) https://github.com/yast/yast-squid/pull/30 Pending requests in repository yast-update: - [RFC] Move the target /etc/resolv.conf to /run (59 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) (480 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 87
by Ancor Gonzalez Sosa 23 Oct '19

23 Oct '19

It’s time for another YaST team report! Let’s see what’s on the menu. - News and improvements in the storage area, specially encryption. - Some polishing of the behavior of YaST Network. - New widgets in libYUI. - A look into systemd timers and how we are using them to replace cron. - A new cool tool to deal with complex object-oriented code. Go check https://lizards.opensuse.org/2019/10/23/yast-sprint-87/ 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 21 Oct '19

21 Oct '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: - [SLE-15-GA] Backports (38 days) https://github.com/yast/yast-apparmor/pull/44 - Port to rake (128 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (95 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-country: - Port to rake (95 days) https://github.com/yast/yast-country/pull/217 - Keyboard rewrite: encapsulate systemd actions (295 days) https://github.com/yast/yast-country/pull/200 - Keyboard rewrite: add documentation and license information (332 days) https://github.com/yast/yast-country/pull/199 - Keyboard rewrite: fix error setting x11 keymap (332 days) https://github.com/yast/yast-country/pull/198 - Keyboard rewrite: add more layouts to the module (332 days) https://github.com/yast/yast-country/pull/197 - Keyboard rewrite: select current layout on startup (332 days) https://github.com/yast/yast-country/pull/196 - Keyboard rewrite: Use strategy pattern to avoid coupling (332 days) https://github.com/yast/yast-country/pull/195 Pending requests in repository yast-devtools: - Associate metadata to desktop files, for appstream builder (40 days) https://github.com/yast/yast-devtools/pull/147 - Move desktop files (133 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-firstboot: - adapted to refactored keyboard module (9 days) https://github.com/yast/yast-firstboot/pull/78 Pending requests in repository yast-installation: - BSC#1132915 - Bootparameter url file:///PATH will not be evaluated co… (165 days) https://github.com/yast/yast-installation/pull/796 - Demo: eager mode of zombie-killer 0.5 (346 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - network-ng: test cases document (draft) (40 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (94 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-online-update-configuration: - Prompt for root password. (187 days) https://github.com/yast/yast-online-update-configuration/pull/21 Pending requests in repository yast-squid: - packaging: remove SuSEfirewall2 artifacts (86 days) https://github.com/yast/yast-squid/pull/30 Pending requests in repository yast-update: - [RFC] Move the target /etc/resolv.conf to /run (52 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) (473 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] Pending Pull Requests
by yast-ci＠opensuse.org 14 Oct '19

14 Oct '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: - [SLE-15-GA] Backports (31 days) https://github.com/yast/yast-apparmor/pull/44 - Port to rake (121 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (88 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-country: - Port to rake (88 days) https://github.com/yast/yast-country/pull/217 - Keyboard rewrite: encapsulate systemd actions (288 days) https://github.com/yast/yast-country/pull/200 - Keyboard rewrite: add documentation and license information (325 days) https://github.com/yast/yast-country/pull/199 - Keyboard rewrite: fix error setting x11 keymap (325 days) https://github.com/yast/yast-country/pull/198 - Keyboard rewrite: add more layouts to the module (325 days) https://github.com/yast/yast-country/pull/197 - Keyboard rewrite: select current layout on startup (325 days) https://github.com/yast/yast-country/pull/196 - Keyboard rewrite: Use strategy pattern to avoid coupling (325 days) https://github.com/yast/yast-country/pull/195 Pending requests in repository yast-devtools: - Associate metadata to desktop files, for appstream builder (33 days) https://github.com/yast/yast-devtools/pull/147 - Move desktop files (126 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-installation: - BSC#1132915 - Bootparameter url file:///PATH will not be evaluated co… (158 days) https://github.com/yast/yast-installation/pull/796 - Demo: eager mode of zombie-killer 0.5 (339 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - network-ng: test cases document (draft) (33 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (87 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-online-update-configuration: - Prompt for root password. (180 days) https://github.com/yast/yast-online-update-configuration/pull/21 Pending requests in repository yast-squid: - packaging: remove SuSEfirewall2 artifacts (79 days) https://github.com/yast/yast-squid/pull/30 Pending requests in repository yast-update: - [RFC] Move the target /etc/resolv.conf to /run (45 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) (466 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] Re: [opensuse-autoinstall] GPT without EFI: HowTo?
by Josef Reidinger 10 Oct '19

10 Oct '19

On Wed, 9 Oct 2019 14:24:17 +0200 Daniel Spannbauer <ds(a)marco.de> wrote: > Am 10/9/19 um 10:15 AM schrieb Ancor Gonzalez Sosa: > > > >> But how can I do this via autoyast? > > Specify a partition with format=false (you don't want a filesystem) and > > partition_id=263 (AutoYaST value for bios-boot). > > > > https://documentation.suse.com/sles/15-SP1/single-html/SLES-autoyast/#ay-pa… > > > > Cheers. > > > Hello, > > > first of all: thanks, I will try this. > > Where did you find the 263 for bios-boot? Hi, value should be specified at https://documentation.suse.com/sles/15-SP1/single-html/SLES-autoyast/#ay-pa… but sadly, it is missing. So something we should improve. ( BTW we read value from source code ) Josef > > > Regards > > > Daniel > > > -- 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 86
by Imobach González Sosa 09 Oct '19

09 Oct '19

Another YaST development sprint is over, so it is time to summarize what has happened during these two weeks. These are the highlights: Now that you had a chance to look at our post about Advanced Encryption * Improving support for multi-device file systems in the expert partitioner. * Fixing networking, secure boot and kdump problems in AutoYaST. * Stop waiting for chrony during initial boot when it does not make sense. * Preparing to support the split of configuration files between /usr/etc and /etc. * Using /etc/sysctl.d to write YaST related settings instead of the /etc/sysctl.conf main file. As usually, you can find the whole report at lizards.opensuse.org: https://lizards.opensuse.org/2019/10/09/highlights-of-yast-development-spri… Enjoy! Regards, Imo -- Imobach González Sosa YaST Team at SUSE LINUX GmbH https://imobachgs.github.io/

1 0

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 October 2019