Hello community, here is the log from the commit of package yast2-proxy for openSUSE:Factory checked in at 2020-05-15 23:50:16 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/yast2-proxy (Old) and /work/SRC/openSUSE:Factory/.yast2-proxy.new.2738 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "yast2-proxy" Fri May 15 23:50:16 2020 rev:20 rq:803054 version:4.3.0 Changes: -------- --- /work/SRC/openSUSE:Factory/yast2-proxy/yast2-proxy.changes 2019-08-27 10:13:52.055969614 +0200 +++ /work/SRC/openSUSE:Factory/.yast2-proxy.new.2738/yast2-proxy.changes 2020-05-15 23:50:18.701312331 +0200 @@ -1,0 +2,7 @@ +Tue May 12 14:38:07 UTC 2020 - josef Reidinger <jreidinger@localhost> + +- Autoyast schema: Allow optional types for string and map objects + (bsc#1170886) +- 4.3.0 + +------------------------------------------------------------------- Old: ---- yast2-proxy-4.2.2.tar.bz2 New: ---- yast2-proxy-4.3.0.tar.bz2 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ yast2-proxy.spec ++++++ --- /var/tmp/diff_new_pack.BukuYn/_old 2020-05-15 23:50:19.485313841 +0200 +++ /var/tmp/diff_new_pack.BukuYn/_new 2020-05-15 23:50:19.485313841 +0200 @@ -1,7 +1,7 @@ # # spec file for package yast2-proxy # -# 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 @@ -17,7 +17,7 @@ Name: yast2-proxy -Version: 4.2.2 +Version: 4.3.0 Release: 0 Summary: YaST2 - Proxy Configuration License: GPL-2.0-or-later ++++++ yast2-proxy-4.2.2.tar.bz2 -> yast2-proxy-4.3.0.tar.bz2 ++++++ diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/yast2-proxy-4.2.2/CONTRIBUTING.md new/yast2-proxy-4.3.0/CONTRIBUTING.md --- old/yast2-proxy-4.2.2/CONTRIBUTING.md 2019-08-22 15:03:06.000000000 +0200 +++ new/yast2-proxy-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-proxy-4.2.2/package/yast2-proxy.changes new/yast2-proxy-4.3.0/package/yast2-proxy.changes --- old/yast2-proxy-4.2.2/package/yast2-proxy.changes 2019-08-22 15:03:06.000000000 +0200 +++ new/yast2-proxy-4.3.0/package/yast2-proxy.changes 2020-05-12 16:52:14.000000000 +0200 @@ -1,4 +1,11 @@ ------------------------------------------------------------------- +Tue May 12 14:38:07 UTC 2020 - josef Reidinger <jreidinger@localhost> + +- Autoyast schema: Allow optional types for string and map objects + (bsc#1170886) +- 4.3.0 + +------------------------------------------------------------------- Thu Aug 22 12:53:15 CEST 2019 - sch...@suse.de - Using rb_default_ruby_abi tag in the spec file in order to diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/yast2-proxy-4.2.2/package/yast2-proxy.spec new/yast2-proxy-4.3.0/package/yast2-proxy.spec --- old/yast2-proxy-4.2.2/package/yast2-proxy.spec 2019-08-22 15:03:06.000000000 +0200 +++ new/yast2-proxy-4.3.0/package/yast2-proxy.spec 2020-05-12 16:52:14.000000000 +0200 @@ -17,7 +17,7 @@ Name: yast2-proxy -Version: 4.2.2 +Version: 4.3.0 Release: 0 Summary: YaST2 - Proxy Configuration License: GPL-2.0-or-later diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/yast2-proxy-4.2.2/src/autoyast-rnc/proxy.rnc new/yast2-proxy-4.3.0/src/autoyast-rnc/proxy.rnc --- old/yast2-proxy-4.2.2/src/autoyast-rnc/proxy.rnc 2019-08-22 15:03:06.000000000 +0200 +++ new/yast2-proxy-4.3.0/src/autoyast-rnc/proxy.rnc 2020-05-12 16:52:14.000000000 +0200 @@ -2,12 +2,17 @@ namespace a = "http://relaxng.org/ns/compatibility/annotations/1.0"; namespace config = "http://www.suse.com/1.0/configns"; +include "common.rnc" + proxy = element proxy { + MAP, + ( element enabled { BOOLEAN }? & - element ftp_proxy { text }? & - element http_proxy { text }? & - element https_proxy { text }? & - element no_proxy { text }? & - element proxy_password { text }? & - element proxy_user { text }? + element ftp_proxy { STRING }? & + element http_proxy { STRING }? & + element https_proxy { STRING }? & + element no_proxy { STRING }? & + element proxy_password { STRING }? & + element proxy_user { STRING }? + ) }
