YaST Development April 2008

yast-devel@lists.opensuse.org

29 participants
44 discussions

[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

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

YaST Development April 2008