public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites: dev-php/pear and friends
Date: Tue, 11 Jun 2024 15:48:21 -0400	[thread overview]
Message-ID: <48960ae13af2c21cdaf2ba0123df4cd1e8af1331.camel@gentoo.org> (raw)
In-Reply-To: <5c08d480-5eae-4193-bc12-ad3d967425ef@gentoo.org>

On Tue, 2024-06-11 at 14:56 +0300, Arthur Zamarin wrote:
> 
> Sounds good to me, then please make sure all that dependency tree needed
> for those targets are EAPI bumped, and most QA warnings from pkgcheck
> are handled. Currently those packages look unmaintained.
> 
> When you (or anyone else) handle those, we can un-last-rite that dep tree.

Several of the open bugs were bogus or obsolete, but there were a few
test failures and version bumps to deal with.

dev-php/PEAR-Net_SMTP: add 1.12.1
dev-php/PEAR-Net_Sieve: add 1.4.7
dev-php/PEAR-PEAR: add 1.10.15
dev-php/PEAR-PEAR: drop 1.10.12
dev-php/PEAR-Archive_Tar: add 1.5.0
dev-php/PEAR-Structures_Graph: add 1.2.0
dev-php/PEAR-Mail_Mime: add 1.10.12
dev-php/PEAR-Console_CommandLine: test deps should be BDEPEND in EAPI=8
dev-php/PEAR-Auth_SASL: add 1.2.0
dev-php/PEAR-Console_CommandLine: add 1.2.6
dev-php/PEAR-Crypt_GPG: add 1.6.9
dev-php/PEAR-Console_Table: update EAPI 7 -> 8

Anything else, let me know.




  reply	other threads:[~2024-06-11 19:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11  4:11 [gentoo-dev] Last rites: dev-php/pear and friends Viorel Munteanu
2024-06-11 11:54 ` Michael Orlitzky
2024-06-11 11:56   ` Arthur Zamarin
2024-06-11 19:48     ` Michael Orlitzky [this message]
2024-06-12  5:57       ` Viorel Munteanu
2024-06-12 10:30         ` Michael Orlitzky

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=48960ae13af2c21cdaf2ba0123df4cd1e8af1331.camel@gentoo.org \
    --to=mjo@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