January 2010 - YaST Development - openSUSE Mailing Lists

[yast-devel] YaST Documentation - Need for new server
by Lukas Ocilka 18 Jan '10

18 Jan '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, As you probably know, server forge.novell.com, on which we store our generated YaST documentation is at the end of its lifetime. We need to move it somewhere else soon. The current total size is currently about 180 MB, cca 11-26 MB per product. I'd like to use this mailing list to gather some ideas where to put it. So, please, write your ideas here. Requirements: 1.) Secure FTP or Rsync or ... access for uploading files. 2.) HTTP access for downloading. Thanks in advance Lukas - -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) - ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iD8DBQFLQw3bVSqMdRCqTiwRAiunAJ0b0nfR6DsShXHW7SQTuvpaSb+KtACeKHj+ 6TdCVmQVSKxDCudWraSrUl0= =xraW -----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] patches for .desktop file categories
by Gabriel Burt 15 Jan '10

15 Jan '10

Some .desktop files' Categories fields have a different X-SuSE-Yast* category than the X-SuSE-YaST-Group field (see bnc#374465). I assume the first patch (yast2-fix-desktop-files.patch) needs to be applied to trunk as well as the SLE11-SP1 branch? I've submitted patched packages for yast2-rdp and yast2-network for SP1. Thanks, Gabriel

3 5

[yast-devel] Webyast - proposal of test&commit rules
by Josef Reidinger 15 Jan '10

15 Jan '10

Hi, due to low test coverage and low quality of test case and code I think it is needed to set some basic rules which ensure some level of code and tests ( maybe you can be surprised how writing test improve code quality, because write tests to method which is more then one page long is extremely annoying, also properly test each XY parameters of method is really annoying, and testing model is much simpler then testing controllers or views). So proposal: - keep prerelease rule - no fix without failing test ( you must at first show test which demonstrate bug and then fix it in separate commit (but I suggest do it in one push to not break hudson)) - it has exception for fixes of spec file and lighttp configuration and UI redesign. - develop new functionality in branch and before merge check test (and only tests not code or run webyast) that functionality is implemented as expected - all plugins must have test case - commit often (so it is easier to review and test this small part). I think that you should commit at least once per day. FAQ: Q: It is hard to test THIS fix ( it is in controller, view, long method, corner case etc.)! A: Then code is not have enough quality. For corner case it is more important to write test for them to prevent regression. First bug can happen, regression is problem of tests, this cannot happen. Q: It is hard to write tests for webclient! A: I agree for previous release. Now it is quite easy and simple howto mail follow this one. Q: I don't know how to create branch in git! A: Ask on IRC! (for this case it is quite easy to do it) Q: I have another problem A: Ask on IRC or on mail if it is long story. I welcome any suggestions or comments. After discuss it will be placed on wiki. What you suggest if commit don't follow rules - immediately revert? Schubi - maybe we could add rule that working XML response for each model in webclient be as file fixture with same name as path on backend to be easy load by sinatra? 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

3 3

[yast-devel] Webyast: How to write tests for webclient
by Josef Reidinger 14 Jan '10

14 Jan '10

Hi, As you can see ( https://bugzilla.novell.com/show_bug.cgi?id=558697 ) there missing test suite at all for some webclient plugins and status of the rest plugins is not also in good shape. So I write here simple howto how you can start with simple test. 1) use yast_model. (helps you to move functionality from controller to model, so it is easier to test): steps: a) create simple model: (e.g. interface is 'org.opensuse.yast.modules.yapi.administrator') class Basesystem < ActiveResource::Base extend YastModel::Base model_interface :'org.opensuse.yast.modules.yapi.administrator' end b)change lines which loads dynamic proxy to model: load_proxy 'org.opensuse.yast.modules.yapi.administrator' # proxy_load to Model.find :one # or :all depends if you have multiresource or single resource as backend 2) create fixtures: a) create xml which you want test as response from rest-service b) save it in test/fixtures/*.xml 3) create simple unit test for model require File.dirname(__FILE__) + '/../test_helper' require 'yast_mock' #1) class ModelTest < ActiveSupport::TestCase def setup response_bs = load_xml_response "basesystem.xml" #2 request_bs = load_xml_response "basesystem-response.xml" #3 ActiveResource::HttpMock.set_authentication ActiveResource::HttpMock.respond_to do |mock| header = ActiveResource::HttpMock.authentication_header mock.resources :"org.opensuse.yast.modules.basesystem" => "/basesystem" mock.permissions "org.opensuse.yast.modules.basesystem", {} mock.get "/basesystem.xml", header, response_bs, 200 mock.post "/basesystem.xml", header, request_bs, 200 end end def test_find test = Model.find :one assert test.ready #4 assert_equal "test", test.response end def test_save test = Model.find :one test.value = "new" test.save #5 end def test_corner_case #6 response_bs = load_xml_response "basesystem_corner.xml" ActiveResource::HttpMock.respond_to do |mock| header = ActiveResource::HttpMock.authentication_header mock.resources :"org.opensuse.yast.modules.basesystem" => "/basesystem" mock.permissions "org.opensuse.yast.modules.basesystem", {} mock.get "/basesystem.xml", header, response_bs, 200 end test = Model.find :one assert_equal "strange chars #\\@$$%^&**", test.response end end notes 1) needed for extension to HttpMock 2) it is xml which you get from rest service when you call show 3) it is xml which you get as response from update 4) just test attributes from ActiveResource. model is complete full featured ActiveResource so it is possible to use all from that model 5) just call save is not enough, try find why ;) 6) test for corner case where you need to load different response from rest-service. try find why this mock doesn't have post method mocked Good and now you have your first initial version of test, which should grow quite lot If you have any difficulty or question, contact me ASAP. I can help you or describe what you need. 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 status call 14-Jan-2010
by Duncan Mac-Vicar Prett 14 Jan '10

14 Jan '10

WebYaST status call 14-Jan-2010 - Proposed milestones sent around - AI kkaempf, dmacvicar, jreidinger, mvidner: select buglist for next round - AI jsrain, dmacvicar: assign those bugs and milestone features -- 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] Update of (almost) all .desktop files
by Katarina Machalkova 14 Jan '10

14 Jan '10

YaST hackers, this is JFYI, I've just svn-committed changes to most of those YaST modules that contain .desktop files. A .desktop file eligible for the update calls /sbin/yast2 (Exec=/sbin/yast2 $foo) and requires root privileges (X-SUSE-YaST- RootOnly = true). Now /sbin/yast2 calls in root-only modules are wrapped in xdg-su and X-KDE- SubstituteUID lines [1] are therefore no longer needed, thus they have been removed. This is a step towards desktop interoperability (a new buzzword, eh? :) ) and it makes YaST modules launchable from desktop menus or icons in any desktop environment, including "minor" players in this field such as XFCE or LXDE (this was possible even before, but without DE-independent way of prompting for root passwd provided by xdg-su, all but 7 YaST modules were of little use with non-root user privileges) As the change is about to affect openSUSE 11.3, I'm not going to do a mass submitreq with all modified packages. It's up to you to decide whether to submit this change to OBS along with other pending changes some time in the future, or whether to push now (in case you don't see any other bugfixes/features for that package coming) References: https://bugzilla.novell.com/show_bug.cgi?id=540627 https://bugzilla.novell.com/show_bug.cgi?id=525876 http://lists.opensuse.org/yast-devel/2009-10/msg00038.html http://lists.opensuse.org/yast-devel/2009-10/msg00052.html fB. [1] X-KDE-SubstituteUID tells KDEsktop to ask for root passwd before launching this application. X-KDE prefix suggestsis that this is KDE-specific key and other DEs may ignore it. Most of them really do, including upstream GNOME -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter

1 0

[yast-devel] Gitorious and commit emails
by Josef Reidinger 13 Jan '10

13 Jan '10

Hi, just note to everyone who doesn't see this new feature yet. If you prefer mail commit mails before RSS feed you can now allow sending email on gitorious. 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 2

[yast-devel] Announcing the WebYaST architecture team
by Klaus Kaempf 13 Jan '10

13 Jan '10

Hi, during development of WebYaST 1.0 we sometimes struggled with (technical) decisions because of a) lack of experience and b) insufficient bandwidth on my side. In order to improve scaling and empower more people, we now have a 'WebYaST architecture team': - Martin Vidner - Josef Reidinger - Duncan MacVicar This team will take technical responsibility of WebYaST and help me in managing the project. Thank you guys for taking the challenge ! Among the first tasks of the team is - to ensure a consistent naming scheme (of packages, plugins, classes, etc.) - release WebYaST for openSUSE - plan and propose the schedule for regular releases - design/structure development of new features The team is just getting up to speed. Expect more details from them in the next days. 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] redesign of webyast users module
by Martin Schmidkunz 12 Jan '10

12 Jan '10

Hi, please find some ideas for a redesign of webYaST`s "Users" module at: http://home.arcor.de/martin.schmidkunz/ (wasn`t sure if it is a good idea to store all the jquery stuff in my Export...) It is based on rlihm`s mock up (http://gagarin.suse.de/). The basic concept is to show only the most important table entry on a top level (e.g. user name). Therefore there are fewer elements on the screen which eases the use of the module and increases its self-descriptivness and its task orientation. On a second level which the user accesses after clicking on the user name the user can choose whether to "edit" or "delete" the entry. Again it is avoided to show non-task related information. Before deleting an item the user is prompted an "Are you sure?" pop up in order to increase error tolerance and prevent the user from unintended data loss. "Edit" shows the settings of the list entry. If more settings are available they are organized in tabs. The "Edit" dialog is left either via "Save" or "Cancel" New list entries can be added via "Add New Item" button on top the list. Concerning "basic concept" * "Save"/"Cancel"/"Add" do not work properly in the mock up * "Add" should be a wizard * User needs to click "Save" twice (once in the edit tab and then in the main window) I am not sure whether this is intuitive. What do you think about that? * list should be sortable but I am not caple of implementing this technically Concerning "Users" module * When adding a user currently there are 8-9 settings which needed to be adjusted and some of them seem quite obscure to me. So, what do you think: which settings should be really editable via GUI? Currently there are: Full Name Groups Default Group (GID) Home Directory Do not create home directory Login Shell Login Name UID Number Password Full Name, Login Name, Password and Groups seem quite clear to me but is it really necessary to set login shell and UID in the GUI? And home directory? Wouldn`t it make sense to have a sane default which could be edited via an editor? * What do you think about showing permissions in the users module as well? This would seem quite logical to me. What is the reason, why permissions and users are separated? Do you have any other topics concerning users module GUI? Looking forward to your comments! Best regards and have a happy 2010, 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™

3 6

[yast-devel] Printer
by Donn Washburn 12 Jan '10

12 Jan '10

Hey Group; This may be the wrong place to bring this up. However, it is a perceived Yast2 Printer problem. I have a Bother MFC-7840W USB laser printer that according to www.linuxprinter.org it works with Brothers drivers - I have them installed. lsusb and hwinfo --usb find it. And modprobe has all the modules required. But Yast2>Hardware>Printer under Add connection wizard USB will not show any devices or my USB printer. Why would this be the case. I went to USB and as I remember I hit enter and on the right side a new window shows up and is always empty. Yast2 then will not advance until something is selected -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb(a)comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 4