| Summary: | dev-python/pyqtgraph-0.9.10 works just fine with PyQt5 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Helmut Jarausch <jarausch> |
| Component: | Current packages | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | qt |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Helmut Jarausch
2015-07-28 12:03:56 UTC
Anything involving qt ought be reviewed by the qt herd, especially anything involving qt4 qt5 options. I suggest qt herd at least be added to metadata.xml make co-maintainership, alternatively switch to qt dev-python/pyqtgraph-0.10.0 allows PyQt5 alternatively to PyQt4 albeit without exposing this through a USE flag - so I guess this bug is obsolete? (In reply to Andreas Sturmlechner from comment #2) > dev-python/pyqtgraph-0.10.0 allows PyQt5 alternatively to PyQt4 albeit > without exposing this through a USE flag - so I guess this bug is obsolete? so it's an automagic dep? that's not good... The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a6cb83a39beef31a0a9a14431446292f02443501 commit a6cb83a39beef31a0a9a14431446292f02443501 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2018-03-05 14:52:23 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2018-03-05 14:58:35 +0000 dev-python/pyqtgraph: Drop 0.10.0 Closes: https://bugs.gentoo.org/556106 Package-Manager: Portage-2.3.24, Repoman-2.3.6 dev-python/pyqtgraph/pyqtgraph-0.10.0.ebuild | 52 ---------------------------- 1 file changed, 52 deletions(-) |
