From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 199DC158020 for ; Fri, 23 Dec 2022 14:53:57 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8C6CBE0863; Fri, 23 Dec 2022 14:53:53 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4F215E0826 for ; Fri, 23 Dec 2022 14:53:53 +0000 (UTC) Message-ID: <00903008109ecd10b2dc8619e9d167e5cb3264ac.camel@gentoo.org> Subject: Re: [gentoo-dev] Last rites: dev-python/* using nose, with no revdeps From: Michael Orlitzky To: gentoo-dev@lists.gentoo.org Date: Fri, 23 Dec 2022 09:53:49 -0500 In-Reply-To: <433a3c57f5e0a741165b8122413c7698acf9e0e8.camel@gentoo.org> References: <433a3c57f5e0a741165b8122413c7698acf9e0e8.camel@gentoo.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.2 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 X-Archives-Salt: 6d5394c9-7ee0-4d2d-9609-eb245af07e4f X-Archives-Hash: 53df3b41cb2cf145c7f0a2044aab4a35 On Fri, 2022-12-23 at 15:35 +0100, Micha=C5=82 G=C3=B3rny wrote: > # Micha=C5=82 G=C3=B3rny (2022-12-23) > # Packages that still use dev-python/nose and have no revdeps. > # > ... > dev-python/python-redmine I'm the (only) maintainer for this, and I didn't even know there was a problem. I have at least filed an upstream issue now. I suppose it suffices to RESTRICT the tests for now?