March 2023 - YaST Development - openSUSE Mailing Lists

D-Installer is now Agama
by Imobach Gonzalez Sosa 31 Mar '23

31 Mar '23

Hi all, It is not a secret that "D-Installer" was not the most loved name for the project. So after some discussions (and a previous failed attempt to find a better name), we have decided to rename the project to "Agama"[1]. As a consequence, D-Installer 0.8[2] was the last release with the old name. Yesterday, we released Agama 1 which is, basically, D-Installer 0.8 with small changes (and potential bugs) introduced by the renaming. Here you are some relevant links: * Repository: https://… [View More]

1 0

D-Installer 0.8 is out!
by Ancor Gonzalez Sosa 30 Mar '23

30 Mar '23

D-Installer will be renamed soon due to popular demand. But before that happens, we want to raise awareness of the new prototype 0.8 with many cool features like: - Preliminary support for unattended installation - Configuration of iSCSI - s390x support including management of DASDs - A brand new command-line interface - Improvements in the web interface, including an embedded terminal Check the full announcement at https://yast.opensuse.org/blog/2023-03-30/d-installer-0-8 Cheers. -- … [View More]

1 0

Playwright v1.32: Now with UI Mode
by Imobach Gonzalez Sosa 25 Mar '23

25 Mar '23

Hi all, Just in case it is relevant for us: UI mode for Playwright: https://github.com/microsoft/playwright/releases/tag/v1.32.0 Regards, Imo -- Imobach González Sosa SUSE Linux LLC

1 0

Removed images from Docker Hub, no CI for SLE12
by Ladislav Slezák 25 Mar '23

25 Mar '23

Hi all, Docker hub is removing the "Free Team" plan, they will only have paid team subscriptions (the lowest is $25 for 5 users/month, = $300/year), see [1]. Because we now build the CI images in OBS we do not need it anymore. So I completely removed the "yastdevel" and "libyui" organizations including all images. They would delete them in a month anyway. The only drawback is that those images were used in the SLE-12 and SLE15-GA + SLE15-SP1 builds. But we still use Travis CI in those … [View More]

3 4

New development server configuration for the D-Installer web frontend
by Ladislav Slezák 17 Mar '23

17 Mar '23

Hi all, I finally merged my PR [1] which improves the development server for the D-Installer frontend. It completely changed how it works. Now the dev server serves the D-Installer Cockpit plugin and the Hot Module Replacement end point. It redirects all Cockpit requests to another server, it works like a proxy. To start the dev server use this command: COCKPIT_TARGET=<IP_or_HOSTNAME> npm run server Where COCKPIT_TARGET is the IP address or hostname of the running D-Installer … [View More]

1 0

The Documentation for Creating a new Maintenance Branch in Git
by Ladislav Slezák 13 Mar '23

13 Mar '23

Hi, recently I have created the SLE-15-SP5 branch in all relevant YaST repositories. The process is not trivial, it needs quite a lot of manual steps to prepare the infrastructure (OBS/IBS/Jenkins/GitHub Actions). Then you need to fine tune a script which does the actual branching in 100+ Git repositories. This time I carefully recorded my steps and created a documentation. And I also uploaded my branching script to GitHub. See https://github.com/yast/helper_scripts/tree/master/github/… [View More]

1 0

GitHub starts requiring 2FA
by Ladislav Slezák 13 Mar '23

13 Mar '23

Hi, this is JFYI: today GitHub starts requiring two-factor authentication (2FA) for the developer accounts. The developer's accounts are quite often used for attacks, with this move they want to make GitHub more safe and reliable. The requirement will be gradual, they will add the requirement is groups. The target date is end of 2023, when 2FA will be mandatory for all developers. That means there is no specific date when your account will be migrated to 2FA, just be prepared for that. Of … [View More]

1 0

Comparing Using D-Bus Client Calls from Rust and Ruby
by josef Reidinger 10 Mar '23

10 Mar '23

Hi everyone, we published new blog post where we try to use and measure D-Bus calling from ruby and from rust and do some measurements and a bit of explanations there. https://yast.opensuse.org/blog/2023-03-07/ruby-rust-dbus-speed Josef

1 0

SLE15-SP5 branching on Friday March 3
by Ladislav Slezák 03 Mar '23

03 Mar '23

Hi all! We will create the SLE-15-SP5 maintenance branch from the master branch for all YaST packages on Friday March 3. I'll start around 15:00 CET (14:00 UTC). Because there are so many packages it will take some time, I'll let you know when it's done. So if you still have some open pull requests for the current SP5 then merge them ASAP or change the target branch in the PR after the SP5 branch is created and possibly also merge the change to master as well. -- Ladislav Slezák YaST … [View More]

1 3

Github CI, Podman and Container Running Systemd
by josef Reidinger 03 Mar '23

03 Mar '23

Hi everyone, We just published a new blog post about running podman and containers with systemd on github CI. We find it useful for our full stack testing. You might find it interesting as well. Have fun https://yast.opensuse.org/blog/2023-02-28/systemd-podman-github-ci Josef

1 0

yast2-transfer maintainer?
by Michael Andres 01 Mar '23

01 Mar '23

Hi all, I just found that I'm assigned as Bugowner for YaST:Head/yast2-transfer. https://build.suse.de/request/show/291017 asks me to review because: Submitter is not a bugowner of the package yast2-transfer I will approve, but maybe we should also remove this assignnemt. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +---------------------------------------------------… [View More]

2 1

D-Installer web: excluding code in production or setting values at compile time
by Ladislav Slezák 01 Mar '23

01 Mar '23

Hi all, I found some interesting Webpack features so I'd like to share them. Excluding Code ============== Sometimes it is useful to behave a bit different in a development build and in the production build. For example you might add some extra debugging in development mode or you might use some development library which does not make sense in production. For example the patternfly-react-seed project[1] which is a template project for the PatternFly library uses the "axe" accessibility … [View More]testing engine [2]. Of course, reporting the potential accessibility issues only makes sense for developers in the development builds. You can do that with code like: ``` if (process.env.NODE_ENV !== "production") { const axe = require("@axe-core/react"); axe(React, ReactDOM, 1000); } ``` That looks pretty straightforward isn't it? But it is actually quite tricky because 1) you cannot access the environment from browser Javascript, 2) even if that worked it's running on a completely different machine. So how it works actually?? The trick is that Webpack replaces (!) the "process.env.NODE_ENV" coode in the source code with the current value when processing it. So what the browser actually sees in the development mode is: ``` if ("development" !== "production") { const axe = require("@axe-core/react"); axe(React, ReactDOM, 1000); } ``` And that condition is always true so that code always runs. In the production mode it would be: ``` if ("production" !== "production") { import { foo } from "foo"; foo.bar(); } ``` So that would never run. But the production builds usually use extra minification and optimization step. The minifier is quite clever and for example it removes the always false conditions from the code completely. So the final minified production code is reduced to: ``` ``` Yes, nothing! :-) By default it works only for the "NODE_ENV" variable but you can add support for any other environment variable using the Webpack EnvironmentPlugin, see [3]. Replacing Values ================ This is similar to the previous case, but instead of replacing an environment variables you can replace any value at the compile time. For example you want to somewhere display the project version or the last git commit hash or the build date or... (Um, the build date is actually a bad idea, that would break reproducible package builds in OBS.) Weback has DefinePlugin for that, see the documentation [4]. If you want to replace a string then it must be quoted because the value is replaced literally. A common trick is to use JSON.stringify(string). On the other hand that allows the replacement to be any expression, even some code to execute. The ESlint step is called *before* these string replacements so it sees the original code. And that means it would complain about undefined variables. The workaround is to define it as a known global in the .eslintrc.json configuration file [5]. HTH, Ladislav [1] https://github.com/patternfly/patternfly-react-seed [2] https://github.com/dequelabs/axe-core [3] https://webpack.js.org/plugins/environment-plugin/ [4] https://webpack.js.org/plugins/define-plugin/ [5] https://eslint.org/docs/latest/use/configure/language-options#specifying-gl… -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8 [View Less]

3 4

[yast2][15.5] bad columns behavior in 15.5 partitioner
by Felix Miata 01 Mar '23

01 Mar '23

Maximum column width seems needed to address. On /every/ return to partition list screen after editing a partition, the column heading widths are reset to defaults instead of applying those selected before the first edit/add/delete. When an nvme type name is stupid lengthy, it can push the Label column so far right that it is inadequately visible, and make the Mount Point column completely invisible. In this case, the Enc column appears to be centered on the XVideo=1440x900,108 screen, the … [View More]

2 2