September 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] yast2-qt Title Bar Enhancements
by Thomas Goettlicher 01 Oct '08

01 Oct '08

I've added some enhancements to the title bar shown by the window manager in yast2-qt. Until now yast2-qt windows had names like YaST, YaST <2>, YaST <3>... That made it difficult to keep an overview of the open YaST modules. Most modules with wizards have there own desktop file with an icon and a list of localized names. The icon has been displayed in the title bar for a long time. The localized name can be used for the window title by now (libyui 2.17.12, qt 2.17.12, yast2 2.17.34). The command to make this happen is pretty simple. Similar to SetDesktopIcon you can use SetDesktopTitle to set the window title of a wizard. Example: Wizard::SetDesktopTitle("lan"); SetDesktopTitle searches for the desktop file in the directory /usr/share/applications/YaST2 and retrieves the localized name. This string is shown in the window title with a prepended "YaST2". If we want to benefit from this enhancement I'd like to ask the maintainers who use wizards to add this single line. Please let me know if you have any objections, suggestions or questions. Thanks Thomas -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 8

[yast-devel] Beware: libzypp-5.13.0 - WhatProvides::empty retruns invers result.
by Michael Andres 29 Sep '08

29 Sep '08

Hi! In libzypp-5.13.0 zypp::sat::WhatProvides::empty retruns the inverse result. That's the reason why e.g zypper in -C 'capability' fails. Just WhatProvides::empty is affected, size and iterator behave as expected. libzypp-5.13.0 is on beta2, so remember this in case of strange error reports. Fixed in 5.13.1 -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma(a)novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1

[yast-devel] RC1: Prague YaST team meeting 2008-09-23
by josef reidinger 29 Sep '08

29 Sep '08

Prague YaST team meeting 2008-09-16 =================================== Present: jkupec, jreidinger, jsrain, juhliarik, jsuchome, kmachalkova, locilka, mzugec Absent: mvidner, lslezak Minutes: jreidinger Next minutes: jsrain libzypp/zypper (jkupec) ----------------------- Keyring callbacks now take KeyContext object to provide some context (repository) information in which the GPG-related issue appeared. Zypper and YaST have been adapted to show this info (bnc #370223). new zypper command: 'licenses' - provides information about licenses of installed packages Continues to work on commit history. Discussion about separate folder /var/log/zypp versus saving logs to /var/log/YaST2/. Documented at http://en.opensuse.org/Libzypp/Package_History jsuchome --------- more modules support dynamic load rpm in inst-sys. kmachalkova ----------- All AA modules now have the very basic commandline support (print "This module does not support commandline" instead of opening UI in CLI mode) (bnc #269891) Default portmapper is rpcbind instead of portmap (which is still supported). Neither portmap nor rpcbind were in inst-sys, making mounting nfs directories and installation onto nfsroot impossible. Rpcbind has now been added and libstorage adjusted to use it. (Bnc #427428) On diskless machine (where automatic partitioning proposal is not possible and user has to modify partitioning by himself), expert partitioner is now started instead of trying to have user select one of (non-existent ;-) ) hard disks to partition. This enables him to mount nfs root or launch iSCSI client. Bnc (#421541) locilka ------- (During upgrade) libzypp doesn't provide any information about old products installed (bnc #429177) -- 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] Restarting YaST
by Lukas Ocilka 29 Sep '08

29 Sep '08

Hi, I've just added a new possibility to restart any YaST module/client while running it from /sbin/yast(2). So far only 'online_update' and 'menu' could have been restarted. The new feature is in yast2-2.17.33. Restarting is easy: * Create /var/lib/YaST2/restart_yast file * Exit the module/client * --> YaST is restarted * Check whether the file exists (which means got 'restarted') * Remove that file Note: 'online_update' and 'menu' behave the same as before. Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.

1 0

[yast-devel] [PATCH] yast2 exit codes
by Stanislav Visnovsky 26 Sep '08

26 Sep '08

Hi! This is a long standing issue: the YCP clients cannot set the exit code for the yast2 process. This makes a big piece of command line functionality unusable. Attached patch implements the following behavior: Exit codes: 0 - everything fine 1 - too few arguments 5 - error in arguments 16 - generic client error 16 + x - client returned 'x' as exit code This is not exactly nice, but it keeps backward compatibility with the already returning exit codes. Basically, if error code is >0 and < 16, this is parameter handling error. if >= 16, you get the exit code by subtracting 16. 0 means no errors. Clients can return only 2 types of exit codes: boolean: true - exit code 0 false - exit code 16 integer: 16 + value Examples: return nil; => exit code 0 return; => exit code 0 return true; => exit code 0 return false; => exit code 16 return "true"; => exit code 0 (it's string!) return 2; => exit code 18 return -15; => exit code 1 return -100; => exit code 172 (process exit code is unsigned) If there are no objections, I will commit the patch + documenting the behavior in man page and in the generated docs. Stano

4 9

[yast-devel] IP netmask broadcast address calculator
by Johannes Meixner 26 Sep '08

26 Sep '08

Hello, I am looking for a "IP address calculator" in YCP. For example when I have IP address and netmask I like to get the resulting broadcast address (not only for 8 16 24 bit netmasks). Or when I have only a IP host or network address, I like to get the usual netmask for it depending on the address block, e.g. 127.x.x.x -> 255.0.0.0 10.x.x.x -> 255.0.0.0 192.168.x.x -> 255.255.255.0 (or 255.255.0.0 ?) In particular it would be nice if it accepts the various ways to specify the netmask, e.g. nnn.nnn.nnn.nnn/mm versus nnn.nnn.nnn.nnn/mmm.mmm.mmm.mmm I guess there is already code in whatever YCP module but where is it? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1

[yast-devel] Nuernberg YaST team - meeting 2008-09-23
by Duncan Mac-Vicar Prett 25 Sep '08

25 Sep '08

Nuernberg YaST team - meeting 2008-09-23 present: aorlovskyy, aschnell, dmacvicar, gs, jdsn, ma, schubi, sh, shaas, snwint, tgoettlicher, mantel minutes: shaas Topics ------ - Installation theming problems bnc#427632 - Wizard with steps doesn't update step status icons bnc#429070 - Richtext unreadable because of patterned background - Boost library is not ready (the maintainer Philipp Thomas is on vacation) -- 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] YCP tricks
by Stanislav Visnovsky 25 Sep '08

25 Sep '08

Hi! I've created a new wiki page for YCP/YaST development tricks and code snippets. http://en.opensuse.org/YaST/Development/Tricks Feel free to update the page! Stano P.S. I hope this does not duplicate any other page. If yes, let me know. -- 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] SSH key changes between stage 1 and stage 2
by Arthur Rodrigo Sawazachi Valadares 24 Sep '08

24 Sep '08

Hi, I noticed that after you're done with stage 1 and the systems reboot, on stage 2 the SSH host key is different, which fires a warning for the client who already recorded the key in it's know_hosts. I think it would be interesting to avoid this issue by copying the keys from the RAM in stage 1 to the disk after partitioning it and before installing the system in it. I wanted to hear any comments or suggestions from this list and check if there's anything this behavior might affect for the worse. Thank you, -- Arthur V. -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 3