Hello community, here is the log from the commit of package yast2-support for openSUSE:Factory checked in at 2014-04-26 06:06:39 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/yast2-support (Old) and /work/SRC/openSUSE:Factory/.yast2-support.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "yast2-support" Changes: -------- --- /work/SRC/openSUSE:Factory/yast2-support/yast2-support.changes 2013-10-19 11:21:05.000000000 +0200 +++ /work/SRC/openSUSE:Factory/.yast2-support.new/yast2-support.changes 2014-04-26 06:06:41.000000000 +0200 @@ -1,0 +2,7 @@ +Thu Apr 24 08:54:37 UTC 2014 - [email protected] + +- adjusted help text - name technical support correctly + (bnc#872123) +- 3.1.1 + +------------------------------------------------------------------- Old: ---- yast2-support-3.1.0.tar.bz2 New: ---- yast2-support-3.1.1.tar.bz2 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ yast2-support.spec ++++++ --- /var/tmp/diff_new_pack.OKVEQs/_old 2014-04-26 06:06:42.000000000 +0200 +++ /var/tmp/diff_new_pack.OKVEQs/_new 2014-04-26 06:06:42.000000000 +0200 @@ -1,7 +1,7 @@ # # spec file for package yast2-support # -# Copyright (c) 2013 SUSE LINUX Products GmbH, Nuernberg, Germany. +# Copyright (c) 2014 SUSE LINUX Products GmbH, Nuernberg, Germany. # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed @@ -17,7 +17,7 @@ Name: yast2-support -Version: 3.1.0 +Version: 3.1.1 Release: 0 BuildRoot: %{_tmppath}/%{name}-%{version}-build ++++++ yast2-support-3.1.0.tar.bz2 -> yast2-support-3.1.1.tar.bz2 ++++++ diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/yast2-support-3.1.0/CONTRIBUTING.md new/yast2-support-3.1.1/CONTRIBUTING.md --- old/yast2-support-3.1.0/CONTRIBUTING.md 1970-01-01 01:00:00.000000000 +0100 +++ new/yast2-support-3.1.1/CONTRIBUTING.md 2014-04-24 11:20:40.000000000 +0200 @@ -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_abbreviations). + +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-support-3.1.0/package/yast2-support.changes new/yast2-support-3.1.1/package/yast2-support.changes --- old/yast2-support-3.1.0/package/yast2-support.changes 2013-10-16 10:16:10.000000000 +0200 +++ new/yast2-support-3.1.1/package/yast2-support.changes 2014-04-24 11:20:40.000000000 +0200 @@ -1,4 +1,11 @@ ------------------------------------------------------------------- +Thu Apr 24 08:54:37 UTC 2014 - [email protected] + +- adjusted help text - name technical support correctly + (bnc#872123) +- 3.1.1 + +------------------------------------------------------------------- Thu Sep 19 17:29:23 UTC 2013 - [email protected] - do not use *.spec.in template, use *.spec file with RPM macros diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/yast2-support-3.1.0/package/yast2-support.spec new/yast2-support-3.1.1/package/yast2-support.spec --- old/yast2-support-3.1.0/package/yast2-support.spec 2013-10-16 10:16:10.000000000 +0200 +++ new/yast2-support-3.1.1/package/yast2-support.spec 2014-04-24 11:20:40.000000000 +0200 @@ -17,7 +17,7 @@ Name: yast2-support -Version: 3.1.0 +Version: 3.1.1 Release: 0 BuildRoot: %{_tmppath}/%{name}-%{version}-build diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/yast2-support-3.1.0/src/include/support/helps.rb new/yast2-support-3.1.1/src/include/support/helps.rb --- old/yast2-support-3.1.0/src/include/support/helps.rb 2013-10-16 10:16:10.000000000 +0200 +++ new/yast2-support-3.1.1/src/include/support/helps.rb 2014-04-24 11:20:40.000000000 +0200 @@ -73,7 +73,7 @@ "\n" + "<p><b><big>Opening Novell Support Center</big></b><br>\n" + "To start a Web browser that opens the Novell Support Center Portal, use <b>Open Novell Support Center</b>.\n" + - "You can then open a Service Request with Novell Technical Support. Make sure you write down\n" + + "You can then open a Service Request with Global Technical Support. Make sure you write down\n" + "the Service Request number to include in the supportconfig data upload.</p>\n" ) + # Ovreview dialog help 2/3 @@ -84,7 +84,7 @@ _( "<p><b><big>Uploading Collected Data</big></b><br>\n" + "To upload the data already collected to a server, use <b>Upload Data</b>.\n" + - "The server may or may not be Novell Technical Support.</p>" + "The server may or may not be Global Technical Support.</p>" ), # Configure1 dialog help 1/3 "support_params" => _( @@ -131,7 +131,7 @@ ) + # Contact dialog help 4/4 _( - "<p><b>Note:</b> If you are uploading a supportconfig tarball to Novell Technical Support,\nmake sure you include the Novell 11-digit service request number from your open service request.\n" + "<p><b>Note:</b> If you are uploading a supportconfig tarball to Global Technical Support,\nmake sure you include the Novell 11-digit service request number from your open service request.\n" ), # Collecting data dialkog help 1/1 "collecting" => _( @@ -146,7 +146,7 @@ # Configure1 dialog help 1/3 "upload_save" => Ops.add( _( - "<p><b><big>Upload supportconfig tarball to Novell Technical Support</big></b><br>\n" + + "<p><b><big>Upload supportconfig tarball to Global Technical Support</big></b><br>\n" + "If you want to store a copy of the supportconfig tarball, select the target\n" + "directory and make sure that this option is checked.\n" + "<br></p>\n" @@ -171,7 +171,7 @@ ), "upload_select" => Ops.add( _( - "<p><b><big>Upload supportconfig tarball to Novell Technical Support</big></b><br>\n" + + "<p><b><big>Upload supportconfig tarball to Global Technical Support</big></b><br>\n" + "If you have already created the supportconfig tarball, write the full path\n" + "into the <i>Package with log files</i> field.\n" + "<br></p>\n" -- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
