bpaddock

Thank you.

Thank you. Because my system is already having issues I am moving to a new clean new container. Only problem so far is the cerbot dependancy dev-python/parsedatetime is not in release-next and it is in the old portage. Is there a procedure for such things to get it properly in release-next portage?

What is the procedure to upgrade a 1.4 container to next-release? As it is hosting all my websites I don't really want to take it down to do a fresh install. Not even sure how to do that on a container?

I just upgraded my container from 1.3 to 1.4 all went well until I rebooted and did a eix-sync that called ego. ego failed saying it could not find the module 'portage'. The fix was simple enough once I figured it out, it should be added to the upgrade instructions. https://www.funtoo.org/Upgrade_Instructions/1.4-release Must make sure that python-3.7 is selected with eselect python. Before doing that the removed 3.6 was still in the list. Is that something that esleect python cleanup should have fixed? I know I ran it.

I was trying to update my Funtoo Virtual Container ( https://www.funtoo.org/Funtoo_Containers ) that I had been lacks in keeping up to date (everything was working fine). Now I've dug myself a deep hole that I need help getting out of. First I did a eix-sync (ego sync) which lead to a error report very similar to the one in this bug report, that is closed yet has people still showing the same problem: https://bugs.funtoo.org/browse/FL-5504?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel I tried to recompile ego as the bug report : https://forums.funtoo.org/topic/1633-more-trouble-ego-problem/ indicates and that in turn lead to "it does the same , im really really starting to hate python". Me too. Which in turn lead me to somehow screwing up my profile. Which should be a simple server profile for the Container. So I seem to have a circular breakage of my profile is broken, I need to update ego and can't because something is wrong with python in the profile. I can still compile something like eix just fine, so the system is not completely down, yet at least. It would seem I need to fix my profile, without ego, get a viable default python set in the profile, then recompile ego. Help? Please. This is the ego traceback:

I added the items I mentioned to the wiki. Should the section about using 6.5.7 be deleted or changed to 0.7.3? I did not see that the accept_keyword was having any effect.

I edited my question above to the current state of things. I have tried, NUMEROUS times, following the ZFS install guide line by line only changing the disk-ids . I used the stage3 via wget as the wiki instructed. I got a fresh one today at about 11AM EST. I know the wiki instructions worked in the past last time I installed my system, sometime ago. I believe something is not correct with with the state of portage, I don't know what. The current combination of zfs-0.7.3, grub and genkernal are not playing well together.

I am trying to bring up a system with ZFS following https://www.funtoo.org/ZFS_Install_Guide I'm having trouble booting. at the completion of the steps in the Guide. # grub-mkconfig -o /boot/grub/grub.cfg None of the 'initramfs-genkernel-XXXX' are being found that were build with the --zfs flag. The Guide indicates these initramfs-genkernel's should be the ones found in its example output. grub-mkconfig is finding the normal initramfs-debian-sources-XXXX and kernel files and these were not build with the --zfs flag to my knowledge. Anyone have any idea why this is happening and how to fix it? If I force a menu entry in /etc/grub.d/40_custom that uses initramfs-genkernel-XXXX the system will boot until it reaches the point where it tries to import the pools. Gives error cannot import 'rpool' no such pool or dataset destroy and re-create the pool... Yet if I go to the grub shell and do a zpool import rpool is found. What is going on here? I think something is broken as when emerging zfs, zfs-0.7.3 and and a new grub were pulled in. Has anyone gotten zfs install to work with the *current* portage? I know it worked in the past, doesn't seem to be working now.