| Summary: | dev-python/pivy: lacks py3.10 and tests | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Michał Górny <mgorny> |
| Component: | Current packages | Assignee: | Miroslav Šulc <fordfrog> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | waebbl-gentoo |
| Priority: | Normal | Keywords: | PullRequest |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=849746 https://github.com/gentoo/gentoo/pull/25823 |
||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 823185 | ||
|
Description
Michał Górny
2022-03-21 09:44:51 UTC
They should soon release a bumped version with support for py3.10. See https://github.com/coin3d/pivy/issues/88 and https://github.com/coin3d/pivy/pull/91 Has been fixed by commit a35d208ffe7246ec96d27054ca272ab8611e7747 Re-opening, only the py310 support is fixed, but not the tests. The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e484db6607f4e935f843e753af1ed8425b00547a commit e484db6607f4e935f843e753af1ed8425b00547a Author: Bernd Waibel <waebbl-gentoo@posteo.net> AuthorDate: 2022-04-29 06:56:14 +0000 Commit: Miroslav Šulc <fordfrog@gentoo.org> CommitDate: 2022-06-10 08:48:23 +0000 dev-python/pivy: bump to 0.6.7 Add py3_11 support, enabling tests Closes: https://bugs.gentoo.org/849746 Bug: https://bugs.gentoo.org/835724 Signed-off-by: Bernd Waibel <waebbl-gentoo@posteo.net> Closes: https://github.com/gentoo/gentoo/pull/25823 Signed-off-by: Miroslav Šulc <fordfrog@gentoo.org> dev-python/pivy/Manifest | 1 + dev-python/pivy/files/pivy-0.6.7-find-qmake.patch | 29 +++++++++++ dev-python/pivy/pivy-0.6.7.ebuild | 59 +++++++++++++++++++++++ 3 files changed, 89 insertions(+) @Sam: Technically the issue hasn't been solved for ~pivy-0.6.6 with the patch, but only for pivy-0.6.7. (In reply to Bernd from comment #5) > @Sam: Technically the issue hasn't been solved for ~pivy-0.6.6 with the > patch, but only for pivy-0.6.7. I think that's OK. We can just stable new Pivy now (in a separate bug), ideally quite soon. |