September 2007 - 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] 3 questions about yast....
by Roberto Angelino 28 Feb '08

28 Feb '08

OK. First some background: My customer has written a sles9->sles10 live update installation script. I just ran it via ssh. It uses autoyast (the sles10 version) and it installs onto a clean partition (i.e., a partition that isn't running sles9). It works, but they've had to mess with some of the ycp files. Note this script is specialized to their nodes because they only ship 2-3 type of nodes. It's not a general purpose script. Here are the 3 questions they have (for sles10 version): 1) After yast completes installation (i.e., post-install), the fstab is created. What yast module makes this call? It has to be in yast2-installation, but I can't find the connection between the installation and yast2-storage where WriteFstab() lives. 2) How does yast determine what the source partition to mount is? 3) bootloader_finish.ycp breaks the install at the end. They got the install to work by commenting out everything in bootload_finish.ycp. What does this file do? Thanks -robert -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

6 10

[yast-devel] Huge window during package install
by Boyd Timothy 01 Oct '07

01 Oct '07

I'm trying to duplicate the following bug so I might be able to fix it: https://bugzilla.novell.com/show_bug.cgi?id=309049 Unfortunately, I have not been able to reproduce it on my computer. Someone yesterday in #opensuse-gnome mentioned that they had seen it a few times but not always. In the times they saw it, there was no window decoration around the window. In other words, there was no window decoration (title bar, etc.). Does anyone know of a case where yast will create a window without window frames? Thanks for any direction someone may have! -Boyd -- 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] added some features to y2makeall
by Christian Kornacker 27 Sep '07

27 Sep '07

i've added a little "hack" to y2makeall to enable building libzypp, build/link YaST (pkg-bindings) against this libzypp and install both on a specified --prefix. furthermore, it's now possible to use an icecream environment for building, which should make the build process a little faster. "why should I use this" you may ask... the first thing that comes in mind is, you can quickly build/test a different YaST version without changing your system's YaST installation and without the need for a VM. unfortunately, not all YaST agents are "y2makeall compatible" yet. i.e. the "storage" agent depends on some "installation" modules (IIRC), the "installation" agent again depends on "storage". another problem is the XVersion file. XVersion gets installed in $sysconfdir by yast2 but the configure scripts search in $coresysconfdir which is $prefix/$sysconfdir. so, finally, these are the new y2makeall parameters: --build-libzypp build your own libzypp --libzypp-source libzypp source dir --libzypp-prefix libzypp install prefix --icecream build using icecc --icecream-prefix defaults to /opt/icecream --jobs make jobs to run simultaneously old one which is used now: --prefix YaST install prefix of course comments are highly appreciated... thanks, Christian -- 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] Branching openSUSE 10.3 -- Proposal
by Lukas Ocilka 25 Sep '07

25 Sep '07

Hi, Despite the fact that most of us are still fixing openSUSE 10.3 bugs, there are some commits that should go to the "after 10.3 only". Our proposal is to branch openSUSE 10.3 on Monday 24th after 18:00 (with RC2 if possible)- Mvidner is a volunteer for doing that :) Please, speak up if you don't like to proposal. Thanks & Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic

5 5

[yast-devel] YaST: 10.3 installation testing
by Steffen Winterfeldt 24 Sep '07

24 Sep '07

Hi, who never needs to test the first stage installation workflow, can safely delete this mail. :-) Starting with beta1, a shiny new linuxrc is used. In particular, you can specify an inst-sys independently of the repository. Like, e.g.: install=ftp://server1/pub/cd1?instsys=my_fancy_instsys [using ftp://server1/pub/cd1/my_fancy_instsys] or even install=ftp://server1/pub/cd1?instsys=nfs://server2/my/fancy_instsys The 'instsys' URL does _NOT_ point to a repository but directly to the instsys image (or directory). The old method of implicitly using a 'boot/<arch>/inst-sys' directory if one exists, is no longer supported. BTW, before someone asks: the linuxrc docs on opensuse.org have been updated. :-) BTW2, as of beta1 linuxrc checks the signatures of all files it downloads. Use 'insecure=1' to turn it off. Steffen -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

5 9

[yast-devel] yast debugger?
by Roberto Angelino 20 Sep '07

20 Sep '07

Is there such a thing? It would be nice to do a yast -d ... ---- Roberto Angelino Dedicated Partner Engineer (310) 529-3527 -- 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] ruby bindings work with the UI now
by Duncan Mac-Vicar Prett 20 Sep '07

20 Sep '07

http://duncan.mac-vicar.com/blog/archives/266 -- 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] finish yast and launch subsequent program
by Johannes Meixner 19 Sep '07

19 Sep '07

Hello, is it possible (with YCP) to finish a YaST module but let it launch a subsequent program? I.e. replace the YaST process by another program? For background info, see https://bugzilla.novell.com/show_bug.cgi?id=310476#c4 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 2

[yast-devel] YaST team minutes digest. Tue, Sept 11.
by Duncan Mac-Vicar Prett 18 Sep '07

18 Sep '07

(last digest was Sept 4, not 9) Table of contents: ------------------------ * Open bugs for 10.3 * YaST workshop * Python-bindings news * Package management stack bug squashing * SLE10 SP1 * ncurses * Applets * Misc * Miscellaneous bugfixes Open bugs for 10.3 -------------------------- * Everyone please check your open bugs for openSUSE 10.3, and move them to openSUSE 11, if they're not going to be fixed for 10.3. Optionally you may create feature requests for enhancements, if appropriate * For 10.3 RC1 fix only major, critical and blocker bugs YaST workshop --------------------- * Please send jsrain and dmacvicar topics you want to present on YaST workshop Python-bindings news ------------------------------ * Importing other YaST modules functionality added * Basic type checking implemented * UI and SCR can now be called from python code, still WIP Package management stack bug squashing ------------------------------------------------------------- * Always refreshing susetags repositories, even if they were up-to-date now fixed * Fixed package size + related disk usage calculation for YUM repositories (bug #308475) * Installation in text-mode stuck on reading repository cache was caused by not providing correct alternative solution of busy cursor animation for ncurses (bug #309376) * Focus on getting the update stack working. CD eject/changing bug (#308362). Michael working on disk space calculation bugs (#308362) Important note: if you are implementing alternative solutions for GUI and text mode, please make sure you test your feature (bugfix) in both UIs. Similarly, if you're implementing feature (fixing a bug) for installation, make sure it gets properly tested in inst-sys SLE10 SP1 --------------------------------- * Installation server providing NFS4-based repository does not work * update of migrate-to-SP1 patch Ncurses --------- Text mode installation broken in beta3. Memory corruption problems? (#305196). (UPDATE: fixed. Unclosed dialog) Michael initiated discussion about one memory corruption bug in libzypp Stefan shared experience with one in the UI and the trick to dlopen and dlclose the library to keep it in memory. Applets. --------- Looking good. Still some bugs filed against them. Some of them are zypper bugs really. Misc. ------ - Christian Kornacker has been working on developing some y2make all enhancements (goal: prefixed yast together with a non-system libzypp) Miscellaneous bugfixes -------------------------------- * yast2-squid now supports opening ports in firewall and contains sysconfig file with firewall ports definition (bug #247745) * showy2log tool improved - now it can read from stdin * backporting Xen support to SLE9 SP4 (paravirtualized machine installation, paravirtualized drivers support in full virtualization) (feature #301974) * static IP configuration + proxy setup in 1st stage should work correctly by now (bugs #298001, #287801) * Install notify messages should no longer pop-up during package update in ncurses UI (bug #308410) * Using obsolete 'getcfg-interface' tool made yast2-dhcp-server unable to retrieve subnet information, thus resulting in generating invalid config file - now fixed (bug #308258) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] how to mark *.ybc file outdated?
by Johannes Meixner 18 Sep '07

18 Sep '07

Hello RPMs for YaST modules install *.ycp files and *.ybc files. Is it possible to change a *.ycp file and then tell YaST somehow that the matching *.ybc file is outdated so that the new code in the new *.ycp file is used? In other words: What must I do to force YaST to ignore the old *.ybc file and use the new *.ycp file or how can I create a single new *.ybc file from a single new *.ycp file with a usual openSUSE 10.3 default installation (i.e. no development tools are installed on this system)? Background information: Regarding bug 310177 I liked to try out a small patch. Therefore I canged /usr/share/YaST2/modules/Printerdb.ycp But I cannot test it because when I change /usr/share/YaST2/modules/Printerdb.ycp it has no effect on the running YaST printer module. It seems YaST uses always /usr/share/YaST2/modules/Printerdb.ybc regardless if the associated *.ycp file has changed. I tried to simply move /usr/share/YaST2/modules/Printerdb.ybc away, but then the printer module cannot be started at all. I get "No such client module printer". 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

10 18

[yast-devel] Re: [yast-commit] r40899 - /trunk/country/timezone/src/dialogs.ycp
by Jiří Suchomel 14 Sep '07

14 Sep '07

Cau, proc chyby v yast2-country nehlasis me? Jirka On Thursday 13 September 2007 18:25, kmachalkova(a)svn.opensuse.org wrote: > Author: kmachalkova > Date: Thu Sep 13 18:25:38 2007 > New Revision: 40899 > > URL: http://svn.opensuse.org/viewcvs/yast?rev=40899&view=rev > Log: > - Remember whether synchronization with NTP server > has been selected (#308238) > - Do not call ntp-client functions before making > sure package yast2-ntp-client gets installed > > Modified: > trunk/country/timezone/src/dialogs.ycp > > Modified: trunk/country/timezone/src/dialogs.ycp > URL: > http://svn.opensuse.org/viewcvs/yast/trunk/country/timezone/src/dialogs.ycp >?rev=40899&r1=40898&r2=40899&view=diff > =========================================================================== >=== --- trunk/country/timezone/src/dialogs.ycp (original) > +++ trunk/country/timezone/src/dialogs.ycp Thu Sep 13 18:25:38 2007 > @@ -142,11 +142,25 @@ > Popup::Error( sformat("Invalid NTP server hostname %1", server) ); > } > > + boolean ntp_used = false; > + > + void CreateUI() { > + WFM::CallFunction("ntp-client_proposal", ["CreateUI"]); > + > + ntp_used = (boolean) WFM::CallFunction("ntp-client_proposal", > ["GetUseNTP"]); + > + if ( UI::WidgetExists(`id(`ntp_content)) ) > + { > + UI::ChangeWidget(`id(`rb), `CurrentButton, (ntp_used ? `ntp : > `manual)); + enable_disable_widgets(ntp_used); > + } > + } > + > term cont = `HBox ( > `RadioButtonGroup (`id (`rb), `HCenter (`VBox ( > `Left (`VBox ( > // radio button label (= how to setup time) > - `Left (`RadioButton (`id (`manual), `opt (`notify), _("Manually"), > true)), + `Left (`RadioButton (`id (`manual), `opt (`notify), > _("Manually"))), `VSpacing (0.5), > `HBox ( > `HSpacing (3), > @@ -157,15 +171,26 @@ > ) > ), > `VSpacing (1), > - `ReplacePoint(`id(`rp), `Empty()) > + `Left (`VBox ( `id(`ntp_content), > + `Left (`RadioButton (`id (`ntp), `opt (`notify), > + // radio button label > + _("Synchronize with NTP Server"), false)), > + `ReplacePoint(`id(`rp), `Empty()) > + ) > + ) > )) > - )))); > + )))); > + > > Wizard::OpenAcceptDialog (); > Wizard::SetContents (_("Change Date and Time"), cont, htext, true, > true); Wizard::SetDesktopIcon("timezone"); > - WFM::CallFunction("ntp-client_proposal", ["CreateUI"]); > - enable_disable_widgets(false); > + > + boolean ntp_installed = (Stage::initial() || Package::Installed > ("yast2-ntp-client")); + > + if (ntp_installed) { > + CreateUI(); > + } > > if (!dt_widgets) > { > @@ -176,8 +201,6 @@ > }); > } > > - boolean ntp_installed = false; > - boolean ntp_used = false; > > any ret = nil; > repeat > @@ -192,10 +215,12 @@ > ntp_installed = Package::Install ("yast2-ntp-client"); > if (!ntp_installed) > { > - ntp_used = false; > + ntp_used = false; > UI::ChangeWidget (`id (`manual), `Value, true); > UI::ChangeWidget (`id (`ntp), `Value, false); > } > + else > + CreateUI(); > } > if (ntp_used ) > { > @@ -287,6 +312,7 @@ > } > } > until( ret==`accept || ret==`cancel ); > + WFM::CallFunction("ntp-client_proposal", [ "SetUseNTP", $["ntp_used" : > ntp_used] ]); Wizard::CloseDialog (); > return (ret == `accept); > }; -- Jiri Suchomel SUSE LINUX, s.r.o. e-mail: jsuchome(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Praha 9, Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] YaST team minutes digest. Tue, Sept 9.
by Duncan Mac-Vicar Prett 10 Sep '07

10 Sep '07

Minutes ====== Weekly digest of minutes will be posted to yast-devel and factory for public consumption. 10.3 === Bugzilla looking better. Waiting for Beta3 PackageKit ======== http://www.packagekit.org/wiki/index.php/Main_Page PackageKit is in FATE and deserves research and that people is informed. jkress, tgoetlicher, and ma will inform themselves and do some research about it and inform the others. Blocker #307047 (SP4) ================= Discussion about sp4 sles9 out of memory bug assigned to gs. Hardware problem? kernel? frishen installation, Machine should be memtested?. zypper: ^^^^^^ Final (hopefully) solution for the yes/no prompt localization found: use glibc's rpmatch() (see man rpmatch) to parse the answer, and mark the whole "Yes" and "No" strings normally for translation (if needed). Bug #304650. NTP: ^^^ Reimplementation of feature #302192 (synchronization with NTP server in 1st stage of installation). Now using 2 new installation clients to set up and save configuration. Related bugs: #299238,#299557, #302389, #302433 #307363 (not fixed yet) setenv(): ^^^^^^^^^ - new builtin in yast2-core for add or change evnironment variables To be used by curl (dowloading repository list) if user needs to configure proxy in 1st stage. Related bug: #305163 pkg-bindings: ^^^^^^^^^^^^ - Media redirection has been implemented. It's possible to redirect the installation repository to a mirror in case of error (unreachable server) (bug #294481) - Zypp SQlite cache is now copied at the end of the first stage to the target system, no need to download/parse metadata again. (bug #304310) - y2base may be killed by oom killer during the 1st stage of installation because of oversized y2log. There were some fixes in pkg-bindings and solver to reduce amount of logs, mostly coming from libzypp. See also: http://lists.opensuse.org/zypp-devel/2007-08/msg00068.html and related bugs: #305087, #305083 - Y2log doesn't contain libzypp debug log messages anymore (can be turned on by enabling yast debug - SHIFT + F7) (bug #306458). - SUSEregister should not start the package manager if it's not needed (bug #304310). - Available kernel package was selected using Pkg::IsAvailable() call which checks for 'provides' tag (not package name), the problem is that e.g. 'kernel-smp' is provided by 'kernel-default' (so it's available) but there is no RPM package 'kernel-smp', so it couldn't be installed (bug #302246). udev: ^^^^^ - autoyast support for udev rules and backward compatibility with ol-style autoyast profiles #303916 if old-style configuration names are found, udev rules are created and files are automatically renamed by sysconfig. For new-style configuration there is possible to define rules for udev in networking section: <networking> ... <net-udev config:type="list"> <line> <rule>ATTR{address}</rule> <value>00:00:00:00:00:00</value> <name>eth0</name> </line> </net-udev> ... </networking> Misc: ^^^^ - support for changing URL through requestMedia callback reimplemented in libzypp and YaST - now displaying repository name instead of product name both in qt and ncurses packager. Related bug: #296782 - One-Click Installation (yast2-metapackage-handler) now has MIME associations for Firefox (#295677) - OES2 configuration - solved problem with changing language (localization) Related bug: #295160 - The bluetooth subsystem is enabled by default (bug 299734) - A better busy indicator for progress popup (animated icon) (bug #296945) - Due to excessive logging, the installation or distro upgrade can run out of memory, #305083 - detection, package installation and configuration of smartlinks modems, #284287 - solved problem with copying rsa and dsa keys - XMessage is displayed only if YaST is crashed -- 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] Tango icons for YaST 10.3
by Krupanský Rastislav 04 Sep '07

04 Sep '07

Hi. I´ve already send my mail to opensuse-factory,but it is preferably to send request to this mailing lists. I don´t know who makes decision about layout of YaST. You've read about new updated KDE 4.0.0 release schedule certainly. http://lists.kde.org/?l=kde-core-devel&m=118856879831611&w=2 or http://techbase.kde.org/Schedules/KDE4/4.0_Release_Schedule So, i´d like to ask.Is it really necessery to use Tango icons for KDE users when KDE 4 will be released on the 20.December (and maybe later, who knows.i don´t believe that KDE4 will be released on time) I know, that Andreas Jaeger wrote, qoute: "Tango icons in general fit much better to KDE4 than the crystal ones -" in discussion http://lists.opensuse.org/opensuse-factory/2007-07/msg00255.html but would it be possible to change your decision? Tango theme for YaST doesn´t really fit with the rest of the KDE desktop. Or some suggestion: If i use KDE cd, or i choose KDE desktop in installation from DVD, i'll have crystal theme for YaST by default. And if i use Gnome cd, or i choose Gnome desktop in installation from DVD, i'll have tango icons for YaST by default. I think it is possible to create, isn´t it? Thanks. Have a nice day :-) Rasto -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1