[Bug 222127] Upgrade devel/py-defusedxml to version 0.5.0
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Thu Sep 7 18:02:42 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222127
Bug ID: 222127
Summary: Upgrade devel/py-defusedxml to version 0.5.0
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: wg at FreeBSD.org
Reporter: pete at nomadlogic.org
Assignee: wg at FreeBSD.org
Flags: maintainer-feedback?(wg at FreeBSD.org)
I am testing out the net/s3ql port and noticed that when I try to run mkfs.s3ql
the following exception is thrown:
AttributeError: module 'xml.etree.ElementTree' has no attribute
'_IterParseIterator'
After doing some digging I came across this issue with the defusedxml project:
https://github.com/tiran/defusedxml/issues/3
It seems there was a bug in regards to python36 that was fixed in v0.5.0.
Locally I bumped the version of py-defusedxml to 0.5.0, rebuilt s3ql an it now
works as expected.
The following diff against the master branch on my end works:
diff --git a/devel/py-defusedxml/Makefile b/devel/py-defusedxml/Makefile
index 787b1fbc0955..2879299c774b 100644
--- a/devel/py-defusedxml/Makefile
+++ b/devel/py-defusedxml/Makefile
@@ -2,7 +2,7 @@
# $FreeBSD$
PORTNAME= defusedxml
-PORTVERSION= 0.4.1
+PORTVERSION= 0.5.0
CATEGORIES= devel python textproc
MASTER_SITES= CHEESESHOP
PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX}
diff --git a/devel/py-defusedxml/distinfo b/devel/py-defusedxml/distinfo
index 92fbd39d668b..01daac7b11e3 100644
--- a/devel/py-defusedxml/distinfo
+++ b/devel/py-defusedxml/distinfo
@@ -1,2 +1,3 @@
-SHA256 (defusedxml-0.4.1.tar.gz) =
cd551d5a518b745407635bb85116eb813818ecaf182e773c35b36239fc3f2478
-SIZE (defusedxml-0.4.1.tar.gz) = 48889
+TIMESTAMP = 1504807319
+SHA256 (defusedxml-0.5.0.tar.gz) =
24d7f2f94f7f3cb6061acb215685e5125fbcdc40a857eff9de22518820b0a4f4
+SIZE (defusedxml-0.5.0.tar.gz) = 60405
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list