June 2009 - YaST Development - openSUSE Mailing Lists

[yast-devel] WebYaST daily status call 2009-Jun-25
by Klaus Kaempf 25 Jun '09

25 Jun '09

WebYaST daily status call 2009-Jun-25 bgeuken, mvidner, mzugec, visnov, kkaempf, jsrain, jreidinger, schubi, mschmidkunz bgeuken: Looked into start (status) page Next: status module mvidner: fix passing empty hash in bindings mzugec: - bugzilla - Next: more learning visnov: got information on requirements for initial launch Next: requirements kkaempf: Requirements gathering Next: test cases jsrain: - no update - jreidinger: released language module rails ajax and jQuery conflict -> move to ruby-devel list Next: more testcase schubi: jQuery tree widget for permissions mschmidkunz: teamed up with bgeuken layout of configuration module selector Next tasks Everyone: Focus on test cases for existing code before writing new code ! -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] Per-plugin code coverage analysis enabled for rest-service
by Klaus Kaempf 25 Jun '09

25 Jun '09

Hi, all plugins below rest-service/plugins can now use the rails_rcov extension from rest-service/webservice. Just go to the plugin dir and run "rake test:{units,functionals}:rcov" i.e. cd rest-service/plugins/time rake test:units:rcov rake test:functionals:rcov and clean up with rake test:units:clobber_rcov rake test:functionals:clobber_rcov Enjoy ! Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] WebYaST daily status call 2009-Jun-24
by Klaus Kaempf 24 Jun '09

24 Jun '09

WebYaST daily status call 2009-Jun-24 mschmidkunz, bgeuken, mvidner, mzugec, visnov, kkaempf mvidner: pushed to git packaging underway simplyfied services view in the client Next: try to remove caching mzugec: learning about resources, rest, routing Next: more learning bgeuken: Learn CSS Next: work with mschmidkunz to integrate UI proposal into web-client kkaempf: git commits are mailed yast-commit(a)opensuse.org Next: requirements for first milestone mschmidkunz: UI layout and structure Next: work with bgeuken and schubi to integrate with web-client visnov: Milestone approaching for Studio launch Next: Define milestone requirements Everyone (working on rest-service modules): Think about quality standards to go with rest-service modules i.e. : availability of testcases, required code coverage, rpm packaging, etc. -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] Adding special options with Yast Bootloader interface
by Leonardo L. P. da Mata 23 Jun '09

23 Jun '09

Hello, i'm working in a project to build a recover system for OpenSuse using Yast, the idea is to copy the contents of a cd into a partition and then boot from this partition with autoyast to restore the installed system "automagically" . I've wrote code for copying the files and it looks good, but I wish to add a booloader option to boot from this partition, but i don't know how do I add this option using the Bootloader.ycp interface. So, where i can find some examples of dealing with new bootloader options? Is there any file that is read with the default proposal in the normal installation? I'm using OpenSuse 11.1 Thanks in advance. -- Leonardo Luiz Padovani da Mata barroca(a)gmail.com "May the force be with you, always" "Nerd Pride... eu tenho. Voce tem?" -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1

[yast-devel] spec files: Summary, Description, Group and License now in SVN
by Martin Vidner 23 Jun '09

23 Jun '09

Hi, short: update devtools. kthxbye. as the PDB is going to be resting, pining for the fjords, etc. soon, Coolo and I have migrated the data to the .spec.in files in SVN. The catch is that Group and License used to be part of the common @HEADER@ inserted by devtools. If you package with old devtools, you will get this error during build: error: Duplicate License entries in package: (main package) Please use yast2-devtools-2.18.9 for "make package". There is also some magic to ensure that it continues to work with older spec.ins that do not contain the tags. BTW, here are the licenses diferent from "GPL v2 or later". IMHO they are mistakes, except for openwsman which looks intentional. yast2-add-on-creator GPL v2 only GPL v2 or later yast2-cluster GPL v2 only yast2-firstboot GPL v2 or later X11/MIT yast2-gtk LGPL v2.1 or later yast2-gtk-pkg LGPL v2.1 or later yast2-kdump GPL v2 only yast2-ldap-server GPL v2 or later X11/MIT openwsman-yast BSD 3-Clause yast2-python-bindings GPL v2 only yast2-reipl GPL v2 only GPL v2 or later yast2-squid GPL v2 only -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] WebYaST status call 2009-Jun-23
by Klaus Kaempf 23 Jun '09

23 Jun '09

WebYaST daily status call 2009-Jun-23 mvidner, mzugec, schubi, kkaempf, bgeuken, jsrain, jreidinger mvidner: service plugin works (kindof) Next: push code to git repo Discuss caching on mailing list mzugec: Pushed network module to git repo Next: learning about resources, rest, routing schubi: permission client jQuery Next: more jQuery kkaempf: got html layout for status page from mschmidkunz, handover to bgeuken Next: Forward git commits to yast-commit(a)opensuse.org bgeuken: Learn CSS jsrain: No updates jreidinger: yast d-bus update submitted Next: time module use jquery datepicker -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 2

[yast-devel] Minutes of Prague YaST Team Meeting: 2009-06-18
by Martin Vidner 19 Jun '09

19 Jun '09

Minutes of Prague YaST Team Meeting: 2009-06-18 =============================================== http://en.opensuse.org/YaST/Team Present: jkupec, jreidinger, jsuchome, juhliarik, kmachalkova, lslezak, mvidner, mzugec Absent: jsrain, locilka (in NBG) Minutes: mvidner Next Minutes: mzugec WebYaST ======= As we send more complex data between YaST and Ruby via DBus, bugs and missing features turn up (bnc#513503, bnc#513571, bnc#512569) ruby-dbus upstream looks stalled :-/ https://trac.luon.net/ruby-dbus jreidinger: finding bugs lslezak: fixing bugs, adding testsuite Miscellaneous ============= mzugec: struggled to get a machine to test a feature kmachalkova: porting YaST control center to Qt4: better painting jkupec: SMT; http://jniq.blogspot.com/search/label/zypper jsuchome: YOU for LDAP client (bnc#509874) image-creator: correctly set target 32bit arch on x86_64 (bnc#510971) mvidner: automake-1.11 not so cool after all. battling build failures. -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] yast2 firstboot issue ...
by Michael Meeks 19 Jun '09

19 Jun '09

Hi guys, I'm having rather a mare of a time with firstboot - I've switched our Moblin:UI/Image-opensuse image away from SLE11 to base from openSUSE11.1 - and (it seems) in the process much has broken. For example, first-boot's X server no longer responds to any input ;-) this (it transpires) is because neither dbus nor hal are started - and our X server requires these to be there to get input. Who starts dbus and hal at firstboot (from init.d/boot) ? Thanks, Michael. -- michael.meeks(a)novell.com <><, Pseudo Engineer, itinerant idiot -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 2

Re: [yast-devel] yast2 firstboot issue ...
by Michael Meeks 18 Jun '09

18 Jun '09

Hi Stefan, On Thu, 2009-06-18 at 18:45 +0200, Stefan Dirsch wrote: > > > I'm having rather a mare of a time with firstboot - I've switched our > > > Moblin:UI/Image-opensuse image away from SLE11 to base from openSUSE11.1 > > Aren't you talking about openSUSE:Factory here ?!? Nope; Moblin:UI doesn't build for factory yet - yet there are many known bugs in SLE11:GA - and there is no public update channel => we have to base from 11.1 for the public builds: at least, that is my current thinking. Then at least what external people test matches well what we have to support, and indeed - we can use the public update channels to update SLE11 based systems since the £$%"£$%£$%ing firewall makes external partner testing of SLE11 based variants practically impossible. There was also some thought from maintenance that updates for our fastboot work are easier to push to 11.1 than SLE11 since there is less concern wrt. stability. > > In that case hal and dbus are started by the YaST start scripts > (in S06-services). Thanks muchly; will debug that tomorrow. I wonder if it is a side-effect of removing sax2* ;-) Regards, Michael. -- michael.meeks(a)novell.com <><, Pseudo Engineer, itinerant idiot -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] Patched ruby dbus bindings
by Josef Reidinger 18 Jun '09

18 Jun '09

Hi, I submit to Yast:Web repo ruby dbus bindings that contains fix for array of variants ('av' or in ycp it is list<any>). I send the patch also to upstream, but it looks quite dead. So it is question if we want use this binding (I find another 3 ruby dbus bindings, each is without commit more then year)? If yes, then I should write also another useful patches like automatic marshaling of ruby objects to variants (now if you use variant in argument you must use array where first item is signature that specify type and second is variable itself (example of this usage is in samba rails plugin)). With this patch and also with lslezak new core (now it is only in his branch) is possible to send quite complex structures from yast to rails. I successfully send map<string,any> where any in one case is map<string,list<string>> and successfully receive it. Welcome any question JR -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 2