From: "Jorge Manuel B. S. Vicetto" <jmbsvicetto@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] I need generic solution to package non-building uder catalyst...
Date: Thu, 9 Jan 2014 02:56:32 +0000 (UTC) [thread overview]
Message-ID: <alpine.LNX.2.00.1401090252120.3080@woodpecker.gentoo.org> (raw)
In-Reply-To: <20140108193004.24874.qmail@stuge.se>
On Wed, 8 Jan 2014, Peter Stuge wrote:
> lin pro wrote:
>> This time it is about help2man requiring Locale_gettext pearl
>> module package.
>> The message in itself is very simple and clear. There is no
>> dev-utils/Locale_gettex available for emerge durring the configure
>> phase.
>
> At first that might seem like a bug in the help2man ebuild.
>
> However,
>
> RDEPEND="dev-lang/perl
> elibc_glibc? ( nls? (
> dev-perl/Locale-gettext
> ) )"
>
> ..the dependency looks fine, meaning that dev-perl/Locale-gettext
> is in fact installed on your system.
>
> The problem may be that perl has been upgraded, perhaps as a result
> of using a newer portage tree for the stage4 than the stage3 was
> built with, but perl modules haven't been upgraded to be availble in
> the new version of perl.
My first impression is the same. You likely need to update / redo your
stage3 so that your perl applications are built for the same perl version
that stage4 is picking up.
> Either chroot into the stage4 temp dir as already described, or hack
> the catalyst stage4-chroot.sh script to run perl-cleaner --all right
> after run_merge -uav system.
>
>
>> My question is hwo to tacke those problems from within catalyst.
>
> Avoid the problem by building a full set of stage1, stage2, stage3
> and stage4 using only one specific portage tree.
From my experience building and debugging catalyst builds, the hardest
part is getting a working spec. When you have a spec that builds, you just
need to check packages that fail to build to see if they have become
broken or check here (or even better #gentoo-releng) to see if there were
any changes to the tree that break catalyst or stage building.
> //Peter
Regards,
Jorge Manuel B. S. Vicetto
prev parent reply other threads:[~2014-01-09 2:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 0:57 [gentoo-catalyst] I need generic solution to package non-building uder catalyst lin pro
2014-01-08 1:09 ` [gentoo-catalyst] " W. Trevor King
2014-01-08 17:51 ` lin pro
2014-01-08 17:59 ` W. Trevor King
2014-01-08 19:30 ` [gentoo-catalyst] " Peter Stuge
2014-01-09 2:56 ` Jorge Manuel B. S. Vicetto [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=alpine.LNX.2.00.1401090252120.3080@woodpecker.gentoo.org \
--to=jmbsvicetto@gentoo.org \
--cc=gentoo-catalyst@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