| Summary: | "AssertionError: SRE module mismatch" when EPYTHON=pypy3 and dev-python/pypy3 is not the last package to be merged | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Jeffrey Lin <jeffrey> |
| Component: | Core | Assignee: | Portage team <dev-portage> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | CC: | python, sam |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=770421 https://bugs.gentoo.org/show_bug.cgi?id=835146 |
||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge output
pypy3 merge log mesa log |
||
Created attachment 699873 [details]
pypy3 merge log
Notice "AssertionError: SRE module mismatch" errors in phases after install.
Created attachment 699879 [details]
mesa log
Mesa was the package scheduled for merging after pypy3, here is its log.
No other packages after this one had a log, as seen in the emerge output attachment.
I should note that running the original emerge command a second time was successful, so it might be something to do with upgrading pypy3 while it is in use.
|
Created attachment 699870 [details] emerge output net-misc/curl failure is not related, please ignore. Notice that packages emerge fine until dev-python/pypy3 is upgraded, then the next package (mesa) dies in pretend phase with "AssertionError: SRE module mismatch". All later packages fail without a log.