Hello community, here is the log from the commit of package yast2-add-on for openSUSE:Factory checked in at 2020-05-09 19:50:50 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/yast2-add-on (Old) and /work/SRC/openSUSE:Factory/.yast2-add-on.new.2738 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "yast2-add-on" Sat May 9 19:50:50 2020 rev:105 rq:801298 version:4.3.0 Changes: -------- --- /work/SRC/openSUSE:Factory/yast2-add-on/yast2-add-on.changes 2020-01-30 09:41:30.429493520 +0100 +++ /work/SRC/openSUSE:Factory/.yast2-add-on.new.2738/yast2-add-on.changes 2020-05-09 19:51:04.940674039 +0200 @@ -1,0 +2,7 @@ +Thu May 7 08:58:18 UTC 2020 - Josef Reidinger <[email protected]> + +- Autoyast schema: Allow optional types for string and map objects + (bsc#1170886) +- 4.3.0 + +------------------------------------------------------------------- Old: ---- yast2-add-on-4.2.15.tar.bz2 New: ---- yast2-add-on-4.3.0.tar.bz2 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ yast2-add-on.spec ++++++ --- /var/tmp/diff_new_pack.byXdXe/_old 2020-05-09 19:51:05.432675095 +0200 +++ /var/tmp/diff_new_pack.byXdXe/_new 2020-05-09 19:51:05.436675104 +0200 @@ -17,7 +17,7 @@ Name: yast2-add-on -Version: 4.2.15 +Version: 4.3.0 Release: 0 Summary: YaST2 - Add-On media installation code License: GPL-2.0-only ++++++ yast2-add-on-4.2.15.tar.bz2 -> yast2-add-on-4.3.0.tar.bz2 ++++++ diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/yast2-add-on-4.2.15/CONTRIBUTING.md new/yast2-add-on-4.3.0/CONTRIBUTING.md --- old/yast2-add-on-4.2.15/CONTRIBUTING.md 2020-01-28 09:54:37.000000000 +0100 +++ new/yast2-add-on-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-add-on-4.2.15/package/yast2-add-on.changes new/yast2-add-on-4.3.0/package/yast2-add-on.changes --- old/yast2-add-on-4.2.15/package/yast2-add-on.changes 2020-01-28 09:54:37.000000000 +0100 +++ new/yast2-add-on-4.3.0/package/yast2-add-on.changes 2020-05-07 17:40:11.000000000 +0200 @@ -1,4 +1,11 @@ ------------------------------------------------------------------- +Thu May 7 08:58:18 UTC 2020 - Josef Reidinger <[email protected]> + +- Autoyast schema: Allow optional types for string and map objects + (bsc#1170886) +- 4.3.0 + +------------------------------------------------------------------- Tue Jan 28 09:30:52 CET 2020 - [email protected] - Fix in installation workflow: Can go back from diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/yast2-add-on-4.2.15/package/yast2-add-on.spec new/yast2-add-on-4.3.0/package/yast2-add-on.spec --- old/yast2-add-on-4.2.15/package/yast2-add-on.spec 2020-01-28 09:54:37.000000000 +0100 +++ new/yast2-add-on-4.3.0/package/yast2-add-on.spec 2020-05-07 17:40:11.000000000 +0200 @@ -17,7 +17,7 @@ Name: yast2-add-on -Version: 4.2.15 +Version: 4.3.0 Release: 0 Summary: YaST2 - Add-On media installation code License: GPL-2.0-only diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/yast2-add-on-4.2.15/src/autoyast-rnc/add-on.rnc new/yast2-add-on-4.3.0/src/autoyast-rnc/add-on.rnc --- old/yast2-add-on-4.2.15/src/autoyast-rnc/add-on.rnc 2020-01-28 09:54:37.000000000 +0100 +++ new/yast2-add-on-4.3.0/src/autoyast-rnc/add-on.rnc 2020-05-07 17:40:11.000000000 +0200 @@ -2,53 +2,73 @@ namespace a = "http://relaxng.org/ns/compatibility/annotations/1.0"; namespace config = "http://www.suse.com/1.0/configns"; +include "common.rnc" + add-on = element add-on { - add_on_products* & - add_on_others* + MAP, + ( + add_on_products* & + add_on_others* + ) } listentry = element listentry { - media_url & # here it is mandatory - product? & - name? & - alias? & - product_dir? & - ask_on_error? & - confirm_license? & - priority? & - element signature-handling { - element accept_unsigned_file { BOOLEAN }? & - element accept_file_without_checksum { BOOLEAN }? & - element accept_verification_failed { BOOLEAN }? & - element accept_unknown_gpg_key { - element all { BOOLEAN }? & - element keys { - LIST, - element keyid { text }* - }? - }? & - element accept_non_trusted_gpg_key { - element all { BOOLEAN }? & - element keys { - LIST, - element keyid { text }* + MAP, + ( + media_url & # here it is mandatory + product? & + name? & + alias? & + product_dir? & + ask_on_error? & + confirm_license? & + priority? & + element signature-handling { + MAP, + ( + element accept_unsigned_file { BOOLEAN }? & + element accept_file_without_checksum { BOOLEAN }? & + element accept_verification_failed { BOOLEAN }? & + element accept_unknown_gpg_key { + MAP, + ( + element all { BOOLEAN }? & + element keys { + LIST, + element keyid { STRING }* + }? + ) + }? & + element accept_non_trusted_gpg_key { + MAP, + ( + element all { BOOLEAN }? & + element keys { + LIST, + element keyid { STRING }* + }? + ) + }? & + element import_gpg_key { + MAP, + ( + element all { BOOLEAN }? & + element keys { + LIST, + element keyid { STRING }* + }? + ) }? - }? & - element import_gpg_key { - element all { BOOLEAN }? & - element keys { - LIST, - element keyid { text }* - }? - }? - }? + ) + }? + ) } -media_url = element media_url { text } -product = element product { text } -name = element name { text } -alias = element alias { text } -product_dir = element product_dir { text } +media_url = element media_url { STRING } +product = element product { STRING } +name = element name { STRING } +alias = element alias { STRING } +product_dir = element product_dir { STRING } ask_on_error = element ask_on_error { BOOLEAN } confirm_license = element confirm_license { BOOLEAN } priority = element priority { INTEGER } @@ -73,4 +93,4 @@ element add_on_others { attribute config:type { text }?, listentry* - } + }
