Branch: refs/heads/fix_messed_client Home: https://github.com/yast/yast-network Commit: 667a941a16e1f1d5b2cbe94f997ebd40e7f52744 https://github.com/yast/yast-network/commit/667a941a16e1f1d5b2cbe94f997ebd40... Author: Josef Reidinger <jreidinger@suse.cz> Date: 2013-11-29 (Fri, 29 Nov 2013) Changed paths: M src/clients/inst_setup_dhcp.rb Log Message: ----------- enclose client into namespace otherwise global namespace is messed Problem is that even if clients acts like script, it is evaluated in global namespace and process is still alive, result is that it mess global namespace. In this particular case it breaks installation because it adds Yast::FileUtils to global namespace as ::FileUtils and when we require original FileUtils from ruby, then it collide and raise exception. Commit: 32072839ec4629d963eb1edbe53f5b85e5f849ac https://github.com/yast/yast-network/commit/32072839ec4629d963eb1edbe53f5b85... Author: Josef Reidinger <jreidinger@suse.cz> Date: 2013-11-29 (Fri, 29 Nov 2013) Changed paths: M VERSION M package/yast2-network.changes M package/yast2-network.spec Log Message: ----------- release Compare: https://github.com/yast/yast-network/compare/667a941a16e1^...32072839ec46