November 2011 - YaST Development - openSUSE Mailing Lists

[yast-devel] opensuse 12.1 DVD install showstopper: "An error occurred during initrd creation"
by Mike Coleman 27 Feb '12

27 Feb '12

Hi, When I install the final 12.1 from the DVD, it fails during the "Saving bootloader configuration..." / "Install boot manager" phase with a dialog titled "An error occurred during initrd creation." (which has no other text). I am unable to complete the install after this point. This is probably the same bug as "Bug 713316 - mkinitrd: fails to run and/or shows no text during install" (https://bugzilla.novell.com/show_bug.cgi?id=3D713316) I've tried installing on three different platforms, and I get the same bug. If I install using the Live GNOME CD on these platforms, the install completes without difficulty. Has anyone succeeded in installing on any hardware using the 12.1 DVD? Thanks, Mike

2 4

[yast-devel] [PATCH] yast2-core: agent-process: fix stdout/stderr test cases
by Alexander Graf 02 Dec '11

02 Dec '11

When running the stdout and stderr test cases while building yast2-core for ARM, we execute processes slower than the yast developer machines apparently :). The test cases expect data to flow between the ycp code and cat within 50 ms, but we can't guarantee that. In fact, it basically never worked in my tests. The real fix would probably to listen on the socket and see if new data comes in and only then read from there, but I'm not sure it's worth it for a test case. Instead, we can just increase the sleeps to something really high so we definitely catch all the shiny new data on the other end of the pipe. Please apply. Signed-off-by: Alexander Graf <agraf(a)suse.de> --- agent-process/testsuite/tests/stderr.ycp | 8 ++++---- agent-process/testsuite/tests/stdout.ycp | 8 ++++---- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/agent-process/testsuite/tests/stderr.ycp b/agent-process/testsuite/tests/stderr.ycp index 3d420e2..74282aa 100644 --- a/agent-process/testsuite/tests/stderr.ycp +++ b/agent-process/testsuite/tests/stderr.ycp @@ -8,12 +8,12 @@ string out1 = (string)SCR::Read(.read_stderr, id); SCR::Write(., id, "foo\n"); - sleep(50); + sleep(500); // read "foo\n" string out2 = (string)SCR::Read(.read_stderr, id); SCR::Write(., id, "foo2\nfoo2\n"); - sleep(50); + sleep(500); // read "foo2\nfoo2\n" string out3 = (string)SCR::Read(.read_stderr, id); @@ -35,12 +35,12 @@ string out1 = (string)SCR::Read(.read_line_stderr, id); SCR::Write(., id, "foo\n"); - sleep(50); + sleep(500); // read "foo\n" string out2 = (string)SCR::Read(.read_line_stderr, id); SCR::Write(., id, "foo2\nfoo2\n"); - sleep(50); + sleep(500); // read "foo2\n" string out3 = (string)SCR::Read(.read_line_stderr, id); diff --git a/agent-process/testsuite/tests/stdout.ycp b/agent-process/testsuite/tests/stdout.ycp index 86c29fd..f1d0241 100644 --- a/agent-process/testsuite/tests/stdout.ycp +++ b/agent-process/testsuite/tests/stdout.ycp @@ -8,12 +8,12 @@ string out1 = (string)SCR::Read(.read, id); SCR::Write(., id, "foo\n"); - sleep(50); + sleep(500); // read "foo\n" string out2 = (string)SCR::Read(.read, id); SCR::Write(., id, "foo2\nfoo2\n"); - sleep(50); + sleep(500); // read "foo2\nfoo2\n" string out3 = (string)SCR::Read(.read, id); @@ -34,12 +34,12 @@ string out1 = (string)SCR::Read(.read_line, id); SCR::Write(., id, "foo\n"); - sleep(50); + sleep(500); // read "foo\n" string out2 = (string)SCR::Read(.read_line, id); SCR::Write(., id, "foo2\nfoo2\n"); - sleep(50); + sleep(500); // read "foo2\n" string out3 = (string)SCR::Read(.read_line, id); -- 1.6.0.2 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

4 8

[yast-devel] Missing cleaning phase in yast development
by Josef Reidinger 29 Nov '11

29 Nov '11

Hi, when I must change something in yast code I notice one important thing. There is missing cleaning phase in development of yast. What is cleaning phase? Go through code and check if all workarounds, hot-fix or special cases is still valid. So check if workaround for broken configuration option is not already fixed upstream, if hot fix cannot be fixed better, if code change during fixing some unexpected condition need some refactoring etc. Well, I can hear notice that there is not enough time and that there is no people, but I think that in midterm ( from one release to another ) it reduce time needed, as people work on better code and it is easier to write new features and reduce bug count. Any opinions? I think that for trunk is now perfect time as 12.1 is out and we should push to upstream to fix our workaround properly. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

5 4

[yast-devel] Re: [yast-commit] r66966 - in /branches/SuSE-Code-11-SP2-Branch/ftp-server: VERSION package/yast2-ftp-server.changes src/write_load.ycp
by Martin Vidner 28 Nov '11

28 Nov '11

On Mon, Nov 28, 2011 at 03:09:24PM -0000, tgoettlicher(a)svn2.opensuse.org wrote: > Author: tgoettlicher > Date: Mon Nov 28 16:09:24 2011 > New Revision: 66966 > > URL: http://svn.opensuse.org/viewcvs/yast?rev=66966&view=rev > Log: > > - backported fix for parsing options from xinetd (bnc#597842) > - 2.17.7 > > > > Modified: > branches/SuSE-Code-11-SP2-Branch/ftp-server/VERSION > branches/SuSE-Code-11-SP2-Branch/ftp-server/package/yast2-ftp-server.changes > branches/SuSE-Code-11-SP2-Branch/ftp-server/src/write_load.ycp > > Modified: branches/SuSE-Code-11-SP2-Branch/ftp-server/VERSION > URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP2-Branch/ftp-s… > ============================================================================== > --- branches/SuSE-Code-11-SP2-Branch/ftp-server/VERSION (original) > +++ branches/SuSE-Code-11-SP2-Branch/ftp-server/VERSION Mon Nov 28 16:09:24 2011 > @@ -1 +1 @@ > -2.17.6 > +2.17.7 > > Modified: branches/SuSE-Code-11-SP2-Branch/ftp-server/package/yast2-ftp-server.changes > URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP2-Branch/ftp-s… > ============================================================================== > --- branches/SuSE-Code-11-SP2-Branch/ftp-server/package/yast2-ftp-server.changes (original) > +++ branches/SuSE-Code-11-SP2-Branch/ftp-server/package/yast2-ftp-server.changes Mon Nov 28 16:09:24 2011 > @@ -1,4 +1,10 @@ > ------------------------------------------------------------------- > +Mon Nov 28 15:37:02 CET 2011 - tgoettlicher(a)suse.de > + > +- backported fix for parsing options from xinetd (bnc#597842) > +- 2.17.7 The bug actually reported was bnc#733039. Please mention both. > + > +------------------------------------------------------------------- > Tue Feb 15 11:18:37 CET 2011 - jsrain(a)suse.cz > > - fixed command line interface - not polling UI while reading the > > Modified: branches/SuSE-Code-11-SP2-Branch/ftp-server/src/write_load.ycp > URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP2-Branch/ftp-s… > ============================================================================== > --- branches/SuSE-Code-11-SP2-Branch/ftp-server/src/write_load.ycp (original) > +++ branches/SuSE-Code-11-SP2-Branch/ftp-server/src/write_load.ycp Mon Nov 28 16:09:24 2011 > @@ -53,7 +53,14 @@ > string option = ""; > y2milestone("---------------boolean SettingsXinetdPure (list <string> server_args)-----------------"); > y2milestone("----------------------------------------------------"); > - > + > + //bnc#597842 Yast2-ftp-server module losses the chroot everyone (chroot-local-user) setting > + if ((FtpServer::vsftpd_edit) || (size(pure_ftpd_xinet_conf) == 0)) > + { > + y2milestone("skip SettingsXinetdPure() -> vsftpd is used or pure_ftpd_xinet_conf is empty"); > + return true; > + } > + The logic of the fix is quite nonobvious. It's a backport, so oh well... I have commented at least in the bug: the problem appears to be that after vsftpd settings are parsed, the correct values are overwritten by parsing the (meaningless) settings for pure-ftpd. > //ChrootEnable > option = find(string opt, pure_ftpd_xinet_conf, ``(opt == "-A")); > if (option != nil) > @@ -1147,4 +1154,4 @@ > > } > > -} > \ No newline at end of file > +} > > -- > To unsubscribe, e-mail: yast-commit+unsubscribe(a)opensuse.org > For additional commands, e-mail: yast-commit+help(a)opensuse.org > -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

2 1

[yast-devel] Re: [yast-commit] r66894 - in /trunk/s390: VERSION package/yast2-s390.changes src/clients/iucvterminal-server.desktop src/clients/iucvterminal.desktop src/iucvterminal-server/ui.ycp
by Josef Reidinger 23 Nov '11

23 Nov '11

Hi, small note: On Tue, 22 Nov 2011 20:00:52 -0000 thardeck(a)svn2.opensuse.org wrote: > Author: thardeck > Date: Tue Nov 22 21:00:51 2011 > New Revision: 66894 > > URL: http://svn.opensuse.org/viewcvs/yast?rev=66894&view=rev > Log: > - fixed wrong Yast categories for IUCV terminal modules (fate#310723) > - fixed disabling of the IUCV input field in the ncurses dialog > (fate#310723) > - check z/VM ids against username specification to prevent umlauts > > @@ -754,7 +754,8 @@ > integer line = 0; > foreach (string zvmid, zvmid_list,{ > line = line + 1; > - if (regexpmatch(zvmid, "[^[:alnum:]]")) > + // since alnum allows umlauts too the id is checked > against the user name specification > + if (regexpmatch(zvmid, "[^[:alnum:]]") || > (!IUCVTerminalServer::CheckUserGroupName(zvmid) && zvmid != "")) { If you have method to check username by specification, then regexmatch looks useless for me and just call check is enough. Also checkusernamegroup should check if zvmid is empty, if it is againts specification. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Code Review
by Thomas Goettlicher 16 Nov '11

16 Nov '11

Hi Gabi, Could you please review my patch for bug 713343 (YaST ncurses help screen is too small) attached to this email? Many thanks, Thomas -- Thomas Goettlicher SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany

2 1

Re: [yast-devel] Branching openSUSE 12.1
by Ralf Haferkamp 15 Nov '11

15 Nov '11

Hi, I'd like to merge some features I developed in the SP2 Branch to trunk, but don't want them to appear in 12.1. Could we please create the 12.1 branch now? regards, Ralf -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 4

[yast-devel] Re: [yast-commit] r66662 - in /trunk/yast2: VERSION library/network/src/SuSEFirewall.ycp package/yast2.changes
by Ladislav Slezak 03 Nov '11

03 Nov '11

Dne 2.11.2011 14:51, locilka(a)svn2.opensuse.org napsal(a): > Author: locilka > Date: Wed Nov 2 14:51:17 2011 > New Revision: 66662 > > URL: http://svn.opensuse.org/viewcvs/yast?rev=66662&view=rev > Log: > - Unified starting, stopping and checking for firewall status > (bnc#727445) > - //if (Mode::normal() || Mode::commandline()) { > - foreach (string service, firewall_services, { > - if (Service::Status(service) == 0) { > - started = true; > - break; > - } > - }); > - //} > + if (Mode::testsuite()) return true; > WATCH OUT! This breaks many testsuites!! E.g. in yast2-nis-client, yast2-nfs-client, yast2-nfs-server, see https://build.opensuse.org/project/monitor?project=YaST%3AHead Their tests expect the call in the output, they fail with this diff: -Execute .target.bash "/sbin/service SuSEfirewall2_init status" $["TERM":"raw"] 0 Either fix the code or the affected tests. -- 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 To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 2

[yast-devel] Re: Expired GPG key for YaST OBS projects
by Duncan Mac-Vicar P. 02 Nov '11

02 Nov '11

On 11/02/2011 02:13 PM, Ladislav Slezak wrote: > Hi Duncan, > > I just noticed that YaST repositories in OBS have expired GPG key, > I tried to extend the key for YaST:Head but there is no key (as it is in > the upper level project YaST). > > Please, run > "osc signkey --extend YaST" > > duncan@linux-jj8o:~> osc signkey --extend YaST <status code="ok" /> Is that enough? :-) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 1