- YaST Development

Version update in git master
by josef Reidinger 30 Aug '23

30 Aug '23

Hi, I do mass version update in master from 4.6.X to 5.0.0 as it was agreed in branching discussion. To sum it here, we basically: 1. bump master to 5.0.0 to emphasize that SLE15 now uses version with 4.X.Y and TW/ALP uses 5.X.Y 2. SLE15 SP6 branch will be based on SLE15 SP5 maintenance branch 3. to avoid version collision if master use some changes and 4.6.X then SP6 branch will be bumped to 4.6.X+1 to avoid having same version for different code 4. as creating SP6 involve some manual steps it takes some time ( I will work on it ), so we will have period without proper SP6 maintenance branch. 5. changes already done to master that does not go to SP5 will be manually evaluated if it makes sense for SP6 Open Question is what to do with distro based versions we use for skelcd/system-role packages as I am not sure if next leap will be 15.6 or 16 and on what code stream it will be based, so I do not bump version there yet. Thanks Josef

1 0

Blog post: news about Agama and ALP
by Ancor Gonzalez Sosa 23 Aug '23

23 Aug '23

After almost five months of radio silence, the YaST Team is back to blogging. Check the latest news about Agama (and how you can use it to install an early preview of ALP Dolomite) at https://yast.opensuse.org/blog/2023-08-21/agama3 Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH

2 1

LibYUI Questions
by Dmitriy Zakharov 14 Aug '23

14 Aug '23

Hello YaST Team, My name is Dmitriy Zakharov, I work as QA engineer for OpenText. Our team is looking for an existing framework/tools that will allow us to automate testing our yast modules. While researching we came across libyui test framework that you have developed. We'd like to thank you for the framework, the team really likes it since everything can be done via REST API. When working on proof-of-concept we were able to automate few tests when starting yast module(e.g. sudo Y2TEST=1 YUI_HTTP_PORT=9999 yast2 host). However, when we tried to start yast in main mode without specifying any module (e.g. sudo Y2TEST=1 YUI_HTTP_PORT=9999 yast2) we could not navigate menu. We are using select action but that doesn't seem to work. Please see screenshots below for more details. Screenshot 1 - our yast main menu yast started without module: sudo Y2TEST=1 YUI_HTTP_PORT=9999 yast2 and no action performed yet [cid:image001.png@01D9BEE4.7693A9F0] Screenshot 2 - view after POST with select action REST call to select "Configure Time/Date" in the left box: curl -X POST 'http://localhost:9999/v1/widgets?id=groups&action=select&value=Configure%20…' Note "Configure Time/Date" in the left box is kind of highlighted but right box still shows items for "Configure Networking" rather than for "Configure Time/Date". Calling GET returns "Configure Time/Date" label as selected. [cid:image002.png@01D9BEE4.7693A9F0] Questions we have are: 1. Is our REST call curl -X POST 'http://localhost:9999/v1/widgets?id=groups&action=select&value=Configure%20…' incorrect and that's why select doesn't work for main mode? 2. Does libyui-rest-api support starting yast without specific module? 3. If libyui-rest-api doesn't currently support starting yast in main mode, is there a plan to support it? Thank you, Dmitriy Zakharov

2 1

yast2 apparmor / aa-logprof behaviour on startup errors
by Christian Boltz 30 Jul '23

30 Jul '23

Hello, Short version: Can someone please check the YaST2 AppArmor module if something needs to be changed for the aa-logprof and aa-genprof change described below? Long version: I'm currently working on a little feature in aa-logprof and aa-genprof to enable logging of all json input and output, which might make debugging a bit easier, and might also make it possible to easily create tests for a complete aa-logprof run. (YaST will be helpful to create these tests, since it's currently the only json client for aa-logprof.) The json format itsself will not change, however I'll have to switch to json mode a bit later. You'll only notice this if there's an error on startup, for example a broken config file or missing apparmor_parser. Now: # aa-logprof --json {"dialog": "apparmor-json-version","data": "2.12"} ERROR: Can't find apparmor_parser at /sbin/apparmor_parser After the change: # python3 aa-logprof --json ERROR: Can't find apparmor_parser at /sbin/apparmor_parser Note that the {"dialog": ... } line no longer gets printed if aa- logprof or aa-genprof error out on startup. For completeness: ERROR: gets printed on stderr, and $? = 1. Again: If there is no error on startup, nothing will change. Is this change a problem for the YaST AppArmor module? (I'd offer to update the json version, but since it no longer gets printed on startup errors, I'm not sure if that's too helpful ;-) So far, this change only exists as a MR: https://gitlab.com/apparmor/apparmor/-/merge_requests/1078 It will probably be included in AppArmor 4.0 (to be released in some months). Regards, Christian Boltz -- "Guten Tag, ich möchte gerne einen Tisch reservieren." "Gerne, auf welchen Namen denn?" "31337 /-/ /\ X0R!" [Jens Benecke in suse-linux zum Thema Realnames]

1 0

Driver Update Disk (DUD) documentation, VirtualBox USB emulation
by Ladislav Slezák 07 Jul '23

07 Jul '23

Hi all, I wrote a short summary about the Driver Update Disk (DUD), how to create it and use it. Especially I tested how to use DUD from an USB flash disk. See https://github.com/yast/yast.github.io/wiki/Driver-Update Note: I created it as a wiki page because I someone needed that quickly, feel free to improve it. Later I'd like to move it to some other place, probably https://github.com/yast/yast.github.io/tree/master/doc published at https://yastgithubio.readthedocs.io/ BTW did you know that the latest VirtualBox can emulate an USB controller with USB disk(s)? Go to the "Storage" section, at the bottom there is small icon containing a plus sign with "Add controller" tool tip. Click it and select "USB". A new USB controller appears in the list above it. Click the plus icon next to it to attach a virtual disk or CD/DVD device. You can attach an existing image or create a new one, just like with the emulated SATA or IDE devices. This might be useful for testing some special use cases. Enjoy! Ladislav -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

1 0

GitHub CI - "leap_latest" updated to Leap 15.5
by Ladislav Slezák 20 Jun '23

20 Jun '23

Hi all, I have updated the "leap_latest" container used in GitHub CI from openSUSE Leap 15.4 to Leap 15.5. You do not need to do any changes, just be prepared that the new CI runs will use Leap 15.5 as the base system. There should be minimal changes between 15.4 and 15.5 so I expect everything should work just fine. However, if you see some related problem just ping me. Ladislav -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

1 0

YaST:Head - added Leap 15.5, removed Leap 15.3
by Ladislav Slezák 20 Jun '23

20 Jun '23

Hello! I have added the openSUSE Leap 15.5 build target to YaST:Head OBS project. (https://build.opensuse.org/project/show/YaST:Head) And I removed the openSUSE Leap 15.3 build target because it is out of support (already for ~6 months) and to save some build resources. Enjoy :-) Ladislav -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

1 0

New Agama OBS Projects systemsmanagement:Agama:Staging and systemsmanagement:Agama:Devel
by Ladislav Slezák 13 Jun '23

13 Jun '23

Hi all, I created new OBS projects for developing the Agama installer: https://build.opensuse.org/project/show/systemsmanagement:Agama:Staging https://build.opensuse.org/project/show/systemsmanagement:Agama:Devel The old YaST:Head:Agama project is not updated anymore and will be removed at some point. Do not use it. I also added the Agama containers from YaST:Head:Containers there. Staging ------- The systemsmanagement:Agama:Staging project contains the latest packages built from the "master" branch in Git. This project contains unstable development version of Agama. It is intended for development or testing new unfinished features. The packages are automatically updated whenever the master branch is changed. Devel ----- The systemsmanagement:Agama:Devel project contains the latest released version of the Agama project. The packages should be more stable than in the Staging project. It is intended for testing. These packages are updated automatically when a new version is released. Documentation ------------- You can find some more details in the documentation: https://github.com/openSUSE/agama/blob/master/doc/obs_integration.md -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

1 0

Report from openSUSE Conference 2023
by Ancor Gonzalez Sosa 31 May '23

31 May '23

Already in my way back from oSC'23, so let's write some notes before I forget. I could feel a lot of interest in Agama even since before the conference itself started, in the welcome party. There was only another topic that looked more important for basically everyone there - the question I was asked 10+ times per day from Thursday to Sunday: Where is the rest of Canary gang? oSC feels incomplete without them! About the second more important topic (apparently), I can say our presentation was extremely well received. Most people looked genuinely interested, not to say excited, about Agama. And looking at the kind of questions I got before the presentation and the feedback I got afterwards, I would say the talk addressed its goal pretty well and there are more people now with a proper understanding of Agama and the installation process in general. And there are people already having ideas about how to contribute, adapt it or adopt it. I saw a lot of interest from the community for adopting Agama as default official installer in a relatively short time frame. Unless we screw things up, I would say Agama will be the official installer for Leap 16. What "Leap 16" means exactly regarding the calendar? Well, nothing is set in stone but my assumption after several conversations is that there will be a Leap 15.6 at some point in the future (still using YaST). So Leap 16 will not arrive before 2024. Gradual integration with Tumbleweed may start a bit in advance. Based on those same conversations, I would also expect openSUSE use Agama as a multi-product installer. As LCP pointed to me, that implies we need to resurrect at some point the theming and branding topic. Other area in which we could get some contributions is the initialization process (everything that happens until the point in which Agama takes over). Some people was curious about that and wanted to try their own ideas. I also had some conversations with Uyuni/SUSE Manager developers. They like the part about being able to track the installation process, but they are not so sure our current solution based on D-Bus would suffice to them. Some extra work is still needed to close the gap (hopefully without blowing up the memory consumption). But now that we have a common understanding and some foundations, we can build from there. Some people even tried to hack a bit on Agama, although not very successfully. We may need to check if our current documentation in that regard is in good shape. I'm likely forgetting several conversations and details, but I think the main topics are covered. Do not hesitate to ask for more details in any of them. Cheers. -- Ancor González Sosa YaST Team at SUSE Software Solutions

3 3

OBS + Git Integration
by Ladislav Slezák 29 May '23

29 May '23

Hi all, Last Friday I watched the "Introduction to OBS Gitlab/Github CI Integration" openSUSE conference presentation [1]. It was quite interesting so I'm sharing some details about it here. Later a recording of the presentation should be available, but the slides [1] and the OBS documentation [2] should be enough. Some additional information is available in the OBS blog [3]. This OBS integration allows automatic update and rebuild of a package whenever a source Git repository is updated (Github or Gitlab are currently supported). Optionally it can also also branch a package if you open a pull (merge) request. For YaST we already do the synchronization by using Jenkins CI. But this OBS integration allows to directly setup the communication between Git and OBS without any 3rd tool in the middle. It looks interesting because with this approach we could quite easily set up automatic update of the Agama packages in some OBS staging project... Ladislav [1] https://events.opensuse.org/conferences/oSC23/program/proposals/4211 [2] https://openbuildservice.org/help/manuals/obs-user-guide/cha.obs.scm_ci_wor… [3] https://openbuildservice.org/2021/11/09/scm-integration-documentation/ -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

1 0