Immediately after "emerge rsync" was complete I entered "emerge kde". Processing occurred for awhile following which the job aborted with the message "IoError: [Errno2] No such file of directory: '/usr/portage/distfiles/ftdocs-2.1.2.tar.bz2'"
ftdocs is part of media-libs/freetype. do you have doc in your USE? please try an emerge sync and emerge kde.
Additional data from the submitter of this bug (he send a mail to kde@gentoo.org): (1) The correct version of Gentoo is 1.1a--sorry, I was in Win2K when I sent the bug report. (2) The original bug that I submitted seems to have been due to a problem on the mirror site (can't tell you which one, I didn't make a note). I decided to redo the whole thing to make sure that it wasn't my error, so I did another "emerge rsync" then "emerge kde". In fact, I did the "emerge kde" three times, each time going to a different mirror, and got the same error each time (a different one than on the bug submission), which was: "UnboundLocalError: Local variable 'cfgfiledict' referenced before assignment". I didn't take careful notes, but it seemed to me that this error occurred in different places in the script each time, although it appears to be implausible.
please post the full output of the failure.
Created attachment 5407 [details] Log file from 'emerge kde > kde.log 2>&1' (My version of Gentoo is actually 1.1a.) I was attempting to upgrade kde. The bombout occurs in a different place each time, sometimes taking a couple of hours to be reached. Whenever the emerge runs for a long time, the existing version of kde gets broken--symptom is a thousandfold (or so) increase in time taken to process commands. (In the latter case I have to restore the system with DriveImage.)
which portage version do you have? emerge --version should show it, if it is before portage-2.0.43, please update to 2.0.43.
Created attachment 5409 [details] Log file from 'emerge kde > kde.log 2>&1' (I am trying to upgrade kde.) I was successful in upgrading to Portage 2.0.43, following which I attempted to emerge kde. The emerge bombed but in a different way (in a way which, however, had happened previously prior to the Portage upgrade). The log attachment shows what happened.
Created attachment 5412 [details] Log file from 'emerge gnome > gnome.log 2>&1' This bug probably is not specific to kde since I have now experienced the same result in attempting to emerge gnome, metacity, and xfree (see attachment for the gnome emerge log). The only emerge in this series which worked propertly was that for portage.
carpaski: please take a look at the second and third attachment, it is an emerge error (with traceback).
please do the following: login as root cd /usr/portage/distfiles wget http://www.ibiblio.org/gentoo/distfiles/ftdocs-2.1.2.tar.bz2 emerge kde (or what you want to merge).
Created attachment 5741 [details] Log file from 'emerge portage > portage.log 2>&1' As per request from hannes@gentoo.org I logged in as root and executed the following commands: emerge rsync # seemed to work okay cd /usr/portage/distfiles wget http://www.ibiblio.org/gentoo/distfiles/ftdocs-2.1.2.tar.bz2 emerge portage (I had restored the system from an image and had not done an emerge to get the latest portage, which was necessary before trying to emerge kde.) The attached log shows the result, which incidentally was the same result obtained before doing the wget.
no activity since 5 months
