YaST Development November 2019

yast-devel@lists.opensuse.org

11 participants
11 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] How deal with modules executed without enough permissions?
by David Díaz 05 Dec '19

05 Dec '19

Hi there! Today, while I was working to fix an issue when executing "yast2 system_settings" without enough permissions[1][2], some questions arose to my mind. Let me share them, * If I run "/usr/sbin/yast2" it warns about the permissions and only shows a few modules[3]. So, * Can we manage [1] and [2] in a "centralized" way? I mean, do we have a way to know in advance when the execution of a certain module will require root permissions? If the answer is NO, * Can we open a discussion/research/whatever to do something to this regard? Do you think it worth it? Or do you already had such discussions in the past? If so, what was the conclusion? Apart from these questions, a little bit off-topic but also related to the topic, I found weird that "yast2 storage" prompt a warning[4] saying > The storage subsystem is locked by an unknown application. > You must quit that application before you can continue. > > Would you like to abort or try again? when it is executed as a normal user. Actually is a problem with permissions, not an "unknown application locking the storage subsystem". Waiting for your inputs, thanks in advance. See you. [1] https://github.com/yast/yast-tune/pull/40 [2] https://github.com/yast/yast-bootloader/pull/583 [3] https://gist.github.com/dgdavid/323e5aa879490e24ea2d0d520550e1fe#gistcommen… [4] https://gist.github.com/dgdavid/323e5aa879490e24ea2d0d520550e1fe#gistcommen… -- David Díaz González YaST Team at SUSE Linux GmbH

6 10

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

25 Nov '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 (163 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-autoinstallation: - [WIP] Count extended partition when determining if partitions fit (9 days) https://github.com/yast/yast-autoinstallation/pull/546 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (130 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-country: - Port to rake (130 days) https://github.com/yast/yast-country/pull/217 Pending requests in repository yast-devtools: - Associate metadata to desktop files, for appstream builder (75 days) https://github.com/yast/yast-devtools/pull/147 - Move desktop files (168 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-firstboot: - Don't use deprecated Progress.on (38 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… (200 days) https://github.com/yast/yast-installation/pull/796 - Demo: eager mode of zombie-killer 0.5 (381 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - add initial test cases document (129 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-online-update-configuration: - Prompt for root password. (222 days) https://github.com/yast/yast-online-update-configuration/pull/21 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (30 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-squid: - packaging: remove SuSEfirewall2 artifacts (121 days) https://github.com/yast/yast-squid/pull/30 Pending requests in repository yast-users: - Move back the UMASK default value to /etc/login.defs (bsc#1099153) (508 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 Sprint 89+90 Report
by Martin Vidner 22 Nov '19

22 Nov '19

* The System Role selection dialog got usability improvements * and we added a CustomStatusItemSelector to the widget library in the process. * Snapper gained machine-readable output * Storage: * remote encrypted devices are activated properly at boot time * random and pervasive encryption also supported in AutoYaST * improved support for AutoYaST Guided Partitioning https://lizards.opensuse.org/2019/11/22/highlights-of-yast-development-spri… -- Martin Vidner, YaST Team http://en.opensuse.org/User:Mvidner

1 0

[yast-devel] YaST feedback/selling point on reddit/openSUSE
by Arvin Schnell 18 Nov '19

18 Nov '19

Hi, there is a discussion about what is so special about YaST: https://old.reddit.com/r/openSUSE/comments/dsni1k/what_is_so_special_about_… ciao Arvin -- Arvin Schnell, <aschnell(a)suse.com> Senior Software Engineer, Research & Development SUSE Software Solutions Germany GmbH Maxfeldstraße 5 90409 Nürnberg Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer -- 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] No way to display unneeded/orphan packages after Package Groups were removed from YaST
by Andrei Borzenkov 16 Nov '19

16 Nov '19

Orphaned/unneeded and some other package classes were integrated in Package Groups view (I understand as sort of "meta-groups"). In current TW (I have now 20191112) there is no more Package Groups - no way to display this information anywhere else. Was it really intentional? This was useful functionality. ... there seems to be Repositories - @System - "Unmaintained Packages"; this list looks like what was called orphaned packages in the past. Is it correct and it is where orphans are shown now? Still am not sure whether there is something like "unneeded". -- 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 11 Nov '19

11 Nov '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 (149 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-autoinstallation: - Remove old workaround (11 days) https://github.com/yast/yast-autoinstallation/pull/535 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (116 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-country: - Port to rake (116 days) https://github.com/yast/yast-country/pull/217 Pending requests in repository yast-devtools: - Associate metadata to desktop files, for appstream builder (61 days) https://github.com/yast/yast-devtools/pull/147 - Move desktop files (154 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-firstboot: - Don't use deprecated Progress.on (24 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… (186 days) https://github.com/yast/yast-installation/pull/796 - Demo: eager mode of zombie-killer 0.5 (367 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - Live instalation: Make network more useful (10 days) https://github.com/yast/yast-network/pull/997 - network-ng: test cases document (draft) (20 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (115 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-online-update-configuration: - Prompt for root password. (208 days) https://github.com/yast/yast-online-update-configuration/pull/21 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (16 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-registration: - WIP: Decreasing required memory (6 days) https://github.com/yast/yast-registration/pull/457 Pending requests in repository yast-squid: - packaging: remove SuSEfirewall2 artifacts (107 days) https://github.com/yast/yast-squid/pull/30 Pending requests in repository yast-update: - [RFC] Move the target /etc/resolv.conf to /run (73 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) (494 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] Default config in /usr/etc vs. YaST
by Andrei Borzenkov 04 Nov '19

04 Nov '19

I wonder was it coordinated with YaST? The first fallout is YaST Users and Security modules which now default to DES password encryption due to missing /etc/login.defs. I am not even sure what the right semantic should be, given that users now can create multiple files each containing single parameter so anything done via YaST is not guaranteed to actually have any effect. https://bugzilla.opensuse.org/show_bug.cgi?id=1155735 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 1

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