YaST Development February 2010

yast-devel@lists.opensuse.org

30 participants
49 discussions

[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

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

YaST Development February 2010