September 2021 - 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

Github Actions Broken
by josef Reidinger 03 Nov '21

03 Nov '21

Hi, just to clarify why now all github actions are red. It is caused by TW glibc update. See for more info https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/… I expect we need to use again 15.3 workaround or wait till github apply patch. Josef

4 5

Rejected maintenance requests
by Ancor Gonzalez Sosa 29 Sep '21

29 Sep '21

I got a list of all the rejected maintenance requests for packages with name "yast2*" in 2021. Then I manually filtered out those which IBS projects are currently in sync with the repository branch (since I assume there was a follow-up request that fixed the problem). These ones still remain to be fixed. Note not all of them correspond to the problem building in i586, there are also other kind of problems. In fact, I'm not even sure if this list includes all the maintenance updates blocked by the i586 problem. Out of sync in SLE-15-GA * yast2-pkg-bindings Out of sync in SLE-15-SP1 * yast2-pkg-bindings Out of sync in SLE-15-SP2 * autoyast2 * yast2-network * yast2-packager Out of sync in SLE-15-SP3 * autoyast2 * yast2-add-on * yast2-country * yast2-installation * yast2-theme * yast2-network * yast2-packager * yast2-schema Branches are not matched to IBS projects as expected * yast2-migration - Looks like it was not correctly branched into SLE-15-SP3 back then * yast2-rear - Problems due to branches when submitting to SLE-12-SPX (yes, 12) * yast2-python-bindings - Branches are messy Cheers. -- Ancor González Sosa YaST Team at SUSE Software Solutions

1 0

YaST: highlights of development sprints 131 & 132
by Ancor Gonzalez Sosa 28 Sep '21

28 Sep '21

Again, the YaST Team combines the information from the two latest sprints into a single blog post, including: - Rethinking some internals in several areas - Heavy work (still in progress) on yast2-users - Improvements in the way YaST handles libYUI plugins - A visual fix in the packages manager - More progress in the release tools Check the full report at https://yast.opensuse.org/blog/2021-09-28/sprints-131-132 Cheers -- Ancor González Sosa YaST Team at SUSE Linux GmbH

1 0

Pending Pull Requests
by yast-ci＠opensuse.org 27 Sep '21

27 Sep '21

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-devtools: - Set %yast_icondir to /usr/share/icons/hicolor (bsc#1186066) (60 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (26 days) https://github.com/yast/yast-journal/pull/45

1 0

coveralls.io is having database issues
by Imobach Gonzalez Sosa 21 Sep '21

21 Sep '21

Hi all, JFYI, it looks like coveralls.io is having serious issues with its database. So if you get a "405 Not Allowed" error when trying to submit a coverage report, like we do through GitHub Actions[1], it will be most likely related to those problems. Let's hope they can recover soon. You can check the progress at their status page[2]. Regards, Imo [1] https://github.com/yast/yast-autoinstallation/pull/793/checks?check_run_id=… [2] https://status.coveralls.io/ -- Imobach González Sosa YaST Team at SUSE LLC https://imobachgs.github.io/

2 1

poor UX in case of fatal error during installation
by jsmeix 21 Sep '21

21 Sep '21

Hello, today morning I did a somewhat older openSUSE Tumbleweed Snapshot20210423 test installation on a KVM virtual machine. Something went wrong during package installation but I could not read the error message because YaST exited and about one second later I was in linuxrc with its ncurses Error/Exit screen. Because what I actually wanted to do is to "just try out something on Tumbleweed" but that error exit interrupted my ongoing work so I did not do a major mental task switch to dig out the error message and YaST logs. Instead I simply exited and retried with an up to date openSUSE Tumbleweed Snapshot20210914 which worked. I guess the error was so fatal that YaST could not do anything else than to exit straight. But the UX is poor in such cases because in practice it is then basically impossible for the user to make a meaningful issue report. I wished there was an easy way how to get the error message and YaST logs out of the installation system in such cases. The installation system had Internet access so if there was some YaST error exit dialog where error message and YaST logs could be sent e.g. to any email address or something similar (which the user could enter/specify as he likes), then it would be easy for the user to make later (after he completed his current actual task) a meaningful issue report. Kind Regards Johannes Meixner -- SUSE Software Solutions Germany GmbH Maxfeldstr. 5 - 90409 Nuernberg - Germany (HRB 36809, AG Nuernberg) GF: Felix Imendoerffer

5 7

Pending Pull Requests
by yast-ci＠opensuse.org 20 Sep '21

20 Sep '21

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-devtools: - Set %yast_icondir to /usr/share/icons/hicolor (bsc#1186066) (53 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (19 days) https://github.com/yast/yast-journal/pull/45

1 0

How to add custom menu category in yast control centre in SLES 15 SP3 and openSUSE Leap 15.3
by Gaurav Kumar 17 Sep '21

17 Sep '21

Hi Team, How to add custom menu category in YaST Control Centre in SLES 15 SP3 and openSUSE Leap 15.3? We need a custom Category in YaST Control Centre in SLES 15 SP3, so that we can place our custom application under that Category. In SLES 12 SP5 we were able to achieve this by creating a custom.menu file having Menu Name, Directory, Category and placing that menu file under /etc/xdg/menus/YaST-gnome-merged Since yast2-control-center-gnome has been deprecated in SLES15SP3 the above workaround is not working here. Regards, Gaurav

2 1