On Sat, 2005-12-03 at 21:38 -0400, Luis F. Araujo wrote:
> Matthias Langer wrote:
>
> >On Sat, 2005-12-03 at 14:04 -0700, Joshua Baergen wrote:
> >
> >
> >>Matthias Langer wrote:
> >>
> >>
> >>>2.) emerge -e world on a system with lot of packages will most likley
> >>>fail somewhere during t
Matthias Langer wrote:
On Sat, 2005-12-03 at 14:04 -0700, Joshua Baergen wrote:
Matthias Langer wrote:
2.) emerge -e world on a system with lot of packages will most likley
fail somewhere during the process for various reasons. Fixig the problem
(for example by unmerging the package wh
Matthias Langer wrote:
On Sat, 2005-12-03 at 21:31 +0100, Jan Kundrát wrote:
On Saturday 03 of December 2005 21:26 Matthias Langer wrote:
1.) If you remove gcc-3.3* before emerge -e system you will be left
behind with a broken python and therefore emerge. Thus i think there
should be a
On Sat, 2005-12-03 at 14:04 -0700, Joshua Baergen wrote:
> Matthias Langer wrote:
> > 2.) emerge -e world on a system with lot of packages will most likley
> > fail somewhere during the process for various reasons. Fixig the problem
> > (for example by unmerging the package which causes it) and res
On Sat, 2005-12-03 at 21:31 +0100, Jan Kundrát wrote:
> On Saturday 03 of December 2005 21:26 Matthias Langer wrote:
> > 1.) If you remove gcc-3.3* before emerge -e system you will be left
> > behind with a broken python and therefore emerge. Thus i think there
> > should be a big red box telling u
Matthias Langer wrote:
2.) emerge -e world on a system with lot of packages will most likley
fail somewhere during the process for various reasons. Fixig the problem
(for example by unmerging the package which causes it) and restarting
the process is not an option, as this may cost you lot's of t
Matthias Langer wrote:
2.) emerge -e world on a system with lot of packages will most likley
fail somewhere during the process for various reasons. Fixig the problem
(for example by unmerging the package which causes it) and restarting
the process is not an option, as this may cost you lot's of t
On Saturday 03 of December 2005 21:26 Matthias Langer wrote:
> 1.) If you remove gcc-3.3* before emerge -e system you will be left
> behind with a broken python and therefore emerge. Thus i think there
> should be a big red box telling users about this.
Our guide says that you have to either run `
Well done, i've allready switched completely to gcc-3.4 with my main box
by reemerging about 650 packages. However, i allready started doing so a
few days ago, so I didn't read the official migration guide before
starting. Now, as everything works fine i just read this guide to
compair it with my o
