public inbox for gentoo-dev-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev-announce] Last rites: app-admin/salt, dev-python/pytest-salt-factories, dev-python/boto
Date: Tue, 27 Feb 2024 16:42:46 +0100	[thread overview]
Message-ID: <3ec0b5307557f30d9cc4f35d7100b25849bb81a4.camel@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 478 bytes --]

# Michał Górny <mgorny@gentoo.org> (2024-02-27)
# dev-python/boto is dead, with last release in 2018.  It has been
# replaced by dev-python/boto3.  It carries a ton of patches and still
# depends on dev-python/nose.
#
# app-admin/salt is its only remaining reverse dependency.  The ebuild
# is of very low quality.
#
# Removal on 2024-03-28.  Bug #888235.
app-admin/salt
dev-python/pytest-salt-factories
dev-python/boto

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]

                 reply	other threads:[~2024-02-27 15:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3ec0b5307557f30d9cc4f35d7100b25849bb81a4.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev-announce@lists.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