September 2009 - YaST Development - openSUSE Mailing Lists

[yast-devel] WebYaST status call 2009-09-24
by Jiri Srain 24 Sep '09

24 Sep '09

present: kkaempf, schubi, lslezak, jsrain, mzugec, mkudlvasr, mvidner kkaempf: - looked into patch model mocking (D-Bus, PackageKit) - refactored, added more comments - TODO: factor out generic D-Bus and PackageKit mocking schubi: - finished language translation stuff, sent to translators - fixing bugs (looks like gettext gem) lslezak: - REST API documentation - looking at administrator UI validation problems mzugec: - no progress mkudlvasr: - merged resource restful branch to master - finished YaST resource class - TODO: research local package build mvidner: - fixing base system setup workflow - put yast2-network for SLES11 into OBS to make network plug-in working from RPM AI everybody: check that all packages build -- 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] custom log merged
by Duncan Mac-Vicar Prett 23 Sep '09

23 Sep '09

I have just merged the log monitor into master. The documentation will go here: http://en.opensuse.org/YaST/Web/VendorCustomization However the config file format is still on RFC: http://lists.opensuse.org/yast-devel/2009-09/msg00056.html Known bugs: - If the service goes down, the ajax update shows infinite errors ( https://bugzilla.novell.com/show_bug.cgi?id=540623 ) Together with the merge, a new model class called Metrics went into the service, together with a MetricsController. This classes are supposed to replace Status and StatusController by providing a cleanuped version using collectd name conventions and a more ActiveResource complaint interface, plus tests done from the beginning, and I intend to port the client so the graphs can be overlapped by instance (see http://auxesis.github.com/visage/) but this is no priority for now. -- Duncan Mac-Vicar P. - Engineering Manager, YaST 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] 6.17.1: New method ui::Selectable::updateCandidateObj
by Michael Andres 23 Sep '09

23 Sep '09

Hi! I added a new method ui::Selectable::updateCandidateObj. As you know it's not sufficient to simply look for an available package with higher version, when looking for an update candidate. There are more policies to respect, like the ones for arch and vendor changes. Also repo priorities may influence the result. updateCandidateObj will return you whether the candidateObj matches the active solver policies and has a greater version, and no PoolItem otherwise. So if the UI wants to suggest Selectables that could be updated, it could suggest the ones providing an updateCandidateObj, and not all where the candidate has 'just' a greater version. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma(a)novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- 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-09-23
by Jiri Srain 23 Sep '09

23 Sep '09

present: mschmidkunz, lslezak, jsrain, jreidinger, mzugec jdsn: - no progress mschimidkunz: - UI mock-ups for network administration and time - TODO: look at bugs lslezak: - spec-file versioning on ML - documenting the documentation process of REST service jreidinger: - debugging problems of FireFox and base system, working on testcase for Firefox mzugec: - no progress - TODO: bzilla -- 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] Registration Rest Api
by J. Daniel Schmidt 22 Sep '09

22 Sep '09

Hi hackers, I want to share my current thoughts about the Rest Api for the registration. Please have a look and feel free to comment and ask. Registration Configuration: --------------------------------- * /registration/config GET get registration server returns: <registrationconfig> <server> <url>https://myregistration.server.com/center/regsvc</url> </server> </registrationconfig> PUT set new registration server the certificate is inclueded as well post data: <registrationconfig> <server> <url>https://somewhere.else.com/center/regsvc</url> </server> <certificate> <data> <![CDATA[ -----BEGIN CERTIFICATE----- MIIFIDCCBAigAwIBAgIJAPP6cY6saTFlMA0GCSqGSIb3DQEBBQUAMIGPMQswCQYD VQQGEwJERTEPMA0 ......... 60QTef32lxeuVH9Kve8gGZiMwDqcJfl J8NLO3kNW3Zys2p4agg22yttmUs= -----END CERTIFICATE----- ]]> </data> </certificate> </registrationconfig> return value is the same as for GET Run Registration: --------------------------------- * /registration POST run registration and return the/a result post data: <registration> <options> <debug>2</debug> <nooptional>1</nooptional> <nohwdata>1</nohwdata> <forcereg>0</forcereg> <httpproxy>http://my.proxy</httpproxy> <httpsproxy>http://my.proxy</httpsproxy> </options> <arguments> <argument> <name>key</name> <value>val</value> </argument> ... </arguments> <registration> returns: <registration> <status>finished|missinginfo|error</status> <message>Some text to display</message> <guid>systemsguid</guid>  <missingarguments> <argument> <name>missingkey</name> <type>string|text|number</type> </argument> ... </missingarguments>  <changedrepos> <repo> <name>repoName</name> <alias>myRepoName</alias> <urls> <url>http://some.host/repo/xy</url> ... </urls> <priority>80</priority> <autorefresh>true</autorefresh> <enabled>true</enabled> <status>added|deleted</status> </repo> ... </changedrepos> <changedservices> <service> <name>some-serv1</name> <url>http://some.host/services/serv1</url> <status>added|deleted</status> </service> ... </changedservices> </registration> There is only one action to perform the registration. And all data has to be send for each request, as it operates in stateless context. The following action depends on the answer to the request. If there are arguments missing a following call is needed (together with the additional arguments). Otherwise the changes to the package system are returned if the registration succeeded. Thanks for comments. Ciao, Daniel -- J. Daniel Schmidt <jdsn(a)suse.de> SUSE Linux Products GmbH Research & Development Maxfeldstr. 5 GF: Markus Rex, HRB 16746 (AG Nürnberg) D-90409 Nürnberg -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

5 11

[yast-devel] Distribution dependent Requires: in *.spec file (SLE11 vs. 11.2)
by Ladislav Slezak 22 Sep '09

22 Sep '09

Hi all, We need to have correct WebYaST package dependencies to YaST in both 11.2 and SLE11 distributions. Because yast packages have completely different version numbers we have to explicitly check this in *.spec file using %suse_version macro. Example (just committed in 'service' REST plugin): ----------------------------------------------------------- # YaPI/SERVICES.pm %if 0%{?suse_version} == 0 || %suse_version > 1110 # 11.2 or newer Requires: yast2 >= 2.18.24 %else # 11.1 or SLES11 Requires: yast2 >= 2.17.10.2 %endif ----------------------------------------------------------- Please adapt your packages accordingly. See http://en.opensuse.org/Build_Service/cross_distribution_package_how_to for more details. -- 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] WebYaST status, 2009-09-21
by Jiri Srain 22 Sep '09

22 Sep '09

present: kkaempf, dmacvicar, schubi, mschmidkunz, lslezak, jsrain, jreidinger kkaempf: - administrative stuff dmacvicar: - merged log into master - ongoing discussion on ML schubi: - continued translation stuff jreidinger: - merged NTP code to master - exceptions discussion on ML - TBD: testing, bugfixing mschmidkunz: - learning jquery - redesign of network mock-up -- 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: [yast-commit] <rest-service> master : Change calling conventions for Invalid parameters to follow DRY
by Klaus Kaempf 22 Sep '09

22 Sep '09

* Josef Reidinger <jreidinger(a)suse.cz> [Sep 22. 2009 10:29]: > else > logger.warn("No argument to update") > - raise InvalidParameters.new [{:name => "language", :error => "Missing"}] > + raise InvalidParameters.new :language => "Missing" This is looking way better now, thanks Josef. Now I wonder if the "Missing" string shouldn't be replaced by a constant to make its semantic meaning clearer ?! 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

2 1

[yast-devel] WebYast: Error reporting in backend and how to use it in plugin
by Josef Reidinger 22 Sep '09

22 Sep '09

Hi, I done error reporting in backend based on exceptions (Universal exceptions is in file exceptions in webservice/lib). There is two type of error: First is invalid or missing parameters. For this case exist InvalidParameters exceptions. For example usage and details please see documentation of this exceptions. After you throw it, then if you don't catch it, it response 422 and use Error reporting structure for ActiveResource. So it return false on ActiveResource#save see ActiveResource::Base documentation for details (section validations errors). Second is problem on target machine like missing file, failed call of script, missing permissions etc. For this case exist ancestor BackendError which if not catched response 503 and serialized xml with description of problem (exceptions.rb contains few child for inspiration). If you don't catch error on frontend it end up in error reporting page which print error. For translated error is neccesarry to add translated string to ErrorConstructor module in libs directory at frontend (see already translated messages for usage). If you have any question, suggestion or problem please say it -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast modules language and time -- 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] Hudson does not build anymore
by Stefan Schubert 22 Sep '09

22 Sep '09

-------- Original-Nachricht -------- Betreff: Hudson does not build anymore Datum: Tue, 22 Sep 2009 10:00:50 +0200 Von: Stefan Schubert <schubi(a)suse.de> An: YaST-devel <yast-devel(a)opensuse.org> Hi, since my last chances in translation Hudson reports errors while building packages. Sorry for that. I will take care .... Greetings Stefan -- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi(a)suse.de ------------------------------------------------------------------------------- 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