July 2013 - YaST Development - openSUSE Mailing Lists

[yast-devel] Build failed in Jenkins: yast-firstboot-HEAD #236
by hudson＠suse.de 30 Jul '13

30 Jul '13

See <http://river.suse.de/job/yast-firstboot-HEAD/236/changes> Changes: [yast-devel] YCP Killer: Unify YaST module structure [yast-devel] YCP Killer: Apply changes needed for Ruby translation [yast-devel] YCP Killer: Translate YCP files into Ruby [yast-devel] YCP Killer: Regenerate Makefile.am files in all source directories ------------------------------------------ [...truncated 178 lines...] /usr/lib/YaST2/bin/ycpmakedep --prefix=/usr > ../.dep.new cat ../.dep.new > .dep rm ../.dep.new make[1]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/desktop'> make[1]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/desktop'> make[1]: Nothing to be done for `all'. make[1]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/desktop'> Making all in doc make[1]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/doc'> Making all in autodocs make[2]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/doc/autodocs'> if [ -n "" ]; then /usr/lib/YaST2/bin/ycpdoc -d. -s./../../src ; fi for i in ; do \ b=${i##./../../src}; b=${b#/}; b=${b//\//__}; b=${b%.pm}; \ pod2html --title=$b --infile=$i --outfile=$b.html; \ echo "<a href='$b.html'>${b/__/::}</a>" > $b.mod.html; \ done if [ -n "./../../src/modules/Firstboot.rb ./../../src/include/firstboot/routines.rb" ]; then yard doc --title "yast2-firstboot -- Development Documentation" -o . -m markdown ./../../src/modules/Firstboot.rb ./../../src/include/firstboot/routines.rb; fi [error]: Missing 'redcarpet' gem for Markdown formatting. Install it with `gem install redcarpet` make[2]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/doc/autodocs'> make[2]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/doc'> XML_CATALOG_FILES=/etc/xml/catalog \ /usr/bin/xsltproc --nonet --xinclude \ /usr/share/YaST2/data/docbook/stylesheets/customize-html.xsl firstboot-doc.xml Writing html/index.html for article cp /usr/share/YaST2/data/docbook/css/yast2docs.css html cp -a `pkg-config --variable=yast2dir yast2-devtools`/data/docbook/images html make[2]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/doc'> make[1]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/doc'> Making all in scripts make[1]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/scripts'> Making all in Firstboot-Stage make[2]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/scripts/Firstboot-…'> make[2]: Nothing to be done for `all'. make[2]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/scripts/Firstboot-…'> make[2]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/scripts'> make[2]: Nothing to be done for `all-am'. make[2]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/scripts'> make[1]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/scripts'> Making all in src make[1]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/src'> make[1]: Nothing to be done for `all'. make[1]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/src'> Making all in testsuite make[1]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/testsuite'> make -f /usr/share/YaST2/data/testsuite/Makefile.testsuite RPMNAME=yast2-firstboot srcdir=. make[2]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/testsuite'> mkdir -p ./run ./config ./yast2-firstboot.test ./tests cp -f /usr/share/YaST2/data/testsuite/skel/default.exp config/default.exp cp -f /usr/share/YaST2/data/testsuite/skel/unix.exp config/unix.exp cp -f /usr/share/YaST2/data/testsuite/skel/unknown.exp config/unknown.exp cp -f /usr/share/YaST2/data/testsuite/skel/testsuite.exp yast2-firstboot.test/testsuite.exp cp -f /usr/share/YaST2/data/testsuite/skel/runtest.sh run/runtest.sh chmod +x run/runtest.sh make[2]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/testsuite'> make[1]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/testsuite'> make[1]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout'> make[1]: Nothing to be done for `all-am'. make[1]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout'> + make check Making check in agents make[1]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/agents'> make[1]: Nothing to be done for `check'. make[1]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/agents'> Making check in control make[1]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/control'> make[1]: Nothing to be done for `check'. make[1]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/control'> Making check in desktop make[1]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/desktop'> make[1]: Nothing to be done for `check'. make[1]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/desktop'> Making check in doc make[1]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/doc'> Making check in autodocs make[2]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/doc/autodocs'> if [ -n "" ]; then /usr/lib/YaST2/bin/ycpdoc -d. -s./../../src ; fi for i in ; do \ b=${i##./../../src}; b=${b#/}; b=${b//\//__}; b=${b%.pm}; \ pod2html --title=$b --infile=$i --outfile=$b.html; \ echo "<a href='$b.html'>${b/__/::}</a>" > $b.mod.html; \ done if [ -n "./../../src/modules/Firstboot.rb ./../../src/include/firstboot/routines.rb" ]; then yard doc --title "yast2-firstboot -- Development Documentation" -o . -m markdown ./../../src/modules/Firstboot.rb ./../../src/include/firstboot/routines.rb; fi [error]: Missing 'redcarpet' gem for Markdown formatting. Install it with `gem install redcarpet` make[2]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/doc/autodocs'> make[2]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/doc'> make[2]: Nothing to be done for `check-am'. make[2]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/doc'> make[1]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/doc'> Making check in scripts make[1]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/scripts'> Making check in Firstboot-Stage make[2]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/scripts/Firstboot-…'> make[2]: Nothing to be done for `check'. make[2]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/scripts/Firstboot-…'> make[2]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/scripts'> make[2]: Nothing to be done for `check-am'. make[2]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/scripts'> make[1]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/scripts'> Making check in src make[1]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/src'> make[1]: Nothing to be done for `check'. make[1]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/src'> Making check in testsuite make[1]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/testsuite'> make -f /usr/share/YaST2/data/testsuite/Makefile.testsuite RPMNAME=yast2-firstboot srcdir=. make[2]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/testsuite'> make[2]: Nothing to be done for `all'. make[2]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/testsuite'> make check-DEJAGNU check-local make[2]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/testsuite'> Making a new site.exp file ... srcdir='.'; export srcdir; \ EXPECT=expect; export EXPECT; \ runtest=runtest; \ if /bin/sh -c "$runtest --version" > /dev/null 2>&1; then \ exit_status=0; l='yast2-firstboot'; for tool in $l; do \ if $runtest --tool $tool --srcdir $srcdir ; \ then :; else exit_status=1; fi; \ done; \ else echo "WARNING: could not find 'runtest'" 1>&2; :;\ fi; \ exit $exit_status WARNING: Couldn't find tool init file Test Run By root on Tue Jul 30 13:03:37 2013 Native configuration is x86_64-suse-linux-gnu === yast2-firstboot tests === Schedule of variations: unix Running target unix Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using ./config/unix.exp as tool-and-target-specific interface file. Running ./yast2-firstboot.test/testsuite.exp ... ERROR: tcl error sourcing ./yast2-firstboot.test/testsuite.exp. ERROR: no files matched glob pattern "./tests/*.{ycp,rb}" while executing "glob "$srcdir/tests/$pattern.{ycp,rb}"" invoked from within "lsort [glob "$srcdir/tests/$pattern.{ycp,rb}"]" invoked from within "set filenames [lsort [glob "$srcdir/tests/$pattern.{ycp,rb}"]]" (file "./yast2-firstboot.test/testsuite.exp" line 18) invoked from within "source ./yast2-firstboot.test/testsuite.exp" ("uplevel" body line 1) invoked from within "uplevel #0 source ./yast2-firstboot.test/testsuite.exp" invoked from within "catch "uplevel #0 source $test_file_name"" === yast2-firstboot Summary === make -f /usr/share/YaST2/data/testsuite/Makefile.testsuite RPMNAME=yast2-firstboot srcdir=. check make[3]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/testsuite'> Parse YCP NOT RUNNING make[3]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/testsuite'> make[2]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/testsuite'> make[1]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/testsuite'> make[1]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout'> make[1]: Nothing to be done for `check-am'. make[1]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout'> + make install Making install in agents make[1]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/agents'> make[2]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/agents'> make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/agents'> make[1]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/agents'> Making install in control make[1]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/control'> make[2]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/control'> make[2]: Nothing to be done for `install-exec-am'. /usr/bin/mkdir -p '/etc/YaST2' /usr/bin/install -c -p -m 644 firstboot.xml '/etc/YaST2' make[2]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/control'> make[1]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/control'> Making install in desktop make[1]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/desktop'> make[2]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/desktop'> make[2]: Nothing to be done for `install-exec-am'. /usr/bin/mkdir -p '/usr/share/autoinstall/modules' /usr/bin/install -c -p -m 644 firstboot.desktop '/usr/share/autoinstall/modules' make[2]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/desktop'> make[1]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/desktop'> Making install in doc make[1]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/doc'> Making install in autodocs make[2]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/doc/autodocs'> if [ -n "" ]; then /usr/lib/YaST2/bin/ycpdoc -d. -s./../../src ; fi for i in ; do \ b=${i##./../../src}; b=${b#/}; b=${b//\//__}; b=${b%.pm}; \ pod2html --title=$b --infile=$i --outfile=$b.html; \ echo "<a href='$b.html'>${b/__/::}</a>" > $b.mod.html; \ done if [ -n "./../../src/modules/Firstboot.rb ./../../src/include/firstboot/routines.rb" ]; then yard doc --title "yast2-firstboot -- Development Documentation" -o . -m markdown ./../../src/modules/Firstboot.rb ./../../src/include/firstboot/routines.rb; fi [error]: Missing 'redcarpet' gem for Markdown formatting. Install it with `gem install redcarpet` make[3]: Entering directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/doc/autodocs'> make[3]: Nothing to be done for `install-exec-am'. if [ -n "" ]; then /usr/lib/YaST2/bin/ycpdoc -d. -s./../../src ; fi for i in ; do \ b=${i##./../../src}; b=${b#/}; b=${b//\//__}; b=${b%.pm}; \ pod2html --title=$b --infile=$i --outfile=$b.html; \ echo "<a href='$b.html'>${b/__/::}</a>" > $b.mod.html; \ done if [ -n "./../../src/modules/Firstboot.rb ./../../src/include/firstboot/routines.rb" ]; then yard doc --title "yast2-firstboot -- Development Documentation" -o . -m markdown ./../../src/modules/Firstboot.rb ./../../src/include/firstboot/routines.rb; fi [error]: Missing 'redcarpet' gem for Markdown formatting. Install it with `gem install redcarpet` /usr/bin/mkdir -p '/usr/share/doc/packages/yast2-firstboot//autodocs' /usr/bin/install -c -p -m 644 ./index.html '/usr/share/doc/packages/yast2-firstboot//autodocs/.' /usr/bin/install: cannot stat ‘./index.html’: No such file or directory make[3]: *** [install-nobase_htmlDATA] Error 1 make[3]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/doc/autodocs'> make[2]: *** [install-am] Error 2 make[2]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/doc/autodocs'> make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `<http://river.suse.de/job/yast-firstboot-HEAD/ws/checkout/doc'> make: *** [install-recursive] Error 1 ++ error_exit 2 ++ echo 'ERROR: detected exitcode 2' ERROR: detected exitcode 2 ++ cleanup ++ echo '==> Running cleanup' ==> Running cleanup ++ rm -f <http://river.suse.de/job/yast-firstboot-HEAD/ws/ICECC/40c0ab7e54f59a1e4e493…> ++ footer_and_exit 1 ++ '[' -z 1 ']' ++ MYEXIT=1 ++ '[' 1 == 0 ']' ++ ascii_failed ++ cat ( ) ( ) ( ) _ ) ( \_ _(_\ \)__ (____\___)) build failed ++ exit 1 Build step 'Execute shell' marked build as failure -- 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] IMPORTANT: Git master is "frozen"!
by Ladislav Slezak 30 Jul '13

30 Jul '13

Hi all, The day D is here! Please, DO NOT commit anything to Git master from now! We will let you know when the Ruby conversion is finished and master is open for further development. Thank you! -- 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] Member of team on github with push rights
by Josef Reidinger 29 Jul '13

29 Jul '13

Hi, because I need now to modify team member ( to add non-personalised user for ycp-killer ), I found that there is some team members with push right, that do no contribution and I see no reason for them to have direct push rights ( of course everyone can use pull request from own fork ). These members are: Scott Reeves https://github.com/sreeves Michael G. Fritch https://github.com/mgfritch Cameron Seader https://github.com/cseader bruclik https://github.com/bruclik Questionable is Bjoern Esser, who actively contribute to libyui, but I don't see activity in YaST, so I expect that also his possible patches should go through pull request ( of course everyone's patches should go through review, but person with push rights can also accept it ). If anyone see reason why it should have push rights, please speak up otherwise they will be removed from team. Thanks 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] Example module for demonstration refactoring
by Josef Reidinger 29 Jul '13

29 Jul '13

Hi, as ruby conversion knocking on a door I want to make after conversion small demonstration how ruby can improve code. I don't want write hypothetical module but change real module. Does anyone have idea which relative small ("network" is not small :) module can be used as demonstration? I plan to demonstrate things like advanced testing in ruby, represent internal structures as objects or error handling with exceptions. Josef -- 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] YaST Ruby final conversion & integration tomorrow
by David Majda 29 Jul '13

29 Jul '13

Hi, on today's YCP Killer meeting we decided we are GO for the YCP to Ruby final conversion & integration tomorrow Tuesday July 30. This means we'll implement the plan outlined in [1] and [2]. The most important thing for you: ** YaST Git will be frozen from 2013-07-30 6:00 CEST ** The freeze is expected to take one day. We will notify you when the freeze is over or if we encounter problems during the final conversion & integration that will make it take longer. [1] http://lists.opensuse.org/yast-devel/2013-07/msg00028.html [2] http://lists.opensuse.org/yast-devel/2013-07/msg00038.html -- David Majda SUSE Studio developer http://susestudio.com/ -- 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] libyui C++
by Manu Gupta 27 Jul '13

27 Jul '13

Hey All With most of the yast rewritten in ruby now, does it in any way affect the libyui c++ bindings -- Regards Manu Gupta -- 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] Integration of YaST in Ruby - update
by David Majda 26 Jul '13

26 Jul '13

Hi, this is an update to my previous e-mail about YaST in Ruby integration [1]. Currently we are finalizing testing of Ruby YaST. On Monday July 29, we will hold an internal go/no-go meeting and if we are good at that point, we will start the final conversion and integration on Tuesday July 30. If we happen to have any unsolved problems on Monday, we may end up starting the integration a day or two later. The integration will be done roughly according to the plan outlined in [1]. We expect the integration to take 1 day, but since we depend on various unpredictable factors such as OBS load, it may end up taking longer. During the whole integration, we will need all YaST Git repositories to be frozen. We won't implement any technical measures to ensure this -- just please don't commit anything to master once the integration starts. If you do so, you may complicate the integration and your changes may be lost. After the go/no-go meeting on Monday, we will announce the decision, and if the decision is "go", we will also announce the time when the integration and associated Git freeze will start. We will also notify you when the conversion is over or if we encounter problems that will make it take longer than 1 day. [1] http://lists.opensuse.org/yast-devel/2013-07/msg00028.html -- David Majda SUSE Studio developer http://susestudio.com/ -- 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] Online documentation for ruby bindings
by Josef Reidinger 24 Jul '13

24 Jul '13

Hi, because ruby bindings became quite critical part when we switch to ruby I start improving its documentation. It can be found online ( and generated in real time ) at http://rubydoc.info/github/yast/yast-ruby-bindings/ I hope that in future we will have it for all our modules, so we have place for recent documentation for me and generated automatic. Note: I just create configuration and start improving doc, so it is now work in progress in sense of documentation completeness. Josef -- 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] Easy driver updates and install testing
by Steffen Winterfeldt 22 Jul '13

22 Jul '13

If you need to use driver updates from time to time and can't quite remember the details, mkdud (available in OBS) does it for you now. # Updating packages is as simple as mkdud -c mydud -d sle11 yast-*.rpm # Or adding some random files to the installation system mkdud -c mydud -d 13.1 dir_with_somefiles # Replacing some individual ycp files mkdir -c mydud -d sle11 foo.ycp bar.ycp bar.ybc Steffen -- Give orange me give eat orange me eat orange give me eat orange give me you. (chimp Nim, using sign language) -- 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] Integration of YaST in Ruby
by David Majda 18 Jul '13

18 Jul '13

Hi, as promised in my yesterday's mail [1], here is a plan of integration of YaST in Ruby into the openSUSE M4. Please let me know if you have any comments or objections. Description ----------- Technically, the integration consists of the following steps: 1. Freeze YaST Git repositories. 2. Do the final translation of frozen code into Ruby (with final versions of YCP Killer and Y2R, which would be labeled as 1.0 at that point). 3. Commit translated Ruby code into master branches of affected YaST repositories. Create tags marking the last YCP-based version and first Ruby-based version. 4. Increase version of all YaST modules to 3.0 (as previously discussed [2]). 5. Wait for YaST packages in YaST:head to build (this will happen automagically after comitting the changes). 6. Submit new YaST packages into Factory. 7. Unfreeze YaST Git repositories. 8. Grab a beer and celebrate the beginning of new shiny Ruby era :-) Plan ---- We think the best time to do the work above is during 3 days from Wednesday July 31 to Friday August 2. This means we would still have few weeks to finish our tooling, stabilize & test everything, and get ready for integration. These dates also fit best vacation schedules and other constrains of people involved. At the same time, there will be still some days before the M4 release. Our goal is actually to accomplish everything on the list on Wednesday July 31 already. Think of the remaining two days as a reserve in case of unforeseen problems (build service trouble, conflicting upstream changes, etc.). So, what do you think? ----- [1] http://lists.opensuse.org/opensuse-factory/2013-07/msg00265.html [2] http://lists.opensuse.org/yast-devel/2013-05/msg00040.html -- David Majda SUSE Studio developer http://susestudio.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