Summary: | net-wireless/crda-1.1.3-r1 with dev-python/m2crypto-0.22.3-r2 with dev-lang/swig-3.0.5 - /usr/lib64/python2.7/site-packages/M2Crypto/BIO.py: AttributeError: 'module' object has no attribute 'PKCS5_SALT_LEN' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | dyle <dyle> |
Component: | Current packages | Assignee: | Panagiotis Christopoulos (RETIRED) <pchrist> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | anton.gubarkov, bitlord0xff, carlphilippreh, cornicx, disp.reg.bugs.gentoo, dlan, doug.hunley, fcoiffie, fordfrog, fulminemizzega, gentoo, gentoobugs, gurligebis, hkbst, hwoarang, iskatu, jgeboski, jwbraun, klaus818, krinpaus, lukas.schneiderbauer, markus.knetschke, mkresch, mmk, nholland, pageexec, patrakov, python, radhermit, robin, scheme, sven.koehler, tetromino, vityokster, whissi, zerochaos, zlg |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 531736 |
Description
dyle
2015-02-05 12:08:15 UTC
I hit this bug too. Also confirming; crda-1.1.3-r1 compiles fine when m2crypto-0.22.3-r2 is emerged with swig-3.0.4. (In reply to Charlie Gehlin from comment #2) > Also confirming; crda-1.1.3-r1 compiles fine when m2crypto-0.22.3-r2 is > emerged with swig-3.0.4. This is an annoying bug. I confirmed it on mips where you hit this because everything is ~mips. One way to fix this is to change the deps on m2crypto to <=dev-lang/swig-3.0.4 and rev bump to force a rebuild. Does m2crtypo work fine otherwise with swig-3.0.5? Because the other approach is to blame crda and fix up its code to use whatever new method there is to get PKCS5_SALT_LEN. I suspect there must be some way of doing that. *** Bug 540618 has been marked as a duplicate of this bug. *** had the same issue and resolution. (In reply to Anthony Basile from comment #3) > One way to fix this is to change the deps on m2crypto to > <=dev-lang/swig-3.0.4 and rev bump to force a rebuild. Does m2crtypo work > fine otherwise with swig-3.0.5? I would say no, given that this is enough to trigger the error: python2.7 -c "from M2Crypto import RSA" Re-assigning this to the python team. I bisected swig, and arrived at this as the first "bad" commit: https://github.com/swig/swig/commit/c21e2423a02939d2a4bc02bdfaa5c3bed3be95b2 swig maintainers, can you please take a look and possibly report this upstream? (In reply to Mike Gilbert from comment #7) > I bisected swig, and arrived at this as the first "bad" commit: > > https://github.com/swig/swig/commit/c21e2423a02939d2a4bc02bdfaa5c3bed3be95b2 > > swig maintainers, can you please take a look and possibly report this > upstream? https://github.com/swig/swig/issues/344 *** Bug 542224 has been marked as a duplicate of this bug. *** *** Bug 542268 has been marked as a duplicate of this bug. *** Per https://github.com/martinpaljak/M2Crypto/issues/60 M2Crypto is being fixed for swig 3.0.5, so making the current version depend on swig 3.0.4 with a revbump, and then the next release of M2Crypto removing that version dep would likely solve most systems without manual intervention. The same error persists in crda-3.18 with dev-lang/swig-3.0.5 and dev-python/m2crypto-0.22.3-r2 installed. So is anyone in particular interested in fixing this? +*m2crypto-0.22.3-r3 (14 Mar 2015) + + 14 Mar 2015; Michał Górny <mgorny@gentoo.org> +m2crypto-0.22.3-r3.ebuild, + -m2crypto-0.22.3-r2.ebuild, m2crypto-0.21.1-r2.ebuild: + Require swig < 3.0.5 as a workaround for bug #538920 (broken constants in + modules). Now things will at least work. Leaving bug open for proper solution. Do the patches listed here fix the issue? https://github.com/martinpaljak/M2Crypto/issues/60 The patches perfectly apply during emerge m2crypto but I don't have any expertise to test beside just rebooting now and see if this works: --- # emerge -p -1 m2crypto swig These are the packages that would be merged, in order: Calculating dependencies ... done! [ebuild R ] dev-lang/swig-3.0.5::gentoo [ebuild R ] dev-python/m2crypto-0.22.3-r4::pmaci --- (In reply to Ulenrich from comment #15) > Do the patches listed here fix the issue? > > https://github.com/martinpaljak/M2Crypto/issues/60 > > The patches perfectly apply during emerge m2crypto > but I don't have any expertise to test > beside just rebooting now and see if this works: > --- > # emerge -p -1 m2crypto swig > > These are the packages that would be merged, in order: > > Calculating dependencies ... done! > [ebuild R ] dev-lang/swig-3.0.5::gentoo > [ebuild R ] dev-python/m2crypto-0.22.3-r4::pmaci > --- The patch applies cleanly to m2crypto however crda still fails to build with a slightly different error after the patch: laptop ~ # emerge --nodeps -av =swig-3.0.5 m2crypto crda These are the packages that would be merged, in order: [ebuild R ] dev-lang/swig-3.0.5::gentoo USE="pcre -ccache -doc" 0 KiB [ebuild R ] dev-python/m2crypto-0.22.3-r3::gentoo PYTHON_TARGETS="python2_7" 0 KiB [ebuild R ] net-wireless/crda-3.18::gentoo USE="-gcrypt" 0 KiB Total: 3 packages (3 reinstalls), Size of downloads: 0 KiB Would you like to merge these packages? [Yes/No] ^C Interrupted. laptop ~ # emerge --nodeps crda >>> Verifying ebuild manifests >>> Emerging (1 of 1) net-wireless/crda-3.18::gentoo * crda-3.18.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) [ ok ] >>> Unpacking source... >>> Unpacking crda-3.18.tar.xz to /var/tmp/portage/net-wireless/crda-3.18/work >>> Source unpacked in /var/tmp/portage/net-wireless/crda-3.18/work >>> Preparing source in /var/tmp/portage/net-wireless/crda-3.18/work/crda-3.18 ... * Applying crda-3.18-no-ldconfig.patch [ ok ] * Applying crda-3.18-no-werror.patch [ ok ] * Applying crda-3.18-openssl.patch [ ok ] * Applying crda-3.18-cflags.patch [ ok ] * Applying crda-3.18-libreg-link.patch [ ok ] >>> Source prepared. >>> Configuring source in /var/tmp/portage/net-wireless/crda-3.18/work/crda-3.18 ... >>> Source configured. >>> Compiling source in /var/tmp/portage/net-wireless/crda-3.18/work/crda-3.18 ... make -j5 -l10 PREFIX=/usr SBINDIR=$(PREFIX)/sbin/ LIBDIR=$(PREFIX)/lib64 UDEV_RULE_DIR=/lib/udev/rules.d REG_BIN=/usr/lib/crda/regulatory.bin USE_OPENSSL=1 CC=x86_64-pc-linux-gnu-gcc V=1 WERROR= all_noverify ./utils/key2pub.py --ssl pubkeys/linville.key.pub.pem pubkeys/sforshee.key.pub.pem keys-ssl.c ERROR: Failed to import the "M2Crypto" module: No module named _m2crypto Please install the "M2Crypto" Python module. On Debian GNU/Linux the package is called "python-m2crypto". Makefile:114: recipe for target 'keys-ssl.c' failed make: *** [keys-ssl.c] Error 1 Please test m2crypto-0.22.3-r4. +*m2crypto-0.22.3-r4 (25 May 2015) + + 25 May 2015; Mike Gilbert <floppym@gentoo.org> + +files/0.22.3-Use-swig-generated-python-loader.patch, + +files/0.22.3-packaging.patch, +m2crypto-0.22.3-r4.ebuild: + Resolve issues with swig-3.0.5, bug 538920. Please try m2crypto-0.21.1-r3 as well. +*m2crypto-0.21.1-r3 (25 May 2015) + + 25 May 2015; Mike Gilbert <floppym@gentoo.org> + +files/0.21.1-0001-Fixed-invalid-variable-name.patch, + +files/0.21.1-0002-Fixing-memory-leaks-in-the-SWIG-wrapper.patch, + +files/0.21.1-0003-Use-swig-generated-python-loader.patch, + +files/0.21.1-packaging.patch, +m2crypto-0.21.1-r3.ebuild: + Resolve issues with swig-3.0.5 in the older 0.21 fork as well. Successfully built dev-lang/swig-3.0.5::gentoo, dev-python/m2crypto-0.22.3-r4::gentoo and net-wireless/crda-3.18::gentoo. dev-python/m2crypto-0.21.1-r3 still depends on old swig, so will not test (In reply to Alexander E. Patrakov from comment #20) > dev-python/m2crypto-0.21.1-r3 still depends on old swig, so will not test Sorry, missed that. + 26 May 2015; Mike Gilbert <floppym@gentoo.org> m2crypto-0.21.1-r3.ebuild: + Unpin swig. I'm going to call this fixed. A stable request has been filed (bug 545606). |