October 2020 - YaST Development - openSUSE Mailing Lists

[yast-devel] openSUSE Conference 2020
by Ancor Gonzalez Sosa 14 Oct '20

14 Oct '20

For those of you who may have overlooked it, starting tomorrow the openSUSE + LibreOffice Virtual Conference will take place online. https://events.opensuse.org/conferences/oSLO Some talks may be interesting for YaST enthusiasts in general or for the YaST Team at SUSE in particular, so check the schedule. This is my particular list in that regard: Integration testing framework for YaST modules https://events.opensuse.org/conferences/oSLO/program/proposals/3277 Top 25 New Features in (Auto)YaST https://events.opensuse.org/conferences/oSLO/program/proposals/3265 Keep up with openSUSE Packaging https://events.opensuse.org/conferences/oSLO/program/proposals/3361 Leap Next https://events.opensuse.org/conferences/oSLO/program/proposals/2960 Transfer a Z System onto your own PC https://events.opensuse.org/conferences/oSLO/program/proposals/3140 Meet the openSUSE board https://events.opensuse.org/conferences/oSLO/program/proposals/3316 Of course, there are many other interesting sessions. Check the full schedule. Cheers. -- Ancor González Sosa YaST Team at SUSE Software Solutions -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Mounting Btrfs subvolumes when there are no snapshots
by Ancor Gonzalez Sosa 14 Oct '20

14 Oct '20

As part of the current effort to improve how we display Btrfs subvolumes in the Partitioner I was checking how we mount them. We always create a fstab entry for each subvolume like /home, /var... That makes a lot of sense when the system has support for snapshots, because the default subvolume is .snapshots/1/snapshot, so those fstab entries are needed to make the content of each subvolume available in the expected location. But when there are no snapshots, the default subvolume is the top-level one (in openSUSE) or the "@" (in SLE). All other subvolumes are children of that one, which means their content would be already available in the expected location. But still we redundantly mount all those subvolumes via fstab. I find that not only redundant but even confusing. If the users decides to umount, let's say, /home... they will see the content is still there after unmounting, which may be puzzling. Does somebody know what's the purpose of mounting those subvolumes when there are no snapshots? Cheers -- Ancor González Sosa YaST Team at SUSE Software Solutions -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 2

[yast-devel] storage and used_features
by Arvin Schnell 14 Oct '20

14 Oct '20

Hi, bug #1065588 is still open. It deals with the installation of NTFS packages if an NTFS file system is found on the system. Even though the file system is not mounted YaST wants to install the NTFS tools. Some users do not like that behaviour. The idea already mentioned in the bug is to make the used features as reported by libstorage-ng more relaxed: When a file system is present but not mounted the corresponding used feature will not be set. So YaST will not propose to install the tools. I think this has one disadvantage: When making a new installation the NTFS tools will not be installed (since AFAIR YaST does not create entries in fstab for those anymore). Anyway, now users or desktop environments cannot mount NTFS. That looks like a regression to me. So my proposal is to have a used_features() function in libstorage-ng that takes an argument, say REQUIRED and SUGGESTED. During installation YaST would install the SUGGESTED tools. In the running system it would only install the REQUIRED tools. Does that look fine? This has one additional consequence: The user could use YaST to just create an XFS. In that case the XFS tools are not required in the final system - but surely they are required to create the XFS. So the actiongraph will also have a used_features() function and YaST must install the corresponding tools. Comments? ciao Arvin -- Arvin Schnell, <aschnell(a)suse.com> Senior Software Engineer, Research & Development SUSE Software Solutions Germany GmbH Maxfeldstraße 5 90409 Nürnberg Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 2

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 12 Oct '20

12 Oct '20

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-autoinstallation: - [PoC] Run the unit tests in parallel (47 days) https://github.com/yast/yast-autoinstallation/pull/670 - Find the Base Product (160 days) https://github.com/yast/yast-autoinstallation/pull/599 Pending requests in repository yast-devtools: - changes (7 days) https://github.com/yast/yast-devtools/pull/154 - Y2logs analyzer (229 days) https://github.com/yast/yast-devtools/pull/149 - Move desktop files (9 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-installation: - [WIP] Warn when an old package is selected to install (16 days) https://github.com/yast/yast-installation/pull/878 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (9 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-theme: - Add pattern-budgie icon (boo#1176164) (17 days) https://github.com/yast/yast-theme/pull/131 Pending requests in repository yast-yast2: - Change the way groups are defined (9 days) https://github.com/yast/yast-yast2/pull/936 Pending requests in repository yast-ycp-ui-bindings: - [WIP] automatic tests for TUI (ncurses) (10 days) https://github.com/yast/yast-ycp-ui-bindings/pull/56 Pending requests in repository yast-ruby-bindings: - Distinguish parsing errors from internal errors (bsc#1174198) (17 days) https://github.com/yast/yast-ruby-bindings/pull/249 - [WIP] Don't crash on NoMethodError when Perl is involved (7 days) https://github.com/yast/yast-ruby-bindings/pull/224 Pending requests in repository yast-rake: - Switch desktop directory (9 days) https://github.com/yast/yast-rake/pull/70 Pending requests in repository yast-cio: - convert to libyui ruby bindings (205 days) https://github.com/yast/yast-cio/pull/34 Pending requests in repository skelcd-control-openSUSE: - Adjust the roles to the new YaST Patterns (286 days) https://github.com/yast/skelcd-control-openSUSE/pull/195 Pending requests in repository yast-auth-server: - Fix an issue where pkg dependencies were not install (16 days) https://github.com/yast/yast-auth-server/pull/63 - Fixes to make the YaST modules work (473 days) https://github.com/yast/yast-auth-server/pull/48 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (6 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository yast-vpn: - [SLE15-SP3] Place file selection buttons at the bottom (179 days) https://github.com/yast/yast-vpn/pull/18 ERROR: API query limit exceeded -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Automatic AutoYaST Schema Validation
by Imobach González Sosa 05 Oct '20

05 Oct '20

Hi all, As you may know, we introduced automatic profile validation in AutoYaST for SLE 15 SP3 and Tumbleweed. When the profile is not correct, AutoYaST complains at the beginning of the autoinstallation. So, as expected, we are getting regular bug reports from openQA. In some cases, the profile is just wrong. However, we have detected several problems in yast2-schema. Although you can disable this feature at boot time (setting YAST_SKIP_XML_VALIDATION to 1), I fear that we are going to get a ton of errors from our users and customers. So I was considering whether we should disable this feature by default, although in that case I would ask openQA to enable it so we can improve yast2- schema quality. What is your point of view? Regards, Imo -- Imobach González Sosa YaST Team at SUSE LLC https://imobachgs.github.io/

6 10

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 05 Oct '20

05 Oct '20

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-autoinstallation: - [PoC] Run the unit tests in parallel (40 days) https://github.com/yast/yast-autoinstallation/pull/670 - Find the Base Product (153 days) https://github.com/yast/yast-autoinstallation/pull/599 Pending requests in repository yast-devtools: - Y2logs analyzer (222 days) https://github.com/yast/yast-devtools/pull/149 Pending requests in repository yast-installation: - [WIP] Warn when an old package is selected to install (9 days) https://github.com/yast/yast-installation/pull/878 Pending requests in repository yast-theme: - Add pattern-budgie icon (boo#1176164) (10 days) https://github.com/yast/yast-theme/pull/131 Pending requests in repository yast-ycp-ui-bindings: - WIP: Nested Items in Table Widgets (11 days) https://github.com/yast/yast-ycp-ui-bindings/pull/55 Pending requests in repository yast-ruby-bindings: - Distinguish parsing errors from internal errors (bsc#1174198) (10 days) https://github.com/yast/yast-ruby-bindings/pull/249 Pending requests in repository yast-cio: - convert to libyui ruby bindings (198 days) https://github.com/yast/yast-cio/pull/34 Pending requests in repository skelcd-control-openSUSE: - Adjust the roles to the new YaST Patterns (279 days) https://github.com/yast/skelcd-control-openSUSE/pull/195 Pending requests in repository yast-auth-server: - Fix an issue where pkg dependencies were not install (9 days) https://github.com/yast/yast-auth-server/pull/63 - Fixes to make the YaST modules work (466 days) https://github.com/yast/yast-auth-server/pull/48 Pending requests in repository yast-vpn: - [SLE15-SP3] Place file selection buttons at the bottom (172 days) https://github.com/yast/yast-vpn/pull/18 ERROR: API query limit exceeded -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] YaST in Hacktoberfest?
by Srinidhi B 01 Oct '20

01 Oct '20

Hello YaST Team, I was looking at the list of issues marked for Hacktoberfest [1] and couldn't find any YaST issues marked for it. I don't see YaST mentioned in the openSUSE blog post for Hacktoberfest as well. Are there any plans to participate in Hactoberfest? Regards, Srinidhi. [1] https://github.com/search?q=label%3Ahacktoberfest+state%3Aopen+no%3Aassigne… [2] https://news.opensuse.org/2020/09/14/opensuse-projects-support-hacktoberfes… N��r��y隊\��^��~�{.n�+��Ǩ��r��i�m��0��ޙ��ɫ-u�ޗ�0��Ǩ�

3 3