- YaST Development

New Agama blog, Agama 10
by Ladislav Slezak 06 Nov '24

06 Nov '24

Hi all! To avoid confusion between YaST and Agama we created a new place for the Agama blog. Since now the YaST blog will be used only for the YaST related posts, for Agama news check the new place: https://agama-project.github.io/blog To give you one more reason to look at the new Agama blog we have just published the Agama version 10 <https://agama-project.github.io/blog/2024/10/30/agama-10> blog post there! 😉 Enjoy! -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

3 2

Improving Agama's OpenAPI specification
by Imobach Gonzalez Sosa 22 Oct '24

22 Oct '24

Hi all, As you may know, Agama can generate an OpenAPI specification for its HTTP API. Until recently, we had an "agama-web-server openapi" subcommand to do that. One advantage is that we could automatically generate clients/types from the spec. Sadly, the specification was invalid because **a lot** of stuff was missing. After some hours of Learning & Innovation, today I am merging a pull request that partially addresses those issues[1]. Kudos to Josef for the review. It implements the following changes: * It makes the OpenAPI specification valid. However, a few endpoints/types are still missing (DASD, issues, etc.). But at least what is included in the spec is valid. * The code that generates the specification is easier to work with. * The OpenAPI is generated at build time (as a xtask[2]) and included in a separate package (agama-openapi). Therefore the "openapi" subcommand is not available anymore. * The specification is generated and validated as part of our CI. So expect some red crosses from now on :-) Let's continue working toward a proper specification we can use to generate for our clients ;-) Regards, Imo [1] https://github.com/agama-project/agama/pull/1564 [2] https://github.com/agama-project/agama/pull/1650

1 0

Fwd: Agama Github page seems to be broken? [Solved]
by Luna Jernberg 22 Oct '24

22 Oct '24

---------- Forwarded message --------- Från: J Leslie Turriff <jlturriff(a)mail.com> Date: tis 22 okt. 2024 kl 06:06 Subject: Re: Agama Github page seems to be broken? [Solved] To: Luna Jernberg <droidbittin(a)gmail.com> Hah. Apparently, now GitHub displays that weird page when one is not logged in. I don't remember seeing that before. Leslie On Monday 21 October 2024 23:40:21 you wrote: > Odd, it works as it should here > > Den tis 22 okt. 2024 kl 05:37 skrev J Leslie Turriff <jlturriff(a)mail.com>: > > No. Look at https://get.opensuse.org/leap/16.0/#download, and > > below the download buttons you'll see > > > > | Choosing Which Media to Download > > | > > |_Agama_ is the new installer that can be used to install Leap 16 and > > |Tumbleweed. There is a plan to support offline installation in Agama. > > | Other installation media such as self-install image will be added > > | later. > > > > where _Agama_ is a link to the Agama GitHub page. But that page is not > > displaying Agama information. > > > > Leslie > > > > On Monday 21 October 2024 23:22:31 you wrote: > > > Hey > > > > > > https://download.opensuse.org/distribution/leap/16.0/installer/iso/agam > > >a-in staller-Leap.x86_64-9.0.0-openSUSE-Build40.1.iso is what i think > > > you are looking for > > > > > > Den tis 22 okt. 2024 kl 04:40 skrev J Leslie Turriff via openSUSE > > > > > > Users <users(a)lists.opensuse.org>: > > > > When I follow the link from the Leap 16.0 Download page to > > > > the Agama GitHub page I don't see anything about Agama, just some > > > > sort of generic GitHub menu. A screenshot is attached. > > > > > > > > Leslie > > > > -- > > > > Platform: Linux > > > > Distribution: openSUSE Leap 15.6 - x86_64 Leslie -- Platform: Linux Distribution: openSUSE Leap 15.5 - x86_64

1 0

Re: Development start of Leap 16.0
by Luna Jernberg 07 Oct '24

07 Oct '24

Translated the get. site to Swedish now Den mån 7 okt. 2024 kl 14:02 skrev Lubos Kocman via openSUSE Factory <factory(a)lists.opensuse.org>: > > Hello everyone! > > (Also available in html > https://news.opensuse.org/2024/10/03/leap-16-0-prealpha/) > > I'd like to announce the start of development and the public > availability of what we currently refer to as Leap 16.0 pre-Alpha. > Since this is a pre-Alpha version, significant changes may occur, and > the final product may look very different in the Alpha, Beta, Release > Candidate, or General Availability stages. > The installer will *currently* offer you Base, GNOME, and KDE. > > Users can get our new Agama install images from > https://get.opensuse.org/leap/16.0. The installer will *currently* > offer you Base, GNOME, and KDE installation. > > Leap 16.0 is a traditional distribution and a successor to Leap 15.6 > with expected General Availability arriving in the Fall of 2025. > > We intend to provide users with sufficient overlap so that 15.6 users > can have a smooth migration, just like they're used to from previous > releases. > > Further details are available on our https://en.opensuse.org/openSUSE:Roadmap. > The roadmap is subject to change since we have to respond to any SUSE > Linux Enterprise Server 16 schedule changes. > > Users can expect a traditional distribution in a brand new form based > on binaries from the latest SLES 16 and community packages from our > Factory development codebase. > > There is no plan to make a Leap 15.7, however, we still need to > deliver previously released community packages from Leap 15 via > Package HUB for the upcoming SLES 15 SP7. This is why there are > openSUSE:Backports:SLE-15-SP7 project and 15.7 repos in OBS. > > > **Who should get it?** > This is a pre-alpha product that is not intended to be installed as > your daily driver. > I highly recommend starting with the installation in a virtual machine > and becoming familiar with the online installer Agama. > > The target audience for pre-Alpha are early adopters and contributors > who would like to actively be part of this large effort. Adopters > should consider booting Agama Media from time to time just to check > compatibility with their hardware. > > For non-contributor users, I highly recommend waiting until we have a > Beta, which is expected in the late Spring of 2025. > > **How to report bugs?** > > I'd like to kindly ask you to check > https://en.opensuse.org/openSUSE:Known_bugs_16.0 before reporting a > new issue. If you find a new issue that is likely to affect users, > please feel free to add it to the page. > > Specifically for Agama I highly recommend using > https://github.com/agama-project/agama/issues and collaborating with > the YaST team on suggestions and incorporating any changes. > > For the rest of the components, the workflow isn't changing; just > select version 16.0. Details in > https://en.opensuse.org/openSUSE:Submitting_bug_reports#Regular_release_pro…. > > > **Feature requests** > > All changes to packages inherited from SLES 16 need to be requested > via our public feature request workflow > https://code.opensuse.org/leap/features. > > Feature requests will be reviewed every Monday at a feature review > meeting, see calendar.opensuse.org, where we'll convert code-o-o > requests into JIRA requests used by SUSE Engineering where applicable. > > The factory-auto bot will reject all code submit requests against SLES > packages with a pointer to code-o-o. > You can get a list of all SLFO/SLES packages simply by running `osc ls > SUSE:SLFO:1.1:Build`. > > Just for clarification SLFO, SUSE Linux Framework One, is the source > pool for SLES 16 and SL Micro 6.X. > > I highly recommend using code-o-o to coordinate larger community > efforts such as Xfce enablement, where we will likely need to update > some of SLES dependencies. > This allows us to share the larger story and better reasoning for > related SLES update requests. The list of features is also extremely > valuable for the Release article. > > **Where to submit packages, how is it built, and where is it tested?** > > Leap 16.0 is built in openSUSE:Leap:16.0 project where we will happily > welcome any community submissions until the Beta code submission > deadline in the late Spring of 2025. > We intend to keep the previous development model and avoid forking > SLES packages unless necessary. > We no longer can > [mirror](https://en.opensuse.org/Portal:Jump:OBS:SRMirroring) SLES > code submissions from OBS into IBS. So all SLES 16 update requests > have to be requested via feature requests. > > For quality control, we have basic test suites based on Agama > installations in Leap 16.0 job group > https://openqa.opensuse.org/group_overview/129. > Later, we plan to rework the existing Leap 16.0 Images job group > https://openqa.opensuse.org/group_overview/126 for testing the > remaining appliance images. > > > The project where we maintain community packages is subject to change > as we have not fully finalized yet how to make Package HUB; we may use > a similar structure with Backports as in 15.3+). > > Further test suite enablement is one of the areas where we currently > need the most help. > Related progress.opensuse.org trackers for Leap 16.0 enablement > https://progress.opensuse.org/issues/164141 and upgrade from 15.6 > https://progress.opensuse.org/issues/166562. > > Another area where you can help is new package submissions and related > maintainer review of package submissions to Leap 16.0. > These reviews make sense as we'd like to check with maintainers > whether that software in a given version makes sense for inclusion > into Leap 16.0, rather than blindly copying all packages over. > > **Involvement in branding and marketing efforts** > > I'm very proud to announce fresh branding efforts and want to thank > all the people who helped give Leap and Tumbleweed a new look. We plan > to publish an article or a video about the changes, and further plans > as we still have a surprise or two in our pocket. > > Do you want to help us on this front? Spread the news and feel free to > join the #openSUSE_Marketing Telegram channel > https://t.me/openSUSE_Marketing! Details at > https://en.opensuse.org/openSUSE:Marketing_team > > Many thanks to all who helped us to reach this point. > > Lubos Kocman > on behalf of the openSUSE Release team

1 0

Using the YaST:Devel repo with Leap 15.6
by Stefan Hundhammer 07 Oct '24

07 Oct '24

I realized just last Friday that we had a problem with the YaST:Devel repo on Leap 15.6: There was no repo based on the openSUSE_Leap_15.6_Update OBS project, just one based on openSUSE_Leap_15.6. That used to work for a while - until there were a number of updates available which would now cause dependency problems: With a newer libzypp, you'd now have to either keep the outdated older libzypp version, or downgrade all YaST packages to the one from 15.6 GA. Now there is the correct YaST:Devel repo: https://download.opensuse.org/repositories/YaST:/Head/openSUSE_Leap_15.6_Up… You can either remove and then re-add your existing YaST:Head repo, or simply edit the URL in the .repo file in /etc/zypp/repos.d : [repo-yast-head] name=YaST:Head enabled=1 autorefresh=1 baseurl=https://download.opensuse.org/repositories/YaST:/Head/openSUSE_Leap… path=/ type=rpm-md priority=50 keeppackages=0 I realized the problem first when I did a manual zypper migration of my old Leap 15.5 to 15.6 with the YaST:Head repo first disabled, then re-enabled: It complained that there was no https://download.opensuse.org/repositories/YaST:/Head/openSUSE_Leap_15.6_Up… , so I removed the '_Update' part to make it work; which turned out to be a bad idea. If you did something similar, please use the new URL above. Kind regards -- Stefan Hundhammer <shundhammer(a)suse.de> YaST Developer SUSE Software Solutions Germany GmbH GF: Ivo Totev; HRB 36809, AG Nürnberg

2 1

Short documentation about WSL (Windows Subsystem for Linux)
by Ladislav Slezak 26 Sep '24

26 Sep '24

Hi all, Recently I have implemented a small feature for WSL. During that process I learned a bit about the WSL, how to install it, use it, etc... I wrote my findings in this document: https://github.com/yast/yast-firstboot/blob/master/doc/testing_wsl.md Enjoy! 😉 -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

1 0

Agama reorganization at Github
by Ancor Gonzalez Sosa 24 Sep '24

24 Sep '24

For some time we have been feeling we need to have several different repositories related to Agama at Github. And we also have been experiencing doubts about how correct is to have the repository under the openSUSE organization at Github. So today we discussed the topic and reached the following agreement. - We will create a new organization "agama-project" at Github. - We will move the openSUSE/agama repository to the new organization. - We will then create separate repositories for the new Agama website and for the crate we are developing to access libzypp from Rust. - At some point in the future, we will also separate the current "/live" directory from the main repository into its own dedicated repo. We plan to do all that (except the last point) tomorrow. So speak up if you oppose. Cheers. -- Ancor González Sosa YaST Team at SUSE Software Solutions

1 0

SLE-15-SP7 branch created
by Ladislav Slezak 17 Sep '24

17 Sep '24

Hi all, I have created the SLE-15-SP7 branch in all relevant YaST Git repositories. The changes are submitted automatically via Jenkins, it is enough to just merge to this branch. Reminder: Whenever you merge a fix to SP6 do not forget to merge the change also to SP7 (and master). Enjoy! 😀 -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

1 0

Unable to run `yast2 autoyast check-profile` in a non-interactive way
by Ioannis Bonatakis 12 Aug '24

12 Aug '24

The goal is to automate the AY profiles which come as .erb templates. We want this for CI I use an TW container which works in an interactive way. However I cant find a way to workaround the warnings and confirmation popups. The command I run is ``` yast2 autoyast check-profile filename=contrib/ay-openqa-worker.xml.erb output=result.xml run-erb=true ``` is there a way to run `check-profile` in a non-interactive way? -- uid Ioannis Bonatakis <ybonatakis(a)suse.com> Key fingerprint = F1CE 542D C18F 89E5 14B7 228E 7483 CFE0 C770 3696

2 3

Reformating the Agama front end code
by David Diaz 12 Jul '24

12 Jul '24

Hi there! I just wanted to let you know that, for the sake of consistency, today we have reformatted all the Agama frontend code base using Prettier and its default settings, except for line length, which has been kept at 100 characters. See https://github.com/openSUSE/agama/pull/1460 Regards.

1 0