public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: <nunojsilva@ist.utl.pt> (Nuno Silva)
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: dev-lang/perl:0
Date: Fri, 30 Jul 2021 16:10:55 +0100	[thread overview]
Message-ID: <se14q0$177l$1@ciao.gmane.io> (raw)
In-Reply-To: cdd3ee5f-4712-eaa5-fd2a-eb68c90632e5@sys-concept.com

On 2021-07-30, thelma@sys-concept.com wrote:

> I'm trying to run an upgrade but I got stuck on perl:
[...]
>   (dev-lang/perl-5.34.0:0/5.34::gentoo, ebuild scheduled for merge) USE="gdbm -berkdb -debug -doc -ithreads -minimal" ABI_X86="(64)" pulled in by
[...]
> Running:  "perl-cleaner --all" gives me:
[...]
>   (dev-lang/perl-5.32.1:0/5.32::gentoo, installed) USE="gdbm -berkdb -debug -doc -ithreads -minimal" ABI_X86="(64)" pulled in by
>     dev-lang/perl:0/5.32= required by (app-text/po4a-0.57:0/0::gentoo, installed) USE="-test" ABI_X86="(64)"
>                  ^^^^^^^^ 

Are you upgrading @world or just dev-lang/perl directly? If it's the
latter, try to upgrade po4a at the same time.

From a quick glance at the po4a ebuild and the perl-module eclass, the
default seems to be a run-time dependency on perl with the same slot and
subslot as the perl present when the package was installed, which would
explain why po4a needs perl:0/5.32.

-- 
Nuno Silva



  parent reply	other threads:[~2021-07-30 15:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30  2:42 [gentoo-user] dev-lang/perl:0 thelma
2021-07-30  2:51 ` thelma
2021-07-30  3:10 ` thelma
2021-07-30  3:20   ` thelma
2021-07-30  8:20     ` John Covici
2021-07-30  8:57       ` Michael
2021-07-30 11:08 ` Michael Orlitzky
2021-07-30 20:50   ` Michael Orlitzky
2021-07-31  6:32     ` William Kenworthy
2021-07-31 16:04       ` thelma
2021-07-30 15:10 ` Nuno Silva [this message]
2021-07-30 16:08   ` [gentoo-user] dev-lang/perl:0 Nuno Silva

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='se14q0$177l$1@ciao.gmane.io' \
    --to=nunojsilva@ist.utl.pt \
    --cc=gentoo-user@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