February 2010 - YaST Development - openSUSE Mailing Lists

[yast-devel] Webyast - models in webclient and webservice - summary
by Josef Reidinger 16 Mar '10

16 Mar '10

Hi, because on Friday I finally merge in webclient yast model I create short summary of both models, its features and why you should use it. webservice model: Inspired by ActiveModel. It adds methods for easy validation, serialization, mass loading and callbacks. for example usage see Ntp and time plugins. For documentation see - class BaseModel::Base (I cannot connect to hudson for direct link) why use it? smart to_xml and to_json so you don't need to define own method unless you have hash with problematic keys (see time model for example how to solve it) validations which checks attributes before save same behavior as ActiveRecord and ActiveResource webclient model: Adaptation of ActiveResource to our case of changing site and credentials to target machine. It adds method model_interface which sets interface for model and fix finding single resource. Also helper methods for HttpMock which tests ActiveResource is added. for example usage see Time plugin or network plugin. For documentation see module YastModel::Base example of usage: class Stime < ActiveResource::Base extend YastModel::Base model_interface :'org.opensuse.yast.modules.yapi.time' end why use it? you can add functionality to model, so no more controllers which have more then one page same usage as any ActiveResource model, so new programmer is not confused what we using easier testing (there is still place to improve it), but I found that many plugins doesn't have test or test is really simple and don't cover enough code. for testing see how looks tests in network or time module. Thanks for attention and I welcome any comments, suggestion or bugs ( ..bugs are not so much welcome, but I fix it) Josef -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast (language,time,basesystem,ntp) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 3

[yast-devel] results enable disable survey
by Martin Schmidkunz 02 Mar '10

02 Mar '10

Hi! Please find the results of enable/disable a settings at: http://en.opensuse.org/UX/Enable_Disable_in_webYaST The results show that it is more usable for webYaST to provide additional text providing the current status of a setting. Thanks for your participation! Martin -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

11 19

[yast-devel] WebYaST: javascript per-plugin library
by Michal Zugec 01 Mar '10

01 Mar '10

Hi! I'd like to share my observation: I needed to share my javascript code between two files (it was form validation for new and edit action + some more) I created webyast-users-ui/plugins/users/public/javascripts/users_edit.js and included it into my files with <%= javascript_include_tag "users_edit.js" %> It's important to use $pluginname as prefix to be unique in whole project! That's it ... Bye, Michal -- Best Regards, Michal Zugec Software developer --------------------------------------------------------------------- SuSE CR, s.r.o. e-mail: mzugec(a)suse.cz Lihovarska 1060/12 tel: +420 284 028 960 190 00 Praha 9 fax: +420 296 542 374 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 6

[yast-devel] Pattern and one click install
by Duncan Mac-Vicar Prett 26 Feb '10

26 Feb '10

The repository now has a one-click http://download.opensuse.org/repositories/YaST:/Web/openSUSE_11.2/webyast.y… And also generates a pattern browsable by YaST/zypper for the repository automatically. The pattern/one click can be installed by doing: osc meta pattern YaST:Web webyast -e YaST:Web/openSUSE_11.2 automatically builds on top of YaST:Web:11.2 so if a one click install is clicked in the first, the later repo is automatically included/added. Only problem we have is that we have right now 5 package lists to maintain: - 3 different appliances - addon - pattern/one click Any ideas how to improve here? -- Duncan Mac-Vicar P. - Novell® Making IT Work As One™ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- 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] WebYaST status update, Fre Feb 26nd
by Klaus Kaempf 26 Feb '10

26 Feb '10

present: jsrain, dmacvicar, kkaempf, bbrunner, vgorobets, mvidner, jdsn, jreidinger, mzugec, lslezak, bubli, jsuchome absent: schubi, mschmidkunz, tgoettlicher, mkudlvasr Status ------ Big thanks to Benjamin for his contributions and much fun in his next team ! bbrunner: - moving on (trainee rotation plan) - next: different team jsrain: - released Wiki tutorial - next: non-webyast dmacvicar: - cleaned up buildservice - took care for openSUSE 11.2 build - added pattern and one-click-install - next: review tutorial kkaempf: - non-webyast vgorobets: - worked through tutorial - next: find bugs to fix mvidner: - going through bugs - next: help WebYaST users jdsn: - bug fixing - product creation (update channel) - next: add more exception catchers jreidinger: - working on bugs - next: bug fixing mzugec: - working on bugs - next: users form validation lslezak: - working on bugs - digged into jQuery bug (will write mail about it) - next: caching in repo module - next: fixing more bugs bubli: - fixed UI bugs (spacing and layout) - added class for fieldsets - fixed systemtime UI - next: make buttons more visual attractive jsuchome: - worked on UI related bugs - still working on mail bugs - next: non-webyast work --- 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 tutorial review finished
by Jiri Srain 25 Feb '10

25 Feb '10

Hi! I finished the review of the WebYaST development tutorial, which is available at http://en.opensuse.org/YaST/Web/Development/Tutorial . It should be up-to- date and it should be possible to crete a new WebYaST module following this tutorial. If you find any issues in the document (I don't claim that it is perfect, also it may be just that something is not clear from reading it), please, either report them to me via bzilla or fix them - it's a wiki :-) Jiri -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain(a)suse.cz Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.cz -- 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 update, Thu Feb 25nd
by Klaus Kaempf 25 Feb '10

25 Feb '10

present: jsrain, dmacvicar, kkaempf, schubi, tgoettlicher, mvidner, mzugec, jsuchome, bubli, vgorobets, mkudlvasr absent: bbrunner, mschmidkunz, jdsn, schubi, bbrunner, jreidinger, lslezak Status ------ WebYaST for SLES11 SP1 Beta5 is done, thank you all! This was a much smoother process than with Beta4. Everyone: Please update your bugs and close the fixed ones. jsrain: - worked on wiki (tutorial) - next: wiki dmacvicar: - built service appliance - shortened package list - next: non-webyast schubi: - created SP1 and 11.2 appliances and addons - testing - next: status module bugs tgoettlicher: - testing - next: addon product test - next: vacation & yast2 mvidner: - testing - pushed updates for the 1.0 release - next: leftover bugs mkudlvasr: - testing - firewall module tests - next: fixing bugs jsuchome: - bug fixes - testing 1.1.11 - next: bug fixing mzugec: - testing 1.1.11 - added test cases - next: yast2 bugs - next: bug fixing bubli: - looked through UI related bugs - replaced icons (using 'Tango' icons now) - next: pick UI bugs to fix vgorobets: - learned by reading WebYaST wiki - testing - next: learn more about webyast - next: check with jsrain kkaempf: - testing, testing, and more testing - writing release notes - next: release WebYaST Beta5 - next: go through bug list --- 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] Re: Webyast - roles management
by Josef Reidinger 24 Feb '10

24 Feb '10

> > Hi, > I found a plugin that seems to do what you want. > http://code.google.com/p/rolerequirement/ Thanks for source. I read it, but I think that it give check to much high-level. We have permissions on layer which communicate with dbus as permission is mapped (name of permission is constructed from dbus call) to dbus call > ... and it seems to be maintained. quote from first paragraph: "NOTE: I am no longer maintaining this project. Please see the note on the github page (http://github.com/timcharper/roll_requirement) for more information. Thanks, Tim" :) > > You are talking about roles in the context of web-yast not in > the context of the underlying OS, right? in context of web-yast > Or do you plan to allow web-yast users to change the OS config > by using yast, read/write to system files etc.? Now webyast users = users in OS. But it can change in future. Klaus can give you more information on this topic. > > From a security point of view it is important to have a complete code > coverage of RBAC to avoid bypassing the ACLs by using another interface > (RESTful vs. UI vs. ...) or delegate an automatic and user-defined task > to the web-application which is then executed with the role of the web-app not > with the role of the web-yast user (something equal to a cron job). Because RBAC is just interface and inside it is about distribution permissions, It works like now..users has individual permissions. Just administrator manage it with roles, do not directly touch each permissions. So another interface cannot bypass this permissions. Josef > > Bye > Thomas > > > Am Dienstag 23 Februar 2010 19:02:54 schrieb Josef Reidinger: > > Hi, > > I get this task and I think it is time to little discussion what is > > possible and how it should be done. (how it looks I think is decided - it > > is similar to groups). > > > > Roles is something like mark which grants user set of actions. So e.g. role > > HR admin can add/remove users and edits its details it is one role but it > > contains more permissions. > > > > At first I investigate little how lib/yast_roles.rb work...and it doesn't > > work. I try play with polkit and if you ask for user which doesn't have > > UID it fails. Problem is that roles doesn't have UID. So roles must be > > stored beside. > > > > My proposal how it could work. > > > > We have defined list of roles in one yaml file. owned by yastws, strict > > permissions. This list contain role and its permissions. Then we have > > second list which assign to role its users. > > If user get into role it get permissions of this role. > > If user remove from role all permissions is removed and again all roles is > > applied. If role is modified then all users in this role has removed > > permissions and all roles is again applied (the longest variant but roles > > should change only rare). > > > > So permission module is changed that it act on roles not on users for > > appliance. For non-appliance usage it acts on users. ( I plan create two > > package to easier maintenance). > > > > I welcome any comments, hints or questions > > > > Josef > > > > -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, parts of webyast -- 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] WebYaST status update, Wed Feb 24nd
by Klaus Kaempf 24 Feb '10

24 Feb '10

jsrain, dmacvicar, kkaempf, mschmidkunz, jdsn, schubi, bbrunner, tgoettlicher, mvidner, jreidinger, mkudlvasr, jsuchome, mzugec, lslezak, bubli, vgorobets jsrain - testing 1.1.11 appliance - worked on wiki - next: wiki dmacvicar: - build service appliance - rubygem fixes - next: non-webyast kkaempf: - testing - fixing ruby-dbus mess I introduced - next: testing 1.1.11 appliance, bug prioritization mschmidkunz: - ui work - next: repository module jdsn: - registration bugs schubi: - creating appliances - testing - next: status module bugs bbrunner: - testing - next: testing tgoettlicher: - testing - next: 1.1.11 test mvidner: - testing - next: leftover bugs jreidinger: - testing - rubygems problems - next: bugs mkudlvasr: - fix language module - next: testing, bug fixing jsuchome: - users module fixes - testing 1.1.11 - next: bug fixing mzugec: - testing 1.1.11 - L3 work - next: test coverage improvement in users lslezak: - improved repository test suite - bug fixing - next: bug fixing bubli: - users main screen design - users filters jQuery - next: ui improvements vgorobets: - setting up - build webyast - next: learn more about webyast --- 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 - roles management
by Josef Reidinger 24 Feb '10

24 Feb '10

Hi, I get this task and I think it is time to little discussion what is possible and how it should be done. (how it looks I think is decided - it is similar to groups). Roles is something like mark which grants user set of actions. So e.g. role HR admin can add/remove users and edits its details it is one role but it contains more permissions. At first I investigate little how lib/yast_roles.rb work...and it doesn't work. I try play with polkit and if you ask for user which doesn't have UID it fails. Problem is that roles doesn't have UID. So roles must be stored beside. My proposal how it could work. We have defined list of roles in one yaml file. owned by yastws, strict permissions. This list contain role and its permissions. Then we have second list which assign to role its users. If user get into role it get permissions of this role. If user remove from role all permissions is removed and again all roles is applied. If role is modified then all users in this role has removed permissions and all roles is again applied (the longest variant but roles should change only rare). So permission module is changed that it act on roles not on users for appliance. For non-appliance usage it acts on users. ( I plan create two package to easier maintenance). I welcome any comments, hints or questions Josef -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, parts of webyast -- 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] some packaging debt
by Duncan Mac-Vicar Prett 23 Feb '10

23 Feb '10

I have noticed the following: Our code depends on rubygem-relevance-rcov, which is a package that follows a now obsolete github convention. I have packaged rubygem-rcov. Would it be feasible to replace it for this iteration? Also we have ruby-rpam which is based on http://gitorious.org/opensuse/yast-rest-service/trees/master/rpam It seems now rpam is even released as a gem from its author (Sept 2009). I have packaged it as rubygem-rpam, should we switch to it? Then we have ruby-polkit, which I would also look into make it a rubygem too. But I have no progress here. -- Duncan Mac-Vicar P. - Novell® Making IT Work As One™ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 6

[yast-devel] WebYaST status call - Feb 23
by Jiri Srain 23 Feb '10

23 Feb '10

jsrain, bbrunner, jdsn, tgoettlicher, dmacvicar, schubi, jsuchome, mschmidkunz, mvidner, jreidinger, lslezak, vgorobets jsrain: working on the tutorial, fixing bugs bbrunner: testing 11.2 image jdsn: brought hudson back on-line, testing on registration tgoettlicher: digged into automatic testing dmacvicar: submitted packages changed to gems, prioritizing bugs schubi: tried yast-web running on factory; will build image mschmidkunz: evaluating survey on enabling/disabling concept, will keep on the repo module mvidner: went through bugs, will work on release jreidinger: webservice-base test, reporting bugs, helping with firewall testsuite lslezak: repo mgr testsuite, look at future polkit migration vgorobets: just moved to the team, welcome EVERYONE: submit your packages until 12:00 CET!!!!! EVERYONE: test and send testreport EVERYONE: if you don't have any bug, offer help to others. If you have too many, ask for help early -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain(a)suse.cz Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.cz -- 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] Re: Help needed on how to run shell script as "root" in WebYaST webservice
by Klaus Kaempf 22 Feb '10

22 Feb '10

Hi WebYaSTies, YaST/Web/Development/Tutorial on the openSUSE Wiki is outdated (I just created bnc#579012 to get this fixed) to get this question answered * Hai Shi <HShi(a)novell.com> [Feb 11. 2010 03:22]: > > Do you have any document that I can follow to achieve this: running a shell script as "root" in WebYaST webservice? > Maybe its a good idea to create a set of 'common' D-Bus services for such scenarios ? 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

4 5

[yast-devel] Webyast - How to show details in flash object
by Josef Reidinger 22 Feb '10

22 Feb '10

Hi, we sometime need to show details in flash message. Especially in error. Definition of details is that it should be something which can be hide/show. Question is how to do it. I see two ways: 1) special mark which separate message from details. This mark is then replaced by code we want. example: flash[:error] = "You don't have enough permissions to run this module. Contact administrator if you need it. ===DETAILS=== User #{user} doesn't have permission #{permission}." advantage: - easy to use - you can easy switch way how details is generated - unified way of details disadvantage: - not common in rails world and don't know where to document it 2) allow html elements in flash message. And details write to flash message (maybe some helper for it is possible) example: flash[:error] = "You don't have enough permissions to run this module. Contact administrator if you need it. " + details("User #{user} doesn't have permission #{permission}.") advantage: - easy to use (again :) - you can easy switch way how details is generated disadvantage: - allows all elements in flash message - allows different personal "improvements" which could lead to inconsistent flash messages Any other ideas how to solve it? Which solution do you prefer? I personally prefer solution 2) which is cleaner for me. So if there is no complains or better ideas I use it. Josef -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, parts of webyast -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 4

[yast-devel] Webyast - keep attention what keys in xml you choose
by Josef Reidinger 22 Feb '10

22 Feb '10

Hi, in short: choose as XML key name of webclient model only if you really want to initialize it with values inside this tag. long version: today I debug interesting problem which has Martin Kudlvasr. When he test his firewall model he get cannot load 'org.opensuse.yast.services'. That is quite strange because he doesn't use Service model where is this interface defined. After some work with rdebug I found that it correctly has interface attached to model Firewall, so problem is not in YastModel but I found it load model Service. Why? Firewall use array of services with service as key. ActiveResource has feature(?) which search in ancestors of ActiveResource and tries found if there is class which has name Service. And it has. So it take nested XML and send it to Service initializer. Possible solution of this situation is: 1) use different name for key (quick and easy) 2) really use same structure for data and benefit from nested models 3) enclose deeper xml key, because ARes search in modules if deep of XML element is bigger then 1 (arrays is not counted) Josef -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, parts of webyast -- 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] html validation
by Duncan Mac-Vicar Prett 22 Feb '10

22 Feb '10

I have committed a Rack Middleware to validate the current page. If it does not, it shows a standard webyast error with the problems. It is by default in the development environment, but only if you have rubygem- tidy installed, if not it is disabled. Mandatory screenshot: http://www.suse.de/~dmacvicar//screenshots/webyast/webyast-html- validator-1.png In the future, as it is based on another code from another application, I would like to extract it back from WebYaST into its own rack component, so that we can share it with other projects. Add different validators support, highlight of elements, etc. Now, you can start looking at the repositories and services page to see the validation errors :-) -- Duncan Mac-Vicar P. - Novell® Making IT Work As One™ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- 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] Status update, Mon Feb 22nd
by Klaus Kaempf 22 Feb '10

22 Feb '10

jsrain, dmacvicar, kkaempf, mschmidkunz, jdsn, schubi, bbrunner, tgoettlicher, mvidner, jreidinger, mkudlvasr, jsuchome, mzugec absent: lslezak Goal of the week: Release ! (SP1 Beta5, openSUSE 11.2, openSUSE 11.3) ================ Status ------ jsrain: - no update - next: review tutorial docs dmacvicar: - help 11.2 appliance - html validation - next: coordinate pairs for release mschmidkunz: - services ui - next: repository module jdsn: - fixed registration timeout + error reporting - next: testcases schubi: - built 11.2 appliance, automatically - next: bug fixing bbrunner: - vacation - next: testing + test creation tgoettlicher: - obs autotest - next: pair with Benji on test issues kkaempf: - rlihm - next: release mvidner: - catched up with mails and bugs - next: release jreidinger: - test coverage review - next: review error reporting, esp. show details mkudlvasr: - 11.2 testing - next: test coverage, bug jsuchome: - bug fixing - next: bug fixing - next: mail configuration mzugec: - 11.2 testing - package updates - next: l3 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

Re: [yast-devel] WebYaST initialization got stuck with error: Permission org.opensuse.yast.modules.yapi.administrator.read is not granted for user root
by Hai Shi 19 Feb '10

19 Feb '10

Hi, Josef: I used the webyast respository from: zypper ar http://www.suse.de/~mvidner/webyast-gmc webyast-gmc zypper ar http://www.suse.de/~mvidner/webyast-lighty webyast-lighty yast2-webservice-administrator package version is 0.0.9-0.1.1. There is no "/var/log/zypp/history" file. linux-sdc3:~ # cd /var/log/zypp/ linux-sdc3:/var/log/zypp # ls linux-sdc3:/var/log/zypp # polkit-auth --user root | grep org.opensuse.yast.modules.yapi.administrator.read org.opensuse.yast.modules.yapi.administrator.read linux-sdc3:/var/log/zypp # polkit-auth --user yastws | grep org.opensuse.yast.modules.yapi.administrator.read org.opensuse.yast.modules.yapi.administrator.read Thanks, Hai >>> Josef Reidinger <jreidinger(a)suse.cz> 2/19/2010 3:27 AM >>> Hai Shi write: > Hi, > I am working on include WebYaST in the appliance. I followed the WebYaST vendor's guide: > http://www.novell.com/documentation/webyast/book_webyast_vendor/?page=/docu… > > WebYaST initialization got stuck after accepting the license with error: Permission org.opensuse.yast.modules.yapi.administrator.read is not granted for user root > > The appliance is vmware image and has 2G memory. I used SUSE Sudio Online to build the appliance. > > Thanks, > Hai > Hi, could you please specify what version of webyast-administrator-ws is in appliance? Permissions should be set in post install script so please look also at /var/log/zypp/history where could be some error report. And if you have not edge version it can be also problem with yastws rights. So please try in appliance this two commands which specify which permission really missing: polkit-auth --user root | grep org.opensuse.yast.modules.yapi.administrator.read #if nothing is showed then root doesn't have rights polkit-auth --user yastws | grep org.opensuse.yast.modules.yapi.administrator.read #if nothing is showed then yastws doesn't have rights Thanks -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, parts of webyast -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 1

[yast-devel] Problem with lvm on hardware raid
by Christian Ehrlicher 19 Feb '10

19 Feb '10

Hi, We've a similar problem like described in bug #231221 ( https://bugzilla.novell.com/show_bug.cgi?id=231221 ). Yast can't create a logical volume and fails with error -4017 (LVM_PV_STILL_ADDED) --> /dev/block/104:3 needs a mapping to /dev/cciss/c0d0p3 It's correctly detected: "dev_names":["/dev/cciss/c0d0", "/dev/block/104:0", "/dev/disk/by- id/cciss-3600508b1001052395359305442350500", "/dev/disk/by- path/pci-0000:06:00.0", "/dev/disk/by-id/edd-int13_dev80"] I can provide the full y2log - but it's huge and therefore I decided to only append the error part. When I'm correct I need to add an additional check for /dev/cciss in Storage::findVolume() (Storage.cc:4830) - is this correct? If so - how can I add a modified libstorage to my install source (we're doing a network install)? We need to install 9 servers with this raid controller and our plan was to use autoyast for this... Thx, Christian Ehrlicher

3 4

[yast-devel] Yast/11.2 uses <arch>-11.1 for path in driverupdate image
by Christian Ehrlicher 19 Feb '10

19 Feb '10

Hi, After I fixed my problem with the lvm hardware raid I tried to create a driverupdate file. Therefore I created the driverupdate as described here: http://ftp.suse.com/pub/people/hvogel/Update-Media-HOWTO/html/ But Yast simply did not recognize my files. After digging around for some hours I found a hint on autoyast-devel that it works with linux/suse/x86_64-11.1/ as path... Can this bug maybe documented somewhere in http://ftp.suse.com/pub/people/hvogel/Update-Media-HOWTO/html/ or opensuse wiki? This could save others some hours of trail and error :) Thx, Christian

1 0

[yast-devel] redesign of repo module UI
by Martin Schmidkunz 19 Feb '10

19 Feb '10

Hi! Please find an idea of repo module UI at: http://home.arcor.de/martin.schmidkunz/repos21.html The main differences to the current UI are: * compliance with basic concept of overviews as shown on gagarin.suse.de (OK, the edit string and delete functionality is missing, but I am sure you`ll figure it out :-)) * less information on screen * hints on priority * first implementation of enable/disable in YaST based on current survey results My usability questions are: * What do you think about the mock up? * What does "Keep downloaded packages" mean? * Does the target user group member know what the term "repository" is? I doubt that. * Does the target user group member know about "priorities"? Shouldn`t it be explained a little bit more? Tooltip? Looking forward to your comments! Cu, Martin ---------------------------------------------------------------- Martin Schmidkunz User Experience Specialist martin.schmidkunz(a)novell.com +49 (0) 911 740 53-346 ----------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) ----------------------------------------------------------------- Novell, Inc. Novell® Making IT Work As One™

12 14

[yast-devel] CSS: Which standard to use?
by Lukas Ocilka 19 Feb '10

19 Feb '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Do we have defined which standard/version should be used for webYaST? There are several of them, see http://www.w3.org/standards/techs/css#w3c_all IMO, we could use 'Cascading Style Sheets Level 2 Revision 1 (CSS 2.1)', but it must be 'defined' somehow. Thanks in advance Lukas - -- Lukas Ocilka Appliances Department, Novell Inc. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iD8DBQFLfQqVVSqMdRCqTiwRAtTJAJwNXmrb1gmPKaxGNeKSez42DJPLuwCeJ13n Qvm5tHkwDwr9Q61nK7n9CcA= =T7nr -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 4

[yast-devel] WebYaST status call - Feb 19
by Jiri Srain 19 Feb '10

19 Feb '10

jsrain, jdsn, tgoettlicher, mzugec, kkaempf, jsuchome, mkudlvasr, jreidinger, lslezak, mvidner, dmacvicar jsrain: working on docu jdsn: planning to fix registration issues today tgoettlicher: trying to get OBS autotest running, ETA today mzugec: fixing, testing new appliance kkaempf: mostly testing jsuchome: testing, testcases, looking into 11.2 appliance mkudlvasr: continuing firewall UIs, fixed in modules jreidinger: held a testing session in Prague, examining test coverage lslezak: bugfixing, testing new appliance, testcases - problems with package kit mocking mvidner: back, catching up dmacvicar: still working on building the appliance in build service -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain(a)suse.cz Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.cz -- 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: Example how to test if request is correctly sent
by Josef Reidinger 19 Feb '10

19 Feb '10

Hi, yesterday during Prague testing session I talk about testing request to ensure, that correct data is sent, that model really try to get information from rest-service etc. Today I add these checks to time module test suite for functional tests. You can see it here http://gitorious.org/opensuse/yast-web-client/commit/6645c5ff1666a63d0d4bb2… If you have any question, feel free to ask Josef -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, parts of webyast -- 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 initialization got stuck with error: Permission org.opensuse.yast.modules.yapi.administrator.read is not granted for user root
by Hai Shi 19 Feb '10

19 Feb '10

Hi, I am working on include WebYaST in the appliance. I followed the WebYaST vendor's guide: http://www.novell.com/documentation/webyast/book_webyast_vendor/?page=/docu… WebYaST initialization got stuck after accepting the license with error: Permission org.opensuse.yast.modules.yapi.administrator.read is not granted for user root The appliance is vmware image and has 2G memory. I used SUSE Sudio Online to build the appliance. Thanks, Hai

2 1

[yast-devel] Re: [yast-commit] r60856 - in /branches/SuSE-Code-11-Branch/gtk: ChangeLog VERSION tests/Firewall_bnc567505.ycp
by Katarina Machalkova 18 Feb '10

18 Feb '10

Hi, all >=== --- branches/SuSE-Code-11-Branch/gtk/ChangeLog (original) > +++ branches/SuSE-Code-11-Branch/gtk/ChangeLog Thu Feb 18 18:22:11 2010 > @@ -1,3 +1,8 @@ > +2010-02-18 Martin Kudlvasr <mkudlvasr(a)novell.com> > + > + * tests/Firewall_bnc567505.ycp: add Ricardo's test for bnc#567505 > + * Version 2.17.16 I've just noticed this test-case and also the bug it is associated with. It's certainly helpful that y2-gtk now handles this situation gracefully and prevents the whole thing from crashing, but - `item cell and the least of all, the entire`item content should *never ever* become nil. If it does, it is a bug in YCP code - think about substituting an empty string if the value is undefined or eliminate nil's from the term list before passing it to UI. The bug (https://bugzilla.novell.com/show_bug.cgi?id=567505) should now be reassigned to y2-firewall maintainer (with lower priority and/or severity) to solve the YCP part. fB. > =========================================================================== >=== --- branches/SuSE-Code-11-Branch/gtk/tests/Firewall_bnc567505.ycp > (added) +++ branches/SuSE-Code-11-Branch/gtk/tests/Firewall_bnc567505.ycp > Thu Feb 18 18:22:11 2010 @@ -0,0 +1,21 @@ > +// bug 567505 > +// GTK UI crashes when cell not set > + > +{ > + UI::OpenDialog( > + `VBox( > + `Table( > + `header("Name", "Price"), > + [ > + `item(`id(1), "Chili", 6), > + `item(`id(2), "Salami Baguette", nil), > + `item(nil), // crash > + `item(`id(4), "Steak Sandwich", 12) > + ] > + ), > + `PushButton("&OK") > + ) > + ); > + UI::UserInput(); > + UI::CloseDialog(); > +} -- 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 - Feb 18
by Jiri Srain 18 Feb '10

18 Feb '10

jsrain, mzugec, tgoettlicher, schubi, kkaempf, dmacvicar, jsuchome, lslezak, mkudlvasr jsrain: Documentation on tutorial mzugec: Missing functionality of Users, TODO: testing tgoettlicher: Tested 1.1.7 schubi: IBS clean-up, started making appliance for 11.2 kkaempf: D-Bus and PackageKit test environment clean-up + Wiki testing page dmacvicar: appliance build in IBS jsuchome: creating test cases lslezak: fixed race condition in PackageKit call, will work on tests mkudlvasr: bugfixing -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain(a)suse.cz Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.cz -- 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: users and groups
by Michal Zugec 18 Feb '10

18 Feb '10

Hi webyast hackers! Today I submited groups selection / deselection implementation into git, see https://bugzilla.novell.com/show_bug.cgi?id=580455 There are 3 issues I'd like to ask you for help: 1 - it doesn't work with Internet Explorer 8 (which is supported browser). Could anyone experienced find where the problem is? 2 - when one of the lists is too long it looks very bad. Any idea how to solve it? (scrollbars, align into more columns, ...) 3 - also some visible distinction between "all groups" and "selected groups" would be nice. I'll add labels there of course ;-) Thank you, Michal -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 5

[yast-devel] Testing documentation cleaned up and enhanced
by Klaus Kaempf 17 Feb '10

17 Feb '10

Hi, http://en.opensuse.org/YaST/Web/Development/Testing is now a tad shorter than before, moving example code to dedicated pages. New pages are http://en.opensuse.org/YaST/Web/Development/Testing/D-Bus about writing tests including D-Bus services and http://en.opensuse.org/YaST/Web/Development/Testing/PackageKit about tests involving PackageKit functionality. 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 status call - Feb 17
by Jiri Srain 17 Feb '10

17 Feb '10

jsrain, mzugec, jdsn, kkaempf, dmacvicar, tgoettlicher, bbrunner, jsuchome, schubi, jreidinger, mschmidkunz everyone: fixing bugs jdsn: digging into registration issues dmacvicar: getting the release out, already announced planning to build appliance in BuildService for next release bbrunner: working on autotest script, starting tests automatically jsuchome: to work on services module schubi: clean-up BS projects in order to run on 11.2 jreidinger: found out security problems - even non-public methods can be called from browser, alrady in bzilla mschmidkunz: created enabling/disabling concept Reminder: Beta5 is due on Thursday next week Please, focus on bugfixing and test cases, everyone should spend time on testing the appliance (we will have a daily build) and write a test report -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain(a)suse.cz Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.cz -- 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] small survey for webyast
by Martin Schmidkunz 17 Feb '10

17 Feb '10

Hi! Please take a few minutes to participate at a short usability survey concerning the presentation of enabling/disabling : http://www.surveymonkey.com/s/PZG7FCP Thanks, Martin ---------------------------------------------------------------- Martin Schmidkunz User Experience Specialist martin.schmidkunz(a)novell.com +49 (0) 911 740 53-346 ----------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) ----------------------------------------------------------------- Novell, Inc. Novell® Making IT Work As One™

1 0

[yast-devel] WebYaST status call - Feb 16
by Jiri Srain 16 Feb '10

16 Feb '10

tgoettlicher, bbrunner, schubi, jsrain, mzugec, jdsn, dmacvicar, mschmidkunz, mkudlvasr, jreidinger, jsuchome everyone: testing and fixing bugs bbrunner: created ruby UI tests, implementing them in the appliance schubi, dmacvivar: creating the add-on CD jdsn: registration issue mschmidkunz: will work on repo UI mkudlvasr: firewall UI jreidinger: testing WebYaST with bad network connection Note: Do not commit/push into head until we release final Beta4 -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain(a)suse.cz Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.cz -- 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 - Feb 15
by Jiri Srain 15 Feb '10

15 Feb '10

jsrain, bbrunner, schubi, mzugec, tgoettlicher, dmacvicar, jsuchome, jdsn everyone: testing, reporting bugs schubi: building RC version, posting to IRC, will announce via email; latest is 1.1.7 mzugec: testing and bugfixing, especially for users dmacvicar: testing buildservice-built image, many build bugs jdsn: fixing registration issues AI everyone: fix only really important bugs (crashes), other bugs to be documented in bzilla -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain(a)suse.cz Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.cz -- 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] YaST dns-server module silently failing
by Nicholas Tung 13 Feb '10

13 Feb '10

Hi all, I have a machine on which the YaST dns-server module is silently failing (no command line output is produced). Fortunately, the server seems to be working, I just can't configure it. I don't want to edit the DNS entries by hand, if possible. Any assistance would be much appreciated. The output on /var/log/messages when restarting named is here [1]. Thanks very much, Nicholas — ntung at ntung — https://ntung.com [1] http://pastebin.com/m38209cbd -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 3

[yast-devel] How to avoid sending nil to dbus
by Josef Reidinger 12 Feb '10

12 Feb '10

Hi, few bugs in last few days contain problem with sending nil to DBus which crash. Easy way to solve it is to use validations. In restService is BaseModel[1] which povides validation. Usage is same as for ActiveRecord validations [2]. For inspiration how it could look like you can look at time model [3] (I allow nil in validation but then handle it, but if sending empty value doesn't make sense you can force non-nil). Feel free to ask questions. Josef [1] http://svn.opensuse.org/autodocs/webyast-service/head/webservice/classes/Ba… [2] http://ar.rubyonrails.org/classes/ActiveRecord/Validations/ClassMethods.html [3] http://gitorious.org/opensuse/yast-rest-service/blobs/master/plugins/time/a… -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, parts of webyast -- 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] How to organize the WebYaST 'control center'
by Klaus Kaempf 12 Feb '10

12 Feb '10

That's a cool way to organize the module icons: http://razorjack.net/quicksand/ (Click on 'Filter by' and 'Sort by' buttons) 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

4 3

[yast-devel] WebYaST call 8.Feb 2010
by Stefan Schubert 09 Feb '10

09 Feb '10

kkaempf, jsrain, dmacvicar, jsuchome, mzugec, schubi, mschmidkunz mzugec: - rewrites password validation jsuchome: - testing mailsettings and fixed additional bugs kkaempf: - DBUS PackageKit testing mschmidkunz: - check current style guide schubi: - create appliance - try to solve the "granting permission problem" ALL: - Submit packages to SP1. Klaus has written an EMAIL how to do this. - This week the focus should be on getting a WebYaST release. -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 1

[yast-devel] Reminder: Watch out on what you test
by Klaus Kaempf 05 Feb '10

05 Feb '10

Just a reminder, since I just stumbled over it: When writing test cases, focus on testing _your_ model (resp. controller) implementation. Do _not_ try to test e.g. the YaPI, D-Bus, PackageKit itself ! Such tests belong to the package providing the used functions (e.g. YaST for YaPI). Thanks ! 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 call 05-Feb-2010
by Klaus Kaempf 05 Feb '10

05 Feb '10

*** Reminder: mvidner is on vacation next week, release manager is schubi mvidner, kkaempf, mzugec, mkudlvasr, jsuchome mvidner: - ruby-dbus patching - packaging for sp1 - next: vacation mzugec: - fixed user update - password validation - next: tests - next: groups management mkudlvasr: - firewall backend tests - next: firewall ui jsuchome: - services UI - battling with mail plugin - still fixing mail after network update - next: look at bugs kkaempf: - digged down on failing packagekit mocking tests - fixed ruby-dbus, repository tests pass now - next: fix remaining patches and packages tests - next: merge to master --- 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 call 04-Feb-2010
by Klaus Kaempf 04 Feb '10

04 Feb '10

mvidner, dmacvicar, kkaempf, mzugec, lslezak, schubi, mkudlvasr, jsuchome mvidner: - released security fix for 1.0 - trained schubi on release mgmt - next: release sp1 appliance dmacvicar: - no update mzugec: - fixed create and delete user bugs - next: fix user update lslezak: - improved routing, passing of dots possible now - fixed repo update bugs - next: write test cases - next: input validation schubi: - release mgmt - next: release mgmt mkudlvasr: - firewall saving - next: get all tests to pass jsuchome: - enhance ui of services - next: look at bugs kkaempf: - debugged failing repo test cases - next: merge to master --- 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: Improved routing - dot is allowed in path :id now
by Ladislav Slezak 03 Feb '10

03 Feb '10

Hi, I have slightly changed routing in WebYaST (in the both components). The problem was that e.g. repositories/show/openSUSE-11.2.xml request was parsed to :id => "openSUSE-11", :format => "2". That obviously could not work properly. It was fixed by specifying requirements for :id parsing: In the service: :requirements => {:id => /[^\/]*(?=\.html|\.xml|\.json)|.+/ } In the client: :requirements => {:id => /[^\/]*(?=\.html|\.js)|.+/ } Now whole string is used for :id, if there is a predefined suffix it is excluded from the :id. The regexps have to be modified if we need to support a new format in the future. (For more details about routing see: http://guides.rubyonrails.org/routing.html http://api.rubyonrails.org/classes/ActionController/Routing.html http://zargony.com/2009/05/05/routing-parameters-with-a-dot ) -- 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 For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] Version information added in Bugzilla
by Klaus Kaempf 03 Feb '10

03 Feb '10

Hi, the 'WebYaST' product in bugzilla.novell.com now has versions to choose from. This means that a bug now has a "version" in which the bug first appeared and a "target milestone", when the bug should be fixed. This is probably much more useful to plan sprints and to flag where/when a bug is to be fixed. I.e. maintenance updates to the 1.0 release have "ApToolkit 1.0 Update" as their target milestones. Additional version can be added freely (20 char limit) at any time. Thoughts ? 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 call 03-Feb-2010
by Klaus Kaempf 03 Feb '10

03 Feb '10

mvidner, kkaempf, mzugec, mkudlvasr, jsuchome, lslezak, mschmidkunz mvidner: - submitted packages to sp1 - kiwi config can now be exported - next: train schubi on release mgmt - next: work on sprint schedule mzugec: - fix user update - next: fix user update mkudlvasr: - firewall backend (fix yast2 module) - next: saving + testing jsuchome: - legacy yast - next: enhance ui of services - next: look at bugs lslezak: - escaping of user input - next: input validation mschmidkunz: - services ui - next: get local development environment schubi: - finished log viewer test cases - bug fixing - next: release mgmt kkaempf: - patches dbus mocking refactored - move generic mocking to webyast-webservice - next: merge to master --- 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] openSUSE 11.3 installer and LXDE
by Andrea Florio 02 Feb '10

02 Feb '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, i'm not (yet) a developer, but i would like to ping who of you work on yast2 DVD installer. openSUSE_11.3 will provide (finally) the new DE called LXDE [1] coolo already putted it on the DVD [2] i wonder if any of you could begin to add the "lxde option" to DE selection during installation, it should go under "other" like xfce. That because is really important for us to test as soon as possible how that new DE work with a clean installation and how eventually improve patterns. For any information you need, i'm here, just ask! Regards Andrea [1] http://en.opensuse.org/LXDE [2] http://www.gitorious.org/opensuse/patterns/commit/26e7f97ca7b8642d76bb8b4d8… - -- - ------------------------------------------ Andrea Florio QSI International School of Brindisi Sys Admin CISCO CCNA Certified openSUSE-Education Administrator openSUSE Official Member (anubisg1) Email: andrea(a)opensuse.org Packman Packaging Team Email: andrea(a)links2linux.de Web: http://packman.links2linux.org/ Cell: +39-328-7365667 - ------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAktfWUAACgkQyCZT87TFPuiybwCg3hWbsPbqEs8hf+8pT/hiDr6z 9PEAoMgaC0a0zETcwsp9Q4hpLIodbCDX =dFgL -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 3

[yast-devel] WebYaST call 02-Feb-2010
by Klaus Kaempf 02 Feb '10

02 Feb '10

schubi, mvidner, kkaempf, mzugec, jsuchome, lslezak schubi: - SLE11 work - next: log viewer test cases mvidner: - SLE11 work - next: release kkaempf: - catched up with mails - next: sync with mvidner mzugec: - l3 issue - next: password validation jsuchome: - testing - next: l3 issue lslezak: - packagekit patch (for repo mgmt) - repo mgmt - next: input validation --- 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] Repackage check-create-certificate.pl?
by Tim Serong 02 Feb '10

02 Feb '10

Hi All, I have a need for check-create-certificate.pl outside of WebYaST. Now, I can just grab a copy from the git repo and package it up separately as part of the project I'm working on (but *not* installed to /usr/sbin, to avoid conflicts in case WebYaST is also installed)... But it'd be nice to avoid this duplication if possible. Is there any scope for moving this script to some common base package? In particular, to some common base package that's available on SLES, in addition to openSUSE? Regards, Tim -- Tim Serong <tserong(a)novell.com> Senior Clustering Engineer, Novell Inc. -- 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] user module and basic ui proposal
by Martin Schmidkunz 01 Feb '10

01 Feb '10

Hi, please find a proposal for users dialog on: http://home.arcor.de/martin.schmidkunz/users5.html As I could not figure out, how to give the link in the list a different format via css I had to skip the link adding :-( Can anyone give me a hint? If that is solved, than of course you would click on edit and then you would get the following page: http://home.arcor.de/martin.schmidkunz/users_edit.html * Login settings: show basic settings for a user * Groups: what is missing is an overview of groups the user is already a member. This overview should be a list similar to the users overview. When the user hovers over a group he is shown the following: video Leave group | Group ID: 123 | Show group members Unfortunately I lack the technical skills to implement this. Can anyone help me with that? Is there a way to display a description of the group (at least I find it hard to image what is behind the group "video")? * Advanced settings: advanced stuff like login shell, home directory. What would be a non-technical description for these terms? Groups management: not really included in the mock up. One idea for group management would be to split the overview vertically into a users overview and a group overview. Permissions: I think that it would make sense to include user permissions in the users module. The users proposal also shows a kind of general proposal for overviews: * "Add" should be shown as a button on top of the overview * The overview items are shown as short entries. On hover some basic actions are revealed: Edit/Delete or in case of services Start/Stop, Refresh. * Edit: settings are shown on the next page with Save/Cancel as buttons. * Delete: shows a confirmation pop up Tabs: Instead of tabs sliders are used to make the layout more consistent. On hover settings are shown. Filter: Filter is shown between the add button and the overview aligned on the left. Is it technical possible to filter the list entries as used in users overview? If something is typed in which is not in the list, would it be possible to include this entry and add a "This entry does not exist. Would you like to create it?") Looking forward to your comments, Martin -- 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] WebYaST call 01-Feb-2010
by Klaus Kaempf 01 Feb '10

01 Feb '10

Attendees: mzugec, jsuchome, mschmidkunz, schubi, kkaempf mzugec - yast2 bugs - next: yast2 bugs jsuchome - tried testing latest image, virtualbox and vmware problems - yast2 bugs - next: services UI mschmidkunz - users module UI mockup, - next: share mockup with services schubi - improved log viewer layout - next: test cases kkaempf - catch up with mails - check last sprint result - next: plan next sprint -- 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] yast documentation
by stefan.eisenwiener＠freenet.de 01 Feb '10

01 Feb '10

Hallo everybody, I have tried to renew the greman webappearance of YaST (because it was the oldest layout). Now I am needing some help. I'm getting to the developers documentation, and somethings don't make sense. -- basic YCP questions 1. Why do we need YCP. (an other scripting language would have done the same trick) 2. Why is YCP type based. 3. What is the use of Symbol and Trem Datatypes in YCP. (not the format) 4. What is the use of Byteblock Datatype. -- Modul design question Why is the SCR concept not used like it was defined in the documentation, to be the system IO. According to the Tutorial one should write a global API of the Modul to access data the Modul works with. This HACK would be redundant if SCR like described in the documentation, would provide the data. OK this would meen the SCR tree would be something like the Registry from the evil Empire of Redmond, founded by Darth Gates. :-) If anyone could help me, it would meen much to me, thanks. best regards Stefan Eisenwiener Unbegrenzter Speicher, Top-Spamschutz, 120 SMS und eigene E-MailDomain inkl. http://office.freenet.de/dienste/emailoffice/produktuebersicht/power/mail/i…

4 3