October 2013 - YaST Development - openSUSE Mailing Lists

[yast-devel] Ops.is() - limited support for maps/lists
by Ladislav Slezak 21 Oct '13

21 Oct '13

Hi all, this is JFYI to be aware of an Ops.is() limitation. During debugging a crash in yast2-sound [1] I found out that Ops.is() implementaion does not properly support all data types. The problem is with typed maps/lists, the internal data type is not checked at all. Example: Ops.is({}, "list") => false Ops.is([], "list") => true Ops.is([1, 2], "list<integer>") => true But also: Ops.is([1, 2], "list<string>") => true This makes a trouble when the internal data type is important: if Ops.is(foo, "list<string>") ... elsif Ops.is(foo, "list<integer>") ... I have checked all occurencies in Yast ([2]) and only yast2-sound seems to be affected therefore I have fixed it just there. See the pull request [3], I simple replaced Ops.is() by native Ruby #is_a? method [4]. [1] https://bugzilla.novell.com/show_bug.cgi?id=845928 [2] https://bugzilla.novell.com/show_bug.cgi?id=845928#c3 [3] https://github.com/yast/yast-sound/pull/4 [4] http://ruby-doc.org/core-2.0.0/Object.html#method-i-is_a-3F -- 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] YaST installer - the future development (for 13.2/SLE12, aka "the new installer")
by Ladislav Slezak 18 Oct '13

18 Oct '13

Hi all, The SUSE YaST team started developing some major YaST features for SUSE Linux Enterprise 12 (SLE12) installer and we would like to include these features in the next openSUSE-13.2 release. The features are mainly about making the installer easier and to simplify the installation workflow. We will not create a completely new installer from scratch (that would need too much time and manpower), we will reuse the existing functionality as much as possible, the current installation framework is quite flexible (e.g. the installation steps are defined in external control.xml file). Here is the summary of the main goals: - Remove the second installation stage (started after reboot), configure the system completely just in one stage, after finishing the installer the freshly installed system must be ready to use. - It should be possible to NOT install the Yast installer itself into the target system to make it smaller (except when firstboot or some complex AutoYast setup is used, then the installer will be needed). - Separate the installer into 3 basic steps (collect data, install, apply config), make the steps replaceable by 3rd party applications. - It should be possible to use the installer just for configuring the installation and exporting the setup into a file (without performing the actual installation). The exported file could be then used to install other system(s). (Like AutoYast does, the new installer will contain some AutoYast functionality). - It should be possible to alternatively deploy already existing appliance image (provided by user) instead of installing from RPMs. - Simplify the installation workflow, auto-configure what's possible, advanced setup (NIS, LDAP, Kerberos...) should be done in installed system. - Use new possibilities for autodetection (e.g. GeoIP for language / time zone proposal). - Works on a system with 512MB RAM only, we also keep in mind the resources needed for the installer. More details about the current proposal will be published later. We would like to discuss these ideas in the openSUSE installer context so the new installer brings also interesting and important features for the openSUSE community users. Ladislav -- 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

7 19

[yast-devel] Rspec and its dependencies
by Josef Reidinger 16 Oct '13

16 Oct '13

Hi, When I play with jenkins setup I face one issue with rspec modules that is newly written ( thanks gabi, vmoravec and mfilka for being explorer ). Issue is that some modules have heavy dependencies and idea of jenkins is to have minimal stable installation so it doesn't need regular updates like old one. There is four possible solutions with this issue: 1) mock everything outside of your module. Pros: - testing only your module - more presure to stable API - only ruby-bindings on jenkins Cons: - in todays modules it can be a lot of work to mock all stuff, so it can discourage developers from writting tests 2) mock everything except yast2 Pros: - tests also yast2 which almost doesn't have external dependencies like SCR calls to system - less work as mocking only non-framework dependencies ( like mock users in ldap module ) Cons: - yast2 must be on jenkins and it effective break idea to have one node to test all maintenance branches 3) install everything on jenkins node Pros: - no mocking Cons: - need to keep it uptodate ( to be honest then we need different volunteer to maintain yast jenkins node ) 4) skip running rspec tests before osc:build and run it only during osc build as part of test if package build Pros: - no dependencies, even ruby bindings is not part, only yast-rake Cons: - if rspec test fail, then it will be later in build, so no fail fast My preffered solution is 4 because it reduce maintain of yast jenkins node and contra is not so big. Lets discussion start. If there is no objections I change yast-rake to not run test:unit before osc:build at the end of week. Josef -- 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] Packages not dropped and not in Yast:Head
by Josef Reidinger 14 Oct '13

14 Oct '13

Hi, when I creating jobs on jenkins I found that we have bunch of modules that is not dropped ( no single README.md ) and also not in Yast:Head, so in fact testing on opensuse is not possible. I like to know if this modules still living and what is reason to not have it in Yast:Head. Reason is that there is some changes that affect all yast modules, so we need to know what must be adapted and what is just dead and we can stop caring about. Below is list of such modules ( please comment if modules are living or should be dropped and reason why it is not in yast:head ): boot_server certify cim cluster heartbeat iplb ipsec irda mail_server mouse mysql_server nts_utils oem_installation openva_security_scanner openwsman phone_services pos-instalation slepos-system-manager slepos-image-builder power_management registration s390 sshd I add to CC all maintainers mentioned in such modules. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

5 5

[yast-devel] 13.1RC1 attempt off to a bad start
by Felix Miata 13 Oct '13

13 Oct '13

http://fm.no-ip.com/SS/Suse/yast2-datetime131rc1.jpg Time was off by TZ offset even though checkbox for UTC time was correctly unset. As SS shows, can't see what it is in order to fix it. cmdline: kernel (hd0,2)/boot/suse131/linux install=http://download.opensuse.org/distribution/13.1/repo/oss/ hostname=myhost hostip=192.168.1.2/24 gateway=192.168.0.1 nameserver=8.8.8.8 kexec_reboot=0 vga=791 video=1152x864 ipv6.disable=1 net.ifnames=0 lang=en keytable=us linux (no access via Mozilla HTTP): ftp'd with mc from gwdg.de 4783344 Oct 9 07:34 initrd (no access via Mozilla HTTP): ftp'd with mc from gwdg.de 67395K Oct 9 07:34 Why installer can't obey either vga= or video= I can't fathom either. EDID provides the device's preferred mode, not mine. -- "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

2 2

[yast-devel] YaST Developer Happiness: Reboot the Documentation
by Martin Vidner 11 Oct '13

11 Oct '13

or, what David and I have been working on: https://hackweek.suse.com/projects/132 -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

1 1

[yast-devel] YaST Developer Documentation: Vision
by Martin Vidner 11 Oct '13

11 Oct '13

In the short term, many things can break. But Don't Panic! We have A Plan! - it has a part focused on NEWCOMERS - it is UP TO DATE - the common part: by having a designated MAINTAINER (mvidner) - the module specific parts: by living in the same REPO as the code - by publishing (and generating) it CONTINUOUSLY - it is EASY TO EDIT, by favoring Markdown over DocBook and MediaWiki - it is REACHABLE, by being well hyperlinked together - we favor FREQUENT and SMALL improvements This is part of "YaST Developer Happiness: Reboot the Documentation" https://hackweek.suse.com/projects/132 -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

1 0

[yast-devel] Rakefile in all yast modules
by Josef Reidinger 09 Oct '13

09 Oct '13

Hi, after few initial set of pull requests that add Rakefile and go thrue review, I see that it is very ineefective to create pull request to each module. So my plan is to do it massive for each module and add it globally to jenkins. Example pull request can be seen in [1], [2] or [3]. If you do not have any objections I will do it tomorrow during lunch. Josef [1] https://github.com/yast/yast-yast2/pull/114 [2] https://github.com/yast/yast-core/pull/53 [3] https://github.com/yast/yast-apparmor/pull/4 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

4 8

[yast-devel] CI and email when build fails
by Josef Reidinger 08 Oct '13

08 Oct '13

Hi, I start setting up jobs for adapted modules in public ci.opensuse.org Question is wheere should it write email when build fail. Options are: 1) Only to person who broke it 2) also to some mailing list (yast-commit or yast-devel) 3) other mail address ( which one?) Without it I worry that it take some time until we notice that something is broken. Josef -- 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] Whitespace: Editors and Indentation
by Martin Vidner 05 Oct '13

05 Oct '13

This howto should help you follow the [style guide][1]. ruby-mode for Emacs has the defaults right. Plain vim defaults to Tab characters so it needs adjustments in ~/.vimrc . [1]: https://github.com/SUSE/style-guides/blob/master/Ruby.md Rules ----- 1. No Tab Characters emacs: (setq-default indent-tabs-mode nil) vim: set expandtab 2. Existing Tab Characters are 8 Columns Wide emacs: (setq-default tab-width 8) vim: set tabstop=8 A notable offender is GitHub which uses 4. See point 1. The tab *key* is a different matter, see point 3. 3. Ruby Indentation Level is 2 emacs: (setq-default ruby-indent-level 2) vim: set softtabstop=2 set shiftwidth=2 If you disagree with this, please read JWZ's explanation of the concepts first: http://www.jwz.org/doc/tabs-vs-spaces.html Future ------ I have also looked into these things but don't have a recommendation. If you want me to continue, speak up. - trailing whitespace: lesser impact, I haven't nailed down the right config yet - local configuration: file-specific is easy but clutters files directory-specific needs a vim plugin; Emacs just works, as usual ;-) -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

3 2