February 2012 - YaST Development - openSUSE Mailing Lists

[yast-devel] YaST2 LDAP and scripts
by Günther J. Niederwimmer 21 Feb '12

21 Feb '12

Hello, Is it possible to find a DOC or a LINK, to find out which Schema and Index the YaST2 Modules and scripts must have? Background: When I like to Install a separate LDAP Server (XEN) and configure other XEN Instances with LDAP support the changes are never written to the LDAP Server. Afterward I found only in the Logs the Error, Index missing or a Error Schema missing usw. When a doc exist it is possible to configure the LDAP server before installing a other XEN Instance? Thanks for the Help, -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

5 11

[yast-devel] Re: [yast-commit] r67465 - in /trunk/nfs-client: package/yast2-nfs-client.changes src/Nfs.ycp src/ui.ycp
by Josef Reidinger 20 Feb '12

20 Feb '12

On Thu, 16 Feb 2012 13:22:20 -0000 mfilka(a)svn2.opensuse.org wrote: > Author: mfilka > Date: Thu Feb 16 14:22:19 2012 > New Revision: 67465 > > URL: http://svn.opensuse.org/viewcvs/yast?rev=67465&view=rev > Log: > > removed some dead code, whitespaces Great, don't hesitate to move out all garbage you found ;) Just I recommend to separate removing dead code and whispaces changes to different commit, so it will be easier to detect. For whitespace correction I recommend indent tool, which can take it in one round. Josef P.S. If you find indentation rules strange, then you are not alone. -- Josef Reidinger Software Engineer Appliance Department SUSE LINUX, s. r. o. Lihovarska 1060/12 190 00 Praha 9 Czech Republic jreidinger(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

4 6

[yast-devel] It's time to switch to GitHub
by Lukas Ocilka 17 Feb '12

17 Feb '12

Hi, As SP2 is not blocking us anymore, it's now time to switch from SVN to GitHub as we've decided earlier in 2011. I know there were some issues with importing all the history but I don't have enough details on which pieces were missing. Maybe not everything is actually needed. Let's focus on finishing the transition now, please. Thanks && Bye Lukas -- Lukas Ocilka, Appliances 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 2

[yast-devel] y2dir ?
by Per Jessen 16 Feb '12

16 Feb '12

I'm trying to use Y2DIR to temporarily fix an iscsi issue during installation, but I simply cannot get it to work. As far as I can tell from /var/log/yast2/y2log, my Y2DIR setting is being ignored. I've tried starting yast: a) Y2DIR=/my2 yast b) export Y2DIR=/my2 yast In /my2 I have the following: # ls -l /my2 total 120 -rw-r--r-- 1 root root 87067 Feb 15 06:49 IscsiClientLib.ybc -rw-r--r-- 1 root root 28721 Feb 15 06:49 IscsiClientLib.ycp I _know_ I had this working last year before Christmas, so it has to be something stupid, but I just cannot see it. /Per Jessen, Zürich -- 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] Ruby-bindings and exception
by Josef Reidinger 15 Feb '12

15 Feb '12

Hi YaST hackers, there is problem with exceptions from ruby modules. Now if risen, yast crash. I found this behavior quite annoying and it should be improved. I can do it, question is what is correct behavior. Does anyone have suggestion? In yast++ we have now error variable and catch exceptions. So I can in ruby bindings ( and only in bindings so ruby code is not affected ) extend class by method that return message of last exception. So you can run code as if (Module::run == nil) y2error ("Problem with run %1",Module.yast_error); I welcome any other suggestions or comments. Also it would be nice to have uniform way....how python bindings solve such problem? And how connection to C++ code behave? Thanks for attention Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

5 12

[yast-devel] YaST++ isn't YaST but ...
by Lukas Ocilka 13 Feb '12

13 Feb '12

Hi, Today we had a talk about the future of YaST++ #1 project and we've found out that maybe "YaST++" isn't actually the best name. Why? Because the project should NOT replace the whole YaST. It's just a configuration library written in Ruby that can be used from several other applications (and YaST is only one of them). Additionally, it's a bit uneasy to find YaST++ project as it usually finds YaST instead. RPM/gem names look strange with "++" in it, etc. So, I'd like to ask you for your feedback on the project name. Do you feel it's appropriate? Do you have any better idea for a project code/name? Thanks in advance Lukas #1 https://github.com/yast/yast--/wiki -- Lukas Ocilka, Appliances 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

1 0

[yast-devel] Re: [yast-commit] r67377 - in /trunk/nfs-client: VERSION package/yast2-nfs-client.changes src/ui.ycp
by Josef Reidinger 08 Feb '12

08 Feb '12

On Wed, 08 Feb 2012 12:03:58 -0000 mfilka(a)svn2.opensuse.org wrote: > Author: mfilka > Date: Wed Feb 8 13:03:57 2012 > New Revision: 67377 > > URL: http://svn.opensuse.org/viewcvs/yast?rev=67377&view=rev > Log: > Base server hostname combobox on existing values - bnc#547983 Hi, congratulate to your first patch. I review your commit and have just small notes: > > snipped > > Modified: trunk/nfs-client/src/ui.ycp > URL: http://svn.opensuse.org/viewcvs/yast/trunk/nfs-client/src/ui.ycp?rev=67377&… > ============================================================================== > --- trunk/nfs-client/src/ui.ycp (original) > +++ trunk/nfs-client/src/ui.ycp Wed Feb 8 13:03:57 2012 > @@ -58,6 +58,11 @@ > list<string> hosts = nil; > > /** > + * List of already defined nfs mount points Well, comment is not precise. If you want list of already defined nfs entries, it is exactly Nfs::nfs_entries. This variable store new state of nfs_entries ( so you have old one in Nfs and this variable store modified list by user and when user decide it is stored ). > + */ > + list< map <string,any> > nfs_entries = Nfs::nfs_entries; > + > + /** > * Let the user choose one of a list of items > * @param title selectionbox title > * @param items a list of items > @@ -178,6 +183,7 @@ > `Bottom (button) > ); > } > + > /** > * Ask user for an entry. > * @param fstab_ent $["spec": "file": "mntops":] or nil > @@ -213,6 +219,21 @@ > servers = [ proposed_server ]; > } > > + // append already defined servers - bug #547983 good to have such comment, it really helps when WTF raised :) > + foreach( map nfs_entry, nfs_entries, > + { > + term couple = SpecToServPath( nfs_entry[ "spec"]:""); > + string known_server = ""; > + > + known_server = couple[0]:""; It is confusing to have multiple lines without intention. simple: string known_server couple[0]:""; is enough in this case. Otherwise good commit. Josef > snipped -- 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: YaST-- review
by Jiri Suchomel 07 Feb '12

07 Feb '12

Dne Pá 3. února 2012 18:59:56, Josef Reidinger napsal(a): > On Fri, 03 Feb 2012 17:46:50 +0100 > > "Duncan Mac-Vicar P." <dmacvicar(a)suse.de> wrote: > > Some stuff that caught my attention, not necessarily bad or good: > > From our WebYaST experience, we have to make it attractive to > > > > non-SUSE developers to try and play with our stuff. The ruby > > eco-system is much bigger and can be leveraged to other usages and > > distributions. > > > > However, the source tree still look a bit "SUSEish": > > - Centered around rpm and not around gems (I would generate the spec > > from gemspecs) I'm not sure what would be the gain. As mentioned, dbus and polkit stuff needs to be packaged, but when you run yast++ as root, these are not needed. But there are package requirements for the config agents (the lower layer) as well: the 'script agents' are running scripts that are mostly part of external packages, that need to be installed. Jiri -- Jiri Suchomel SUSE LINUX, s.r.o. e-mail: jsuchome(a)suse.cz 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

1 0

[yast-devel] 11.4 build of Yast2 failures?
by Marc Chamberlin 01 Feb '12

01 Feb '12

Hi, In order for me to try and grok the YaST bootloader setup module, I thought I would try and download the source code for YaST and compile it on my openSuSE11.4 x86_64 system. Then perhaps I can instrument the code in order to understand the model of the bootloader that YaST presents... (and yes, I have asked before for help on understanding the model, and not gotten any useful replies, just sympathy from others who like me do not have a clue what the various settings will do either.. And yes, I understand GRUB, and the GNU documentation, but the openSuSE model and the bootloader GUI remains incomprehensible to me...) I followed the instructions found at http://en.opensuse.org/openSUSE:YaST_development and one of the things these instructions did was to refer me to another tutorial - http://en.opensuse.org/openSUSE:YaST_tutorials_development_in_general which indicated that I needed to be sure to install a number of additional packages. I carefully tried to install the listed packages, but a number (shown below) were missing - gettext-devel gtk-devel there is a gtk2-devel package installed on my system. Equivalent? liby2util-devel openssl-devel there is a libopenssl-devel package installed on my system. Equivalent? pkgconfig there is a pkg-config package installed on my system. Equivalent? I dunno what to do about that, so decided to punt and go on. (Anyone got any ideas on how I should locate these packages?) Anywise, I downloaded the YaST source from the SVN (but not from trunk) using the following command - svn co http://svn.opensuse.org/svn/yast/branches/SuSE-Linux-11_4-Branch/ which I guessed would get me the source code for the version of YaST2 that was installed in my system. The checkout proceed fine, as did the three make commands to build and install YaST2. But when I got to the step - y2tool y2makeall I got a number of errors as shown below (steps not shown appeared to build properly without errors) These may be related to the fact that I was unable to find and install all the required packages, so if that is the case, then I need to understand how to find and install those packages. Thanks in advance for helping me with this... Marc... Errors from the automatic compile of all of YaST...... Building storage make -f Makefile.cvs make ERROR: 'make -j8 ' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/storage Building registration make -f Makefile.cvs make ERROR: 'make -j8 ' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/registration Building sound make -f Makefile.cvs make ERROR: 'make -j8 ' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/sound Building schema make -f Makefile.cvs make ERROR: 'make -j8 ' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/schema Building openwsman-yast make -f Makefile.cvs ERROR: 'make -f Makefile.cvs' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/openwsman-yast Building boot-server make -f Makefile.cvs make /usr/bin/sudo make install ERROR: '/usr/bin/sudo make install' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/boot-server Building cim make -f Makefile.cvs ERROR: 'make -f Makefile.cvs' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/cim Building heartbeat make -f Makefile.cvs make /usr/bin/sudo make install ERROR: '/usr/bin/sudo make install' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/heartbeat Building qt-graph (cmake based) make -f Makefile.cvs cd qt-graph/build make ERROR: 'make -j8 ' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/qt-graph Building ruby-bindings (cmake based) make -f Makefile.cvs ERROR: 'make -f Makefile.cvs' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/ruby-bindings cd ruby-bindings/build Building slide-show make -f Makefile.cvs ERROR: 'make -f Makefile.cvs' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/slide-show Building you-server make -f Makefile.cvs make /usr/bin/sudo make install ERROR: '/usr/bin/sudo make install' failed for /home/marc/yast2/SuSE-Linux-11_4-Branch/you-server y2makeall summary: Success in 103 directories Failure in 12 directories: storage (base package) registration (base package) sound (base package) schema (base package) openwsman-yast boot-server cim heartbeat qt-graph ruby-bindings slide-show you-server -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 2