YaST Development August 2007

yast-devel@lists.opensuse.org

16 participants
19 discussions

[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] 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] Improved UI::RunInTerminal - registration in text-mode possible
by Katarina Machalkova 24 Aug '07

24 Aug '07

Hola brave yast hackers! In order to get ready for re-introducing thread support into yast2-ncurses (post 10.3) I've improved UI::RunInTerminal builtin. As you may know, this builtin is ncurses-specific and it is very useful for calling external programs from text-mode interface. For example, running yast modules from the text-mode control centre menu in the same terminal is a common usecase. Another example is product-creator (Lado?), where you can enter gpg interactive mode via UI::RunInTerminal to generate keys to sign your product. Until recently, due to a bug (well, rather not implemented feature ;-) ) not all applications could be run via UI::RunInTerminal (as it was e.g. the case of w3m), as yast duly redirected their stdout and stderr into the y2log. After adding some file descriptor magic into y2-ncurses code, it now works. And - this is probably the most important - *Customer centre registration can now be carried out in the text-mode as well* To test the new improved yast2-ncurses, grab the packages from here: /work/built/mbuild/bragg-kmachalkova-504/ (only amd64 and i386). Note: they require new yast2-core B. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter

3 3

[yast-devel] Proofreading YaST Messages
by Karl Eichwalder 24 Aug '07

24 Aug '07

In an heroic way, Martina Dejmek proofread many (new) YasT messages the last days. Internally, find the results in my export directory as .../10.3/proofed-2007-08-23.tar.gz . Maybe, I should create a bug report an attach it. Two notes ========= 1/ Do *not* apply these corrections now. Remember, string freeze is effective since quite some time. 2/ We will use the corrections as "overloads". This means, we will install them as en_US translations. So, if you receive a bug report with an unknown message quoted, check the en_US .mo file using msgunfmt and use the msgid for grepping thru your sources. If any "translation" does not match you expection, talk to me and Martina. We will happily adjust the en_US files for something better. Let me repeat with other words, we did not touch the messages already approved by the previous proofreader. But considerably more than 2000 messages were in an unchecked state in the meantime and Martina worked on those only. For the record, Jana proofread several important modules completely some days ago. Jana's findings, together with remarks by Benji, already made it into the source code. I'm rather happy that we reached this goal now! Karl -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- 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] incompatibility between Beta1 and Beta2 of 10.3
by Martin Vidner 23 Aug '07

23 Aug '07

Hi hackers, while enhancing yast2-core for a new feature (watch http://news.opensuse.org/), I had to introduce an incompatibility in the code. It means that if you update (recompile) yast2-core, you have to update (recompile) not only some of the binary packages - all the UIs and all the language bindings - but also all the *.ybc files. In short, you should update all YaST packages. The symptoms of failure include: "createUI() called before setServerOptions() !" "UI::GetDisplayInfo ... ... caught invalid bytecode" I am sorry to have delayed this announcement to the point where most of the affected people already have found out the heard way :-/ -- 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

1 0

[yast-devel] New y2makeall
by Stefan Hundhammer 23 Aug '07

23 Aug '07

I just checked in a new version of y2makeall. It now checks if multiple versions (or none at all) of libzypp are installed. By default, it terminates if there are multiple versions. Reason: It happens on a regular basis that some subdirectories (with binaries) are built with a previous version of libzypp and some others with a more recent one. This will result in all kinds of very subtle bugs or even crashes, sometimes already in build tools like the YCP byte code compiler. Typically, you want to sudo rm -rf /usr/lib/libzypp* cd somewhere/libzypp make && sudo make install This latest version of y2makeall now checks against this very common problem. You can override that behaviour with --ignore-libzypp . It should work on 32 and 64 bit platforms, albeit I could only do rudimentary testing on 64 bit platforms (it simply checks for presence of /usr/lib64). 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] Browser with functional links
by Benji Weber 22 Aug '07

22 Aug '07

Hi, Posting this here incase anyone else hadn't thought of this before. There are a number of exciting things that would be possible with a web page & usable links within YaST. The registration module just launches an external browser. There is of course the Rich Text widget that provides a useful subset of html, and by combining with the xdg-open utility we can have links that open in the appropriate browser or application for the user's desktop environment. e.g. a link to a webpage will open in konqueror/firefox depending on user's browser. Link to a pdf would open in kpdf on KDE, link to an irc:// link would open in konversation/xchat etc. Sample code: { string OPEN_CMD = "xdg-open"; UI::OpenDialog(`opt(`centered), `MinHeight(22, `MinWidth(68, `VBox( `RichText(`id(`rtext),"") ) ) ) ); UI::ChangeWidget(`rtext,`Value,"<body bgcolor=\"White\">\ <h1>Browser demo</h1>\ <p>Example of page with functional links within YaST</p>\ <li><a href=\"http://example.com\">This link should open in your browser</a></li>\ <li><a href=\"irc://irc.freenode.net/#yast\">This link should connect you to the YaST channel</a></li>\ <li><a href=\"http://wiki.novell.com/images/d/d8/Quick_Reference_11_UNIX-Linux_Troublesho…">This link should open in your PDF viewer</a></li>\ </body>"); any input = UI::UserInput(); while(is(input,string)) { SCR::Execute(.target.bash, OPEN_CMD + " '" + (string)input + "'"); input = UI::UserInput(); } } You can do relatively complex things, for example here is a screenshot of yaloki's irc support page running inside YaST http://bw.uwcs.co.uk/yast-browser-qt.png . Minor annoyances include requiring absolute paths for images. Does anyone have any thoughts on how to do this even better, or potential applications for this? _ Benjamin Weber -- 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] Re: [opensuse-factory] YaST2 Control Center - icon order
by Stanislav Visnovsky 22 Aug '07

22 Aug '07

Resending to the proper mailing list. S. Dňa Pi 10. August 2007 23:56 Peter Buschbacher napísal: > Hello! > Can someone tell me what file controls the order of Icons, the Text, and > the texts of the bottom 'helpline'. I really don't like the order > especially in the Software-Section as it looks to me very unordered, and > the texts do not really take (new) users by the hand to quickly take the > right actions. > If I knew where the config for this is done, it would be easier to me to > make suggestions that can't be misunderstood and I did not find it with > some help of locate. > Peter Buschbacher > --------------------------------------------------------------------- > To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org > For additional commands, e-mail: opensuse-factory+help(a)opensuse.org -- 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] devtools: better locale handling support
by Karl Eichwalder 14 Aug '07

14 Aug '07

Am I allowed to check in the following enhancement (iirc, we already discussed this soemwhere, but then I lost track...). I think we need this for better locale support and the packaging level... I was asked to change the .spec file and then tweaking create-spec was the consequence. I'm not a perl hacker, thus I'm asking. The patch seems to do what I what. Index: devtools/skeletons/trans/yast2-trans-XXpkgXX.spec.in =================================================================== --- devtools/skeletons/trans/yast2-trans-XXpkgXX.spec.in (revision 40078) +++ devtools/skeletons/trans/yast2-trans-XXpkgXX.spec.in (working copy) @@ -22,4 +22,5 @@ %files %defattr(-,root,root) %doc @docdir@ -@localedir@ +%dir @localedir@ +%lang(@ISO639@) @localedir@/@LL@ Index: devtools/bin/y2autoconf =================================================================== --- devtools/bin/y2autoconf (revision 40258) +++ devtools/bin/y2autoconf (working copy) @@ -185,6 +185,8 @@ '@YAST2-INIT-PO@' => 'LL=${RPMNAME##*-} AC_SUBST(LL) +ISO639=${LL%_*} +AC_SUBST(ISO639) AC_ARG_WITH(own_compendium, AS_HELP_STRING([--with-own_compendium=FILE], Index: devtools/bin/create-spec =================================================================== --- devtools/bin/create-spec (revision 40258) +++ devtools/bin/create-spec (working copy) @@ -47,7 +47,9 @@ $provides_locale = ""; if ($RPMNAME =~ /^yast2-trans-(.*)/) { - $provides_locale = "Provides:\tlocale(yast2:$1)\n" + $provides_locale = "Provides:\tlocale(yast2:$1)\n"; + $LL = "$1"; + $ISO639 = `echo -n $1 | sed -e 's/_.*//'`; } if ($#ARGV > 0) @@ -212,6 +214,10 @@ "\@scrconfdir\@" => "${yast2dir}/scrconf", "\@desktopdir\@" => "%{prefix}/share/applications/YaST2", '@fillupdir@' => '/var/adm/fillup-templates', + + "\@LL\@" => "$LL", + "\@ISO639\@" => "$ISO639", + ); # The main program -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- 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] updating / upgrading
by Karl Eichwalder 09 Aug '07

09 Aug '07

There, once again, seems to be some confusion about the terms update/updating and upgrade/upgrading. It is Novell policy, _not_ to use upgrade if you talk about software issues. "Upgrade" is strictly reserved for hardware issues. In short, do not use the word "upgrade". Unfortunately, I do not know where all this is documented. Probably in one of ours (SUSE/Novell) style-guides... -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 3

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 August 2007