you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 1 year ago (5 children)

How did you do that? (Both "that"s I guess!)

  • source
  • parent
  • hideshow 5 child comments
  • [–] 2 points 1 year ago* (2 children)

    I found out there were binary packages that were build together and manually downloaded and unpacked every package I needed for a minimum coherent build chain (no kernel but gcc, gnuutils etc) and used that to get emerge working again to build a new build chain with my own settings and used that to rebuild system to get rid of the foreign packages and be back. The gentoo wiki helped a lot.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 1 year ago (1 child)

    Nice! Sounds like a learning experience. Was it a fun challenge for you or annoying, in the end?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 1 year ago

    Haha both of course. Young me was intrigued by this great puzzle of getting the system back up. Much quicker than a reinstall, too! At the same time it was one of the Gentoo moments that made me switch to Arch and Manjaro later. I certainly learned a lot with Gentoo but it was also a fragile timesink.

  • source
  • parent
  • [–] 1 point 1 year ago* (1 child)

    I suppose to rescue it you can grab a portable Python release and use that to emerge a proper one, another option would be booting into a live environment. And to cause this, --unmerge and --rage-clean are your friends. No idea how you'd do that "accidentally", though.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 1 year ago

    I remember I struggled with broken dynamic linking from bringing in binaries from the outside. I needed an entire build-chain from the same build and then build my way up with source packages (you have them around in gentoo) in my system until i reached portage. And then used emerge to recompile the buildchain twice so it was compatible with my system again.

  • source
  • parent