September 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

Cockpit development
by Ladislav Slezák 20 Dec '22

20 Dec '22

Hello, recently I fixed a small bug in cockpit [1]. The fix is rather trivial but it was quite difficult to test it and verify that it really fixes the problem. ALP Prerequisites ================= 1. Install ALP from https://download.opensuse.org/repositories/SUSE:/ALP/images/, see the previous mails about the installation and configuration 2. Install cockpit with "transactional-update pkg install cockpit", then reboot the system (the backend packages are already preinstalled in the ALP image, this will install the web frontend) 3. Start the cockpit service: "systemctl enable --now cockpit.socket" Now you will have the standard cockpit installed and ready to run, you might test it by connecting to https://localhost:9090 Development =========== Note: I needed to patch a cockpit plugin which is basically a JS code + HTML + CSS. If you would need to patch the cockpit core (the C code) it would be more difficult, see the suggestion in the end. I did the development directly on my workstation (Leap 15.4), the ALP instance was running in a VM. Development Prerequisites ------------------------- For patching a cockpit plugin you should not need much libraries installed, but the the Makefile (generated by autotools) requires the libraries also for the C part. On my workstation I had to additionally install these packages: zypper install json-glib-devel krb5-devel sassc nodejs16 You might actually need some more libraries or tools (autotools), I use my workstation as a development machine and it already contains a lot of libraries. Check that nodejs and npm default versions are 16, esp. if you have multiple versions installed. Originally I probably did something wrong and got some strange failures... Then you can checkout the sources from GitHub git clone git@github.com:cockpit-project/cockpit.git and checkout the version used in ALP cd cockpit git checkout -b 276 Check https://build.opensuse.org/package/show/SUSE:ALP/cockpit, it might change in the future. To build the sources use: # this installs the npm packages using "npm install" ./autogen.sh # autogen.sh runs configure but it will very likely fail, by default it needs # some additional libraries, if you want to patch just a plugin then run ./configure --disable-doc --disable-ssh --disable-pcp --disable-polkit make Now the compiled plugins are available in ./dist/ subdirectory. Now we need to transfer these changed file to the ALP system. There are several possibilities to do this. You can run an "scp" command after each edit/build or you can use some network file system. I tested that with sshfs. The disadvantage is that the sshfs packages are not available for ALP, as a workaround I installed the "sshfs" and "fuse3" packages from Tumbleweed. That works currently because ALP is based on TW, but that will probably not work later when ALP is branched from TW. The clean solution would be to provide a container for that... To mount a directory over sshfs run sshfs <user>@<machine>:<path_to_git_checkout> /mnt Now we need cockpit to load the new files. Fortunately it can load the plugins from the user's $HOME: mkdir ~/.local/share/cockpit link the shared directory from the development machine ln -s /mnt/dist/networkmanager/ ~/.local/share/cockpit/networkmanager (You could link the whole /dist/ to override all plugins, but that could possibly have some side effects, I'd rather just override the updated plugin to be safe.) Then you can just reload the cockpit page in the web browser and that's it, you do not need to relogin or restart the cockpit service. Testing with the "main" branch ============================== Then I wanted to test my change also with the "main" branch to be sure it can be properly submitted to upstream. It turned out that they changed the way how the node modules are loaded. They do not run "npm install" anymore, but rather use Git submodules for that, the whole "node_modules" directory is a Git submodule. The problem is that the submodules are not checked out by default. If you want to use the "main" branch then do the initial checkout with git clone --recurse-submodules git@github.com:cockpit-project/cockpit.git or if you already have a clone without submodules then you can download them with git submodule update --init Be careful when switching the branches! When you later switch to an older version you might need to delete the "node_modules" directory and run ./autogen.sh to install them via npm otherwise you will end up with different modules and probably get some nasty errors! Patching the Core Cockpit ========================= If you need to patch the C part then you could just run "make" and copy the built binary to the ALP VM. The problem is that /usr is read-only in ALP. But you can create a writable overlay using overlayfs: mkdir /tmp/upperdir mkdir /tmp/workdir mount -t overlay overlay -o lowerdir=/usr,upperdir=/tmp/upperdir/,workdir=/tmp/workdir/ /usr Then the /usr will become writable, see more details in https://www.kernel.org/doc/Documentation/filesystems/overlayfs.txt Now you can easily rewrite or edit the files there cp /mnt/cockpit-tls /usr/libexec/cockpit-tls To take effect you need to restart the cockpit service systemctl restart cockpit HTH Ladislav [1] https://github.com/cockpit-project/cockpit/pull/17776 -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

2 2

Pending Pull Requests
by yast-ci＠opensuse.org 26 Sep '22

26 Sep '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-core: - .target.tmpdir - honor the target root (bsc#1199840) (26 days) https://github.com/yast/yast-core/pull/159 Pending requests in repository yast-devtools: - Sle15sp3 boo1199396 (53 days) https://github.com/yast/yast-devtools/pull/168 - Boo1199396 (52 days) https://github.com/yast/yast-devtools/pull/167 - Set %yast_icondir to /usr/share/icons/hicolor (bsc#1186066) (230 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-installation: - Remake some icons (62 days) https://github.com/yast/yast-installation/pull/1028 Pending requests in repository yast-packager: - Do not call [Install done] on aborted packages (9 days) https://github.com/yast/yast-packager/pull/623 - Remake some icons (62 days) https://github.com/yast/yast-packager/pull/603 Pending requests in repository yast-schema: - Added '<security_policies/>' element within the security section (26 days) https://github.com/yast/yast-schema/pull/145 Pending requests in repository yast-theme: - Add pantheon desktop support (299 days) https://github.com/yast/yast-theme/pull/154 Pending requests in repository yast-users: - Remove LDAP parts (31 days) https://github.com/yast/yast-users/pull/366 - Update readme (47 days) https://github.com/yast/yast-users/pull/365 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (229 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository skelcd-control-suse-manager-proxy: - fix setting default module section in installation control file (10 days) https://github.com/yast/skelcd-control-suse-manager-proxy/pull/21 Pending requests in repository skelcd-control-suse-manager-server: - fix setting default module section in installation control file (10 days) https://github.com/yast/skelcd-control-suse-manager-server/pull/27 Pending requests in repository skelcd-control-MicroOS: - Revert https://github.com/yast/skelcd-control-MicroOS/pull/57 partially, (11 days) https://github.com/yast/skelcd-control-MicroOS/pull/58 Pending requests in repository yast-sap-ha: - Add released updates. (16 days) https://github.com/yast/yast-sap-ha/pull/17 - YaST2 HA Setup for SAP Products - cannot input several instance numbe… (16 days) https://github.com/yast/yast-sap-ha/pull/15

1 0

Testing ALP
by Ladislav Slezák 23 Sep '22

23 Sep '22

Hi all, I did some testing of the new ALP project and here are some notes about installing and configuring it. If you have more tips for the ALP then just write them here, thank you in advance! 1. Download =========== You can download the ALP images directly from https://download.opensuse.org/repositories/SUSE:/ALP/images/ there are pre-built images for several platforms, choose the one which best fits your use case. In the iso/ subdirectory you can find bootable ISO images which can be used to install ALP in any system (even bare metal). Note: As ALP is still in heavy development it is recommended to use a virtual machine for testing. There are two types of images - with transactional system (read-only file system with snapshots) or non-transactional (classic, writable file system). Here it depends what you need to do and if you are already familiar with a transactional system. If unsure then I'd suggest starting with the non-transactional images as they are more close to the traditional systems and are easier to use and manage. 2. Installation =============== Uncompress the downloaded image with "unxz" and use the disk image in your favorite VM platform. If you use the ISO image then just boot from it and then confirm deploying the image on the disk. Be careful, this rewrites ALL data on the target disk! 3. Configuration ================ The disk images use empty password for the root user (just press ENTER when asked for the password). The ISO image installs a simple configuration tool [1] which runs at the first boot and can configure some basic things like locales or the root password. 4. Storage ========== The disk images use virtual disk with size from 20 to 30GB (depends on the type) so there is quite a lot of free space for experimenting. The ISO image installer creates just a 2GB root partition where about 1.2GB is used. So there is not much space for experimenting, especially if you want to run some containers. You can expand the root partition over the whole disk with these commands: # resize the partition, the root FS is on /dev/sda4 # (note the space between the disk and the partition number!!) growpart /dev/sda 4 # resize the filesystem /usr/lib/systemd/systemd-growfs / Btrfs can be resized online (while mounted) so you can see the result immediately and you do not need to reboot. You might check the resulting size with "df -h /". 5. SSH Access ============= By default the SSH service is enabled and running. However, the root login is not allowed by default. There are two options: 1. Create a regular user: # create the user useradd <username> # set the password passwd <username> Then use this user in the SSH connection. If you need to switch to root then use "su" or "sudo" later. 2. Allow root Login # create a config file echo "PermitRootLogin yes" > /etc/ssh/sshd_config.d/root.conf # restart the service systemctl restart sshd Then connect as root via SSH. 6. Software =========== If you need to install some more packages then you can use zypper with the pre-configured ALP repository. If you need some package which is not present there then you might try adding an OBS repository which is built against openSUSE Tumbleweed. (ALP is based on TW so the packages should be compatible in the most cases.) So if you want to try the latest YaST packages (especially the "yast-in-container" package) then use this repository [2]. HTH! Ladislav [1] https://github.com/openSUSE/jeos-firstboot [2] https://download.opensuse.org/repositories/YaST:/Head/openSUSE_Tumbleweed/ -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

2 2

YaST: 9th development report of 2022
by Ancor Gonzalez Sosa 22 Sep '22

22 Sep '22

The YaST Team keeps working on the already known three fronts: - Improving the installation of traditional (open)SUSE systems - Polishing and extending the containerized version of YaST - Smoothing the experience of managing ALP with Cockpit Check the full report at https://yast.opensuse.org/blog/2022-09-22/yast-report-2022-9 Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH

1 0

Pending Pull Requests
by yast-ci＠opensuse.org 19 Sep '22

19 Sep '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-core: - .target.tmpdir - honor the target root (bsc#1199840) (19 days) https://github.com/yast/yast-core/pull/159 Pending requests in repository yast-devtools: - Sle15sp3 boo1199396 (46 days) https://github.com/yast/yast-devtools/pull/168 - Boo1199396 (45 days) https://github.com/yast/yast-devtools/pull/167 - Set %yast_icondir to /usr/share/icons/hicolor (bsc#1186066) (223 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-installation: - Remake some icons (55 days) https://github.com/yast/yast-installation/pull/1028 Pending requests in repository yast-packager: - Remake some icons (55 days) https://github.com/yast/yast-packager/pull/603 Pending requests in repository yast-schema: - Added '<security_policies/>' element within the security section (19 days) https://github.com/yast/yast-schema/pull/145 Pending requests in repository yast-theme: - Add pantheon desktop support (292 days) https://github.com/yast/yast-theme/pull/154 Pending requests in repository yast-users: - Remove LDAP parts (24 days) https://github.com/yast/yast-users/pull/366 - Update readme (40 days) https://github.com/yast/yast-users/pull/365 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (222 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository yast-sap-ha: - Add released updates. (9 days) https://github.com/yast/yast-sap-ha/pull/17 - Fix validating SAP instance number (9 days) https://github.com/yast/yast-sap-ha/pull/16 - YaST2 HA Setup for SAP Products - cannot input several instance numbe… (9 days) https://github.com/yast/yast-sap-ha/pull/15 - YaST2 HA Setup for SAP Products - cannot input several instance numbe… (9 days) https://github.com/yast/yast-sap-ha/pull/14

1 0

YaST containers - Git repository or repositories?
by Ladislav Slezák 12 Sep '22

12 Sep '22

Hello! This is related to https://trello.com/c/AVE56dla. The problem is that the YaST containers for ALP are currently developed directly in OBS without any Git repository. And that makes the development difficult, you cannot easily check the history, reviews are nor possible, etc... So let's create a Git repository at GitHub! The question is whether we should create a separate Git repository for each container or have a single repository with all containers. I'd prefer to have a single repository, the reasons are: 1) There is a strong relationship between the containers, each is built on top of other. Changing the base container changes all derived ones. 2) This would also make container versioning easier. This is pretty similar to the libyui library where we also had problems to keep all plugins in sync. My proposal: | + Rakefile (top level) + *.changes (contains aggregated changes for all containers) + yast-mgmt-ncurses | + Rakefile (specific for this container) | + Dockerfile | ... + yast-mgmt-qt | + Rakefile (specific for this container) | + Dockerfile | ... The top-level Rakefile would just call the tasks in the subdirectories, e.g. "rake osc:commit" would call "rake osc:commit" in yast-mgmt-ncurses and others. We would just need to handle the problem when it fails in some subdirectory but succeeds in others. Note: it seems that the OBS multibuild feature does not support multiple Dockerfiles, so we cannot use the exactly same solution as in libyui. If you have any better idea or improvement just ping me. If it turns out that having everything in one repo does not work well we can always split it later. -- 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 12 Sep '22

12 Sep '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-autoinstallation: - Add support for security policies (12 days) https://github.com/yast/yast-autoinstallation/pull/845 Pending requests in repository yast-core: - .target.tmpdir - honor the target root (bsc#1199840) (12 days) https://github.com/yast/yast-core/pull/159 Pending requests in repository yast-devtools: - Sle15sp3 boo1199396 (39 days) https://github.com/yast/yast-devtools/pull/168 - Boo1199396 (38 days) https://github.com/yast/yast-devtools/pull/167 - Set %yast_icondir to /usr/share/icons/hicolor (bsc#1186066) (216 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-http-server: - Query php version dynamically (30 days) https://github.com/yast/yast-http-server/pull/58 Pending requests in repository yast-installation: - Remake some icons (48 days) https://github.com/yast/yast-installation/pull/1028 Pending requests in repository yast-packager: - Remake some icons (48 days) https://github.com/yast/yast-packager/pull/603 Pending requests in repository yast-schema: - Added '<security_policies/>' element within the security section (12 days) https://github.com/yast/yast-schema/pull/145 Pending requests in repository yast-security: - Add a security policy validation mechanism (10 days) https://github.com/yast/yast-security/pull/128 Pending requests in repository yast-theme: - Add pantheon desktop support (285 days) https://github.com/yast/yast-theme/pull/154 Pending requests in repository yast-users: - Remove LDAP parts (17 days) https://github.com/yast/yast-users/pull/366 - Update readme (33 days) https://github.com/yast/yast-users/pull/365 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (215 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository yast-storage-ng: - Security policy checks (11 days) https://github.com/yast/yast-storage-ng/pull/1308

1 0

YaST: 8th development report of 2022
by Ancor Gonzalez Sosa 06 Sep '22

06 Sep '22

Check the latest development report from the YaST Team including: - The fix of an elusive YaST bug regarding the graphical interface - Initial handling of transactional systems in YaST - A general reflection about 1:1 management of transactional systems - Some improvements in the metrics functionality of Cockpit See the full version at https://yast.opensuse.org/blog/2022-09-06/yast-report-2022-8 Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH

1 0

Pending Pull Requests
by yast-ci＠opensuse.org 05 Sep '22

05 Sep '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: - Sle15sp3 boo1199396 (32 days) https://github.com/yast/yast-devtools/pull/168 - Boo1199396 (31 days) https://github.com/yast/yast-devtools/pull/167 - Set %yast_icondir to /usr/share/icons/hicolor (bsc#1186066) (209 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-http-server: - Query php version dynamically (23 days) https://github.com/yast/yast-http-server/pull/58 Pending requests in repository yast-installation: - another try at adressing the hidpi issue (bsc#1199020) (18 days) https://github.com/yast/yast-installation/pull/1049 - Remake some icons (41 days) https://github.com/yast/yast-installation/pull/1028 Pending requests in repository yast-packager: - Remake some icons (41 days) https://github.com/yast/yast-packager/pull/603 Pending requests in repository yast-theme: - Add pantheon desktop support (278 days) https://github.com/yast/yast-theme/pull/154 Pending requests in repository yast-users: - Remove LDAP parts (10 days) https://github.com/yast/yast-users/pull/366 - Update readme (26 days) https://github.com/yast/yast-users/pull/365 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (208 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository yast-vpn: - [SLE15-SP3] Place file selection buttons at the bottom (9 days) https://github.com/yast/yast-vpn/pull/18

1 0