February 2014 - YaST Development - openSUSE Mailing Lists

[yast-devel] Fixing yast2-slide-show for SLE11 SP3
by Karl Eichwalder 16 Sep '15

16 Sep '15

I want to fix yast2-slide-show for SLE11 SP3. Which git commands do I have to use, please? Thus far, I have checked out trunk only. -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 7

[yast-devel] who is the maintainer?
by Arvin Schnell 08 Dec '14

08 Dec '14

Hi, while reassigning yast-maintainers bugs I noticed that once again the maintainer/bugowner information is inconsistent: The content of the MAINTAINER file in git differs from the output of 'osc maintainer' or 'osc bugowner'. This leads to confusion. We had this problem before and apparently fail to solve the inconsistency long term. So I propose to drop the MAINTAINER file in git and rely on osc. Instead we can have a AUTHORS files so that people not knowing about osc can still reach the authors. Regards, Arvin -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

6 10

[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] Never include anything in global namespace
by Josef Reidinger 28 Feb '14

28 Feb '14

Hi, I just would like to remind that noone should include/extend anything to global namespace in his ruby code. It affects clients, modules, libs and also includes. The most visible part is `include Yast` which cause that all modules living in Yast namespace start living in global namespace and start colliding with ruby classes and modules. But also other smaller modules can cause problem. example of code that can break complete installation is https://github.com/yast/yast-network/blob/11d9c4b7435bb34f5c40c8c19d8c68c58… So please do not do it. Josef -- 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] What means calling Service.[Start|Stop|Enable|Disable]("foo")?
by Johannes Meixner 28 Feb '14

28 Feb '14

Hello, when there is one service foo with two systemd unit files foo.service and foo.socket and a YaST module calls Service.Enable("foo") Service.Start("foo") Service.Stop("foo") Service.Disable("foo") what is each call meant to result in the system? Does calling Service.[Start|Stop|Enable|Disable]("foo") mean both foo.service and foo.socket get started/stopped/enabled/disabled or does calling Service.[Start|Stop|Enable|Disable]("foo") mean only foo.service gets started/stopped/enabled/disabled? I would expect that calling Service.[Start|Stop|Enable|Disable]("foo") means "the whole 'foo' thing" (both foo.service and foo.socket) while calling Service.[Start|Stop|Enable|Disable]("foo.service") means only foo.service (but not foo.socket). See in particular https://bugzilla.novell.com/show_bug.cgi?id=800492#c8 that reads [it was YCP at that time (openSUSE 12.3)] (excerpt): ----------------------------------------------------------------------- ... the YCP call Service::Stop("foo") should completely stop those service in all ways how those service can be active or semi-active via systemd. This way Service::Stop("foo") would work for systemd in compliance how it worked all the time for SysVinit and all YaST modules that use Service::Stop("foo") would work the same for systemd and SysVinit. In contrast if Service::Stop("foo") only stops foo.service but not foo.socket, foo.path (and all other possible ways which may exist in systemd), then Service::Stop("foo") would be basically useless functionality for systemd because if e.g. foo.socket is still active, any normal user can activate the service by triggering systemd via the socket ----------------------------------------------------------------------- Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 5

[yast-devel] How to avoid rebooting between stage1 and stage2 of installation?
by Lin Ma 27 Feb '14

27 Feb '14

Hi all, I'm running some unattended_http_install tests on os12.3 and 13.1, I dont want the vm to reboot/turn off before the end of stage 2. I noticed that "openSUSE 11.0 uses the kexec feature and does not reboot anymore between stage1 and stage2. " How can I use this feature to avoid reboot? Do I need to modify autoyast file? Thanks, Lin

3 2

[yast-devel] about removal of yast2-python-bindings, yast2-cluster needs it.
by Dongmao Zhang 27 Feb '14

27 Feb '14

hi,all I have SCR agent written by python in yast2-cluster module. It requires yast2-python-bindings 'import ycp', So what is the suggestion about this issue? Do you have any alternative python library to do this? Thanks a lot. Dongmao Zhang >Script 'mail_helper' called by ro >Hi dmzhang(a)suse.com, >/mounts/work_src_done/SLE12/yast2-cluster was not checked in by ro for >the following reasons: >(submitrequest 33435 on https://build.suse.de) >yast2-python-bindings is deprecated and scheduled for removal >this is "only old proof of concept" according to yast2 developers. >please discuss this first with the yast2 maintainers. >your dist/autobuild team. -- 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] Pending Pull Requests
by yast-ci＠opensuse.org 27 Feb '14

27 Feb '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 skelcd-control-SLES: - Running client for loadin net config from install.inf (5 days) https://github.com/yast/skelcd-control-SLES/pull/14 -- 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] I18n - added N_() and Nn_() to Yast
by Ladislav Slezak 26 Feb '14

26 Feb '14

Hi all, I just have added N_() and Nn_() gettext equivalents to the latest ruby-bindings (yast2-ruby-bindings-3.1.12). These functions take the same arguments as _() and n_() functions but do *not* translate the strings, they return the original untranslated values. The side effect is that these string are found by gettext when crating POT file and so they can be translated by translators. Of course, to make it fully usable you need to do translation later using _() or n_(). Some examples when this can be used: - translating constants (see [1] for an example) - for logging an untranslated text, but displaying translated text to the user: begin ... # does not translate, the exception contains the untranslated string, # but it's recognized by gettext like normal _() raise FooError, N_("Foo failed.") ... rescue FooError => e # log the original (untranslated) error log.error e.message # but display translated error to the user, # _() does the actual translation Popup.Error(_(e.message)) end This approach can be used whenever you need both original and translated text. Later we could use this to fix Report.Error() to log the untranslated text instead of the translation. Enjoy! [1] https://github.com/webyast/webyast/wiki/Localization#wiki-translating-const… -- 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 1

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

26 Feb '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-registration: - Check for defined client class to avoid warnings (4 days) https://github.com/yast/yast-registration/pull/15 Pending requests in repository yast-ycp-ui-bindings: - simple example for release notes button (4 days) https://github.com/yast/yast-ycp-ui-bindings/pull/17 Pending requests in repository yast-ruby-bindings: - Convert logging (5 days) https://github.com/yast/yast-ruby-bindings/pull/102 - test cyclic includes (7 days) https://github.com/yast/yast-ruby-bindings/pull/101 Pending requests in repository skelcd-control-SLES: - Running client for loadin net config from install.inf (4 days) https://github.com/yast/skelcd-control-SLES/pull/14 Pending requests in repository skelcd-control-SLED: - Remove suseconfig (5 days) https://github.com/yast/skelcd-control-SLED/pull/9 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0