[yast-devel] WebYaST Beta 3 released
Hi! here it is. Go break it and report back. APPLIANCE DOWNLOAD: http://www.suse.de/~mvidner/webyast-beta3/vm/WebYaST_on_SLES11.i686-0.0.20.v... http://www.suse.de/~mvidner/webyast-beta3/vm/WebYaST_on_SLES11.i686-0.0.20.v... ( gpg --verify WebYaST_on_SLES11.i686-0.0.20.vmx.tar.gz.asc ) sha1sum: 32bfb17093e1f5370b6f84a6cbe175e883280a80 internal: ftp://cml.suse.cz/testing/webyast/WebYaST_on_SLES11.i686-0.0.20.vmx.tar.gz REPOSITORY: zypper ar http://www.suse.de/~mvidner/webyast-beta3 webyast-beta3 USAGE: 1. Run the appliance In the 1st run, accept the SLES EULA 2. Point the browser to port 54984 (**) Select the "localhost" item, Log in as root, with password linux 3. Go through the base setup (language, admin, time, mail) GENERAL NEWS: - Releasing it also as a repository - Added the registration module - Added translations - Added log config for /status - Added /administrator and /mail_settings to base system setup - Added the EULA module, but unconfigured. MODULE SPECIFIC NEWS: (new!) http://www.suse.de/~mvidner/webyast-beta3/ChangeLog KNOWN BUGS: - See this query for a complete bug list: https://bugzilla.novell.com/buglist.cgi?query_format=advanced&product=openSUSE+11.2&component=WebYaST&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=REOPENED FEEDBACK: - irc://irc.opensuse.org/yast - https://bugzilla.novell.com/enter_bug.cgi?component=WebYaST&product=openSUSE+11.2&format=guided (please disregard the oS11.2 version and instead remember to mention the appliance version.) See http://en.opensuse.org/Bugs/WebYaST - mailto:yast-devel@opensuse.org **) options: - have the virtual machine set to network bridging - tunnel out from the inside: /root/bin/webyast-ssh 10.0.2.2 (where 10.0.2.2 is how the VM sees the host in a VirtualBox NAT setup. It forwards the ports 54984, 4984, and 10022->22) -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
On Monday 26 October 2009 17:51:16 Martin Vidner wrote:
KNOWN BUGS: - See this query for a complete bug list:
Registration raises an error (did not use the latest code).
You can workaround this by applying the attached patch.
Ciao,
Daniel
--
J. Daniel Schmidt
On Monday 26 October 2009 19:06:38 J. Daniel Schmidt wrote:
On Monday 26 October 2009 17:51:16 Martin Vidner wrote:
KNOWN BUGS: - See this query for a complete bug list:
Registration raises an error (did not use the latest code). You can workaround this by applying the attached patch.
Ciao, Daniel
The right way to fix it would be first to update plugins/registration/test/unit/registration_test.rb and reproduce the bug by passing a non-Hash. Then add the safeguard code and make sure the test pass. Anyway, how that situation happens? that it receives data that is not a Hash? Another minor detail. I suggest you use obj.is_a?(MyClass) instead of obj.class == MyClass What you are doing is equivalent to obj.instance_of?(MyClass) or testing if the class of the object is exactly Hash. However obj.is_a?(MyClass) determines whether obj is a Hash or any subclass of it, which is more close to what you are looking for (testing whether the object acts like a hash) (the 100% correct way would be to see if the object respond to some Hash-like methods, but that would be too much). Still, I am concerned on how that code would get anything that is not a Hash or nil. -- Duncan Mac-Vicar P. - Engineering Manager, YaST SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
* Duncan Mac-Vicar Prett
On Monday 26 October 2009 19:06:38 J. Daniel Schmidt wrote:
On Monday 26 October 2009 17:51:16 Martin Vidner wrote:
KNOWN BUGS: - See this query for a complete bug list:
Registration raises an error (did not use the latest code). You can workaround this by applying the attached patch.
Ciao, Daniel
The right way to fix it would be first to update plugins/registration/test/unit/registration_test.rb and reproduce the bug by passing a non-Hash. Then add the safeguard code and make sure the test pass.
Anyway, how that situation happens? that it receives data that is not a Hash?
Another minor detail. I suggest you use obj.is_a?(MyClass) instead of obj.class == MyClass
I fixed this yesterday and just pushed. Using kind_of? to make the test more liberate. Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Martin Vidner write:
Hi! <snip/> - Added /administrator and /mail_settings to base system setup
Hi, How do you add this to config file? I don't see it in git and I want add registration to it. So if we add it during building appliance or in package default? Klaus - is somewhere defined what should be default modules which run during basesystem?
MODULE SPECIFIC NEWS: (new!) http://www.suse.de/~mvidner/webyast-beta3/ChangeLog
Maybe changes should be separated by packages and not be date as more interesting is what changed in a module then when it is changed. -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast modules language and time -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
* Josef Reidinger
Martin Vidner write:
Hi! <snip/> - Added /administrator and /mail_settings to base system setup
Hi, How do you add this to config file? I don't see it in git and I want add registration to it. So if we add it during building appliance or in package default?
Klaus - is somewhere defined what should be default modules which run during basesystem?
The default basesystem setup should include the following modules (in this order, if possible): - language - EULAs - root password - network - time + ntp[*] - mail - registration [*] ntp only if network setup was successful Hth, Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Klaus Kaempf write:
* Josef Reidinger
[Oct 27. 2009 18:23]: Martin Vidner write:
Hi! <snip/> - Added /administrator and /mail_settings to base system setup
Hi, How do you add this to config file? I don't see it in git and I want add registration to it. So if we add it during building appliance or in package default?
Klaus - is somewhere defined what should be default modules which run during basesystem?
The default basesystem setup should include the following modules (in this order, if possible):
- language - EULAs - root password - network - time + ntp[*] - mail - registration
[*] ntp only if network setup was successful
done. Remaining issues is network which is not prepared for basesystem (mvidner works on it). And check for working network in ntp (I look at it with help from network guys, but I think it is not ready to beta4 (but now it at least report if fail, so you see that ntp sync doesn't work)). -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast modules language and time -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (5)
-
Duncan Mac-Vicar Prett
-
J. Daniel Schmidt
-
Josef Reidinger
-
Klaus Kaempf
-
Martin Vidner