Hello community,

here is the log from the commit of package python-python-daemon for 
openSUSE:Factory checked in at 2012-02-17 15:01:12
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-python-daemon (Old)
 and      /work/SRC/openSUSE:Factory/.python-python-daemon.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python-python-daemon", Maintainer is ""

Changes:
--------
--- 
/work/SRC/openSUSE:Factory/python-python-daemon/python-python-daemon.changes    
    2011-11-25 23:05:49.000000000 +0100
+++ 
/work/SRC/openSUSE:Factory/.python-python-daemon.new/python-python-daemon.changes
   2012-02-17 15:01:14.000000000 +0100
@@ -1,0 +2,7 @@
+Thu Jan  5 13:25:37 UTC 2012 - [email protected]
+
+- reverted to 1.5.5 (per bnc#731071 and Debian bug #585404,
+  upstream has retracted version 1.6 due to brokenness)
+- updated license header
+
+-------------------------------------------------------------------

Old:
----
  python-daemon-1.6.tar.bz2

New:
----
  python-daemon-1.5.5.tar.bz2

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

Other differences:
------------------
++++++ python-python-daemon.spec ++++++
--- /var/tmp/diff_new_pack.IWc7vA/_old  2012-02-17 15:01:15.000000000 +0100
+++ /var/tmp/diff_new_pack.IWc7vA/_new  2012-02-17 15:01:15.000000000 +0100
@@ -18,11 +18,11 @@
 
 
 Name:           python-python-daemon
-Version:        1.6
+Version:        1.5.5
 Release:        0
 Url:            http://pypi.python.org/pypi/python-daemon/
 Summary:        Library to implement a well-behaved Unix daemon process
-License:        PSF-2+
+License:        Python-2.0
 Group:          Development/Languages/Python
 Source:         python-daemon-%{version}.tar.bz2
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build

++++++ python-daemon-1.6.tar.bz2 -> python-daemon-1.5.5.tar.bz2 ++++++
++++ 3615 lines of diff (skipped)

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to