YaST Development July 2022

yast-devel@lists.opensuse.org

9 participants
11 discussions

D-Installer 0.4.2 released (and submission to Factory status update)

by Imobach Gonzalez Sosa

Hi all, After releasing D-Installer 0.4.1, we found an issue that we felt should be fixed ASAP. So I am releasing 0.4.2 today. ## Change * Prevent the installation from being blocked when the user changes the language (gh#yast/yast-dinstaller#239 and gh#yast/yast-dinstaller#240). * Add a new service org.opensuse.DInstaller.Language to handle yast2-country related logic. ## Submission to Factory Previous submission requests were declined because YaST:Head:D- Installer is not a devel project for openSUSE:Factory. But before asking for help to build service admins, I wonder if we should move our packages to YaST:Head instead. Regards, Imo -- Imobach González Sosa YaST Team at SUSE LLC https://imobachgs.github.io/

1 week, 3 days

D-Installer 0.4.1 released and submitted to Factory

by Imobach Gonzalez Sosa

Hi all, Today we are announcing the release of D-Installer 0.4.1 and its submission to Factory (finally!). If you are brave enough and you would like to give it a try, you can grab the ISO from the YaST:Head:D-Installer project: https://build.opensuse.org/package/binaries/YaST:Head:D-Installer/d-install… ## Changes * Adapt the CLI to the new D-Bus status/progress reporting API (gh#yast/d-installer#229). * The software service respond to D-Bus messages during software installation (gh#yast/d-installer#223), so the progress is properly refreshed during installation. * Fix several user interface-related issues (gh#yast/d-installer#230): - Avoid reloading the page when pushing the enter key. - Always display the D-Bus error page when the connection gets broken. Reload the UI again when the D-Bus connection is working again. - Update the product selection page when the product is modified in background (e.g., using the CLI). - Update the first user settings when they are changed in background. - Refresh the storage section when the settings are modified in background. - If the storage proposal fails, display the error even after reloading the page. ## Submission to Factory * rubygem-d-installer: https://build.opensuse.org/request/show/991367 * rubygem-d-installer-cli: https://build.opensuse.org/request/show/991368 * cockpit-d-installer: https://build.opensuse.org/request/show/991369 Best regards, Imo -- Imobach González Sosa YaST Team at SUSE LLC https://imobachgs.github.io/ -- Imobach González Sosa

1 week, 4 days

Pending Pull Requests

by yast-ci＠opensuse.org

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 (13 days) https://github.com/yast/yast-devtools/pull/168 - Set %yast_icondir to /usr/share/icons/hicolor (bsc#1186066) (167 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-installation: - another try at adressing the hidpi issue (bsc#1199020) (16 days) https://github.com/yast/yast-installation/pull/1049 - Fixed a syntax error in the README (51 days) https://github.com/yast/yast-installation/pull/1047 - Remake some icons (132 days) https://github.com/yast/yast-installation/pull/1028 Pending requests in repository yast-kdump: - Implement KDUMP_AUTO_RESIZE (90 days) https://github.com/yast/yast-kdump/pull/123 Pending requests in repository yast-packager: - Remake some icons (151 days) https://github.com/yast/yast-packager/pull/603 Pending requests in repository yast-theme: - Add pantheon desktop support (236 days) https://github.com/yast/yast-theme/pull/154 Pending requests in repository yast-update: - [SP3] Use the "norecovery" mount option (bsc#1195894) (159 days) https://github.com/yast/yast-update/pull/179 Pending requests in repository yast-auth-server: - Remove Kerberos Functionality (45 days) https://github.com/yast/yast-auth-server/pull/74 - Fix log path (121 days) https://github.com/yast/yast-auth-server/pull/72 Pending requests in repository yast.github.io: - [dependencies] Bump nokogiri from 1.13.3 to 1.13.6 (66 days) https://github.com/yast/yast.github.io/pull/324 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (166 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository helper_scripts: - [dependencies] Bump nokogiri from 1.13.3 to 1.13.6 in /jekyll (66 days) https://github.com/yast/helper_scripts/pull/39 Pending requests in repository yast-samba-provision: - Sle15 sp1 update (65 days) https://github.com/yast/yast-samba-provision/pull/10 Pending requests in repository yast-sap-ha: - Sle 15 sp3 (34 days) https://github.com/yast/yast-sap-ha/pull/9

1 week, 6 days

YaST: 5th development report of 2022

by Ancor Gonzalez Sosa

Since the YaST team is lately involved in many projects not limited to YaST itself, we decided to expand a bit the scope of our blog to cover those (mainly ALP-related) topics. Check our latest post with: - Some notes about the already mentioned change in scope for the blog - The announcement of D-Installer 0.4 - A brief introduction to Iguana, a container-capable boot image - Progress on containerized YaST - Some Cockpit news See the whole report at https://yast.opensuse.org/blog/2022-07-19/yast-report-2022-5 Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH

2 weeks, 5 days

Pending Pull Requests

by yast-ci＠opensuse.org

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 (6 days) https://github.com/yast/yast-devtools/pull/168 - Set %yast_icondir to /usr/share/icons/hicolor (bsc#1186066) (160 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-installation: - another try at adressing the hidpi issue (bsc#1199020) (9 days) https://github.com/yast/yast-installation/pull/1049 - Fixed a syntax error in the README (44 days) https://github.com/yast/yast-installation/pull/1047 - Remake some icons (125 days) https://github.com/yast/yast-installation/pull/1028 Pending requests in repository yast-kdump: - Implement KDUMP_AUTO_RESIZE (83 days) https://github.com/yast/yast-kdump/pull/123 Pending requests in repository yast-packager: - Remake some icons (144 days) https://github.com/yast/yast-packager/pull/603 Pending requests in repository yast-theme: - Add pantheon desktop support (229 days) https://github.com/yast/yast-theme/pull/154 Pending requests in repository yast-update: - [SP3] Use the "norecovery" mount option (bsc#1195894) (152 days) https://github.com/yast/yast-update/pull/179 Pending requests in repository yast-auth-server: - Remove Kerberos Functionality (38 days) https://github.com/yast/yast-auth-server/pull/74 - Fix log path (114 days) https://github.com/yast/yast-auth-server/pull/72 Pending requests in repository yast.github.io: - [dependencies] Bump nokogiri from 1.13.3 to 1.13.6 (59 days) https://github.com/yast/yast.github.io/pull/324 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (159 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository helper_scripts: - [dependencies] Bump nokogiri from 1.13.3 to 1.13.6 in /jekyll (59 days) https://github.com/yast/helper_scripts/pull/39 Pending requests in repository yast-samba-provision: - Sle15 sp1 update (58 days) https://github.com/yast/yast-samba-provision/pull/10 Pending requests in repository yast-sap-ha: - Sle 15 sp3 (27 days) https://github.com/yast/yast-sap-ha/pull/9

2 weeks, 6 days

D-Installer 0.4 released

by Imobach Gonzalez Sosa

Hi all, Today we released D-Installer 0.4. This release was focused on improving the architecture and the internals of D-Installer. You can read the relevant stuff in this GitHub issue: https://github.com/yast/d-installer/pull/223 Perhaps we might consider publishing the content of that issue in our blog. What do you think? Regards, Imo -- Imobach González Sosa YaST Team at SUSE LLC https://imobachgs.github.io/

3 weeks, 2 days

Pending Pull Requests

by yast-ci＠opensuse.org

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 (61 days) https://github.com/yast/yast-devtools/pull/168 - Set %yast_icondir to /usr/share/icons/hicolor (bsc#1186066) (153 days) https://github.com/yast/yast-devtools/pull/161 Pending requests in repository yast-installation: - Do not restart services when the package is updated (24 days) https://github.com/yast/yast-installation/pull/1048 - Fixed a syntax error in the README (37 days) https://github.com/yast/yast-installation/pull/1047 - Remake some icons (118 days) https://github.com/yast/yast-installation/pull/1028 Pending requests in repository yast-kdump: - Implement KDUMP_AUTO_RESIZE (76 days) https://github.com/yast/yast-kdump/pull/123 Pending requests in repository yast-packager: - Remake some icons (137 days) https://github.com/yast/yast-packager/pull/603 Pending requests in repository yast-python-bindings: - Boo1200804 (18 days) https://github.com/yast/yast-python-bindings/pull/43 - Sle15 sp1 examples fixup (18 days) https://github.com/yast/yast-python-bindings/pull/42 Pending requests in repository yast-theme: - Add pantheon desktop support (222 days) https://github.com/yast/yast-theme/pull/154 Pending requests in repository yast-update: - [SP3] Use the "norecovery" mount option (bsc#1195894) (145 days) https://github.com/yast/yast-update/pull/179 Pending requests in repository yast-auth-server: - Remove Kerberos Functionality (31 days) https://github.com/yast/yast-auth-server/pull/74 - Fix log path (107 days) https://github.com/yast/yast-auth-server/pull/72 Pending requests in repository yast.github.io: - [dependencies] Bump nokogiri from 1.13.3 to 1.13.6 (52 days) https://github.com/yast/yast.github.io/pull/324 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (152 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository helper_scripts: - [dependencies] Bump nokogiri from 1.13.3 to 1.13.6 in /jekyll (52 days) https://github.com/yast/helper_scripts/pull/39 Pending requests in repository yast-samba-provision: - Sle15 sp1 update (51 days) https://github.com/yast/yast-samba-provision/pull/10 Pending requests in repository yast-sap-ha: - Sle 15 sp3 (20 days) https://github.com/yast/yast-sap-ha/pull/9

3 weeks, 6 days

Re: ALP WG Meeting minutes - July 5th 2022

by Lars Vogdt

> > Please correct me, if my assumptions are wrong: > > * A Flatpak will include all needed libraries, which will blow up > > the needed (installation and mirror) space > > No, flatpaks support runtimes which would contain the required > libraries and these are shared between different flatpaks. E.g. on > flathub you already have a GNOME runtime and a KDE runtime. We could > create our own openSUSE Tumbleweed runtime and base our flatpaks on > that. This sounds to me like: "Flatpak is just another packaging format. But instead to rely on packagers to provide Apparmor/SeLinux profiles, Flatpaks are using cgroups from the beginning, which makes them more secure." - Is that description close enough to the truth? > >> > 2) Will ALP still allow one 'zypper up' call to update all > >> > software (container, flatpak, rpm) on a system? > >> > > >> > 3) Will OBS auto-convert current rpms to flatpaks? > >> > >> Theoretically that could be done, but I think that's at the moment > >> out of scope. > > > > For 2, does this mean we loose the current benefit of updating a > > whole system with just one single tool? > > > > So for 3, this currently means that packagers have more work, > > because they need to provide the needed Flatpak build configuration > > as well? > > Not really. Currently a packager has to provide a spec file for every > code stream and maintain those independently and make them build. With > flatpaks in the mix, you'd have to maintain a single code stream and a > flatpak build description. IMHO this answer is wrong. Most packages in OBS are not using spec files for every code stream, but include macros in one single spec file to build for multiple code streams. But this brings me to two other questions: 10) Is there something like _multibuild support planned for Flatpak? 11) Will there be a tool to convert spec files into Flatpak files? > > How is a migration from RPM to Flatpak expected in this case? > > Afaik there are no plans to support a migration from SLE to ALP. Are there plans to support a migration from openSUSE to ALP? Regards, Lars

1 month

Modified installation progress

by josef Reidinger

Challenge: ---------- Libzypp supports parallel download and install. Yast installation progress does not fit it at all [1]. Issues are secondary progress bar that does not work with parallel installation. Also there are overwhelming amount of information on screen that is quite distracting. That information is often wrong like time estimation. And also table for media is a bit useless nowadays as everything is on one iso/medium, so there is no need to see when cd switch will be needed. The details tab are the most visible as it is default one. Proposal: --------- Remove completely that details tab and keep just release notes one[2]. It contains release notes that contain useful information and also has just one progress bar. For that bar remove keep always just remaining size and count of packages, so user has idea how it does, but do not print what exactly is installing or any time estimation. If there are more release notes allow to switch between them. Also keep possibility to have slide show which we had in past for installation if someone create some ( when checked other OSes, the Ubuntu slide show during installation looks probably the best from user POV ). The same changes will apply to ncurses front end[3], we just need to check why formatting of release notes are so badly formatted. And same for opensuse[4] of course. Josef [1] https://pasteboard.co/cNBjER6SnLLT.png [2] https://pasteboard.co/WnI7wS7VVVqq.png [3] https://pasteboard.co/vzQvY1PaVDaD.png [4] https://pasteboard.co/FzEqcIN7Xnas.png

1 month

Re: Modified Progress Video

by Lukáš Krejza

Hi, Dne 5. 7. 2022 12:59 napsal uživatel Kenneth Wimer <wimer(a)suse.com>: Hi all, I would like to understand this better from a UX perspective. What action can a user take during installation to remedy a situation in which some package couldn’t be installed? Switch to TTY with ctrl+alt+f4 and debug. What circumstances lead to these failures? Anything from non-standard hardware, configuration, package selection or just outdated iso and some mirrors unavailable Is this information available in a log file? Should be in zypp log AFAIK, but switching to TTY and doing "tail -f /var/log/zypp/*" is not very ergonomic IMHO. What action can a user take during installation vs after? Manually download broken RPM to cache, do a debug, reinstall, restart installation with modified configuration to workaround an issue, ... Is the “normal” linux text boot still accessible by a switch at the bootloader stage? Just press esc. Or you can disable plymouth completely as a kernel param. Best regards, Kenneth Cheers, Gfs on the road

1 month

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

YaST Development July 2022