March 2014 - YaST Development - openSUSE Mailing Lists

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 14 Mar '14

14 Mar '14

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-metapackage: - fix fail message on sle (9 days) https://github.com/yast/yast-metapackage/pull/2 -- 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 13 Mar '14

13 Mar '14

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-metapackage: - fix fail message on sle (9 days) https://github.com/yast/yast-metapackage/pull/2 -- 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 12 Mar '14

12 Mar '14

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-kdump: - Fix button width (8 days) https://github.com/yast/yast-kdump/pull/9 Pending requests in repository yast-metapackage: - fix fail message on sle (7 days) https://github.com/yast/yast-metapackage/pull/2 Pending requests in repository yast-users: - migrate to AuthClient module (6 days) https://github.com/yast/yast-users/pull/38 -- 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 and GitHub friends: Travis, Coveralls, CodeClimate, RubyDoc
by Ladislav Slezak 11 Mar '14

11 Mar '14

Hi all, you probably know the services listed in $subj, if not here is a short summary: - Travis - is a CI service similar to Jenkins (see [1] output), but it's directly integrated with GitHub, e.g. it displays the test status (passed/failed) at GitHub commits or pull requests. The advantage is that you can see the build status even *before* creating or merging the pull request. I'm already using it at rubygem-scc_api, see example [2] (There are green checkmarks in front of commit numbers, for open pull requests it colorizes the "merge" box in green/red depending on the build status.) - Coveralls - monitors code coverage, it's an extension for simplecov code coverage tool. It maintains the code coverage history so you can easily see how it is being improved (or not ;-)), see example [3] It also comments on pull requests, see [4]. Unfortunately I have seen it commenting just few times, I do not know if you need a payed account for full support or it's a bug... Anyway, it's a nice add-on feature. - CodeClimate - Provides code metrics, it can find duplicated code, too complex (long) methods...etc. Do not be surprised that it reports a bad code for Yast modules, esp. after automatic YCP to Ruby conversion the code does not look nice. Again, it provides history so you can see how you code quality gets better (or not), you can easily find the commits which added bad quality code. See example [5] The services above also provide badges (PNG icons) which you can place into the main README.md page so you can quickly see the current overall status, see [6]. Click an icon to the details. - RubyDoc - The last service I'd like to mention is RubyDoc.info which builds yard documentation and supports GitHub repositories. The advantage is that the documentation is built automatically and you do not need any extra server to host it. See example [7]. Using in Yast ------------- The main issue when using Travis in Yast is that it can install the additional Ruby libraries only via gems (using bundler). And because Yast is not available as a gem we have a trouble. My workaround it to basically stub all Yast functionality, see yast-registration pull request [8]. That means this approach is good for new code which does not depend on Ruby YCP support much (the legacy builtins etc...) and does not use much Yast specific features. And even with new code some parts cannot be tested or it is really difficult to test them (e.g. Yast clients). This also does not allow to run the old tests which depend on the y2logging feature. All in all I think this is acceptable solution, the advantages mentioned above overweight the extra mocking needed. I'm already using the services in rubygem-scc_api and I really like them. Please, check the pull request [9] and post here what you think about this approach. You can check [10] to see how it should look like after merging it. Possible solution ------------------ Travis actually supports installing any additional packages, but unfortunately for us, it builds on Ubuntu (32-bit Ubuntu 12.04) system. If we would port Yast (at least the base packages) to Ubuntu we could easily move to Travis without any workarounds... (yeah, that sounds like a hackweek or workshop project, doesn't it? :-)) See details in [10] Any comments? [1] https://travis-ci.org/yast/rubygem-scc_api/jobs/20453199 [2] https://github.com/yast/rubygem-scc_api/pull/26 [3] https://coveralls.io/r/yast/rubygem-scc_api?branch=master [4] https://github.com/yast/rubygem-scc_api/pull/10#issuecomment-34160955 [5] https://codeclimate.com/github/yast/rubygem-scc_api [6] https://github.com/yast/rubygem-scc_api [7] http://rubydoc.info/github/yast/yast-yast2/frames [8] https://github.com/yast/yast-registration/pull/25 [9] https://github.com/lslezak/yast-registration [10] http://docs.travis-ci.com/user/build-configuration/#Using-3rd-party-PPAs -- 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

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 11 Mar '14

11 Mar '14

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-kdump: - Fix button width (7 days) https://github.com/yast/yast-kdump/pull/9 Pending requests in repository yast-metapackage: - fix fail message on sle (6 days) https://github.com/yast/yast-metapackage/pull/2 -- 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 10 Mar '14

10 Mar '14

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-kdump: - Fix button width (6 days) https://github.com/yast/yast-kdump/pull/9 Pending requests in repository yast-metapackage: - fix fail message on sle (6 days) https://github.com/yast/yast-metapackage/pull/2 -- 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] openSUSE-12.3 target build disabled in YaST:Head
by Ladislav Slezak 07 Mar '14

07 Mar '14

I have announced this in another thread, I'm just announcing it is a separate mail so it's not overlooked... -- 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

1 0

[yast-devel] [RFC] make Builtins.y2milestone(), y2...() obsolete?
by Ladislav Slezak 07 Mar '14

07 Mar '14

Hi all, another change in yast2-ruby-bindings-3.1.7 is a new Yast::Logger module which wraps Y2Logger mentioned in the previous mail. The module provides standard Ruby logging way [1] for writing into y2log. Example: module Yast class Foo < Client include Yast::Logger def foo # this will be logged into y2log using the usual y2log format # Builtins.y2debug() replacement log.debug "debug" # Builtins.y2milestone() replacement log.info "info" # Builtins.y2error() replacement log.error "error" end end end (See [2] for a real example) The advantages over the Builtins.y2*() are: - it's a standard Ruby way (used also in Rails) - we can easily drop Builtins.y2*() in the future - the Logger API is much more flexible (Logger can log to a different file, STDOUT/STDERR, even a String), can be dynamically changed at run time (set different log level, temporarily enable/disable logging, etc...) (of course, these features do not work currently as it's just a wrapper for y2*(), but that could be changed easily) - the Logger API also supports block parameter for lazy evaluation of the message so e.g. log.debug { "#{(0..10000).to_a}" } has NO performance impact if debug logging is disabled as the string is NOT evaluated. That's nice when you log too much details or log huge data structures. Disadvantages: - the y2*() functions can log different call frame or can log a complete backtrace (but that can be done easily in Ruby and this feature is not used much in Yast) - little bit different log levels, e.g. there is no direct equivalent to y2internal(), on the other hand there is a "fatal" error level (see [3] for the current mapping) Problems which prevent from global change (via a script): - percent place holders (e.g. "%1") do not work, automatic change of the existing code to the new logging style is not trivial - the old logging is used in old tests, automatic replace could potentially break some tests So therefore I'd like to make all Builtins.y2*() functions obsolete and in new code use only the new logging style. And suggest changing the logging when touching the old code (if it does not break tests). What do you think about this proposal? [1] http://www.ruby-doc.org/stdlib-2.1.0/libdoc/logger/rdoc/Logger.html [2] https://github.com/yast/yast-registration/commit/a0c852743b78ac54562e52e826… [3] https://github.com/yast/yast-ruby-bindings/pull/97/files#diff-c61ab27bc14ba… -- 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

5 7

[yast-devel] Wizard UI Documentation
by Julian Zwickl 06 Mar '14

06 Mar '14

Hi, did you have a documentation about the YaST Wizard(UI) for Ruby? And how can I parse .ini configs? Does YaST have a special method? My aim is to control and to set up a deamon(smbtad = Samba Traffic Analyzer Daemon). Regards, Julian -- 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] Re: Run YaST Module with GUI
by Martin Vidner 05 Mar '14

05 Mar '14

On Wed, Mar 05, 2014 at 01:48:46PM +0100, Julian Zwickl wrote: > Hi Martin, > > i have a problem. I modified the yast-cio source but when i > type the command rake run the Module doesn't show a window or anything > else. > > Can you take a look? > https://github.com/hhetter/yast2-smbta/blob/master/src/lib/smbtad/smbta_dia… Hi Julian, I am forwarding this to the public mailing list, hope you don't mind since the repo is public anyay :) y2log (/var/log/YaST2/y2log for sudo rake run, or ~/.y2log) says: 2014-03-05 14:34:35 <3> mrakoplas.suse.cz(6936) [liby2] Y2ProgramComponent.cc(receiveFromExternal):370 External program src/clients/smbta.rb returned invalid data. (No other error means no data at all) Well, that is not of much help, but "strace -f -efile rake run" reveals that YaST tries to simply exec src/clients/smbta.rb. Removing the executable bit helps. -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

1 1