Hello community,

here is the log from the commit of package python-troveclient for 
openSUSE:Factory checked in at 2014-08-14 14:57:53
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-troveclient (Old)
 and      /work/SRC/openSUSE:Factory/.python-troveclient.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python-troveclient"

Changes:
--------
--- /work/SRC/openSUSE:Factory/python-troveclient/python-troveclient.changes    
2014-04-08 12:46:32.000000000 +0200
+++ 
/work/SRC/openSUSE:Factory/.python-troveclient.new/python-troveclient.changes   
    2014-08-14 14:58:00.000000000 +0200
@@ -1,0 +2,6 @@
+Thu Jul 31 17:01:12 UTC 2014 - [email protected]
+
+- Rename rpmlintrc to %{name}-rpmlintrc.
+  Follow the packaging guidelines.
+
+-------------------------------------------------------------------

Old:
----
  rpmlintrc

New:
----
  python-troveclient-rpmlintrc

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

Other differences:
------------------
++++++ python-troveclient.spec ++++++
--- /var/tmp/diff_new_pack.R2bE0A/_old  2014-08-14 14:58:01.000000000 +0200
+++ /var/tmp/diff_new_pack.R2bE0A/_new  2014-08-14 14:58:01.000000000 +0200
@@ -26,6 +26,7 @@
 Group:          Development/Languages/Python
 Url:            http://launchpad.net/python-troveclient
 Source:         
http://tarballs.openstack.org/python-troveclient/python-troveclient-%{version}.tar.gz
+Source1:        python-troveclient-rpmlintrc
 BuildRequires:  openstack-suse-macros
 BuildRequires:  python-pbr >= 0.5.21
 # Documentation requirements:

++++++ python-troveclient-rpmlintrc ++++++
# This symling is for the -test package and can be ignored:
addFilter("dangling-symlink /var/lib/python-swiftclient-test/swiftclient")
# This file is ok, it's for the unit testsuite
addFilter("hidden-file-or-dir /var/lib/python-swiftclient-test/.unittests")
-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to