February 2017 - YaST Development - openSUSE Mailing Lists

[yast-devel] Overcommit - automatic checks via Git hooks
by Ladislav Slezak 21 Dec '22

21 Dec '22

Hi, I found a quite interesting tool called Overcommit [1]. It provides an easy way for setting up Git commit hooks and provides some basic checking plugins. The nice feature of the Git commit hooks is that you can run some checks automatically and early in the development. For example with the commit hooks you can run Rubocop check automatically whenever a commit is created. And if the check fails the commit is not created. I can see "make Rubocop happy" commits quite often (happens to me as well), with Overcommit you can easily avoid that. I have tried several Overcommit checks: - Rubocop - runs Rubocop at "commit" - Rspec - runs the tests before "push" - Branch blacklist - can forbid direct commits to configured branches, e.g. "master" (forces using pull requests, avoids commits to master my mistake) - Commit message spellcheck - warns when there is a possible typo Check my blog post [2] for the details, esp. watch the recorded screencast where I wanted to show some mistakes which it can catch. The tool looks promising, I'll try using it for some time. If you want to try it as well check the blog post for the installation steps. Enjoy! [1] https://github.com/brigade/overcommit [2] http://blog.ladslezak.cz/2016/06/06/overcommit/ -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak(a)suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 3

[yast-devel] YaST Tips&Tricks
by Ladislav Slezak 25 Jan '22

25 Jan '22

Hi all, some time ago we discussed where and how we should share "Tips&Tricks" for YaST users and developers. IIRC there was no clear conclusion so I decided to start a wiki [1] to collect all our tricks we know or use. For now it's just a place for dumping your ideas, links, short howtos, etc... When we collect enough data we can probably split it to several categories or move it somewhere else. We just need the data first. I have added there some my tricks from my personal "knowledgebase" file. If you have better tricks or find something wrong simply change it, it's a wiki ;-) Ladislav [1] https://github.com/yast/yast.github.io/wiki/YaST-Tips-and-Tricks -- 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

2 1

[yast-devel] HOWTO: Screencast recording
by Ladislav Slezak 22 Jul '17

22 Jul '17

Hi all, Yesterday I published a short blog post about recording a screencast (a desktop session) to create a video or an animated image. So if you want to have nice animated images in READMES [1] or in pull requests [2] then check this post [3]. Enjoy! [1] https://github.com/lslezak/build-rake/blob/master/README.md [2] https://github.com/yast/yast-registration/pull/240 [3] http://lslezak.blogspot.cz/2016/01/recording-screencast-in-linux.html -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak(a)suse.com SUSE -- 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-related talks/workshops in oSC'17
by Ancor Gonzalez Sosa 31 Mar '17

31 Mar '17

Just for you information, I have submitted the following two abstracts for openSUSE Conference 2017. I'm sharing them here just to keep track of the YaST-related content we will deliver. Feel free to help with "my" talk/workshop (definitely the workshop would benefit from having different speakers for each technology) or share here the ones you have submitted. FORMAT: 15 min talk TITLE: YaST: from the repository to the distributions SUBTITLE: Continuous testing and delivery, the YaST way ABSTRACT: In this talk we will briefly explore all the mechanisms and workflows used by the YaST developers in order to share as much code as possible between all the SUSE and openSUSE distributions, while ensuring the quality of all the different YaST modules. Learn how Rake, unit tests, Github, Jenkins, Travis, OBS and even Docker are used to deliver the developer's work to the already released products (via maintenance updates), to the ones still to be released and to our rolling distribution Tumbleweed. FORMAT: 3 hours workshop TITLE: Develop a YaST module in the 21st century way SUBTITLE: Enjoyable object-oriented YaST development ABSTRACT: YaST, the openSUSE beloved Swiss army knife, has been around since 1996. The history of quite some components still present in the current version can be tracked back to 1999. In 2013 the code was automatically converted from YCP, a purpose-specific procedural programming language, to Ruby, a general-purpose object oriented one. Since then, the YaST team has been trying to steady replace many YCP components and paradigms with new object-oriented, test-driven ones. In this workshop we will develop a new YaST module from scratch using the new Ruby-based approach. That is, object oriented dialogs and clients, CFA to modify the configuration files, Cheetah to execute system commands, RSpec tests and so on. Attendees are expected to be proficient with object oriented programming (preferably Ruby) and to have an recent openSUSE system (can be a virtual machine) to follow the workshop. Having read the YaST development tutorial in advance would definitely be a plus. That's all folks. 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

4 3

[yast-devel] Feedback needed! Hack Week project to re-define storage-ng API
by Ancor Gonzalez Sosa 07 Mar '17

07 Mar '17

My Hack Week project is in that state in which all the important parts work and now it's time to decide if it's worth investing a couple of extra days to finish it all the way down. Since the ultimate goal is to change how YaST interacts with storage-ng, I would need the opinion of as many YaST developers as possible. So please, please, please, take a look to this and give your opinion. https://github.com/yast/yast-storage-ng/pull/169 The most important question is - do you prefer the proposed approach and API* or do you prefer to continue accessing directly to libstorage-ng from YaST? Thanks * In general, minor details in the API can be ironed out in the short future. -- 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 21

[yast-devel] YaST(team)-related Hack Week project
by Ancor Gonzalez Sosa 02 Mar '17

02 Mar '17

I'm aware of several YaST-related projects during this Hack Week 15. So I though it would be good to collect them all in a thread with a sentence about the outcome/status, just to ensure they are not forgotten. We could also use the thread to mention the non-YaST projects worked by members of the YaST team, just for fun. I will start with the stuff I worked on YaST ==== Title: yast2-storage-ng as a libstorage-ng wrapper. POC URL: https://hackweek.suse.com/projects/yast2-storage-ng-as-a-libstorage-ng-wrap… Status: Some working code and a clear ideas on how to finish it. 7 out of the 8 YaST developers who expressed their opinion like the new layer and think it's the way to go, so we should probably continue working on it. More details in the project comments. Title: storage-ng improvements URL: https://hackweek.suse.com/15/projects/yast-storage-ng-improvements Status: I leave this section to Iván. Non YaST (just for fun) ======================= Title: Add information about listeners to Jangouts UI URL: https://hackweek.suse.com/15/projects/add-information-about-listeners-to-ja… Status: Needs adaptations in Janus, so I gave up for the time being. Title: Improving Jangouts UX URL: https://hackweek.suse.com/15/projects/improving-jangouts-ux Status: Cynthia is guiding us through a quite interesting process that will continue. Outcome of the first step in the project comments. Title: Finish my family openSUSE adoption URL: https://hackweek.suse.com/15/projects/finish-my-family-opensuse-adoption Status: Was much harder than expected due to an evil HP BIOS. See project comment. -- 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

5 4

[yast-devel] New yast2 maintainers
by Josef Reidinger 01 Mar '17

01 Mar '17

Hi, I am more then happy to promote Knut with Martin as backup as our next yast2 maintainers sorter for next month. Currently after hackweek our queue is a bit bigger, but I try to somehow lower it today. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 1

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 28 Feb '17

28 Feb '17

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-add-on: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (20 days) https://github.com/yast/yast-add-on/pull/37 - Handling in URLs (304 days) https://github.com/yast/yast-add-on/pull/28 Pending requests in repository yast-autoinstallation: - Added documentation explanining different network scenarios (7 days) https://github.com/yast/yast-autoinstallation/pull/289 Pending requests in repository yast-bootloader: - [blog] Improve ui serial console (68 days) https://github.com/yast/yast-bootloader/pull/393 Pending requests in repository yast-control-center-gnome: - remove useless changlog, (69 days) https://github.com/yast/yast-control-center-gnome/pull/26 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (217 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-installation: - Merge of SLE-12-SP2-CASP into master (10 days) https://github.com/yast/yast-installation/pull/525 Pending requests in repository yast-network: - Add a Codacy badge to README.md (26 days) https://github.com/yast/yast-network/pull/499 - Forbid the addition of wlan interfaces to bridge proposal (bsc#956755) (53 days) https://github.com/yast/yast-network/pull/483 - Improved adding routes (111 days) https://github.com/yast/yast-network/pull/458 Pending requests in repository yast-packager: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (19 days) https://github.com/yast/yast-packager/pull/230 - Added yast2-sw_single-wrapper to handle rpms in Plasma (139 days) https://github.com/yast/yast-packager/pull/195 - Added yast2-sw_single-wrapper to handle rpms in KDE (146 days) https://github.com/yast/yast-packager/pull/190 - Allow KDE to use packager for opening rpms (189 days) https://github.com/yast/yast-packager/pull/174 - Prioritize yast-packager for opening rpms (153 days) https://github.com/yast/yast-packager/pull/173 Pending requests in repository yast-pkg-bindings: - [WIP] Return valid repository signature flag (bsc#1009127) (11 days) https://github.com/yast/yast-pkg-bindings/pull/65 - Fixed failure when trying to save a plugin service (bsc#1021117) (28 days) https://github.com/yast/yast-pkg-bindings/pull/64 - [WIP] Build ruby-lint definitions (243 days) https://github.com/yast/yast-pkg-bindings/pull/60 Pending requests in repository yast-rdp: - bnc#988353 RDP dialog displays error during installation (186 days) https://github.com/yast/yast-rdp/pull/4 Pending requests in repository yast-security: - refactoring autoconverted ruby code into ruby code (145 days) https://github.com/yast/yast-security/pull/40 Pending requests in repository yast-snapper: - [WIP] Added snapshot Class with strategy pattern. (271 days) https://github.com/yast/yast-snapper/pull/40 Pending requests in repository yast-sound: - [WIP] (L3) SP4 soundcard DB update (24 days) https://github.com/yast/yast-sound/pull/19 Pending requests in repository yast-storage: - Add option to disable swap creation (117 days) https://github.com/yast/yast-storage/pull/182 - Propose /boot for encrypted root on PowerPC (117 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-theme: - Add yast2-branding-openSUSE-Oxygen (23 days) https://github.com/yast/yast-theme/pull/74 Pending requests in repository yast-vm: - Bsc#978225 (25 days) https://github.com/yast/yast-vm/pull/16 Pending requests in repository yast-yast2: - [WIP] Support for unsigned repositories (bsc#1009127) (19 days) https://github.com/yast/yast-yast2/pull/537 - Disable buttons cwm (41 days) https://github.com/yast/yast-yast2/pull/531 - Do a full type detection when creating cache (52 days) https://github.com/yast/yast-yast2/pull/527 - Add to fstab parser only optional ending line otherwise it can cause (96 days) https://github.com/yast/yast-yast2/pull/509 - [WIP] Build ruby-lint definitions (242 days) https://github.com/yast/yast-yast2/pull/480 Pending requests in repository yast-ruby-bindings: - [WIP] Build ruby-lint definitions (242 days) https://github.com/yast/yast-ruby-bindings/pull/170 Pending requests in repository yast-crowbar: - Cloud5 (315 days) https://github.com/yast/yast-crowbar/pull/47 Pending requests in repository yast-samba-client: - add checkbox for the net ads join --no-dns-updates switch (192 days) https://github.com/yast/yast-samba-client/pull/48 - update idmap config syntax (194 days) https://github.com/yast/yast-samba-client/pull/47 Pending requests in repository yast-rake: - Initial tab completetion implementation (87 days) https://github.com/yast/yast-rake/pull/32 - Added version:wbump task (257 days) https://github.com/yast/yast-rake/pull/31 Pending requests in repository yast-auth-server: - bnc#965311 - yast ldap-server-ssl-check does not handle ldaps only ldap+starttls works (335 days) https://github.com/yast/yast-auth-server/pull/25 - Drop ca mgm (404 days) https://github.com/yast/yast-auth-server/pull/21 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] 2nd attempt: do we need a layer between libstorage-ng and (the rest) of YaST?
by Ancor Gonzalez Sosa 27 Feb '17

27 Feb '17

Since the original thread is already ruined with discussions about concrete API design details that were not the main topic of my question, I will try once again from scratch. Do we need a layer between libstorage-ng and (the rest) of YaST? I think so. Why do I? TLDR; libstorage-ng is multilanguage (with a Ruby-agnostic API, to say the least) and YaST-agnostic. Therefore, we need a layer to close the distance between libstorage-ng and Ruby/YaST. The alternative is to have boilerplate code all along YaST (like downcast) and our own customization for the Ruby tools. If you agree, please say so. If you disagree, please provide counterarguments. Now the long version of my reasoning (and you know that "long" means in my case). ;-) A) Libstorage-ng API is designed to be useful for many languages and for many potential users, not only Ruby and YaST. B) Libstorage-ng is designed to be relatively low-level, not hiding details about how the different moving pieces (devices, filesystems, etc.) are connected and allowing to model all the possibilities that can happen in reality. That's perfectly fine. It makes libstorage-ng more versatile and powerful. But it has some implications. A consequence for (A): when taking API design decisions, if there are several ways of doing something and no way is universally better than the others[*], libstorage-ng always work in the way that is not standard in Ruby. That means libstorage-ng does not play nicely with the Ruby ecosystem, causing extra work for the Ruby developers just to keep using the tools chosen for YaST development and testing. For (B) it means libstorage-ng does not offer a direct answer to the kind of questions usually asked all around YaST (yast-packager, yast-bootloader, yast-country....). Although examples-based discussion has proved to lead to off-topic, I will try once again: A typical question from YaST to the storage layer: - For this given filesystem, which are the physical disks (whatever technology is used)? That question would be plain wrong from the libstorage-ng POV, because there is no such a direct relationship (not always) and therefore the user of the library is expected to know all the possible paths from a a filesystem to its disks and traverse all those paths doing the corresponding checks for empty and performing the downcasts in every step. In other words, there is no a_filesystem.all_disks But the user is expected to do this blk_dev = a_filesystem.blk_devices[0] if Storage.encryption?(blk_device) blk_device = Storage.to_encryption(blk_device).blk_device end return [Storage.to_disk(blk_dev)] if Storage.disk?(blk_dev) if Storage.partition?(blk_device) partition = Storage.to_partition(blk_device) if Storage.disk?(partition.partition_table.partitionable) return [Storage.to_disk(partition.partition_table.partitionable)] else # MD case end elsif Storage.lvm_lv?(blk_device) # The LVM case, which is double the size than the partition one end This is a simplified example don't taking into account he possibilities of multi-device filesystems or encryptions in other layers than the very first one (right below the filesystem). While adapting other modules to use the new libstorage directly we have found many examples of that gap between the abstraction level expected by YaST and the level of "clarity" about the internal structure enforced by libstorage-ng. So please refrain from discussing every single variable name in the example or providing an alternative with 4 fewer lines. That will not change the main point. :) So, as said at the beginning, libstorage-ng is perfect as it is, for the goal it is designed. That goal is not to be Ruby-compliant or to match the YaST use-case 100%. So we need an extra layer to walk that way. IMHO, opposing to the creation of that layer just to avoid the fact that some developers has to know and work with both layers is not reasonable. If you disagree, please provide counter-arguments to the provided arguments, instead of discussing the wording of the examples. ;-) Cheers. [*] As proved by the endless discussions focused on examples and counter-examples in which nobody convinces nobody else. -- 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 8

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 27 Feb '17

27 Feb '17

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-add-on: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (19 days) https://github.com/yast/yast-add-on/pull/37 - Handling in URLs (303 days) https://github.com/yast/yast-add-on/pull/28 Pending requests in repository yast-autoinstallation: - Added documentation explanining different network scenarios (6 days) https://github.com/yast/yast-autoinstallation/pull/289 Pending requests in repository yast-bootloader: - [blog] Improve ui serial console (67 days) https://github.com/yast/yast-bootloader/pull/393 Pending requests in repository yast-control-center-gnome: - remove useless changlog, (68 days) https://github.com/yast/yast-control-center-gnome/pull/26 Pending requests in repository yast-country: - Ensure ntp is installed (when Install Recommended Packages is off) (216 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-installation: - Merge of SLE-12-SP2-CASP into master (9 days) https://github.com/yast/yast-installation/pull/525 Pending requests in repository yast-network: - Add a Codacy badge to README.md (25 days) https://github.com/yast/yast-network/pull/499 - Forbid the addition of wlan interfaces to bridge proposal (bsc#956755) (52 days) https://github.com/yast/yast-network/pull/483 - Improved adding routes (110 days) https://github.com/yast/yast-network/pull/458 Pending requests in repository yast-packager: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (18 days) https://github.com/yast/yast-packager/pull/230 - Added yast2-sw_single-wrapper to handle rpms in Plasma (138 days) https://github.com/yast/yast-packager/pull/195 - Added yast2-sw_single-wrapper to handle rpms in KDE (145 days) https://github.com/yast/yast-packager/pull/190 - Allow KDE to use packager for opening rpms (188 days) https://github.com/yast/yast-packager/pull/174 - Prioritize yast-packager for opening rpms (152 days) https://github.com/yast/yast-packager/pull/173 Pending requests in repository yast-pkg-bindings: - [WIP] Return valid repository signature flag (bsc#1009127) (10 days) https://github.com/yast/yast-pkg-bindings/pull/65 - Fixed failure when trying to save a plugin service (bsc#1021117) (27 days) https://github.com/yast/yast-pkg-bindings/pull/64 - [WIP] Build ruby-lint definitions (242 days) https://github.com/yast/yast-pkg-bindings/pull/60 Pending requests in repository yast-rdp: - bnc#988353 RDP dialog displays error during installation (185 days) https://github.com/yast/yast-rdp/pull/4 Pending requests in repository yast-security: - refactoring autoconverted ruby code into ruby code (144 days) https://github.com/yast/yast-security/pull/40 Pending requests in repository yast-snapper: - [WIP] Added snapshot Class with strategy pattern. (270 days) https://github.com/yast/yast-snapper/pull/40 Pending requests in repository yast-sound: - [WIP] (L3) SP4 soundcard DB update (23 days) https://github.com/yast/yast-sound/pull/19 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