Hello community,
here is the log from the commit of package yast2-configuration-management for
openSUSE:Factory checked in at 2020-05-09 19:51:04
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/yast2-configuration-management (Old)
and /work/SRC/openSUSE:Factory/.yast2-configuration-management.new.2738
(New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "yast2-configuration-management"
Sat May 9 19:51:04 2020 rev:15 rq:801310 version:4.3.0
Changes:
--------
---
/work/SRC/openSUSE:Factory/yast2-configuration-management/yast2-configuration-management.changes
2020-04-05 20:50:44.769021945 +0200
+++
/work/SRC/openSUSE:Factory/.yast2-configuration-management.new.2738/yast2-configuration-management.changes
2020-05-09 19:51:11.736688628 +0200
@@ -1,0 +2,7 @@
+Thu May 7 15:05:43 UTC 2020 - Josef Reidinger <jreidin...@suse.com>
+
+- Autoyast schema: Allow optional types for string and map objects
+ (bsc#1170886)
+- 4.3.0
+
+-------------------------------------------------------------------
Old:
----
yast2-configuration-management-4.2.4.tar.bz2
New:
----
yast2-configuration-management-4.3.0.tar.bz2
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ yast2-configuration-management.spec ++++++
--- /var/tmp/diff_new_pack.q08sDN/_old 2020-05-09 19:51:12.900691127 +0200
+++ /var/tmp/diff_new_pack.q08sDN/_new 2020-05-09 19:51:12.904691136 +0200
@@ -17,7 +17,7 @@
Name: yast2-configuration-management
-Version: 4.2.4
+Version: 4.3.0
Release: 0
Url: https://github.com/yast/yast-migration
Summary: YaST2 - YaST Configuration Management
++++++ yast2-configuration-management-4.2.4.tar.bz2 ->
yast2-configuration-management-4.3.0.tar.bz2 ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-configuration-management-4.2.4/CONTRIBUTING.md
new/yast2-configuration-management-4.3.0/CONTRIBUTING.md
--- old/yast2-configuration-management-4.2.4/CONTRIBUTING.md 2020-03-31
12:00:20.000000000 +0200
+++ new/yast2-configuration-management-4.3.0/CONTRIBUTING.md 1970-01-01
01:00:00.000000000 +0100
@@ -1,87 +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 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 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-configuration-management-4.2.4/package/yast2-configuration-management.changes
new/yast2-configuration-management-4.3.0/package/yast2-configuration-management.changes
---
old/yast2-configuration-management-4.2.4/package/yast2-configuration-management.changes
2020-03-31 12:00:20.000000000 +0200
+++
new/yast2-configuration-management-4.3.0/package/yast2-configuration-management.changes
2020-05-07 17:58:51.000000000 +0200
@@ -1,4 +1,11 @@
-------------------------------------------------------------------
+Thu May 7 15:05:43 UTC 2020 - Josef Reidinger <jreidin...@suse.com>
+
+- Autoyast schema: Allow optional types for string and map objects
+ (bsc#1170886)
+- 4.3.0
+
+-------------------------------------------------------------------
Mon Mar 30 21:01:50 UTC 2020 - Imobach Gonzalez Sosa <igonzalezs...@suse.com>
- Do not force to use formulas during the 1st stage (bsc#1168080).
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/yast2-configuration-management-4.2.4/package/yast2-configuration-management.spec
new/yast2-configuration-management-4.3.0/package/yast2-configuration-management.spec
---
old/yast2-configuration-management-4.2.4/package/yast2-configuration-management.spec
2020-03-31 12:00:20.000000000 +0200
+++
new/yast2-configuration-management-4.3.0/package/yast2-configuration-management.spec
2020-05-07 17:58:51.000000000 +0200
@@ -17,7 +17,7 @@
Name: yast2-configuration-management
-Version: 4.2.4
+Version: 4.3.0
Release: 0
Url: https://github.com/yast/yast-migration
Summary: YaST2 - YaST Configuration Management
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/yast2-configuration-management-4.2.4/src/autoyast-rnc/configuration_management.rnc
new/yast2-configuration-management-4.3.0/src/autoyast-rnc/configuration_management.rnc
---
old/yast2-configuration-management-4.2.4/src/autoyast-rnc/configuration_management.rnc
2020-03-31 12:00:20.000000000 +0200
+++
new/yast2-configuration-management-4.3.0/src/autoyast-rnc/configuration_management.rnc
2020-05-07 17:58:51.000000000 +0200
@@ -2,23 +2,28 @@
namespace a = "http://relaxng.org/ns/compatibility/annotations/1.0";
namespace config = "http://www.suse.com/1.0/configns";
+include "common.rnc"
+
configuration_management = element configuration_management {
- element type { text }? &
- element master { text }? &
- element auth_attempts { INTEGER }? &
- element auth_time_out { INTEGER }? &
- element enable_services { BOOLEAN }? &
- element formulas_roots { LIST, formulas_root* }? &
- element states_roots { LIST, states_root* }? &
- element pillar_root { text }? &
- element pillar_url { text }? &
- element keys_url { text }? &
- element states_url { text }? &
- element modules_url { LIST, modules_url* }? &
- element enabled_states { LIST, enabled_state* }?
+ MAP,
+ (
+ element type { STRING }? &
+ element master { STRING }? &
+ element auth_attempts { INTEGER }? &
+ element auth_time_out { INTEGER }? &
+ element enable_services { BOOLEAN }? &
+ element formulas_roots { LIST, formulas_root* }? &
+ element states_roots { LIST, states_root* }? &
+ element pillar_root { STRING }? &
+ element pillar_url { STRING }? &
+ element keys_url { STRING }? &
+ element states_url { STRING }? &
+ element modules_url { LIST, modules_url* }? &
+ element enabled_states { LIST, enabled_state* }?
+ )
}
-formulas_root = element (path | listentry) { text }
-states_root = element (path | listentry) { text }
-modules_url = element (url | listentry) { text }
-enabled_state = element (state | listentry) { text }
+formulas_root = element (path | listentry) { STRING }
+states_root = element (path | listentry) { STRING }
+modules_url = element (url | listentry) { STRING }
+enabled_state = element (state | listentry) { STRING }
