February 2016 - YaST Development - openSUSE Mailing Lists

[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] before I file another bug about font sizes...
by Felix Miata 21 Oct '16

21 Oct '16

...I want to make sure there is a solution that I simply have not yet found. Expected (OK) fonts results (e.g.): sw_single @120 DPI in KDE3 on 13.1: http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesOK131kde3-120.png sw_single @132 DPI in KF5 on TW: http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesOKtwkde5-132.png Not expected (undersized) fonts results (e.g.): sw_single @108 DPI in TDE on 13.2: http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesTooSmall132tde-108.png sw_single @120 DPI in KDE3 on 42.1: http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesTooSmall421kde3-120.p… sw_single @168 DPI in KDE3 on 42.1: http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesTooSmall421kde3-168.p… Clearly sw_single (and other y2 apps) post-13.1 (except in KF5) is using smaller fonts than those used in the y2 control center and in the rest of DE UI, as if both the non-KF5 DE's font settings and QT's font setting in Trolltech.conf are being disregarded. Is there something that can be installed or removed to bring up font sizes to match the rest of the DE and y2cc in KDE3 and TDE without loading the installation with QT5 and/or KF5, or even with QT5 and/or KF5? Or, is this a bug that's already been filed, or one that needs filing? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 4

[yast-devel] Refactoring madness: chapter three
by Ancor Gonzalez Sosa 01 Mar '16

01 Mar '16

This is the (hopefully) last part of my list of thing I considered as the obvious way to go while refactoring/reviewing code at some point but turned out to be more controversial than I expected. This week we'll probably agree in a more shared and less personal view about these topics. 1) RSpec as a design validator I like the RSpec approach to unit testing and I consider the RSpec tests of a class like the detailed documentation about its behavior. I try to write the RSpec tests relatively early in the process (without reaching the extreme of TDD) because it allows me to validate my design decisions. If I struggle to write meaningful readable RSpec test or I need a lot of non-obvious mocking during the process, then I conclude that my classes are not properly designed. In that case, I sometimes switch to TDD mode, writing the desired RSpec and then fixing my class. 2) Another note about OOP design In our new code there are some things that I consider kind of "design smells". I can be, as always, wrong but I feel like some of our code is misusing OOP as a mere way of encapsulate functionality. Going back to concrete real examples, we had this: fake_probing = Yast::Storage::FakeProbing.new devicegraph = fake_probing.devicegraph factory = Yast::Storage::FakeDeviceFactory.new(devicegraph) factory.load_yaml_file(input_file) yaml_writer = Yast::Storage::YamlWriter.new yaml_writer.write(devicegraph, output_file) The fact that we had a "new" every couple of lines is a design smell to me. The adopted solution was creating class methods, so we can do things like this. fake_probing = Yast::Storage::FakeProbing.new devicegraph = fake_probing.devicegraph Yast::Storage::FakeDeviceFactory.load_yaml_file(devicegraph, input_file) Yast::Storage::YamlWriter.write(devicegraph, output_file) Just a cosmetic fix for an issue that I consider deeper: we are writing good old procedural code dressed up as OO code. Every class has the only responsibility of implementing one step in a process and only one public method to execute that step (manipulating a set of I/O arguments). Is just one example of solutions that are perfectly correct but look quite unfamiliar to a Ruby developer's eyes and are quite hard to express as a set of RSpec behavior-oriented specs. Not saying they are wrong, just that they don't look like "the ruby way". Like this alternative which (although not perfect) is a much more "rubyist" way of writing the same: factory = Yast::Storage::DevicegraphFactory.new devicegraph = factory.create_from_file(input_file) File.open(output_file, 'w') {|f| f.write devicegraph.to_yaml } 3) Write every piece of code as something to maintain This is more related to Scrum than to Ruby or OOP. Since we are using Scrum to create YaST, I expect most PBIs to result in a YaST client that can be invoked using /sbin/yast2 or in a set of RSpecs that will be executed in every "rake test:unit" and used as a reference documentation in the future. I consider tests in the "examples" directory to be dead code. I consider that moving code from /test or /src/clients into /src/examples is the first step to have it broken with nobody ever noticing. A have a similar feeling about code used for debugging. It should be "in the right place" design-wise. Don't think in the debugging code as something temporary. If you are needing it today, you will probably need it (or something very similar) also in the future. Make it part of your design... and use mechanisms that would be useful when that code is executed as an RSpec test or yast client. That's all. Sorry again for the long text. I suck at summarizing. 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 4

[yast-devel] new-proposal is dead...
by Ancor Gonzalez Sosa 29 Feb '16

29 Feb '16

...long live the new proposal! This mail is just for letting you know that we already deleted the "new-proposal" branch from the yast-storage git repository. All the code and commits from there are now in the yast-storage-ng repository, in the master branch. There is still work to do[1], but you should already aim to the new repo when working in the new yast-storage. Cheers. [1] https://trello.com/c/IRNNAfuY/ -- 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

1 0

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

29 Feb '16

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: - Fix install rules SLE 12 GA (31 days) https://github.com/yast/yast-autoinstallation/pull/190 - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (45 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (33 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (145 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-installation: - Poc recover values (125 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (86 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (88 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Add option to disable swap creation (32 days) https://github.com/yast/yast-storage/pull/182 - Propose /boot for encrypted root on PowerPC (68 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Cleanup NetworkInterfaces.Read (24 days) https://github.com/yast/yast-yast2/pull/433 Pending requests in repository yast-auth-server: - Drop ca mgm (39 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (93 days) https://github.com/yast/yast.github.io/pull/55 Pending requests in repository aytests-tests: - [do not merge] Installation rules (16 days) https://github.com/yast/aytests-tests/pull/12 -- 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] Pending Pull Requests
by yast-ci＠opensuse.org 26 Feb '16

26 Feb '16

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: - Fix install rules SLE 12 GA (27 days) https://github.com/yast/yast-autoinstallation/pull/190 - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (41 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-bootloader: - [do not merge] partial usage of config files gem (20 days) https://github.com/yast/yast-bootloader/pull/280 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (29 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (141 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-dhcp-server: - Fix "One or more selected network interfaces is not configured" (29 days) https://github.com/yast/yast-dhcp-server/pull/11 Pending requests in repository yast-installation: - Poc recover values (121 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-live-installer: - Fix Symlink resolution (29 days) https://github.com/yast/yast-live-installer/pull/6 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (82 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (84 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Add option to disable swap creation (28 days) https://github.com/yast/yast-storage/pull/182 - Ported support for LVM proposal setting from SP1 to Master (5 days) https://github.com/yast/yast-storage/pull/177 - Propose /boot for encrypted root on PowerPC (64 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Cleanup NetworkInterfaces.Read (20 days) https://github.com/yast/yast-yast2/pull/433 - Count test coverage more accurately (30 days) https://github.com/yast/yast-yast2/pull/426 Pending requests in repository yast-auth-server: - Drop ca mgm (35 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (89 days) https://github.com/yast/yast.github.io/pull/55 Pending requests in repository aytests-tests: - [do not merge] Installation rules (12 days) https://github.com/yast/aytests-tests/pull/12 -- 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] Pending Pull Requests
by yast-ci＠opensuse.org 26 Feb '16

26 Feb '16

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: - Fix install rules SLE 12 GA (28 days) https://github.com/yast/yast-autoinstallation/pull/190 - [Review] Request from 'schubi2' @ 'yast/yast-autoinstallation/review_160113_bug_955878_merged_with_sp1' (42 days) https://github.com/yast/yast-autoinstallation/pull/179 Pending requests in repository yast-bootloader: - [do not merge] partial usage of config files gem (21 days) https://github.com/yast/yast-bootloader/pull/280 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (30 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (142 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-installation: - Poc recover values (122 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-snapper: - [DO NOT MERGE] Added snapshot Class with strategy pattern. (83 days) https://github.com/yast/yast-snapper/pull/40 - Cleanup and delete multiple snapshots at once (#bsc#956143). (85 days) https://github.com/yast/yast-snapper/pull/39 Pending requests in repository yast-storage: - Add option to disable swap creation (29 days) https://github.com/yast/yast-storage/pull/182 - Propose /boot for encrypted root on PowerPC (65 days) https://github.com/yast/yast-storage/pull/155 Pending requests in repository yast-yast2: - Cleanup NetworkInterfaces.Read (21 days) https://github.com/yast/yast-yast2/pull/433 Pending requests in repository yast-auth-server: - Drop ca mgm (36 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository yast.github.io: - Add some documentation about submit requests (90 days) https://github.com/yast/yast.github.io/pull/55 Pending requests in repository aytests-tests: - [do not merge] Installation rules (13 days) https://github.com/yast/aytests-tests/pull/12 -- 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] yast2 proxy configuration test error
by guenter 25 Feb '16

25 Feb '16

Hi folks, because I have no Novell account nere a bug report to whom it me concern: opensuse 13.1 yast2 proxy test proxy config => returns error Details: > GET http://www.novell.com/ HTTP/1.1 > Host: www.novell.com > User-Agent: curl/7.42.1 > Accept: */* > Proxy-Connection: Keep-Alive > * HTTP 1.0, assume close after body < HTTP/1.0 301 Moved Permanently Solution: Choose another test destination Regards, guenter -- . -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

4 4

[yast-devel] renamed new libstorage
by Arvin Schnell 25 Feb '16

25 Feb '16

Hi, as decided during the planning meeting I have renamed the new libstorage to libstorage-ng: Some things I renamed: RPM name to libstorage-ng (and subpackages accordingly). Library so name to libstorage-ng. Textdomain to libstorage-ng. Git repository from libstorage-bgl-eval to libstorage-ng. I also changed the version to 1.0.0 and the major library version to 3 (yes, those numbers are entirely independent). Some things I did not rename: C++ namespace (still "storage"). C++ header files (still "/usr/include/storage/..."). The name of the Python, Ruby and Perl5 modules (still "storage"). Fillup/sysconfig file (still "storage"). Regards, Arvin -- Arvin Schnell, <aschnell(a)suse.com> Senior Software Engineer, Research & Development SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- 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: highlights of development sprint 15
by Ancor Gonzalez Sosa 25 Feb '16

25 Feb '16

Three sprints in a row and we keep blogging about YaST development! https://lizards.opensuse.org/?p=11707 Enjoy -- 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