Hello community,
here is the log from the commit of package update-test-trival for
openSUSE:Factory checked in at 2014-08-27 10:57:29
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/update-test-trival (Old)
and /work/SRC/openSUSE:Factory/.update-test-trival.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "update-test-trival"
Changes:
--------
--- /work/SRC/openSUSE:Factory/update-test-trival/update-test-trival.changes
2011-09-23 12:49:31.000000000 +0200
+++
/work/SRC/openSUSE:Factory/.update-test-trival.new/update-test-trival.changes
2014-08-27 10:57:29.000000000 +0200
@@ -1,0 +2,6 @@
+Thu Aug 21 16:27:09 CEST 2014 - [email protected]
+
+- improve description of packages and fix content of README files
+- some minor fixes and clean-ups in the spec file
+
+-------------------------------------------------------------------
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ update-test-trival.spec ++++++
--- /var/tmp/diff_new_pack.f3ySGZ/_old 2014-08-27 10:57:30.000000000 +0200
+++ /var/tmp/diff_new_pack.f3ySGZ/_new 2014-08-27 10:57:30.000000000 +0200
@@ -1,7 +1,7 @@
#
-# spec file for package update-test-trival (Version 0)
+# spec file for package update-test-trival
#
-# Copyright (c) 2010 SUSE LINUX Products GmbH, Nuernberg, Germany.
+# Copyright (c) 2014 SUSE LINUX Products GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
@@ -15,18 +15,15 @@
# Please submit bugfixes or comments via http://bugs.opensuse.org/
#
-# norootforbuild
-
Name: update-test-trival
Version: 0
-Release: 3
-Summary: Package for testing the update stack during product
development.
+Release: 0
+Summary: Package for testing the update stack during product development
License: GPL-2.0+
+Group: System/YaST
BuildArch: noarch
-AutoReqProv: on
Source0: %{name}.tar.bz2
-Group: System/YaST
BuildRoot: %{_tmppath}/%{name}-%{version}-build
%description
@@ -35,162 +32,103 @@
We will provide a "always" working update for this package so that the
update stack could be easily tested.
-
-
-Authors:
---------
- Harald M�ller-Ney <[email protected]>
-
%package -n update-test-reboot-needed
-License: GPL-2.0+
-Summary: Package for testing the update stack during product
development.
+Summary: Test update that requires a system reboot
Group: System/YaST
%description -n update-test-reboot-needed
Package for testing the update stack during product development.
-We will provide a "always" working update for this package so that the
-update stack could be easily tested.
-
-
-
-Authors:
---------
- Harald M�ller-Ney <[email protected]>
+An update for this package should inform the user that a system
+reboot is necessary. This is used, for example, in kernel updates.
%package -n update-test-relogin-suggested
-License: GPL-2.0+
-Summary: Package for testing the update stack during product
development.
+Summary: Test update that requires a session restart
Group: System/YaST
%description -n update-test-relogin-suggested
Package for testing the update stack during product development.
-We will provide a "always" working update for this package so that the
-update stack could be easily tested.
-
-
-
-Authors:
---------
- Harald M�ller-Ney <[email protected]>
+An update for this package should inform the user that a session
+restart (re-login) is necessary. This is used, for example, in
+window manager updates.
%package -n update-test-interactive
-License: GPL-2.0+
-Summary: Package for testing the update stack during product
development.
+Summary: Test update that requires confirmation
Group: System/YaST
%description -n update-test-interactive
Package for testing the update stack during product development.
-We will provide a "always" working update for this package so that the
-update stack could be easily tested.
-
-
-
-Authors:
---------
- Harald M�ller-Ney <[email protected]>
+An update for this package should show a message to the user
+and wait for confirmation before proceeding. This is used, for
+example, in package updates that include proprietary licenses.
%package -n update-test-affects-package-manager
-License: GPL-2.0+
-Summary: Package for testing the update stack during product
development.
+Summary: Test update that requires a software stack restart
Group: System/YaST
%description -n update-test-affects-package-manager
Package for testing the update stack during product development.
-We will provide a "always" working update for this package so that the
-update stack could be easily tested.
-
-
-
-Authors:
---------
- Harald M�ller-Ney <[email protected]>
+An update for this package should be installed first by the
+update stack and then ask the user to run the update process
+again to apply other updates that might be available. This is
+used, for example, to update packages from the software update
+stack (zypper, libzypp, packagekit, etc).
%package -n update-test-security
-License: GPL-2.0+
-Summary: Package for testing the update stack during product
development.
+Summary: Test update that includes security fixes
Group: System/YaST
%description -n update-test-security
Package for testing the update stack during product development.
-We will provide a "always" working update for this package so that the
-update stack could be easily tested.
-
-
-
-Authors:
---------
- Harald M�ller-Ney <[email protected]>
+An update for this package should have its category set to
+"security", indicating that one or more security vulnerabilities
+are being fixed.
%package -n update-test-feature
-License: GPL-2.0+
-Summary: Package for testing the update stack during product
development.
+Summary: Test update that includes new features
Group: System/YaST
%description -n update-test-feature
Package for testing the update stack during product development.
-We will provide a "always" working update for this package so that the
-update stack could be easily tested.
-
-
-
-Authors:
---------
- Harald M�ller-Ney <[email protected]>
-
+An update for this package should have its category set to
+"feature", indicating that it includes a new feature and not
+only fixes.
%package -n update-test-optional
-License: GPL-2.0+
-Summary: Package for testing the update stack during product
development.
+Summary: Test update that is not mandatory
Group: System/YaST
%description -n update-test-optional
Package for testing the update stack during product development.
-We will provide a "always" working update for this package so that the
-update stack could be easily tested.
-
-
-
-Authors:
---------
- Harald M�ller-Ney <[email protected]>
+An update for this package should have its category set to
+"optional". The software stack should not select such updates
+for installation by default. This is used, for example, to add
+new packages to a product.
%prep
%setup -q -n %{name}
%build
-echo "%{name}-%{version}-${release}" > VERSION
-echo -n "Build at: " >> VERSION
+echo "Package: %{name}-%{version}-%{release}" > VERSION
+echo -n "Build date: " >> VERSION
LANG=POSIX date -u >> VERSION
-
-%install
-# skip-check-libtool-deps
-for i in update-test-reboot-needed update-test-interactive
update-test-affects-package-manager update-test-security update-test-optional
update-test-relogin-suggested update-test-feature; do
-cat > README.$i <<-EOF
-Package for testing the update stack during product development.
-This package should require a reboot of the machine.
-EOF
-done
-for i in `ls -A README.update-test*`; do
- echo >> $i
- echo "Package Version : %{version}" >> $i
- echo "Package Release : %{release}" >> $i
-# echo "Architecture : %{_target_cpu}" >> $i
- echo -n "Generated on : " >> $i
- date >> $i
- echo >> $i
- echo " Remember to have a lot of fun!" >> $i
+for readme in README.update-test*; do
+ echo "---" >> $readme
+ echo "Package Version : %{version}" >> $readme
+ echo "Package Release : %{release}" >> $readme
+ echo -n "Generated on : " >> $readme
+ date >> $readme
+ echo >> $readme
+ echo " Remember to have a lot of fun!" >> $readme
done
-echo "%{version}-%{release}" >> VERSION
-%clean
-rm -rf $RPM_BUILD_ROOT
+%install
%files
%defattr(-,root,root)
++++++ update-test-trival.tar.bz2 ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/update-test-trival/AUTHOR
new/update-test-trival/AUTHOR
--- old/update-test-trival/AUTHOR 2006-10-18 17:49:35.000000000 +0200
+++ new/update-test-trival/AUTHOR 2014-08-21 16:57:01.000000000 +0200
@@ -1,2 +1,2 @@
-This package is created by
- Harald Müller-Ney <[email protected]>
+This package was created by Harald Müller-Ney <[email protected]>
+and is maintained by the Maintenance Team <[email protected]>.
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/update-test-trival/README
new/update-test-trival/README
--- old/update-test-trival/README 2006-10-18 17:48:27.000000000 +0200
+++ new/update-test-trival/README 2014-08-21 16:54:53.000000000 +0200
@@ -1,7 +1,3 @@
-update-test-trivial
-
-Is a package for testing our update stack.
-It is used for testing the most trivial update scenario.
-
-The version-release of the package installed is:
+update-test-trival
+A package for testing the update stack during product development.
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/update-test-trival/README.update-test-affects-package-manager
new/update-test-trival/README.update-test-affects-package-manager
--- old/update-test-trival/README.update-test-affects-package-manager
1970-01-01 01:00:00.000000000 +0100
+++ new/update-test-trival/README.update-test-affects-package-manager
2014-08-21 16:22:02.000000000 +0200
@@ -0,0 +1,8 @@
+Package for testing the update stack during product development.
+
+An update for this package should be installed first by the
+update stack and then ask the user to run the update process
+again to apply other updates that might be available. This is
+used, for example, to update packages from the software update
+stack (zypper, libzypp, packagekit, etc).
+
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/update-test-trival/README.update-test-feature
new/update-test-trival/README.update-test-feature
--- old/update-test-trival/README.update-test-feature 1970-01-01
01:00:00.000000000 +0100
+++ new/update-test-trival/README.update-test-feature 2014-08-21
16:23:04.000000000 +0200
@@ -0,0 +1,6 @@
+Package for testing the update stack during product development.
+
+An update for this package should have its category set to
+"feature", indicating that it includes a new feature and not
+only fixes.
+
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/update-test-trival/README.update-test-interactive
new/update-test-trival/README.update-test-interactive
--- old/update-test-trival/README.update-test-interactive 1970-01-01
01:00:00.000000000 +0100
+++ new/update-test-trival/README.update-test-interactive 2014-08-21
16:21:49.000000000 +0200
@@ -0,0 +1,6 @@
+Package for testing the update stack during product development.
+
+An update for this package should show a message to the user
+and wait for confirmation before proceeding. This is used, for
+example, in package updates that include proprietary licenses.
+
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/update-test-trival/README.update-test-optional
new/update-test-trival/README.update-test-optional
--- old/update-test-trival/README.update-test-optional 1970-01-01
01:00:00.000000000 +0100
+++ new/update-test-trival/README.update-test-optional 2014-08-21
16:22:26.000000000 +0200
@@ -0,0 +1,7 @@
+Package for testing the update stack during product development.
+
+An update for this package should have its category set to
+"optional". The software stack should not select such updates
+for installation by default. This is used, for example, to add
+new packages to a product.
+
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/update-test-trival/README.update-test-reboot-needed
new/update-test-trival/README.update-test-reboot-needed
--- old/update-test-trival/README.update-test-reboot-needed 1970-01-01
01:00:00.000000000 +0100
+++ new/update-test-trival/README.update-test-reboot-needed 2014-08-21
16:21:35.000000000 +0200
@@ -0,0 +1,5 @@
+Package for testing the update stack during product development.
+
+An update for this package should inform the user that a system
+reboot is necessary. This is used, for example, in kernel updates.
+
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/update-test-trival/README.update-test-relogin-suggested
new/update-test-trival/README.update-test-relogin-suggested
--- old/update-test-trival/README.update-test-relogin-suggested 1970-01-01
01:00:00.000000000 +0100
+++ new/update-test-trival/README.update-test-relogin-suggested 2014-08-21
16:22:41.000000000 +0200
@@ -0,0 +1,6 @@
+Package for testing the update stack during product development.
+
+An update for this package should inform the user that a session
+restart (re-login) is necessary. This is used, for example, in
+window manager updates.
+
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/update-test-trival/README.update-test-security
new/update-test-trival/README.update-test-security
--- old/update-test-trival/README.update-test-security 1970-01-01
01:00:00.000000000 +0100
+++ new/update-test-trival/README.update-test-security 2014-08-21
16:22:16.000000000 +0200
@@ -0,0 +1,6 @@
+Package for testing the update stack during product development.
+
+An update for this package should have its category set to
+"security", indicating that one or more security vulnerabilities
+are being fixed.
+
--
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
