June 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-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

Libyui tabs
by Ancor Gonzalez Sosa 15 Jul '21

15 Jul '21

As you may know, this pull request in libyui brought nicer tabs in Qt that rely on QTabWidget https://github.com/libyui/libyui/pull/31 As explained there, some hacks were needed because the philosophy of tabs in Qt is different from the one in libyui. With Qt, the widgets contained in all tabs exist in memory (they keep their state and can be referenced) as long as the group of tabs exists. Changing between tabs is controlled by Qt itself (mostly transparent to the program) and its just a matter of which widgets are visible and which are not. In some sense, switching tabs is not so different from scrolling a screen - some widgets will become visible and other will not be longer in the spotlight, but all widgets are still there. With libyui, switching a tab is just an event and it's program responsibility to actually redraw the content below the tabs. Something that is done thanks to the usage of replace points and that implies destroying all the visible widgets and creating new ones to be drawn in their places. If the program is using CWM (which offers an extra abstraction layer on top of libyui with it's own sequence of events), that means that for every widget that becomes hidden (destroyed, actually) a "validate" and a "store" events are triggered. On the other hand, the status of every widget that becomes visible (created again, actually) must be initialized based on an "init" event (apart from calling the constructor, the usual calls to "content", etc.). While reviewing the changes in libyui we came to the question of whether it would be actually better to adopt the Qt philosophy in libyui. Maybe with an alternative widget (to not completely break backwards compatibility and CWM tabs). What do you think? Would it be worth considering? Cheers -- Ancor González Sosa YaST Team at SUSE Software Solutions

2 1

YaST: highlights of development sprint 126
by Ancor Gonzalez Sosa 28 Jun '21

28 Jun '21

As the main highlight for this sprint, the YaST team finished the first phase of the reworked management of users and groups in (Auto)YaST. Check all the details at https://yast.opensuse.org/blog/2021-06-28/sprint-126 Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH

1 0

Pending Pull Requests
by yast-ci＠opensuse.org 28 Jun '21

28 Jun '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-cluster: - Fix crypto hash and select type 4.4.1 (9 days) https://github.com/yast/yast-cluster/pull/98 Pending requests in repository yast-devtools: - Set %yast_icondir to /usr/share/icons/hicolor (bsc#1186066) (41 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-drbd: - packaging: Do not build for i586 and s390 (37 days) https://github.com/yast/yast-drbd/pull/32 Pending requests in repository yast-firstboot: - Adapt root and user clients to Y2User (6 days) https://github.com/yast/yast-firstboot/pull/123 Pending requests in repository yast-installation: - Adapt to Y2Users (9 days) https://github.com/yast/yast-installation/pull/969 - Avoid conflicts with filesystem and hicolor-icon-theme (bsc#1184786) (39 days) https://github.com/yast/yast-installation/pull/958 - Replace old splash commands with plymouth ones (159 days) https://github.com/yast/yast-installation/pull/904 Pending requests in repository yast-instserver: - Adapt Rakefile and Dockerfile for SLE-15-SP2 (226 days) https://github.com/yast/yast-instserver/pull/50 Pending requests in repository yast-network: - Removed unused methods and imports. (33 days) https://github.com/yast/yast-network/pull/1221 Pending requests in repository yast-online-update: - Improved openSUSE/SLE detection (bsc#1184243) (87 days) https://github.com/yast/yast-online-update/pull/35 - Added recommends to yast2-online-update-frontend (bsc#1177997) (235 days) https://github.com/yast/yast-online-update/pull/33 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (268 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-python-bindings: - Fix backtrace formatting in YPython::PyErrorHandler() (Merge SLE-15-SP3 into master) (87 days) https://github.com/yast/yast-python-bindings/pull/39 - Fix backtrace formatting in YPython::PyErrorHandler() (Merge SLE-15-SP2 into SLE-15-SP3) (87 days) https://github.com/yast/yast-python-bindings/pull/38 Pending requests in repository yast-theme: - Fix the icons' style and minify them (71 days) https://github.com/yast/yast-theme/pull/143 - Add pattern-budgie icon (boo#1176164) (129 days) https://github.com/yast/yast-theme/pull/131 Pending requests in repository yast-ycp-ui-bindings: - Failing autowrap (201 days) https://github.com/yast/yast-ycp-ui-bindings/pull/64 - New UI Example for ComboBox (216 days) https://github.com/yast/yast-ycp-ui-bindings/pull/62 Pending requests in repository skelcd-control-openSUSE: - Add support for riscv64 (51 days) https://github.com/yast/skelcd-control-openSUSE/pull/241 - Ntp servers (167 days) https://github.com/yast/skelcd-control-openSUSE/pull/223 Pending requests in repository yast-auth-server: - Fix an issue where pkg dependencies were not install (275 days) https://github.com/yast/yast-auth-server/pull/63 - Fixes to make the YaST modules work (732 days) https://github.com/yast/yast-auth-server/pull/48 Pending requests in repository yast.github.io: - Move IRC to Libera.chat (11 days) https://github.com/yast/yast.github.io/pull/291 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (265 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository yast-storage-ng: - Partial fix for bug#176140 (222 days) https://github.com/yast/yast-storage-ng/pull/1166 Pending requests in repository helper_scripts: - [dependencies] Bump nokogiri from 1.11.3 to 1.11.4 in /jekyll (39 days) https://github.com/yast/helper_scripts/pull/28 Pending requests in repository patterns-yast: - Make x11_yast pattern visible (bsc#1186343) (33 days) https://github.com/yast/patterns-yast/pull/35 Pending requests in repository skelcd-control-leanos: - Default ntp servers (167 days) https://github.com/yast/skelcd-control-leanos/pull/72 Pending requests in repository yast-rmt: - use docker image from OBS (285 days) https://github.com/yast/yast-rmt/pull/50 - Enforce full coverage (285 days) https://github.com/yast/yast-rmt/pull/40 Pending requests in repository skelcd-control-MicroOS: - sync with SLE (207 days) https://github.com/yast/skelcd-control-MicroOS/pull/27 - unify proposed partition sizes with openSUSE MicroOS (208 days) https://github.com/yast/skelcd-control-MicroOS/pull/26 Pending requests in repository skelcd-control-SMO: - install the microos-selinux pattern by default (67 days) https://github.com/yast/skelcd-control-SMO/pull/6

1 0

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

21 Jun '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) (34 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-drbd: - packaging: Do not build for i586 and s390 (30 days) https://github.com/yast/yast-drbd/pull/32 Pending requests in repository yast-installation: - Avoid conflicts with filesystem and hicolor-icon-theme (bsc#1184786) (32 days) https://github.com/yast/yast-installation/pull/958 - Replace old splash commands with plymouth ones (152 days) https://github.com/yast/yast-installation/pull/904 Pending requests in repository yast-instserver: - Adapt Rakefile and Dockerfile for SLE-15-SP2 (219 days) https://github.com/yast/yast-instserver/pull/50 Pending requests in repository yast-network: - Removed unused methods and imports. (26 days) https://github.com/yast/yast-network/pull/1221 Pending requests in repository yast-online-update: - Improved openSUSE/SLE detection (bsc#1184243) (80 days) https://github.com/yast/yast-online-update/pull/35 - Added recommends to yast2-online-update-frontend (bsc#1177997) (228 days) https://github.com/yast/yast-online-update/pull/33 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (261 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-python-bindings: - Fix backtrace formatting in YPython::PyErrorHandler() (Merge SLE-15-SP3 into master) (80 days) https://github.com/yast/yast-python-bindings/pull/39 - Fix backtrace formatting in YPython::PyErrorHandler() (Merge SLE-15-SP2 into SLE-15-SP3) (80 days) https://github.com/yast/yast-python-bindings/pull/38 Pending requests in repository yast-theme: - Fix the icons' style and minify them (64 days) https://github.com/yast/yast-theme/pull/143 - Add pattern-budgie icon (boo#1176164) (122 days) https://github.com/yast/yast-theme/pull/131 Pending requests in repository yast-ycp-ui-bindings: - Failing autowrap (194 days) https://github.com/yast/yast-ycp-ui-bindings/pull/64 - New UI Example for ComboBox (209 days) https://github.com/yast/yast-ycp-ui-bindings/pull/62 Pending requests in repository skelcd-control-openSUSE: - Add support for riscv64 (44 days) https://github.com/yast/skelcd-control-openSUSE/pull/241 - Ntp servers (160 days) https://github.com/yast/skelcd-control-openSUSE/pull/223 Pending requests in repository yast-auth-server: - Fix an issue where pkg dependencies were not install (268 days) https://github.com/yast/yast-auth-server/pull/63 - Fixes to make the YaST modules work (725 days) https://github.com/yast/yast-auth-server/pull/48 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (258 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository yast-storage-ng: - Partial fix for bug#176140 (215 days) https://github.com/yast/yast-storage-ng/pull/1166 Pending requests in repository helper_scripts: - [dependencies] Bump nokogiri from 1.11.3 to 1.11.4 in /jekyll (32 days) https://github.com/yast/helper_scripts/pull/28 Pending requests in repository patterns-yast: - Make x11_yast pattern visible (bsc#1186343) (26 days) https://github.com/yast/patterns-yast/pull/35 Pending requests in repository skelcd-control-leanos: - Default ntp servers (160 days) https://github.com/yast/skelcd-control-leanos/pull/72 Pending requests in repository yast-rmt: - use docker image from OBS (278 days) https://github.com/yast/yast-rmt/pull/50 - Enforce full coverage (278 days) https://github.com/yast/yast-rmt/pull/40 Pending requests in repository skelcd-control-MicroOS: - sync with SLE (200 days) https://github.com/yast/skelcd-control-MicroOS/pull/27 - unify proposed partition sizes with openSUSE MicroOS (201 days) https://github.com/yast/skelcd-control-MicroOS/pull/26 Pending requests in repository skelcd-control-SMO: - install the microos-selinux pattern by default (60 days) https://github.com/yast/skelcd-control-SMO/pull/6

1 0

YaST: highlights of development sprint 125
by Ancor Gonzalez Sosa 17 Jun '21

17 Jun '21

Time flies and another two weeks of YaST development have passed. Apart from learning and experimenting with technologies that will shape the role of Linux installers in the future, the YaST team fixed quite some bugs and made some progress in the following features: - Simplified support for hibernation - Make network forwarding configurable in the installer - Improved tabs in graphical mode - Progress in the rewrite of yast2-users Check the full report at https://yast.opensuse.org/blog/2021-06-17/sprint-125 Cheers. PS.- And remember openSUSE Virtual Conference 2021 starts tomorrow! https://events.opensuse.org/conferences/oSVC21 -- Ancor González Sosa YaST Team at SUSE Linux GmbH

1 0

Quick look at 15.3 retrospective
by josef Reidinger 16 Jun '21

16 Jun '21

Hi, raw data[1] was published for Leap 15.3 retrospective and I use that opportunity to look into it if there is something related to yast. General impression is that people are in general not so happy about older versions of some packages and that update repos are confusing. Also some people do not update before upgrade and there was quite lot complains about conflicts in patches caused by some SLE patches. Yast Specific feedback (unsorted): - Lack of translations EVEN THOUGH I am the (Finnish) translator! Some strings are missing even though I am sure they’ve been in the localization files for a long time. Like the system roles (KDE Plasma, GNOME, Xfce): they were translated in time for Leap 15.2 and remain translated in Weblate, so why are the strings not being used? - yast settings like ratbagctl (NOTE: in section "what is not going well" and to be honest I do not get what reporter mean, if someone has clue. Maybe missing yast module for configurable mouses? ) - I have very old hardware Dell Inspiron 1525 which had Leap 15.2 installed and the upgrade to Leap 15.3 via external USB and choosing upgrade went very smoothly. The NET image was available just a few hours after launch when I tried and I had no hiccups during the download of packages here in India. All in all this method worked well for me. ( NOTE: as negative was that zypper dup failed for that user due to need of more repos and failed to do it properly. So he do snapper rollback and use usb for upgrade ) - After installation I checked for updates and got error messages that 1. a dependency for a file could not be resolved (can't remember which one). 2. no data for NonOSS and NonOSS update repositories could be found, I then replaced the "$_releaseserver" in the URL with "15.3" and it worked - I cannot install or boot it on my laptop because of the shim issue https://bugzilla.opensuse.org/show_bug.cgi?id=1185232 so I unfortunately am using Fedora until opensuse is fixed - guided installing to disk. no major changes with installer probably a good thing - The installer did not recognize my internal ssd and could not install. My device is an Acer Aspire 5 A515-56-56DJ. - 1.I did a new install.Re-install (It clears out old rubbish). It worked but the install instructions need MUCH more clarity, to BOTH reformat root"/", mount it, THEN SELECT snapshots in pop up, then select to mount swap and /home or you get mini installation in old root "/" without "/home" being added and without snapshots. 2. This ability to only add snapshots AFTER you select mount "/" is bad it needs it own clear box. The instructions should say snapshots wanted as a BOX on the page, before ticking 'mount'. then if low storage a reply "snapshots not available due storage limits" can be displayed 3. I experimented (with a friend) and found why others missed this 'snapshot' enable process. - * Yast team was always super responsive. Thanks to zypper team for fixing a lot of last minute issues. - Did an offline upgrade; the installer didn’t manage to install some packages (six libX packages, I forgot the exact ones) from the SUSE repository but otherwise successfully completed the installation. When starting YaST the first time, it notified about the missing libX-packages and prompted to install them, which it successfully did. Also there seems to be a problem with some libreoffice packages (libreoffice-icon-themes, and libreoffice localisations) being available in a newer version than the main libreoffice package, making them impossible to update. Additionally, zypper up wants to remove yast2-trans-en and install yast2-trans. YaST, however, marks yast2-trans as unneeded and wants to replace it with yast2-trans. - almost translated installer download packages while installing clever disk partitioner in installer repository filter in yast software install updates by one-click in taskbar boot linux system easily by linuxrc in installer media ( NOTE: in positive, negative follows, non yast related stuff is filtered out ) can't hide grub loading message installer will install ibus ime,but it can't change theme.installer should install fcitx mute led in keyboard isn't working kde connect can't connect to phone,I should modify firewall setting gnome edition can't display all yast settings in my pc - a) the partition manager, if you use your own layout, is... uncomfortable, at least. - 2 - the ${releasever} feature in repo file is very good - The hardware detection and driver loading part of the installing took way too long. when I try to open YaST software management and It's already being used I get a ruby error instead of a proper error message saying that it is already being used. I hope you find it useful and maybe for some issues it makes sense to create proper bug reports? Josef [1] https://en.opensuse.org/Portal:15.3/Retrospective

1 0