August 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

Revamping yast2-users: the UI
by David Díaz 14 Sep '21

14 Sep '21

Hi there! In the context of revamping yast2-users[1], I spent some days looking for an alternative layout that could help to improve the current UI by reducing the number of tabs and grouping form fields to make better use of available space. However, due to our resolution constraints (UI must fit well in an 80x24 terminal) and some UI library limitations[2], looks like there is not too much room for big changes and our best bet is to keep the layout almost as it is, just making some necessary adjustments[3]. Summarizing them a lot, those changes will consist of adding a top menu bar for making easier the user navigation, moving all settings to the same dialog, improving filters by using a popup, making small changes in forms, and adding some summary views. Of course, nothing is written in stone and it would be nice to know your feedback and/or ideas too. So, please, keep reading the following links if you are interested and tell us what do you think. Is there anything we overlooked? Some other ideas we should evaluate? Remember that you can reach us by email, on IRC, or even by directly leaving a comment in those Github issues. Thanks! [1] "Revamping yast2-users" mailing list thread - https://lists.opensuse.org/archives/list/yast-devel@lists.opensuse.org/thre… [2] "UI library limitations" https://github.com/yast/yast-users-ng/issues/8 [3] "Revamping yast2-users UI: an initial proposal" https://github.com/yast/yast-users-ng/issues/6 -- David Díaz YaST Team at SUSE LINUX GmbH IRC: dgdavid

1 1

YaST: highlights of development sprints 129 & 130
by Ancor Gonzalez Sosa 31 Aug '21

31 Aug '21

Curious about the summer activities of the YaST Team? Housekeeping, learning and much more in a new report from the YaST trenches at: https://yast.opensuse.org/blog/2021-08-31/sprints-129-130 Highlights include: * Better management of the Help button in text mode * Improved unmounting of file-systems at the end of installation * More robust handling of progress bars * Integrating contributions made by our users * Learning and improving the Release Tools Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH

1 0

[yast-devel] https://en.opensuse.org/SDB:Linuxrc in need of edit???
by Felix Miata 30 Aug '21

30 Aug '21

NameScheme=by-label on installer cmdline has had no effect I have observed for a lot longer than I can remember, several years at least, continuing in 15.3 build 117.13. Has it been removed and the linuxrc page need matching update? Is this a broken installer option? Am I not understanding why it's listed on the linuxrc page? Shouldn't it prevent me from needing to change default mount by in the expert partitioner? -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

2 1

Preventing from running the same module twice
by Lukas Ocilka 30 Aug '21

30 Aug '21

Hi, While checking and refining some older bugs and feature request with David and Ancor, we came across an interesting one: *Prevent the same YaST module from running twice at the same time* We've been discussing the topic back and forth, identified some use-cases in which it would make sense, a few technical solutions and even more obstacles, but we decided it would make sense to ask for opinions at YaST Devel first. Why to prevent from running the same twice? - Some may click too fast and run two or more at the same time -> here you instantly see more modules starting - Some may start a YaST module, then do something else, overlook the first one, start another, ... then hard to say which one wins at the end and what would be the changes --> is that likely? - Two admins could run the same module without knowing about each other --> this may happen in remote session at COVID times How to prevent from running them more times? - Logging the PID, storing it at some file (module/client name), checking at startup (more PIDs in case of more sessions of the same?) - Either at YaST startup scripts (easier) or YaST core (some might skip using a startup script, is that likely?) - Showing a message (another special client) and offering some options, e.g., kill the other session, exiting - Offering a read-only mode (quite hard) for the second session - Another idea was to bring the UI to the front (only possible with Qt) instead of starting a new one Some possible problems - Some admins really just run YaST to see the current configuration, so preventing from running something twice might not be an option - Some YaST modules can be called from within another ones, e.g., Repositories from the Packager, what to do with that? - Some YaST modules can be called as a user; what if the user differs? Quite some unknowns as you may see :) Is that worth it? Is there a simpler solution? Would that fit? Links - https://bugzilla.suse.com/show_bug.cgi?id=959866 - https://jira.suse.com/browse/SLE-2999 (internal) Thanks for your opinions Lukas -- Lukas Ocilka, Systems Mgmt & Consulting Team Leader & YaST Product Owner SLE Department, SUSE Linux

4 3

Pending Pull Requests
by yast-ci＠opensuse.org 29 Aug '21

29 Aug '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) (32 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-online-update: - Added recommends to yast2-online-update-frontend (bsc#1177997) (12 days) https://github.com/yast/yast-online-update/pull/33 Pending requests in repository yast-ycp-ui-bindings: - New UI Example for ComboBox (32 days) https://github.com/yast/yast-ycp-ui-bindings/pull/62 Pending requests in repository skelcd-control-openSUSE: - Ntp servers (230 days) https://github.com/yast/skelcd-control-openSUSE/pull/223 Pending requests in repository skelcd-control-leanos: - Default ntp servers (230 days) https://github.com/yast/skelcd-control-leanos/pull/72 Pending requests in repository yast-rmt: - use docker image from OBS (32 days) https://github.com/yast/yast-rmt/pull/50 - Enforce full coverage (32 days) https://github.com/yast/yast-rmt/pull/40

1 0

Pending Pull Requests
by yast-ci＠opensuse.org 22 Aug '21

22 Aug '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) (25 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-installation: - Replace old splash commands with plymouth ones (25 days) https://github.com/yast/yast-installation/pull/904 Pending requests in repository yast-online-update: - Improved openSUSE/SLE detection (bsc#1184243) (25 days) https://github.com/yast/yast-online-update/pull/35 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (25 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-theme: - Add pattern-budgie icon (boo#1176164) (25 days) https://github.com/yast/yast-theme/pull/131 Pending requests in repository yast-ycp-ui-bindings: - Failing autowrap (25 days) https://github.com/yast/yast-ycp-ui-bindings/pull/64 - New UI Example for ComboBox (25 days) https://github.com/yast/yast-ycp-ui-bindings/pull/62 Pending requests in repository skelcd-control-openSUSE: - Ntp servers (223 days) https://github.com/yast/skelcd-control-openSUSE/pull/223 Pending requests in repository rubocop-yast: - Move from Travis to GitHub Actions (13 days) https://github.com/yast/rubocop-yast/pull/5 Pending requests in repository helper_scripts: - [dependencies] Bump addressable from 2.7.0 to 2.8.0 in /jekyll (25 days) https://github.com/yast/helper_scripts/pull/30 - [dependencies] Bump nokogiri from 1.11.3 to 1.11.4 in /jekyll (25 days) https://github.com/yast/helper_scripts/pull/28 Pending requests in repository skelcd-control-leanos: - Default ntp servers (223 days) https://github.com/yast/skelcd-control-leanos/pull/72 Pending requests in repository yast-rmt: - use docker image from OBS (25 days) https://github.com/yast/yast-rmt/pull/50 - Enforce full coverage (25 days) https://github.com/yast/yast-rmt/pull/40 Pending requests in repository skelcd-control-MicroOS: - sync with SLE (13 days) https://github.com/yast/skelcd-control-MicroOS/pull/27

1 0

Ruby 2.7 removes profiler
by josef Reidinger 20 Aug '21

20 Aug '21

Hi, just come when debugging some slowdown in yast[1] that ruby 2.7 ( one in TW ) removes profiler. What is result? Y2PROFILER=1 no longer works. Do you know about any lightweigth alternative? Advantage of builtin profiler was that was part of ruby, so no additional dependencies are needed. Josef [1] https://bugzilla.suse.com/show_bug.cgi?id=1189617#c6

1 0

Help for closing old and open PRs
by David Díaz 17 Aug '21

17 Aug '21

Hi folks! ## TL;DR YaST team is trying to merge or close old and open[1] PR against YaST modules. Jump to the "Current status" section to see if you can help. Thanks in advance! ## The long story As probably you already know, this mailing list receives a weekly reminder about YaST "Pending Pull Requests" to encourage us, the YaST team and the maintainers of YaST modules, to review not only the started work on our side but also the external contributions. However, IMHO, still receiving almost the same long and outdated list every Monday makes it useless. That's why during the YaST sprint 129 I went through the list in an attempt to bring help either, closing if not relevant anymore or moving them forward. To do so, I have been trying to reach involved people through Github mentions. But I fully understand that it's the holidays season for most of us, and maybe the Github notification is missing among other ones. That's why I'm sending this mail, to increase my opportunities of reaching you out ;) So please, if you had open a PR against a YaST module or are in charge of some modules, keep reading the current status and take a moment to see if you can help. If not, maybe you can just spread the word :) ## Current status After going through the 33 open PRs linked in the "Pending Pull Request" mail received on July 26th 2021[2], the current status is * 4 has been already merged - https://github.com/yast/patterns-yast/pull/35 - https://github.com/yast/yast-country/pull/273 - https://github.com/yast/yast-drbd/pull/32 - https://github.com/yast/yast-network/pull/1221 * 2 are waiting for a review - https://github.com/yast/skelcd-control-openSUSE/pull/241 - https://github.com/yast/yast-installation/pull/958 * 4 has been already reviewed but still waiting for the author/maintainer for an action - https://github.com/yast/yast-installation/pull/904 - https://github.com/yast/yast-python-bindings/pull/38 - https://github.com/yast/yast-python-bindings/pull/39 - https://github.com/yast/yast-auth-server/pull/63 * 6 are waiting for an answer from the author/maintainer to know if it must be closed - https://github.com/yast/helper_scripts/pull/28 - https://github.com/yast/helper_scripts/pull/30 - https://github.com/yast/skelcd-control-MicroOS/pull/26 - https://github.com/yast/skelcd-control-MicroOS/pull/27 - https://github.com/yast/yast-rmt/pull/40 - https://github.com/yast/yast-rmt/pull/50 * 8 are waiting for information about the status of the PR or the author's intention - https://github.com/yast/yast-devtools/pull/161 - https://github.com/yast/yast-journal/pull/45 - https://github.com/yast/yast-online-update/pull/33 - https://github.com/yast/yast-online-update/pull/35 - https://github.com/yast/yast-packager/pull/482 - https://github.com/yast/yast-theme/pull/131 - https://github.com/yast/yast-ycp-ui-bindings/pull/62 - https://github.com/yast/yast-ycp-ui-bindings/pull/64 * 6 were manually closed - https://github.com/yast/skelcd-control-SMO/pull/6 - https://github.com/yast/yast-auth-server/pull/48 - https://github.com/yast/yast-instserver/pull/50 - https://github.com/yast/yast-storage-ng/pull/1166 - https://github.com/yast/yast-theme/pull/143 * 1 was automatically closed - https://github.com/yast/yast.github.io/pull/297 * 2 needs more work yet - https://github.com/yast/skelcd-control-leanos/pull/72 - https://github.com/yast/skelcd-control-openSUSE/pull/223 * 1 is related to a repo that (most probably) is going to be archived - https://github.com/yast/rubocop-yast/pull/5 BTW, Did you know about this module? I didn't but, although "it is more or less abandoned code", I found it somehow interesting to see that there "were" a Rubocop plugin intended for converting the automatic code conversion done by YCP Killer. Hopefully, we could manage to merge/close them and start taking a look to draft PRs[3] too :P Thanks a lot! Have a nice day! [1] https://github.com/pulls?q=is%3Aopen+is%3Apr+org%3Ayast+archived%3Afalse+-i… [2] https://lists.opensuse.org/archives/list/yast-devel@lists.opensuse.org/thre… [3] https://github.com/pulls?q=is%3Aopen+is%3Apr+org%3Ayast+archived%3Afalse+dr… -- David Díaz YaST Team at SUSE LINUX GmbH IRC: dgdavid

1 0