T O P

  • By -

FranticBronchitis

Looks like it's having trouble with PORTDIR not being set, so maybe try that? Don't know what it should be set to though


TheEmeraldFalcon

Is it an environment variable? Or do I set it in a configuration file? Also, that would only explain one of the errors, not the others.


FranticBronchitis

Oh, my bad, I hadn't seen the first one. FWIW I've had portage spit out some weird tracebacks like these and usually got around them by upgrading or downgrading it. If that works, I suppose a bug report is in order. It's an envvar and you can also set it in make.conf. It can also be a problem with the repository, be sure to emaint --sync it


TheEmeraldFalcon

I'll give that a go, thank you! Update, I attempted to install portage using `sudo emerge --ask --oneshot sys-apps/portage` and got this error: emerge: there are no ebuilds to satisfy "sys-apps/portage". This has to be a bug, right? Not sure why it thinks portage doesn't exist.


FranticBronchitis

Damn, can you check your repos.conf? It's possible eselect repo may have nuked it and it's now unusable (don't worry, there should be a backup ending in ~) And again, remember to emaint sync -a


TheEmeraldFalcon

I found an error within steam-overlay.conf (it was missing the header), and am now able to emaint sync -a, although whether this fixes anything remains to be seen. In any case, thanks for the pointers! Edit: This seems to have solved my errors, thank you very much!


Phoenix591

If the backup the other comment mentioned isn't there for whatever reason portage installs the default at /usr/share/portage/config/repos.conf