- YaST Development

Fwd: Submitting Agama 9 and agama-installer-openSUSE to Factory
by Luna Jernberg 11 Jul '24

11 Jul '24

---------- Forwarded message --------- Från: Luna Jernberg <droidbittin(a)gmail.com> Date: tors 11 juli 2024 kl 10:08 Subject: Re: Submitting Agama 9 and agama-installer-openSUSE to Factory To: Lubos Kocman <lubos.kocman(a)suse.com>, Ancor Gonzalez Sosa <ancor(a)suse.de>, bittin <bittin(a)opensuse.org>, Luna Jernberg <droidbittin(a)gmail.com>, Ladislav Slezák <lslezak(a)suse.com>, José Iván López González <jlopez(a)suse.de>, Imobach Gonzalez Sosa <IGonzalezSosa(a)suse.com>, josef Reidinger <jreidinger(a)suse.cz> Hey! I got a bit of a feeling and updated the Swedish translation today, but i will work on very low energy during the summer, as i don't really feel good mentally so don't expect me to contribute as fast as before Den tis 2 juli 2024 kl 12:59 skrev Lubos Kocman via openSUSE Factory <factory(a)lists.opensuse.org>: > > Hello openSUSE! > > I hope that you all share the excitement from the progress that the > Agama/YaST team shared on osc2024! > YaST blog has a nice summary of all new features > https://yast.opensuse.org/blog/2024-06-28/agama-9. All osc2024 videos > should be soon at > https://www.youtube.com/playlist?list=PL_AMhvchzBadtOw4K3kWfWhidyhXPnW9P > in case you need more context. > > I sat together with Max and YaST folks by the table at the openSUSE > Conference and we were able to get a bootable Leap 16.0 image deployed > by Agama 9. Many thanks to the team for their support in incorporating > our submissions at https://github.com/openSUSE/agama. Here's the Leap > 16 Image, just please don't try to install Leap16/GNOME yet. I hope to > get that working by end of the week :) > https://download.opensuse.org/repositories/openSUSE:/Leap:/16.0:/Images/ima… > > With that said, I believe this is the right time to get all bits to > Factory so early adopters can get their hands on it. See my Leap 16 > feature tracker for a list of initial Agama submissions to Factory > https://code.opensuse.org/leap/features/issue/158 > > agama-installer-openSUSE (the actual deliverable) is a live image that > can, at the moment, install a variety of openSUSE distributions, > namely MicroOS, *Leap 16, and Tumbleweed. You can find specific distro > configs in agama-products-opensuse. After initial feedback from Leap > Micro 6.0 GA, I'd also like to consider adding support for Leap Micro > 6.X to satisfy a few individuals for who the self-install simply > doesn't cut it. > > Please consider the agama-install-openSUSE as an alternative for early > adopters who like to play with new tech. We still have some homework > to do as this is currently online installer-only. Yes, you can use > Packages DVD with Agama, but that might be too large for some. > > Being fully transparent here, the long-term plan would be to adopt > Agama by default in Tumbleweed, Leap 16 / SLES 16, and Leap Micro 6.X. > I can imagine that if everything goes well the transition could happen > with Leap 16 GA somewhen in 2nd half of 2025 > https://en.opensuse.org/openSUSE:Roadmap#DRAFT_Schedule_for_openSUSE_Leap_1… > > Many thanks to the Agama/YaST team for all of their hard work! > The project is nowhere close where it was last year. > > Lubos > on behalf of openSUSE release team

1 0

Error : No workflow defined for this installation mode
by Gabriel MACHADO 07 Jul '24

07 Jul '24

Hello, I have build an opensuse microOS iso image with kiwi-ng successfully. Then, I tried to customize my iso with an autoyast profile with the help of this documentation : https://osinside.github.io/kiwi/working_with_images/setup_yast_on_first_boo… The image was built successfully but when I use it, I have the following error : No workflow defined for this installation mode What does mean this error ? How can I fix it ? Should the kiwi-ng documentation be updated ? I also reported this issue on kiwi google group: https://groups.google.com/g/kiwi-images/c/r3L_fwXp3Xc Regards, Gabriel.

2 4

Dropping systemsmanagement:Agama:Staging
by Imobach Gonzalez Sosa 02 Jul '24

02 Jul '24

Hi all, We are in the middle of submitting Agama code to openSUSE:Factory. So there are a few changes you should be aware of: * We are phasing out systemsmanagement:Agama:Staging[1] and the project will be removed in a few hours. * From now on, all the code will be automatically submitted to systemsmanagement:Agama:Devel[1]. This will be the development project for Agama. * The agama-live package has been renamed to agama-installer-openSUSE. We are updating the docs and the workflows in https://github.com/openSUSE/agama/pull/1425, Sorry for any inconvenience it may cause. Regards, Imo [1] https://build.opensuse.org/project/show/systemsmanagement:Agama:Devel

1 0

Fwd: Announcing Agama 8
by Ancor Gonzalez Sosa 31 May '24

31 May '24

This mail made me realize I should publish the announcements with a reply-to to yast-devel. Forwarding it (a bit more manual). -------- Forwarded Message -------- Subject: Re: Announcing Agama 8 Date: Thu, 30 May 2024 16:47:56 +0200 From: Marcela Mašláňová <xyz(a)abcd.com> To: Ancor Gonzalez Sosa <ancor(a)suse.de> Hi, I tried out agama-live.s390x-8.0.0-openSUSE-Build1.22.iso inqemu. The s390x not even boot. It complained about missing dasd and then it ended up in some odd state not even starting the installer. I opened the x86_64 image which offered installer right away. And it looks good. I suppose some important piece is missing in s390x. Thank you, Marcela "future Ihno" Maslanova On Fri, May 17, 2024 at 3:19 PM Ancor Gonzalez Sosa <ancor(a)suse.de <mailto:ancor@suse.de>> wrote: The first Cockpit-free version of Agama was just published today. This pre-release may be a big rough around the edges, so feedback would be appreciated. See more details at the official announcement: https://yast.opensuse.org/blog/2024-05-17/agama-8 <https://yast.opensuse.org/blog/2024-05-17/agama-8> Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH

1 0

Agama 8 is out
by Ancor Gonzalez Sosa 17 May '24

17 May '24

Agama just switched to a more lightweight architecture which no longer depends on Cockpit. Agama 8 is the first pre-release to take advantage of it. This version may be a big rough around the edges, so feedback would be appreciated. See more details at the YaST Team blog: https://yast.opensuse.org/blog/2024-05-17/agama-8 Enjoy -- Ancor González Sosa YaST Team at SUSE Linux GmbH

1 0

Agama and YaST at the openSUSE Conference 2024
by Ancor Gonzalez Sosa 12 Apr '24

12 Apr '24

The call for papers closes in less than two weeks. Time to plan our presence there and submit all the abstracts. Cheers. -- Ancor González Sosa YaST Team at SUSE Software Solutions

4 6

JFYI: new zypp::VendorSupportOption::VendorSupportSuperseded
by Michael Andres 18 Mar '24

18 Mar '24

https://jira.suse.com/browse/PED-8014 https://jira.suse.com/browse/OBS-301 Hi. We're about to introduce a new zypp::VendorSupportOptionzypp enum value VendorSupportSuperseded: /** * The package was discontinued and has been superseded by a new package * with a different name. The new package is the successor of the * old package, and as such only the new package is supported * in the future. * * The old package will not receive updates anymore, so it's highly * recommended to switch to the new package as soon as possible. * * \Note Packages carrying this flag also return the name of a * successor in \ref Package::supersededBy(). */ VendorSupportSuperseded It's slightly different than the well known VendorSupport{ACC,Level[123]} enum values. Packages with VendorSupportSuperseded will also offer a list of package names (and most probably a list of satSolvables in Package::supersededByItems). The user string for the enum value is kind of generic: "The package was discontinued and has been superseded by a new package with a different name." It may be appropriate to somehow join it with the list of superseding items. The API to retrieve the values will be available in libzypp 17.32.0. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres (he/him/his), Engineering & Innovation, ma(a)suse.com +------------------------------------------------------------------+ SUSE Software Solutions Germany GmbH www.suse.com Frankenstr. 146, 90461 Nuernberg, Germany Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg) +------------------------------------------------------------------+

1 0

Announcing Agama 7
by Imobach Gonzalez Sosa 28 Feb '24

28 Feb '24

Hi all, We are pleased to announce the availability of Agama 7. Among other features, it brings: * Allow choosing localization settings for the installed system (language, keyboard and timezone). * Use zram to reduce memory consumption. * Add support to install MicroOS and MicroOS Desktop. Drop Leap 16.0 support. * Simplified software selection based on a curated list of patterns per product. * Registration support. It is enabled for Dolomite. * Allow to select the file system type selection and to choose a policy to make space. * Support for network bonding in the unattended scenario. If you are interested in the details, please check the announcement on our team's blog: https://yast.opensuse.org/blog/2023-12-22/agama7 Thanks! Regards, Imo

4 15

Blog post: Agama future plans
by Ancor Gonzalez Sosa 08 Feb '24

08 Feb '24

Will 2024 be the year for Agama (the new installer based on YaST internals) to finally take off? Find more about the YaST Teams plans at the new blog post https://yast.opensuse.org/blog/2024-02-08/year-of-agama Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH

1 0

New Rubocop Version
by josef Reidinger 01 Feb '24

01 Feb '24

Hi there, as i work on migrating old configuration to newer rubocop version we support, i also take oppurtinity and some learning time to try the latest rubocop version. I am creating three experimental pull requests. One is for yast2.rpm, which is a combination of new and old code, storage-ng, which is just new code, and yast2-country, which has no rubocop at all. And let me write here what I see: yast2 - https://github.com/yast/yast-yast2/pull/1298 only automatic fixes (both -a and -A) are applied and a test fixture needs to be modified as new cop also contains some FileUtils changes. Storage-ng - https://github.com/yast/yast-storage-ng/pull/1364 is more tricky. As one of the changes is that methods with `?` at the end of the name should return boolean, but in storage there are methods that use nil to indicate not specified. I am not sure which is correct, but we need to be aware of this and perhaps disable it if it is intentional. And also a bug is found in the code https://github.com/yast/yast-storage-ng/pull/1364/commits/0d4a52f44c19a9e89… (it is not revealed as it looks like the method is not called at all). country - https://github.com/yast/yast-country/pull/321 is a bit bigger, as rubocop was not there before. But thanks to a lot of autocorrection it was not that bad. Unfortunately, I also have a bug in the autocorrection that has already been reported to rubocop. The good thing is that rubocop itself detects it after a change and reports invalid syntax. I also see two infinite loops in the autocorrection, which new rubocop reports quite well, so I improve the code manually and everything works fine. Overall impression is that after applying new cops code looks better and especially new syntax for named parameters really improve feel of our ruby code so it start looking like modern ruby code. Of course, porting from SLE15 will be more work, but due to many autocorrections I think it will be quite smooth. Another thing we can do for a smoother migration to the new version is to disable auto-enable of new cops and decide what to enable and what not to enable one by one (of course in the shared rubocop config). Last but not least, new rubocop does not work on Leap15. So I create my own container with the latest rubocop in which I run it. Another option is to use something like rbenv and for CI just use rpm as CI runs on TW. We can discuss whether to add it or not on the review, but feel free to comment here if you have any thoughts on it. Josef

3 4