December 2007 - YaST Development - openSUSE Mailing Lists

[yast-devel] Re: [opensuse-factory] Problems with yast2
by Lukas Ocilka 12 Dec '07

12 Dec '07

Markus Koßmann wrote: > After updating my factory installation yesterday evening " yast2 sw_single" > fails with: > 635 Error while creating client module sw_single > > y2log shows > [...] > 2007-12-11 19:38:23 <1> linux-n04x(5049) [wfm] Y2WFMComponent.cc(import):698 > Y2WFMComponent::import (SlideShow) > 2007-12-11 19:38:23 <3> linux-n04x(5049) [Interpreter] > clients/sw_single.ycp:21 Loading module 'Language' failed > 2007-12-11 19:38:23 <3> linux-n04x(5049) [libycp] Import.cc(import):97 No > matching component found > 2007-12-11 19:38:23 <3> linux-n04x(5049) [Interpreter] > clients/sw_single.ycp:21 Import 'Language' failed... > 2007-12-11 19:38:23 <3> linux-n04x(5049) [Interpreter] > clients/sw_single.ycp:21 Could not create its namespace > 2007-12-11 19:38:23 <3> linux-n04x(5049) [libycp] Bytecode.cc(readFile):1161 > Caught invalid bytecode in '/usr/share/YaST2/modul > es/SlideShow.ybc' It seems to show two different problems: * Loading module 'Language' failed Import.cc(import):97 No matching component found - yast2-country has been split into two packages recently (yast2-country and yast2-country-data). Language.ycp is newly in yast2-country-data. - Make sure you have yast2-country-data package installed. - (Wrong dependencies in some YaST RPM?) - If you have updated yast2-country to a new verson, Language.ycp probably got deleted. * Caught invalid bytecode in SlideShow.ybc - Probably old yast2-packager (SlideShow is part of it). You need to update that package too. - Maybe caused be the very same mistake by wrong RPM dependencies. You can still use 'zypper' to update your packages when YaST is broken :) Bye Lukas PS: Adding yast-devel into Cc:

2 1

[yast-devel] Work report
by Stephan Kulow 12 Dec '07

12 Dec '07

Hi! For those seeing my commits on the commit list, I thought I give you a little report on what I did in your SVN: http://www.kdedevelopers.org/node/3119 What's not written in there: the way it's implemented relies on a fixed size of 1024x768 and I bet on my laptop screen to even look just as bad as on the screenshot. But that's details - and basically out of scope of ITO :) Greetings, Stephan -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 5

[yast-devel] YaSTRS (SuSE repositories adding tool)
by Lukas Ocilka 11 Dec '07

11 Dec '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I've just found this tool "YaSTRS". It seems to generate system commands that import GPG keys for selected repositories and call zypper to add those repositories. See: http://yastrs.hardon.co.il/ About YaSTRS YaSTRS is trying to be the same as easyurpmi for SuSE\OpenSuSE. It provides a simple way to find and add repositories for your SuSE distrubution: Just pick your version and architecture, choose the repositories you wish to add, and you will get a script that adds them for you. Example: - --- cut i686 --- rpm --import http://packman.unixheads.com/suse/10.3/gpg-pubkey-1abd1afb.asc && zypper sa http://packman.unixheads.com/suse/10.3/ \"Packman \" && rpm --import http://download.opensuse.org/distribution/10.3/repo/ossgpg-pubkey-0dfb3188-… http://download.opensuse.org/distribution/10.3/repo/ossgpg-pubkey-307e3d54-… http://download.opensuse.org/distribution/10.3/repo/ossgpg-pubkey-3d25d3d9-… http://download.opensuse.org/distribution/10.3/repo/ossgpg-pubkey-7e2e3b05-… http://download.opensuse.org/distribution/10.3/repo/ossgpg-pubkey-9c800aca-… http://download.opensuse.org/distribution/10.3/repo/ossgpg-pubkey-a1912208-… && zypper sa http://download.opensuse.org/distribution/10.3/repo/oss \"opensuse oss \" && echo "All repositories were added succesfully!" - --- cut i686 --- It seems that it is similar to Community Repositories ;) Bye Lukas -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHXw/DVSqMdRCqTiwRArJVAJ4jVn8q59OgHpwMzkXr1a3Jk+t2ewCgleBa 8zeV5MnVRa1K8ROaNIXNMcA= =cXxH -----END PGP SIGNATURE----- -- 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] Re: [softwaremgmt] YAST2 got signal 11
by Lukas Ocilka 11 Dec '07

11 Dec '07

Sebastian Reinhardt wrote: (see softwaremgmt at opensuse.org) > I installed the YAST these packages, but no success. The repair > capabilities of openSUSE 10.3- DVD could not help, too. Now I had more > problems, because of not working Updates, made during repair with Suse- > DVD, many programs were damaged. Due to other problems (I changed some > hardware drivers and so HAL- and Automount were also broken), now I have > chosen the Winstone- Repair- Method: a new installation (of openSuSe, of > course)! I remebered the last changes I have made before the problems > occure and I think that the last updated library was "glibc". Maybe > there was and incompatibility, or so... Hi, It seems that your system is currently in a *very* inconsistent state and I honestly really don't know what to do (maybe others /yast-devel/ could help). If I were you, I'd insert the 10.3 installation DVD into the drive, reboot the machine and "update" the system back to 10.3. I wouldn't definitely use any FACTORY repository (maximally OSS and/or NON-OSS). Then you could add a FACTORY source again and call zypper to upgrade your system. No packages should report broken dependencies before accepting the upgrade. Bye Lukas PS: /yast-devel/: any better idea?

1 0

[yast-devel]
by Lukas Ocilka 11 Dec '07

11 Dec '07

Hi, I've just (partly) finished a Pattern-Selector proposal for new installation/software management. See: http://en.opensuse.org/YaST/Development/Pattern_Selector_Proposal Even if $this one is finished, it's still work in progress: * We'd like not to use RichText * Expandable pattern-groups * Pattern names printed in bold (?) * Possibility to hide the pattern description (?) All ideas are welcome :) Thanks and Bye Lukas PS: We're still 'a bit' limited by UI capabilities, of course ;) -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic

9 11

[yast-devel] Language::language (and maybe other variables / functions)
by Lukas Ocilka 10 Dec '07

10 Dec '07

Hi, As I've already written, I'm just trying to break some YaST*.rpm dependencies (See thread "[yast-devel] openSUSE 11.0 - Splitting YaST packages - Call for help"). I've found that there might be a candidate for moving some functionality (or only variable) to yast2.rpm or somewhere similarly. It is: +-------------------------------------------------+ | modules/Language.ycp, namely Language::language | +-------------------------------------------------+ These modules use Language YCP module: add-on autoinstallation firstboot installation metapackage network packager Language.ycp is part of yast2-country which directly uses (requires) these rpms: yast2 yast2-bootloader yast2-storage yast2-x11 I'm writing to the yast-devel mailing-list first before asking yast2-country maintainer to move Language::language (or more) somewhere else because I want to know where you think it is a good idea, whether it would help your modules at all ;) So, let me know, please :) Bye and Thanks! Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic clients/release_notes_popup.ycp: string tmp = sformat (path_templ, Language::language); clients/release_notes_popup.ycp: tmp = sformat (path_templ, substring (Language::language, 0, 2)); clients/release_notes_popup.ycp: string tmp = sformat (path_templ, Language::language); clients/release_notes_popup.ycp: tmp = sformat (path_templ, substring (Language::language, 0, 2)); clients/inst_rpmcopy.ycp: Packages::SlideShowSetUp (Language::language); clients/inst_rpmcopy.ycp: Pkg::SetTextLocale (Language::language); clients/inst_rpmcopy.ycp: SlideShow::SetLanguage (Language::language); clients/yast_inf_finish.ycp: linuxrc["Language"] = Language::language; clients/inst_proposal.ycp: Pkg::SetLocale (Language::language); clients/inst_proposal.ycp: Pkg::SetAdditionalLocales ([Language::language]); clients/software_proposal.ycp: if (Pkg::GetPackageLocale () != Language::language) clients/software_proposal.ycp: Pkg::SetPackageLocale (Language::language); clients/software_proposal.ycp: if (! contains (Pkg::GetAdditionalLocales (), Language::language)) clients/software_proposal.ycp: add (Pkg::GetAdditionalLocales (), Language::language)); clients/inst_welcome.ycp:map welcome = CustomDialogs::load_file_locale(patterns,directory, Language::language); clients/language_auto.ycp: "language" : Language::language_on_entry, clients/language_auto.ycp: "languages" : Language::languages_on_entry, clients/language_auto.ycp: Console::SelectFont (Language::language); clients/language_proposal.ycp: string language_on_entry = Language::language; clients/language_proposal.ycp: (Language::languages == "" || Language::languages == language_on_entry) && clients/language_proposal.ycp: Language::languages = Misc::CustomSysconfigRead ("INSTALLED_LANGUAGES", "", clients/language_proposal.ycp: y2milestone ("languages got from target system: %1", Language::languages); clients/language_proposal.ycp: language_on_entry, Language::language, Language::languages); clients/language_proposal.ycp: if (force_reset && language_on_entry != Language::language) clients/language_proposal.ycp: "language_changed": (language_on_entry != Language::language ) clients/language_proposal.ycp: "language_changed": (language_on_entry != Language::language) clients/firstboot_language.ycp: string language_on_entry = Language::language; clients/firstboot_language.ycp: if( Language::language != language_on_entry || Language::ExpertSettingsChanged ) clients/language.ycp: splitstring (Language::languages, ",")); clients/language.ycp: y2milestone ("canceled -> restoring: %1", Language::language_on_entry); clients/language.ycp: Language::Set (Language::language_on_entry); clients/language.ycp: Console::SelectFont (Language::language); clients/language.ycp: Language::language, selection[Language::language,1]:"")); clients/language.ycp: string languages = Language::languages; clients/language.ycp: splitstring (languages, ","), ``(lang_code != Language::language)); clients/language.ycp: string language = options["lang"]:Language::language; clients/language.ycp: Language::languages = mergestring (llanguages, ","); clients/language.ycp: if (language != Language::language) clients/select_language.ycp: string language = Language::language; clients/select_language.ycp: list<string>languages = splitstring (Language::languages, ","); clients/select_language.ycp: // with the default selection according to Language::language clients/select_language.ycp: if (language != Language::language) clients/select_language.ycp: y2milestone ("Language changed from %1 to %2", Language::language, language); clients/select_language.ycp: Language::languages = clients/select_language.ycp: Language::languages = mergestring (selected_languages, ","); clients/inst_autoinit.ycp: Installation::encoding = Console::SelectFont( Language::language ); clients/inst_autoinit.ycp: UI::SetLanguage (Language::language, Installation::encoding); clients/inst_autoinit.ycp: WFM::SetLanguage (Language::language, "UTF-8"); clients/save_config_finish.ycp: string lang = Language::language; clients/inst_release_notes.ycp: Language::language, clients/inst_release_notes.ycp: substring (Language::language, 0, 2), clients/inst_productsources.ycp: language_long = Language::language; include/packager/load_release_notes.ycp: string tmp = sformat (path_templ, Language::language); include/packager/load_release_notes.ycp: tmp = sformat (path_templ, substring (Language::language, 0, 2)); include/installation/inst_inc_second.ycp: Pkg::SetLocale (Language::language); include/installation/inst_inc_second.ycp: string language = Language::language; include/installation/inst_inc_first.ycp: Installation::encoding = Console::SelectFont (Language::language); include/installation/inst_inc_first.ycp: UI::SetLanguage (Language::language, Installation::encoding); include/installation/inst_inc_first.ycp: WFM::SetLanguage (Language::language, "UTF-8"); modules/AutoinstClone.ycp: general["language"] = Language::language; modules/Timezone.ycp: string new_timezone = lang2tz[Language::language]:""; modules/Timezone.ycp: GetTimezoneForLanguage( Language::language, "US/Eastern"); modules/Timezone.ycp: * Uses Language::language for translation. modules/Packages.ycp: string language = Language::language; modules/Packages.ycp: list<string> locales = LocaleVersions (Language::language); modules/Packages.ycp: Pkg::SetTextLocale (Language::language); modules/Packages.ycp: force_reset, reinit, Language::language); modules/Packages.ycp: Pkg::SetAdditionalLocales ([Language::language]); modules/Keyboard.ycp: * Uses Language::language for translation. modules/Keyboard.ycp: default_keyboard = GetKeyboardForLanguage( Language::language, "english-us" ); modules/Keyboard.ycp: GetKeyboardForLanguage ( Language::language, "english-us" ); modules/ProductLicense.ycp: Language::language, modules/ProductLicense.ycp: substring (Language::language, 0, 2), // "it_IT" -> "it" modules/ProductLicense.ycp: y2milestone ("Preffered lang: %1", Language::language); modules/SlideShow.ycp: global string language = Language::language; modules/OneClickInstall.ycp: summary = YPX::SelectValue(xml,"/metapackage/group[@distversion='" + Product::name + "']/summary[@lang='" + Language::language + "']"); modules/OneClickInstall.ycp: summary = YPX::SelectValue(xml,"/metapackage/group[not(@distversion)]/summary[@lang='" + Language::language + "']"); modules/OneClickInstall.ycp: description = YPX::SelectValue(xml,"/metapackage/group[@distversion='" + Product::name + "']/description[@lang='" + Language::language + "']"); modules/OneClickInstall.ycp: description = YPX::SelectValue(xml,"/metapackage/group[not(@distversion)]/description[@lang='" + Language::language + "']"); modules/OneClickInstall.ycp: string summary = YPX::SelectValue(xml,THIS_REPO_XPATH + "summary[@lang='"+ Language::language +"']"); modules/OneClickInstall.ycp: string description = YPX::SelectValue(xml,THIS_REPO_XPATH + "description[@lang='"+ Language::language +"']"); modules/OneClickInstall.ycp: string summary = YPX::SelectValue(xml,THIS_SOFTWARE_XPATH + "summary[@lang='"+ Language::language +"']"); modules/OneClickInstall.ycp: string description = YPX::SelectValue(xml,THIS_SOFTWARE_XPATH + "description[@lang='"+ Language::language +"']");

4 5

[yast-devel] Progress:: supports subprogress (yast2-2.16.17)
by Ladislav Slezak 07 Dec '07

07 Dec '07

Hi all, I have enhanced the Progress module, now it can display an additional progress bar above the main progress bar. It can be used for detailed progress of the current task. Currently it's used in PackageCallbacks to implement total and detailed progress. The subprogress can be either the standard `Progress widget or the tick progress widget (the well known animated icon ;-)) or none. See the descriptions of Progress::Subprogress*() functions for more details. Here is an example how to use the new feature: // create a standard progress Progress::New(...); // add a subprogress bar with 42 steps Progress::SubprogressType(`progress, 42); Progress::SubprogressTitle("Subprogress label"); // set the value of the subprogress Progress::SubprogressValue(1); ... Progress::SubprogressValue(42); // remove the subprogress (the task is finished) Progress::SubprogressType(`none, nil); // next stage Progress::NextStage(); -- 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] Re: [opensuse-factory] Accessible installer
by Stanislav Visnovsky 07 Dec '07

07 Dec '07

Let's move to yast-devel. Dňa Wednesday 28 November 2007 04:23:55 Hans Petter Jansson ste napísal: > The GNOME team set up a wiki page for 11.0 ideas. One of the requests is > for accessibility options to be available in the YaST installer, in > particular: > > * Screen magnifier - shows a magnified version of the portion of the > screen you're pointing at. > > * Screen reader - reads the labels and input text out loud. > > * Braille output - provides tactile display of labels and input text via > a special device. > > In GNOME, we use Orca to accomplish this, together with the at-spi > infrastructure. It is a Python app. I don't know what Qt/KDE uses, but I > imagine something similar. > > So I have some questions for the YaST/installer guys: > > * What accessibility technologies are available in the installer today, > and how are they configured? AFAIK, we have support for visually impaired people: - linuxrc can be run in linemode to allow screen readers - yast2 ncurses interface has high contrast color scheme available - there is support for braille peripherials > > * If we're missing accessibility functionality, how feasible would it be > to implement it for 11.0? Depends on the technology. One constraint I see right away is the size of of inst-sys, we would need to do some magic there to keep it reasonably sized. First, we would need to know exactly what we want to support. The 3 points above? Stano > > * Given that the installer is a Qt app, what technologies could we use? > > Also see > > http://en.opensuse.org/GNOME/Ideas/11.0#Accessibility -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

5 8

[yast-devel] DNS Server Module ?
by Günther J. Niederwimmer 07 Dec '07

07 Dec '07

Hello, is there any planing to recondition the YaST2 DNS Server Module ? In the momentary condition, it is not possible to create a secure or little individually named.conf ? The most importend things are "views" and a parser to include some parameters ? my reported Bug with "allow-transfer", is existent over a long time :(. I found a new bug with ldap not yet reported .... -- 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] Input field width in the mod-ui
by Stefan Hundhammer 06 Dec '07

06 Dec '07

This bug may be of general interest: https://bugzilla.novell.com/show_bug.cgi?id=345819 In short, input fields (formerly known as TextEntry) and password fields now no longer take all the space they can get, but by default use a reasonable default width - unless you tell them to behave differently. This was buggy in the old UI: They always stretched, even though though they should not unless explicitly told (with `opt(`hstretch) ). This bug is now fixed, but that OTOH means that it now behaves differently. If we can live with adding some `opt(`hstretch) in some dialogs I would very much prefer to keep the bug fix and add that `opt(`hstretch) where necessary and/or useful. With the fix we can have both ways: Input fields that use a reasonable width by default and input fields that stretch to take whatever space is available. Going back to the old version would mean we only have input fields that stretch, and in cases where you don't want all the width to be consumed by an input field use HWeight() or add some HSquash() or HVSquash() around the VBox() to make it smaller, but of course always take care not to have them become too small and add some MinWidth() - about like this: `HSquash( `MinWidth( 30, // min. 30 units wide (80x25 is main window size) `VBox( `InputField(`id(...), "blurb" ), `InputField(`id(...), "blurb" ), ... `InputField(`id(...), "blurb" ) ) ) ) So now the question is: Which kind of pain is bigger? Adding `opt(`hstretch) or reverting to the old (IMHO buggy) behaviour? 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

3 6