Hello community, here is the log from the commit of package yast2-kdump for openSUSE:Factory checked in at 2020-05-15 23:50:23 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/yast2-kdump (Old) and /work/SRC/openSUSE:Factory/.yast2-kdump.new.2738 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "yast2-kdump" Fri May 15 23:50:23 2020 rev:100 rq:803136 version:4.3.0 Changes: -------- --- /work/SRC/openSUSE:Factory/yast2-kdump/yast2-kdump.changes 2020-03-01 21:26:54.684422088 +0100 +++ /work/SRC/openSUSE:Factory/.yast2-kdump.new.2738/yast2-kdump.changes 2020-05-15 23:50:26.657327660 +0200 @@ -1,0 +2,7 @@ +Tue May 12 09:10:14 UTC 2020 - Josef Reidinger <[email protected]> + +- Autoyast schema: Allow optional types for string and map objects + (bsc#1170886) +- 4.3.0 + +------------------------------------------------------------------- Old: ---- yast2-kdump-4.2.9.tar.bz2 New: ---- yast2-kdump-4.3.0.tar.bz2 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ yast2-kdump.spec ++++++ --- /var/tmp/diff_new_pack.n20UPe/_old 2020-05-15 23:50:27.353329001 +0200 +++ /var/tmp/diff_new_pack.n20UPe/_new 2020-05-15 23:50:27.353329001 +0200 @@ -17,7 +17,7 @@ Name: yast2-kdump -Version: 4.2.9 +Version: 4.3.0 Release: 0 Summary: Configuration of kdump License: GPL-2.0-only ++++++ yast2-kdump-4.2.9.tar.bz2 -> yast2-kdump-4.3.0.tar.bz2 ++++++ diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/yast2-kdump-4.2.9/.travis.yml new/yast2-kdump-4.3.0/.travis.yml --- old/yast2-kdump-4.2.9/.travis.yml 2020-02-18 13:49:52.000000000 +0100 +++ new/yast2-kdump-4.3.0/.travis.yml 2020-05-12 17:36:35.000000000 +0200 @@ -8,4 +8,4 @@ script: # the "yast-travis-ruby" script is included in the base yastdevel/ruby image # see https://github.com/yast/docker-yast-ruby/blob/master/yast-travis-ruby - - docker run -it -e TRAVIS=1 -e TRAVIS_JOB_ID="$TRAVIS_JOB_ID" yast-kdump-image yast-travis-ruby + - docker run -it --privileged -e TRAVIS=1 -e TRAVIS_JOB_ID="$TRAVIS_JOB_ID" yast-kdump-image yast-travis-ruby diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/yast2-kdump-4.2.9/CONTRIBUTING.md new/yast2-kdump-4.3.0/CONTRIBUTING.md --- old/yast2-kdump-4.2.9/CONTRIBUTING.md 2020-02-18 13:49:52.000000000 +0100 +++ new/yast2-kdump-4.3.0/CONTRIBUTING.md 1970-01-01 01:00:00.000000000 +0100 @@ -1,89 +0,0 @@ -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 the 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.suse.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.) - -When creating a bug report, please follow our [bug reporting -guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug). - -We can't guarantee that every bug will be fixed, but we'll try. - -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. Update the package version (in `packages/*.spec`, usually by - `rake version:bump`) and add a new entry to the `package/*.changes` file - (by `osc vc package`). - For bigger changes or changes which need longer discussion it is advised to - add this as a separate last commit so it can be easily updated when another - change is merged in the meantime. - - 5. Make sure your change didn't break anything by building the RPM package - (`rake osc:build`). The build process includes running the full testsuite. - - 6. Publish the branch and create a pull request. - - 7. YaST developers will review your change and possibly point out issues. - Adapt the code under their guidance until they are all resolved. - - 8. 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. - -### 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 Bugzilla 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-kdump-4.2.9/package/yast2-kdump.changes new/yast2-kdump-4.3.0/package/yast2-kdump.changes --- old/yast2-kdump-4.2.9/package/yast2-kdump.changes 2020-02-18 13:49:52.000000000 +0100 +++ new/yast2-kdump-4.3.0/package/yast2-kdump.changes 2020-05-12 17:36:35.000000000 +0200 @@ -1,4 +1,11 @@ ------------------------------------------------------------------- +Tue May 12 09:10:14 UTC 2020 - Josef Reidinger <[email protected]> + +- Autoyast schema: Allow optional types for string and map objects + (bsc#1170886) +- 4.3.0 + +------------------------------------------------------------------- Tue Feb 18 11:35:05 UTC 2020 - Stefan Hundhammer <[email protected]> - Fixed user-visible messages (bsc#1084015) diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/yast2-kdump-4.2.9/package/yast2-kdump.spec new/yast2-kdump-4.3.0/package/yast2-kdump.spec --- old/yast2-kdump-4.2.9/package/yast2-kdump.spec 2020-02-18 13:49:52.000000000 +0100 +++ new/yast2-kdump-4.3.0/package/yast2-kdump.spec 2020-05-12 17:36:35.000000000 +0200 @@ -17,7 +17,7 @@ Name: yast2-kdump -Version: 4.2.9 +Version: 4.3.0 Release: 0 Summary: Configuration of kdump License: GPL-2.0-only diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/yast2-kdump-4.2.9/src/autoyast-rnc/kdump.rnc new/yast2-kdump-4.3.0/src/autoyast-rnc/kdump.rnc --- old/yast2-kdump-4.2.9/src/autoyast-rnc/kdump.rnc 2020-02-18 13:49:52.000000000 +0100 +++ new/yast2-kdump-4.3.0/src/autoyast-rnc/kdump.rnc 2020-05-12 17:36:35.000000000 +0200 @@ -2,57 +2,63 @@ namespace a = "http://relaxng.org/ns/compatibility/annotations/1.0"; namespace config = "http://www.suse.com/1.0/configns"; +include "common.rnc" kdump = element kdump { - (kdump_crash_kernel_value | kdump_crash_kernel_list)? & - # parameter specify crashkernel value for xen hypervisor - (kdump_crash_xen_kernel_value | kdump_crash_xen_kernel_list)? & - kdump_add_crash_kernel? & - kdump_general? + MAP, + ( + (kdump_crash_kernel_value | kdump_crash_kernel_list)? & + # parameter specify crashkernel value for xen hypervisor + (kdump_crash_xen_kernel_value | kdump_crash_xen_kernel_list)? & + kdump_add_crash_kernel? & + kdump_general? + ) } -kdump_crash_kernel_value = element crash_kernel { text } -kdump_crash_xen_kernel_value = element crash_xen_kernel { text } +kdump_crash_kernel_value = element crash_kernel { STRING } +kdump_crash_xen_kernel_value = element crash_xen_kernel { STRING } kdump_crash_kernel_list = element crash_kernel { - LIST, - kdump_crash_kernel_entry+ + LIST, + kdump_crash_kernel_entry+ } kdump_crash_xen_kernel_list = element crash_xen_kernel { - LIST, - kdump_crash_kernel_entry+ + LIST, + kdump_crash_kernel_entry+ } -kdump_crash_kernel_entry = element listentry { text } +kdump_crash_kernel_entry = element listentry { STRING } kdump_add_crash_kernel = element add_crash_kernel { BOOLEAN } -kdump_general = - element general { - element KDUMP_KERNELVER { text }? & - element KDUMP_CPUS { text }? & - element KDUMP_COMMANDLINE { text }? & - element KDUMP_COMMANDLINE_APPEND { text }? & - element KDUMP_CONTINUE_ON_ERROR { text }? & - element KDUMP_REQUIRED_PROGRAMS { text }? & - element KDUMP_PRESCRIPT { text }? & - element KDUMP_POSTSCRIPT { text }? & - element KDUMPTOOL_FLAGS { text }? & - element KDUMP_NETCONFIG { text }? & - element KDUMP_NET_TIMEOUT { text }? & - element KDUMP_COPY_KERNEL { text }? & - element KEXEC_OPTIONS { text }? & - element KDUMP_RUNLEVEL { text }? & - element KDUMP_IMMEDIATE_REBOOT { text }? & - element KDUMP_TRANSFER { text }? & - element KDUMP_SAVEDIR { text }? & - element KDUMP_KEEP_OLD_DUMPS { text }? & - element KDUMP_FREE_DISK_SIZE { text }? & - element KDUMP_VERBOSE { text }? & - element KDUMP_DUMPLEVEL { text }? & - element KDUMP_DUMPFORMAT { text }? & - element KDUMP_SMTP_SERVER { text }? & - element KDUMP_SMTP_USER { text }? & - element KDUMP_SMTP_PASSWORD { text }? & - element KDUMP_NOTIFICATION_TO { text }? & - element KDUMP_NOTIFICATION_CC { text }? & - element KDUMP_HOST_KEY { text }? +kdump_general = element general { + MAP, + ( + element KDUMP_KERNELVER { STRING }? & + element KDUMP_CPUS { STRING }? & + element KDUMP_COMMANDLINE { STRING }? & + element KDUMP_COMMANDLINE_APPEND { STRING }? & + element KDUMP_CONTINUE_ON_ERROR { STRING }? & + element KDUMP_REQUIRED_PROGRAMS { STRING }? & + element KDUMP_PRESCRIPT { STRING }? & + element KDUMP_POSTSCRIPT { STRING }? & + element KDUMPTOOL_FLAGS { STRING }? & + element KDUMP_NETCONFIG { STRING }? & + element KDUMP_NET_TIMEOUT { STRING }? & + element KDUMP_COPY_KERNEL { STRING }? & + element KEXEC_OPTIONS { STRING }? & + element KDUMP_RUNLEVEL { STRING }? & + element KDUMP_IMMEDIATE_REBOOT { STRING }? & + element KDUMP_TRANSFER { STRING }? & + element KDUMP_SAVEDIR { STRING }? & + element KDUMP_KEEP_OLD_DUMPS { STRING }? & + element KDUMP_FREE_DISK_SIZE { STRING }? & + element KDUMP_VERBOSE { STRING }? & + element KDUMP_DUMPLEVEL { STRING }? & + element KDUMP_DUMPFORMAT { STRING }? & + element KDUMP_SMTP_SERVER { STRING }? & + element KDUMP_SMTP_USER { STRING }? & + element KDUMP_SMTP_PASSWORD { STRING }? & + element KDUMP_NOTIFICATION_TO { STRING }? & + element KDUMP_NOTIFICATION_CC { STRING }? & + element KDUMP_HOST_KEY { STRING }? + ) }
