YaST Development August 2020

yast-devel@lists.opensuse.org

12 participants
14 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] Y2Packager::Resolvable - search by RPM dependencies

by Ladislav Slezak

Hi all, I have improved the Y2Packager::Resolvable call (and the internally used Pkg.Resolvables call) to allow searching by RPM dependencies (provides, obsoletes, conflicts, requires, recommends, suggests, supplements, enhances). Examples: Just use the dependency name as the additional parameter: Y2Packager::Resolvable.find(kind: :package, provides: "application()") This searches for the exact string. Optionally you can use a regular expression, just add the "_regexp" suffix to the dependency name: Y2Packager::Resolvable.find(kind: :package, obsoletes_regexp: "^yast2-config-") The regular expression is a POSIX extended regular expression, not a Ruby regular expression! The regexp parameter is just passed to the underlying libzypp/libsolv. The filtering happens directly on the C++ level so it's much faster than filtering on the Ruby level. Do not forget to escape regexp metacharacters like []() # seach for autoyast() supplements Y2Packager::Resolvable.find(kind: :package, supplements_regexp: "^autoyast\\(.*\\)") If an invalid regexp is passed then the ArgumentError exception is raised. You can combine more dependencies like "provides" and "obsoletes" in one call (if that makes sense). The result is logical AND, all dependencies must match. To use this new feature you need yast2-pkg-bindings-4.3.0 and yast2-4.3.21 (or newer). The old Pkg.PkgQueryProvides() call has been marked as obsolete. The enhanced Pkg.Resolvables() call is more powerful as it covers also the other dependencies than "Provides" and allows using a regexp. Enjoy! :) -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

7 months, 2 weeks

[yast-devel] Special views in the Partitioner

by Ancor Gonzalez Sosa

As you all know, we recently got to the conclusion of adding a menu bar to the YaST Partitioner and getting rid of several entries we have in the left-hand tree. Check https://github.com/yast/yast-storage-ng/blob/master/doc/partitioner_ui.md#a… We are in the process of implementing that, but we are not sure how to represent the screens that are now a misplaced entry in the tree: Device Graphs, Installation Summary and Settings. Option 1: as pop-ups (even if they are full-screen pop-ups) In this option, "Settings" will be likely accessible through the "System" menu (which we are considering to rename to "Partitioner") and the other two would live in a "View" menu. See screenshot at https://github.com/yast/yast-storage-ng/pull/1120 We would consider that the normal view is the one with the devices tree at the left, the tables of devices at the right and the menu at the top. The other three views (settings, graph and summary) would be rendered on top of the normal one (if we use classic pop-ups) or hiding it (if we use the current approach of full-screen pop-ups). The menu bar would not be accessible from such views and the user would need to close the (maybe full-screen) pop-up using an "Ok" button to get back to the normal view. In the current Partitioner, double-clicking in a node of the Device Graph takes you to the entry of such device in the tree. I guess it would keep doing the same, so it would be an alternative way of closing the pop-up. Option 2: as four first-class citizen views In this option, there would be a "View" menu with four entries: Devices, Device Graph, Installation Summary and Settings. The "Devices" view would be equivalent to the normal one in the previous option. All the others would use the full screen (no left tree) and will still provide access to the menu bar. They would need no specific button to be closed. Instead, the user would use "View -> Devices" (or any other view, since all of them are equally important in this interface). The main advantage of this option is that we wouldn't need to change how the current Device Graphs, Summary or Settings screens work. For example, no need to add a button to save the new settings and close or another to quit the settings dialog without applying. Which option do you think would be better? 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

7 months, 2 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-apparmor: - Port to rake (443 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-autoinstallation: - Find the Base Product (118 days) https://github.com/yast/yast-autoinstallation/pull/599 Pending requests in repository yast-bootloader: - Add UPDATE_NVRAM in /etc/sysconfig/bootloader (bsc#1157550). (48 days) https://github.com/yast/yast-bootloader/pull/611 - Fix resume with uuid partition (410 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-core: - Fixes for gensalt handling with libxcrypt. (185 days) https://github.com/yast/yast-core/pull/144 Pending requests in repository yast-devtools: - Y2logs analyzer (187 days) https://github.com/yast/yast-devtools/pull/149 - Supplement changes from YCC (215 days) https://github.com/yast/yast-devtools/pull/148 - Move desktop files (448 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 (20 days) https://github.com/yast/yast-installation/pull/878 - clarify that ssh_import processes host keys (bsc#1172400) (87 days) https://github.com/yast/yast-installation/pull/860 - Demo: eager mode of zombie-killer 0.5 (661 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - network-ng: test cases document (draft) (283 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (409 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (152 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-registration: - [SP3] Fix misleading default_skipping_text (BSC#1167795) (65 days) https://github.com/yast/yast-registration/pull/488 Pending requests in repository yast-vm: - bsc#1169214 - When NetworkManager is being used bridge creation will not work so show warning popup (12 days) https://github.com/yast/yast-vm/pull/47 Pending requests in repository yast-yast2: - Bnc#1081441 (137 days) https://github.com/yast/yast-yast2/pull/1047 - [WIP] CWM improvements (138 days) https://github.com/yast/yast-yast2/pull/1044 - Change the way groups are defined (447 days) https://github.com/yast/yast-yast2/pull/936 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (578 days) https://github.com/yast/yast-yast2/pull/894 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (578 days) https://github.com/yast/yast-yast2/pull/893 - [WIP] Firewalld fixes for the new UI (726 days) https://github.com/yast/yast-yast2/pull/813 - [WIP] Drop SuSEfirewall2 completely (711 days) https://github.com/yast/yast-yast2/pull/806 Pending requests in repository yast-ycp-ui-bindings: - [WIP] Support bold font inside tables (738 days) https://github.com/yast/yast-ycp-ui-bindings/pull/35 Pending requests in repository yast-ruby-bindings: - Fixes for gensalt handling with libxcrypt. (185 days) https://github.com/yast/yast-ruby-bindings/pull/239 - [WIP] Don't crash on NoMethodError when Perl is involved (241 days) https://github.com/yast/yast-ruby-bindings/pull/224 - log method name (825 days) https://github.com/yast/yast-ruby-bindings/pull/216 Pending requests in repository yast-rake: - Switch desktop directory (448 days) https://github.com/yast/yast-rake/pull/70 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

7 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-apparmor: - Port to rake (436 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-autoinstallation: - Find the Base Product (111 days) https://github.com/yast/yast-autoinstallation/pull/599 Pending requests in repository yast-bootloader: - Add UPDATE_NVRAM in /etc/sysconfig/bootloader (bsc#1157550). (41 days) https://github.com/yast/yast-bootloader/pull/611 - Fix resume with uuid partition (403 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-core: - Fixes for gensalt handling with libxcrypt. (178 days) https://github.com/yast/yast-core/pull/144 Pending requests in repository yast-devtools: - Y2logs analyzer (180 days) https://github.com/yast/yast-devtools/pull/149 - Supplement changes from YCC (208 days) https://github.com/yast/yast-devtools/pull/148 - Move desktop files (441 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 (13 days) https://github.com/yast/yast-installation/pull/878 - clarify that ssh_import processes host keys (bsc#1172400) (80 days) https://github.com/yast/yast-installation/pull/860 - Demo: eager mode of zombie-killer 0.5 (654 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - network-ng: test cases document (draft) (276 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (402 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (145 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-registration: - [SP3] Fix misleading default_skipping_text (BSC#1167795) (58 days) https://github.com/yast/yast-registration/pull/488 Pending requests in repository yast-yast2: - Bnc#1081441 (130 days) https://github.com/yast/yast-yast2/pull/1047 - [WIP] CWM improvements (131 days) https://github.com/yast/yast-yast2/pull/1044 - Change the way groups are defined (440 days) https://github.com/yast/yast-yast2/pull/936 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (571 days) https://github.com/yast/yast-yast2/pull/894 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (571 days) https://github.com/yast/yast-yast2/pull/893 - [WIP] Firewalld fixes for the new UI (719 days) https://github.com/yast/yast-yast2/pull/813 - [WIP] Drop SuSEfirewall2 completely (704 days) https://github.com/yast/yast-yast2/pull/806 Pending requests in repository yast-ycp-ui-bindings: - [WIP] Support bold font inside tables (731 days) https://github.com/yast/yast-ycp-ui-bindings/pull/35 Pending requests in repository yast-ruby-bindings: - Fixes for gensalt handling with libxcrypt. (178 days) https://github.com/yast/yast-ruby-bindings/pull/239 - [WIP] Don't crash on NoMethodError when Perl is involved (234 days) https://github.com/yast/yast-ruby-bindings/pull/224 - log method name (818 days) https://github.com/yast/yast-ruby-bindings/pull/216 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

7 months, 4 weeks

[yast-devel] Innovation Time: installation of new server

by josef Reidinger

Hi, as my today innovation time I spend couple of hours with installing our new server in NUE. For access please see https://wiki.suse.net/index.php/YaST/team-it-infrastructure#Our_Servers ( internal only! ). Few my notes I observe during it: 1. it uses BMC to initial access to machine. Java applet version with openJDK was disaster, HTML5 version works surprising well. 2. PXE in NUE works quite fine, it just needs tuning of kernel parameter. 3. installation without ssh was not possible. I am not sure what UI is picked, but it does not show anything in console. So I do ssh installation. 4. suggested ssh -X was quite slow. Probably ssh -XYC will be faster, but I do not try it. 5. System is SLE 15 SP2 and I picked system role KVM virtualization host and configuration looks reasonable. 6. partitioning needs tunning. It wants to use just one of SSD, but guided setup with using both disk and LVM create good proposal ( reasonable system and maximum /var/lib/libvirt for images ) 7. I keep rest of defaults as it looks reasonable. So what now? Current there are only my ssh keys, but I already ask infra team to add machine to their salt slaves and apply ssh for yast team members same as we have in prague server. connection via libvirt works well for me. No VM is there yet, but maybe we can migrate our german IBS workers. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

8 months

[yast-devel] Virtual Ruby Conference Tomorrow

by josef Reidinger

Hi, if you are interested tomorrow is free ruby virtual conference. See https://noruko.org/ Some talks can be interesting, maybe mvidner find Sorbet presentation interesting. Matz will talk about ruby 3.0 and more. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

8 months

[yast-devel] Highlights of development sprint 106

by Ancor Gonzalez Sosa

Although the YaST team is focusing on bugfixing in this summer season, we still have three interesting features to share with our fellow chameleons: - New menu bar widget in libYUI. Check the screenshots in the blog post. - Configuration of the firewall in AutoYaST moved to the first stage. - Preliminary support to mark the packages affected by BootHole and show a warning message if such old packages are going to be installed. Check the extended versions with links at https://yast.opensuse.org/blog/2020-08-17/sprint-106 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

8 months

[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-apparmor: - Port to rake (429 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-autoinstallation: - Find the Base Product (104 days) https://github.com/yast/yast-autoinstallation/pull/599 Pending requests in repository yast-bootloader: - Add UPDATE_NVRAM in /etc/sysconfig/bootloader (bsc#1157550). (34 days) https://github.com/yast/yast-bootloader/pull/611 - Fix resume with uuid partition (396 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-core: - Fixes for gensalt handling with libxcrypt. (171 days) https://github.com/yast/yast-core/pull/144 Pending requests in repository yast-devtools: - Y2logs analyzer (173 days) https://github.com/yast/yast-devtools/pull/149 - Supplement changes from YCC (201 days) https://github.com/yast/yast-devtools/pull/148 - Move desktop files (434 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 (6 days) https://github.com/yast/yast-installation/pull/878 - clarify that ssh_import processes host keys (bsc#1172400) (73 days) https://github.com/yast/yast-installation/pull/860 - Demo: eager mode of zombie-killer 0.5 (647 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - network-ng: test cases document (draft) (269 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (395 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (138 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-registration: - [SP3] Fix misleading default_skipping_text (BSC#1167795) (51 days) https://github.com/yast/yast-registration/pull/488 Pending requests in repository yast-yast2: - Bnc#1081441 (123 days) https://github.com/yast/yast-yast2/pull/1047 - [WIP] CWM improvements (124 days) https://github.com/yast/yast-yast2/pull/1044 - Change the way groups are defined (433 days) https://github.com/yast/yast-yast2/pull/936 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (564 days) https://github.com/yast/yast-yast2/pull/894 - save_y2logs: save kernel messages and udev log (bsc#1089647, bsc#1085… (564 days) https://github.com/yast/yast-yast2/pull/893 - [WIP] Firewalld fixes for the new UI (712 days) https://github.com/yast/yast-yast2/pull/813 - [WIP] Drop SuSEfirewall2 completely (697 days) https://github.com/yast/yast-yast2/pull/806 Pending requests in repository yast-ycp-ui-bindings: - [WIP] Support bold font inside tables (724 days) https://github.com/yast/yast-ycp-ui-bindings/pull/35 Pending requests in repository yast-ruby-bindings: - Fixes for gensalt handling with libxcrypt. (171 days) https://github.com/yast/yast-ruby-bindings/pull/239 - [WIP] Don't crash on NoMethodError when Perl is involved (227 days) https://github.com/yast/yast-ruby-bindings/pull/224 - log method name (811 days) https://github.com/yast/yast-ruby-bindings/pull/216 Pending requests in repository yast-rake: - Switch desktop directory (434 days) https://github.com/yast/yast-rake/pull/70 Pending requests in repository yast-cio: - convert to libyui ruby bindings (149 days) https://github.com/yast/yast-cio/pull/34 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

8 months

[yast-devel] First meeting to discuss the long term vision for our UI framework

by Ancor Gonzalez Sosa

The YaST team wants to take some time to think in the long term and try to envision the future of our UI design/programming... which may be anything from just an improved libYUI to something completely different and unrelated. It likely makes sense to start discussing what are the requisites (and/or use cases) for the UI of YaST in the long term, so we have planned a meeting with all the interested people in this topic tomorrow Thursday at 2pm CEST. Usual meeting point: https://li2023-182.members.linode.com/#/rooms/2001 As said, the topic will be: requirements for the future UI of YaST. Some food for thought about the topic: - Do we ALWAYS need to offer TUI+GUI for all modules and steps? - Does it have any value to offer something else beyond TUI/GUI? - What are the requisites regarding support for programming languages? Those are not the only points to discuss, just some hints to get your brain started. 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

8 months, 1 week

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

YaST Development August 2020