Search Criteria
Package Details: python2-lxml 4.9.4-3
Package Actions
Git Clone URL: | https://aur.archlinux.org/python2-lxml.git (read-only, click to copy) |
---|---|
Package Base: | python2-lxml |
Description: | Python2 binding for the libxml2 and libxslt libraries |
Upstream URL: | https://lxml.de/ |
Licenses: | custom, BSD |
Submitter: | patlefort |
Maintainer: | patlefort |
Last Packager: | patlefort |
Votes: | 10 |
Popularity: | 0.016701 |
First Submitted: | 2021-06-22 01:52 (UTC) |
Last Updated: | 2024-06-16 13:11 (UTC) |
Dependencies (9)
- libxml2-2.9AUR
- libxslt (libxslt-gitAUR)
- python2AUR (python2-binAUR)
- cython2AUR (make)
- python2-setuptoolsAUR (make)
- python2-cssselectAUR (check)
- python2-beautifulsoup4 (optional) – malformed HTML parsing support
- python2-cssselectAUR (optional) – CSS parsing support
- python2-html5libAUR (optional) – HTML5 parsing support
Required by (2)
- keyboardlayouteditor-git
- python2-html5lib (optional)
Latest Comments
1 2 3 4 5 Next › Last »
patlefort commented on 2024-03-31 01:03 (UTC)
I've added the additional arguments and now depend on libxml2-2.9. It build fine and tests run fine. Let's see if
libxml2-2.9
soname problem will be fixed.PreparationH67 commented on 2024-03-30 18:09 (UTC)
Build does complete when using @isl 's suggestion to use patchelf to fix the libxml2-2.9 SONAME and then update the build options in the PKGBUILD file. This does seem like the best way to get a clean build right now. It does seem that this other package should patch the SONAME issue so building against it is easy and IIRC that is the correct way to configure and use such a package.
jester commented on 2024-03-03 13:04 (UTC)
@cmsigler I have got the same error than you
patlefort commented on 2024-02-08 18:36 (UTC)
For now you can still build and install it if the failed use case doesn't affect you since it is only some tests failing. Unfortunately python 2 is no longer supported upstream and this is the last version I am able to compile so it's up to us to try and fix it.
cmsigler commented on 2024-02-08 14:18 (UTC)
Hi,
This pkg isn't crucial for my use. But like others have seen, it hasn't been able to build for me in a long time.
FYI, I tried building in a clean chroot this morning with no success. There's only one check error, so it's somewhat puzzling to me that upstream doesn't grok this problem and fix it(?). I see:
====================================================================== ERROR: test_html_prefix_nsmap (lxml.tests.test_etree.ETreeOnlyTestCase)
Traceback (most recent call last): File "/usr/lib/python2.7/unittest/case.py", line 329, in run testMethod() File "/build/python2-lxml/src/lxml-lxml-4.9.4/src/lxml/tests/test_etree.py", line 3128, in test_html_prefix_nsmap self.assertEqual({}, el.nsmap) AttributeError: 'NoneType' object has no attribute 'nsmap'
====================================================================== FAIL: test_illegal_utf8_recover (lxml.tests.test_unicode.EncodingsTestCase)
Traceback (most recent call last): File "/usr/lib/python2.7/unittest/case.py", line 329, in run testMethod() File "/build/python2-lxml/src/lxml-lxml-4.9.4/src/lxml/tests/test_unicode.py", line 172, in test_illegal_utf8_recover self.assertEqual('\ufffd\ufffd\ufffd', tree.text) File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual raise self.failureException(msg) AssertionError: '\ufffd\ufffd\ufffd' != u'\ufffd\ufffd\ufffd'
Thank you for working on this AUR pkg :)
Clemmitt Sigler
bkb commented on 2023-08-10 13:43 (UTC)
Make
aur/python2-lxml-bin
vagelis commented on 2023-07-16 13:29 (UTC)
Don't care as it's used by 1 program only which I use rarely. If it crashes I'll check on it then
is1 commented on 2023-07-16 13:21 (UTC)
@vagelis This will result in runtime crashes when the problematic function is called by user programs, just as in the test run.
vagelis commented on 2023-07-16 13:05 (UTC)
@is1 my workaround was to comment out the test.py in PKGBUILD and installation completed successfully.
is1 commented on 2023-07-16 13:03 (UTC)
@vagelis @patlefort For me it builds fine if
libxml2
version 2.11 isn’t installed alongsidelibxml2-2.9
, without any failing tests. Then/usr/lib/libxml2.so.2
points to/usr/lib/libxml2-2.9/libxml2.so.2.9.10
instead of the new library version. This was my configuration which may not work for other users and I’m sorry for the confusion this caused.libxml2-2.9
isn’t configured properly to work alongside the newer version because it hasn’t set itsSONAME
properly, so dynamically linking against this library is made more complicated even with correct compiler flags set.objdump -x /usr/lib/libxml2-2.9/libxml2.so.2.9.10 | grep -i soname
giveslibxml2.so.2
, the same name as the new library version which shadows it. Also seeldconfig -p | grep libxml2
. So a proper fix would be to patch this other package (or as a quick fix dopatchelf --set-soname libxml2.so.2.9.10 /usr/lib/libxml2-2.9/libxml2.so.2.9.10; ldconfig
).It is however possible to build the package anyway by setting the runtime path in the linker options of
gcc
. To do this, both invocations ofsetup.py
inPKGBUILD
have to be run with these additional arguments:python setup.py ... --with-xml2-config=xml2-config-2.9 --with-xslt-config=xslt-config --auto-rpath
. Thengcc
puts full paths into theRUNPATH
shared object property. This works for me, however, as the history oflibtool
shows, it may result in other problems.1 2 3 4 5 Next › Last »