November 2020 - YaST Development - openSUSE Mailing Lists

[yast-devel] Innovation Time: Feedback from forums
by josef Reidinger 13 Nov '20

13 Nov '20

Hi, I use my todays innovation time to try to collect feedback from forums and as we have quite nice opensuse retrospective output, I try to focus on SLE. So I use forums.suse.com and here is few links with short description: AutoYast - looking for recommended autoyast profile for VM server http://forums.suse.com/discussion/13055/template-best-practices-and-hardeni… - problem with configuring network using autoyast ( not clear what is root of issue ) http://forums.suse.com/discussion/14165/autoyast-sles15-sp1 - easy way to install also custom rpms in autoyast http://forums.suse.com/discussion/14138/adding-custom-rpm-to-installer - trying to add packages iso to directory and use it in autoyast and failed http://forums.suse.com/discussion/14065/installer-fails-to-find-add-ons-fro… - not clear documenation how to reference files from enhanced DVD in autoyast http://forums.suse.com/discussion/13986/copy-a-file-from-the-installer-dvd - autoyast use case unattended installation from USB - documenation not clear http://forums.suse.com/discussion/12227/sles15-unattended-install-from-usb Storage - user trying to resize living system with partitioner and failed. Error probably does not help much: http://forums.suse.com/discussion/14113/resize-partition-error - kudos to partitioner for easy way of deleting btrfs snapshot http://forums.suse.com/discussion/11718/how-to-delete-btrfs-subvolume - switching DOS MBR and GPT real use case http://forums.suse.com/discussion/13961/need-to-convert-mbr-to-gpt - another fs resize http://forums.suse.com/discussion/13205/file-system-increase - another replacing filesystem, this time root one http://forums.suse.com/discussion/12576/replacing-root-filesystem-from-sdb2… Features ( new use cases ) - disable usb due to sec certificates - ca management missing and auth_server missing wizard like setup http://forums.suse.com/discussion/14022/authentication-server-with-yast-and… - again ca management missing http://forums.suse.com/discussion/13084/ca-management-yast-tool-missing - problem to configure proxy in SLES. Works in opensuse http://forums.suse.com/discussion/14221/install-sles-behind-a-proxy - offline self-update from medium http://forums.suse.com/discussion/13582/self-update-offline Misc - package search with RMT error message confuse user: http://forums.suse.com/discussion/14233/how-to-add-a-module-repo-to-an-exis… - issue with packager, cannot find patterns view http://forums.suse.com/discussion/14120/install-selinux-sles-15-sp1 - people use suse firewall module http://forums.suse.com/discussion/13097/sles-12-sp4-cant-manage-firewall-du… - looks like systemd sockets are not always understandable for users and complain to yast http://forums.suse.com/discussion/12846/vnc-server-service - upgrade of system to the same version sometimes can help with boot problems http://forums.suse.com/discussion/14797/sles12sp5-vm-stuck-at-grub-when-boo… - many confusion with SP1 DVD layout like in http://forums.suse.com/discussion/13504/yast-yast2-is-missing-after-install… - even servers is now installed using USB http://forums.suse.com/discussion/14228/install-from-usb Josef -- 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] YaST: highlights of development sprint 112
by Ancor Gonzalez Sosa 11 Nov '20

11 Nov '20

Time has come for the YaST Team to pay the debts from the previous report: - We promised some news about Cockpit and we have a whole new Cockpit module to present. - We mentioned our talk in the openSUSE + LibreOffice Virtual Conference and now we have the video for you. - We told you we were working on several changes in YaST and it's time to present them all, including big enhancements in the Partitioner UI and other usability improvements. Check the whole report at https://yast.opensuse.org/blog/2020-11-10/sprint-112 Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH

1 0

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

09 Nov '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-devtools: - changes (35 days) https://github.com/yast/yast-devtools/pull/154 Pending requests in repository yast-instserver: - Adapt Rakefile and Dockerfile for SLE-15-SP2 (32 days) https://github.com/yast/yast-instserver/pull/50 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (37 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-theme: - Update branding (10 days) https://github.com/yast/yast-theme/pull/132 - Add pattern-budgie icon (boo#1176164) (45 days) https://github.com/yast/yast-theme/pull/131 Pending requests in repository yast-ruby-bindings: - [WIP] Don't crash on NoMethodError when Perl is involved (35 days) https://github.com/yast/yast-ruby-bindings/pull/224 Pending requests in repository skelcd-control-openSUSE: - AY: write linuxrc proxy and hostname to inst-sys (9 days) https://github.com/yast/skelcd-control-openSUSE/pull/220 - Server Role should install the new yast2_server pattern (33 days) https://github.com/yast/skelcd-control-openSUSE/pull/217 Pending requests in repository yast-auth-server: - Fix an issue where pkg dependencies were not install (44 days) https://github.com/yast/yast-auth-server/pull/63 - Fixes to make the YaST modules work (501 days) https://github.com/yast/yast-auth-server/pull/48 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (34 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository yast-storage-ng: - Add `textdomain` to fix untranslated error messages (472 days) https://github.com/yast/yast-storage-ng/pull/925 Pending requests in repository yast-caasp: - Allow Mirror configuration (34 days) https://github.com/yast/yast-caasp/pull/39 Pending requests in repository yast-rmt: - Add metadata into packages (35 days) https://github.com/yast/yast-rmt/pull/51 - use docker image from OBS (54 days) https://github.com/yast/yast-rmt/pull/50 - Enforce full coverage (54 days) https://github.com/yast/yast-rmt/pull/40 -- 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] btrfs level 0 qgroups
by Arvin Schnell 02 Nov '20

02 Nov '20

Hi, users can do funny things with btrfs qgroups leading to problems: When a subvolume is created a corresponding level 0 qgroup is also created by btrfs. The subvolume id and thus the qgroup id are not predictable (see below). The user can also manually create level 0 qgroups. So the user can 1) manually create qgroup 0/260 and 2) create a subvolume that could get id 260 and the corresponding qgroup gets the id 0/260. A nice qgroup id collision. If libstorage-ng would commit such a setup the manually creation of qgroup 0/260 would fail if it happens after the subvolume creation. Also the user could set different limits for both qgroups which is obviously impossible to commit correctly. I do not see any use-case for level 0 qgroups without a corresponding subvolume. Our btrfs developers also said that there is none. So to avoid such problems with libstorage-ng and YaST I propose to 1) disallow creating level 0 qgroups without an corresponding subvolume and 2) ignore level 0 qgroups without a corresponding subvolume during probing. Item 2) seems like a good idea anyway since btrfs does not delete qgroups when deleting subvolumes, so a hugh number (like several thousands) of useless level 0 qgroups may exist in the system. Comments? Why is the subvolume id not predictable? For once it is not just the next free id: E.g. after deleting all subvolume the ids do not restart at 257. Likely it is possible by further analysis of the btrfs to know the next id but that is internal to btrfs. And finally any other program, e.g. snapper, can concurrently create subvolumes and thus ruin any attempt to predict the ids. 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 4

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

02 Nov '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 (68 days) https://github.com/yast/yast-autoinstallation/pull/670 - Find the Base Product (181 days) https://github.com/yast/yast-autoinstallation/pull/599 Pending requests in repository yast-devtools: - Fixed order in %yast_desktop_files macro (19 days) https://github.com/yast/yast-devtools/pull/155 - changes (28 days) https://github.com/yast/yast-devtools/pull/154 - Y2logs analyzer (250 days) https://github.com/yast/yast-devtools/pull/149 - Move desktop files (30 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-dhcp-server: - Fix URL in spec file (12 days) https://github.com/yast/yast-dhcp-server/pull/55 Pending requests in repository yast-installation: - [WIP] Warn when an old package is selected to install (37 days) https://github.com/yast/yast-installation/pull/878 Pending requests in repository yast-instserver: - Adapt Rakefile and Dockerfile for SLE-15-SP2 (25 days) https://github.com/yast/yast-instserver/pull/50 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (30 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-theme: - Add pattern-budgie icon (boo#1176164) (38 days) https://github.com/yast/yast-theme/pull/131 Pending requests in repository yast-yast2: - Change the way groups are defined (30 days) https://github.com/yast/yast-yast2/pull/936 Pending requests in repository yast-ycp-ui-bindings: - [WIP] automatic tests for TUI (ncurses) (31 days) https://github.com/yast/yast-ycp-ui-bindings/pull/56 Pending requests in repository yast-ruby-bindings: - [WIP] Don't crash on NoMethodError when Perl is involved (28 days) https://github.com/yast/yast-ruby-bindings/pull/224 Pending requests in repository yast-rake: - Switch desktop directory (30 days) https://github.com/yast/yast-rake/pull/70 Pending requests in repository yast-cio: - convert to libyui ruby bindings (226 days) https://github.com/yast/yast-cio/pull/34 Pending requests in repository skelcd-control-openSUSE: - Server Role should install the new yast2_server pattern (26 days) https://github.com/yast/skelcd-control-openSUSE/pull/217 - Fix update external link for non-x86 on Leap - bsc#1120938 (26 days) https://github.com/yast/skelcd-control-openSUSE/pull/215 - Adjust the roles to the new YaST Patterns (307 days) https://github.com/yast/skelcd-control-openSUSE/pull/195 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