I use ~x86 History. I have updated the system yesterday. Today, after rebooting I have noticed many small errors in my system, for example: - /etc/modules.autoload.d/kernel-2.6 has not my additions - /etc/conf.d/local.start has not my additions - /etc/conf.d/domainname is without my modification - /etc/conf.d/hostname is without my modification Probably something else :-( I have decided to re-sync my system. Syncing ended with the error shown below (new portage files were received). Any further emerge attempt to sync begins and ends with this error too. ... File "/usr/bin/emerge", line 10, in ? import portage File "/usr/lib/portage/pym/portage.py", line 7353, in ? do_upgrade(mykey) File "/usr/lib/portage/pym/portage.py", line 7246, in do_upgrade db["/"]["bintree"].move_ent(mysplit) File "/usr/lib/portage/pym/portage.py", line 5697, in move_ent catfile.write(mynewcat+"\n") NameError: global name 'mynewcat' is not defined Reproducible: Always Steps to Reproduce:
/etc/conf.d/clock was also returned to initial state.
Post emerge --info output.
As I have said, emerge using causes this error (full output is shown below). Why the issue status was changed to RESOLVED NEEDINFO? //////////////////////////// emerge --info Performing Global Updates: /usr/portage/profiles/updates/2Q-2005 (Could take a couple of minutes if you have a lot of binary packages.) .='update pass' *='binary update' @='/var/db move' s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*' .!!! Invalid binary package: porthole-0.4.1.tbz2 ..........................%Traceback (most recent call last): File "/usr/bin/emerge", line 10, in ? import portage File "/usr/lib/portage/pym/portage.py", line 7353, in ? do_upgrade(mykey) File "/usr/lib/portage/pym/portage.py", line 7246, in do_upgrade db["/"]["bintree"].move_ent(mysplit) File "/usr/lib/portage/pym/portage.py", line 5697, in move_ent catfile.write(mynewcat+"\n") NameError: global name 'mynewcat' is not defined
Comment #3: No, you said that emerge sync causes problems, not that any use of emerge causes traceback. Anyway, exact portage version is really important, are you using 2.0.51.20-r?
sys-apps/portage-2.0.51.20-r4 is in use (was determined with qpkg :-)
Created attachment 57171 [details, diff] One line fix Will do -r5 in a day or two.
Jason, Thanks! emerge seems to work now. Does found bug explain a silent overwriting of user's config files? Which other side-effects must I look for?
The config file issue was due to not adding the appropriate variables to the profiles. If you synced and portage-2.0.51-r4 was available, the issue was gone - even before you upgraded.
I have not synced and upgraded now - just added a line to portage.py file. I'm going to wait for r5.
This seems better in -r5, but I still get this error when running fixpackages. Several quaters of updates seem to work fine until we get to this error below; Performing Global Updates: /usr/portage/profiles/updates/1Q-2003 (Could take a couple of minutes if you have a lot of binary packages.) .='update pass' *='binary update' @='/var/db move' s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*' ......................@%Traceback (most recent call last): File "/usr/sbin/fixpackages", line 10, in ? import portage File "/usr/lib/portage/pym/portage.py", line 7353, in ? do_upgrade(mykey) File "/usr/lib/portage/pym/portage.py", line 7246, in do_upgrade db["/"]["bintree"].move_ent(mysplit) File "/usr/lib/portage/pym/portage.py", line 5697, in move_ent catfile.write(mynewcat+"\n") NameError: global name 'mynewcat' is not defined
Are you 100% sure that traceback came while running -r5? I can't see how it is possible...
Yes, it is definitely -r5. I specifically upgraded to it to see if this problem was resolved.
Can you attach portage.py please? I really can't see how it's possible with the code that I'm looking at.
it appears to have been related to how I copied the new ebuild of portage from one host to another. Sorry for the noise.
Fixed on or before 2.0.51.22-r1
Looking through the batch of bugs, I'm not sure that some of these are actually fixed in stable. Others, the requirements have possibly changed after the initial fix was committed. If you think this bug has been closed incorrectly, please reopen or ask that it be reopened.
