[gentoo-catalyst] Little help building stage3 (Can't locate Tie/Hash.pm building autoconf-2.65-r1)

[gentoo-catalyst] Little help building stage3 (Can't locate Tie/Hash.pm building autoconf-2.65-r1)

[Daniel van Ham Colchete]

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

Hey people,

a little bit more than two years ago I built a catalyst-based stage4 for a
server cluster and have been able to manage everything and upgrade
everything in an very automated way and very organized way, thanks to
Catalyst (and cfengine). Every time I want to upgrade my system I just
create another stage4 based of the last one, but with a newer snapshot, get
the binary packages from the cache and upgrade my cluster with them. Even
kernel upgrades goes nicely with the right scripts.

A lot have changed since July 2008 in Gentoo, some of the changes made it
difficult to maintain the upgrade cycle of my old stage4 and I had to start
over, make a new stage4 and reinstall everything. It is good to have a fresh
start anyway.

My problem is that I`m not able to build a stage3 because of a problem
emerging autoconf-2.65-r1.

This is useful info: http://pastebin.com/YjddiQwh
And this is the build log: http://pastebin.com/Em8fyRyT
This is my stage 1, 2 and 3 files: http://pastebin.com/bkcuGaP7

Tie/Hash.pm is available on my old Perl 5.8.8 installation but it doesn't
appear to be on Perl 5.12.2. So, when building a new stage3 Perl 5.8.8 is
not getting there and I think this is the cause of the problem. I think it
is very easy to reproduce the problem.

The stage1 build failed as well, but when I did a catalyst -a -f stage1.spec
after the failure, the build finished correctly, so I didn`t want to search
for the root cause.

Thank you very much for any help.

Best regards,
Daniel Colchete

[-- Attachment #2: Type: text/html, Size: 1729 bytes --]

Re: [gentoo-catalyst] Little help building stage3 (Can't locate Tie/Hash.pm building autoconf-2.65-r1)

[Peter Stuge]

Daniel van Ham Colchete wrote:
> And this is the build log: http://pastebin.com/Em8fyRyT
> This is my stage 1, 2 and 3 files: http://pastebin.com/bkcuGaP7

Which version of perl is in the 20101019 stage3?


> Tie/Hash.pm is available on my old Perl 5.8.8 installation but it
> doesn't appear to be on Perl 5.12.2.

I've done similar as you, but I tried to take a shortcut and build
stage4 directly from today's stage3.

For the most psrt it works fine, but especially with perl modules
there's a twist.

Portage doesn't know which version of perl that the installed modules
were built against, and even if a module was built against an older
perl, the dependency on that module is still satisfied, even if perl
has been upgraded so that the module cannot be found.

This happened to me when today's stage3 had one version of perl, and
a newer one was in my stage4.

Rather than doing the correct thing and build my own stage3 like you,
I just hacked around it by calling perl-cleaner --allmodules in
/usr/lib64/catalyst/targets/stage4/stage4-chroot.sh which is kinda
ugly but does work.


> So, when building a new stage3 Perl 5.8.8 is not getting there and
> I think this is the cause of the problem.

Again, which version is in your stage3?


> The stage1 build failed as well, but when I did a
> catalyst -a -f stage1.spec after the failure, the build finished
> correctly, so I didn`t want to search for the root cause.

Leaving unexplained errors is always risky, and can definately come
back to bite you later. Do you at least recall how it failed? If it
was related to perl then this might still be the same problem, but I
don't know if perl is at all involved in stage1.


//Peter

Re: [gentoo-catalyst] Little help building stage3 (Can't locate Tie/Hash.pm building autoconf-2.65-r1)

[Graham Murray]

Peter Stuge <peter@stuge.se> writes:

> Leaving unexplained errors is always risky, and can definately come
> back to bite you later. Do you at least recall how it failed? If it
> was related to perl then this might still be the same problem, but I
> don't know if perl is at all involved in stage1.

I had this failure building autoconf during a stage 1 build. The stage3
I was using as a seed was using perl-5.8.8, but the stage1 had already
built perl-5.12.2. I did not try continuing.

Re: [gentoo-catalyst] Little help building stage3 (Can't locate Tie/Hash.pm building autoconf-2.65-r1)

[Daniel van Ham Colchete]

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

On Tue, Oct 26, 2010 at 2:11 PM, Peter Stuge <peter@stuge.se> wrote:

> Daniel van Ham Colchete wrote:
> > And this is the build log: http://pastebin.com/Em8fyRyT
> > This is my stage 1, 2 and 3 files: http://pastebin.com/bkcuGaP7
>
> Which version of perl is in the 20101019 stage3?
>
> 5.8.8


>
> > Tie/Hash.pm is available on my old Perl 5.8.8 installation but it
> > doesn't appear to be on Perl 5.12.2.
>
> I've done similar as you, but I tried to take a shortcut and build
> stage4 directly from today's stage3.
>
> For the most psrt it works fine, but especially with perl modules
> there's a twist.
>
> Portage doesn't know which version of perl that the installed modules
> were built against, and even if a module was built against an older
> perl, the dependency on that module is still satisfied, even if perl
> has been upgraded so that the module cannot be found.
>
> This happened to me when today's stage3 had one version of perl, and
> a newer one was in my stage4.
>
> Rather than doing the correct thing and build my own stage3 like you,
> I just hacked around it by calling perl-cleaner --allmodules in
> /usr/lib64/catalyst/targets/stage4/stage4-chroot.sh which is kinda
> ugly but does work.
>

The problem is that Tie/Hash.pm is a built in module. When the stage1
installs Perl 5.12.2 the Tie/Hash.pm is not going to /usr/lib/perl/5.12.2
even though Perl 5.8.8 is not installed on /tmp/stage1root. I`m pretty much
sure this is a bug with the recently stabilized new Perl 5.12.2 ebuild.



>
>
> > So, when building a new stage3 Perl 5.8.8 is not getting there and
> > I think this is the cause of the problem.
>
> Again, which version is in your stage3?
>
>
> > The stage1 build failed as well, but when I did a
> > catalyst -a -f stage1.spec after the failure, the build finished
> > correctly, so I didn`t want to search for the root cause.
>
> Leaving unexplained errors is always risky, and can definately come
> back to bite you later. Do you at least recall how it failed? If it
> was related to perl then this might still be the same problem, but I
> don't know if perl is at all involved in stage1.
>
>
> //Peter
>
>
I solved the problem using the 20101019 portage snapshot. The guys at releng
still didn`t release Tuesday`s stage3 for this week and I think it was
because of the same problem.

I think the weekly builds are a very good way to improve system packages
stability on Portage, but I`m also getting some other problems with
non-system packages. Examples:

 * ipvsadm doesn`t build with the stable gentoo-source because the directory
include/asm changed to include/asm-generic on the kernel`s source. Solution
one: create a link. Solution two: patch. I went with #1.
 * sys-cluster/heartbeat-2.0.7-r2 doesn`t compile using the latest GCC/Glib
pair. I`m not sure witch one is the root cause. Quick solution: go for
sys-cluster/heartbeat-2.0.8 (~x86).

So, my suggestion is that the QA guys build a few stage4 stages (KDE, Gnome,
mail server, web server, file server, db server) weekly internally to
monitor for inconsistencies on the non-system part of Portage and file the
bugs everytime there is one. This way the probability of a user getting into
problems before QA is reduced.

Another sugestion: have any stabilizing package a 48 hour delay so that the
stage4 could be tested in advance. Or give a 48 hour delay for the entire
official portage tree, make QA tests daily on the live one and minimize the
risks this way also.

Thanks for the help.

Best,
Daniel van Ham Colchete

[-- Attachment #2: Type: text/html, Size: 4600 bytes --]

Re: [gentoo-catalyst] Little help building stage3 (Can't locate Tie/Hash.pm building autoconf-2.65-r1)

[Peter Stuge]

Daniel van Ham Colchete wrote:
> > I just hacked around it by calling perl-cleaner --allmodules in
> > /usr/lib64/catalyst/targets/stage4/stage4-chroot.sh which is kinda
> > ugly but does work.
> 
> The problem is that Tie/Hash.pm is a built in module.

Ah. Then the hack would be to re-emerge perl instead of running
perl-cleaner.


> When the stage1 installs Perl 5.12.2 the Tie/Hash.pm is not going
> to /usr/lib/perl/5.12.2 even though Perl 5.8.8 is not installed on
> /tmp/stage1root. I`m pretty much sure this is a bug with the
> /recently stabilized new Perl 5.12.2 ebuild.

Weird problem. I jumped from 5.8.8 (seed stage3) to 5.12.1 (my stage4)
and that worked out well;

$ qfile Hash.pm
dev-lang/perl (/usr/lib/perl5/5.12.1/Tie/Hash.pm)


//Peter