From: "David M. Fellows" <fellows@unb.ca>
To: <gentoo-user@lists.gentoo.org>, Francisco Ares <frares@gmail.com>
Subject: Re: [gentoo-user] missing dependencies
Date: Wed, 26 Feb 2014 07:54:39 -0400 [thread overview]
Message-ID: <30c29c92-afd6-4aa5-9ac0-e8dafd707a23@BL2PRD0411HT003.namprd04.prod.outlook.com> (raw)
In-Reply-To: <CAHH9eM6o8zOivJV7but=0QHwhyvkSemrWusca9MjSAQd-rDfhw@mail.gmail.com>
On Wed, 26 Feb 2014 08:12:35 -0300
Francisco Ares wrote -
> --001a113311e686e7f304f34d4a39
> Content-Type: text/plain; charset="UTF-8"
>
> Hi All,
>
> It has been for a while, now: every now and then, when updating a perl
> module, it fails to emerge. Checking the log, it is possible to see
> something like this, when I tied to update dev-perl/File-MimeInfo :
>
> ...
> Checking prerequisites...
> requires:
> ! File::BaseDir is not installed
> ! File::DesktopEntry is not installed
> ...
>
> Then I checked to see, and both dev-perl/File-BaseDir and
> dev-perl/File-DesktopEntry are really not installed and are not requested
> for the dev-perl/File-MimeInfo update.
>
> At first I thought it was a one and only case. But as time goes by, there
> has been perl packages that refuse to emerge at first, and then, checking
> the emerge log, finding missing modules and manually emerging them,
> everything goes as it should.
>
> Does anyone have a clue on where did I miss them?
You need to run perl-cleaner to rebuild perl modules after a perl update.
emerge perl-cleaner if neecessary
perl-cleaner --all -p
to check
and perl-cleaner --all
do do the work.
Dave F
next prev parent reply other threads:[~2014-02-26 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 11:12 [gentoo-user] missing dependencies Francisco Ares
2014-02-26 11:54 ` Neil Bothwick
2014-02-26 12:29 ` Francisco Ares
2014-02-26 11:54 ` David M. Fellows [this message]
2014-02-26 12:30 ` Francisco Ares
2014-02-26 12:58 ` Francisco Ares
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=30c29c92-afd6-4aa5-9ac0-e8dafd707a23@BL2PRD0411HT003.namprd04.prod.outlook.com \
--to=fellows@unb.ca \
--cc=frares@gmail.com \
--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