Script 'mail_helper' called by ro Hello packager, This is just FYI. Your package was checked in in distribution "sle12" by autobuild-member: ro. Here comes the log... ---------------------------%<------------------------------ Hi, here is the log from ci_new_pac /mounts/work_src_done/SLE12/yast2-sysconfig -> sle12 ## BNC# 869408 : "sysconfig editor mentions about the obsoleted SuSEconfig" (RESOLVED/FIXED) Changes: -------- --- /work/SRC/SUSE:SLE-12:GA/yast2-sysconfig/yast2-sysconfig.changes 2014-01-17 14:16:34.000000000 +0100 +++ /mounts/work_src_done/SLE12/yast2-sysconfig/yast2-sysconfig.changes 2014-03-28 16:07:46.000000000 +0100 @@ -1,0 +2,7 @@ +Fri Mar 28 15:56:52 CET 2014 - locilka@suse.com + +- Removed any mention about SuSEconfig, that has been already + dropped a while ago (bnc#869408) +- 3.1.1 + +------------------------------------------------------------------- calling whatdependson for sle12-i586 Packages directly triggered for rebuild: - yast2-dhcp-server - yast2-schema - yast2-sysconfig ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/SUSE:SLE-12:GA/yast2-sysconfig (Old) and /mounts/work_src_done/SLE12/yast2-sysconfig (BS:build ID:35167 MAIL:yast-commit@opensuse.org) (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Package is "yast2-sysconfig", Maintainer is "yast-commit@opensuse.org" Old: ---- yast2-sysconfig-3.1.0.tar.bz2 New: ---- yast2-sysconfig-3.1.1.tar.bz2 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ yast2-sysconfig.spec ++++++ --- /var/tmp/diff_new_pack.la3ii9/_old 2014-03-28 16:40:52.000000000 +0100 +++ /var/tmp/diff_new_pack.la3ii9/_new 2014-03-28 16:40:52.000000000 +0100 @@ -17,43 +17,32 @@ Name: yast2-sysconfig -Version: 3.1.0 +Version: 3.1.1 Release: 0 BuildRoot: %{_tmppath}/%{name}-%{version}-build Source0: %{name}-%{version}.tar.bz2 -BuildRequires: perl-XML-Writer -BuildRequires: update-desktop-files -BuildRequires: yast2 -BuildRequires: yast2-devtools >= 3.0.6 -BuildRequires: yast2-testsuite +Group: System/YaST +License: GPL-2.0+ +BuildRequires: perl-XML-Writer update-desktop-files yast2 yast2-testsuite +BuildRequires: yast2-devtools >= 3.1.10 Requires: perl Requires: yast2 >= 2.21.22 # For tests BuildRequires: ruby -BuildArch: noarch +BuildArchitectures: noarch -Provides: y2c_rc_config -Provides: yast2-config-rcconfig -Provides: yast2-config-sysconfig -Obsoletes: y2c_rc_config -Obsoletes: yast2-config-rcconfig -Obsoletes: yast2-config-sysconfig -Provides: y2t_rc_config -Provides: yast2-trans-rcconfig -Provides: yast2-trans-sysconfig -Obsoletes: y2t_rc_config -Obsoletes: yast2-trans-rcconfig -Obsoletes: yast2-trans-sysconfig +Provides: y2c_rc_config yast2-config-rcconfig yast2-config-sysconfig +Obsoletes: y2c_rc_config yast2-config-rcconfig yast2-config-sysconfig +Provides: yast2-trans-sysconfig yast2-trans-rcconfig y2t_rc_config +Obsoletes: yast2-trans-sysconfig yast2-trans-rcconfig y2t_rc_config Requires: yast2-ruby-bindings >= 1.0.0 Summary: YaST2 - Sysconfig Editor -License: GPL-2.0+ -Group: System/YaST %description A graphical /etc/sysconfig/* editor with integrated search and context @@ -61,8 +50,8 @@ %package devel-doc Requires: yast2-sysconfig = %version -Summary: YaST2 - Sysconfig Editor - Development Documentation Group: System/YaST +Summary: YaST2 - Sysconfig Editor - Development Documentation %description devel-doc This package contains development documentation for using the API @@ -77,6 +66,7 @@ %install %yast_install + %files %defattr(-,root,root) %dir %{yast_yncludedir}/sysconfig @@ -96,4 +86,3 @@ %files devel-doc %doc %{yast_docdir}/autodocs -%changelog ++++++ yast2-sysconfig-3.1.0.tar.bz2 -> yast2-sysconfig-3.1.1.tar.bz2 ++++++ diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/yast2-sysconfig-3.1.0/CONTRIBUTING.md new/yast2-sysconfig-3.1.1/CONTRIBUTING.md --- old/yast2-sysconfig-3.1.0/CONTRIBUTING.md 1970-01-01 01:00:00.000000000 +0100 +++ new/yast2-sysconfig-3.1.1/CONTRIBUTING.md 2014-03-28 16:08:28.000000000 +0100 @@ -0,0 +1,87 @@ +YaST Contribution Guidelines +============================ + +YaST is an open source project and as such it welcomes all kinds of +contributions. If you decide to contribute, please follow these guidelines to +ensure the process is effective and pleasant both for you and YaST maintainers. + +There are two main forms of contribution: reporting bugs and performing code +changes. + +Bug Reports +----------- + +If you find a problem, please report it either using +[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guided&product=openSUSE+Factory&component=YaST2) +or [GitHub issues](../../issues). (For Bugzilla, use the [simplified +registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp) +if you don't have an account yet.) + +If you find a problem, please report it either using +[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee +that every bug will be fixed, but we'll try. + +When creating a bug report, please follow our [bug reporting +guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug). + +Code Changes +------------ + +We welcome all kinds of code contributions, from simple bug fixes to significant +refactorings and implementation of new features. However, before making any +non-trivial contribution, get in touch with us first — this can prevent wasted +effort on both sides. Also, have a look at our [development +documentation](http://en.opensuse.org/openSUSE:YaST_development). + +To send us your code change, use GitHub pull requests. The workflow is as +follows: + + 1. Fork the project. + + 2. Create a topic branch based on `master`. + + 3. Implement your change, including tests (if possible). Make sure you adhere + to the [Ruby style + guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md). + + 4. Make sure your change didn't break anything by building the RPM package + (`rake osc:build`). The build process includes running the full testsuite. + + 5. Publish the branch and create a pull request. + + 6. YaST developers will review your change and possibly point out issues. + Adapt the code under their guidance until they are all resolved. + + 7. Finally, the pull request will get merged or rejected. + +See also [GitHub's guide on +contributing](https://help.github.com/articles/fork-a-repo). + +If you want to do multiple unrelated changes, use separate branches and pull +requests. + +Do not change the `VERSION` and `*.changes` files as this could lead to +conflicts. + +### Commits + +Each commit in the pull request should do only one thing, which is clearly +described by its commit message. Especially avoid mixing formatting changes and +functional changes into one commit. When writing commit messages, adhere to +[widely used +conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html). + +If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure +you mention it in the commit message for cross-reference. Use format like +bnc#775814 or gh#yast/yast-foo#42. See also [GitHub +autolinking](https://help.github.com/articles/github-flavored-markdown#references) +and [openSUSE abbreviation +reference](http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines#Current_set_of_...). + +Additional Information +---------------------- + +If you have any question, feel free to ask at the [development mailing +list](http://lists.opensuse.org/yast-devel/) or at the +[#yast](http://webchat.freenode.net/?channels=%23yast) IRC channel on freenode. +We'll do our best to provide a timely and accurate answer. diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/yast2-sysconfig-3.1.0/VERSION new/yast2-sysconfig-3.1.1/VERSION --- old/yast2-sysconfig-3.1.0/VERSION 2013-10-21 10:02:10.000000000 +0200 +++ new/yast2-sysconfig-3.1.1/VERSION 1970-01-01 01:00:00.000000000 +0100 @@ -1 +0,0 @@ -3.1.0 diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/yast2-sysconfig-3.1.0/doc/metadata.txt new/yast2-sysconfig-3.1.1/doc/metadata.txt --- old/yast2-sysconfig-3.1.0/doc/metadata.txt 2013-10-21 10:02:10.000000000 +0200 +++ new/yast2-sysconfig-3.1.1/doc/metadata.txt 2014-03-28 16:08:28.000000000 +0100 @@ -75,8 +75,7 @@ can be avoided by defining right descriptions. Action keywords describe actions which are required to activate changes. -Usually it means starting SuSEconfig module and service restart or -reload. +Usually it means a service restart or reload. I. Descriptive keywords: @@ -143,8 +142,6 @@ it is required to do an action with old value (e.g. stop daemon which name is changed) - Config - start selected SuSEconfig/ULconfig modules - ServiceReload - reload services if they are running (specify only the init script file names without the path) @@ -190,7 +187,7 @@ All sysconfig variables are divided into basic categories: Hardware - all hardware related settings (e.g. sysconfig files: sound, keyboard...) -System - basic system configuration (boot, suseconfig, cron, console, security...) +System - basic system configuration (boot, cron, console, security...) Desktop - desktop settings (kde, gnome, xdm...) Applications - java, ispell, man... Network - network services (apache, mail, nfs...) @@ -246,21 +243,11 @@ - save all changed variables - - start all specified SuSEconfig modules - - restart/reload specified services which are running (command "/etc/init.d/testservice status" returns 0). - start generic commands - - If activation commands are missing in the whole sysconfig file complete -SuSEconfig will be started for backward compatibility with old sysconfig files. -Some variables need no activation (e.g. options in /etc/sysconfig/boot file are -used only at boot), use empty Config: tag (or any from above tags) to not start -the SuSEconfig script - if some action tag is specified (even empty) the -backward compatible action (calling the SuSEconfig script) will not be started. - Each command will be started only once to speed up the activation if more modified variables need the same activation command. The commands are compared without any parsing or semantic check when testing whether the command has diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/yast2-sysconfig-3.1.0/package/yast2-sysconfig.changes new/yast2-sysconfig-3.1.1/package/yast2-sysconfig.changes --- old/yast2-sysconfig-3.1.0/package/yast2-sysconfig.changes 2013-10-21 10:02:10.000000000 +0200 +++ new/yast2-sysconfig-3.1.1/package/yast2-sysconfig.changes 2014-03-28 16:08:28.000000000 +0100 @@ -1,4 +1,11 @@ ------------------------------------------------------------------- +Fri Mar 28 15:56:52 CET 2014 - locilka@suse.com + +- Removed any mention about SuSEconfig, that has been already + dropped a while ago (bnc#869408) +- 3.1.1 + +------------------------------------------------------------------- Thu Sep 19 17:33:13 UTC 2013 - lslezak@suse.cz - do not use *.spec.in template, use *.spec file with RPM macros diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/yast2-sysconfig-3.1.0/package/yast2-sysconfig.spec new/yast2-sysconfig-3.1.1/package/yast2-sysconfig.spec --- old/yast2-sysconfig-3.1.0/package/yast2-sysconfig.spec 2013-10-21 10:22:10.000000000 +0200 +++ new/yast2-sysconfig-3.1.1/package/yast2-sysconfig.spec 2014-03-28 16:08:28.000000000 +0100 @@ -17,7 +17,7 @@ Name: yast2-sysconfig -Version: 3.1.0 +Version: 3.1.1 Release: 0 BuildRoot: %{_tmppath}/%{name}-%{version}-build @@ -26,7 +26,7 @@ Group: System/YaST License: GPL-2.0+ BuildRequires: perl-XML-Writer update-desktop-files yast2 yast2-testsuite -BuildRequires: yast2-devtools >= 3.0.6 +BuildRequires: yast2-devtools >= 3.1.10 Requires: perl Requires: yast2 >= 2.21.22 diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/yast2-sysconfig-3.1.0/src/include/sysconfig/complex.rb new/yast2-sysconfig-3.1.1/src/include/sysconfig/complex.rb --- old/yast2-sysconfig-3.1.0/src/include/sysconfig/complex.rb 2013-10-21 10:02:10.000000000 +0200 +++ new/yast2-sysconfig-3.1.1/src/include/sysconfig/complex.rb 2014-03-28 16:08:28.000000000 +0100 @@ -314,7 +314,7 @@ Ops.greater_than(Builtins.size(conf_modules), 0) # parse string with options, then add them to the rich text conf = String.ParseOptions(conf_modules, Sysconfig.parse_param) - # header in the variable description text, SuSEconfig/ULconfig module names are appended + # header in the variable description text result = Ops.add( Ops.add( Ops.add( @@ -815,21 +815,15 @@ Wizard.CreateTree(_Tree, _("&Configuration Options")) helptext = - # helptext for popup - part 1/3 + # helptext for popup - part 1/2 _( "<p>After you save your changes, this editor changes the variables in the\n" + "corresponding sysconfig file. Then it starts activation commands, which changes the underlying configuration files, stops and starts daemons,\n" + "and runs low-level configuration tools so your configuration in sysconfig takes effect.</p>\n" ) + - # helptext for popup - part 2/3 + # helptext for popup - part 2/2 _( "<p><b>Important:</b> You still can edit each individual configuration file manually. The name of file is displayed in the variable description.</p>" - ) + - # helptext for popup - part 3/3 - _( - "<p> SuSEconfig saves a checksum of each configuration file, so it can detect if\n" + - " you have manually changed any of them. If you have changed a configuration file manually,\n" + - " it will not touch it.</p>\n" ) Wizard.SetContents( continue with "q"... Checked in at Fri Mar 28 16:41:28 CET 2014 by ro Remember to have fun... -- To unsubscribe, e-mail: yast-commit+unsubscribe@opensuse.org For additional commands, e-mail: yast-commit+help@opensuse.org