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.
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.
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.
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.
I sure hope there are ways to unpack RPMs by hand and copy the contents where they need to be. Would be very unlinuxy to make it a binary format and not a zipped container of some sort. But you might struggle depending on the amount of dependencies.
I once accidentally deleted python from my gentoo system (needed for emerge) and rescued it.
You are the chosen one.
How did you do that? (Both "that"s I guess!)
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.
Nice! Sounds like a learning experience. Was it a fun challenge for you or annoying, in the end?
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.
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,
--unmergeand--rage-cleanare your friends. No idea how you’d do that “accidentally”, though.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.
Wow, I did that on CentOS and reinstalling the OS was the only sure shot way I could figure
I sure hope there are ways to unpack RPMs by hand and copy the contents where they need to be. Would be very unlinuxy to make it a binary format and not a zipped container of some sort. But you might struggle depending on the amount of dependencies.
Yeah, figuring out which dependencies in which locations just seemed not worth it