April 2008 - YaST Development - openSUSE Mailing Lists

[yast-devel] buttons buttons buttons
by Martin Schmidkunz 24 Oct '08

24 Oct '08

Hi, when testing openSUSE 11.1/SLES 11 I came across a rather curious situation: many modules have already switched their label from Abort/OK(Accept, Finish...) to the style guide compliant Cancel/OK label. However in every case there is a third, inactive "Back" button included. This doesn't make sense as there is nothing to go back and the dialog is just an overview. I suppose this is due to many of you using wizard.ycp as base template for creating your module. What do you think about using the button box (http://lizards.opensuse.org/2008/08/28/button-order-in-yast-trying-to-make-…) instead of the buttons of wizard.ycp? In my opinion this would have the following advantages: * consistent button order in pop ups and in the module * user would not need to deal with an inactive button * button order in YaST would be consistent with the desktop used by the user What do you think about that issue? 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. 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

3 6

[yast-devel] Reminder: Text freeze on Monday
by Jiri Srain 21 May '08

21 May '08

Hi! This is just a reminder, that the text freeze for openSUSE 11.0 strings in YaST is on Monday, April 21st, 10:00 AM. After the text freeze, string changes are only allowed, if the original message is so bad that translators do not have a chance to get it right. String additions due to bug fixes or because of missing _("tagging") are allowed. Typos and other cosmetical things will be fixed with overloads in en_GB.po and en_US.po files. 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

2 2

[yast-devel] Prague YaST team meeting 2008-04-29
by Jan Kupec 30 Apr '08

30 Apr '08

Prague YaST team meeting 2008-04-29 =================================== Present: jkupec, jreidinger, jsrain, juhliarik, jsuchome, kmachalkova, locilka, lslezak, mvidner, mzugec Minutes: jkupec Next minutes: jreidinger Installation ------------ - desktop selection rewritten (locilka) (bnc #379157, http://lists.opensuse.org/opensuse-factory/2008-04/msg00612.html) - registration is not required to add an update repo now (locilka) (bnc #381360) - correct pattern order based on metadata in the installation proposal (lslezak) - fixed installation progress for > 2G to install (32bit integer overflow problem) (lslezak) Add-On Creator (jsuchome) -------------- Add-On-Creator now comes with /etc/sysconfig/add-on-creator, where user can define the content file default values for new products. List of Add-On Products is saved into $HOME/add_on_products.ycp if module is run as regular user. libzypp ------- - PoolQuery fixed for (exact/glob/regex) matching of the name attribute of patches/patterns/products. (matz, ma, jkupec) + some more fixes zypper ------ - package licenses are rendered to plain text + viewed in pager (jreidinger) (bnc #260883) - install summary displays vendor and architecture changes - new option 'p' in the Continue? prompt shown when installed is used with (default) --force-resolution and there are packages to-be-removed (will probably add more heuristic post 11.0) - support for prompt helps (pitty that we have text freeze :O( - progress reporting output unified - many bug fixes, more to come :O) Misc ---- - mzugec and mvidner were testing beta1, reporting bugs - YOU - special warning will be displayed if user makes his own selection in addition to the preselected patches, no hidden solver run (bnc#367057) (jsuchome) - Patch CD (SP2): ensure first CD is in drive before synchronization with ZMD (bnc#381594) - juhliarik was fixing bootloader - bubli came back from Nuremberg alive and in good health - Sound - hot-plugged devices will be added as last to avoid device reordering/renaming problems (lslezak) - Product.ycp - reads the product name from /etc/SuSE-release or from content file (lslezak) - SLE10 SMT - integrated to SLE10-SP2 installation workflow (locilka) -- 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] "Repository" menu in the PackageSelector widget is optional now, how to use it
by Ladislav Slezak 30 Apr '08

30 Apr '08

Hi all, Because of bug https://bugzilla.novell.com/show_bug.cgi?id=381956 I added `opt(`repoMgr) option to the `PackageSelector widget (default is off now). The option enables starting repository management from the package selector directly. If you want to display the "Repository" menu in your module you should: * if `PackageSelector is used directly: add `opt(`repoMgr) option and handle `repo_mgr result - the best idea is to call WFM::CallFunction( "repositories", [ `sw_single_mode ]); `sw_single_mode means that the packages in the pool should be refreshed after adding/removing a repository) and then display the package selector again. * if inst_packages.ycp client is used call: symbol result = (symbol)WFM::CallFunction( "inst_packages",[`searchMode, `repoMgr]); in a loop (`repoMgr parameter enables the menu). If `repo_mgr is returned start repositories.ycp (see the previous paragraph) and then inst_packages.ycp again. Check your code and decide whether the "Repository" option makes sense in your modules adapt them according the steps above. Especially check for installation/running system. If you have any questions just ask me... (The `opt(`repoMgr) option is currently supported by Qt UI only.) Ladislav -- 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] new SCR agent for xml (again)
by Jiří Suchomel 29 Apr '08

29 Apr '08

Hi hackers, since yast2-2.16.57 you can use a new agent for reading and writing XML files from YaST. The SCR path is .anyxml - yes, it is same as the one of previous agent that we had before (it was announced in http://lists.opensuse.org/yast-devel/2007-11/msg00057.html). The old agent was found incapable for parsing more than very simple files and was renamed to .barexml, see bug 366867 for details. The new agent is using Perl XML::Simple library and is able to return whole content of XML file in a tree structure. Usage: Read a file /tmp/in.xml into YCP map: map config = (map)SCR::Read (.anyxml, $[ "file" : "/tmp/in.xml", "args" : $[ "ForceArray" : 0, "KeepRoot" : 1 ] ]); See the attached example XML file and it's YCP representation got as a result of this command. You can see that the call can take some optional arguments, the meaning of those 2 in example is "force nested elements to be represented as arrays even when there is only one" and "retain the root element name". The agent should actually be able to parse most[*] of the options that XML::Simple provides, see http://search.cpan.org/dist/XML-Simple/lib/XML/Simple.pm for more. Writing modified YCP structure back to XML is also easy: SCR::Write (.anyxml, $[ "file" : "/tmp/config.xml", "xml" : config, ]); Find a bit more about usage directly in the agent file: http://svn.opensuse.org/svn/yast/trunk/yast2/library/agents/ag_anyxml Jiri [*] = not tested -- 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

2 2

[yast-devel] Releasing suppressed log lines
by Stefan Hundhammer 29 Apr '08

29 Apr '08

http://mvidner.blogspot.com/2008/04/opensuse-110-beta-1-is-that-murderers.h… I like the idea of that, and it actually already helped me to track down some bugs. But I have one request for that: Could we somehow make it more visible which log lines were released later, and where the segfault occurred? Currently IMHO it's very hard to find that dividing line: There is a lot of noise from the YCP interpreter (it even dumps the entire code to the log that is being executed - a bit overkill IMHO) and other libs. I'd like some indentation (some blanks or a tab) for those released log lines. Is that feasible? Failing that, some blank lines (4-5) and a marker would also be helpful so you can see quickly while scrolling where those released debug log lines begin: 2008-04-28 17:27:11 <0> snell(18431) [qt-ui] YQApplication.cc(YQApplication):61 YQApplication constructor end 2008-04-28 17:27:11 <1> snell(18431) [qt-ui] YQUI_core.cc(initUI):243 YQUI initialized. Thread ID: 0xb685fb90 2008-04-28 17:27:11 <0> snell(18431) [qt-ui] YQMainWinDock.cc(YQMainWinDock):57 MainWinDock initial size: 895 x 683 *** SEGFAULT *** Releasing suppressed debug log lines: 2008-04-28 17:27:10 <0> bla... 2008-04-28 17:27:10 <0> bla... 2008-04-28 17:27:10 <0> bla... 2008-04-28 17:27:10 <0> bla... >>> End of suppressed debug log lines 2008-04-28 17:27:10 <1> ...log from another y2base process... CU -- Stefan Hundhammer <sh(a)suse.de> Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- 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] Prague YaST team meeting 2008-04-24
by Jan Kupec 29 Apr '08

29 Apr '08

Prague YaST team meeting 2008-04-24 =================================== Present: jkupec, jreidinger, jsrain, juhliarik, jsuchome, locilka, lslezak, mvidner, mzugec Absent: kmachalkova (exchange) Guest: msvec Minutes: jkupec Next minutes: jkupec YaST2 core ---------- - feature code name "Blanik" - release 42 last log messages on yast crash (mvidner) http://mvidner.blogspot.com/2008/04/opensuse-110-beta-1-is-that-murderers.h… libzypp ------- - fate #120118 - Locks API is ready, but PoolQuery needs a fix for (exact/glob) matching of the name attribute of patches/patterns/products! Other stuff should work. - It seems that we now have API matching all the application layer requirements, jkupec will document it on http://en.opensuse.org/Libzypp/Application_Layer/API Anybody is welcome to participate. zypper ------ - richtext descriptions are now finally rendered to plain text (jreidinger) - fate #302919 done - improvements if the install command like: zypper install foo-1.2.4 or foo=1.2.4 or even foo = 1.2.4 zypper install yast2* zypper install anjuta -kdevelop zypper install packman:MPlayer whateverfromanywhere factory:foo - fate #302148 - compatibility with rug, few commands added: whatprovides packages patterns products service-types list-resolvables mount install/update options global options - fate #120118 - package locking commands added (addlock, removelock, locks) - many bug fixes Samba (jsuchome) ----- - done fate #301320: Windows Domain Membership Yast module should include a field to specify the OU for the machine account - done fate #300458: Samba-client module needs option to leave an domain Users (jsuchome) ----- - Finished feature #302980: Simplified user config during installation. Installation ------------ - kexec is used now instead of rebooting the machine after the installation. You can use kexec_reboot=0 boot parameter to suppress this behavior. (juhliarik) - image-based installatino: ability to choose target architecture added (allows multiarch installation media) (locilka) SuSEFirewall2 (locilka) ------------- - possibility to switch Samba browsing on added High Availability ----------------- - command line interface added (lslezak) Pkg-Bindings (lslezak) ------------ - ability to switch callbacks on/off added: added PackageCallbacks::RegisterEmptyProgressCallbacks() and PackageCallbacks::RestorePreviousProgressCallbacks() functions - Improved computing of total size of packages to install and to download in the installation proposal - sum the sizes in pkg-bindings instead of on the YCP level (speed up from 17 seconds to <1 second) Printer (mzugec) ------- - Avoid the Automated Setup For "Non-Recommended" (means not fully supported) Printers (FaTE#120083) - With bcm-firmware-cutter download firmware for Broadcom wireless cards (FaTE#302130). Misc ---- - lslezak and mzugec represented openSUSE on Linux Expo - mvidner is having fun with SP1 -> SP2 migration :O) - mvidner is working on lazy loading of libzypp in yast - there is a problem with order of destruction of static objects (fate#302119, bnc#381917) - Fixes and code cleanup in the dirinstall module (lslezak) -- 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 desktop files should use 'Settings' and 'System' categories
by Lukas Ocilka 28 Apr '08

28 Apr '08

Morning, There is a generic bug 382778 - YaST desktop files should use Settings and System categories in bugzilla. https://bugzilla.novell.com/show_bug.cgi?id=382778 It's hard to assign it to one developer as almost all YaST desktops files are affected. The bug is about adding two more main categories to the list of categories supported by particular desktop file. The bug mentions also "Desktop Menu Specification" http://specifications.freedesktop.org/menu-spec/menu-spec-latest.html#categ… Example: -------- http://svn.opensuse.org/svn/yast/trunk/packager/src/config/sw_single.desktop Currently it contains: Categories=Qt;X-SuSE-YaST;X-SuSE-YaST-Software; The reporter wants it to contain: Categories=Qt;X-SuSE-YaST;X-SuSE-YaST-Software;Settings;System; -------- Would it break anything? E.g., KDE/GNOME/ncurses control center? Thx && Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.

3 4

[yast-devel] Image-based Installation
by Lukas Ocilka 23 Apr '08

23 Apr '08

Hi, I've written a new blog entry for those who are interested in Image-based installation (That strange: dialog "Deploying Images..." in installation). See http://kobliha-suse.blogspot.com/ Have a lot of fun ;) Lukas

2 1

[yast-devel] Proposals and bug reports
by Jakub 'Livio' Rusinek 21 Apr '08

21 Apr '08

Hi, I made few proposals and bug reports in bugzilla. https://bugzilla.novell.com/show_bug.cgi?id=371793 - add per instance repo enabling https://bugzilla.novell.com/show_bug.cgi?id=380648 - yast's online update component tries to update not installed packages https://bugzilla.novell.com/show_bug.cgi?id=381506 - zypper and yast should tell what changes will be made with transaction https://bugzilla.novell.com/show_bug.cgi?id=381636 - zypper and yast start counting task completion percentage from 100% https://bugzilla.novell.com/show_bug.cgi?id=381638 - when clicking "abort", yast asks for saving changes, even when no changes were made https://bugzilla.novell.com/show_bug.cgi?id=381641 - lirc module request https://bugzilla.novell.com/show_bug.cgi?id=381643 - yast2 should remember search options Currently that's all. Please say, what do you think. -- Jakub 'Livio' Rusinek http://liviopl.jogger.pl/

2 1

[yast-devel] blog aggregation: Comet YaST
by Martin Vidner 21 Apr '08

21 Apr '08

Grr, http://planetsuse.org is down again, and still missing some team members, so I decided to play with Yahoo Pipes and create a little Comet YaST for the team: Web: http://pipes.yahoo.com/pipes/pipe.info?_id=rAY4JAQO3RGtU17gyZ1_DQ RSS: http://pipes.yahoo.com/pipes/pipe.run?_id=rAY4JAQO3RGtU17gyZ1_DQ&_render=rss Enjoy, and if you know of a blog that I forgot to add, let me know. -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- 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] Nuernberg YaST team - meeting 2008-04-17
by Duncan Mac-Vicar Prett 18 Apr '08

18 Apr '08

Nuernberg YaST team - meeting 2008-04-17 * tgoettlicher working on PackageKit backend for opensuse-updater-kde4. so far looking good. note that zypper backend is also functional. * jdsn working on the post install registration workflow, to be called from the updater applet. idea of merging registration configuration and regstration module in the process * kmachalkova updated the nfs client module to support nfsv4 :-), partitioner redesign (with aschnell) and looking into ncurses package selector to keep up with the new libzypp API. * sh has been fixing yast-ui bugs here and there together with the wizard changes. worried about perl-binding crashes. dangling pointers somewhere. * schubi. maintaining coolo :-) misc bugfixes in preparation for beta1 * dmacvicar. integrating libzypp changes with package selector. * mantel. worked mainly on jeos. * snwint. feature for extending braille support in the installation. it can now read the menu entries sending sound via usb. no critical bugs * shaas: package kit backend. patches implemented. strange bug when getting foreign (read non-english) names from rpm db. patches dont have self-provides * gs: sles9 bugs. looking into ncurses package selector too and libzypp api changes. * ma: preparing libzypp for beta1. next steps weak locks. implemented new way of creating capabilities * aschnell: partitioner redesign. few bugs apart of that. -- 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] Package callbacks - turning off
by Ladislav Slezak 16 Apr '08

16 Apr '08

Hi all, I have added these new functions into PackageCallbacks.ycp (yast2-2.16.52): RegisterEmptyProgressCallbacks() - registers empty callbacks RestorePreviousProgressCallbacks() - restores the previous registered callbacks (Pkg-bindings have a stack of registered functions for each callback, unregistering a callback means removing the function from the top of the stack.) If you need to temporarily turn off the callbacks then use the functions in a wrapper to ensure that the restoring function is always called: //disable callbacks PackageCallbacks::RegisterEmptyProgressCallbacks(); // Start the requested operation here DoActionWithoutCallbacks(); // restore the previous callbacks PackageCallbacks::RestorePreviousProgressCallbacks(); RegisterEmptyProgressCallbacks() sets empty callbacks for all progress callbacks, if you need to disable just a particular type of callback then use PackageCallbacks::SetDummy*Callbacks() and PackageCallbacks::Restore*Callbacks() functions. The new functionality is used to fix bug #377919, but it might be useful in other modules/scripts. -- 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

2 2

[yast-devel] liby2util is obsolete
by Stefan Hundhammer 16 Apr '08

16 Apr '08

FYI: We just moved liby2util to the unsupported/ branch in SVN. Those of you building YaST2 from SVN might want to delete the local check-out of liby2util. The remaining relevant parts of liby2util had been moved to yast2-core/liby2util-r or to the UIs some time ago. If you wonder why debug logging sometimes doesn't work, check /usr/lib for several versions of liby2util and delete the oldest ones - that one might be the result of y2makeall building and installing that obsolete liby2util. CU -- Stefan Hundhammer <sh(a)suse.de> Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- 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] named.conf
by Günther J. Niederwimmer 15 Apr '08

15 Apr '08

Hello, is there a possible way to deactivate in YaSt2-XXX Modules the "function" change named.conf ? some modules / scripts change the named.conf by using a ldap server ? The result in the most time, a non functioning named server ? -- mit freundlichen Grüßen / best Regards Günther J. Niederwimmer -- 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] Switch to new locks api
by Josef Reidinger 14 Apr '08

14 Apr '08

Libzypp uses new locking api now. You can find it in Locks.h. Works everything except unlock, which I hope implement today. few notes about functions - supported is reading and writing locks to file (default is file specified in zypp.conf). - loadLock append to locks available, if someone find useful setting new locks instead appending (something like restore old locks for frontend) it can be added. - addLock locks all result of query and also store this query for later save, also Selectabable can be locked, it uses optimally query to lock - saving locks must frontend explicit call - saving locks rewrite locks file (as unwanted side effect remove all comments) - existEmptyLocks and removeEmptyLocks is functions to maintance locks. First say if exist some locks which doesn't lock anything and second clean it. (ask for each lock by callback) - if locksfile.apply (see zypp.conf) is on (default) then after start of zypp locks is loaded and applied overview of new file format structure is 'attribute: value', locks (queries) separated by empty line attribute can be global_string (see addString for PoolQuery), string_type (values can be exact, substring, regex, glob), repo (repo allias), kind (Resolvable kind), require_all (if all attribute must match), case_sensitive (search case sensitive), install_status( values can be all, installed, not-installed) and all SolvAttributes with replaced colon ( s/:/_/g ). for example look [0]. default locks file path is /etc/zypp/locks Pepa [0] http://svn.opensuse.org/svn/zypp/trunk/libzypp/tests/zypp/data/PoolQuery/sa… -- 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] web based YaST
by Michal Zugec 14 Apr '08

14 Apr '08

When we discussed about web frontend, just look how Google do their staff with Python (for inspiration): http://www.youtube.com/watch?v=bfgO-LXGpTM http://code.google.com/appengine/docs/whatisgoogleappengine.html Miso -- 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] changes not in Factory
by Stephan Kulow 14 Apr '08

14 Apr '08

Hi, I tested what changes in YaST:SVN are not yet in Factory and this is the list. Please submit your changes, having them in SVN alone does not help :) Greetings, Stephan yast2/yast2.changes yast2/COPYRIGHT.english yast2/library/log/src/LogViewCore.ycp yast2/library/packages/src/PackageCallbacks.ycp yast2/library/system/src/FileChanges.ycp yast2/library/wizard/src/Wizard.ycp yast2/README yast2-add-on/yast2-add-on.changes yast2-add-on/src/add-on.desktop yast2-add-on/src/add-on-workflow.ycp yast2-add-on/src/add-on.ycp yast2-add-on/src/inst_language_add-on.ycp yast2-add-on/src/vendor.desktop yast2-add-on-creator/COPYRIGHT.english yast2-add-on-creator/README yast2-add-on-creator/src/add-on-creator.ycp yast2-add-on-creator/src/complex.ycp yast2-apparmor/COPYRIGHT.english yast2-apparmor/src/clients/GenProf.ycp yast2-apparmor/src/clients/LogProf.ycp yast2-apparmor/src/clients/SD_AddProfile.ycp yast2-apparmor/src/clients/SD_DeleteProfile.ycp yast2-apparmor/src/clients/SD_EditProfile.ycp yast2-apparmor/src/clients/SD_Report.ycp yast2-apparmor/src/include/subdomain/apparmor_ycp_utils.ycp yast2-apparmor/src/include/subdomain/config_complain.ycp yast2-apparmor/src/include/subdomain/profile_dialogs.ycp yast2-apparmor/src/include/subdomain/reporting_archived_dialogs.ycp yast2-apparmor/src/include/subdomain/reporting_dialogues.ycp yast2-apparmor/src/include/subdomain/reporting_utils.ycp yast2-backup/yast2-backup.changes yast2-backup/src/backup.desktop yast2-backup/src/Backup.ycp yast2-backup/src/help_texts.ycp yast2-backup/testsuite/tests/RestoreBackupSettings.out yast2-backup/testsuite/tests/WriteBackupProfiles.out yast2-backup/VERSION yast2-ca-management/yast2-ca-management.changes yast2-ca-management/COPYRIGHT.english yast2-ca-management/README yast2-ca-management/src/ca_mgm.desktop yast2-ca-management/src/common_cert.desktop yast2-ca-management/src/crlExport.ycp yast2-ca-management/src/new_cert.ycp yast2-ca-management/src/YaPI/CaManagement.pm yast2-core/agent-modules/testsuite/tests/dir.scr yast2-core/agent-modules/testsuite/tests/read1.scr yast2-core/agent-modules/testsuite/tests/write1.scr yast2-core/agent-modules/testsuite/tests/write2.scr yast2-core/agent-modules/testsuite/tests/write3.scr yast2-core/agents-perl/doc/ycp-pm-pod.html yast2-core/wfm/src/Y2WFMComponent.cc yast2-core/ylwrap yast2-country/COPYRIGHT.english yast2-country/timezone/data/timezone_raw.ycp yast2-country/timezone/testsuite/tests/GetDateTimeMap.ycp yast2-country/timezone/testsuite/tests/GetDateTime.ycp yast2-devtools/yast2-devtools.changes yast2-devtools/devtools/admin/all-packages yast2-devtools/devtools/bin/showy2log yast2-devtools/devtools/bin/version yast2-devtools/devtools/data/YaST2.dict.txt yast2-devtools/devtools/doc/skeletons/config/index.html yast2-devtools/devtools/skeletons/config/src/XXpkgXX.desktop yast2-devtools/devtools/skeletons/config-python/src/XXpkgXX.desktop yast2-devtools/yast2/ycp-mode.el yast2-devtools/ycpdoc/doc/example/deprecated.html yast2-devtools/ycpdoc/doc/example/example2.html yast2-devtools/ycpdoc/doc/example/example.html yast2-devtools/ycpdoc/doc/example/files.html yast2-devtools/ycpdoc/doc/example/intro.html yast2-devtools/ycpdoc/doc/example/mis.html yast2-devtools/ycpdoc/doc/example/modules.html yast2-devtools/ycpdoc/doc/example/struct1.html yast2-dhcp-server/yast2-dhcp-server.changes yast2-dhcp-server/src/dialogs2.ycp yast2-dhcp-server/src/dns-helps.ycp yast2-dhcp-server/src/dns-server-wizard.ycp yast2-dhcp-server/src/helps.ycp yast2-dns-server/yast2-dns-server.changes yast2-dns-server/src/dns-server.desktop yast2-dns-server/src/DnsServer.pm yast2-dns-server/VERSION yast2-drbd/yast2-drbd.changes yast2-fingerprint-reader/COPYRIGHT.english yast2-fingerprint-reader/README yast2-fingerprint-reader/src/dialogs.ycp yast2-fingerprint-reader/src/helps.ycp yast2-ftp-server/src/complex.ycp yast2-ftp-server/src/dialogs.ycp yast2-ftp-server/src/ftp-server.ycp yast2-ftp-server/src/FtpServer.ycp yast2-ftp-server/src/helps.ycp yast2-ftp-server/src/wid_functions.ycp yast2-gtk/yast2-gtk.changes yast2-gtk/VERSION yast2-hardware-detection/yast2-hardware-detection.changes yast2-hardware-detection/COPYRIGHT.english yast2-hardware-detection/README yast2-http-server/yast2-http-server.changes yast2-http-server/src/http-server.desktop yast2-http-server/src/YaST/httpdUtils.pm yast2-inetd/yast2-inetd.changes yast2-inetd/COPYRIGHT.english yast2-inetd/src/inetd.desktop yast2-installation/yast2-installation.changes yast2-installation/control/docs/control-doc.xml yast2-installation/src/clients/inst_network_setup.ycp yast2-installation/src/clients/inst_proposal.ycp yast2-installation/TODO yast2-instserver/yast2-instserver.changes yast2-instserver/src/instserver.desktop yast2-irda/yast2-irda.changes yast2-irda/COPYRIGHT.english yast2-irda/README yast2-irda/src/irda.desktop yast2-irda/src/ui.ycp yast2-iscsi-client/yast2-iscsi-client.changes yast2-iscsi-client/src/iscsi-client.desktop yast2-iscsi-server/yast2-iscsi-server.changes yast2-iscsi-server/src/iscsi-server.desktop yast2-kdump/COPYRIGHT.english yast2-kerberos-client/COPYRIGHT.english yast2-kerberos-client/README yast2-kerberos-client/src/dialogs.ycp yast2-kerberos-server/yast2-kerberos-server.changes yast2-kerberos-server/agents/ag_kadmin yast2-kerberos-server/COPYRIGHT.english yast2-kerberos-server/README yast2-kerberos-server/src/advanced_items.ycp yast2-kerberos-server/src/complex.ycp yast2-kerberos-server/src/helps.ycp yast2-kerberos-server/src/kerberos-server.desktop yast2-kerberos-server/src/KerberosServer.pm yast2-ldap/yast2-ldap.changes yast2-ldap/COPYRIGHT.english yast2-ldap/doc/ldap.html yast2-ldap/README yast2-ldap/src/LdapAgent.cc yast2-ldap-client/yast2-ldap-client.changes yast2-ldap-client/autodocs-ycp.ami yast2-ldap-client/COPYRIGHT.english yast2-ldap-client/src/ldap_client.rnc yast2-ldap-client/src/ldap.ycp yast2-ldap-client/src/Ldap.ycp yast2-mail/yast2-mail.changes yast2-mail/COPYRIGHT.english yast2-mail/src/mail.desktop yast2-metapackage-handler/yast2-metapackage-handler.changes yast2-metapackage-handler/src/OneClickInstallCLI.ycp yast2-metapackage-handler/src/OneClickInstallUI.ycp yast2-metapackage-handler/src/OneClickInstallWidgets.ycp yast2-metapackage-handler/src/OneClickInstallWorkerFunctions.ycp yast2-metapackage-handler/src/OneClickInstallWorker.ycp yast2-metapackage-handler/VERSION yast2-mouse/yast2-mouse.changes yast2-mouse/autodocs-ycp.ami yast2-mouse/src/mouse.desktop yast2-network/src/clients/dsl_proposal.ycp yast2-network/src/clients/isdn_proposal.ycp yast2-network/src/clients/lan_proposal.ycp yast2-network/src/clients/modem_proposal.ycp yast2-network/testsuite/tests/Provider.out yast2-nfs-client/COPYRIGHT.english yast2-nfs-client/src/Nfs.ycp yast2-nfs-client/src/routines.ycp yast2-nfs-client/src/ui.ycp yast2-nfs-server/yast2-nfs-server.changes yast2-nfs-server/src/nfs_server.desktop yast2-nis-client/COPYRIGHT.english yast2-nis-client/src/ui.ycp yast2-nis-server/yast2-nis-server.changes yast2-nis-server/COPYRIGHT.english yast2-nis-server/src/nis_server.desktop yast2-online-update/COPYRIGHT.english yast2-online-update/README yast2-packager/yast2-packager.changes yast2-packager/src/modules/SlideShowCallbacks.ycp yast2-packager/src/modules/SourceManager.ycp yast2-pam/autodocs-ycp.ami yast2-pam/COPYRIGHT.english yast2-pam/README yast2-pam/src/Autologin.ycp yast2-pam/src/PamSettings.ycp yast2-perl-bindings/doc/YaPI.html yast2-perl-bindings/doc/YaST__YCP.html yast2-phone-services/yast2-phone-services.changes yast2-phone-services/COPYRIGHT.english yast2-phone-services/README yast2-phone-services/src/config/answering_machine.desktop yast2-phone-services/src/config/fax.desktop yast2-phone-services/src/phone-services/answering_machine.ycp yast2-phone-services/src/phone-services/fax.ycp yast2-pkg-bindings/yast2-pkg-bindings.changes yast2-pkg-bindings/src/Target.cc yast2-printer/yast2-printer.changes yast2-printer/agent-ppd/src/md5.c yast2-printer/agent-ppd/src/PPDdb.cc yast2-printer/VERSION yast2-product-creator/COPYRIGHT.english yast2-product-creator/README yast2-product-creator/src/kiwi_dialogs.ycp yast2-product-creator/src/Kiwi.ycp yast2-product-creator/src/routines.ycp yast2-profile-manager/yast2-profile-manager.changes yast2-profile-manager/COPYRIGHT.english yast2-profile-manager/README yast2-profile-manager/src/dialogs.ycp yast2-profile-manager/src/profile-manager.desktop yast2-profile-manager/src/ProfileManager.ycp yast2-registration/yast2-registration.changes yast2-registration/COPYRIGHT.english yast2-registration/README yast2-registration/src/clients/inst_suse_register.ycp yast2-registration/src/clients/suse_register_auto.ycp yast2-registration/src/config/customer_center.desktop yast2-registration/src/config/suse_register.desktop yast2-repair/COPYRIGHT.english yast2-repair/README yast2-repair/src/osr_module_partition.ycp yast2-restore/yast2-restore.changes yast2-restore/src/helps.ycp yast2-restore/src/restore.desktop yast2-ruby-bindings/src/swig/CMakeLists.txt yast2-ruby-bindings/src/swig/ycp.rb yast2-ruby-bindings/src/swig/yui.i yast2-ruby-bindings/src/swig/yui.rb yast2-samba-client/yast2-samba-client.changes yast2-samba-client/COPYRIGHT.english yast2-samba-client/README yast2-samba-client/src/dialogs.ycp yast2-samba-client/src/routines.ycp yast2-samba-client/src/samba-client.ycp yast2-samba-client/src/SambaNetJoin.pm yast2-samba-client/VERSION yast2-samba-server/yast2-samba-server.changes yast2-samba-server/src/dialogs.ycp yast2-samba-server/src/helps.ycp yast2-samba-server/src/samba-server.desktop yast2-scanner/COPYRIGHT.english yast2-scanner/README yast2-schema/yast2-schema.changes yast2-schema/COPYRIGHT.english yast2-schema/README yast2-security/yast2-security.changes yast2-security/autodocs-ycp.ami yast2-security/COPYRIGHT.english yast2-security/src/helps.ycp yast2-security/src/routines.ycp yast2-security/src/security.desktop yast2-security/src/widgets.ycp yast2-slp/yast2-slp.changes yast2-slp/COPYRIGHT.english yast2-slp/README yast2-slp-server/yast2-slp-server.changes yast2-slp-server/src/slp-server.desktop yast2-squid/yast2-squid.changes yast2-squid/src/dialogs.ycp yast2-squid/src/helps.ycp yast2-squid/src/SquidACL_local_functions.ycp yast2-squid/src/SquidACL.ycp yast2-squid/src/Squid.ycp yast2-squid/src/store_del.ycp yast2-sudo/yast2-sudo.changes yast2-sudo/COPYRIGHT.english yast2-sudo/README yast2-sudo/src/sudo.desktop yast2-support/COPYRIGHT.english yast2-support/README yast2-tftp-server/yast2-tftp-server.changes yast2-tftp-server/COPYRIGHT.english yast2-tftp-server/README yast2-tftp-server/src/tftp-server.desktop yast2-transfer/agent-curl/src/CurlAgent.cc yast2-transfer/COPYRIGHT.english yast2-transfer/README yast2-update/yast2-update.changes yast2-update/src/clients/update_proposal.ycp yast2-update/src/modules/Update.ycp -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 10

[yast-devel] Pattern icons
by Duncan Mac-Vicar P. 12 Apr '08

12 Apr '08

While trying the new icon eyecandy in the package selector, I figure out .pat files have wrong icons (10.3) - patterns with no icons -> yast-system -> should be pattern-generic (this one is autocorrected by the code right now) - kde devel pattern should use pattern-kde-devel - gnome devel pattern should use pattern-gnome-devel - app armor should use pattern-apparmor - .NET environment should use pattern-mono - Base system should use pattern-basis and not the novell box - Base development -> pattern-basis-devel There are more, but those appear at first sight, because we have cool icons but not use them. I tested on 10.3, but a quick look reveals factory patterns have the same icons. Duncan -- 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] Debugging kernelcrash in installation system
by Bernhard Walle 11 Apr '08

11 Apr '08

Hi YaST hackers, I observe a kernel bug that happens only in YaST partitioning code. Probably the partitioner does some "weird" thing (load modules, etc.) that triggers the bug. How to debug this? Is it possible to trigger the same hardware detection code in a running system? Or do I need to rebuild the kernel (easy) and the installation initrd (because of modules)? Any suggestions appreciated. Bernhard -- 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] yast style guide
by Martin Schmidkunz 11 Apr '08

11 Apr '08

Hi everybody, after some discussion and work I would like to present a first draft of a YaST style guide to you: http://en.opensuse.org/Image:Ysg.pdf The intention of the style guide is NOT to dictate every pixel in every module but to make some basic actions and behaviors consistent which increases usability. The work was mostly done by Lukas (locilka) and me. Nonetheless this is just a draft and I would like to see it as a base for further discussion. First of all because two people cannot represent the large variety of opinions you all have and what all of you consider as acceptable. A style guide which is not supported by you, the developers, is IMHO useless (and we already have one useless style guide :-)) So: * Do you think the extent of the current draft is sufficient? * Which issues are missing? * Which ones should be removed? * Are there any contentwise issues you object/agree upon? I am looking forward to you 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. 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

3 7

[yast-devel] SWIG bindings for libyui available: YCP-free YaST dialogs !
by Klaus Kaempf 11 Apr '08

11 Apr '08

Things you do with some spare time in the evening ... ;-) Hi, I just imported 'libyui-bindings' into the YaST svn repository, providing SWIG bindings (well, just Ruby for now) for libyui. For the curious: svn co http://svn.opensuse.org/svn/yast/trunk/libyui-bindings cd libyui-bindings mkdir build cd build cmake .. make cd ../swig/ruby/examples ruby hello_world.rb Enjoy ! Now back to sat-solver and libzypp ... Klaus -- 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] new PoolItem/ResObject call isRelevant()
by Stefan Schubert 10 Apr '08

10 Apr '08

Hi, this is interesting for all UIs concerning package handling. This call gives an answer to "Is this PoolItem/ResObject interesting for user and should it be shown ?" /** Returns true if the solvable is relevant which means e.G. for patches * that at least one package of the patch is installed. */ bool isRelevant() const; 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 1

[yast-devel] YaST2 meeting Prague - 8.4.2008
by Michal Zugec 10 Apr '08

10 Apr '08

Czech YaST2 team (Prague) meeting 2008-04-08 ======================================= Present: jkupec, jreidinger, jsrain, juhliarik, jsuchome, locilka, lslezak, mvidner, mzugec Absent: kmachalkova (exchange) Minutes: mzugec Next minutes: jsrain libzypp --------- jkupec and jreidinger are working on pool query in libzypp (pool query API and locks, unlocking) Product Creator -------------------- Full repository URL (=including password for https) has to be saved into kiwi configuration file (bnc#376666). Timezone & NTP ----------------------- Timezone module now distinguishes between one-time synchronization and saving the NTP client configuration (FaTE#302917) SuSEFirewall2 -------------------- There are special rules from bridged devices (mostly used for network in virtualized environment). sshd_config SCR agent -------------------------------- Two agents were merged into one because of unification. InstExtensionImage --------------------------- This YCP module newly uses the `extend` command which can update a running inst-sys with an RPM content. Control center ------------------- inst_sources desktop file was removed because that functionality is already in packager. From the same reason was removed desktop files for route and dns. Heartbeat -------------- CLI Command line mode support is being implemented. Sysconfig ------------- Fixed problem with writing "" string in CLI. IOgrind, valgrid -------------------- iogrind is Michael Meeks' I/O profiler and visualizer. Mvidner has packaged it as Buildservice project: http://mvidner.blogspot.com/2008/04/iogrind-in-opensuse-build-service.html Log compression ------------------------ The y2logs in /var/log/YaST2 can be very large (20-30MB), but they compress very well. Now they're compressed with gzip (FaTE#300637) Devtools ------------ There is possibility to run make check without a prior make install (FaTE#2306). Added a -M and -I switch to y2base for specifying additional module and include pathes. (The switches are taken from ycpc , different means like passing colon-separated directories via an environment variable are also feasible.) Network ----------- New features: - support for default gateway metrics (FaTE#301948) (http://mzugec.blogspot.com/2008/04/yast2-network-metric.html) - option in UI for dhcpcd "-G" - don't touch default route (bnc#366948) Printer --------- - LPD protocol switching support (bnc#120086) -- 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] new builtin sublist
by Arvin Schnell 09 Apr '08

09 Apr '08

Hi, I have added a new builtin to YCP (yast2-core 2.16.46) called sublist. More or less like substring. ciao Arvin -- Arvin Schnell, <aschnell(a)suse.de> Software Engineer, Research & Development 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 3

[yast-devel] Product plans
by Benji Weber 09 Apr '08

09 Apr '08

Greetings All, Currently in factory Product::name, Product::distversion etc all return an empty string. Probably because there is no product installed. Is it planned to have products installed once zypp supports them again, or will Product.ycp obtain its data from somewhere else? Or is Product.ycp being dropped completely and I should use something else? At present I am using Product to determine which instructions from a YMP match the installed system. Should I compare against something else, like /etc/SuSE-release? https://bugzilla.novell.com/show_bug.cgi?id=373367 was my report for no product installed. -- Benjamin Weber -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

9 13

[yast-devel] YaST and kexec
by Arvin Schnell 07 Apr '08

07 Apr '08

Hi, normally I don't criticise other peoples code but I just saw the kexec code in YaST. Just a call "kexec -e"! The current program and kernel is gone: No umount, no sync, no SCR flush, no start-script cleanup, no halt according to AutoYaST, no nothing. Use the method that has been there for years: Tell linuxrc what to do. Look at yast_inf_finish.ycp. I already pointed there last week on IRC. ciao Arvin -- 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] YaST2-sound rebuild
by Dean Hilkewich 07 Apr '08

07 Apr '08

Is it possible to make the src.rpm package for the YaST2-sound generate a new list of supported cards from the alsa modules that are present on the system? I see the script that is supposed to do that in yast2-sound-2.16.4/data/src but it doesn't get triggered when doing a rpmbuild --rebuild. This way adding new soundcard support in the YaST module would be easier if the card is supported by a newer kernel or alsa update. -- 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] YCP and Float
by Arvin Schnell 07 Apr '08

07 Apr '08

Hi Protectors Of YCP, which is the easiest way to display a float with 3 digits after the decimal point and rounding to zero? ciao Arvin -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 6

[yast-devel] Small usability comment on YaST2 installer
by Dominique Leuenberger 07 Apr '08

07 Apr '08

Hi, Last weekend I gave a openSUSE 11.0 Alpha3 disk to a friend and made him install openSUSE... I tried to follow a bit what he did and where issues were. The biggest thing I've seen that he was to much attracted by the green next button, even though the system was busy and next not available (like on first screen, when system is initializing.. the next button is green and as there is nothing else, it's very attractive to click it... ). Otherwise he was not that much worried by the installation... except: the first user he wanted to create, as a typical windows user, he wanted to name it Admin... ;) but even that's a valid user... The partition proposal was a bit weird... he had a 40GB disk, 20GB filled with windows.. openSUSE suggested to delete windows and use the whole disk... of course *I* would agree to this.. he was not really pleased. Dominique -- 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] Package selector (qt) now has unmaintained packages filter
by Duncan Mac-Vicar Prett 04 Apr '08

04 Apr '08

Just select packages from Repository @System, and then as a secondary filter select "Unmaintained", and you will see all packages not available in any repository, but installed. In case Katarina or Ricardo want to mimic this, it is pretty easy, as once you have installed packages (either by status or from repo().isSystemRepo() ), you seect the ones whose selectable candidate is null. I think in the Qt selector it was like 7 lines of code. Duncan -- 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] Help Texts and Help Buttons in YCP Dialogs
by Stefan Hundhammer 04 Apr '08

04 Apr '08

We needed this to make removing the permanent help panel in the NCurses wizard possible, but it might also be useful at other places (Popup.ycp?): You can now declare a push button a "help button". When activated, that button will now try to automatically show the help text that belongs to its dialog. The help text is stored as a (new) widget property `HelpText in some parent widget in that dialog, preferably a layout widget like `VBox() or `HBox(). Example: (ycp-ui-bindings/examples/HelpText.ycp) { UI::OpenDialog( `VBox(`id(`mainLayout), `Label("Hello, World!"), `HBox( `PushButton(`opt(`helpButton ), "&Help"), `PushButton(`opt(`default ), "&OK") ) ) ); UI::ChangeWidget(`mainLayout, `HelpText, "Oh, come on, do you really need help for this?" ); UI::UserInput(); UI::CloseDialog(); } Please note that we might do cooler stuff with this new `HelpText widget property, so for now please use it in this way. In the future, we might use this for tool tip help, so the dialog's help text should really be in a container widget like this VBox and not on the help button itself (otherwise the tool tip of that help button would be the entire dialog's help text - not desirable). The help button will traverse up its widget hierarchy and use the topmost `HelpText it can find. CU -- Stefan Hundhammer <sh(a)suse.de> Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- 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] Minutes of Prague YaST2 Team Meeting: 2008-04-01
by Martin Vidner 04 Apr '08

04 Apr '08

Minutes of Prague YaST2 Team Meeting: 2008-04-01 ================================================ http://en.opensuse.org/YaST/Team Present: jkupec, jreidinger, jsrain, jsuchome, juhliarik, kmachalkova, locilka, lslezak, mvidner, mzugec Absent: - Minutes: mvidner Next Minutes: mzugec Package Management ------------------ "zypper verify" implemented (fate#301918). Repository priorities implemented in zypper and yast following ma's work in libzypp (bnc#369827). Persistent package locks being implemented using generic queries (fate#120118). Redesigned ncurses packager widget is in the trunk now: http://duncan.mac-vicar.com/blog/archives/303 Pkg callback registration will use function pointers instead of strings (fate#302296). Get patch metadata also via Fedora's updateinfo.xml (one file instead of many). "I think there is no Fate or Bugzilla entry for that, only the unbound desire to get rid of superfluous data and complexities, to simplify it, improve it, and make customers happy :O)" Installation ------------ System installation will be extra fast, stay tuned for details. Kexec instead of reboot during the installation (fate#303395). Second stage of installation (after reboot^Wkexec) is non-interactive by default (fate#303396). Perl runtime errors will not make YaST crash now (fate#412). Miscellaneous ------------- Product Creator is catching up with Kiwi for 11.0, gets support for Kiwi profiles. Remember to run "make spellcheck" from time to time. Keep maintainer overview table up to date, help out colleagues by serving as a backup: http://en.opensuse.org/YaST/Maintainers -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- 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] Let's make YaST more attractive
by Katarina Machalkova 04 Apr '08

04 Apr '08

Hi, yast hackers, One of the action items of last YaST workshop was to make YaST look cool and sexy so that it is more attractive to our users. We have already make a great step towards achieving this goal, but we're somehow omitting two target groups: 1. text-mode (ncurses) users and 2. female audience. But our interface still lacks warm, soft, pastel colour shades that are so appealing to many women, so they may feel uncomfortable using YaST. This new default skin for xterm terminals tries to kill two birds with one stone: http://en.opensuse.org/Image:Pink-yast.jpg It gives entirely new look to text-mode interface and at the same time, is makes it very attractive for girls and women. It will be part of yast2-ncurses 2.16.21, that will come out of Factory very soon. Enjoy! frozenB. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter

9 10

[yast-devel] failing packages
by Stephan Kulow 04 Apr '08

04 Apr '08

Hi, From what I can tell they all fail in their test suites: -rw-r--r-- 1 root root 63149 4. Apr 03:29 yast2-dhcp-server -rw-r--r-- 1 root root 84277 4. Apr 03:20 yast2-dns-server -rw-r--r-- 1 root root 54827 4. Apr 03:02 yast2-firewall -rw-r--r-- 1 root root 48150 4. Apr 03:03 yast2-isns -rw-r--r-- 1 root root 151021 4. Apr 03:09 yast2-network -rw-r--r-- 1 root root 94763 4. Apr 03:24 yast2-samba-server -rw-r--r-- 1 root root 100815 4. Apr 03:20 yast2-users Greetings, Stephan -- 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] builtin toterm
by Arvin Schnell 03 Apr '08

03 Apr '08

Hi YaST Hackers, the toterm builtin in YCP (yast2-core 2.16.42) has been extended a bit. It: - also accepts a symbol - accepts a symbol and a list See documentation for examples. ciao Arvin -- 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] Time for a change: Let's rename YaST
by Lukas Ocilka 03 Apr '08

03 Apr '08

Hi, Just now it might be the right time to change the name we have been using for years 'YaST'. It seems we (and our users) still consider this name being somehow 'geeky' [0]. Why should we do that :)? Well, I've found that people still don't know how to write it and similarly as a language evolves, we could follow our users and make it easier for them. Currently several mutations are in use: 'YaST', 'Yast', 'yast', 'YAST', ... The change could be trivial 'YaST' -> 'YAST' (because it is an abbreviation). We could compare the proposed change to 'SuSE' -> 'SUSE' (currently 'openSUSE', of course). Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno. [0] http://dictionary.reference.com/browse/geeky 1. a peculiar or otherwise dislikable person, esp. one who is perceived to be overly intellectual. 2. a computer expert or enthusiast (a term of pride as self-reference, but often considered offensive when used by outsiders.)

13 23

[yast-devel] Nuernberg YaST team - meeting 2008-04-01
by Duncan Mac-Vicar P. 03 Apr '08

03 Apr '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Nuernberg YaST team - meeting 2008-04-01 - - Gabi is back will look at possible ncurses open features example: combobox inputfield empty label, we dont want to use space if there is no label. - - remove help sh: extend dialog to store help text? could make more sense than fixing ncurses. - - perl bindings libstorage API has structs, ints and stl string. strange bug that creates a crash. sh has spent quite some time debugging it. yast bootloader crashes. easy to reproduce. - - autoyast perl bootloader testing. dmacvicar will look into the module to see if perl-Test-Simple could be used for basic exercises, then will pass on hubert and snwint. - - tgoettlicher: refresh repositories part of the updater (instead of having the helper doing it all) no time, no feature. no good reasons. we should not do this. - - idea in bugzilla, package mgmt: send dbus signal when adding and removing repos and other events. question: which dbus signal? is a packagekit spec? - - google soc deadline extended 1 week talk about idea of having swig ycp output, sh: UI bindings are automated somehow. dmacvicar to post idea in wiki (done) - - aschnell: evms proposal bug - - control center project. low priority right now. 1st priority is to get opensuse updater, package selector and pathes working nice. - - not installing product discussion and possible side effects. - - discussion about sp2 request: Qt package selector autodeps check on or off configurable. autosolv off default. pattern selection sometimes does not trigger changes. In case that would make sense (most people think it does not) would we need a YaST wide configuration? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFH8/x5zR62qWZ+QtERAradAKCwZyDCNhFqkQyLL5DNRaRsE1FUOwCggz4N v/xVdOp0xWbXE6GWaGKkblo= =KApS -----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 1

[yast-devel] SCR Agents: etc_ssh_sshd_config.scr vs sshd.scr
by Lukas Ocilka 02 Apr '08

02 Apr '08

Hi Hackers, Please, before you write your own SCR agent, check whether such agent doesn't already exist. We currently have two different SCR agents that modify the very same file 'etc_ssh_sshd_config.scr' [0] and 'sshd.scr' [1]. On the other hand, creating a dependency on another YaST module just because of such agent doesn't make sense. In such cases, it is better to unify and move the client(s) to some other package (often yast2.rpm). Why am I writing this here? Well, this is an example I've found unintentionally... [0]http://svn.opensuse.org/svn/yast/trunk/kerberos-client/agents/etc_ssh_ssh… [1]http://svn.opensuse.org/svn/yast/trunk/sshd/agents/sshd.scr -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.

6 12

[yast-devel] Type check in package callbacks => binary incompatibility of *.ybc
by Ladislav Slezak 02 Apr '08

02 Apr '08

Hi developers! I just have implemented compile time type check in package callbacks (see fate#302296 or bnc#51913). In short: function references are now used instead of strings (e.g. Pkg::CallbackProgressDownload(PackageCallbacks::ProgressDownload) instead of Pkg::CallbackProgressDownload("PackageCallbacks::ProgressDownload") which was error prone). The advantage is that registering an invalid function is found at compile time now. Thanks to this feature I have found some problems and fixed them (missing callback functions, wrong parameters etc...) The disadvantage is that the binary compatibility of *.ybc files is broken now. Use 'y2tool y2compile' from yast2-devtools to recompile the modules after installing new yast2-pkg-bindings, yast2-packager and yast2. The implementation of the package callbacks has been moved to yast2.rpm to break cyclic dependency between yast2 and yast2-packager. Another change is that PackageCallbacksInit.ycp module is obsoleted now, but remains for backward compatibility. Use PackageCallbacks::InitPackageCallbacks() instead of PackageCallbacksInit::InitPackageCallbacks() in your modules. I have also adapted the other yast packages which register their own callbacks (autoinstallation, online-update, product-creator), please check my changes and submit the new package. The change was quite large (and spread across 6 packages), if you find any problem with the new callbacks then contact me. Ladislav -- 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] establish states moved from ResStatus to PoolItem
by Stefan Schubert 02 Apr '08

02 Apr '08

Hi, the establish states are no longer available in the ResStatus cause they will be evaluate by the solver while every call of: PoolItem.h /** Whether the items requirements are met. */ bool isSatisfied() const; /** Whether the items requirements are broken. */ bool isBroken() const { return ! isSatisfied(); } Unfortunately I have no write permission to YaST svn, so could you please fix the concerning packages. Thank you. I have already fixed zypper,libzypp-bindings and libzypp-testsuite. Greetings Stefan Index: gtk/src/yzyppwrapper.cc =================================================================== --- gtk/src/yzyppwrapper.cc (Revision 45958) +++ gtk/src/yzyppwrapper.cc (Arbeitskopie) @@ -517,7 +517,7 @@ if (impl->type == Ypp::Package::PATCH_TYPE) { if (impl->zyppSel->hasInstalledObj()) { // broken? show as available - if (impl->zyppSel->installedPoolItem().status().isIncomplete()) + if (impl->zyppSel->installedPoolItem().isBroken()) return false; } } @@ -1568,7 +1568,7 @@ if (!patch) continue; if (!(*it)->hasInstalledObj()) - if (!(*it)->hasCandidateObj() || !(*it)->candidatePoolItem().status().isNeeded()) + if (!(*it)->hasCandidateObj() || !(*it)->candidatePoolItem().isBroken()) continue; category = addCategory (type, patch->category()); break; Index: ncurses-pkg/src/NCPackageSelector.cc =================================================================== --- ncurses-pkg/src/NCPackageSelector.cc (Revision 45958) +++ ncurses-pkg/src/NCPackageSelector.cc (Arbeitskopie) @@ -659,7 +659,7 @@ if ( selectable->hasInstalledObj() ) // patch installed? { // display only if broken - if ( selectable->installedPoolItem().status().isIncomplete() ) + if ( selectable->installedPoolItem().isBroken() ) { displayPatch = true; yuiWarning() << "Installed patch is broken: " << patchPtr->name().c_str() << " - " @@ -670,7 +670,7 @@ { if (selectable->hasCandidateObj() && - selectable->candidatePoolItem().status().isSatisfied() ) + selectable->candidatePoolItem().isSatisfied() ) { //patch not installed, but it is satisfied (updated to the version patch requires) //all that is missing are patch metadata, so let's display the patch @@ -688,7 +688,8 @@ // isSatisfied(): all packages are installed, therefore the isNeeded() flag // isn't set. BUT the patch meta data aren't installed and therefore it makes // sense to install the patch - if ( selectable->candidatePoolItem().status().isNeeded()) + if ( selectable->candidatePoolItem().status().isInstalled() + && selectable->candidatePoolItem().isBroken()) { displayPatch = true; } @@ -1397,7 +1398,7 @@ descr += "<br>"; if ( selectable->hasInstalledObj() - && selectable->installedPoolItem().status().isIncomplete() ) + && selectable->installedPoolItem().isBroken() ) { descr += _( "----- this patch is broken !!! -----" ); descr += "<br>"; Index: pkg-bindings/src/Resolvable_Properties.cc =================================================================== --- pkg-bindings/src/Resolvable_Properties.cc (Revision 45958) +++ pkg-bindings/src/Resolvable_Properties.cc (Arbeitskopie) @@ -293,7 +293,7 @@ info->add(YCPString("interactive"), YCPBoolean(patch_ptr->interactive())); info->add(YCPString("reboot_needed"), YCPBoolean(patch_ptr->reboot_needed())); info->add(YCPString("affects_pkg_manager"), YCPBoolean(patch_ptr->affects_pkg_manager())); - info->add(YCPString("is_needed"), YCPBoolean(it->status().isNeeded())); + info->add(YCPString("is_broken"), YCPBoolean(it->isBroken())); } // dependency info Index: pkg-bindings/src/ProvideProcess.cc =================================================================== --- pkg-bindings/src/ProvideProcess.cc (Revision 45958) +++ pkg-bindings/src/ProvideProcess.cc (Arbeitskopie) @@ -54,7 +54,7 @@ } if (!provider.status().isInstalled() - && (!onlyNeeded || provider.status().isNeeded()) ) // take only needed items (e.G. needed patches) + && (!onlyNeeded || provider.isBroken()) ) // take only needed items (e.G. needed patches) { // deselect the item if it's already selected, // only one item should be selected -- ******************************************************************************* 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

[yast-devel] Tiny change to FormatSizeWithPrecision
by Arvin Schnell 01 Apr '08

01 Apr '08

Hi, are there any objections to change FormatSizeWithPrecision to return "1 MB" instead of "1024 kB" and alike? Normally, when displaying e.g. package sizes, it shouldn't matter but in storage I want to display stribe sizes and such things where I have powers of two and the shorter "1 MB" looks better. ciao Arvin -- Arvin Schnell, <aschnell(a)suse.de> Software Engineer, Research & Development 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 1

[yast-devel] [Announcement] New YaST module
by Lukas Ocilka 01 Apr '08

01 Apr '08

Hi, I've just found a new YaST module completely written without YCP and SCR. And no, this is not a joke! See more at: http://www.codedread.com/yastframe.php Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.

2 1

[yast-devel] Truncating changes file
by Lukas Ocilka 01 Apr '08

01 Apr '08

Hi, I've just sent new yast2-installation into autobuild and one thing made me stop to think about our changes files: yast2-installation-2.16.28.tar.bz2 size: 225750 yast2-installation.changes size: 213761 Is it really wort having 208 kB of changes for such package? Is anybody interested in it? In my opinion, users are interested in the changes that have been made since the last release or codebase change. Ancient changes are just filling-up the RPM database, that's all. My proposal is to keep the changes file untouched but change the `make package` script to cut off a.) changes that belong to some older release (e.g., 10.2 vs 10.3) b.) changes that belong to some older codebase (e.g., 10.3 vs 11.0) We can simply use the package VERSION which should be increased by one with every release (currently 2.16, next will be 2.17). This would make our installation smaller, RPM faster and we would still keep our changes in SVN. The build service checks would have to be changed probably because they check for inconsistencies in changes files too. What do you think of that? Any better idea? Thx && Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.

3 3