From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites: dev-python/* using nose, with no revdeps
Date: Fri, 23 Dec 2022 17:43:18 +0100 [thread overview]
Message-ID: <e4840038fb60f3a23b39d8c86e7241ce75a20a27.camel@gentoo.org> (raw)
In-Reply-To: <00903008109ecd10b2dc8619e9d167e5cb3264ac.camel@gentoo.org>
On Fri, 2022-12-23 at 09:53 -0500, Michael Orlitzky wrote:
> On Fri, 2022-12-23 at 15:35 +0100, Michał Górny wrote:
> > # Michał Górny <mgorny@gentoo.org> (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 you should start using pkgcheck then, or reading QA reports
for your packages.
> I suppose it suffices to RESTRICT the tests for now?
>
That's more harm than good. We can't lastrite nose at this point
anyway, we're just moving through the huge list.
--
Best regards,
Michał Górny
next prev parent reply other threads:[~2022-12-23 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 14:35 [gentoo-dev] Last rites: dev-python/* using nose, with no revdeps Michał Górny
2022-12-23 14:53 ` Michael Orlitzky
2022-12-23 16:43 ` Michał Górny [this message]
[not found] ` <2659553.mvXUDI8C0e@t490>
2022-12-23 20:21 ` [gentoo-dev-announce] " John Helmert III
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e4840038fb60f3a23b39d8c86e7241ce75a20a27.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox