Hello community,
here is the log from the commit of package yast2-installation-control for
openSUSE:Factory checked in at 2016-11-03 12:55:40
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/yast2-installation-control (Old)
and /work/SRC/openSUSE:Factory/.yast2-installation-control.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "yast2-installation-control"
Changes:
--------
---
/work/SRC/openSUSE:Factory/yast2-installation-control/yast2-installation-control.changes
2016-03-20 11:47:27.000000000 +0100
+++
/work/SRC/openSUSE:Factory/.yast2-installation-control.new/yast2-installation-control.changes
2016-11-03 12:55:41.000000000 +0100
@@ -1,0 +2,12 @@
+Mon Oct 31 09:41:57 UTC 2016 - [email protected]
+
+- Added support for read-only proposal modules (fate#321739)
+- 3.2.0
+
+-------------------------------------------------------------------
+Thu Oct 27 14:51:19 CEST 2016 - [email protected]
+
+- Make subvolumes configurable in control.xml (fate#321737)
+- 3.1.13.1
+
+-------------------------------------------------------------------
Old:
----
yast2-installation-control-3.1.13.tar.bz2
New:
----
yast2-installation-control-3.2.0.tar.bz2
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ yast2-installation-control.spec ++++++
--- /var/tmp/diff_new_pack.BPCAw4/_old 2016-11-03 12:55:42.000000000 +0100
+++ /var/tmp/diff_new_pack.BPCAw4/_new 2016-11-03 12:55:42.000000000 +0100
@@ -17,7 +17,7 @@
Name: yast2-installation-control
-Version: 3.1.13
+Version: 3.2.0
Release: 0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++++++ yast2-installation-control-3.1.13.tar.bz2 ->
yast2-installation-control-3.2.0.tar.bz2 ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-installation-control-3.1.13/CONTRIBUTING.md
new/yast2-installation-control-3.2.0/CONTRIBUTING.md
--- old/yast2-installation-control-3.1.13/CONTRIBUTING.md 2016-03-14
15:29:19.000000000 +0100
+++ new/yast2-installation-control-3.2.0/CONTRIBUTING.md 2016-11-01
15:51:50.000000000 +0100
@@ -3,7 +3,7 @@
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.
+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.
@@ -17,13 +17,11 @@
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.suse.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).
+We can't guarantee that every bug will be fixed, but we'll try.
+
Code Changes
------------
@@ -44,15 +42,22 @@
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
+ 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.
- 5. Publish the branch and create a pull request.
+ 6. Publish the branch and create a pull request.
- 6. YaST developers will review your change and possibly point out issues.
+ 7. 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.
+ 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).
@@ -60,9 +65,6 @@
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
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/yast2-installation-control-3.1.13/control/control.rnc
new/yast2-installation-control-3.2.0/control/control.rnc
--- old/yast2-installation-control-3.1.13/control/control.rnc 2016-03-14
15:29:19.000000000 +0100
+++ new/yast2-installation-control-3.2.0/control/control.rnc 2016-11-01
15:51:50.000000000 +0100
@@ -444,6 +444,7 @@
| partitions
| btrfs_increase_percentage
| btrfs_default_subvolume
+ | subvolumes
try_separate_home = element try_separate_home { BOOLEAN }
limit_try_home = element limit_try_home { text }
@@ -461,6 +462,28 @@
btrfs_increase_percentage = element btrfs_increase_percentage { INTEGER }
btrfs_default_subvolume = element btrfs_default_subvolume { text }
+## Optional, but if this element appears (even if it's empty),
+## the internal fallback list is not used
+subvolumes = element subvolumes {
+ LIST,
+ subvolume*
+}?
+
+subvolume = element subvolume {
+ ## subvolume path without leading /
+ element path { text } &
+
+ ## Optional: COW; default: true
+ element copy_on_write { BOOLEAN }? &
+
+ ## Optional: comma-separated architectures (default: all)
+ ## Prepend ! to negate
+ ## Example 1: i386,x86_64
+ ## Example 2: ppc,!board_powernv
+ ## (i.e. on PPC, but not if it's a board_powernv machine
+ element archs { text }?
+}
+
# these have to be defined by Storage
partitions = element partitions {
LIST,
@@ -558,6 +581,9 @@
## Presentation order in the current proposal (integer).
## Lower numbers first.
element presentation_order { text }? &
+ ## Read only flag - if true the proposal cannot be changed (clicked) by
user,
+ ## the default is false
+ element read_only { BOOLEAN }? &
## Inexplicit proposal name if not explicitely defined by 'name' and
'presentation_order'
text?
}
@@ -569,7 +595,7 @@
proposal = element proposal {
## Unique ID of the proposal
element unique_id { text } &
- ##
+ ##
element label { text }? &
## Defines for which architectures is this proposal used.
## Comma-separated list of architectures as seen in
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/yast2-installation-control-3.1.13/control/control.rng
new/yast2-installation-control-3.2.0/control/control.rng
--- old/yast2-installation-control-3.1.13/control/control.rng 2016-03-14
15:29:19.000000000 +0100
+++ new/yast2-installation-control-3.2.0/control/control.rng 2016-11-01
15:51:50.000000000 +0100
@@ -887,6 +887,7 @@
<ref name="partitions"/>
<ref name="btrfs_increase_percentage"/>
<ref name="btrfs_default_subvolume"/>
+ <ref name="subvolumes"/>
</choice>
</define>
<define name="try_separate_home">
@@ -960,6 +961,44 @@
<text/>
</element>
</define>
+ <define name="subvolumes">
+ <a:documentation>Optional, but if this element appears (even if it's
empty),
+the internal fallback list is not used</a:documentation>
+ <optional>
+ <element name="subvolumes">
+ <ref name="LIST"/>
+ <zeroOrMore>
+ <ref name="subvolume"/>
+ </zeroOrMore>
+ </element>
+ </optional>
+ </define>
+ <define name="subvolume">
+ <element name="subvolume">
+ <interleave>
+ <element name="path">
+ <a:documentation>subvolume path without leading /</a:documentation>
+ <text/>
+ </element>
+ <optional>
+ <element name="copy_on_write">
+ <a:documentation>Optional: COW; default: true</a:documentation>
+ <ref name="BOOLEAN"/>
+ </element>
+ </optional>
+ <optional>
+ <element name="archs">
+ <a:documentation>Optional: comma-separated architectures (default:
all)
+Prepend ! to negate
+Example 1: i386,x86_64
+Example 2: ppc,!board_powernv
+(i.e. on PPC, but not if it's a board_powernv machine</a:documentation>
+ <text/>
+ </element>
+ </optional>
+ </interleave>
+ </element>
+ </define>
<!-- these have to be defined by Storage -->
<define name="partitions">
<element name="partitions">
@@ -1116,6 +1155,13 @@
</element>
</optional>
<optional>
+ <element name="read_only">
+ <a:documentation>Read only flag - if true the proposal cannot be
changed (clicked) by user,
+the default is false</a:documentation>
+ <ref name="BOOLEAN"/>
+ </element>
+ </optional>
+ <optional>
<text>
<a:documentation>Inexplicit proposal name if not explicitely
defined by 'name' and 'presentation_order'</a:documentation>
</text>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/yast2-installation-control-3.1.13/package/yast2-installation-control.changes
new/yast2-installation-control-3.2.0/package/yast2-installation-control.changes
---
old/yast2-installation-control-3.1.13/package/yast2-installation-control.changes
2016-03-14 15:29:19.000000000 +0100
+++
new/yast2-installation-control-3.2.0/package/yast2-installation-control.changes
2016-11-01 15:51:50.000000000 +0100
@@ -1,4 +1,16 @@
-------------------------------------------------------------------
+Mon Oct 31 09:41:57 UTC 2016 - [email protected]
+
+- Added support for read-only proposal modules (fate#321739)
+- 3.2.0
+
+-------------------------------------------------------------------
+Thu Oct 27 14:51:19 CEST 2016 - [email protected]
+
+- Make subvolumes configurable in control.xml (fate#321737)
+- 3.1.13.1
+
+-------------------------------------------------------------------
Mon Mar 14 12:18:49 UTC 2016 - [email protected]
- Added self_update_url (FATE#319716)
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/yast2-installation-control-3.1.13/package/yast2-installation-control.spec
new/yast2-installation-control-3.2.0/package/yast2-installation-control.spec
---
old/yast2-installation-control-3.1.13/package/yast2-installation-control.spec
2016-03-14 15:29:19.000000000 +0100
+++
new/yast2-installation-control-3.2.0/package/yast2-installation-control.spec
2016-11-01 15:51:50.000000000 +0100
@@ -17,7 +17,7 @@
Name: yast2-installation-control
-Version: 3.1.13
+Version: 3.2.0
Release: 0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
