March 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] How to get info from failed test (old-style)
by Lukas Ocilka 31 Mar '14

31 Mar '14

Hi, I've started getting exit code 16 when running SuSEFirewall test and was not able to find out where the problem is, as logs did not contain anything. I've found out how to run the test manually and get all the logs... This all the info `make check` gives me: Running ./yast2.test/testsuite.exp ... Checking started Running SuSEFirewall ... FAIL: Test case failed for SuSEFirewall: Return code: '16'. child process exited abnormally And here's what I needed to run to get all the logs: `cd yast-yast2/library/network/testsuite` `/usr/lib/YaST2/bin/y2base -l - -c /usr/share/YaST2/data/testsuite/log.conf -I ../src -M ../src tests/SuSEFirewall.rb UI` Then I've got everything including the error and its backtrace Client call failed with 'undefined method `[]' for nil:NilClass' and backtrace ["/usr/share/YaST2/lib/yast2/systemd_unit.rb:143:in `block in extract_properties'", ...] Internal error. Please report a bug report with logs. Details: undefined method `[]' for nil:NilClass Caller: /usr/share/YaST2/lib/yast2/systemd_unit.rb:143:in `block in extract_properties' I hope this will be helpful Thanks to Josef for hints Bye Lukas -- Lukas Ocilka, Yast TL, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- 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] y2m use cases
by Roman Neuhauser 28 Mar '14

28 Mar '14

hello, i've started dabbling in yast-meta (y2m), and i'm curious how much of it i can remove without stepping on anyone's toes. :) * do you use y2m? * if you don't, why? * if you do, how? * do you have multiple checkouts? how do you workaround y2m's nominal non-support for this? * do you have different subsets of repositories in different checkouts? * do you use the FAV feature? how? also: * do you have some use cases y2m does not support? what would be welcome additions? and: * do we need y2m at all? maybe a bunch of submodules or subtrees in yast-meta would work even better? -- roman -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

5 14

[yast-devel] Confusing text to translate yast module bootloader
by Freek de Kruijf 28 Mar '14

28 Mar '14

I found the text below from the bootloader module to translate. Do not install bootcode into "/" partition (<a href="enable_boot_root ">do not install</a> The "enable_boot_root" does not match with "do not install". This is apparently a message showing a status that the bootcode will not be installed into the "/" partition. By clicking the text in the link, this status should be reverted. But the text "do not install" is not reverting the status, where "enable_boot_root" is. -- fr.gr. member openSUSE Freek de Kruijf -- 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] Pending Pull Requests
by yast-ci＠opensuse.org 27 Mar '14

27 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-bootloader: - Install grub2 into boot_prep device (14 days) https://github.com/yast/yast-bootloader/pull/54 -- 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] Using ERB templates for RichText in Yast
by Ladislav Slezak 26 Mar '14

26 Mar '14

Hi, I was adding AutoYast support to the registration module and found a nice improvement for creating RichText messages. The current approach is using the Summary module, so for displaying the overview of the current AutoYast configuration I used code like this: summary = "" summary = Summary.AddHeader(summary, _("Registration Settings")) summary = Summary.OpenList(summary) summary = Summary.AddListItem(summary, _("Email: %s") % @config.email) summary = Summary.CloseList(summary) This does not look nice. Then I realized that RichText content is actually an HTML subset. And for rendering HTML Ruby has a native support: ERB templates. They are used in Ruby on Rails for rendering web pages so it should work for Yast RichText as well. I found out that it is actually very easy to use ERB, just create the summary using ERB template like for any other RoR application: summary.erb: <h3><%= _("Registration Settings") %></h3> <ul> <li><%= _("Email: %s") % h((a)config.email) %></li> </ul> This looks much better! (Notice the h() method for escaping <>& characters in the value!) Then simply render it when needed: erb = ERB.new(File.read("summary.erb")) # render the ERB template in the context of the current object # i.e. the @config attribute is accessible for the ERB renderer summary = erb.result(binding) And that's it! I have added support for *.erb files in the latest y2makepot so even the translatable strings from *.erb files are correctly extracted to POT files. Note: real code needs a small trick with specifying the textdomain for y2makepot, see the full change in yast2-registration [1]. Enjoy! [1] https://github.com/yast/yast-registration/pull/30/files -- 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 26 Mar '14

26 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-autoinstallation: - add README.md for test_xml directory (14 days) https://github.com/yast/yast-autoinstallation/pull/37 Pending requests in repository yast-bootloader: - Install grub2 into boot_prep device (13 days) https://github.com/yast/yast-bootloader/pull/54 Pending requests in repository yast-control-center: - Move away from deprecated macros, and use imported targets instead (13 days) https://github.com/yast/yast-control-center/pull/8 Pending requests in repository yast-dns-server: - Splitting TXT and SPF records longer than 255 chars into more strings (12 days) https://github.com/yast/yast-dns-server/pull/29 Pending requests in repository yast-metapackage: - fix fail message on sle (21 days) https://github.com/yast/yast-metapackage/pull/2 Pending requests in repository yast-network: - Fixed internal error raised when cloning config in AY moduleb (14 days) https://github.com/yast/yast-network/pull/168 Pending requests in repository yast-online-update-configuration: - rerun zypper if it returns 103 (6 days) https://github.com/yast/yast-online-update-configuration/pull/4 Pending requests in repository yast-registration: - Travis integration (14 days) https://github.com/yast/yast-registration/pull/25 Pending requests in repository yast-vm: - We should use patterns to install all required virtualization packages. (7 days) https://github.com/yast/yast-vm/pull/3 -- 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: added Popup.Feedback()
by Ladislav Slezak 25 Mar '14

25 Mar '14

Hi all, I have added new method Popup.Feedback() to yast2-3.1.26 (see details in https://github.com/yast/yast-yast2/pull/194) Basically it's a safe wrapper around ShowFeedback() and ClearFeedback(), it uses "ensure" block, the popup is automatically closed at the end (even when an exception is raised in the code). So instead of Popup.ShowFeedback("loading FOO", "please wait...") sleep 10 Popup.ClearFeedback use Popup.Feedback("loading FOO", "please wait...") do sleep 10 end Enjoy! -- 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 25 Mar '14

25 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-autoinstallation: - add README.md for test_xml directory (13 days) https://github.com/yast/yast-autoinstallation/pull/37 Pending requests in repository yast-bootloader: - Install grub2 into boot_prep device (12 days) https://github.com/yast/yast-bootloader/pull/54 Pending requests in repository yast-control-center: - Move away from deprecated macros, and use imported targets instead (12 days) https://github.com/yast/yast-control-center/pull/8 Pending requests in repository yast-dns-server: - Splitting TXT and SPF records longer than 255 chars into more strings (11 days) https://github.com/yast/yast-dns-server/pull/29 Pending requests in repository yast-metapackage: - fix fail message on sle (20 days) https://github.com/yast/yast-metapackage/pull/2 Pending requests in repository yast-network: - Fixed internal error raised when cloning config in AY moduleb (13 days) https://github.com/yast/yast-network/pull/168 Pending requests in repository yast-registration: - Travis integration (13 days) https://github.com/yast/yast-registration/pull/25 Pending requests in repository yast-vm: - We should use patterns to install all required virtualization packages. (6 days) https://github.com/yast/yast-vm/pull/3 -- 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] Re: yast2-samba-client packaging
by Jiri Suchomel 24 Mar '14

24 Mar '14

Hi David, sorry for late reply: I replied to wrong address and my mail wasn't delivered. Find it below. Jiri Dne St 19. března 2014 18:19:18, Jiri Suchomel napsal(a): > Dne St 19. března 2014 17:50:21, David Disseldorp napsal(a): > > Hi Jiri, > > > > I've submitted a yast2-samba-client fix for bnc#869185 upstream, and > > now plan to submit the fix for 11SP3 maintenance. > > > > It appears that the normal process is to just tag a new release in the > > changelog and then generate a corresponding tarball. > > > > Is there a "blessed" way of doing this, or should I just use git, e.g. > > git archive --format=tar --prefix=yast2-samba-client-2.17.28/ <commit> \ > > > > | bzip2 > yast2-samba-client-2.17.28.tar.bz2 > > Hi David, > the way I was doing it was: > > - checkout SP3 branch of yast module from git > - generate tarball using 'make package-local' target (there might have been > some changes recently in this point, because rake is used now; but it should > not affect SP3 branch AFAIK) > - upload it to my IBS project and let it build for SP3 build target > - if build succedes, create submit request to appropriate Update:Test > project > > In general, if you have any YaST related questions, you can ask on mailing > list (yast-devel) or public IRC channel (#yast). > > > Cheers, David > > Jiri -- Jiri Suchomel SUSE LINUX, s.r.o. Lihovarská 1060/12 tel: +420 284 028 960 190 00 Praha 9, Czech Republic http://www.suse.cz -- 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] Pending Pull Requests
by yast-ci＠opensuse.org 24 Mar '14

24 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-autoinstallation: - add README.md for test_xml directory (12 days) https://github.com/yast/yast-autoinstallation/pull/37 Pending requests in repository yast-bootloader: - Install grub2 into boot_prep device (11 days) https://github.com/yast/yast-bootloader/pull/54 Pending requests in repository yast-control-center: - Move away from deprecated macros, and use imported targets instead (11 days) https://github.com/yast/yast-control-center/pull/8 Pending requests in repository yast-dns-server: - Splitting TXT and SPF records longer than 255 chars into more strings (10 days) https://github.com/yast/yast-dns-server/pull/29 Pending requests in repository yast-metapackage: - fix fail message on sle (19 days) https://github.com/yast/yast-metapackage/pull/2 Pending requests in repository yast-network: - Fixed internal error raised when cloning config in AY moduleb (12 days) https://github.com/yast/yast-network/pull/168 Pending requests in repository yast-registration: - Travis integration (12 days) https://github.com/yast/yast-registration/pull/25 -- 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] systemd & installation
by Steffen Winterfeldt 21 Mar '14

21 Mar '14

As in the foreseeable future there will be no systemd running during installation (systemd does not work for PID != 1) and the old init.d scripts are gone I've added a 'service_start' script to the installation system. So, if you really have to start service 'foo' for some reason, try 'service_start foo'. It's far from perfect but I hope it works at least for the most common services. Steffen -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

4 7

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

21 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-autoinstallation: - add README.md for test_xml directory (9 days) https://github.com/yast/yast-autoinstallation/pull/37 Pending requests in repository yast-bootloader: - Install grub2 into boot_prep device (8 days) https://github.com/yast/yast-bootloader/pull/54 Pending requests in repository yast-control-center: - Move away from deprecated macros, and use imported targets instead (8 days) https://github.com/yast/yast-control-center/pull/8 Pending requests in repository yast-dns-server: - Splitting TXT and SPF records longer than 255 chars into more strings (7 days) https://github.com/yast/yast-dns-server/pull/29 Pending requests in repository yast-metapackage: - fix fail message on sle (16 days) https://github.com/yast/yast-metapackage/pull/2 Pending requests in repository yast-network: - Fixed internal error raised when cloning config in AY moduleb (9 days) https://github.com/yast/yast-network/pull/168 Pending requests in repository yast-registration: - Travis integration (9 days) https://github.com/yast/yast-registration/pull/25 -- 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 20 Mar '14

20 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-autoinstallation: - add README.md for test_xml directory (8 days) https://github.com/yast/yast-autoinstallation/pull/37 Pending requests in repository yast-bootloader: - Install grub2 into boot_prep device (7 days) https://github.com/yast/yast-bootloader/pull/54 Pending requests in repository yast-control-center: - Move away from deprecated macros, and use imported targets instead (7 days) https://github.com/yast/yast-control-center/pull/8 Pending requests in repository yast-dns-server: - Splitting TXT and SPF records longer than 255 chars into more strings (6 days) https://github.com/yast/yast-dns-server/pull/29 Pending requests in repository yast-metapackage: - fix fail message on sle (15 days) https://github.com/yast/yast-metapackage/pull/2 Pending requests in repository yast-network: - Fixed internal error raised when cloning config in AY moduleb (8 days) https://github.com/yast/yast-network/pull/168 Pending requests in repository yast-registration: - Travis integration (8 days) https://github.com/yast/yast-registration/pull/25 -- 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] Disable InputField on the run
by Julian Zwickl 19 Mar '14

19 Mar '14

Hey Guys, I have a question. Is it possible to disable InputFields on the run? I want to click on a checkbox and then the InputField should be disabled. The CheckBox and the InputField are placed on a DumbTab widget. I queried the status of the CheckBox with UI.Querywidget, this works for me. Then i tried to dis-/enable the InputField with UI.ChangeWidget but it still doesn't work. Did you have a good example? Maybe you can take a look( http://pastebin.suse.de/9388) Regards, Julian -- 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] Pending Pull Requests
by yast-ci＠opensuse.org 19 Mar '14

19 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-autoinstallation: - add README.md for test_xml directory (7 days) https://github.com/yast/yast-autoinstallation/pull/37 Pending requests in repository yast-bootloader: - Install grub2 into boot_prep device (6 days) https://github.com/yast/yast-bootloader/pull/54 Pending requests in repository yast-control-center: - Move away from deprecated macros, and use imported targets instead (6 days) https://github.com/yast/yast-control-center/pull/8 Pending requests in repository yast-dns-server: - Splitting TXT and SPF records longer than 255 chars into more strings (5 days) https://github.com/yast/yast-dns-server/pull/29 Pending requests in repository yast-metapackage: - fix fail message on sle (14 days) https://github.com/yast/yast-metapackage/pull/2 Pending requests in repository yast-network: - Fixed internal error raised when cloning config in AY moduleb (7 days) https://github.com/yast/yast-network/pull/168 Pending requests in repository yast-registration: - Travis integration (7 days) https://github.com/yast/yast-registration/pull/25 -- 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 18 Mar '14

18 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-autoinstallation: - add README.md for test_xml directory (6 days) https://github.com/yast/yast-autoinstallation/pull/37 Pending requests in repository yast-metapackage: - fix fail message on sle (13 days) https://github.com/yast/yast-metapackage/pull/2 Pending requests in repository yast-network: - Fixed internal error raised when cloning config in AY moduleb (6 days) https://github.com/yast/yast-network/pull/168 Pending requests in repository yast-registration: - Travis integration (6 days) https://github.com/yast/yast-registration/pull/25 -- 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 17 Mar '14

17 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 (12 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] rpmlint warnings
by Martin Vidner 14 Mar '14

14 Mar '14

Hi, an openSUSE reviewer has just dropped by to remind us that our packages produce too many rpmlint warnings. In particular, here: https://build.opensuse.org/package/live_build_log/YaST:Head/yast2/openSUSE_… for this SR https://build.opensuse.org/request/show/224596 Please check the lists below for the worst cases and fix them when you're tired of SLE bugs ;-) $ osc ls YaST:Head > packages $ for i in `cat packages`; do echo $i osc remotebuildlog --last YaST:Head $i openSUSE_Factory x86_64 > $i.log done ERRORS: $ grep [1-9].errors *.log kupdateapplet.log:[ 132s] 4 packages and 0 specfiles checked; 3 errors, 19 warnings. libstorage.log:[ 1027s] 6 packages and 0 specfiles checked; 1 errors, 13 warnings. libyui.log:[ 95s] 3 packages and 0 specfiles checked; 1 errors, 3 warnings. skelcd-control-openSUSE-LangAddOn.log:[ 46s] 2 packages and 0 specfiles checked; 2 errors, 3 warnings. yast2-branding-openSUSE.log:[ 62s] 2 packages and 0 specfiles checked; 2 errors, 10 warnings. yast2-devtools.log:[ 29s] 3 packages and 0 specfiles checked; 1 errors, 4 warnings. yast2-hardware-detection.log:[ 117s] 2 packages and 0 specfiles checked; 1 errors, 8 warnings. yast2-ldap.log:[ 124s] 2 packages and 0 specfiles checked; 1 errors, 8 warnings. yast2-perl-bindings.log:[ 172s] 2 packages and 0 specfiles checked; 2 errors, 4 warnings. yast2-pkg-bindings.log:[ 353s] 2 packages and 0 specfiles checked; 1 errors, 2 warnings. yast2-python-bindings.log:[ 144s] 2 packages and 0 specfiles checked; 4 errors, 4 warnings. yast2-slide-show.log:[ 127s] 4 packages and 0 specfiles checked; 1 errors, 31 warnings. yast2-slp.log:[ 148s] 2 packages and 0 specfiles checked; 1 errors, 6 warnings. yast2-snapper.log:[ 214s] 2 packages and 0 specfiles checked; 1 errors, 11 warnings. yast2-squid.log:[ 108s] 2 packages and 0 specfiles checked; 1 errors, 7 warnings. WARNINGS, 10 and more: $ grep warnings\\. *.log | sort -t, -k2 -n ... yast2-branding-openSUSE.log:[ 62s] 2 packages and 0 specfiles checked; 2 errors, 10 warnings. yast2-online-update.log:[ 115s] 3 packages and 0 specfiles checked; 0 errors, 10 warnings. yast2-all-packages.log:[ 45s] 2 packages and 0 specfiles checked; 0 errors, 11 warnings. yast2-metapackage-handler.log:[ 64s] 2 packages and 0 specfiles checked; 0 errors, 11 warnings. yast2-nis-client.log:[ 115s] 3 packages and 0 specfiles checked; 0 errors, 11 warnings. yast2-snapper.log:[ 214s] 2 packages and 0 specfiles checked; 1 errors, 11 warnings. yast2-storage.log:[ 170s] 3 packages and 0 specfiles checked; 0 errors, 11 warnings. yast2-sysconfig.log:[ 94s] 3 packages and 0 specfiles checked; 0 errors, 12 warnings. libstorage.log:[ 1027s] 6 packages and 0 specfiles checked; 1 errors, 13 warnings. yast2-mail.log:[ 190s] 2 packages and 0 specfiles checked; 0 errors, 13 warnings. autoyast2.log:[ 91s] 3 packages and 0 specfiles checked; 0 errors, 14 warnings. yast2-trans-stats.log:[ 61s] 2 packages and 0 specfiles checked; 0 errors, 14 warnings. yast2-core.log:[ 315s] 4 packages and 0 specfiles checked; 0 errors, 16 warnings. yast2-apparmor.log:[ 73s] 2 packages and 0 specfiles checked; 0 errors, 17 warnings. yast2-packager.log:[ 140s] 3 packages and 0 specfiles checked; 0 errors, 18 warnings. kupdateapplet.log:[ 132s] 4 packages and 0 specfiles checked; 3 errors, 19 warnings. yast2-bootloader.log:[ 93s] 3 packages and 0 specfiles checked; 0 errors, 21 warnings. yast2-country.log:[ 138s] 3 packages and 0 specfiles checked; 0 errors, 26 warnings. yast2-sound.log:[ 113s] 3 packages and 0 specfiles checked; 0 errors, 26 warnings. yast2-slide-show.log:[ 127s] 4 packages and 0 specfiles checked; 1 errors, 31 warnings. yast2.log:[ 620s] 3 packages and 0 specfiles checked; 0 errors, 39 warnings. yast2-trans.log:[ 1163s] 74 packages and 0 specfiles checked; 0 errors, 215 warnings. rubygem-gettext.log:[ 87s] 4 packages and 0 specfiles checked; 0 errors, 360 warnings. -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

2 1

[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

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

05 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-theme: - updated installer styles (4 days) https://github.com/yast/yast-theme/pull/18 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0