| Summary: | Python headers included are bungled, probably due to multi-arch issues | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Denis Bitouzé <dbitouze> |
| Component: | RPM Packages | Assignee: | Philippe Makowski <makowski.mageia> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | davidwhodgins, makowski.mageia, qa-bugs |
| Version: | 3 | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | python-2.7.5-1.2.mga3.src.rpm | CVE: | |
| Status comment: | |||
| Bug Depends on: | 11785 | ||
| Bug Blocks: | |||
| Attachments: | correct virualenv.py | ||
|
Description
Denis Bitouzé
2013-09-24 19:07:05 CEST
Manuel Hiebel
2013-09-27 21:32:42 CEST
CC:
(none) =>
makowski.mageia for me it is a bug in the pillow install script later versions don't have this problem we package it without problem report this to plone or tweak their setup to use a better version of pillow 1.7.8 is an old version Created attachment 4382 [details]
correct virualenv.py
I did some tests, the problem is in the virtualenv they are setting up, that have include/multiarch-x86_64-linux/python2.7 -> /usr/include/python2.7/
instead of
include/python2.7 -> /usr/include/python2.7/
so if in their /packages/virtualenv-1.10.1.tar.gz you put this virtualenv.py instead, all is ok
(In reply to Philippe Makowski from comment #2) > Created attachment 4382 [details] > correct virualenv.py > > I did some tests, the problem is in the virtualenv they are setting up, that > have include/multiarch-x86_64-linux/python2.7 -> /usr/include/python2.7/ > instead of > include/python2.7 -> /usr/include/python2.7/ > > so if in their /packages/virtualenv-1.10.1.tar.gz you put this virtualenv.py > instead, all is ok I'll try it, thanks! As it works like this with Ubuntu, is there a way to have something which works in all cases? yes, report the problem to upstream virtualenv it seems that these lines (1009:10019) in virtualenv.py (https://github.com/pypa/virtualenv/blob/develop/virtualenv.py#L1009) multiarch_exec = '/usr/bin/multiarch-platform' if is_executable_file(multiarch_exec): # In Mageia (2) and Mandriva distros the include dir must be like: # virtualenv/include/multiarch-x86_64-linux/python2.7 # instead of being virtualenv/include/python2.7 p = subprocess.Popen(multiarch_exec, stdout=subprocess.PIPE, stderr=subprocess.PIPE) stdout, stderr = p.communicate() # stdout.strip is needed to remove newline character inc_dir = join(home_dir, 'include', stdout.strip(), py_version + abiflags) else: inc_dir = join(home_dir, 'include', py_version + abiflags) are causing more trouble that solving a problem that don't exist anymore under Mageia pull request to upstream : https://github.com/pypa/virtualenv/pull/472 (In reply to Philippe Makowski from comment #5) > pull request to upstream : https://github.com/pypa/virtualenv/pull/472 I confirm Plone can be installed smoothly on Mageia 3 as soon as virtualenv.py is changed as you said. Thanks! Updated packages in core/updates_testing: ======================== python-virtualenv-1.10.1-1.2.mga3.noarch Source RPMs: python-virtualenv-1.10.1-1.2.mga3.src This also fix mga#11785 Assignee:
bugsquad =>
qa-bugs This bug should be closed when bug 11785 is pushed, as it includes python-virtualenv-1.10.1-1.2.mga3.src. CC:
(none) =>
davidwhodgins Assigning Philippe again as python-virtualenv is being updated in bug 11785 which is also assigned to QA Could you update the advisory there please Philippe to reflect the fixes here too. CC:
(none) =>
qa-bugs Suggested advisory: ======================== Updated python-virtualenv packages fix : - security vulnerabilities: Changed behavior of ssl.match_hostname() to follow RFC 6125 (mga#11785). References: https://bugs.mageia.org/show_bug.cgi?id=11785 http://bugs.python.org/issue17997#msg194950 - inc_dir settings to avoid #include nested too deeply" error References: https://bugs.mageia.org/show_bug.cgi?id=11283 Updated packages in core/updates_testing: ======================== python-virtualenv-1.10.1-1.2.mga3.noarch Source RPMs: python-virtualenv-1.10.1-1.2.mga3.src Assignee:
makowski.mageia =>
qa-bugs Sorry Philippe if it wasn't clear, I was meaning on the other bug. We have two bugs assigned for the same package update at the moment and will be using bug 11785 where python-virtualenv is part of the security update rather than this one. Please leave this one assigned to yourself to avoid the confusion. Assignee:
qa-bugs =>
makowski.mageia Done Status:
NEW =>
RESOLVED Unfortunately, this bug still arises with Plone 4.3.4 on Mageia 4. (In reply to Denis Bitouzé from comment #13) > Unfortunately, this bug still arises with Plone 4.3.4 on Mageia 4. again see my comments, I can't do anything if virtualenv insist on not applying the patch. And why Plone insist on installing their own virualenv. We patch virtualenv in our package, if you use our package or vitualenv with this patch (http://svnweb.mageia.org/packages/cauldron/python-virtualenv/current/SOURCES/virtualenv-1.10.1-mga-fix_inc_dir.patch?view=markup), all is ok. Report upstream yourself to virtualenv and or plone. OK, sorry for the noise. |