Hello community,

here is the log from the commit of package yast2-services-manager for 
openSUSE:Factory checked in at 2020-05-15 23:50:40
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/yast2-services-manager (Old)
 and      /work/SRC/openSUSE:Factory/.yast2-services-manager.new.2738 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "yast2-services-manager"

Fri May 15 23:50:40 2020 rev:52 rq:803184 version:4.3.0

Changes:
--------
--- 
/work/SRC/openSUSE:Factory/yast2-services-manager/yast2-services-manager.changes
    2019-09-23 13:15:25.605126396 +0200
+++ 
/work/SRC/openSUSE:Factory/.yast2-services-manager.new.2738/yast2-services-manager.changes
  2020-05-15 23:50:43.989361060 +0200
@@ -1,0 +2,7 @@
+Tue May 12 15:32:28 UTC 2020 - josef Reidinger <jreidinger@localhost>
+
+- Autoyast schema: Allow optional types for string and map objects
+  (bsc#1170886)
+- 4.3.0
+
+-------------------------------------------------------------------

Old:
----
  yast2-services-manager-4.2.5.tar.bz2

New:
----
  yast2-services-manager-4.3.0.tar.bz2

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ yast2-services-manager.spec ++++++
--- /var/tmp/diff_new_pack.RRperr/_old  2020-05-15 23:50:44.813362648 +0200
+++ /var/tmp/diff_new_pack.RRperr/_new  2020-05-15 23:50:44.813362648 +0200
@@ -1,7 +1,7 @@
 #
 # spec file for package yast2-services-manager
 #
-# Copyright (c) 2019 SUSE LINUX GmbH, Nuernberg, Germany.
+# Copyright (c) 2020 SUSE LINUX GmbH, Nuernberg, Germany.
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -24,7 +24,7 @@
 ######################################################################
 
 Name:           yast2-services-manager
-Version:        4.2.5
+Version:        4.3.0
 Release:        0
 Summary:        YaST2 - Services Manager
 License:        GPL-2.0-or-later

++++++ yast2-services-manager-4.2.5.tar.bz2 -> 
yast2-services-manager-4.3.0.tar.bz2 ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/yast2-services-manager-4.2.5/CONTRIBUTING.md 
new/yast2-services-manager-4.3.0/CONTRIBUTING.md
--- old/yast2-services-manager-4.2.5/CONTRIBUTING.md    2019-09-09 
11:07:40.000000000 +0200
+++ new/yast2-services-manager-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-services-manager-4.2.5/package/yast2-services-manager.changes 
new/yast2-services-manager-4.3.0/package/yast2-services-manager.changes
--- old/yast2-services-manager-4.2.5/package/yast2-services-manager.changes     
2019-09-09 11:07:40.000000000 +0200
+++ new/yast2-services-manager-4.3.0/package/yast2-services-manager.changes     
2020-05-12 18:02:09.000000000 +0200
@@ -1,4 +1,11 @@
 -------------------------------------------------------------------
+Tue May 12 15:32:28 UTC 2020 - josef Reidinger <jreidinger@localhost>
+
+- Autoyast schema: Allow optional types for string and map objects
+  (bsc#1170886)
+- 4.3.0
+
+-------------------------------------------------------------------
 Fri Sep  6 14:28:55 CEST 2019 - [email protected]
 
 - Set BaseTargets::GRAPHICAL and Target::GRAPHICAL if package "xdm"
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' 
old/yast2-services-manager-4.2.5/package/yast2-services-manager.spec 
new/yast2-services-manager-4.3.0/package/yast2-services-manager.spec
--- old/yast2-services-manager-4.2.5/package/yast2-services-manager.spec        
2019-09-09 11:07:40.000000000 +0200
+++ new/yast2-services-manager-4.3.0/package/yast2-services-manager.spec        
2020-05-12 18:02:09.000000000 +0200
@@ -24,7 +24,7 @@
 ######################################################################
 
 Name:           yast2-services-manager
-Version:        4.2.5
+Version:        4.3.0
 Release:        0
 Summary:        YaST2 - Services Manager
 Group:          System/YaST
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' 
old/yast2-services-manager-4.2.5/src/autoyast-rnc/services-manager.rnc 
new/yast2-services-manager-4.3.0/src/autoyast-rnc/services-manager.rnc
--- old/yast2-services-manager-4.2.5/src/autoyast-rnc/services-manager.rnc      
1970-01-01 01:00:00.000000000 +0100
+++ new/yast2-services-manager-4.3.0/src/autoyast-rnc/services-manager.rnc      
2020-05-12 18:02:09.000000000 +0200
@@ -0,0 +1,81 @@
+default namespace = "http://www.suse.com/1.0/yast2ns";
+namespace a = "http://relaxng.org/ns/compatibility/annotations/1.0";
+namespace config = "http://www.suse.com/1.0/configns";
+
+include "common.rnc"
+
+# runlevel legacy schema
+
+runlevel_service_name   = element service_name   { STRING }
+runlevel_service_status = element service_status { STRING }
+runlevel_service_start  = element service_start  { STRING }
+runlevel_service_stop   = element service_stop   { STRING }
+
+runlevel_service =
+  element service {
+     attribute config:type { text }?   &
+       runlevel_service_name?          &
+       runlevel_service_start?         &
+       runlevel_service_stop?          &
+       runlevel_service_status?
+  }
+
+runlevel_services =
+  element services {
+    attribute config:type { "list" }?,
+    runlevel_service*
+  }
+
+runlevel_default = element \default { STRING }
+
+runlevel_content = element runlevel { MAP, (runlevel_default? & 
runlevel_services?) }
+
+# current services-manager schema
+
+# by default, AutoYast exports list entries as 'listentry'
+service = element service { STRING } | element listentry { STRING }
+
+sm_enable =
+  element enable {
+    LIST,
+    service*
+  }
+
+sm_disable =
+  element disable {
+    LIST,
+    service*
+  }
+
+sm_on_demand =
+  element on_demand {
+    LIST,
+    service*
+  }
+
+new_services_list =
+  element services {
+    MAP,
+    (
+      sm_disable? &
+      sm_enable? &
+      sm_on_demand?
+    )
+  }
+
+old_services_list =
+  element services {
+    LIST,
+    service*
+  }
+
+services =
+  old_services_list | new_services_list
+
+default_target = element default_target { STRING }
+
+services_manager_content = default_target? & services?
+
+services-manager =
+  element services-manager { MAP, services_manager_content } |
+  element runlevel         { MAP, runlevel_content         }
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' 
old/yast2-services-manager-4.2.5/src/autoyast_rnc/services-manager.rnc 
new/yast2-services-manager-4.3.0/src/autoyast_rnc/services-manager.rnc
--- old/yast2-services-manager-4.2.5/src/autoyast_rnc/services-manager.rnc      
2019-09-09 11:07:40.000000000 +0200
+++ new/yast2-services-manager-4.3.0/src/autoyast_rnc/services-manager.rnc      
1970-01-01 01:00:00.000000000 +0100
@@ -1,76 +0,0 @@
-default namespace = "http://www.suse.com/1.0/yast2ns";
-namespace a = "http://relaxng.org/ns/compatibility/annotations/1.0";
-namespace config = "http://www.suse.com/1.0/configns";
-
-# runlevel legacy schema
-
-runlevel_service_name   = element service_name   { text }
-runlevel_service_status = element service_status { text }
-runlevel_service_start  = element service_start  { text }
-runlevel_service_stop   = element service_stop   { text }
-
-runlevel_service =
-  element service {
-     attribute config:type { text }?   &
-       runlevel_service_name?          &
-       runlevel_service_start?         &
-       runlevel_service_stop?          &
-       runlevel_service_status?
-  }
-
-runlevel_services =
-  element services {
-    attribute config:type { "list" }?,
-    runlevel_service*
-  }
-
-runlevel_default = element \default { text }
-
-runlevel_content = element runlevel { runlevel_default? & runlevel_services? }
-
-# current services-manager schema
-
-# by default, AutoYast exports list entries as 'listentry'
-service = element service { text } | element listentry { text }
-
-sm_enable =
-  element enable {
-    LIST,
-    service*
-  }
-
-sm_disable =
-  element disable {
-    LIST,
-    service*
-  }
-
-sm_on_demand =
-  element on_demand {
-    LIST,
-    service*
-  }
-
-new_services_list =
-  element services {
-    sm_disable? &
-    sm_enable? &
-    sm_on_demand?
-  }
-
-old_services_list =
-  element services {
-    LIST,
-    service*
-  }
-
-services =
-  old_services_list | new_services_list
-
-default_target = element default_target { text }
-
-services_manager_content = default_target? & services?
-
-services-manager =
-  element services-manager { services_manager_content } |
-  element runlevel         { runlevel_content         }


Reply via email to