YaST Development September 2020

yast-devel@lists.opensuse.org

16 participants
16 discussions

[yast-devel] Reminder: verify_partial_doubles is not default

by Josef Reidinger

Hi, again I hit by thinking that verify_partial_doubles is now default in rspec3. It is not and will be in rspec4. So what it means? rspec does not check if mocked methods exists at all and it can result in many not so funny errors in test suite. I am just faced it in network, so I create non trivial commit[1] that enables it there. It includes also how to avoid failures on mocked class[2] which avoided build dependencies. From list of errors it can check is typos[3], mocking of wrong class[4] and mocking non-existing methods[5]. So feel free to take it as inspiration and enable it also in your test helper. Josef [1] https://github.com/yast/yast-network/pull/830/commits/e18da64fce25242a51710… [2] https://github.com/yast/yast-network/pull/830/commits/e18da64fce25242a51710… [3] https://github.com/yast/yast-network/pull/830/commits/e18da64fce25242a51710… [4] https://github.com/yast/yast-network/pull/830/commits/e18da64fce25242a51710… [5] https://github.com/yast/yast-network/pull/830/commits/e18da64fce25242a51710… -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

4 months, 2 weeks

[yast-devel] Innovation Time: Feedback from forums

by josef Reidinger

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

5 months

[yast-devel] Automatic AutoYaST Schema Validation

by Imobach González Sosa

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 months, 2 weeks

[yast-devel] YaST in Hacktoberfest?

by Srinidhi B

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��Ǩ�

6 months, 2 weeks

[yast-devel] Highlights of development sprint 109

by Ancor Gonzalez Sosa

The YaST Team continues focusing on improving both AutoYaST and the management of storage devices. Let's take a quick glance at some of the results. - New YaST test client to check AutoYaST dynamic profiles. - Improved detection of which YaST package is needed to process each section of the profile, relying on RPM’s supplement information. - First steps to annotate the documentation of AutoYaST with better information about the corresponding version for each feature. - Final design of the new Partitioner user interface. - Improved automatic submission of translations to Leap and SLE. Check the whole report at https://yast.opensuse.org/blog/2020-09-29/sprint-109 Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

6 months, 3 weeks

[yast-devel] 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-autoinstallation: - [PoC] Run the unit tests in parallel (33 days) https://github.com/yast/yast-autoinstallation/pull/670 - Find the Base Product (146 days) https://github.com/yast/yast-autoinstallation/pull/599 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (438 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-devtools: - Y2logs analyzer (215 days) https://github.com/yast/yast-devtools/pull/149 - Supplement changes from YCC (243 days) https://github.com/yast/yast-devtools/pull/148 - Move desktop files (476 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (180 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-pkg-bindings: - WIP: Master jira sle 15184 (10 days) https://github.com/yast/yast-pkg-bindings/pull/138 Pending requests in repository yast-update: - WIP: Master jira sle 15184 (10 days) https://github.com/yast/yast-update/pull/156 Pending requests in repository yast-vm: - bsc#1169214 - When NetworkManager is being used bridge creation will not work so show warning popup (40 days) https://github.com/yast/yast-vm/pull/47 Pending requests in repository yast-yast2: - [WIP] Drop SuSEfirewall2 completely (739 days) https://github.com/yast/yast-yast2/pull/806 Pending requests in repository yast-ycp-ui-bindings: - [WIP] Support bold font inside tables (766 days) https://github.com/yast/yast-ycp-ui-bindings/pull/35 Pending requests in repository yast-ruby-bindings: - [WIP] Don't crash on NoMethodError when Perl is involved (269 days) https://github.com/yast/yast-ruby-bindings/pull/224 Pending requests in repository yast-rake: - Switch desktop directory (476 days) https://github.com/yast/yast-rake/pull/70 Pending requests in repository yast-cio: - convert to libyui ruby bindings (191 days) https://github.com/yast/yast-cio/pull/34 Pending requests in repository skelcd-control-openSUSE: - Adjust the roles to the new YaST Patterns (272 days) https://github.com/yast/skelcd-control-openSUSE/pull/195 Pending requests in repository yast-auth-server: - Fixes to make the YaST modules work (459 days) https://github.com/yast/yast-auth-server/pull/48 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (170 days) https://github.com/yast/yast-journal/pull/45 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

6 months, 3 weeks

[yast-devel] Hint: Easy adapting changes from forks

by josef Reidinger

Hi, as I now work on merging various pull requests, it often lives in own forks, where I do not have permissions and I am looking for the easiest way to make them again mergeable and sometimes adapt it to our needs. what works best for me is e.g. for this pr: https://github.com/yast/yast-ruby-bindings/pull/239 ```shell git checkout master && git pull && git checkout -b my_branch wget https://github.com/yast/yast-ruby-bindings/pull/239.patch # notice .patch suffix git am -3 239.patch # and then solve conflicts and branch is ready for new pr ``` Do you know easier way? This way it is for me like good old kernel mailing lists where you get set of patches that you can apply. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

6 months, 3 weeks

[yast-devel] Nicer logging lines for ruby code

by josef Reidinger

Hi, after our final drop of old testsuite nothing prevent to merge [1]. So now we will have in y2log also method names, so I hope easier grepping. Example how it changed: - 2018-05-28 13:10:29 <1> linux-vvcf.privatesite(12728) [Ruby] y2storage/dump_manager.rb:230 Devicegraph dump directory: /var/log/YaST2/storage - 2018-05-28 13:10:29 <1> linux-vvcf.privatesite(12728) [Ruby] y2storage/dump_manager.rb:264 Dumping Devicegraph to 01-probed + 2018-05-28 13:25:35 <1> linux-vvcf.privatesite(20263) [Ruby] y2storage/dump_manager.rb(lazy_init):230 Devicegraph dump directory: /var/log/YaST2/storage + 2018-05-28 13:25:35 <1> linux-vvcf.privatesite(20263) [Ruby] y2storage/dump_manager.rb(dump_internal):264 Dumping Devicegraph to 01-probed Of course we are not necessary limited to that change and we can change more as we need, so I welcome any feedback. One idea I have is to replace that "Ruby" component by real components e.g. by matching component and gettext domain. so in this case it can be "storage". Josef [1] https://github.com/yast/yast-ruby-bindings/pull/216 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

6 months, 3 weeks

[yast-devel] Smaller disk footprint [Bug 1176767]

by Martin Vidner

https://bugzilla.suse.com/show_bug.cgi?id=1176767 Recently I was looking at https://cockpit-project.org/ and how it relates to YaST. One of the factors was the disk footprint: Cockpit takes up less than 10 MB. YaST takes up 258 MiB on disk. (counting just the base, not the actual config modules) Starting with a 2020-09-01 openSUSE Tumbleweed that already has Cockpit installed, these are the byte sizes of packages installed by "zypper install yast2" 218922718 glibc-locale 16627072 ruby2.7 9940016 ruby2.7-rubygem-nokogiri 3427518 hwinfo 3413184 libruby2_7-2_7 3310778 yast2-core 2589200 yast2 2279763 ruby2.7-rubygem-unf_ext 1378488 yast2-pkg-bindings 1179325 libyui-ncurses13 1095423 ruby2.7-rubygem-simpleidn 949088 libyui13 788911 libjemalloc2 721238 yast2-hardware-detection 686097 augeas-lenses 646032 yast2-ycp-ui-bindings 463280 yast2-ruby-bindings 360824 libxslt1 316728 yast2-perl-bindings 226562 augeas 167706 libx86emu3 129288 libyaml-0-2 129144 ruby2.7-rubygem-unf 115505 ruby2.7-rubygem-ruby-augeas 108310 ruby2.7-rubygem-fast_gettext 63522 ruby2.7-rubygem-cfa 62415 ruby2.7-rubygem-gem2rpm 51387 ruby2.7-rubygem-cheetah 47974 fdupes 38714 ruby-common 34725 perl-gettext 10762 ruby2.7-rubygem-abstract_method 3389 yast2-logs 84 ruby Now, glibc-locale is required by libyui-ncurses (based on bug 849255) but since 2 years ago a smaller subpackage exists, glibc-locale-base, which can be used as long as YaST runs in English only. Looking into another big dependency, ruby2.7-rubygem-nokogiri.rpm has 9.5 MiB out of which 8.8 MiB is /usr/lib64/ruby/gems/2.7.0/cache/nokogiri-1.10.10.gem, just a useless repackaging of the source gem. -- Martin Vidner, YaST Team http://en.opensuse.org/User:Mvidner

6 months, 4 weeks

[yast-devel] A menu for the YaST Partitioner

by Ancor Gonzalez Sosa

Some time ago, we decided to make several changes in the Partitioner UI. Check this section (or the full document if you are interested enough) for more details: https://github.com/yast/yast-storage-ng/blob/master/doc/partitioner_ui.md#a… We are currently working on adding a new menu bar, but we have two decisions to take. We would like to have some feedback from everyone in the YaST Team and also from SUSE UX experts, so I'm sending this to both Ken and the yast-devel list. For those that are not that familiar with the current UI of the Partitioner, I added some kind of appendix at the end of this mail to refresh minds. First question: what approach should we follow for the menu bar? After some discussions, we have three proposals. I created three branches in the yast-storage-ng repository so you can play with them. For the less technical users (downloading the repo and running the demo may not be trivial), I'm open to create videos or have a video-call to show them in action. Menu proposal 1 https://github.com/ancorgs/yast-storage-ng/blob/menu_minimal/README.md Menu proposal 2 https://github.com/ancorgs/yast-storage-ng/blob/menu_classic/README.md Menu proposal 3 https://github.com/ancorgs/yast-storage-ng/blob/menu_explicit/README.md We have to decide on the general approach, not on every detail. Some entries could be relocated or renamed afterwards. If we decide to take proposal 1, then we are done. No second question. If we take 2 or 3, which both include options that are "contextual" to the device currently selected, we have another thing to decide... Second question: what to do with the menu-buttons below the tables? (check the appendix below if you don't know what are we talking about) Option 1. Remove them as all the functionality is already in the menus. Option 2. Keep them as they are. Option 3. Use simple buttons with only a small set of actions. If we choose option 3. Selecting a disk would only show "Edit" and "View Partitions". But not the options to create/clone partition tables (the menu bar should be used for that). Selecting a partition would show "Edit" and "Delete", but not resizing or moving. And so on. What's your view on the topic? Cheers. And now, the appendix about the current UI, only in case you need it: We offer many actions per each device (editing, resizing, deleting, etc.). For that we have menu-buttons right below all the Partitioner tables (there are too many actions, they don't fit as regular buttons). Not all the actions make sense for all kind of devices (for example, you cannot delete a hard disk or format an LVM volume group). So every time a new device is selected in the table, those menu-buttons change to only offer the actions that make sense for that type of device. In the System table that contains all the devices, there are also additional buttons for general actions like "Rescan Devices" or "Configure". They have never belonged there. In the tables of a particular technology (like RAID or Volume Management) there are buttons to add new devices of the corresponding type. Cheers again. -- 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

6 months, 4 weeks

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

YaST Development September 2020