public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-dev-announce] Last rites: net-nds/nsscache
Date: Thu, 25 Jan 2024 12:32:06 +0100	[thread overview]
Message-ID: <274e14c990c0a42b42a4ba43270a38b8ef8f78ab.camel@gentoo.org> (raw)
In-Reply-To: <robbat2-20240125T073609-341725009Z@orbis-terrarum.net>

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

On Thu, 2024-01-25 at 07:40 +0000, Robin H. Johnson wrote:
> On Wed, Jan 24, 2024 at 12:55:25PM +0100, Michał Górny wrote:
> > # Michał Górny <mgorny@gentoo.org> (2024-01-24)
> > # No support for Python 3.11+.  No PEP517.  Tests are not enabled.
> > # The current keyworded version is from 2019.  It was bumped in 2022
> > # but it has not been keyworded since (pending "testing").
> > # Depends on unmaintained dev-python/bsddb3.
> > # Removal on 2024-02-23.  Bug #897136.
> > net-nds/nsscache
> Infra needs this; upstream was AWOL for a long time, but I see they have
> released 0.48/0.49 that contain much needed fixes.
> 
> I'll verify 0.49's behavior (0.47 was broken for Infra's use case).

Then Infra needs to start using their commits access to actively
maintain their packages rather than ignoring them until they are last-
rited once again because of months of complete negligence.  Or move them
to their overlay where that can rot peacefully without bothering others.

-- 
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-01-25 11:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24 11:55 [gentoo-dev] Last rites: net-nds/nsscache Michał Górny
2024-01-25  7:40 ` [gentoo-dev] Re: [gentoo-dev-announce] " Robin H. Johnson
2024-01-25 11:32   ` Michał Górny [this message]

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=274e14c990c0a42b42a4ba43270a38b8ef8f78ab.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