April 2022 - 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

Modified installation progress
by josef Reidinger 06 Jul '22

06 Jul '22

Challenge: ---------- Libzypp supports parallel download and install. Yast installation progress does not fit it at all [1]. Issues are secondary progress bar that does not work with parallel installation. Also there are overwhelming amount of information on screen that is quite distracting. That information is often wrong like time estimation. And also table for media is a bit useless nowadays as everything is on one iso/medium, so there is no need to see when cd switch will be needed. The details tab are the most visible as it is default one. Proposal: --------- Remove completely that details tab and keep just release notes one[2]. It contains release notes that contain useful information and also has just one progress bar. For that bar remove keep always just remaining size and count of packages, so user has idea how it does, but do not print what exactly is installing or any time estimation. If there are more release notes allow to switch between them. Also keep possibility to have slide show which we had in past for installation if someone create some ( when checked other OSes, the Ubuntu slide show during installation looks probably the best from user POV ). The same changes will apply to ncurses front end[3], we just need to check why formatting of release notes are so badly formatted. And same for opensuse[4] of course. Josef [1] https://pasteboard.co/cNBjER6SnLLT.png [2] https://pasteboard.co/WnI7wS7VVVqq.png [3] https://pasteboard.co/vzQvY1PaVDaD.png [4] https://pasteboard.co/FzEqcIN7Xnas.png

15 40

Talk for openSUSE Conference 2022
by Ancor Gonzalez Sosa 04 Jun '22

04 Jun '22

I plan to submit this. Feel free to provide feedback before I do it. Title: Almost two years of YaST News Subtitle: Recent changes and future plans at YaSTland Abstract: YaST, the flagship installer and configuration tool of openSUSE is in constant development. Just as its unattended companion AutoYaST. Although the YaST Team at SUSE tries to communicate progress as often as possible in the YaST Blog, it has been almost two years since we presented the "Top 25 New Features in (Auto)YaST" at openSUSE Conference 2020. So it's time for another live update! We will recap the main changes and new features that are already integrated into openSUSE Tumbleweed and that will be included at openSUSE Leap 15.4, to be released just a couple of days after the talk. We will also take a look to some ideas for future development... and we really need the feedback of the whole openSUSE community for that. So please join us and speak up! -- Ancor González Sosa YaST Team at SUSE Software Solutions

5 8

TRANSLATORS comments
by Ladislav Slezák 27 Apr '22

27 Apr '22

Hi all! TL;DR: Use the "TRANSLATORS" tag for marking the comments for translators. Full version: Currently we extract *all* preceding comments to the generated POT files. The side effect is that in some cases the comment contains the license header, Yardoc comments or even commented out code. That might be confusing for translators. The solution is to use some special tag and instruct gettext to extract the comments only following this special tag. We already use the "TRANSLATORS" tag in YaST for that. Example: # this comment is *not* copied to the POT file # TRANSLATORS: this comment *is* copied to the POT file # this *is* copied as well _("Translatable text") Unfortunately it is not used everywhere, when I tried to use it globally a lot of comments from POT files were lost. For that reason I have introduced the POTCOMMENTS file, similar to the existing POTFILES used in some repositories. That file should contain the tag name passed to gettext. I.e. it should just contain the "TRANSLATORS" value so it is the same in all repositories. If that file is missing the old approach (all comments) is used, so it is backward compatible and we can gradually fix the modules one by one. See https://github.com/yast/yast-devtools/pull/166 for the implementation details and https://github.com/yast/yast-firstboot/pull/136 as an example how it was fixed in one YaST module. Enjoy! Ladislav -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

2 1

Pending Pull Requests
by yast-ci＠opensuse.org 25 Apr '22

25 Apr '22

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) (76 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-installation: - Remake some icons (41 days) https://github.com/yast/yast-installation/pull/1028 Pending requests in repository yast-kdump: - Implement KDUMP_AUTO_RESIZE (24 days) https://github.com/yast/yast-kdump/pull/123 Pending requests in repository yast-packager: - Remake some icons (60 days) https://github.com/yast/yast-packager/pull/603 Pending requests in repository yast-pam: - Add a function to detect if the system runs a dual PAM stack (12 days) https://github.com/yast/yast-pam/pull/28 Pending requests in repository yast-storage: - Fix LVM VG resize (17 days) https://github.com/yast/yast-storage/pull/310 Pending requests in repository yast-theme: - Add pantheon desktop support (145 days) https://github.com/yast/yast-theme/pull/154 Pending requests in repository yast-update: - [SP3] Use the "norecovery" mount option (bsc#1195894) (68 days) https://github.com/yast/yast-update/pull/179 Pending requests in repository yast-auth-server: - Fix log path (30 days) https://github.com/yast/yast-auth-server/pull/72 Pending requests in repository yast.github.io: - [dependencies] Bump nokogiri from 1.13.3 to 1.13.4 (12 days) https://github.com/yast/yast.github.io/pull/321 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (75 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository helper_scripts: - [dependencies] Bump nokogiri from 1.13.3 to 1.13.4 in /jekyll (12 days) https://github.com/yast/helper_scripts/pull/38 Pending requests in repository yast-sap-ha: - SUSE SAP HA Yast wizard for HANA doesn´t configure the HANA hooks. (12 days) https://github.com/yast/yast-sap-ha/pull/7 Pending requests in repository system-role-common-criteria: - add a missing Wizard.CloseDialog (bsc#1194279) (6 days) https://github.com/yast/system-role-common-criteria/pull/7

1 0

How to localize pattern description in SLES 15 SP3
by Gaurav Kumar 20 Apr '22

20 Apr '22

Hello Team, In SLES 15 SP3, how are the patterns and package descriptions translated? Until SLES 12 SP5, we were modifying the package package-translations by merging the po files for a translated language and creating the package-translations-$lang.mo files In SLES 15 SP3, I tried to do the same, merging all po files for a translated language and creating the package-translations-$lang.mo files. Now in SLES 15 SP3 during installation, if I change the language I am not getting the translated description for the patterns. I would really appreciate it if you could help us understand how to localize our patterns and package descriptions. Regards, Gaurav.

2 2

Pending Pull Requests
by yast-ci＠opensuse.org 18 Apr '22

18 Apr '22

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) (69 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-installation: - Remake some icons (34 days) https://github.com/yast/yast-installation/pull/1028 Pending requests in repository yast-kdump: - Implement KDUMP_AUTO_RESIZE (17 days) https://github.com/yast/yast-kdump/pull/123 Pending requests in repository yast-packager: - Remake some icons (53 days) https://github.com/yast/yast-packager/pull/603 Pending requests in repository yast-storage: - Fix LVM VG resize (10 days) https://github.com/yast/yast-storage/pull/310 Pending requests in repository yast-theme: - Add pantheon desktop support (138 days) https://github.com/yast/yast-theme/pull/154 Pending requests in repository yast-update: - [SP3] Use the "norecovery" mount option (bsc#1195894) (61 days) https://github.com/yast/yast-update/pull/179 Pending requests in repository yast-auth-server: - Fix log path (23 days) https://github.com/yast/yast-auth-server/pull/72 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (68 days) https://github.com/yast/yast-journal/pull/45

1 0

Pending Pull Requests
by yast-ci＠opensuse.org 11 Apr '22

11 Apr '22

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) (62 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-installation: - Remake some icons (27 days) https://github.com/yast/yast-installation/pull/1028 Pending requests in repository yast-kdump: - Implement KDUMP_AUTO_RESIZE (10 days) https://github.com/yast/yast-kdump/pull/123 Pending requests in repository yast-packager: - Remake some icons (46 days) https://github.com/yast/yast-packager/pull/603 Pending requests in repository yast-pam: - Add a function to detect if the system runs a dual PAM stack (13 days) https://github.com/yast/yast-pam/pull/28 Pending requests in repository yast-theme: - Add pantheon desktop support (131 days) https://github.com/yast/yast-theme/pull/154 Pending requests in repository yast-update: - [SP3] Use the "norecovery" mount option (bsc#1195894) (54 days) https://github.com/yast/yast-update/pull/179 Pending requests in repository yast-auth-server: - Fix log path (16 days) https://github.com/yast/yast-auth-server/pull/72 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (61 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository yast-sap-ha: - SUSE SAP HA Yast wizard for HANA doesn´t configure the HANA hooks. (13 days) https://github.com/yast/yast-sap-ha/pull/7

1 0

SLE-15-SP4 branch created
by Ladislav Slezák 07 Apr '22

07 Apr '22

Hello! The SLE-15-SP4 branch has been created in all relevant YaST and libyui repositories. Affected changes: - The "master" branch is now autosubmitted only to Factory. - The SLE-15-SP4 branch is submitted to SLE-15-SP4 maintenance project, if you still need to submit a fix to GA then you need to do that manually ("rake osc:commit" + "osc sr Devel:YaST:SLE-15-SP4 <package> SUSE:SLE-15-SP4:GA" and reject that maintenance autosubmission). - The already open SP4 pull requests need to change the target branch. - The version in "master" was bumped to 4.5.0 (that might cause conflicts in the already opened pull requests) There are some additional improvements to the branching done in the past: - The SP4 branch was merged to master and the specific SP4 changes (Rakefile, GitHub Actions) were reverted. That means the first merge from SP4 to "master" will be a clean merge, no need to revert that changes manually. - The "openSUSE-15_4" branch has been created in the openSUSE Leap specific packages which are not present in SLE (yast-alternatives, yast-docker, yast-migration-sle, yast-slp-server). In the past the branching was missing for those... =:o If you find any problem related to the branching then just ping me. Enjoy! :-) Ladislav -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

2 1

D-Installer Roadmap at GitHub
by Imobach Gonzalez Sosa 06 Apr '22

06 Apr '22

Hi all, After last Tuesday meeting, I have tried to build a short-term roadmap for D-Installer. I put the first version of the roadmap in Confluence, but as we want to keep it public, I decided to give GitHub projects feature a try. You can find more information at GitHub documentation: https://docs.github.com/en/issues/trying-out-the-new-projects-experience Regarding D-Installer, here is the result: https://github.com/orgs/yast/projects/1 As you may see, I decided to just plan for three iterations and the dates are probably not realistic at all. We will adjust them as we go forward and gain more experience about the project. Regards, Imo -- Imobach González Sosa YaST Team at SUSE LLC https://imobachgs.github.io/

1 0