May 2013 - YaST Development - openSUSE Mailing Lists

[yast-devel] [PATCH yast-mail] Use /etc/hostname instead of /etc/HOSTNAME
by Cristian Rodríguez 20 May '13

20 May '13

--- src/YaPI/MailServer.pm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/YaPI/MailServer.pm b/src/YaPI/MailServer.pm index 2051480..005cd5d 100644 --- a/src/YaPI/MailServer.pm +++ b/src/YaPI/MailServer.pm @@ -2387,7 +2387,7 @@ sub WriteMailLocalDomains { my $host = `hostname -f`; chomp $host; if( ! $host ) { - $host = `cat /etc/HOSTNAME`; chomp $host; + $host = `cat /etc/hostname`; chomp $host; if( ! $host ) { $host = 'linux.lokal'; @@ -2983,7 +2983,7 @@ sub activate_virus_scanner { my $mydomain = `hostname -d`; chomp $mydomain; if( ! $myhostname ) { - $myhostname = `cat /etc/HOSTNAME`; chomp $myhostname; + $myhostname = `cat /etc/hostname`; chomp $myhostname; if( ! $myhostname ) { $myhostname = 'linux.lokal'; -- 1.8.2.3 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 1

[yast-devel] [PATCH yast-restore] Use /etc/hostname instead of /etc/HOSTNAME
by Cristian Rodríguez 20 May '13

20 May '13

--- src/Restore.ycp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/Restore.ycp b/src/Restore.ycp index ad3391c..ffb1040 100644 --- a/src/Restore.ycp +++ b/src/Restore.ycp @@ -897,7 +897,7 @@ you may find current contact information at www.novell.com "kdebase3" : $["descr" : "KDE base package: base system", "files":["/etc/opt/kde3/share/config/kdm/kdmrc"], "prefix" : "", "sel_type" : "X", "vers" : "3.0-19"], "mozilla" : $["descr" : "Open Source WWW browser", "files" : ["/opt/mozilla/chrome/installed-chrome.txt"], "prefix" : "", "sel_type" : "X", "vers" : "0.9.8-54"], "lprng" : $["descr" : "LPRng Print Spooler", "files" : ["/etc/init.d/lpd"], "prefix" : "", "sel_type" : "X", "vers" : "3.8.5-49"], - "netcfg":$["descr" : "Network configuration files in /etc", "files" : ["/etc/HOSTNAME", "/etc/defaultdomain", "/etc/exports", "/etc/hosts"], "prefix":"", "sel_type":"X", "vers":"2002.3.20-0"] + "netcfg":$["descr" : "Network configuration files in /etc", "files" : ["/etc/hostname", "/etc/defaultdomain", "/etc/exports", "/etc/hosts"], "prefix":"", "sel_type":"X", "vers":"2002.3.20-0"] ]; // set default selection -- 1.8.2.3 -- 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] [PATCH yast-yast2] Use /etc/hostname instead of /etc/HOSTNAME
by Cristian Rodríguez 19 May '13

19 May '13

--- library/types/src/Hostname.ycp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/library/types/src/Hostname.ycp b/library/types/src/Hostname.ycp index a98aa30..65e091b 100644 --- a/library/types/src/Hostname.ycp +++ b/library/types/src/Hostname.ycp @@ -165,7 +165,7 @@ global define string CurrentFQ() { map hostname_data = (map) SCR::Execute(.target.bash_output, "hostname --fqdn"); if (hostname_data == nil || hostname_data["exit"]:-1 != 0 ) { - fqhostname = ($[] != (map) SCR::Read(.target.stat, "/etc/HOSTNAME") ? (string) SCR::Read(.target.string, "/etc/HOSTNAME"):""); + fqhostname = ($[] != (map) SCR::Read(.target.stat, "/etc/hostname") ? (string) SCR::Read(.target.string, "/etc/hostname"):""); if ( fqhostname == "" || fqhostname == nil ) { -- 1.8.2.3 -- 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] fulltime Y2DEBUG=1???
by Roberto Angelino 15 May '13

15 May '13

I have a customer who is asking if it's OK to set Y2DEBUG=1 all the time: When we encounter SLES media problem, one of the first things SuSE engineers ask us to do is reproduce with Y2DEBUG=1 on the kernel commandline. We were thinking about always having this media feature enabled going forward. Can we ask SuSE engineers if there is any cause for concern in doing this? ---- Roberto Angelino Dedicated Partner Engineer Developer Support (310) 529-3527 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

6 5

[yast-devel] Automatical built of YaST packages
by Thomas Goettlicher 10 May '13

10 May '13

Developers, I'm happy to announce that YaST packages are built and submitted automatically now. For every change of a YaST package located in the git repo's master branch ( https://github.com/yast/ ) the package is build automatically. On success it's submitted to YaST:Head in the build service, otherwise an email on yast-commit(a)opensuse.org informs about the failure. Packages in YaST:Head still need to be submitted to Factory manually because we want to make sure not to break Factory by this automatism. Cheers, 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 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

6 9

[yast-devel] YCP-killer and YCP data files
by Ladislav Slezak 02 May '13

02 May '13

Hi all, as you know we are working on a "YCP-killer" project, which should translate all YCP files to ruby and then get rid of our specific YCP language. I found a problem related to reading data YCP files. The problem is that some modules have data in YCP files which are read at runtime via these SCR calls: SCR::Read(.target.yast2, "foo.ycp") SCR::Read(.target.ycp, "bar.ycp") We can convert that YCP files to ruby with the converter but the loading mechanism will not not work. And keeping the data files in YCP format is also not an option. There are basically two possibilities: - convert the YCP files to a different format (plain text, YML, XML...) - modify the YCP files so that they can be used as an include file (includes are converted to ruby files so there is no change needed after the conversion) Which solution is better depends on the data in the file, some non-structured data could be simply converted to a plain text file, converting structured data is usually more complex. The second solution is easier for structured data as the file itself can be more or less left untouched, only the loading mechanism needs to be changed to an include statement. The disadvantage of the second solution is that the data is loaded persistently to memory (as it actually becomes code) so for large data files it might not be a good idea. As a proof of concept I adapted two YCP modules and changed the data files to includes, see these pull requests: https://github.com/yast/yast-ntp-client/pull/5/files https://github.com/yast/yast-mouse/pull/2/files The mouse module is little bit tricky as the database contains translations. And they need to be translated dynamically to reflect possible language changes during installation proposal, therefore I added a wrapper function which always returns a fresh instance of the data with the current translations. Conslusion: If you have some spare time and want to help us with the ruby translation you can start removing the YCP data files. You can look at the pull requests above for a hint how to do that. Or just ask here or on the IRC. Thank you! -- 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

8 16