Summary: | dev-python/m2crypto-0.22.3-r4 stable request | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Matthias Lippert <mae.lippert> |
Component: | [OLD] Keywording and Stabilization | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | junghans, stephan.menzel |
Priority: | Normal | Keywords: | STABLEREQ |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 531736 |
Description
Matthias Lippert
2015-04-05 11:00:59 UTC
The quoted message is meant to inform you that *swig* will not be updated to a newer version due to m2crypto not working with it yet. In stead, a version of swig lower-than 3.0.5 will be used. See bug 538920 for details on the incompatibility. Portage does not consider this situation on its own to be an error, and will typically continue with the current task after printing the message. Now this is even a problem on stable amd64. I guess the solution would be to stabilize =m2crypto-0.22.3-r4. Please stabilize: =dev-python/m2crypto-0.22.3-r4 Stable for PPC64. arm stable Stable for HPPA. amd64 stable x86 stable ppc stable alpha stable ia64 stable sparc stable. Closing. |