Please stabilize.
ALLARCHES stable. Closing.
Reopening for missing arches.
(In reply to Michał Górny from comment #2) > Reopening for missing arches. For ikelos: what happened here is that because amd64/x86 were manually CCed, the nattka bot couldn't CC the correct arches (see https://packages.gentoo.org/packages/dev-python/mypy -- i.e. most of them). Using * as was done in the original bug means that nattka expands the CC list for us and ensures we don't miss other arches. See: https://archives.gentoo.org/gentoo-dev/message/e7eb47e3395c18bd98f25e90aabfc816 and https://archives.gentoo.org/gentoo-dev/message/b71fc507d5e017569d7ba385e257afe4 (the original announcement).
arm arm64 ppc ppc64 sparc (ALLARCHES) done all arches done
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=18ccda1e517a9a9237dbeebdfe8ae5a2eb4d4d9a commit 18ccda1e517a9a9237dbeebdfe8ae5a2eb4d4d9a Author: Sam James <sam@gentoo.org> AuthorDate: 2021-02-26 16:46:36 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-02-26 16:48:17 +0000 dev-python/mypy: "Remove old" This reverts commit 2d14e70d597d62cdf758f83ed19fc5126179350a. Bug: https://bugs.gentoo.org/772491 Signed-off-by: Sam James <sam@gentoo.org> dev-python/mypy/Manifest | 2 + dev-python/mypy/files/mypy-0.790-py39-fixes.patch | 161 ++++++++++++++++++++++ dev-python/mypy/mypy-0.790.ebuild | 76 ++++++++++ 3 files changed, 239 insertions(+) https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=875af1de0ff4632864be59f044af5212d450645e commit 875af1de0ff4632864be59f044af5212d450645e Author: Sam James <sam@gentoo.org> AuthorDate: 2021-02-26 16:46:03 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-02-26 16:48:16 +0000 dev-python/mypy: not suitable for ALLARCHES Compiles libraries: >copying build/lib.linux-sparc64-3.8/native__mypyc.cpython-38-sparc-linux-gnu.so >copying build/lib.linux-sparc64-3.8/native.cpython-38-sparc-linux-gnu.so >copying build/lib.linux-sparc64-3.8/other__mypyc.cpython-38-sparc-linux-gnu.so >copying build/lib.linux-sparc64-3.8/other.cpython-38-sparc-linux-gnu.s Bug: https://bugs.gentoo.org/773088 Bug: https://bugs.gentoo.org/772491 Package-Manager: Portage-3.0.15, Repoman-3.0.2 Signed-off-by: Sam James <sam@gentoo.org> dev-python/mypy/metadata.xml | 1 - 1 file changed, 1 deletion(-)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e3084383ab861819d4a8d96badbd6edd22a2e517 commit e3084383ab861819d4a8d96badbd6edd22a2e517 Author: Sam James <sam@gentoo.org> AuthorDate: 2021-02-26 17:45:57 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-02-26 17:46:02 +0000 dev-python/mypy: revert to ~arch for 0.800 Bug: https://bugs.gentoo.org/772491 Package-Manager: Portage-3.0.15, Repoman-3.0.2 Signed-off-by: Sam James <sam@gentoo.org> dev-python/mypy/mypy-0.800.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arm64 done
Ok, sorry about that Sam. My understanding was that I shouldn't be asking for stabilization of packages I haven't tested on other arches, but it seems I don't need to be involved in stabilization at all unless an issue arises. Perhaps it would be better to assign stabilization requests to a nattka alias and simply CC in the maintainers?
amd64 done
