Lost my make.defaults after emerge --sync (SOLVED)

[Varsuuk]

I haven't updated my laptop in ages.

Last night I ran emerge --sync

then

emerge portage

which failed due to not having my profile set.

I used to point to default-linux/x86/2005.0

Is there any way I can find out the old values I had set there that I might need? In particular - I suspect I very MUCH need the old
USE = "......." line if my updates are going to work correctly?

I have the old RCS dispatch-conf thing setup - is there any chance that dir/file is recoverable - I am guessing not since it appears to have gone during emerge --sync not emerging a product...

Please any tips respond asap (or if can and that's a choice - email me via this forum - not sure if it does that)

[Katphish]

hehe, I hit this with an old workstation just two nights ago.

/etc/make.conf is still around for your local edits. The profile is unsupported so you might as well upgrade a 2006.x one. The desktop subdirectory is pretty nice.

Code: Select all

cd /etc
rm make.profile
ln -s ../usr/portage/profiles/default-linux/x86/2006.1/desktop make.profile

[lngndvs]

This bit me as well, on an amd64. I had not updated this system in a long time, and found that I had a make.profile pointing to a non-existent /usr/portage/profiles//default-linux/amd-64/2005.1 .

I tried editing the link as you suggested, without success. I still get the same message, when using emerge:

Littlebird etc # emerge --sync
>>> cfg-update-1.8.0-r3 : No new packages have been emerged, checksum index OK...
Traceback (most recent call last):
File "/usr/bin/emerge", line 4391, in ?
retval = emerge_main()
File "/usr/bin/emerge", line 4100, in emerge_main
settings, trees, mtimedb = load_emerge_config()
File "/usr/bin/emerge", line 4011, in load_emerge_config
trees = portage.create_trees(trees=trees, **kwargs)
File "/usr/lib/portage/pym/portage.py", line 7122, in create_trees
config_incrementals=portage_const.INCREMENTALS)
File "/usr/lib/portage/pym/portage.py", line 1057, in __init__
for k, v in rawprofileuse.iteritems():
AttributeError: 'NoneType' object has no attribute 'iteritems'

I noted that the OP had posted within 24 hours of me. I found nothing on bugzilla, but will now recheck.

Thank you for any ideas.

Alan Davis

[i92guboj]

I haven't updated my laptop in ages.

Last night I ran emerge --sync

then

emerge portage

which failed due to not having my profile set.

I used to point to default-linux/x86/2005.0

Is there any way I can find out the old values I had set there that I might need? In particular - I suspect I very MUCH need the old
USE = "......." line if my updates are going to work correctly?

First, when you sync ALL things under ${PORTDIR} can be overwritten, erased, toasted, killed, etc. etc... That is not a good place to put custom settings at all. That is one of the reasons why some of us think that portage should reside in /var, but that is another story.

The 2005 profiles have been deprecated (we are now in 2007), so, you would do better migrating to something like 2006.1 or so. You don't need the old make.defaults, since each new profile do have a proper set. You can put custom settings in /etc/make.conf. There is where all your custom cflags, use flags, portage variables and such should reside. That file will not be overwritten. About your old use flags... sorry, but if they where in a make.defaults into /usr/portage, it has been probably erased. A way to try to rebuild your old set of use flags is to emerge -puDvN world and see what is changing with your use flags, then add the correct ones manyally into make.conf.

I have the old RCS dispatch-conf thing setup - is there any chance that dir/file is recoverable - I am guessing not since it appears to have gone during emerge --sync not emerging a product...

I just use the stardard etc-update, so I cant tell for sure, but I really don't think that dispatch-conf does any backup at all of the stuff into /etc/portage... That is supposed to be volatile stuff, so there is no need to do such backups.

Bear in mind that between major releases use flags gets removed or added, there is nothing wrong with that. If you don't know what a specific use flag does, you are better leaving it alone. You can always change it at a later stage and recompile the needed package(s).

EDIT, oh, almost forgot, you first need to creaty the profile symlink. Do it manually, since on an old install you might not have "eselect profile". Just rm /etc/make.profile and then ln -s /usr/portage/profiles/default-linux/amd64/2006.1/desktop/ /etc/make.profile. That is for amd64, you might need any other.

[Varsuuk]

THANKS so much guys for the fast response!

Yea, I just hadn't used it in soooo long (no real 'personal projects/coding time' and at work we use RHEL I hate not having the newer better versions of things like KDevelop) time. Turns out I just brain froze - no, I never modified my USE flags there. I just looked in the new 2006.x dirs and saw THEY had USE flags and I ASSumed... so ya, my changes are in /etc/make.conf and still there.

I even forgot my forums account name/pw - unless it went inactive (Sigurd or DanDelgado, I believe)

The ln to the 2007.1 setup allowed me to start updating.

---Dan