Hello community,

here is the log from the commit of package python-strict-rfc3339 for 
openSUSE:Factory checked in at 2019-04-04 12:00:42
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-strict-rfc3339 (Old)
 and      /work/SRC/openSUSE:Factory/.python-strict-rfc3339.new.3908 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python-strict-rfc3339"

Thu Apr  4 12:00:42 2019 rev:2 rq:690288 version:0.7

Changes:
--------
--- 
/work/SRC/openSUSE:Factory/python-strict-rfc3339/python-strict-rfc3339.changes  
    2019-03-29 20:34:53.946614874 +0100
+++ 
/work/SRC/openSUSE:Factory/.python-strict-rfc3339.new.3908/python-strict-rfc3339.changes
    2019-04-04 12:00:46.417283583 +0200
@@ -1,0 +2,5 @@
+Thu Mar 14 16:32:12 UTC 2019 - Jan Engelhardt <jeng...@inai.de>
+
+- Trim bias from descriptions.
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ python-strict-rfc3339.spec ++++++
--- /var/tmp/diff_new_pack.XVLFjU/_old  2019-04-04 12:00:47.441284403 +0200
+++ /var/tmp/diff_new_pack.XVLFjU/_new  2019-04-04 12:00:47.441284403 +0200
@@ -20,7 +20,7 @@
 Name:           python-strict-rfc3339
 Version:        0.7
 Release:        0
-Summary:        Strict, simple, lightweight RFC3339 functions
+Summary:        RFC 3339 functions
 License:        GPL-3.0-only
 Group:          Development/Languages/Python
 Url:            http://www.danielrichman.co.uk/libraries/strict-rfc3339.html
@@ -33,11 +33,10 @@
 %python_subpackages
 
 %description
-Strict, simple, lightweight RFC3339 functions
+RFC 3339 functions.
  - Convert unix timestamps to and from RFC3339.
  - Either produce RFC3339 strings with a UTC offset (Z) or with the offset
    that the C time module reports is the local timezone offset.
- - Simple with minimal dependencies/libraries.
  - Avoid timezones as much as possible.
  - Be very strict and follow RFC3339.
 


Reply via email to