February 2013 - YaST Development - openSUSE Mailing Lists

[yast-devel] WFM and other languages
by Josef Reidinger 05 Feb '13

05 Feb '13

Hi, as part of my improvements to ruby bindings and ruby usability for YaST I create script for starting clients code. But clients code can be run also via WFM and it is problem. Now it is hardcoded there, that it must be ycp - https://github.com/yast/yast-core/blob/master/wfm/src/Y2CCWFM.cc#L65 I think it would be nice to change it and it is also required if we want to have complete module in ruby that play nice with ycp modules. My idea is to search also for other suffixes ( now if I know only ruby can call clients, but maybe in future other bindings want to use it also ) and call directly ruby component to call its client that is passed. For this goal it would be nice to enhance PathSearch to detect on its own suffixes, so it can be on one place and not have everywhere try for various suffixes. Also there is one more problem in yast2 script. It pass only client name without suffix, so it is hard to decide in script itself if client is ruby or ycp. Is there any way how to detect it in yast script? Or how to use PathSearch from shell ( of course with passed '-I' parameters ) Thanks for answer 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] possible bug report: snapper dumps core
by carsten＠ags.tu-bs.de 05 Feb '13

05 Feb '13

Hey, I'm running snapper on Arch Linux, using lvm thin provisioning for the snapshots. It seems to be working fine (I can create, mount, delete,... snapshots). However, after a command completes, some boost thread seems to die: [system log excerpt] Feb 05 06:41:49 mammoth dbus-daemon[477]: dbus[477]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper) Feb 05 06:41:49 mammoth dbus[477]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper) Feb 05 06:41:49 mammoth dbus-daemon[477]: dbus[477]: [system] Successfully activated service 'org.opensuse.Snapper' Feb 05 06:41:49 mammoth dbus[477]: [system] Successfully activated service 'org.opensuse.Snapper' Feb 05 06:41:50 mammoth dbus-daemon[477]: terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::thread Feb 05 06:41:50 mammoth dbus-daemon[477]: what(): boost thread: thread not joinable: Invalid argument Feb 05 06:41:50 mammoth systemd-coredump[573]: Process 570 (snapperd) dumped core. mammoth ~ # pacman -Q snapper-git thin-provisioning-tools-git lvm2-thin dbus boost systemd snapper-git 20130205-1 thin-provisioning-tools-git 20130205-1 lvm2-thin 2.02.98-1 dbus 1.6.8-6 boost 1.52.0-1 systemd 197-4 mammoth ~ # /usr/sbin/snapperd -h usage: snapperd [--options] Options: --stdout, -s Log to stdout. --debug, -d Turn on debugging. terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::thread_resource_error> >' what(): boost thread: thread not joinable: Invalid argument Aborted (core dumped) If this is the wrong place for such a report, or, since it's not suse-related, there is no general interest, please tell me. Otherwise, are there other reports that might help identify the problem? Regards, Carsten Bohnens -- 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] Wrong parts of documentation
by Josef Reidinger 04 Feb '13

04 Feb '13

Hi, during traversing YCP documentation to continue with proper implementation builtins in ruby for ruby bindings, I found that some places are wrong. First think is select builtin. In documentation is that if there is wrong typem it should return default, but in fact it return always nil try mentioned example on your own: select ([1, "two"], 0, "no") -> "no" documentation says "no" but it is nil http://doc.opensuse.org/projects/YaST/openSUSE11.3/tdg/select-list.html Second part is bracket operator, where it missing documentation that it can be used also for terms. http://doc.opensuse.org/projects/YaST/openSUSE11.3/tdg/bracket.html 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] Broken autosubmit to YaST:Head?
by Ladislav Slezak 04 Feb '13

04 Feb '13

Hi all, I noticed that yast2-control-center is broken in YaST:Head, the spec file was missing. I added it manually but after some time the package got resubmitted and the spec file got lost again: https://build.opensuse.org/package/rdiff?linkrev=base&package=yast2-control… Can somebody check the auto submitting code for YaST:Head? It seems that only this single package is affected, the other packages seem to be OK. -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 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 3