Profiles, and the 2004.3->2005.0 Upgrade

eradicator

With the release of 2005.1 on the horizon, we are getting ready to mark the 2004.3 profile deprecated. This won't happen until after the 2005.1 release, but we're making sure the upgrade path is rock solid, so things go smoothly.

For 2005.0 users, the differences between 2005.0 and 2005.1 are extremely subtle, and if you're keeping your packages up to date, you won't notice any change at all between the two for an installed system.

2004.3 users will need to follow the 2005.0 Upgrade Guide to update their system to 2005.0/2005.1. The guide is titled 2005.0 since 2005.1 isn't released yet, but once 2005.1 is released, the process will be nearly identical (the only change is between using the 2005.0 and 2005.1 directory). This upgrade guide and the associated script have gone through many revisions and bugfixes, so many thanks go out to the users who have helped us refine them over the past months. I am very grateful for your help and patience, and the result will hopefully be a smooth upgrade process for everyone else once 2004.3 is finally deprecated.

Near the bottom of the upgrade guide, we list common problems and solutions users have had with the upgrade. Most of these problems are now correctly handled and avoided by the script, but they are left there for your information in the event you encounter something similar.

I would like to get some feedback from users still on 2004.3 who have upgraded recently or since this posting. Please report "works for me" or any problems you have as a reply to this thread.

Thanks.
_________________
Gentoo Developer: amd64, sparc, sound, toolchain, accessibility

Vespira · n00b Joined: 20 Feb 2005 Posts: 33 Location: Arizona, USA

posting a followup, per your request

i was upgrading from 2004.3 to 2005.1 per your instructions, and once i got to emerging glibc, it blew up >.<

this is the last snippet of info i received...

eradicator · Posted: Tue Aug 09, 2005 1:55 am Post subject:

Ok, thanks for the note. The actual problem is that you've got emul-glibc-2.3.5 which has linuxthreads-tls per default. Now you're emerging 2.3.5-r1 with USE=-linuxthreads-tls and that's confusing the linker.

Another solution is to re-emerge the currently-installed glibc version rather than the latest glibc, then emerge the latest one when you do your emerge -uv system after the emul libs are removed.

Or you could just use USE=linuxthreads-tls

I've updated the script and the upgrade guide (takes a while to make it to the website) with this information. Thanks.
_________________
Gentoo Developer: amd64, sparc, sound, toolchain, accessibility

eradicator · Posted: Tue Aug 09, 2005 1:59 am Post subject:

Oh... also, if reverting back from 'nptlonly', be careful. If you start getting segfaults, make sure you don't have /lib*/libpthread-2.3.5.so leftover. libpthread-0.10.so is the correct (linuxthreads) one, but for some reason portage sometimes leaves the old one there, but it's usually from very dated (around 2.3.3.XXX) glibcs, so the portage bug which resulted in this problem is most likely fixed. If you do have this problem still, please let me know.
_________________
Gentoo Developer: amd64, sparc, sound, toolchain, accessibility

OldTango · l33t Joined: 21 Feb 2004 Posts: 718

I had numerous problems upgrading to the new profile and even filed a bug report on it. Gcc and glibc constantly sipt out a varity of errors as did emerging sandbox which pointed back to c-compiler. I followed the upgrade guide exactly. I was finnaly able to build sucessfully only after an idea eradicator had about my problem. You suggested I delete my /emul directory and re-emerge my emul-libs. That fixed all my problems and errors completely.

My conclusion from my experience was that even though I had always followed all the gentoo docs, for building, maintaining and updating my amd64 system there are things I can't control or maybe just don't understand how to with my currant Linux knowledge.

Portage either didn't, couldn't or wouldn't update my emul-linux-x86-libs properly during normal day to day updates for my system. Maybe because other apps were still using certian libs located there. My only indication of this is that after every attempt to upgrade any app needing 32bit nvidia libs to run ie..(quake3) wouldn't untill I re-emerged nvidia-kernel and nvidia-glx.

So I think if you have been using 2004.3 for quite a while, have newer versions of glibc and gcc and run a lot of 32bit apps, you may run into some problems upgrading unless the new upgrade script addresses these issues. I don't understand why I had so many upgrading problems, but I did. The only thing that fixed it was deleting the /emul directory and than re-emerging it.

After a sucessful build under the new profile I have done a emerge -e world and 384 packages were re-compiled without error, except 2 which spit out md5 errors which was solved by deleting them in /usr/portage/distfiles, syncing and then re-emerging them.

GOOD LUCK TO ALL.

eradicator · Posted: Fri Aug 12, 2005 9:29 pm Post subject:

linoleum · Tux's lil' helper Joined: 15 Nov 2004 Posts: 129

Hi,
I'm updating from 2004.3 to 2005.0 experiecing some problems very similar to the ones raised above by Vespira. The reply by eradicator was

linoleum · Tux's lil' helper Joined: 15 Nov 2004 Posts: 129

I tried to modify the 2004.3-2005.0upgrade.sh and apparently I was able to implement your suggestion. Here

mystos · Posted: Fri Sep 09, 2005 3:16 am Post subject: multilib on 2005.0?

I went through the gamut of the problems with the early script, the manual
steps and all the forum suggestions. I eventually gave up and tried hard to get
back to a clean and stable 2004.3 profile. I've had little problems since so I think I
was mostly successful. Today I got the message via emerge about the deprecation of
2003.4 and after checking the date of the upgrade script and searching the forums
for problems I decided to try it again.

It immediately got the error about /lib32 and /usr/lib32 dirs; and after a quick look
and seeing only one file and a sym link I simply deleted them and kept going.

It subsequently failed on stage 2 with the error executing 32bit executable msg and no
suitable libc library in the log. That took an hour of digging (I shouldn't have, but I did
this during work;) The problem is similar to the "size of long double" issue, and after hesitating
a bit tried just doing the section under the If using the scripted upgrade:
in the Code Listing 9 box of the upgrade how-to. and kept going.
And miracle of miracles, the nice script finishes with is congratulatory message - cool.

Ok, so fine, the emerge -v system worked with no suggestions, but I immediately tried

eradicator · Posted: Fri Sep 09, 2005 7:30 am Post subject:

eradicator · Posted: Fri Sep 09, 2005 7:40 am Post subject: Re: multilib on 2005.0?

samuel.penn · Posted: Sat Sep 10, 2005 11:20 am Post subject: Script refuses to run

First off, I should probably point out that all my machines perform an automatic "emerge --sync" via cron, so I never normally see the output. The fan in my AMD64 box has been playing up over the last week, so I've been leaving the machine switched off, and I just (for the first time in months) did an emerge --sync by hand, and I now see the following warning (for the first time):

!!! Your current profile is deprecated and not supported anymore.
!!! Please upgrade to the following profile if possible:
default-linux/amd64/2005.0

So, I've no idea if this warning has been given for the past 3 months, or just started today!

If I run the script listed in the document it points to, then I get the same error, plus a pointer to the document which told me to run the script. The full output is:

OldTango · l33t Joined: 21 Feb 2004 Posts: 718

The warnig about /lib32 & /usr/lib32 means that one or both are not symlinks anymore. Under 2004.3 they are symlinks. Find the common problems section in the how to and follow thoes instructions using the scripted method.

samuel.penn · Posted: Sat Sep 10, 2005 1:45 pm Post subject:

OldTango · l33t Joined: 21 Feb 2004 Posts: 718

Yes that is true but following that section will also get the libs where they need to be. If you attempt to upgrade with broken libs you will get all kinds of errors, not just the ones listed.

Many things have changed recently. You most likely are running newer versions of gcc, glibc, binutils and base layout under an older profile which could cause problems upgrading. You may wish to post your emerge info and wait to see if eradicator responds to this post. He knows the problems you can encounter well and may have better advise for you.

samuel.penn · Posted: Sat Sep 10, 2005 2:49 pm Post subject: emerge --info

fenris scripts # emerge --info

!!! Your current profile is deprecated and not supported anymore.
!!! Please upgrade to the following profile if possible:
default-linux/amd64/2005.0

To upgrade do the following steps:

# The 2004.3 profile is now deprecated and subject to removal at any point
# after February 1, 2006. Please update your system to the 2005.0 profile
# by using the upgrade guide located at:
#
# http://amd64.gentoo.org/howtos/index.xml?part=1&chap=1
#
# Do not simply change the symlink.

Portage 2.0.51.19 (default-linux/amd64/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r11 x86_64)
=================================================================
System uname: 2.6.11-gentoo-r11 x86_64 AMD Athlon(tm) 64 Processor 3200+
Gentoo Base System version 1.4.16
Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Mar 27 2005, 20:38:31)]
dev-lang/python: 2.3.4-r1
sys-apps/sandbox: [Not Present]
sys-devel/autoconf: 2.59-r6, 2.13
sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4
sys-devel/binutils: 2.15.92.0.2-r1
sys-devel/libtool: 1.5.10-r4
virtual/os-headers: 2.6.8.1-r4
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CFLAGS="-O2"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr//lib/mozilla/defaults/pref /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d"
CXXFLAGS="-O2"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict"
GENTOO_MIRRORS="ftp://194.117.143.72/mirrors/gentoo http://ftp.easynet.nl/mirror/gentoo/ ftp://194.117.143.69/mirrors/gentoo http://194.117.143.71 ftp://194.117.143.70/mirrors/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://wotan.glendale/gentoo-portage"
USE="amd64 X aalib alsa avi berkdb bitmap-fonts cdparanoia crypt cups curl dvd dvdread eds emboss encode esd fam flac foomaticdb fortran gd gif gimpprint gpm gstreamer gtk gtk2 imagemagick imlib ipv6 jabber java jpeg junit kde ldap lzw lzw-tiff mad motif mozilla mozsvg mp3 mpeg multilib ncurses nls ogg oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl spell ssl svg tcltk tcpd theora tiff truetype truetype-fonts type1-fonts unicode usb userlocales vorbis xine xinerama xml xml2 xmms xpm xv xvid zlib userland_GNU kernel_linux elibc_glibc"
Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS

Trappies · n00b Joined: 15 Mar 2004 Posts: 55

Hi Guys,

I am a still a bit of a noob when it comes to these tecnical details. I tried running the script today and it gave me the same as the above message. But my one gives the following error :

blubb · Posted: Sat Sep 10, 2005 4:04 pm Post subject:

eradicator · Posted: Sat Sep 10, 2005 5:31 pm Post subject:

samuel.penn · Posted: Sat Sep 10, 2005 6:22 pm Post subject: /lib32 etc

I don't believe I have ever tried to manually upgrade to 2005.0. I wouldn't have done it unless I got a message saying to do it (as happened today), or during initial installation (June this year).

eradicator · Posted: Sat Sep 10, 2005 6:54 pm Post subject:

ok samuel... please just emerge 'emul-linux-x86-glibc' and see if that fixes the problem. It should.

Thanks.
_________________
Gentoo Developer: amd64, sparc, sound, toolchain, accessibility

regnnick · n00b Joined: 20 Dec 2003 Posts: 19

Hello,

I've got a similar problem than samuel. I've first tried to update manually but was stuck with the long double problem. So I've tried to reverse what I have done and use the script. But I get the following message

samuel.penn · Posted: Sat Sep 10, 2005 10:26 pm Post subject:

Angryguy · Posted: Sun Sep 11, 2005 12:09 am Post subject:

I'm also trying to upgrade the profile and am having problems.

I followed the directions to execute the sh upgrade script, only to get the message:

OldTango · l33t Joined: 21 Feb 2004 Posts: 718

Angryguy wrote: