Hmm, that's strange, because I thought multilib was forced in the default 2005.0 profile, so putting USE=multilib would have no effect?




On 16/04/2005, at 4:26 AM, Tres Melton wrote:

Duncan,

        After thumbing through a notebook I was keeping through this process I
have a confession to make.  My x86 profile was the one that became
marked deprecated (I don't recall the version) and not the 2004.3 on my
AMD64 system.

The problem that I had with moving from 2004.3 to 2005.0 on the AMD64
system was that I had included multilib in the 2004.3 system and that
caused it to blow when trying to upgrade. The solution (partly from
memory and partly from notes) was to backout to 2004.3, remove the
additional multilib stuff, "emerge -avDut --newuse world" (long time
here), and then perform the 2004.3 to 2005.0 migration, add multilib to
my USE flags, and then "emerge -avDut --newuse" with the 2005.0 profile
(another long time). After the above steps and some minor house keeping
I got a stable system back.


        The only problem that I have now is that "revdep-rebuild" re-emerges
openoffice-bin everytime I run it.  "revdep-rebuild" says that I can
rerun it at completion to ensure that everything was properly repaired
at which time it promptly re-emerges openoffice-bin.  Oh well,
everything else seems to be pretty stable.  The only exception to this
is the e17 stuff but that is in the area of me "getting to keep the
pieces" so I can't complain there.

I feel the need to apologize for not researching my statements properly
prior to posting. Again, thanks for your insight into AMD64 + multilib
and sorry for any confusion I caused.


(further comments in excerpt below)

On Thu, 2005-04-14 at 22:20 -0700, Duncan wrote:
Tres Melton posted <[EMAIL PROTECTED]>, excerpted
below, on Thu, 14 Apr 2005 09:06:03 -0600:


...
That's an unfortunate possibility. =8^( However, my reply was in the
context of someone asking if he should give up, which implies his system
isn't /that/ broken currently, or he'd not be asking. If the option
continues to exist, I was simply saying there was no further issue in
delaying until later -- until that deprecated warning appears.


My system was functional at the midway point but emerge wasn't. I could
use it but I couldn't change/adjust any packages. I am a firm Gentoo
convert because of the portage system. Redhat, Mandrake, and even
Debian seem to work for a while after first installing but they all
start to deteriorate as time elapses. Soon enough I couldn't install
any new software and my system was pretty much stagnated. Gentoo, and
more importantly, portage, fixes all of this and everything seems to
continue staying up to date. If I sync daily, weekly, or not for a
couple of months, emerge always brings everything up to date. THAT is
the main reason that I am a Gentoo convert. (That and the ability to
manually manage any package that I see fit with "emerge --inject" or
package.provided now).


--
Tres

--
[email protected] mailing list


-- [email protected] mailing list



Reply via email to