November 2009 - YaST Development - openSUSE Mailing Lists

[yast-devel] WebYaST status call 13-Nov-2009
by Duncan Mac-Vicar Prett 13 Nov '09

13 Nov '09

present: jsrain, lslezak, jreidinger, bbrunner, schubi, jdsn, kkaempf, dmacvicar, jsuchome jsrain: RC2 "candidate" built internally, uploaded internally with announcement If you have a P2 bug that is not P2 currently then send it to jsrain for the list of known bugs lslezak: layout admin module, jquery validation breaks it. Will test latest appliance jreidinger: fixed bugs & submitted new package. Will fix basesystem problems bbrunner: created testcases for old modules, tested RC1, will test RC2 and run test automatically jsuchome: testing latest build, fixing webclient bugs. No more important ones. schubi: IE8 bug. status module click takes age on IE8 * : it may be that jqplot IE8 canvas emulation is done with js jdsn: debugging registration kkaempf: testing, looking usability problems permissions problem bug: changes should not be introduced at this point! dmacvicar: no updates everyone: thanks to jreidinger mvidner for release! -- 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] Re: [yast-commit] <web-client> master : Added Subnet mask string into network module
by Josef Reidinger 13 Nov '09

13 Nov '09

Martin Schmidkunz write: > ref: refs/heads/master > commit 8d1e8a1f8e8af1605e9ccbde2ae4286f6e77e200 > Author: Martin Schmidkunz <mschmidkunz(a)suse.de> > Date: Thu Nov 12 14:02:55 2009 +0100 > > Added Subnet mask string into network module > --- > plugins/network/app/views/network/index.html.erb | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/plugins/network/app/views/network/index.html.erb > b/plugins/network/app/views/network/index.html.erb index 3d51ee6..ce370b6 > 100644 > --- a/plugins/network/app/views/network/index.html.erb > +++ b/plugins/network/app/views/network/index.html.erb > @@ -170,7 +170,7 @@ > <%=text_field_tag :ip, @ip, :disabled => static_disabled %> > </p> > <p> > - <label for="<%= :netmask %>"><%=_("Prefixlen")%></label> > + <label for="<%= :netmask %>"><%=_("Subnet mask / > Prefixlen")%></label> <%=text_field_tag :netmask, @netmask, :disabled => > static_disabled %> </p> > </fieldset> > Hi, before your commit I change validation to require only Subnet prefix and according to mzugec, it is easier and allows easy use also if we extend support for IPv6. So user now can insert only /nn where nn is prefix of site. Is there reason to allow also subnet mask? thanks 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

1 0

[yast-devel] on bnc#554946 and late RC
by Martin Kudlvasr 13 Nov '09

13 Nov '09

Hi, just before today's RC, we've hit a 554946 (WebYaST reports permission errors). Backend reported bad rights everywhere and webclient ended in endless loop. 2 things caused this: 1) change of policyKit rights setup scripts which is called in all plugin %post. Until now /etc/yastws/tools/policyKit-rights.rb was used, but then it was changed to /usr/sbin/grantwebyastrights (IMHO good change from long time perspective). It change happened 2 days ago. So yast2-webservice was installed and the right script was run. But then the plugin scripts were installed without adding their rights in .policy files. 2) fix of bnc#554452 (Basic setup workflow starts with an error message). Originally (some weeks ago), when there was an exception in some basesystem module, the webclient stayed in endless loop of redirections. To brake the loop an to see the message, I've created the additional page. Now, when solving bug 554452, I hoped that we are long past problems with read permissions. But it looks like we will have to find another way of breaking the endless loop in basesystem (filed as bnc#554989). Cheers, Martin -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 3

[yast-devel] idea for 11.3 / installation procedure
by Dominique Leuenberger 13 Nov '09

13 Nov '09

Hello Yast-Hackers. 11.2 has hit the virtual shelves and this of course gives us all the freedom to hack on whatever we feel like hacking on. And of course, before every hack comes the idea (and sometimes the discussion). So let me just throw an idea in the room, which some might like, some might not. I'd propose a change in the installation workflow, when creating users, mainly assigning a password. At this stage, you enter the Full name, requested username and the user's password. Once you click NEXT the system is checking the strength of the password and let's you know (sometimes in 2 dialog boxes) if you're sure that you want to use the password. Whenever I observe users, I see them straight clicking through. Typically, a computer that asks something has to be answered with 'YES'. On the other hand, I observed users choosing their password on some websites, which use a 'strength meter' for the password. Every letter you type makes the meter go up, showing the strength. Surprisingly enough, as there is a live visual feedback, users more often try to twek their password (according the 'explanation' given around the strength meter) in order to achieve a 'green' strength meter, or at least getting to the yellow bars. After googling a bit, in order to give some visualization for you fellow readers, I can offer you: http://ui-patterns.com/userset/39/image/553#focus What does everybody think about such an enhancement? (yes, of course I can file it in fate... but it's useless to file if everybody just jumps and yells NOOO!!!). Dominique -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 2

[yast-devel] WebYaST status call 12-Nov-2009
by Duncan Mac-Vicar Prett 12 Nov '09

12 Nov '09

present: jsrain, mkudlvasr, lslezak, jsuchome, kkaempf, jdsn, schubi, dmacvicar jsrain: Did WebYaST presentation yesterday. Everyone: submit RC2 changes as soon as possible, jsrain will create image mjudlvasr: looked at some bugs, but not working manly on WebYaST lslezak: changes in patches module, reading patches in the background is done, too late for RC2, should be postponed. Working on validations in administrator module jsuchome: working on bugreports from kkaempf Discussion about wording in administrator module, possible use of help/tooltips etc. General agreement wording of "set" vs "change" is confusing as one already used the root password to login. kkaempf: busy, tested images and filed issues, will continue testing schubi: bugfixes in status and permissions module. Now to look registration module user interface (possibility to skip it) mschmidkunz: UI bugs, will continue with them dmacvicar: no updates jdsn: testing registration against NCC, debugging problem. Works with SLMS. dmacvicar points out that NCC internally may be an SMT instance -- 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] <web-client> master : showing flash if no data is available (bnc#524614)
by Josef Reidinger 12 Nov '09

12 Nov '09

Stefan Schubert write: > ref: refs/heads/master > commit a31f5e4c62058ff85094a86c38ff574bb3e067db > Author: Stefan Schubert <schubi(a)suse.de> > Date: Thu Nov 12 10:12:42 2009 +0100 > > showing flash if no data is available (bnc#524614) > --- > .../status/app/controllers/status_controller.rb | 25 > +++++++++++++++++-- 1 files changed, 22 insertions(+), 3 deletions(-) > > diff --git a/plugins/status/app/controllers/status_controller.rb > b/plugins/status/app/controllers/status_controller.rb index > 012449f..7b4cf03 100644 > --- a/plugins/status/app/controllers/status_controller.rb > +++ b/plugins/status/app/controllers/status_controller.rb > @@ -101,11 +101,30 @@ class StatusController < ApplicationController > > till = Time.new > from = till - 300 #last 5 minutes > - ActionController::Base.benchmark("Status data read from the server") > do - status = @client.find(:dummy_param, :params => { :start => > from.to_i.to_s, :stop => till.to_i.to_s }) + begin > + ActionController::Base.benchmark("Status data read from the server") > do + status = @client.find(:dummy_param, :params => { :start => > from.to_i.to_s, :stop => till.to_i.to_s }) + end > + create_data_map status > + rescue Exception => e ^^^ catch general Exception is not good idea, as it can enclose bugs. If you have for missing data proper BackendException with its unique identifier and you can check there simple as rescue Exception => e raise e unless ClientException.new(e).backend_exception_type == "YOUR_ID" flash...etc... end This catch only expected exception and other is not hidden and properly reported ( e.g. this change breaks control center, as on my pc AJAX set this message stuff which is then showed in language module which I select.) Josef > + flash[:warning] = e.message > + logger.warn e > end > - create_data_map status > # logger.debug @data_group.inspect > + > + #checking if there is one valid data entry at least > + found = false > + @data_group.each do |key, map| > + map.each do |graph_key, list_value| > + unless list_value.empty? > + found = true > + break > + end > + end > + break if found > + end > + flash[:notice] = _("No data found for showing system status.") unless > found + > true > end > -- 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

1 0

[yast-devel] Re: [yast-commit] Build failed in Hudson:
by Klaus Kaempf 11 Nov '09

11 Nov '09

Now that git is back up, this is a real packaging error :-} Klaus * Hudson Integration Service <hudson(a)suse.de> [Nov 11. 2009 14:57]: > See http://yast.suse.de:3334/job/webyast-service-head-i586/596/changes > > Changes: > > [Josef Reidinger] fix removing files from package in osc_submit task, release 0.0.10 > > [Josef Reidinger] rename script for grnating webyast rights and place to proper location (bnc#542077) > > [Josef Reidinger] don't automatic use index.php, as we not use php for webyast > > [Stefan Schubert] version 0.0.7 > > [Stefan Schubert] Merge branch 'master' of git@git.opensuse.org:projects/yast/rest-service > > [Stefan Schubert] added doc files > > ------------------------------------------ > A SCM change trigger started this job > Checkout > [workspace] $ git fetch > Checking out origin/master > [workspace] $ git checkout -f origin/master > Previous HEAD position was c9c9108... fix version of yast2-network > HEAD is now at 42c2433... added doc files > [workspace] $ git rev-parse origin/master > [workspace] $ git log --numstat -M --summary --pretty=raw 329b2610999c8f4478c3feb948ef7d66520652fe..42c243333c783c05bacb80a01d7aae2d9e9c3499 > [locks-and-latches] Checking to see if we really have the locks > [locks-and-latches] Have all the locks, build can start > [workspace] $ /bin/sh -xe /tmp/hudson1681495046727357549.sh > + sudo -E /data/hudson/bin/build-chroot.sh webyast rest-service head-i586 > SCRIPT ID: I am /data/hudson/bin/build-chroot.sh at http://yast.suse.de:3334/job/webyast-service-head-i586/ws/ > ..copying source code http://yast.suse.de:3334/job/webyast-service-head-i586/ws/* /data/hudson/HUDSON-CHROOT/webyast-head-i586/src/rest-service > ..copying make script to /data/hudson/HUDSON-CHROOT/webyast-head-i586/root > ... mounting sys > ... mounting proc > ... mounting pts > mount: special device none does not exist > Can't mount devpts /data/hudson/HUDSON-CHROOT/webyast-head-i586/dev/pts > ... switching to chroot and starting build > SCRIPT ID: I am /root/make-zypp.sh at / > > ??,????????'????????,????,????????'????????,????,????????'????????,????,????????'????????,????,????????'????????,?? > > + echo webyast-rest-service > webyast-rest-service > + case "${MODULE}" in > + SUBDIR=webservice > + cd /src/rest-service > + echo /src/rest-service > /src/rest-service > + ls > INSTALL > Makefile > README > Rakefile > doc > index.html.template > plugins > policy-tools > rpam > ruby-polkit > webservice > webservice-tasks > + [[ rest-service == \r\e\s\t\-\s\e\r\v\i\c\e ]] > + echo 'start dbus..' > start dbus.. > + /etc/init.d/dbus start > Starting D-Bus daemon..done > + echo 'Running as root' > Running as root > + echo 'Test plain SCR call' > Test plain SCR call > + echo '`Read(.target.tmpdir)' > + /usr/lib/YaST2/bin/y2base -l - stdio scr > 2009-11-11 13:50:47 <1> golelet(4490) [liby2] genericfrontend.cc(main):668 Launched YaST2 component 'y2base' '-l' '-' 'stdio' 'scr' > 2009-11-11 13:50:47 <1> golelet(4490) [ui-component] YUIComponentCreator.cc(createInternal):113 Creating UI component for "" > 2009-11-11 13:50:47 <1> golelet(4490) [liby2] genericfrontend.cc(main):822 YAST_IS_RUNNING is yes > ([]) > ("/tmp/YaST2-04490-PYIGFy") > ((nil)) > 2009-11-11 13:50:47 <2> golelet(4490) [liby2] Y2StdioComponent.cc(doActualWork):120 Communication ended prior to result () message > 2009-11-11 13:50:47 <1> golelet(4490) [liby2] genericfrontend.cc(main):837 Finished YaST2 component 'y2base' > 2009-11-11 13:50:47 <1> golelet(4490) [liby2] genericfrontend.cc(main):842 Exiting with client return value 'nil' > + check_exit 0 > + '[' -z 0 ']' > + MYEXIT=0 > + '[' 0 == 0 ']' > + echo 'exit code: 0 ... good, lets continue' > exit code: 0 ... good, lets continue > + return > + case "${MODULE}" in > + echo 'Creating shared tasks gem' > Creating shared tasks gem > + pushd webservice-tasks > /src/rest-service/webservice-tasks /src/rest-service > + rake package-local > gem build yast2-webservice-tasks.gemspec > (in /src/rest-service/webservice-tasks) > Updating yast2-webservice-tasks.gemspec (0.0.10)... > Updating package/rubygem-yast2-webservice-tasks.spec (0.0.10)... > WARNING: no description specified > WARNING: no rubyforge_project specified > Successfully built RubyGem > Name: yast2-webservice-tasks > Version: 0.0.10 > File: yast2-webservice-tasks-0.0.10.gem > cp yast2-webservice-tasks-0.0.10.gem package > + echo 'Installing gem...' > Installing gem... > + gem install yast2-webservice-tasks-0.0.10.gem > ERROR: http://gems.rubyforge.org/ does not appear to be a repository > Successfully installed yast2-webservice-tasks-0.0.10 > 1 gem installed > Installing ri documentation for yast2-webservice-tasks-0.0.10... > Installing RDoc documentation for yast2-webservice-tasks-0.0.10... > + popd > /src/rest-service > + sudo rake install_policies > (in /src/rest-service) > (in /src/rest-service/webservice) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/time) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/patches) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/users) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/network) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/basesystem) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/samba_server) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/system) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/administrator) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/registration) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/mail_settings) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/securities) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/language) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/services) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/eulas) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/ntp) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/status) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > + check_exit 0 > + '[' -z 0 ']' > + MYEXIT=0 > + '[' 0 == 0 ']' > + echo 'exit code: 0 ... good, lets continue' > exit code: 0 ... good, lets continue > + return > + cat > + check_exit 0 > + '[' -z 0 ']' > + MYEXIT=0 > + '[' 0 == 0 ']' > + echo 'exit code: 0 ... good, lets continue' > exit code: 0 ... good, lets continue > + return > + pushd webservice > /src/rest-service/webservice /src/rest-service > + ruby package/policyKit-rights.rb --user root --action grant > ruby: No such file or directory -- package/policyKit-rights.rb (LoadError) > ++ error_exit 1 > ++ echo 'ERROR: detected exit code 1' > ERROR: detected exit code 1 > ++ footer_and_exit 1 > ++ '[' -z 1 ']' > ++ MYEXIT=1 > ++ '[' 1 == 0 ']' > ++ ascii_failed > ++ cat > > ( ) > ( ) ( > ) _ ) > ( \_ > _(_\ \)__ > (____\___)) > > build failed > > ++ echo 'stopping dbus..' > stopping dbus.. > ++ /etc/init.d/dbus stop > Shutting down D-Bus daemon..done > ++ exit 1 > ... unmounting sys > ... unmounting proc > ... unmounting pts > umount: /data/hudson/HUDSON-CHROOT/webyast-head-i586/dev/pts: not mounted > Can't unmount devpts /data/hudson/HUDSON-CHROOT/webyast-head-i586/dev/pts > [locks-and-latches] Releasing all the locks > [locks-and-latches] All the locks released > Publishing Javadoc > Archiving artifacts > Build wasn't successful, skipping saikuro coverage report > Publishing rails stats report... > [workspace] $ rake --silent stats > Failed to send e-mail to Stefan Schubert because no e-mail address is known, and no default e-mail domain is configured > > -- > To unsubscribe, e-mail: yast-commit+unsubscribe(a)opensuse.org > For additional commands, e-mail: yast-commit+help(a)opensuse.org --- 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 2

[yast-devel] WebYaST status call 09-Nov-2009
by Duncan Mac-Vicar Prett 11 Nov '09

11 Nov '09

present: mvidnet, jsrain, jsuchome, jreidinger, mkudlvasr, schubi, jdsn, bbrunner, kkaempf, mschmidkunz, dmacvicar mvidner: new image will be renamed to RC1. We will not wait for new license text. appliance_doc branch has announcement AI: kkaempf : remove beta in product metadata (talk to ro) jsrain: opened bugs for backports that should go to SLE11GA yast2-storage can be removed after core is there (and see what happens) jsuchome: pepa log viewer, removing SCR::execute looking in some checking permissions bug discussion about permission checking on the client jreidinger: rewrote permissions module, changed behavior today: log viewer, if works bug about SCR::execute can be closed mkudlvasr : testing RC1, REST API docs schubi: images icons licenses, COPYING jdsn: fixing hudson, test RC1 bbrunner: test RC1, filed bugs kkaempf: thanks! for RC1. mschmidkunz: status UI dmacvicar: fixed yast2-ruby-bindings, cleanup bugzilla/fate -- 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 2

[yast-devel] Versioning YaST packages in the Code11 branch
by Jiri Srain 10 Nov '09

10 Nov '09

Hi! I recently noticed that several of us use incorrect versioning of the packages in the Code-11 branch in SVN (which means for SLES11 and/or openSUSE 11.1 maintenance updates). To summarize: SuSE-Code-11-Branch: 2.17.x.y, where 1.17.x is the version which was released in SLES11 and y is increasing with every new submit SuSE-Code-11-SP1-Branch 2.17.x, where x is increasing with every new submit This ensures that we avoid having two different packages (one from Code-11 branch and another one from SP1 branch) with the same version. Please, follow this policy strictly. The only exception is when the SP1 and Code11 packages are the same. Thanks! Jiri -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain(a)suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 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] git question
by Martin Schmidkunz 09 Nov '09

09 Nov '09

Hi, when committing my stuff I first use "git commit -a -m "explanatory text"" and then "git push" But when using "git push" I receive the following message: To git+ssh://git@git.opensuse.org/projects/yast/web-client.git ! [rejected] master -> master (non-fast forward) error: failed to push some refs to 'git+ssh://git@git.opensuse.org/projects/yast/web-client.git' To prevent you from losing history, non-fast-forward updates were rejected. Merge the remote changes before pushing again. See 'non-fast forward' section of 'git push --help' for details. Unfortunately the git help was not useful for me, so I hope that someone can help me answering my questions: * how can I avoid this message? * are my changes committed at all? (couldn`t spot them at http://git.opensuse.org/?p=projects/yast/web-client.git;a=summary) Thanks and have a nice evening, 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. SUSE® Linux Enterprise 10 Your Linux is ready http://www.novell.com/linux -- 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] Re: [opensuse-ruby] WebYaST: loading patches and status in the control center
by Klaus Kaempf 09 Nov '09

09 Nov '09

[Switching discussion to yast-devel] * Ladislav Slezak <lslezak(a)suse.cz> [Nov 09. 2009 14:27]: > > Hi all, > > I'd like to discuss the problem reported in bug #550934 > ('It takes minutes to refresh "system is up to date" and "system is healthy"') > > It takes very long time to load the initial patches and system status information > which is displayed on the first page (the WebYaST control center) using AJAX requests. > > I already have implemented caching in the patches module so the available patches are > not evaluated in every control center reload. But the first call still takes much time... > > The problem is that the first patch status request triggers repository metadata > download and cache rebuild which in case of slow/bad/overloaded network connection > can take several minutes (as reported in the bug). > > A similar problem is in the status module, but not that serious - the status is read > from the local machine so network is not involved in this case. And even on a slow > machine it won't block for more than several seconds. > > > I have these possible solutions for reading the patch status: > > * don't display the status messages at all (IMO bad solution, I find the overview > messages quite useful...) > > * make displaying of the status messages configurable (so users can hide and disable > status loading if it's too slow) > > * use a background job for reading patches (display a generic message like > "Reading patches" when the request takes too long and refresh the status after > some time again to get the real status.) > > AFAIK an AJAX request cannot be stopped (at least the [Stop] button in FF is disabled > when the page is loaded but an AJAX request is in progress). > > I'd prefer the last solution. Me too. Its important to present a honest explanation without being too technical. Maybe adding more steps to visualize progress would be helpful, i.e. "contacting update server", "retrieving update information", "evaluating update information", ... 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: Changing permissions to not use Scr (bnc#472752)
by Josef Reidinger 09 Nov '09

09 Nov '09

Hi, as part of removing Scr.Execute I plan to remove it from permissions module and I have three questions: 1) Does we support granting or removing permissions for users this release ( the most problematic part as granting permission is really great permission) ? 2) is problem if anyone can read what permissions have any user? (Maybe I can restrict it only to current login user, but then permissions module have problem) 3) Have yastws always enough permissions to run polkit-auth and polkit-action? (for current appliance yes) Thanks Josef -- 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 1

[yast-devel] permissions rewrite
by Martin Kudlvasr 09 Nov '09

09 Nov '09

irc.suse.de#rails > <jreidinger> schubi: Who is owner of permissions rest service? I found it > that implementation is ... not good. I plan to rewrite it to use model, > because now it is badly testable. I had the same feeling when I went through the code 2 days ago. I just didn't want to break the RC release (and had some bugs to solve). The work in progress is in "refactor-permissions" branch. Martin -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 4

[yast-devel] openSUSE 11.2 review, some critics on YaST
by Klaus Kaempf 09 Nov '09

09 Nov '09

YaSTies, watch starting at approx. 1:30 http://www.youtube.com/watch?v=vquPKhszDes 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] Images/icons in WebYaST
by Stefan Schubert 06 Nov '09

06 Nov '09

Hi, I have cleaned up the images and icons directory and have added a COPYING file. For the future please make an entry in COPYING ( where the image comes from and the concerning license) when you add a new image/icon. Thank you and greetings Stefan -- 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 stay in a tab in DialogTree after clicking Next
by Johannes Meixner 06 Nov '09

06 Nov '09

Hello, short story: in yast2-printer I use a DialogTree and in one of its tabs (which is not its initial tab) I like to stay in the tab after the user clicked Next when an error happened while writing the settings to the system so that the user can change the settings in the tab until it works or he can click [Cancel] to enforce leaving the dialog. Details: in yast2-printer I have in src/dialogs.ycp -------------------------------------------------------------------------- widgets_handling = ... "NETWORKPRINTING" : $[ "widget" : `custom, "custom_widget" : widgetNetworkPrinting, "init" : initNetworkPrinting, "handle" : handleNetworkPrinting, "help" : HELPS["printing_via_network_dialog"]:"" ], . . . tabs_description = ... "network" : $[ "header" : _("Print via Network"), "tree_item_label" : _("Print via Network"), "caption" : _("Print via Network"), "contents" : `VBox( "NETWORKPRINTING" ), "widget_names" : ["NETWORKPRINTING"] ], . . . DialogTree::ShowAndRun ( $[ "ids_order" : [ "overview", "network", ... ], "initial_screen" : "overview", -------------------------------------------------------------------------- I like to stay in the "NETWORKPRINTING" tab when writing its settings fails. In src/printingvianetwork.ycp I have currently in the handleNetworkPrinting() function: ---------------------------------------------------------------------------- if( `next == event["ID"]:nil ) { if( ! ApplyNetworkPrintingSettings() ) { Popup::Error( // Popup::Error message: _("Failed to apply the settings to the system.") ); // In case of an error stay on the "Print via Network" dialog // so that the user can either change his settings until it works // or he can use the [Cancel] button to return to the Overview dialog: return nil; } ---------------------------------------------------------------------------- but this does not work. Instead the whole YaST module is exiting with `next regardless that I explicitely "return nil" and in y2log there is: ------------------------------------------------------------------------------ 2009-11-06 11:06:28 <1> nelson(6379) [liby2] Y2ProgramComponent.cc(result):159 Sending result: `result (nil) 2009-11-06 11:06:28 <1> nelson(6379) [liby2] genericfrontend.cc(main):777 Finished YaST2 component 'y2base' 2009-11-06 11:06:28 <1> nelson(6379) [liby2] genericfrontend.cc(main):782 Exiting with client return value '`next' ------------------------------------------------------------------------------ Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- 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 status call 06-Nov-2009
by Benjamin Brunner 06 Nov '09

06 Nov '09

WebYaST call, 06 Nov 2009 participants: jsrain, schubi, bbrunner, jreidinger, jdsn, mvidner, jsuchome, stano, bbrunner schubi: - finished last bug in status module - today will work with icons and images for license-stuff jdsn: - worked on registration module - tested SLMS and SMT jsuchome: - custom services does not work for RC1 - worked at log viewer jsrain: - no updates - installed the latest snapshot mvidner: - RC1 looks okay - release today soon after lunch jreidinger: - removed scr_execute for custom logs - today will change permission controller in backend -stano: - everybody must set up support-level for their maintained packages (L3) - figured out a SLMS problem Have a nice weekend! -- 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: Improvements after first release (discussion)
by Josef Reidinger 06 Nov '09

06 Nov '09

Hi, I would like to summarize and also start discussion what should be improved after first webyast release. Because I think that things which affects infrastructure should be done before changes in plugin to benefit from improvements and also if we collect useful things which should framework provide, then it is easier to implement it together and cooperate between features. I separate issues to simple and more complex. Simple: - all webclient plugins should have testsuite (related to improvement activeResource usage on webclient as now it is quite hard to create good tests ) - all rest service should have REST documentation - all rest service should properly report invalid values ( related to validations in ActiveModel ). Properly report is to use InvalidValue exception which reports 422 and xml description which ActiveResource understand ( done automatic in InvalidValue exception) - remove static rest_authentificate file and use gem, because current solution require that we also port all security changes in rest_authentificate manually Complex: - Rest-service framework should provide Basic model and two Basic controller for REST. model should contain helper for permission check for read and write permission, validations, automatic loading and storing xml. Controllers should provide basic REST operation for single resource and multiple resource REST service provides xml and json api. After some research the best look to backport ActiveModel from rails 3.0 and add own specific yast extensions. I can maintain it as gem. Example plugin after this improvement: controller: LanguageController < SingleRESTController end model: Language < YaSTModel #permissions checks read_permission yapi("language.read") write_permission yapi("language.write") #validations, generally known from ActiveResource and ActiveRecord + own specific if it is needed for DBUS validates_inclusion_of :language, :in => @known_languages #etc... def find (...) #Active model parameters create( yastdbuscall (language.read,params...)) #create uses automatic new a load end def save yastdbuscall (language.read,params...) #maybe some checks etc. end end Thats what should simple plugin which is backended by DBus contain, Other non- problem related things should be handled in framework (if you must copy and paste code, then something is wrong, when you write plugin you should add only specific things related to that plugin). - Change permissions and resource call in frontend. It is huge wasting of sourced and one of problems that leads to slow webyast. My solution is to ask webservice for all resources and all permission for logged user after login and then use this values stored in webclient. This helps avoid calling three rest resources instead of one ( you can see example in network, where is 4 rest calls which lead to 12!!! rest service call just to provide information about network). Related also to next note. - Simplify ActiveResource handling in webclient. Current generated way is uncommon and each person, which want create own plugin fight with it. Solution used in network, which provide some basic class is for me just half solution. What should be done is class which act like common ActiveResource which is well known rails source. My suggestion is to join with previous task and provide extension of ActiveResource which takes site from a storage (known after login), path on site from a storage (known after login if we do previous note) and credentials (same as now or improved). This is what ActiveResource need to improve. So after this change our code should look like common ActiveResource code and not as some strange code which looks like it doesn't use rails. Welcome any opinions, suggestion and ideas what should be also improved 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

1 0

[yast-devel] WebYaST: use ||= Ruby operator
by Ladislav Slezak 05 Nov '09

05 Nov '09

Use message ||= "Unknown error" instead of if message.nil? message = "Unknown error" end It makes the code shorter and more readable. -- 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 call 04-Nov-2009
by Benjamin Brunner 05 Nov '09

05 Nov '09

WebYaST call, 04 Nov 2009 participants: bbrunner, schubi, jdsn, duncanmv, jsuchome, jsrain, jreidinger schubi: - bugfixed system_check rake tasks - today will work on bugs in status module jdsn: - created an xml for registration module duncanmv: - fixed ruby-bindings bugs - today will work on bug 5512706 bbrunner: - reviewed public-folder and deleted unused images and icons - tested WebYaST-UI - overworked the package-list on opensuse.org jsrain: - no updates jreidinger: - fixed bugs, if someone needs help for his bugs you can contact him jsuchome: - worked on services to providing ruby bindings additional: Tomorrow, jsrain will have the reports, thank you! -- 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] RC 1 upcoming
by Martin Vidner 05 Nov '09

05 Nov '09

Hi! today at noon is the check-in deadline for WebYaST RC1, and the following is next: * building the packages and the appliance * while getting last minute fixes from you * overnight QA in Beijing will run validation tests (new!) * we will release it on Friday morning document your changes in .changes * refer to bug numbers (and mark the bugs fixed) * point to README_FOR_APP, especially for vendor customization * don't forget that others may have changed your module (Robert most likely did) Use this to check the real changes: git log --stat -- plugins/$MINE submit to YaST:Web:STABLE osc sr -m "many new bugs. fixed." YaST:Web $PKG YaST:Web:STABLE -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

1 0

[yast-devel] Webyast - calling another rest-services
by Josef Reidinger 04 Nov '09

04 Nov '09

Hi, As time comes we should start to think how in our infrastructure we should call another modules. E.g. call collectd status from status module should use services module. I see there few problems: 1) How to avoid permission check for another controllers? For example if status just want to run rccollectd status user should have just permission to status and not need to read services ( if we create permission mess no one set it and paranoid customer doesn't webyast) 2) How to avoid load correct controller with interface and another little strange things in our rest-service? And should we create hard dependencies or have fallback if target module is not available? 3) We should study how to do it properly to avoid future problems. Josef -- 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

1 0

[yast-devel] Deleted unused images
by Benjamin Brunner 04 Nov '09

04 Nov '09

I removed the unused images and the unused yast.js and fake-data.js script in the public folder. Here the complete list of the deleted items: # deleted: plugins/custom_services/public/icons/custom-service.png # deleted: webclient/public/icons/kupdateapplet_busy.png # deleted: webclient/public/icons/kupdateapplet_gray.png # deleted: webclient/public/icons/pattern-network.png # deleted: webclient/public/icons/yast-apparmor.png # deleted: webclient/public/icons/yast-bluetooth.png # deleted: webclient/public/icons/yast-dhcp-server.png # deleted: webclient/public/icons/yast-dsl.png # deleted: webclient/public/icons/yast-firewall.png # deleted: webclient/public/icons/yast-hdd.png # deleted: webclient/public/icons/yast-http-server.png # deleted: webclient/public/icons/yast-ldap-server.png # deleted: webclient/public/icons/yast-misc.png # deleted: webclient/public/icons/yast-package-manager.png # deleted: webclient/public/icons/yast-partitioning.png # deleted: webclient/public/icons/yast-pm.png # deleted: webclient/public/icons/yast-printer.png # deleted: webclient/public/icons/yast-raid.png # deleted: webclient/public/icons/yast-service-22.png # deleted: webclient/public/icons/yast-sound.png # deleted: webclient/public/icons/yast-x11.png # deleted: webclient/public/images/Yast_crystal_logo_gray.png # deleted: webclient/public/images/button_critical.png # deleted: webclient/public/images/button_ok.png # deleted: webclient/public/images/button_warning.png # deleted: webclient/public/images/computer_connected.png # deleted: webclient/public/images/configure.png # deleted: webclient/public/images/empty.png # deleted: webclient/public/images/geckohead-green.png # deleted: webclient/public/images/geckohead-grey.png # deleted: webclient/public/images/geckohead-grey_001.png # deleted: webclient/public/images/icons/48/clock.png # deleted: webclient/public/images/icons/48/computer.png # deleted: webclient/public/images/icons/48/computer_48.png # deleted: webclient/public/images/icons/48/user.png # deleted: webclient/public/images/icons/48/user_add.png # deleted: webclient/public/images/icons/48/user_delete.png # deleted: webclient/public/images/icons/48/user_manage.png # deleted: webclient/public/images/icons/48/user_warning.png # deleted: webclient/public/images/key_add.png # deleted: webclient/public/images/n-geeko.png # deleted: webclient/public/images/probe.png # deleted: webclient/public/images/rails.png # deleted: webclient/public/images/reload.png # deleted: webclient/public/images/restart.png # deleted: webclient/public/images/start.png # deleted: webclient/public/images/status.png # deleted: webclient/public/images/stop.png # deleted: webclient/public/images/suse-logo.png # deleted: webclient/public/images/webyast.png # deleted: webclient/public/inc/fake-data.js # deleted: webclient/public/inc/yast.js # deleted: webclient/public/stylesheets/images/bg-head-gradient-blue.png # deleted: webclient/public/stylesheets/images/bg-head-gradient-bluegrey.png -- 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] <web-client> master : display correct language name
by Martin Vidner 04 Nov '09

04 Nov '09

On Tue, Nov 03, 2009 at 06:36:27PM +0100, Ladislav Slezak wrote: > ref: refs/heads/master > commit 055f49b8bd433d33b00dd88fdec3e390b8508a74 > --- a/webclient/vendor/plugins/lang_helper/lib/lang_helper.rb > +++ b/webclient/vendor/plugins/lang_helper/lib/lang_helper.rb > @@ -42,6 +42,12 @@ module LangHelper > end > > def current_locale_name > + # check full locale at first (language + country) > + if LANGUGAGES.has_key?(locale.to_s) toog manyg g's (fortunately consistently in the code) -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

2 1

[yast-devel] [webYaST] Bug 551276 - remove Scr.execute from services plugin
by Jiří Suchomel 04 Nov '09

04 Nov '09

Hi! We are still undecided which way to go in bug 551276. Picture: we need a way to call (from rest service) a custom script which is written in custom config file. Currently we are parsing the config file directly in rest service plugin and calling the script with Scr.execute. We have these options so far: a) use YaPI::SERVICES and call the script from here. The problem is, to parse yml file, we'd need perl-YAML package, which is not on SLE11, but on SDK. b) use YaPI::SERVICES, and from perl file, call ruby module which would care for parsing yml file. But for using ruby at this place, we'd need yast2-ruby-bindings, which also is not on SLE11. Could we include in as a part of webYaST? c) write new dbus service. We'd need ruby-dbus package: also not part of SLE11, but included in webYaST repo anyway. Comparing to a+b, this would mean more code, and new service which may need new security audit. d) do not use YML as config file, but something parsable from Perl without additional requires. d2) use file called custom_services.yml, and parse it directly from Perl. This means, it could not be true yml, only minimal subset. There's ongoing discussion in bug 551276, but maybe more people can find the right solution. 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 For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 2