Hello community,

here is the log from the commit of package python-pyasn1 for openSUSE:Factory 
checked in at 2012-07-30 09:38:51
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-pyasn1 (Old)
 and      /work/SRC/openSUSE:Factory/.python-pyasn1.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python-pyasn1", Maintainer is "[email protected]"

Changes:
--------
--- /work/SRC/openSUSE:Factory/python-pyasn1/python-pyasn1.changes      
2012-05-03 11:00:08.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.python-pyasn1.new/python-pyasn1.changes 
2012-07-30 09:39:05.000000000 +0200
@@ -1,0 +2,16 @@
+Fri Jul 27 18:03:18 UTC 2012 - [email protected]
+
+- updated to upstrean release 0.1.4
+- includes fix needed by python-ldap's module ldap.syncrepl
+
+Most important changes include:
+
+* A built-in de/serialization debugging facility added
+* Package versioning added (pyasn1.__version__)
+* Leading sub-OIDs overflow condition handled
+* REAL type exponent encoding implemented properly at BER codec
+* Boolean BER decoder fixed to allow arbitrary payload
+* Leading 0x80 octet now handled properly by DER/CER/DER
+   ObjectIdentifier decoder
+
+-------------------------------------------------------------------

Old:
----
  pyasn1-0.1.3.tar.gz

New:
----
  pyasn1-0.1.4.tar.gz

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

Other differences:
------------------
++++++ python-pyasn1.spec ++++++
--- /var/tmp/diff_new_pack.0zevvC/_old  2012-07-30 09:39:06.000000000 +0200
+++ /var/tmp/diff_new_pack.0zevvC/_new  2012-07-30 09:39:06.000000000 +0200
@@ -17,7 +17,7 @@
 
 
 Name:           python-pyasn1
-Version:        0.1.3
+Version:        0.1.4
 Release:        0
 Summary:        ASN.1 types and codecs
 License:        BSD-3-Clause

++++++ pyasn1-0.1.3.tar.gz -> pyasn1-0.1.4.tar.gz ++++++
++++ 4005 lines of diff (skipped)

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

Reply via email to