Summary: | =dev-python/matplotlib-2.1.2-r1 stabilisation | ||||||
---|---|---|---|---|---|---|---|
Product: | Gentoo Linux | Reporter: | Till Schäfer <till2.schaefer> | ||||
Component: | Stabilization | Assignee: | Gentoo Science Related Packages <sci> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | normal | CC: | asturm, dan, frp.bissey, iskatu, kripton, luisav.ferreira, msava, o.freyermuth, python, tb | ||||
Priority: | Normal | Keywords: | STABLEREQ | ||||
Version: | unspecified | Flags: | stable-bot:
sanity-check+
|
||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Package list: |
dev-python/matplotlib-2.1.2-r1
dev-python/cycler-0.10.0
dev-python/versioneer-0.16
dev-python/cairocffi-0.8.0
dev-python/colorspacious-1.1.0
dev-python/xcffib-0.5.1
media-libs/qhull-2015.2
dev-python/subprocess32-3.2.7
dev-python/functools32-3.2.3
dev-python/sphinx-gallery-0.1.12
|
Runtime testing required: | --- | ||||
Bug Depends on: | 622420, 626878 | ||||||
Bug Blocks: | 571778, 613350, 634952, 638792 | ||||||
Attachments: |
|
Description
Till Schäfer
2017-10-31 15:00:56 UTC
The current stable package fails for everybody upgrading to python 3.5 with qt5 enabled. Can you please proceed with the stabilization? This version also appears to be unaffected by the ICE from bug # 638792 and could workaround that problem if stabilized. Please stabilise. dev-python/matplotlib-1.4.3 is broken (as above) on the stable non-keyword portage tree. This version builds some of the times. See bug #581550. If someone could come up with a list of dependencies that need to be stabilized, that would help move this bug along. As far as I can see, we need: - dev-python/cycler-0.10.0 - dev-python/versioneer-0.16 Well, let's give it a shot. An automated check of this bug failed - repoman reported dependency errors (19 lines truncated):
> dependency.bad dev-python/matplotlib/matplotlib-1.5.3-r2.ebuild: DEPEND: arm(default/linux/arm/13.0) ['dev-python/cairocffi[python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)]']
> dependency.bad dev-python/matplotlib/matplotlib-1.5.3-r2.ebuild: RDEPEND: arm(default/linux/arm/13.0) ['dev-python/cairocffi[python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)]']
> dependency.bad dev-python/matplotlib/matplotlib-1.5.3-r2.ebuild: DEPEND: ppc64(default/linux/powerpc/ppc64/13.0/64bit-userland) ['dev-python/cairocffi[python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)]']
cairocffi-0.8.0 may not need stabilisation (I am not against but it is not the point here), 0.7.2 is quite enough. The message just says there isn't a stable version of cairocffi on two arch - arm and ppc64. Is there any reason cairocffi-0.7.2 cannot be stabilised on those arch and therefore require 0.8.0? (In reply to François Bissey from comment #9) cairocffi-0.8.0 has been in the tree for several months. I see no obvious reason not to stabilize it. Like I said I am not against it. It just felt the wrong answer to the question. Do we know why there is no stable cairocffi on arm and ppc64? Any problems on those arch could very well be still present with 0.8.0. (In reply to François Bissey from comment #11) For someone who is not against it, you sure are asking a lot of questions... Anyway, it's not stable on those archs because nobody asked those arch teams to mark it stable. (In reply to Mike Gilbert from comment #12) > (In reply to François Bissey from comment #11) > > For someone who is not against it, you sure are asking a lot of questions... > I don't see any contradiction in that. I am a trained scientist, I ask questions about things. > Anyway, it's not stable on those archs because nobody asked those arch teams > to mark it stable. OK. It turns out that both cairocffi-0.7.2 and cairocffi-0.8.0 have issues that need resolving. Help investigating would be most welcome. An automated check of this bug failed - repoman reported dependency errors (19 lines truncated):
> dependency.bad dev-python/cairocffi/cairocffi-0.8.0.ebuild: DEPEND: arm(default/linux/arm/13.0) ['>=dev-python/xcffib-0.3.2[python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)]']
> dependency.bad dev-python/cairocffi/cairocffi-0.8.0.ebuild: RDEPEND: arm(default/linux/arm/13.0) ['>=dev-python/xcffib-0.3.2[python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)]']
> dependency.bad dev-python/cairocffi/cairocffi-0.8.0.ebuild: DEPEND: ppc64(default/linux/powerpc/ppc64/13.0/64bit-userland) ['>=dev-python/xcffib-0.3.2[python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)]']
(In reply to François Bissey from comment #13) > I don't see any contradiction in that. I am a trained scientist, I ask > questions about things. Please consider that answering your questions takes a little bit of my time, and that's really wasted time on my side. It also kind of seems like you don't think I know what I'm doing, which kind of irks me. I'm guessing that's not your intent, but that's how it came across to me. To more directly answer the question of "why 0.8.0 instead of 0.7.2": it actually saves work in the long run. This way the arm and ppc64 teams will only have to test 1 version instead of 2. An automated check of this bug succeeded - the previous repoman errors are now resolved. I also would like this to be stabilized. I have a clean system and will install it soon again. I will let you guys know if it barks with some dependencies. Are they any specific use flags someone want to be checked before I give it a go ? I know that 1.4.3 has similar segfaults, so in my opinion, the random png saved plot segfault while threaded(tk) in 1.5.x and 1.4.x are in all available packages. 1.5.x does solve some issues with threading. And it does compile with the latest batch of stable :) I can't reproduce the cairocffi-0.8.0 failure on stable. Since 1.5.3-r1 was removed, let's bump this to 2.1.0-r1. An automated check of this bug failed - repoman reported dependency errors (95 lines truncated):
> dependency.bad dev-python/matplotlib/matplotlib-2.1.0-r1.ebuild: DEPEND: amd64(default/linux/amd64/13.0) ['dev-python/subprocess32[python_targets_python2_7(-)?,-python_single_target_python2_7(-)]', '>=media-libs/qhull-2013', 'dev-python/colorspacious[python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)]']
> dependency.bad dev-python/matplotlib/matplotlib-2.1.0-r1.ebuild: RDEPEND: amd64(default/linux/amd64/13.0) ['dev-python/subprocess32[python_targets_python2_7(-)?,-python_single_target_python2_7(-)]', '>=media-libs/qhull-2013']
> dependency.bad dev-python/matplotlib/matplotlib-2.1.0-r1.ebuild: DEPEND: amd64(default/linux/amd64/13.0/desktop) ['dev-python/subprocess32[python_targets_python2_7(-)?,-python_single_target_python2_7(-)]', '>=media-libs/qhull-2013', 'dev-python/colorspacious[python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)]']
An automated check of this bug failed - repoman reported dependency errors (47 lines truncated):
> dependency.bad dev-python/matplotlib/matplotlib-2.1.0-r1.ebuild: DEPEND: amd64(default/linux/amd64/13.0) ['dev-python/colorspacious[python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)]']
> dependency.bad dev-python/matplotlib/matplotlib-2.1.0-r1.ebuild: DEPEND: amd64(default/linux/amd64/13.0/desktop) ['dev-python/colorspacious[python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)]']
> dependency.bad dev-python/matplotlib/matplotlib-2.1.0-r1.ebuild: DEPEND: amd64(default/linux/amd64/13.0/desktop/gnome) ['dev-python/colorspacious[python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)]']
An automated check of this bug failed - repoman reported dependency errors:
> dependency.bad dev-python/matplotlib/matplotlib-2.1.0-r1.ebuild: DEPEND: arm(default/linux/arm/13.0) ['dev-python/functools32[python_targets_python2_7(-)?,-python_single_target_python2_7(-)]']
> dependency.bad dev-python/matplotlib/matplotlib-2.1.0-r1.ebuild: RDEPEND: arm(default/linux/arm/13.0) ['dev-python/functools32[python_targets_python2_7(-)?,-python_single_target_python2_7(-)]']
x86 stopped stabilization due to bug 643626. x86 stable No, x86 is not stable - I run the wrong script :/ x86 stable amd64 stable Created attachment 515354 [details]
error compile phase with python 2.7
I'm using gentoo with profile
default/linux/amd64/17.0 (stable)
It compiles with python 2.7 and fails.
I think matplotlib-2.1.0-r1 was accidentally cleaned from the tree, making the only stable in-tree version 1.4.3. If memory serves, 1.4.3 doesn't currently compile with PIE enabled and/or qt-5.7. Could it please be added back if this was unintentional? Raising stabilisation target to dev-python/matplotlib-2.1.2-r1 to follow up changes in bug 622420, re-adding amd64/x86. Adding dev-python/sphinx-gallery-0.1.12 to obsolete bug 644002. *** Bug 644002 has been marked as a duplicate of this bug. *** ppc64 stable amd64 stable (In reply to Samuel Bernardo from comment #29) > Created attachment 515354 [details] > error compile phase with python 2.7 > > I'm using gentoo with profile > default/linux/amd64/17.0 (stable) > > It compiles with python 2.7 and fails. Same problem, here; the output of emerge is the same. I am using gentoo (stable) with profile default/linux/amd64/17.0/desktop/plasma (stable) Use flags and python targets for matplotlib: cairo examples gtk2 latex qt5 tk wxwidgets -doc -excel -gtk3 -pyside -test PYTHON_TARGETS="python2_7 python3_5 -python3_4 -python3_6" (In reply to João Paulo Teixeira from comment #35) > (In reply to Samuel Bernardo from comment #29) > > Created attachment 515354 [details] > > error compile phase with python 2.7 > > > > I'm using gentoo with profile > > default/linux/amd64/17.0 (stable) > > > > It compiles with python 2.7 and fails. > > Same problem, here; the output of emerge is the same. I am using gentoo > (stable) with profile > > default/linux/amd64/17.0/desktop/plasma (stable) > > Use flags and python targets for matplotlib: > > cairo examples gtk2 latex qt5 tk wxwidgets -doc -excel -gtk3 -pyside -test > PYTHON_TARGETS="python2_7 python3_5 -python3_4 -python3_6" It looks like wxgtk needs to be rebuilt: Fatal Error: Mismatch between the program and library build versions detected. The library used 3.0 (wchar_t,compiler with C++ ABI 1010,wx containers,compatible with 2.8), and wxPython used 3.0 (wchar_t,compiler with C++ ABI 1009,wx containers,compatible with 2.8). I'd say it has been compiled with an older version of g++ that some other parts tested and matplotlib doesn't like it. I'm the following error during compilation, that seems to be related to the errors described in previous messages: Fatal Error: Mismatch between the program and library build versions detected. The library used 3.0 (wchar_t,compiler with C++ ABI 1010,wx containers,compatible with 2.8), and wxPython used 3.0 (wchar_t,compiler with C++ ABI 1009,wx containers,compatible with 2.8). qt5agg: yes [installing, Qt: 5.9.4, PyQt: 5.9.4; PySide2 not found] qt4agg: no [skipping due to configuration] gtk3agg: no [skipping due to configuration] gtk3cairo: no [skipping due to configuration] gtkagg: no [skipping due to configuration] tkagg: yes [installing; run-time loading from Python Tcl / Tk] /var/tmp/portage/dev-python/matplotlib-2.1.2-r1/temp/environment: line 1737: 10247 Aborted (core dumped) "${@}" * ERROR: dev-python/matplotlib-2.1.2-r1::gentoo failed (compile phase): * (no error message) It seems that matplotlib-2.1.2-r1 revealed a missing compile dependency for wxPython, that need to be recompiled when gcc is upgraded. x86 stable No longer blocking gcc-7-stable. Superseded by bug 655400. |