February 2024 - YaST Development - openSUSE Mailing Lists

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

Agama on default HTTPS port, Avahi/mDNS
by Ladislav Slezak 01 Feb '24

01 Feb '24

Hi all, I have updated the Agama Live ISO in Staging to use the standard HTTPS port instead of the default Cockpit port 9090. That should make it easier to use Agama, you do not need to add the ":9090" part to the Agama URL. The automatic HTTP -> HTTPS redirection is also active. Additionally Avahi/mDNS has been enabled, you can use the https://agama.local URL to connect to the running Agama instance. (Note: You might need to configure the firewall to allow resolving the ".local" names. For Android phones you need Android 12+.) You can always access the Agama instance using a plain IP address if Avahi/mDNS does not work for you. The old way still works. You can now also scan the local network for all running Agama instances with this command: avahi-browse -t -r _agama._sub._https._tcp See more details in https://github.com/openSUSE/agama?tab=readme-ov-file#avahimdns This change will be later propagated also to the next official Agama release. Enjoy! 😉 Ladislav -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

3 6